RTN 620 Feature

OptiX RTN 600 Radio Transmission System V100R003
Feature Description
Issue Date
02 2009-02-25
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
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:
Copyright Huawei Technologies Co., Ltd. 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 the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
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 the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
OptiX RTN 600 Radio Transmission System Feature Description
Contents
Contents
About This Document.....................................................................................................................1 1 Introduction to the DCN...........................................................................................................1-1
1.1 Composition of the DCN.................................................................................................................................1-2 1.2 Huawei DCN Solution....................................................................................................................................1-3
2 HW ECC Solution......................................................................................................................2-1
2.1 Feature Description.........................................................................................................................................2-3 2.2 Basic Concepts................................................................................................................................................2-3 2.2.1 HW ECC Protocol Stack........................................................................................................................2-4 2.2.2 Extended ECC........................................................................................................................................2-6 2.3 Availability......................................................................................................................................................2-9 2.4 Relation with Other Features...........................................................................................................................2-9 2.5 Realization Principle.......................................................................................................................................2-9 2.5.1 How to Establish ECC Routes.............................................................................................................2-10 2.5.2 How to Transfer Messages...................................................................................................................2-11 2.5.3 Extended ECC......................................................................................................................................2-12 2.6 Planning Guide..............................................................................................................................................2-13 2.7 Configuration Guide......................................................................................................................................2-17 2.7.1 Configuration Flow..............................................................................................................................2-17 2.7.2 Modifying the NE ID...........................................................................................................................2-20 2.7.3 Modifying the Communication Parameters of an NE..........................................................................2-21 2.7.4 Configuring DCCs................................................................................................................................2-23 2.7.5 Configuring the Extended ECC............................................................................................................2-25 2.7.6 Configuring DCC Transparent Transmission......................................................................................2-27 2.7.7 Querying ECC Routes..........................................................................................................................2-28 2.7.8 Creating NEs by Using the Search Method.........................................................................................2-29 2.7.9 Creating NEs by Using the Manual Method........................................................................................2-31 2.8 Configuration Example.................................................................................................................................2-34 2.9 Maintenance Guide.......................................................................................................................................2-35 2.9.1 Relevant Alarms and Events................................................................................................................2-35 2.9.2 FAQs....................................................................................................................................................2-36
3 IP over DCC Solution................................................................................................................3-1

3.1 Feature Description.........................................................................................................................................3-3 Issue 02 (2009-02-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. i
Contents
3.2 Basic Concepts................................................................................................................................................3-3 3.2.1 IP over DCC Protocol Stack...................................................................................................................3-3 3.2.2 Access Modes.........................................................................................................................................3-5 3.3 Availability......................................................................................................................................................3-6 3.4 Relation with Other Features...........................................................................................................................3-6 3.5 Realization Principle.......................................................................................................................................3-7 3.6 Planning Guide................................................................................................................................................3-8 3.7 Configuration Guide......................................................................................................................................3-11 3.7.1 Configuration Flow..............................................................................................................................3-12 3.7.2 Querying IP Routes..............................................................................................................................3-13 3.7.3 Creating Static IP Routes.....................................................................................................................3-14 3.8 Configuration Example.................................................................................................................................3-15 3.9 Maintenance Guide.......................................................................................................................................3-16 3.9.1 Relevant Alarms and Events................................................................................................................3-16 3.9.2 FAQs....................................................................................................................................................3-17
4 OSI over DCC Solution.............................................................................................................4-1

4.1 Feature Description.........................................................................................................................................4-3 4.2 Basic Concepts................................................................................................................................................4-3 4.2.1 OSI over DCC Protocol Stack................................................................................................................4-3 4.2.2 Access Mode..........................................................................................................................................4-6 4.3 Availability......................................................................................................................................................4-7 4.4 Relation with Other Features...........................................................................................................................4-7 4.5 Realization Principle.......................................................................................................................................4-8 4.6 Planning Guide................................................................................................................................................4-9 4.7 Configuration Guide......................................................................................................................................4-12 4.7.1 Configuration Flow..............................................................................................................................4-13 4.7.2 Configuring the CLNS Role.................................................................................................................4-14 4.7.3 Querying OSI Routes...........................................................................................................................4-15 4.8 Configuration Example.................................................................................................................................4-16 4.9 Maintenance Guide.......................................................................................................................................4-17 4.9.1 Relevant Alarms and Events................................................................................................................4-17 4.9.2 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-6 5.5 Planning Guide................................................................................................................................................5-6 5.6 Configuration Flow.........................................................................................................................................5-9 5.7 Configuration Example.................................................................................................................................5-11 5.8 Maintenance Guide.......................................................................................................................................5-12 5.8.1 Relevant Alarms and Events................................................................................................................5-12 ii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-02-25)
Contents
5.8.2 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 6.4 Realization Principle.......................................................................................................................................6-4 6.5 Planning Guide................................................................................................................................................6-5 6.6 Configuration Flow.........................................................................................................................................6-7 6.7 Configuration Example...................................................................................................................................6-8 6.8 Maintenance Guide.........................................................................................................................................6-8 6.8.1 Relevant Alarms and Events..................................................................................................................6-8 6.8.2 FAQs......................................................................................................................................................6-9
7 1+1 HSB........................................................................................................................................7-1
7.1 Feature Description.........................................................................................................................................7-2 7.2 Basic Concepts................................................................................................................................................7-2 7.2.1 System Configuration.............................................................................................................................7-2 7.2.2 Protection Type......................................................................................................................................7-4 7.2.3 Switching Conditions.............................................................................................................................7-4 7.2.4 Switching Impact....................................................................................................................................7-7 7.3 Availability......................................................................................................................................................7-8 7.4 Relation with Other Features...........................................................................................................................7-8 7.5 Realization Principle.......................................................................................................................................7-8 7.5.1 SDH/PDH Microwave............................................................................................................................7-9 7.5.2 Hybrid Microwave...............................................................................................................................7-11 7.6 Planning Guide..............................................................................................................................................7-14 7.7 Configuration Guide......................................................................................................................................7-14 7.7.1 Creating IF 1+1 Protection...................................................................................................................7-14 7.7.2 Modifying the Parameters of IF 1+1 Protection...................................................................................7-18 7.8 Maintenance Guide.......................................................................................................................................7-21 7.8.1 IF 1+1 Protection Switching................................................................................................................7-21 7.8.2 Relevant Alarms and Events................................................................................................................7-22 7.8.3 FAQs....................................................................................................................................................7-22
8 1+1 FD...........................................................................................................................................8-1
8.1 Feature Description.........................................................................................................................................8-2 8.2 Basic Concepts................................................................................................................................................8-2 8.2.1 System Configuration.............................................................................................................................8-2 8.2.2 Protection Type......................................................................................................................................8-5 8.2.3 Switching Conditions.............................................................................................................................8-6 8.2.4 Switching Impact....................................................................................................................................8-9 8.3 Availability......................................................................................................................................................8-9 8.4 Relation with Other Features...........................................................................................................................8-9 Issue 02 (2009-02-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
Contents
8.5 Realization Principle.....................................................................................................................................8-10 8.5.1 SDH/PDH Microwave..........................................................................................................................8-10 8.5.2 Hybrid Microwave...............................................................................................................................8-12 8.6 Planning Guide..............................................................................................................................................8-16 8.7 Configuration Guide......................................................................................................................................8-17 8.7.1 Creating IF 1+1 Protection...................................................................................................................8-17 8.7.2 Modifying the Parameters of IF 1+1 Protection...................................................................................8-21 8.8 Maintenance Guide.......................................................................................................................................8-23 8.8.1 IF 1+1 Protection Switching................................................................................................................8-24 8.8.2 Relevant Alarms and Events................................................................................................................8-24 8.8.3 FAQs....................................................................................................................................................8-25
9 1+1 SD...........................................................................................................................................9-1
9.1 Feature Description.........................................................................................................................................9-2 9.2 Basic Concepts................................................................................................................................................9-2 9.2.1 System Configuration.............................................................................................................................9-2 9.2.2 Protection Type......................................................................................................................................9-4 9.2.3 Switching Conditions.............................................................................................................................9-4 9.2.4 Switching Impact....................................................................................................................................9-8 9.3 Availability......................................................................................................................................................9-8 9.4 Relation with Other Features...........................................................................................................................9-9 9.5 Realization Principle.......................................................................................................................................9-9 9.5.1 SDH/PDH Microwave............................................................................................................................9-9 9.5.2 Hybrid Microwave...............................................................................................................................9-12 9.6 Planning Guide..............................................................................................................................................9-16 9.7 Configuration Guide......................................................................................................................................9-16 9.7.1 Creating IF 1+1 Protection...................................................................................................................9-16 9.7.2 Modifying the Parameters of IF 1+1 Protection...................................................................................9-20 9.8 Maintenance Guide.......................................................................................................................................9-23 9.8.1 IF 1+1 Protection Switching................................................................................................................9-23 9.8.2 Relevant Alarms and Events................................................................................................................9-24 9.8.3 FAQs....................................................................................................................................................9-24
10 Cross-Polarization Interference Cancellation...................................................................10-1

10.1 Feature Description.....................................................................................................................................10-2 10.2 Basic Concepts............................................................................................................................................10-2 10.2.1 CCDP and XPIC.................................................................................................................................10-3 10.2.2 System Configuration.........................................................................................................................10-4 10.3 Availability..................................................................................................................................................10-5 10.4 Relation with Other Features.......................................................................................................................10-5 10.5 Realization Principle...................................................................................................................................10-6 10.6 Planning Guide............................................................................................................................................10-7 10.7 Creating an XPIC Workgroup.....................................................................................................................10-8 10.8 Maintenance Guide...................................................................................................................................10-12 iv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-02-25)
Contents
10.8.1 Relevant Alarms and Events............................................................................................................10-12 10.8.2 FAQs................................................................................................................................................10-13
11 N+1 Protection........................................................................................................................11-1
11.1 Feature Description.....................................................................................................................................11-2 11.2 Basic Concepts............................................................................................................................................11-2 11.2.1 System Configuration.........................................................................................................................11-3 11.2.2 Protection Type..................................................................................................................................11-7 11.2.3 Switching Condition...........................................................................................................................11-7 11.2.4 Switching Impact................................................................................................................................11-9 11.3 Availability..................................................................................................................................................11-9 11.4 Relation with Other Features.......................................................................................................................11-9 11.5 Realization Principle.................................................................................................................................11-10 11.5.1 2+1 Protection Configuration...........................................................................................................11-10 11.5.2 3+1 Protection Configuration...........................................................................................................11-11 11.6 Planning Guide..........................................................................................................................................11-14 11.7 Configuration Guide..................................................................................................................................11-14 11.7.1 Configuration Flow..........................................................................................................................11-15 11.7.2 Creating an N+1 Protection Group...................................................................................................11-15 11.7.3 Creating REGs..................................................................................................................................11-18 11.7.4 Configuration Example....................................................................................................................11-21 11.8 Maintenance Guide...................................................................................................................................11-21 11.8.1 Starting/Stopping the N+1 Protection Protocol................................................................................11-21 11.8.2 N+1 Protection Switching................................................................................................................11-22 11.8.3 Relevant Alarms and Events............................................................................................................11-22 11.8.4 FAQs................................................................................................................................................11-23
12 Automatic Transmit Power Control Function..................................................................12-1

12.1 Feature Description.....................................................................................................................................12-2 12.2 Availability..................................................................................................................................................12-2 12.3 Relation with Other Features.......................................................................................................................12-3 12.4 Realization Principle...................................................................................................................................12-3 12.5 Planning Guide............................................................................................................................................12-5 12.6 Configuring the ATPC Function.................................................................................................................12-5 12.7 Maintenance Guide ....................................................................................................................................12-8 12.7.1 Relevant Alarms and Events..............................................................................................................12-8 12.7.2 FAQs..................................................................................................................................................12-9
13 Hybrid Microwave.................................................................................................................13-1
13.1 Feature Description.....................................................................................................................................13-2 13.2 Basic Concepts............................................................................................................................................13-2 13.2.1 Service Transmission Mode...............................................................................................................13-3 13.2.2 AM.....................................................................................................................................................13-4 13.2.3 Working Mode...................................................................................................................................13-5 Issue 02 (2009-02-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
Contents
OptiX RTN 600 Radio Transmission System Feature Description 13.2.4 QoS Control for Ethernet Services.....................................................................................................13-6
13.3 Availability..................................................................................................................................................13-7 13.4 Relation with Other Features.......................................................................................................................13-7 13.5 Realization Principle...................................................................................................................................13-8 13.6 Planning Guide..........................................................................................................................................13-10 13.7 Configuration Guide..................................................................................................................................13-11 13.8 Maintenance Guide...................................................................................................................................13-11 13.8.1 Relevant Alarms and Events............................................................................................................13-12 13.8.2 FAQs................................................................................................................................................13-12
14 Sub-Network Connection Protection.................................................................................14-1

14.1 Feature Description.....................................................................................................................................14-2 14.2 Basic Concepts............................................................................................................................................14-2 14.2.1 Protection Type..................................................................................................................................14-3 14.2.2 SNCP Service Pair.............................................................................................................................14-3 14.2.3 Switching Condition...........................................................................................................................14-3 14.2.4 Switching Impact................................................................................................................................14-6 14.3 Availability..................................................................................................................................................14-6 14.4 Relation with Other Features.......................................................................................................................14-7 14.5 Realization Principle...................................................................................................................................14-7 14.6 Planning Guide............................................................................................................................................14-8 14.7 Configuration Guide....................................................................................................................................14-9 14.7.1 Creating Cross-Connections for SNCP Services...............................................................................14-9 14.7.2 Setting the Automatic Switching Conditions of SNCP Services.....................................................14-13 14.7.3 Converting Normal Services into SNCP Services...........................................................................14-15 14.7.4 Converting SNCP Services into Normal Services...........................................................................14-18 14.8 Maintenance Guide...................................................................................................................................14-19 14.8.1 SNCP Switching...............................................................................................................................14-19 14.8.2 Relevant Alarms and Events............................................................................................................14-20 14.8.3 FAQs................................................................................................................................................14-20
15 Linear Multiplex Section Protection...................................................................................15-1

15.1 Feature Description.....................................................................................................................................15-3 15.2 Basic Concepts............................................................................................................................................15-4 15.2.1 Protection Type..................................................................................................................................15-5 15.2.2 Meaning of Byte K.............................................................................................................................15-6 15.2.3 Switching Condition...........................................................................................................................15-7 15.2.4 Switching Impact................................................................................................................................15-9 15.3 Availability..................................................................................................................................................15-9 15.4 Relation with Other Features.....................................................................................................................15-10 15.5 Realization Principle.................................................................................................................................15-10 15.5.1 1+1 Linear MSP...............................................................................................................................15-10 15.5.2 1:N Linear MSP...............................................................................................................................15-12 15.6 Planning Guide..........................................................................................................................................15-13 vi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-02-25)
Contents
15.7 Creating Linear MSP.................................................................................................................................15-13 15.8 Maintenance Guide...................................................................................................................................15-18 15.8.1 Starting/Stopping the Linear MSP Protocol.....................................................................................15-18 15.8.2 Linear MSP Switching.....................................................................................................................15-19 15.8.3 Relevant Alarms and Events............................................................................................................15-19 15.8.4 FAQs................................................................................................................................................15-20
16 Two-Fiber Bidirectional Ring MSP....................................................................................16-1

16.1 Feature Description.....................................................................................................................................16-3 16.2 Basic Concepts............................................................................................................................................16-4 16.2.1 Protection Type..................................................................................................................................16-4 16.2.2 Meaning of Byte K.............................................................................................................................16-4 16.2.3 Switching Condition...........................................................................................................................16-6 16.2.4 Switching Impact................................................................................................................................16-8 16.3 Availability..................................................................................................................................................16-8 16.4 Relation with Other Features.......................................................................................................................16-8 16.5 Realization Principle...................................................................................................................................16-8 16.6 Planning Guide..........................................................................................................................................16-10 16.7 Configuring the Ring MSP........................................................................................................................16-11 16.8 Maintenance Guide...................................................................................................................................16-14 16.8.1 Starting/Stopping the Ring MSP Protocol.......................................................................................16-14 16.8.2 Ring MSP Switching........................................................................................................................16-15 16.8.3 Relevant Alarms and Events............................................................................................................16-15 16.8.4 FAQs................................................................................................................................................16-15
17 Features of Ethernet Ports.....................................................................................................17-1

17.1 Feature Description.....................................................................................................................................17-2 17.2 Basic Concepts............................................................................................................................................17-2 17.2.1 Auto-Negotiation Function................................................................................................................17-3 17.2.2 Jumbo Frames....................................................................................................................................17-4 17.2.3 Flow Control Function.......................................................................................................................17-5 17.3 Availability..................................................................................................................................................17-6 17.4 Relation with Other Features.......................................................................................................................17-7 17.5 Realization Principle...................................................................................................................................17-7 17.5.1 Auto-Negotiation Function................................................................................................................17-7 17.5.2 Flow Control Function.......................................................................................................................17-8 17.6 Planning Guide............................................................................................................................................17-9 17.7 Configuration Guide..................................................................................................................................17-10 17.7.1 Configuring External Ethernet Ports................................................................................................17-10 17.7.2 Modifying the Type Field of Jumbo Frames....................................................................................17-18 17.8 Maintenance Guide...................................................................................................................................17-19 17.8.1 Relevant Alarms and Events............................................................................................................17-19 17.8.2 FAQs................................................................................................................................................17-20
Issue 02 (2009-02-25)
vii
Contents
18 Encapsulation and Mapping of Ethernet Services...........................................................18-1

18.1 Feature Description.....................................................................................................................................18-3 18.2 Basic Concepts............................................................................................................................................18-4 18.2.1 Encapsulation and Mapping Protocols...............................................................................................18-4 18.2.2 Virtual Concatenation........................................................................................................................18-5 18.2.3 LCAS..................................................................................................................................................18-5 18.3 Availability..................................................................................................................................................18-6 18.4 Relation with Other Features.......................................................................................................................18-6 18.5 Realization Principle...................................................................................................................................18-6 18.5.1 Encapsulation and Mapping...............................................................................................................18-6 18.5.2 Virtual Concatenation......................................................................................................................18-10 18.5.3 LCAS................................................................................................................................................18-11 18.6 Planning Guide..........................................................................................................................................18-15 18.7 Configuring the Internal Port of the Ethernet Board.................................................................................18-16 18.8 Maintenance Guide...................................................................................................................................18-24 18.8.1 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth....................................................18-24 18.8.2 Relevant Alarms and Events............................................................................................................18-26 18.8.3 FAQs................................................................................................................................................18-27
19 VLAN........................................................................................................................................19-1
19.1 Feature Description.....................................................................................................................................19-3 19.2 Basic Concepts............................................................................................................................................19-3 19.2.1 Frame Format.....................................................................................................................................19-4 19.2.2 TAG Attribute....................................................................................................................................19-4 19.2.3 Application.........................................................................................................................................19-5 19.3 Availability..................................................................................................................................................19-7 19.4 Relation with Other Features.......................................................................................................................19-7 19.5 Realization Principle...................................................................................................................................19-7 19.6 Planning Guide............................................................................................................................................19-7 19.7 Configuration Guide....................................................................................................................................19-8 19.7.1 Configuration Flow............................................................................................................................19-8 19.7.2 Creating Ethernet Line Service........................................................................................................19-10 19.8 Configuration Example (PORT-Shared EVPL Service)...........................................................................19-15 19.9 Configuration Example (VCTRUNK-Shared EVPL Service)..................................................................19-16 19.10 Maintenance Guide.................................................................................................................................19-17 19.10.1 Relevant Alarms and Events..........................................................................................................19-18 19.10.2 FAQs..............................................................................................................................................19-18
20 Layer 2 Switching...................................................................................................................20-1
20.1 Feature Description.....................................................................................................................................20-2 20.2 Basic Concepts............................................................................................................................................20-2 20.2.1 Bridge.................................................................................................................................................20-3 20.2.2 STP/RSTP..........................................................................................................................................20-6 20.2.3 IGMP Snooping..................................................................................................................................20-7 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-02-25)
Contents
20.2.4 Broadcast Packet Suppression............................................................................................................20-9 20.3 Availability................................................................................................................................................20-10 20.4 Relation with Other Features.....................................................................................................................20-10 20.5 Realization Principle.................................................................................................................................20-10 20.5.1 Bridge...............................................................................................................................................20-11 20.5.2 STP/RSTP........................................................................................................................................20-11 20.5.3 IGMP Snooping................................................................................................................................20-16 20.6 Planning Guide..........................................................................................................................................20-18 20.7 Configuration Guide..................................................................................................................................20-19 20.7.1 Creating the Ethernet LAN Service..................................................................................................20-20 20.7.2 Modifying the Mounted Port of a Bridge.........................................................................................20-25 20.7.3 Creating the VLAN Filter Table......................................................................................................20-27 20.7.4 Creating the Entry of a MAC Address Table Manually ..................................................................20-29 20.7.5 Modifying the Aging Time of the MAC Address Table Entry........................................................20-31 20.7.6 Configuring the Spanning Tree Protocol ........................................................................................20-32 20.7.7 Configuring the IGMP Snooping Protocol.......................................................................................20-37 20.7.8 Modifying the Aging Time of the Multicast Table Item..................................................................20-38 20.7.9 Configuring the Broadcast Packet Suppression Function................................................................20-40 20.8 Maintenance Guide...................................................................................................................................20-41 20.8.1 Querying the Actual Capacity of the MAC Address Table and the Dynamic Entry.......................20-41 20.8.2 Querying the Running Information About the Spanning Tree Protocol..........................................20-42 20.8.3 Querying the Running Information About the IGMP Snooping Protocol ......................................20-43 20.8.4 Relevant Alarms and Events............................................................................................................20-44 20.8.5 FAQs................................................................................................................................................20-44
21 QoS............................................................................................................................................21-1
21.1 Feature Description.....................................................................................................................................21-2 21.2 Basic Concepts............................................................................................................................................21-3 21.2.1 Flow Classification.............................................................................................................................21-3 21.2.2 CAR....................................................................................................................................................21-4 21.2.3 CoS.....................................................................................................................................................21-5 21.2.4 Traffic Shaping...................................................................................................................................21-6 21.3 Availability..................................................................................................................................................21-7 21.4 Relation with Other Features.......................................................................................................................21-7 21.5 Realization Principle...................................................................................................................................21-8 21.5.1 CAR....................................................................................................................................................21-8 21.5.2 Traffic Shaping.................................................................................................................................21-10 21.5.3 Egress Queue Scheduling.................................................................................................................21-10 21.6 Planning Guide..........................................................................................................................................21-13 21.7 Configuration Guide..................................................................................................................................21-14 21.7.1 Creating a Flow................................................................................................................................21-15 21.7.2 Creating the CAR.............................................................................................................................21-17 21.7.3 Creating the CoS..............................................................................................................................21-20 Issue 02 (2009-02-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
OptiX RTN 600 Radio Transmission System Feature Description 21.7.4 Binding the CAR/CoS......................................................................................................................21-23 21.7.5 Configuring the Traffic Shaping......................................................................................................21-24 21.7.6 Configuring the CoS of the IFH2 Board..........................................................................................21-25 21.7.7 Setting the Queue Scheduling Mode................................................................................................21-26
21.8 Maintenance Guide...................................................................................................................................21-27 21.8.1 Relevant Alarms and Events............................................................................................................21-27 21.8.2 FAQs................................................................................................................................................21-28
22 QinQ.........................................................................................................................................22-1
22.1 Feature Description.....................................................................................................................................22-3 22.2 Basic Concepts............................................................................................................................................22-3 22.2.1 Frame Format.....................................................................................................................................22-3 22.2.2 Network Attributes.............................................................................................................................22-5 22.2.3 Application of the QinQ Technology in Line Services......................................................................22-6 22.2.4 Application of the QinQ Technology in LAN Services.....................................................................22-8 22.3 Availability................................................................................................................................................22-10 22.4 Relation with Other Features.....................................................................................................................22-11 22.5 Realization Principle.................................................................................................................................22-11 22.6 Planning Guide..........................................................................................................................................22-13 22.6.1 EVPL Services Based on QinQ........................................................................................................22-13 22.6.2 EVPLAN Services Based on the IEEE 802.1ad Bridge...................................................................22-15 22.7 Configuration Guide..................................................................................................................................22-16 22.7.1 Configuration Flow (EVPL Services Based on QinQ)....................................................................22-17 22.7.2 Configuration Flow (EVPLAN Services Based on the IEEE 802.1ad Bridge)...............................22-18 22.7.3 Modifying the Type Field of QinQ Frames.....................................................................................22-20 22.7.4 Creating QinQ Line Services...........................................................................................................22-21 22.7.5 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge...............................22-25 22.8 Configuration Example (EVPL Services Based on QinQ).......................................................................22-30 22.9 Configuration Example (EVPLAN Services Based on the IEEE 802.1ad Bridge)..................................22-32 22.10 Maintenance Guide.................................................................................................................................22-33 22.10.1 Relevant Alarms and Events..........................................................................................................22-34 22.10.2 FAQs..............................................................................................................................................22-34
23 Remote Monitoring Feature.................................................................................................23-1

23.1 Feature Description.....................................................................................................................................23-3 23.2 Basic Concepts............................................................................................................................................23-3 23.2.1 SNMP.................................................................................................................................................23-3 23.2.2 RMON Management Groups.............................................................................................................23-4 23.2.3 RMON Alarms and Performance Events...........................................................................................23-6 23.3 Availability................................................................................................................................................23-12 23.4 Relation with Other Features.....................................................................................................................23-13 23.5 Realization Principle.................................................................................................................................23-13 23.6 Planning Guide..........................................................................................................................................23-14 23.7 Configuration Guide..................................................................................................................................23-15 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-02-25)
Contents
23.8 Maintenance Guide...................................................................................................................................23-15 23.8.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port...................................23-15 23.8.2 Configuring an Alarm Group for an Ethernet Port..........................................................................23-16 23.8.3 Configuring a History Control Group..............................................................................................23-17 23.8.4 Browsing the Performance Data in the History Group of an Ethernet Port.....................................23-18 23.8.5 FAQs................................................................................................................................................23-19
24 ETH OAM................................................................................................................................24-1
24.1 Feature Introduction....................................................................................................................................24-3 24.2 Basic Concept..............................................................................................................................................24-4 24.2.1 IEEE 802.1ag OAM Management.....................................................................................................24-4 24.2.2 IEEE 802.1ag OAM Operation..........................................................................................................24-7 24.2.3 IEEE 802.3ah OAM Operations.........................................................................................................24-9 24.3 Availability................................................................................................................................................24-10 24.4 Relations with Other Features...................................................................................................................24-10 24.5 Function Implementation..........................................................................................................................24-10 24.5.1 802.1ag OAM...................................................................................................................................24-11 24.5.2 802.3ah OAM...................................................................................................................................24-15 24.6 Planning Guide..........................................................................................................................................24-23 24.6.1 IEEE 802.1ag OAM.........................................................................................................................24-23 24.6.2 IEEE 802.3ah OAM.........................................................................................................................24-24 24.7 Using the IEEE 802.1ag OAM..................................................................................................................24-25 24.7.1 Configuration Flow..........................................................................................................................24-26 24.7.2 Creating MDs...................................................................................................................................24-27 24.7.3 Creating MAs...................................................................................................................................24-29 24.7.4 Creating MPs....................................................................................................................................24-30 24.7.5 Performing a Continuity Check........................................................................................................24-33 24.7.6 Performing a Loopback Check.........................................................................................................24-34 24.7.7 Performing a Link Trace Check.......................................................................................................24-35 24.7.8 Activating the AIS............................................................................................................................24-37 24.7.9 Performing a Ping Test.....................................................................................................................24-38 24.7.10 Performing Performance Detection................................................................................................24-41 24.8 IEEE 802.1ag OAM Example...................................................................................................................24-43 24.9 Using the IEEE 802.3ah OAM..................................................................................................................24-43 24.9.1 Configuration Flow..........................................................................................................................24-44 24.9.2 Enabling the Auto-Discovery Function of OAM.............................................................................24-46 24.9.3 Enabling the Link Event Notification..............................................................................................24-49 24.9.4 Modifying the Parameters of the OAM Error Frame Monitoring Threshold...................................24-52 24.9.5 Performing the Remote Loopback...................................................................................................24-54 24.9.6 Enabling the Self-Loop Detection....................................................................................................24-55 24.10 Maintenance Guide.................................................................................................................................24-56 24.10.1 Relevant Alarms and Events..........................................................................................................24-57 24.10.2 FAQs..............................................................................................................................................24-58 Issue 02 (2009-02-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
25 Link aggregation.....................................................................................................................25-1
25.1 Overview.....................................................................................................................................................25-3 25.2 Basic Concepts............................................................................................................................................25-3 25.2.1 LAG Types.........................................................................................................................................25-4 25.2.2 Port Types..........................................................................................................................................25-4 25.2.3 Switching Conditions.........................................................................................................................25-5 25.2.4 Switching Impact................................................................................................................................25-6 25.3 Availability..................................................................................................................................................25-6 25.4 Relation with Other Features.......................................................................................................................25-6 25.5 Principle......................................................................................................................................................25-6 25.6 Service Planning..........................................................................................................................................25-7 25.7 Creating a LAG...........................................................................................................................................25-9 25.8 Maintenance Guide...................................................................................................................................25-17 25.8.1 Relevant Alarms and Events............................................................................................................25-18 25.8.2 FAQs................................................................................................................................................25-18
26 Link State Pass Through.......................................................................................................26-1

26.1 Feature Description.....................................................................................................................................26-2 26.2 Availability..................................................................................................................................................26-4 26.3 Relation with Other Features.......................................................................................................................26-4 26.4 Realization Principle...................................................................................................................................26-4 26.4.1 Point-to-Point Service........................................................................................................................26-4 26.4.2 Point-to-Multipoint Service................................................................................................................26-6 26.5 Planning Guide..........................................................................................................................................26-10 26.6 LPT Configuration....................................................................................................................................26-11 26.7 Maintenance Guide...................................................................................................................................26-15 26.7.1 Relevant Alarms and Events............................................................................................................26-15 26.7.2 FAQs................................................................................................................................................26-16
27 Synchronous Ethernet...........................................................................................................27-1
27.1 Feature Description.....................................................................................................................................27-2 27.2 Availability..................................................................................................................................................27-2 27.3 Relation with Other Features.......................................................................................................................27-3 27.4 Realization Principle...................................................................................................................................27-3 27.5 Planning Guide............................................................................................................................................27-4 27.6 Configuration Guide....................................................................................................................................27-5 27.6.1 Configuring the Clock Sources..........................................................................................................27-5 27.6.2 Configuring the Ethernet Clock Source.............................................................................................27-7 27.7 Maintenance Guide.....................................................................................................................................27-8 27.7.1 Checking the Clock Synchronization Status......................................................................................27-8 27.7.2 Relevant Alarms and Events..............................................................................................................27-9 27.7.3 FAQs..................................................................................................................................................27-9
28 Glossary....................................................................................................................................28-1
xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-02-25)
Contents
29 Acronyms and Abbreviations..............................................................................................29-1
Issue 02 (2009-02-25)
xiii
Figures
Figures
Figure 1-1 DCN....................................................................................................................................................1-2 Figure 2-1 Networking of the HW ECC solution.................................................................................................2-3 Figure 2-2 Architecture of the HW ECC protocol stack .....................................................................................2-4 Figure 2-3 Networking for the extended ECC (using a network cable)...............................................................2-7 Figure 2-4 Networking for the extended ECC (using a hub)...............................................................................2-7 Figure 2-5 Networking for the extended ECC (using network cables to connect NEs in series)........................2-8 Figure 2-6 Networking example for establishing ECC routes ..........................................................................2-10 Figure 2-7 Realization principle of message transferring (HW ECC)...............................................................2-12 Figure 2-8 Networking example for the HW ECC solution...............................................................................2-15 Figure 2-9 Allocation of IDs and IP addresses for all NEs................................................................................2-16 Figure 2-10 Configuration flow for the HW ECC solution ...............................................................................2-18 Figure 3-1 Application of the IP over DCC solution...........................................................................................3-3 Figure 3-2 Architecture of the IP over DCC protocol stack ................................................................................3-4 Figure 3-3 Realization principle of message transferring (gateway mode).........................................................3-7 Figure 3-4 Realization principle of message transferring (direct connection mode)...........................................3-8 Figure 3-5 Networking example for the IP over DCC solution.........................................................................3-10 Figure 3-6 Allocation of IDs and IP addresses for all NEs................................................................................3-11 Figure 3-7 Configuration flow for the IP over DCC solution ...........................................................................3-12 Figure 4-1 Application of the OSI over DCC solution........................................................................................4-3 Figure 4-2 Architecture of the OSI over DCC protocol stack .............................................................................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 Realization principle of message transferring (gateway mode).........................................................4-8 Figure 4-6 Realization principle of message transferring (direct connection mode)...........................................4-9 Figure 4-7 Networking example for the OSI over DCC solution......................................................................4-11 Figure 4-8 Allocation of NE areas ....................................................................................................................4-12 Figure 4-9 Configuration flow for the OSI over DCC solution ........................................................................4-13 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
Issue 02 (2009-02-25)
xv
Figures
OptiX RTN 600 Radio Transmission System Feature Description 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 example for the DCC transparent transmission solution ...............................................5-8 Figure 5-7 Allocations of IDs and IP addresses for all NEs.................................................................................5-9 Figure 5-8 Configuration flow for the DCC transparent transmission solution ................................................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-6 Figure 6-5 Configuration flow for the DCC transparent transmission through the external clock interface solution ...............................................................................................................................................................................6-7 Figure 7-1 1+1 HSB protection............................................................................................................................7-2 Figure 7-2 Typical configuration of one 1+1 HSB protection group (IDU 620).................................................7-3 Figure 7-3 Typical configuration of one 1+1 HSB protection group (IDU 605 2B/2F)......................................7-4 Figure 7-4 1+1 HSB realization principle (before the switching, in the transmit direction)...............................7-9 Figure 7-5 1+1 HSB realization principle (before the switching, in the receive direction).................................7-9 Figure 7-6 1+1 HSB realization principle (after the switching, in the receive direction)..................................7-10 Figure 7-7 1+1 HSB realization principle (after the switching, in the transmit direction)................................ 7-10 Figure 7-8 1+1 HSB realization principle (before the switching, in the transmit direction)............................. 7-11 Figure 7-9 1+1 HSB realization principle (before the switching, in the receive direction)...............................7-12 Figure 7-10 1+1 HSB realization principle (after the switching, in the receive direction)................................7-13 Figure 7-11 1+1 HSB realization principle (after the switching, in the transmit direction).............................. 7-13 Figure 8-1 1+1 FD protection...............................................................................................................................8-2 Figure 8-2 Typical configuration 1 of one 1+1 FD protection group (IDU 620).................................................8-3 Figure 8-3 Typical configuration 2 of one 1+1 FD protection group (IDU 620).................................................8-4 Figure 8-4 Typical configuration 1 of one 1+1 FD protection group (IDU 605 2B/2F)......................................8-5 Figure 8-5 Typical configuration 2 of one 1+1 FD protection group (IDU 605 2B/2F)......................................8-5 Figure 8-6 1+1 FD realization principle (before the switching, in the transmit direction)................................8-10 Figure 8-7 1+1 FD realization principle (before the switching, in the receive direction)..................................8-11 Figure 8-8 1+1 FD HSB realization principle (after the switching, in the receive direction)............................8-11 Figure 8-9 1+1 FD HSM realization principle (after the switching, in the receive direction)...........................8-12 Figure 8-10 1+1 FD realization principle (before the switching, in the transmit direction)..............................8-13 Figure 8-11 1+1 FD realization principle (before the switching, in the receive direction)................................8-14 Figure 8-12 1+1 HSB realization principle (after the switching, in the transmit direction).............................. 8-15 Figure 8-13 1+1 FD HSB realization principle (after the switching, in the receive direction)..........................8-15 Figure 8-14 1+1 FD HSM realization principle (after the switching, in the receive direction).........................8-16 Figure 9-1 1+1 SD protection...............................................................................................................................9-2 Figure 9-2 Typical configuration of one 1+1 SD protection group (IDU 620)....................................................9-3 Figure 9-3 Typical configuration of one 1+1 SD protection group (IDU 605 2B/2F).........................................9-4 xvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-02-25)
Figures
Figure 9-4 1+1 SD realization principle (before the switching, in the transmit direction)................................9-10 Figure 9-5 1+1 SD realization principle (before the switching, in the receive direction)..................................9-10 Figure 9-6 1+1 SD HSB realization principle (after the switching, in the receive direction)............................9-11 Figure 9-7 1+1 SD HSB realization principle (after the switching, in the transmit direction)..........................9-11 Figure 9-8 1+1 SD HSM realization principle (after the switching, in the receive direction)...........................9-12 Figure 9-9 1+1 SD realization principle (before the switching, in the transmit direction)................................9-12 Figure 9-10 1+1 SD realization principle (before the switching, in the receive direction)................................9-13 Figure 9-11 1+1 SD HSB realization principle (after the switching, in the receive direction)..........................9-14 Figure 9-12 1+1 SD HSB realization principle (after the switching, in the transmit direction)........................9-14 Figure 9-13 1+1 SD HSM realization principle (after the switching, in the receive direction).........................9-15 Figure 10-1 Channel configuration in ACAP mode (without the application of the XPIC technology)...........10-2 Figure 10-2 Channel configuration in CCDP mode (with the application of the XPIC technology)................10-2 Figure 10-3 Single-polarization transmission....................................................................................................10-3 Figure 10-4 CCDP transmission.........................................................................................................................10-3 Figure 10-5 Typical configuration of XPIC.......................................................................................................10-4 Figure 10-6 Typical XPIC configuration (1+1 protection configuration)..........................................................10-6 Figure 10-7 Realization principle of XPIC........................................................................................................10-7 Figure 11-1 N+1 protection ...............................................................................................................................11-2 Figure 11-2 Typical configuration of one 2+1 protection group........................................................................11-4 Figure 11-3 Typical channel configuration of one 2+1 protection group..........................................................11-4 Figure 11-4 Typical configuration of one 3+1 protection group........................................................................11-6 Figure 11-5 Typical channel configuration of one 3+1 protection group..........................................................11-6 Figure 11-6 Realization principle of 2+1 protection (before the switching)....................................................11-10 Figure 11-7 Realization principle of 2+1 protection (after the switching).......................................................11-11 Figure 11-8 Realization principle of the 3+1 protection (before the switching)..............................................11-12 Figure 11-9 Realization principle of the 3+1 protection (after the switching).................................................11-13 Figure 11-10 Configuration flow for the N+1 protection mode.......................................................................11-15 Figure 12-1 ATPC realization principle.............................................................................................................12-4 Figure 13-1 Application of the Hybrid microwave feature................................................................................13-2 Figure 13-2 Multiplexing E1 services and Ethernet services into the Hybrid microwave frame......................13-3 Figure 13-3 Working principle of the Hybrid microwave .................................................................................13-4 Figure 13-4 Cable connection when the 1+1 protection is configured for the Hybrid microwave....................13-8 Figure 13-5 AM switching (before the switching).............................................................................................13-9 Figure 13-6 AM switching (after the switching)..............................................................................................13-10 Figure 14-1 Sub-Network Connection Protection..............................................................................................14-2 Figure 14-2 SNCP service pair...........................................................................................................................14-3 Figure 14-3 SNCP realization principle (before the switching).........................................................................14-7 Figure 14-4 SNCP realization principle (after the switching)............................................................................14-8 Figure 15-1 1+1 linear MSP ..............................................................................................................................15-3 Figure 15-2 1:N linear MSP ..............................................................................................................................15-4 Figure 15-3 Realization principle of 1+1 linear MSP (before the switching)..................................................15-10 Figure 15-4 Realization principle of 1+1 linear MSP (after the switching, in the single-ended mode)..........15-11 Issue 02 (2009-02-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Figures
OptiX RTN 600 Radio Transmission System Feature Description Figure 15-5 Realization principle of 1+1 linear MSP (after the switching, in the dual-ended mode).............15-11 Figure 15-6 Realization principle of 1:1 linear MSP (before the switching)...................................................15-12
Figure 15-7 Realization principle of 1:1 linear MSP (after the switching)......................................................15-12 Figure 16-1 Two-fiber bidirectional MSP ring..................................................................................................16-3 Figure 16-2 Realization principle of the two-fiber bidirectional ring MSP (before the switching)...................16-9 Figure 16-3 Realization principle of the two-fiber bidirectional ring MSP (after the switching)......................16-9 Figure 17-1 Waveform of a single FLP..............................................................................................................17-8 Figure 17-2 Consecutive FLP bursts and NLPs ................................................................................................17-8 Figure 17-3 Structure of the PAUSE frame.......................................................................................................17-9 Figure 18-1 Internal port of the Ethernet service board.....................................................................................18-3 Figure 18-2 Structure of the GFP frame ............................................................................................................18-7 Figure 18-3 GFP type field format.....................................................................................................................18-8 Figure 18-4 VC-3-Xv/VC-4-Xv multiframe and sequence indicator ..............................................................18-11 Figure 18-5 Capacity adjustment process (addition of a member) ..................................................................18-13 Figure 18-6 Capacity adjustment process (deletion of a member) ..................................................................18-13 Figure 18-7 Capacity adjustment process (one member link restored after a failure).....................................18-14 Figure 19-1 Tagged frame format......................................................................................................................19-4 Figure 19-2 PORT-shared EVPL service...........................................................................................................19-6 Figure 19-3 VCTRUNK-shared EVPL service..................................................................................................19-6 Figure 19-4 Configuration flow of the EPL service that uses the VLAN feature (PORT-shared or VCTRUNKshared EVPL service) .........................................................................................................................................19-9 Figure 20-1 Relations among the VB, LP, external port, and VCTRUNK port................................................20-3 Figure 20-2 802.1d bridge and 802.1q bridge....................................................................................................20-3 Figure 20-3 802.1ad Bridge................................................................................................................................20-4 Figure 20-4 Transmission of the multicast packet (with IGMP Snooping disabled).........................................20-8 Figure 20-5 Transmission of the multicast packet (with IGMP Snooping enabled)..........................................20-9 Figure 21-1 FIFO queue.....................................................................................................................................21-2 Figure 21-2 SP queue.........................................................................................................................................21-2 Figure 21-3 Basic principle of the token bucket algorithm................................................................................21-8 Figure 21-4 Basic principle of the algorithm that is used by the CAR..............................................................21-9 Figure 21-5 Basic principle of the algorithm that is used by the traffic shaping.............................................21-10 Figure 21-6 SP queue.......................................................................................................................................21-11 Figure 21-7 WRR scheduling algorithm..........................................................................................................21-12 Figure 21-8 SP+WRR scheduling algorithm....................................................................................................21-13 Figure 22-1 Format of the Ethernet frame with only a C-TAG.........................................................................22-4 Figure 22-2 Format of the Ethernet frame with a C-TAG and an S-TAG.........................................................22-4 Figure 22-3 Format of the Ethernet frame with only an S-TAG........................................................................22-5 Figure 22-4 EVPL (QinQ) Services.................................................................................................................22-11 Figure 22-5 Example of the EVPLAN (802.1ad bridge) service.....................................................................22-12 Figure 22-6 Ports used by the QinQ line services............................................................................................22-14 Figure 22-7 Configuration flow for the QinQ line service...............................................................................22-17 Figure 22-8 Configuration flow for the EVPLAN service that is based on the 802.1ad bridge......................22-19 Figure 24-1 Ethernet OAM solution..................................................................................................................24-3 xviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-02-25)
Figures
Figure 24-2 Logical diagram of maintenance domain layers.............................................................................24-7 Figure 24-3 IEEE 802.1ag OAMPDU.............................................................................................................24-11 Figure 24-4 Continuity check diagram.............................................................................................................24-12 Figure 24-5 Loopback test diagram..................................................................................................................24-13 Figure 24-6 Link trace test diagram.................................................................................................................24-14 Figure 24-7 IEEE 802.3ah OAMPDU.............................................................................................................24-15 Figure 24-8 Packet format of the information OAMPDU...............................................................................24-17 Figure 24-9 Packet format of event notification OAMPDU............................................................................24-21 Figure 24-10 Packet format of the loopback control OAMPDU.....................................................................24-22 Figure 24-11 IEEE 802.1ag OAM configuration flow.....................................................................................24-26 Figure 24-12 IEEE 802.3ah OAM configuration flow.....................................................................................24-45 Figure 25-1 Link aggregation group.................................................................................................................. 25-3 Figure 25-2 Application of the LACP protocol..................................................................................................25-7 Figure 25-3 Networking diagram of a LAG.......................................................................................................25-8 Figure 26-1 Point-to-Point LPT networking diagram........................................................................................26-2 Figure 26-2 Point-to-Multipoint LPT networking diagram............................................................................... 26-3 Figure 27-1 Application of the synchronous Ethernet in the wireless access network......................................27-2 Figure 27-2 Realization principle of the synchronous Ethernet.........................................................................27-4
Issue 02 (2009-02-25)
xix
Tables
Tables
Table 2-1 Availability of the HW ECC solution..................................................................................................2-9 Table 2-2 Description of the configuration flow of the HW ECC solution ...................................................... 2-19 Table 3-1 Availability of the IP over DCC solution.............................................................................................3-6 Table 3-2 Description of the configuration flow of the IP over DCC solution .................................................3-13 Table 4-1 Availability of the OSI over DCC solution..........................................................................................4-7 Table 4-2 Description of the configuration flow of the OSI over DCC solution ..............................................4-13 Table 5-1 Availability of the DCC transparent transmission solution.................................................................5-5 Table 5-2 Description of the configuration flow of the DCC transparent transmission solution ......................5-10 Table 6-1 Availability of the DCC transparent transmission through the external clock interface solution........6-4 Table 6-2 Description of the configuration flow of the DCC transparent transmission through the external clock interface solution...................................................................................................................................................6-7 Table 7-1 Switching conditions of the 1+1 HSB protection................................................................................7-4 Table 7-2 Trigger conditions of the automatic 1+1 HSB switching ....................................................................7-7 Table 7-3 Availability of the 1+1 HSB feature....................................................................................................7-8 Table 8-1 HSB switching conditions of the 1+1 FD protection...........................................................................8-6 Table 8-2 Trigger conditions of the automatic HSB switching ...........................................................................8-7 Table 8-3 Trigger conditions of the automatic HSM switching ..........................................................................8-8 Table 8-4 Availability of the 1+1 FD feature.......................................................................................................8-9 Table 9-1 HSB switching conditions of the 1+1 SD protection...........................................................................9-5 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 SD feature.......................................................................................................9-8 Table 10-1 Availability of the XPIC feature......................................................................................................10-5 Table 11-1 Switching conditions of the N+1 protection.................................................................................... 11-7 Table 11-2 Availability of the N+1 protection feature.......................................................................................11-9 Table 11-3 Description of the configuration flow of the N+1 protection mode...............................................11-15 Table 12-1 ATPC performance.......................................................................................................................... 12-2 Table 12-2 Availability of the ATPC feature.....................................................................................................12-3 Table 13-1 Radio work modes in the case of hybrid microwave frames........................................................... 13-5 Table 13-2 Availability of the Hybrid microwave feature................................................................................. 13-7 Table 14-1 Switching conditions of SNCP.........................................................................................................14-3 Table 14-2 Trigger conditions of the automatic SNCP switching (VC-4 services)...........................................14-5 Table 14-3 Trigger conditions of the automatic SNCP switching (VC-3/VC-12 services)...............................14-6 Table 14-4 Availability of the SNCP solution....................................................................................................14-6 Issue 02 (2009-02-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
Tables
OptiX RTN 600 Radio Transmission System Feature Description Table 15-1 Meaning of byte K (linear MSP)......................................................................................................15-6 Table 15-2 Bridge request code (linear MSP)....................................................................................................15-7 Table 15-3 Linear MSP switching conditions....................................................................................................15-8 Table 15-4 Availability of the linear MSP solution.........................................................................................15-10 Table 16-1 Meaning of byte K (two-fiber bidirectional ring MSP)...................................................................16-5 Table 16-2 Switching request code....................................................................................................................16-5 Table 16-3 Switching conditions of the two-fiber bidirectional ring MSP........................................................16-6 Table 16-4 Availability of the two-fiber bidirectional ring MSP.......................................................................16-8 Table 17-1 Auto-negotiation rules of FE electrical ports (when the local port adopts the auto-negotiation mode) .............................................................................................................................................................................17-3 Table 17-2 Auto-negotiation rules of GE electrical ports (when the local port adopts the auto-negotiation mode) .............................................................................................................................................................................17-4 Table 17-3 Availability of the Ethernet port feature..........................................................................................17-6 Table 17-4 Methods used by ports to process data frames...............................................................................17-17 Table 18-1 Availability of the Ethernet encapsulation and mapping feature.....................................................18-6 Table 18-2 UPI values of the client management frame....................................................................................18-9 Table 18-3 LCAS CTRL words .......................................................................................................................18-12 Table 18-4 Methods used by ports to process data frames...............................................................................18-23 Table 19-1 Data frame processing method of the switch port............................................................................19-5 Table 19-2 Availability of the VLAN................................................................................................................19-7 Table 19-3 Configuration flow of the EVPL service that uses the VLAN feature (PORT-shared EVPL service) .............................................................................................................................................................................19-9 Table 19-4 Configuration flow of the EVPL service that uses the VLAN feature (VCTRUNK-shared EVPL service) ...........................................................................................................................................................................19-10 Table 20-1 Three Types of Bridges Supported by the Ethernet Switching Board.............................................20-4 Table 20-2 Availability of Layer 2 Switching..................................................................................................20-10 Table 21-1 CoS Type..........................................................................................................................................21-5 Table 21-2 Availability of the QoS Feature.......................................................................................................21-7 Table 22-1 Line services between C-aware ports...............................................................................................22-6 Table 22-2 Line services between a C-aware port and an S-aware port............................................................22-6 Table 22-3 Line services between S-aware ports...............................................................................................22-7 Table 22-4 Characteristics of the IEEE 802.1ad bridge.....................................................................................22-8 Table 22-5 LAN services that enter and exit the IEEE 802.1ad bridge through the C-aware port....................22-9 Table 22-6 LAN services that enter and exit the IEEE 802.1ad bridge through the S-aware port...................22-10 Table 22-7 Availability of the QinQ feature....................................................................................................22-11 Table 22-8 Description of the configuration flow of the QinQ line service.....................................................22-17 Table 22-9 Description of the configuration flow of the EVPLAN service that is based on the 802.1ad bridge ...........................................................................................................................................................................22-19 Table 23-1 RMON alarms(IDU 610/620)..........................................................................................................23-6 Table 23-2 RMON alarms(IDU 605).................................................................................................................23-6 Table 23-3 RMON performance events(IDU 610/620).....................................................................................23-6 Table 23-4 RMON performance events(IDU 605)...........................................................................................23-10 Table 23-5 Availability of the RMON Feature................................................................................................23-12 Table 24-1 Availability of the ETH-OAM Feature..........................................................................................24-10
xxii
Issue 02 (2009-02-25)
Tables
Table 24-2 Mapping relation between values and OMA packet types (non-standard MP).............................24-11 Table 24-3 Mapping relation between code values and OAM packet types....................................................24-16 Table 24-4 Details of OAM configuration bytes..............................................................................................24-18 Table 24-5 Mapping relation between OAM working modes and OAM functions.........................................24-20 Table 24-6 Application scenarios for various functions of IEEE 802.3ah OAM.............................................24-25 Table 24-7 Descriptions of the IEEE 802.1ag OAM configuration flow.........................................................24-27 Table 24-8 Descriptions of the IEEE 802.3ah OAM configuration flow.........................................................24-46 Table 25-1 Trigger conditions of an LAG switching.........................................................................................25-5 Table 25-2 Availability of the LAG feature.......................................................................................................25-6 Table 25-3 Panned LAG parameters and their value..........................................................................................25-8 Table 26-1 Availability of the LPT feature........................................................................................................26-4 Table 26-2 Parameter of the Point-to-Point LPT..............................................................................................26-13 Table 26-3 Parameter of the Point-to-Multipoint LPT.....................................................................................26-14 Table 27-1 Availability of the synchronous Ethernet feature.............................................................................27-2
Issue 02 (2009-02-25)
xxiii
About This Document
About This Document
Purpose
This document describes the main features of the OptiX RTN 600 radio transmission system. It provides readers a comprehensive knowledge on the functionality, principle, configuration, and maintenance of the product features.
Related Versions
The following table lists the product versions related to this document. Product Name OptiX RTN 600 OptiX iManager T2000 Version V100R003 V200R007C03
Intended Audience
This document is intended for network planning engineers. Before you read this document, ensure that you have acquired the basic knowledge of digital microwave communication.
Organization
This document is organized as follows. Chapter 1 Introduction to the DCN 2 HW ECC Solution Content Introduces the DCN and DCN solutions. Describes the functionality, principle, configuration operations, and maintenance operations of the HW ECC solution.
1
Issue 02 (2009-02-25)
About This Document
Chapter 3 IP over DCC Solution
Content Describes the functionality, principle, configuration operations, and maintenance operations of the IP over DCC solution. Describes the functionality, principle, configuration operations, and maintenance operations of the OSI over DCC solution. Describes the functionality, principle, configuration operations, and maintenance operations of the DCC transparent transmission solution. Describes the functionality, principle, configuration operations, and maintenance operations of the DCC transparent transmission through the external clock interface solution. Describes the functionality, principle, configuration operations, and maintenance operations of the 1+1 HSB protection scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the 1+1 FD protection scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the 1+1 SD protection scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the XPIC scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the N+1 protection scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the ATPC. Describes the functionality, principle, configuration operations, and maintenance operations of the Hybrid microwave. Describes the functionality, principle, configuration operations, and maintenance operations of the SNCP scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the linear MSP scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the two-fiber bidirectional ring MSP scheme.
4 OSI over DCC Solution
5 DCC Transparent Transmission Solution 6 DCC Transparent Transmission Through the External Clock Interface Solution 7 1+1 HSB
8 1+1 FD
9 1+1 SD
10 Cross-Polarization Interference Cancellation 11 N+1 Protection
12 Automatic Transmit Power Control Function 13 Hybrid Microwave
14 Sub-Network Connection Protection 15 Linear Multiplex Section Protection 16 Two-Fiber Bidirectional Ring MSP
Issue 02 (2009-02-25)
About This Document
Chapter 17 Features of Ethernet Ports
Content Describes the functionality, principle, configuration operations, and maintenance operations of the autonegotiation function, Jumbo frames, and flow control function of the Ethernet port. Describes the functionality, principle, configuration operations, and maintenance operations of the encapsulation and mapping technology, the related virtual concatenation technology and the LCAS technology of Ethernet services. Describes the functionality, principle, configuration operations, and maintenance operations of the VLAN scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the two layer switching scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the QoS scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the QinQ scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the RMON scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the ETN ROM scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the LAG scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the LPT scheme. Describes the functionality, principle, configuration operations, and maintenance operations of the Synchronous Ethernet scheme. Lists the terms used in this document. Lists the acronyms and abbreviations used in this document.
18 Encapsulation and Mapping of Ethernet Services 19 VLAN
20 Layer 2 Switching
21 QoS 22 QinQ 23 Remote Monitoring Feature 24 ETH OAM
25 Link aggregation 26 Link State Pass Through 27 Synchronous Ethernet
28 Glossary 29 Acronyms and Abbreviations
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Issue 02 (2009-02-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3
About This Document
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, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows. 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. Examples of information displayed on the screen are in Courier New.
Update History
Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.
Updates in Issue 02 (2009-02-25)

Second release. Known defects are modified as required.
Updates in Issue 01 (2008-09-20)

Initial release.
4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-02-25)
1 Introduction to the DCN
1
About This Chapter
Introduction to the DCN
The network management system (NMS) establishes communication with a transmission network element (NE) through the data communication network (DCN) to manage and maintain the NE. 1.1 Composition of the DCN In a DCN, both the NMS and NE are nodes of the DCN. The DCN between the NMS and NEs is called the external DCN, and the DCN between NEs is called the internal DCN. 1.2 Huawei DCN Solution The OptiX transmission equipment of Huawei provides multiple DCN solutions for a variety of networks that comprise the transmission equipment.
Issue 02 (2009-02-25)
1-1
1.1 Composition of the DCN

In a DCN, both the NMS and NE are nodes of the DCN. The DCN between the NMS and NEs is called the external DCN, and the DCN between NEs is called the internal DCN. Figure 1-1 DCN
NMS
External DCN
Internal DCN
Router
LAN switch
OptiX optical transmission equipment OptiX radio transmission equipment
External DCN
In an actual network, the NMS and NEs may be located on different floors of a building, or in different buildings, or even in different cities. Hence, an external DCN that comprises the data communication equipment such as LAN switches and routers is required to connect the NMS and the NEs. As the external DCN involves knowledge of data communication, no detailed description is provided in this document. The DCN mentioned in this document refers to the internal DCN, unless otherwise specified.
1-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-02-25)
Internal DCN
In an internal DCN, an NE uses the DCC bytes of the overhead as the physical channels of the DCN.
l
When the D1 byte of the PDH microwave overhead is used, a bandwidth of 64 kbit/s can be provided for the DCN. When D1D3 bytes of the PDH microwave overhead are used, a bandwidth of 192 kbit/s can be provided for the DCN. When D1D3 bytes of the SDH regenerator section overhead (RSOH) are used, a bandwidth of 192 kbit/s can be provided for the DCN. When D4D12 bytes of the SDH multiplex section overhead (MSOH) are used, a bandwidth of 576 kbit/s can be provided for the DCN. When D1D12 bytes of the SDH section overhead are used, a bandwidth of 768 kbit/s can be provided for the DCN. When D1D3 bytes of the Hybrid microwave overhead are used, a bandwidth of 192 kbit/ s can be provided for the DCN.
NOTE
l l
In the PDH microwave frame or Hybrid microwave frame, the DCC bytes are defined by Huawei. In the SDH microwave frame, the defined DCC bytes comply with the SDH overhead specifications.
1.2 Huawei DCN Solution

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

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

When the network comprises the OptiX transmission equipment and the third-party equipment that supports the OSI over DCC function, the OSI over DCC solution is the first choice. With the OSI over DCC solution, NEs transmit the data that supports the open system interconnection (OSI) protocol through DCCs. As the OSI protocol is a standard protocol, the network management problem is solved when the network comprises the OptiX equipment and the third-party equipment. The configuration, however, is more complicated than both the HW ECC solution and the IP over DCC solution. For details on the OSI over DCC solution, see 4 OSI over DCC Solution.
DCC Transparent Transmission Solution

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

When a PDH network or a network that does not support transparent transmission of DCC bytes exists on the transmission path of NM messages, use the DCC transparent transmission through the external clock interface solution. With the DCC transparent transmission through the external clock interface solution, DCC bytes are loaded into the timeslots of the E1 provided by the external clock interface and the thirdparty equipment transmits the E1 as an ordinary E1 service. When this solution is applied, the transmission bandwidth of one E1 service is occupied. For details on the DCC transparent transmission through the external clock interface solution, see 5 DCC Transparent Transmission Solution.
Network Management Information Transmitted as Services on Auxiliary Interfaces Solution

The network management information can be transmitted as synchronous data services or asynchronous data services according to the type of the third-party network management interface. For configuration of this solution, see the chapter that describes how to configure the services and functions for auxiliary interfaces in IDU 610/620 Configuration Guide and the chapter that describes how to configure the services and functions for auxiliary interfaces in IDU 605 Configuration Guide.
1-4
Issue 02 (2009-02-25)

NOTE
l l
The IDU 610/620 supports the preceding six solutions. The IDU 605 supports only the HW ECC solution , the IP over DCC solution and Network Management Information Transmitted as Services on Auxiliary Interfaces Solution.
Issue 02 (2009-02-25)
1-5
2 HW ECC Solution
2
About This Chapter
HW ECC Solution
The NEs use unified DCCs to transmit the data of the HW ECC protocol by using the HW ECC solution. In this way, the NMS can manage NEs. The HW ECC solution applies to a network that comprises only the OptiX transmission equipment. 2.1 Feature Description This topic considers the application of the HW ECC solution (when a network comprises only the OptiX transmission equipment) as an example to describe the HW ECC solution. 2.2 Basic Concepts This topic describes the basic concepts that you should be familiar with before you use the HW ECC solution. 2.3 Availability The HW ECC solution requires the support of the applicable equipment and boards. 2.4 Relation with Other Features It is recommended that you adopt only one of the following solutions to form a DCN: HW ECC solution, IP over DCC solution, and OSI over DCC solution. 2.5 Realization Principle This topic describes how to establish ECC routes, transfer messages, and realize the extended ECC in the HW ECC solution. 2.6 Planning Guide When using the HW ECC solution, plan the parameters of an ECC network according to the situation of the network. 2.7 Configuration Guide This topic describes the configuration flow and the corresponding configuration tasks of the HW ECC solution. An example is provided as additional information to help understand the configuration. 2.8 Configuration Example This topic provides an example to describe how to configure the HW ECC solution. 2.9 Maintenance Guide
2 HW ECC Solution
This topic describes the alarms and performance events relevant to the HW ECC solution, and the problems that occur frequently during the application of the solution.
2-2
Issue 02 (2009-02-25)
2 HW ECC Solution
2.1 Feature Description

This topic considers the application of the HW ECC solution (when a network comprises only the OptiX transmission equipment) as an example to describe the HW ECC solution. When a network comprises only the OptiX transmission equipment, the equipment uses the HW ECC protocol. The HW ECC protocol realizes the transmission of ECCs through DCCs or extended ECCs. Hence, the T2000 or T2100 can manage OptiX NEs of different types in a unified manner by using the HW ECC protocol. See Figure 2-1. Figure 2-1 Networking of the HW ECC solution
T2000
OptiX optical transmission equipment OptiX radio transmission equipment Radio link Fiber Network cable
2.2 Basic Concepts

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

ITU-T G.784 defines the architecture of the ECC protocol stack based on the OSI seven layer reference model. The HW ECC protocol stack is based on the ECC protocol stack. Figure 2-2 Architecture of the HW ECC protocol stack
Application layer Presentation layer Session layer Transport layer Network layer Media access layer Physical layer HW ECC protocol stack Transport layer Network layer Data link layer Physical layer
OSI model
Physical Layer
The main function of the physical layer is to control physical channels. The physical layer performs the following functions:
l
Maintains the status of the physical channel. The physical layer maintains the status information of the DCC to which each line port corresponds. The status information includes the following:

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 the physical channels.
Provides the data communication service.
Physical channels are classified into the following two categories:

l
DCC channel DCC channels use the DCC bytes in SDH frames or PDH microwave frames as the channels for the communication among NEs. In the HW ECC solution:
2-4
Issue 02 (2009-02-25)

2 HW ECC Solution
SDH line ports generally use bytes D1 to D3 as DCC channels. When the IF1A/B board transmits 16xE1 or higher-capacity PDH microwave signals, the IF1A/B board always uses bytes D1 to D3 as DCC channels. When the IF1A/B board transmits PDH microwave signals less than 16xE1, the IF1A/ B board always uses byte D1 as the DCC channel. The microwave ports of the IF0A/B board and IDU 605 always use bytes D1 to D3 as DCC channels. When the IFH2 board transmits Hybrid microwave signals, the IFH2 board always uses bytes D1 to D3 that are defined by Huawei as DCC channels.
Extended channel Extended channels use the Ethernet as a channel for the communication among NEs. The transmission of ECCs through extended channels is called the extended ECC. For details about the extended ECC, see 2.2.2 Extended ECC.
Media Access Layer

The main function of the media access layer (MAC layer) is to activate or close physical DCCs between the physical layer and the network layer. The MAC layer performs the following functions:
l
Establishes and maintains the MAC connection between adjacent NEs. When there is a reachable physical channel between two adjacent NEs, the MAC layer establishes a MAC connection between the NEs. Each MAC connection includes the address of the opposite NE, the ID of the physical channel, the connection timer, and other information. The MAC connection has the following characteristics:
A MAC connection exists between any two adjacent NEs that can communicate through the ECC. A MAC connection is a bidirectional connection. There is only one MAC connection between any two adjacent NEs that can communicate through the ECC, even if many ports of the two NEs that support the DCC are interconnected. The physical channel of the current MAC connection is also the current ECC route. The MAC layer receives the data frame transferred from the physical layer. If the destination address is the local station, the MAC layer transfers the data frame to the network layer. Otherwise, the MAC layer discards the data frame. The MAC layer sends the data frame from the network layer. If the destination address of the data frame has a MAC connection, the MAC layer sends the data frame to the corresponding physical channel in the physical layer through the MAC connection. Otherwise, the MAC layer discards the data frame.
Network Layer
The main function of the network layer (NET layer) is to provide the route addressing function for data frames and the route management function for the DCC communication network. The NET layer performs the following functions:
l
Establishes and maintains ECC routes.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-5
Issue 02 (2009-02-25)
2 HW ECC Solution
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 layer) is to provide the end-to-end communication service for the upper layer. As the communication between the OptiX equipment and the NMS is controlled by the end-to-end connection-oriented service in the application layer, the L4 layer provides only the end-to-end connectionless communication service, that is, transparent data transfer service.
NOTE
In the HW ECC protocol stack, the NE address used by each layer is the ID of the NE. The NE ID has 24 bits. The highest eight bits represent the subnet ID (or the extended ID) and the lowest 16 bits represent the basic ID. For example, if the ID of an NE is 0x090001, the subnet ID of the NE is 9 and the basic ID is 1.
2.2.2 Extended ECC

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

T2000
Hub
Network cable
The Ethernet NM port and the NE cascading port of the OptiX RTN 600 are equivalent to two ports on a hub. Hence, you can use network cables to connect NEs in series. This type of connection is equivalent to the hub connection.
Issue 02 (2009-02-25)
2-7
2 HW ECC Solution
Figure 2-5 Networking for the extended ECC (using network cables to connect NEs in series)
T2000
Network cable
Network cable
CAUTION
l
If you use a hub to connect NEs or use network cables to connect NEs in series, there must be no network loop in the Ethernet. Otherwise, a broadcast storm occurs and the SCC board is reset repeatedly. As both the Ethernet NM port and the NE cascading port of the OptiX RTN 600 have the MDI and MDI-X adaptive capability, either a straight through cable or a crossover cable can be used as the network cable for the extended ECC. The OptiX RTN NEs can transmit network management information with the other OptiX NEs through extended ECCs.
Extension Mode
There are two extension modes for the extended ECC:
l
Automatic mode In an Ethernet, the NE with the largest IP address is automatically considered as the server and other NEs are automatically considered as clients. The NEs automatically establish TCP connections between the server and clients and also establish corresponding MAC connections according to the TCP connections. In the automatic mode, the server and clients need not be manually specified.
Specified mode In the manual mode, NEs establish TCP connections between the server and clients according to the server, clients, IDs of connecting ports, which are set manually, and other information that is entered manually. Then, the NEs establish corresponding MAC connections according to the TCP connections.
2-8
Issue 02 (2009-02-25)

NOTE
2 HW ECC Solution
l l
By default, the automatic ECC extension mode of the OptiX RTN 600 is enabled. The maximum number of the NEs that are connected in automatic ECC extension mode is 4, and the maximum number of the NEs that are connected in specified ECC extension mode is 8.
2.3 Availability
The HW ECC solution requires the support of the applicable equipment and boards. Table 2-1 Availability of the HW ECC solution Feature HW ECC solution (including the extended ECC) Applicable Board SCC (all the versions) Applicable Equipment IDU 605 IDU 610/620
2.4 Relation with Other Features

It is recommended that you adopt only one of the following solutions to form a DCN: HW ECC solution, IP over DCC solution, and OSI over DCC solution. If you combine the HW ECC solution with other solutions to form a network, note the following points:
l l
The HW ECC protocol stack of NEs can communicate with the IP protocol stack. The HW ECC protocol stack of NEs can communicate with the OSI protocol stack in the same area of the L1 layer. It is recommended that you adopt the HW ECC protocol to manage the OptiX equipment if DCC bytes are used to transparently transmit NM messages when the OptiX equipment is used together with the third-party equipment to form a network. It is recommended that you adopt the HW ECC 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 together with the third-party equipment to form a network.
2.5 Realization Principle

This topic describes how to establish ECC routes, transfer messages, and realize the extended ECC in the HW ECC solution. 2.5.1 How to Establish ECC Routes The HW ECC solution adopts the shortest path first algorithm to establish ECC routes. In this context, the shortest path refers to the path with minimum number of stations. 2.5.2 How to Transfer Messages In the HW ECC solution, the messages between NEs are transferred in the NET layer of the NEs. 2.5.3 Extended ECC
2 HW ECC Solution
The extended ECC realizes the MAC connection between adjacent NEs by using the TCP connection.
2.5.1 How to Establish ECC Routes

The HW ECC solution adopts the shortest path first algorithm to establish ECC routes. In this context, the shortest path refers to the path with minimum number of stations. The following describes how an NE establishes ECC routes: 1. 2. The physical layer of an NE maintains the status information of the DCC to which each line port corresponds. The MAC layer of the NE establishes the MAC connection between the NE and the adjacent NE. The steps are as follows: (1) The NE broadcasts the connection request frame (MAC_REQ) to the adjacent NE in a periodical manner. (2) After receiving the MAC_REQ, the adjacent NE returns the connection response frame (MAC_RSP). (3) If the MAC_RSP is received within the specified time, the NE establishes a MAC connection between the NE and the adjacent NE. 3. The NET layer of the NE establishes the NET layer routing table. The steps are as follows: (1) According to the status of the MAC connection, the NE establishes an initial NET layer routing table. (2) The NE broadcasts its routing table to the adjacent NE in a periodical manner through the routing response message. (3) The adjacent NE updates its NET layer routing table according to the received routing response message and the shortest path first algorithm. (4) At the next route broadcasting time, the NE broadcasts its current NET layer routing table to the adjacent NE. Figure 2-6 Networking example for establishing ECC routes
NE1
NE2
NE5
NE3
NE4
2-10
Issue 02 (2009-02-25)
2 HW ECC Solution
The following describes how to establish ECC routes between NEs. The network shown in Figure 2-6 is provided as an example. 1. The physical layer of each NE maintains the status information of the DCC to which each line port corresponds. The physical layer of each NE detects that there are two available DCCs. 2. The MAC layer of the NE establishes the MAC connection between the NE and the adjacent NE. NE1 is considered as an example to describe how to establish the MAC connection. (1) NE1 broadcasts the frame MAC_REQ to NE2 and NE5 in a periodical manner through its two available DCCs. The frame MAC_REQ contains the ID of NE1. (2) After receiving the frame MAC_REQ, NE2 and NE5 return their respective MAC_RSP frames. The frame MAC_RSP from NE2 contains the ID of NE2 and the frame MAC_RSP from NE5 contains the ID of NE5. (3) After receiving the MAC_RSP frames, NE1 establishes a MAC connection between NE1 and NE2 and a MAC connection between NE1 and NE5 according to the NE ID, DCC that reports the frame, and other information. 3. The NET layer of the NE establishes the NET layer routing table. NE1 is considered as an example to describe how to establish the NET layer routing table. (1) According to the status of the MAC connection, NE1 establishes an initial NET layer routing table. In the routing table, there are two routes, one to NE2 and one to NE5. (2) NE1 broadcasts its routing table to adjacent NEs in a periodical manner through the routing response message. (3) After receiving the routing response message from NE1, NE2 and NE5 update their respective NET layer routing tables. After the update, there is a route to NE5 in the NET layer routing table of NE2, and the transfer NE is NE1. There is a route to NE2 in the NET layer routing table of NE5, and the transfer NE is also NE1. Similarly, NE1 also adds the routes to NE3 and NE4 in its NET layer routing table according to the routing response messages from NE2 and NE5. There are two routes between NE1 and NE3. The distance of the route whose transfer NE is NE2 is 1 and the distance of the route whose transfer NE is NE5 is 2. Hence, according to the shortest path first principle, only the route whose transfer NE is NE2 is retained in the NET layer routing table. The routes to NE4 are processed in the same way as those to NE3. (4) If the DCC between NE1 and NE2 becomes faulty, the MAC connection between NE1 and NE2 fails. In this case, NE1 updates the routes to NE2 and NE3 in its NET layer routing table according to the routing response message from NE5. Hence, the routes to NE2 and NE3 are re-established. In this way, the ECC route is protected.
2.5.2 How to Transfer Messages

In the HW ECC solution, the messages between NEs are transferred in the NET layer of the NEs. Figure 2-7 illustrates how the HW ECC solution transfers the messages originating from the T2000 to a destination NE.
Issue 02 (2009-02-25)
2-11
2 HW ECC Solution
Figure 2-7 Realization principle of message transferring (HW ECC)

Application TCP IP Application TCP IP L4 NET MAC Ethernet Ethernet DCC T2000 Gateway NE DCC Transfer NE DCC Destination NE NET MAC Application L4 NET MAC
The realization principle is as follows: 1. 2. 3. The T2000 transfers application layer messages to the gateway NE through the TCP connection between them. The gateway NE extracts the messages from the TCP/IP protocol stack and reports the messages to the application layer. The application layer of the gateway NE queries the address of the destination NE in the messages. If the address of the destination NE is not the same as the address of the local station, the gateway NE queries the core routing table of the application layer according to the address of the destination NE to obtain the corresponding route and the communication protocol stack of the transfer NE. As the communication protocol stack of the transfer NE in Figure 2-7 is HW ECC, the gateway NE transfers the messages to the transfer NE through the HW ECC stack. After receiving the packet that encapsulates the messages, the NET layer of the transfer NE queries the address of the destination NE of the packet. If the address of the destination NE is not the same as the address of the local station, the transfer NE queries the NET layer routing table according to the address of the destination NE to obtain the corresponding route and then transfers the packet. After receiving the packet, the NET layer of the destination NE reports the packet to the application layer through the L4 layer because the address of the destination NE of the packet is the same as the address of the local station. The application layer functions according to the message sent from the T2000.
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 MAC connection between adjacent NEs by using the TCP connection.
2 HW ECC Solution
Automatic Mode
The realization principle is as follows: 1. 2. 3. 4. 5. Each NE obtains the IP addresses of other NEs that are in the same Ethernet through the address resolution protocol (ARP). The NE with the largest IP address automatically functions as the server and detects the TCP requests from the clients. Other NEs automatically function as clients and send TCP connection requests to the server. After receiving the TCP connection request from a client, the server establishes the corresponding TCP connection. The NEs use the TCP connection as a MAC connection to realize ECC communication.
Specified Mode
The realization principle of the specified mode is basically the same as the realization principle of the automatic mode. The difference is that in the specified mode, the server, clients, and IDs of connecting ports are manually specified.
2.6 Planning Guide

When using the HW ECC solution, plan the parameters of an ECC network according to the situation of the network.
Prerequisite
You must understand the application of the equipment in the network and the engineering requirements of the project.
Procedure
Step 1 Select a proper NE as the gateway NE according to the situation of the network. Adhere to the following principles when planning a gateway NE:
l
Select the NE that is the closest to the NMS, the central node of star services, or the NE that accesses the maximum number of DCCs, as the gateway NE if possible. Set two gateway NEs, one active and one standby, for an ECC subnet if possible.
NOTE
An ECC subnet is an ECC network that comprises a gateway NE and non-gateway NEs that communicate with the T2000 through the gateway NE. An ECC network can consist of one or more ECC subnets.
Step 2 Plan the external DCN according to the position of the gateway NE and the T2000. Adhere to the following principles when planning an external DCN:
l
The bandwidth of the external DCN must not be lower than the DCC bandwidth that the network uses. The link at 256 kbit/s already meets the requirements. It is recommended that you do not use the office LAN or Internet as the transmission channel of the external DCN for stability purposes and security reasons.
Issue 02 (2009-02-25)
2 HW ECC Solution
l
It is recommended that you use the 2 Mbit/s channel to transport the external DCN. The Quidway 2501 or other equivalent router is recommended. The channel for the external DCN should be provided by other network (not the monitored network). If the external DCN uses the channel provided by the data processing board, consider the risk when the external DCN uses the service channel provided by the monitored network. Provide active and standby DCN routes or gateways for the external DCN if possible.
Step 3 Plan the IDs of NEs. Adhere to the following principles when planning NE IDs:
l l
The IDs of the NEs in a DCN should not be repeated. When the number of existing NEs does not exceed the range represented by the basic ID, do not use the extended ID if possible. In the case of a newly-built network, it is recommended that you adhere to the following rules to allocate NE IDs.
In the case of a ring network, it is recommended that you allocate NE IDs in turn, in the direction of the primary ring (counterclockwise). In the case of a chain/tree network, it is recommended that you allocate NE IDs in turn from the core to the edges.
Allocate unused IDs for the NEs that are added on an existing network.
Step 4 Plan the IP addresses of NEs. Adhere to the following principles when planning the IP addresses of NEs:
l
The IP address, subnet mask, and default gateway of the gateway NE must meet the planning requirements of the external DCN. Ensure that the IP addresses of the NEs that use the extended ECC are in the same network segment. Except the gateway NE, set the IP addresses of NEs according to the NE IDs.
NOTE
l l
When you set the IP address of an NE according to the ID of the NE, set the IP address to 0x81000000+ID. For example, if the NE ID is 0x090001, set the IP address to 129.9.0.1. By default, the subnet mask is 255.255.0.0.
Step 5 Optional: If the extended ECC needs to be used, plan the information of the extended ECC. Adhere to the following principles when planning the extended ECC:
l
Ensure that the IP addresses of the NEs that use the extended ECC are in the same network segment. If you use a hub to connect NEs or network cables to connect NEs in series to form a network through the extended ECC, ensure that there is no network loop in the Ethernet. If you use a hub to connect NEs to form a network through the extended ECC, do not connect any other equipment to the hub. The number of clients to be accessed through the extended ECC should not exceed 4. It is recommended that you use the specified mode to extend the ECC. Do not use the automatic mode.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-02-25)
l l
2-14

l
2 HW ECC Solution
When several gateway NEs are connected to the T2000 through a hub, do not use the automatic ECC extension function of the gateway NEs. When you use the specified mode to extend the ECC, it is recommended that you specify the NE near the T2000 as the server of the TCP connection and specify other NEs as clients. Set the port ID to any number between 1601 and 1699.
Step 6 Optional: Plan the ECC network division solution. Adhere to the following principles when planning the ECC network division solution:
l
It is recommended that the number of NEs in an ECC subnet does not exceed 50. The number of NEs in an ECC subnet must not exceed 100. When the number of NEs in an ECC network exceeds 50, it is recommended that you add gateway NEs to divide the network into several ECC subnets. The DCCs between ECC subnets must be disabled. When dividing an ECC network, you must plan the corresponding external DCNs. The division of an ECC network should not affect the existing ECC route restoration (protection) capability.
l l l
----End
Example
Figure 2-8 Networking example for the HW ECC solution
NE203 NE204 NE206 NE205
NE201 NE202
NE101 NE102 NE104 NE106 OptiX optical transmission equipment OptiX radio transmission equipment Quidway 2501 Radio link Network cable Hub Fiber
NE103
T2000
2 Mbit/s channel
Issue 02 (2009-02-25)
2-15
2 HW ECC Solution
Figure 2-8 shows a transmission network that comprises only the OptiX equipment. The steps to plan the DCN are as follows: 1. As there are more than 40 sets of optical transmission equipment and also more than 40 sets of radio transmission equipment, divide the ECC network to two ECC subnets according to the type of equipment. Select the central node of the optical transmission service NE101 and the central node of the radio transmission service NE202 as the gateway NE. As the T2000 and NE202 are located in different sites, use a router Quidway 2501 to build the external DCN between them. Allocate IDs and IP addresses for all the NEs according to the situation of the network. Figure 2-9 Allocation of IDs and IP addresses for all NEs
9-205 129.9.0.205 0.0.0.0
2. 3. 4.
9-203 129.9.0.203 0.0.0.0 11.0.0.1/16
9-204 129.9.0.204 0.0.0.0
9-202 11.0.0.202 11.0.0.1
9-206 129.9.0.206 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-106 129.9.0.106 0.0.0.0
Extended ID-Basic ID IP address Gateway
5.
Plan the extended ECC. As there is no DCC between NE204 and NE205 and also between NE204 and NE206, use network cables to connect the Ethernet NE port and the NE cascading port to extend the ECC. Use the manual mode to extend the ECC. Set the parameters as follows:
l l l
server: 129.9.0.204 client: 129.9.0.205, 129.9.0.206 port: 1601
6.
Divide the ECC network. Set the DCCs of both the east and west line ports on the ring of NE201 to "disable". Set the bytes D1 to D3 on the ring to pass through NE201 to ensure that the protection of the ECC routes on the ring is not affected.
2-16
Issue 02 (2009-02-25)
2 HW ECC Solution
2.7 Configuration Guide

This topic describes the configuration flow and the corresponding configuration tasks of the HW ECC solution. An example is provided as additional information to help understand the configuration. 2.7.1 Configuration Flow The configuration of the HW ECC solution consists of two parts, that is, the configuration at the near end of the NE by using the Web LCT and the creation of the NE topology on the T2000. 2.7.2 Modifying the NE ID Modify the NE ID according to the engineering plan to ensure that each NE ID is unique. The modification does not affect services. 2.7.3 Modifying the Communication Parameters of an NE The communication parameters of an NE include the IP address of the NE, the extended ID, the gateway IP, the subnet mask, and the NSAP address. 2.7.4 Configuring DCCs To meet the NM requirements of a complicated network, it is necessary to set the channel type, enable/disable status, and protocol type of the DCC according to the network planning. 2.7.5 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 SCC boards of the NEs to realize communication through the extended ECC. 2.7.6 Configuring DCC Transparent Transmission The OptiX equipment supports the DCC transparent transmission function. With this function, the equipment can transparently transmit NM messages when the OptiX equipment is used together with other equipment to form a network and can also transparently transmit the management messages between ECC subnets. 2.7.7 Querying ECC Routes By querying ECC routes, you can verify whether the ECC configuration is correct and whether the DCC communication is normal. 2.7.8 Creating NEs by Using the Search Method The T2000 can search 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 address. In addition, the T2000 can create the NEs that are found in batches. Compared with the method of manually creating NEs, this method is faster and more reliable. 2.7.9 Creating NEs by Using the Manual Method You can only create NEs one by one through the manual method. The manual method, unlike the search method, does not allow creating NEs in batches.
2.7.1 Configuration Flow

The configuration of the HW ECC solution consists of two parts, that is, the configuration at the near end of the NE by using the Web LCT and the creation of the NE topology on the T2000.
Issue 02 (2009-02-25)
2-17
2 HW ECC Solution
Figure 2-10 Configuration flow for the HW ECC solution

Start
Modify IDs and IP addresses for NEs
2 Configure DCCs for NEs
Extended ECC required?
No
Yes Configure extended ECCs
DCC transparent transmission required? Yes 4 Configure DCC transparent transmission
No
5 Query ECC routes at the gateway NE 6 Create NEs on the T2000
End
2-18
Issue 02 (2009-02-25)
2 HW ECC Solution
Table 2-2 Description of the configuration flow of the HW ECC solution Number 1 Description
l
When setting the IP address information for the gateway NE, you may need to set the default gateway, in addition to setting the IP address and subnet mask, depending on the situation of the external DCN. For information on modifying the ID of an NE, see 2.7.2 Modifying the NE ID. For information on modifying the IP address information of an NE, see 2.7.3 Modifying the Communication Parameters of an NE. The Protocol Type of the line port should be set to HW ECC (default value). The Channel Type of the SDH port should be set to D1-D3 (default value). The DCC type of the PDH microwave port or Hybrid microwave port is not required to adjust the DCC type manually. When dividing an ECC network, set the enable status of the DCC between ECC subnets to Disable. For the configuration process, see 2.7.4 Configuring DCCs. Set the ECC extended mode to Specified mode. In the case of the NE that is selected as the server, set the Port at the server side. In the case of the NEs that are planned as clients, set the Opposite IP and Port at the client side. The Opposite IP should be set to the IP address of the server. The Port should be set to the one that is set at the server side. For the configuration process, see 2.7.5 Configuring the Extended ECC. The IDU 605 does not support DCC transparent transmission. For the configuration process, see 2.7.6 Configuring DCC Transparent Transmission. An ECC route exists between the gateway NE and each of its managed non-gateway NEs. No ECC route exists between the gateway NE and each of the other NEs in ECC subnets. ECC routes follow the shortest path first principle. For the querying process, see 2.7.7 Querying ECC Routes.
l l
l l
l l
l l
There are two methods to create an NE on the T2000.

l
Create NEs in batches by using the search method. For the configuration process, see 2.7.8 Creating NEs by Using the Search Method.
Create NEs one by one by using the manual method. For the configuration process, see 2.7.9 Creating NEs by Using the Manual Method.
Issue 02 (2009-02-25)
2-19
2 HW ECC Solution
2.7.2 Modifying the NE ID

Modify the NE ID according to the engineering plan to ensure that each NE ID is unique. The modification does not affect services.
Prerequisite
The user must log in to the NE. You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > NE Attribute from the Function Tree. Step 2 Click Modify NE ID. The system displays the Modify NE ID dialog box. Step 3 Set a new ID for the NE.
Step 4 Click OK. A dialog box is displayed and click OK. ----End
Parameters
Parameter New ID Value Range 1 to 49135 Default Value Description
l
The new ID refers to the basic ID. When the extended ID is not used, the basic ID of an NE within any network that is managed by an NMS must be unique. Set this parameter according to the planning of the DCN. When the number of existing NEs does not exceed the range represented by the basic ID, do not modify the extended ID. It is recommended that you use the default value.
New Extended ID
1 to 254
2-20
Issue 02 (2009-02-25)

NOTE
2 HW ECC Solution
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.
Postrequisite
After you change the ID of an IDU 605 1A/1B/2B NE, you need to delete the NE, and then recreate and re-log in to the NE. Otherwise, the communication between the NMS and the NE cannot be recovered. After you change the ID of an IDU 605 1F/2F NE, you only need to re-log in to the NE, thus recovering the communication between the NMS and the NE. After you change the ID of an IDU 610/620 NE, you only need to re-log in to the NE, thus recovering the communication between the NMS and the NE.
2.7.3 Modifying the Communication Parameters of an NE

The communication parameters of an NE include the IP address of the NE, the extended ID, the gateway IP, the subnet mask, and the NSAP address.
Prerequisite
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > Communication Parameters from the Function Tree. Step 2 Set the communication parameters of the NE.
Issue 02 (2009-02-25)
2-21
2 HW ECC Solution
Step 3 Click Apply. ----End
Parameters
Parameter IP Value Range Default Value Before an NE is delivered from the factory, the IP address of the NE is set to 129.9.0.x, where x represents the preset basic ID of the NE. 0.0.0.0 255.255.0.0 Description In the case of the HW ECC solution, adhere to the following principles when setting the IP address: l The IP address, subnet mask, and default gateway of the gateway NE must meet the planning requirements of the external DCN. l Ensure that the IP addresses of the NEs that use the extended ECC are in the same network segment. l Set the IP addresses of the NEs except the gateway NE according to the NE IDs. That is, set the IP address of such an NE to 0x81000000+ID. For example, if the NE ID is 0x090001, set the IP address to 129.9.0.1.
Gateway IP Subnet Mask
2-22
Issue 02 (2009-02-25)
2 HW ECC Solution
Parameter Extended ID
Value Range 1 to 254
Default Value 9
Description
l
When the number of existing NEs does not exceed the range represented by the basic ID, do not modify the extended ID. It is recommended that you use the default value.
NSAP Address
This parameter is valid only when the OSI over DCC solution is applied. This parameter is used to set only the area ID of an NSAP address. The other parts of the NSAP address are automatically generated by the NE.
2.7.4 Configuring DCCs

To meet the NM requirements of a complicated network, it is necessary to set the channel type, enable/disable status, and protocol type of the DCC according to the network planning.
Prerequisite
Precautions
The IDU 610/620 can simultaneously support twelve channels comprising byte D1, twelve channels comprising bytes D1 to D3, six channels comprising bytes D4 to D12, and two channels comprising bytes D1 to D12. If the DCC communication configuration already exceeds the restriction, close or adjust the DCCs of certain ports, depending on the actual situation. The IDU 605 supports only one channel that comprises bytes D1 to D3.
Procedure
Step 1 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. Step 2 Optional: Modify the channel type or protocol type of an existing DCC. 1. 2. 3. Select the DCC to be modified and click Delete. Click Create. The system displays the Create dialog box. Set the DCC.
Issue 02 (2009-02-25)
2-23
2 HW ECC Solution
4. 1. 2.
Click OK. Double-click the cell in the Enable Status column to which the DCC corresponds. Set the required state in the drop-down box. Click Apply.
Step 3 Optional: Modify the enable status of a DCC.
----End
Parameters
Parameter Port Enabled/Disabled Value Range Line ports, external clock interface Enabled, Disabled Default Value Enabled (in the case of line ports) Disabled (in the case of the external clock interface) Description The IDU 605 does not support the external clock interface. It is recommended that you use the default value except in the following cases:
l
Set Enabled/Disabled of the port that is connected to another ECC subnet to Disabled. Set Enabled/Disabled of the port that is connected to a third-party network but does not transmit NM messages to Disabled. When the DCC transparent transmission through the external clock interface solution is applied, set Enabled/ Disabled of the used external clock interface to Enabled.
2-24
Issue 02 (2009-02-25)
2 HW ECC Solution
Parameter Channel Type
Value Range D1-D1, D1-D3, D4D12, D1-D12
Default Value D1-D1 (when the IF1A/B board transmits PDH microwave signals of a capacity less than 16xE1) D1-D3 (in other cases)
Description It is recommended that you use the default value except in the following cases:
l
When the IP over DCC solution or OSI over DCC solution is applied, set Channel Type of the SDH line ports to the same value as the channel type of third-party network. When the DCC transparent transmission solution is applied, the channel type of the SDH line ports must not conflict with the channel type of the third-party network.
Protocol Type
HW ECC, TCP/IP, OSI
HW ECC
It is recommended that you use the default value except in the following cases:
l
When the IP over DCC solution is applied, set Protocol Type to TCP/IP. When the OSI over DCC solution is applied, set Protocol Type to OSI. This parameter is valid only when Protocol Type is set to OSI. Set LAPD Role to User at one end of a DCC and to Network at the other end of the DCC.
LAPD Role
User, Network
User
2.7.5 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 SCC boards of the NEs to realize communication through the extended ECC.
Prerequisite
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > ECC Management from the Function Tree. Step 2 Set the ECC Extended Mode. Step 3 Optional: Set other parameters when the ECC extended mode is set to the specified mode.
Issue 02 (2009-02-25)
2-25
2 HW ECC Solution
Step 4 Click Apply. The system displays the prompt "This operation will reset communication between NEs. Are you sure to continue?" Step 5 Click OK. ----End
Parameters
Parameter ECC Extended Mode Port (on the server side) Value Range Auto mode, Specified mode 1601 to 1699 Default Value Specified mode 1601 Description It is recommended that you use the default value.
l
This parameter is valid only when ECC Extended Mode is set to Specified mode. Set this parameter only when the NE functions as the server of the extended ECC. Generally, select the NE that is the nearest to the T2000 as the server. Set this parameter to a value, which ranges from 1601 to 1699. This parameter is valid only when ECC Extended Mode is set to Specified mode. Set this parameter only when the NE functions as a client of the extended ECC. All the NEs that use the extended ECC, except the NE that functions as the server, function as clients. Set Opposite IP and Port to the IP address and port number of the server NE respectively.
Opposite IP (on the client side) Port (on the client side)
1601 to 1699
1601
2-26
Issue 02 (2009-02-25)
2 HW ECC Solution
2.7.6 Configuring DCC Transparent Transmission

The OptiX equipment supports the DCC transparent transmission function. With this function, the equipment can transparently transmit NM messages when the OptiX equipment is used together with other equipment to form a network and can also transparently transmit the management messages between ECC subnets.
Prerequisite
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. The system displays the Create DCC Transparent Transmission Byte dialog box. Step 4 Set the parameters of the DCC transparent transmission byte.
Step 5 Click OK. ----End
Parameters
Parameter Source Timeslot/ Porta Value Range Line ports Default Value Description -
Issue 02 (2009-02-25)
2-27
2 HW ECC Solution
Parameter Transparent Transmission of Overhead Byte at Source Port
Value Range D1, D2, D3, D4, D5, D6, D7, D8, D9, D10, D11, D12, E1, E2, F1, X1, X2, X3, X4b
Default Value D1
Description
l
Only one overhead byte can be selected at a time. X1, X2, X3, and X4 represent the selfdefined overhead bytes that are used when asynchronous data services are transmitted. The overhead byte must not be a used byte (for example, the byte used by a DCC that is in use).
Sink Timeslot/Porta Transparent Transmission of Overhead Byte at Sink Port
Line ports D1, D2, D3, D4, D5, D6, D7, D8, D9, D10, D11, D12, E1, E2, F1, X1, X2, X3, X4b
D1
Only one overhead byte can be selected at a time. The overhead byte must not be a used byte (for example, the byte used by a DCC that is in use). Generally, Transparent Transmission of Overhead Byte at Sink Port is set to the same value as Transparent Transmission of Overhead Byte at Source Port. These two parameters, however, can be set to different values.
NOTE
l l
a: The system establishes a bidirectional cross-connection between the overhead byte at the source port and the overhead byte at the sink port. Hence, you can set a port to be a source port or a sink port. b: When an IF port works in the PDH mode, the number of overhead bytes that can be used is less than the number of overhead bytes that are listed.
2.7.7 Querying ECC Routes

By querying ECC routes, you can verify whether the ECC configuration is correct and whether the DCC communication is normal.
Prerequisite
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC Link Management from the Function Tree. Step 2 Check whether the ECC routes and their parameters in NE ECC Link Management List are in accordance with the planning information. ----End
2 HW ECC Solution
2.7.8 Creating NEs by Using the Search Method

The T2000 can search 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 address. In addition, the T2000 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 l
The user must log in to the T2000. The user must have the "NE and network operator" authority or higher. The NE to be created must have normal communication with the T2000.
Procedure
Step 1 Choose File > Search for NE from the Main Menu. Step 2 Optional: Add a search domain. 1. 2. Click Add. The system displays the Input Search Domain dialog box. Select an address type and enter the search address.
3.
Click OK.
Step 3 Optional: Repeat Step 2 to add several search domains. Step 4 Click Start. After the search ends, the NE Found list displays all the NEs that are found. Step 5 Create NEs. 1. 2. 3. 4. 5. Select an NE that is not created from the NE Found list. Optional: Select the corresponding Gateway of the NE. Click Create NE. The system displays the Create NE dialog box. Specify User Name and Password. Click OK. The icon of the created NE is displayed in the Main Topology.
2 HW ECC Solution
Step 6 Optional: Repeat Step 5 to create other NEs that are not created. ----End
Parameters
Parameter Address type (in the Input Search Domain dialog box) Value Range IP Address of GNE, NSAP Address, IP Address Range of GNE Default Value IP Address Range of GNE Description
l
When the OSI over DCC solution is applied, select NSAP Address. If the IP address of the gateway NE is known, select IP Address of GNE. If the IP address of the gateway NE is unknown and only the IP address range of the gateway NE is known, select IP Address Range of GNE. When Address type is set to NSAP Address, set the search address to the NSAP address of the gateway NE. When Address type is set to IP Address of GNE, set the search address to the IP address of the gateway NE. When Address type is set to IP Address Range of GNE, set the search address to the broadcast address of the network segment to which the gateway NE belongs.
Search address (in the Input Search Domain dialog box)
129.9.255.255 (when Address type is set to IP Address Range of GNE) (in the case of other situations)
User name (in the Input Search Domain dialog box) Password (in the Input Search Domain dialog box) GNE ID
root
This parameter specifies the user name of the gateway NE. It is recommended that you use the default value. The default password of user root is password.
l
password
This parameter specifies the identifier of the gateway to which the NE to be created belongs. The identifier is represented by "NE" + "Extended ID" + "-" + "Basic ID". If you set GNE ID to the ID of the NE to be created, the NE to be created is created as a gateway NE. When the NE to be created can belong to several gateway NEs, exercise caution when selecting a gateway NE according to the planning information for the ECC network.
2-30
Issue 02 (2009-02-25)
2 HW ECC Solution
Parameter All NEs use the same User and Password (in the Create NE dialog box) User Name (in the Create NE dialog box) Password (in the Create NE dialog box)
Value Range Selected, Not selected
Default Value Selected
Description When All NEs use the same User and Password is selected, you can use User Name and Password to log in to all the NEs.
You can use root as the user name at the first login. The default password of user root is password.
NOTE
l l
When Address type is set to NSAP Address, ensure that the T2000 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 T2000 server and gateway NE are not in the same network segment, ensure that the IP routes of the network segments to which the T2000 server and gateway NE belong are configured on the T2000 and related routers.
2.7.9 Creating NEs by Using the Manual Method

You can only create NEs one by one through the manual method. The manual method, unlike the search method, does not allow creating NEs in batches.
Prerequisite
l l l l
The user must log in to the T2000. The user must have the "NE and network operator" authority or higher. The NE to be created must have normal communication with the T2000. 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 Right-click in the blank space of the Main Topology and choose Create > Topology Object. The system displays the Create Topology Object dialog box. Step 2 Select the NE type from the Object Type tree. Step 3 Complete the following information: ID, Extended ID, Name, and Remarks. Step 4 Set the Gateway Type parameter for the NE. If ... The Gateway Type parameter is set to Gateway
Issue 02 (2009-02-25)
Then ... Proceed to the next step.
2-31
2 HW ECC Solution
If ...
Then ...
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.
Step 6 Specify NE User and Password. Step 7 Click OK. Step 8 Click the Main Topology. The icon of the NE is displayed at the cursor position. ----End
2-32
Issue 02 (2009-02-25)
2 HW ECC Solution
Parameters
Parameter ID Value Range 1 to 49135 Default Value Description This parameter specifies the basic ID of the NE to be created. The NE ID that consists of the basic ID and extended ID is the identifier of the NE on the T2000. This parameter specifies the extended ID of the NE to be created. Generally, the extended ID is set to 9. The Name of each NE must be unique. It is recommended that you set Name to a character string that includes the location of the NE, the ID of the NE, or other information.
l
Extended ID
1 to 254
Name
Gateway Type
Gateway, NonGateway
Non-Gateway
If the NE to be created is a gateway NE, set Gateway Type to Gateway. If the NE to be created is a non-gateway NE, set Gateway Type to NonGateway. If the NE to be created can function as a gateway NE or a non-gateway NE, set Gateway Type according to the planning information for the DCN.
Affiliated Gateway
When Gateway Type is set to NonGateway, set the gateway NE to which the NE to be created belongs.
l
Protocol
IP, OSI
IP
When Gateway Type is set to Gateway, you need to set this parameter. When the OSI over DCC solution is applied, set this parameter to OSI. In the case of other situations, set this parameter to IP.
IP Address
This parameter specifies the IP address of the NE to be created. When Protocol is set to IP, you need to set this parameter. This parameter specifies the NSAP address of the NE to be created. When Protocol is set to OSI, you need to set this parameter. You only need to set the area ID, and the other parts are automatically generated by the NE.
NSAP Address
Issue 02 (2009-02-25)
2-33
2 HW ECC Solution
NOTE
l l
When Protocol is set to OSI, ensure that the T2000 is installed with the OSI protocol stack software. When Protocol is set to IP, and the T2000 server and gateway NE are not in the same network segment, ensure that the IP routes of the network segments to which the T2000 server and gateway NE belong are configured on the T2000 and related routers.
2.8 Configuration Example

This topic provides an example to describe how to configure the HW ECC solution.
Precautions
NOTE
l l
For the parameters in this example, refer to the example in 2.6 Planning Guide. This example provides only the configurations of the typical NEs: NE101, NE201, NE202, NE204, and NE205.
Procedure
Step 1 Set IDs for the NEs. See 2.7.2 Modifying the NE ID.
l l l l l
The extended ID of NE101 is 9 and the ID is 101. The extended ID of NE201 is 9 and the ID is 201. The extended ID of NE202 is 9 and the ID is 202. The extended ID of NE204 is 9 and the ID is 204. The extended ID of NE205 is 9 and the ID is 205.
Step 2 Set the IP address information for the NEs. See 2.7.3 Modifying the Communication Parameters of an NE.
l
The IP address of NE101 is 10.0.0.101, the subnet mask is 255.255.0.0, and the default gateway is 0.0.0.0 (default value). The IP address of NE201 is 129.9.0.201, the subnet mask is 255.255.0.0, and the default gateway is 0.0.0.0 (default value). The IP address of NE202 is 11.0.0.202, the subnet mask is 255.255.0.0, and the default gateway is 11.0.0.1. The IP address of NE204 is 129.9.0.204, the subnet mask is 255.255.0.0, and the default gateway is 0.0.0.0 (default value). The IP address of NE205 is 129.9.0.205, the subnet mask is 255.255.0.0, and the default gateway is 0.0.0.0 (default value). Set the Protocol Type of all the line ports of all NEs to HW ECC (default value). Set the Channel Type of all SDH ports of all NEs to D1-D3 (default value). Set Channel Type of all PDH microwave ports of all NEs to the default value. Set Enable Status of the DCCs of both the east and west line ports on the ring of NE201 to Disable.
Step 3 Set DCCs for the NEs. See 2.7.4 Configuring DCCs.
l l l l
Step 4 Set the extended ECC parameters of NE204 and NE205. See 2.7.5 Configuring the Extended ECC.

l l l
2 HW ECC Solution
Set ECC Extended Mode of both NE204 and NE205 to Specified mode. In the case of NE204, set Port in the Set Server field to 1601. In the case of NE205, set Opposite IP to 129.9.0.204 and Port to 1601 in the Set Client field.
Step 5 Configure the transparent transmission between bytes D1 to D3 of the west line port of NE201 and bytes D1 to D3 of the east line port of NE201. See 2.7.6 Configuring DCC Transparent Transmission. Step 6 Query the ECC routes of NE101 and NE202. See 2.7.7 Querying ECC Routes.
l l l l
At NE101, there is no route to NE201, NE202, NE204, and NE205. At NE202, there is a route to NE201 and the transfer NE is NE201. At NE202, there is a route to NE204 and the transfer NE is NE204. At NE202, there is a route to NE205 and the transfer NE is NE204.
Step 7 Use the search method to create NEs on the T2000. See 2.7.8 Creating NEs by Using the Search Method. The search domains are as follows:
l l
The search domain with the gateway NE whose IP address is 10.0.0.101 The search domain with the gateway NE whose IP address is 11.0.0.201
NOTE
As 11.0.0.201 and the IP address of the T2000 are not in the same network segment, configure static routes on both the T2000 and the corresponding router to ensure that the TCP/IP communication between them is normal.
All NEs can be successfully created. ----End
2.9 Maintenance Guide

This topic describes the alarms and performance events relevant to the HW ECC solution, and the problems that occur frequently during the application of the solution. 2.9.1 Relevant Alarms and Events When there is a fault in the communication between the T2000 and an NE, the T2000 reports the corresponding alarm. 2.9.2 FAQs This topic lists the problems that occur frequently during the application of the HW ECC solution.
2.9.1 Relevant Alarms and Events

When there is a fault in the communication between the T2000 and an NE, the T2000 reports the corresponding alarm.
Relevant Alarms
l
GNE_CONNECT_FAIL
Issue 02 (2009-02-25)
2 HW ECC Solution
The GNE_CONNECT_FAIL alarm indicates that the connection between the T2000 and the gateway NE fails. When the connection between the T2000 and the gateway NE fails, the T2000 reports this alarm.
l
NE_COMMU_BREAK The NE_COMMU_BREAK alarm indicates that the communication with the NE is interrupted. When the communication between the T2000 and the NE is interrupted, the T2000 reports this alarm.
NE_NOT_LOGIN The NE_NOT_LOGIN alarm indicates that the login to the NE fails. When the T2000 cannot log in to the NE, the T2000 reports this alarm.
Relevant Events
None.
2.9.2 FAQs
This topic lists the problems that occur frequently during the application of the HW ECC solution. Q: Why does the T2000 always fail to log in to an NE? A: Common causes are as follows:
l
The communication connection between the T2000 and the gateway NE is faulty. To locate the fault, run the ping or tracert command on the T2000 server. The ECC route between the gateway NE and a non-gateway NE is faulty. To locate the fault, check the ECC route between the gateway NE and the non-gateway NE.
l l
NE IDs conflict. When the T2000 connects several gateway NEs by using a hub, the gateway NEs start the automatic ECC extension function.
Q: Why does the T2000 frequently fail to log in to NEs? A: Common causes are as follows:
l
The T2000 is faulty. If this is the case, the T2000 fails to log in to all NEs. The IP addresses of gateway NEs conflict. If this is the case, the T2000 fails to log in to all the NEs of an ECC subnet. An ECC subnet is of a large scale. If this is the case, the T2000 fails to log in to the NEs that access several DCCs.
Q: Why does the SCC board of the gateway NE or of the NE that uses the extended ECC frequently reset? A: Common causes are as follows:

l
2 HW ECC Solution
The LAN to which the NE is connected accesses unknown equipment, resulting in a conflict between the NE and the equipment. There is a loop in the LAN to which the NE is connected (especially when there is a loop between the Ethernet NM port and the NE cascading port), resulting in a network storm.
Q: What are the problems encountered when performing operations on an ECC subnet of a large scale? A: Main hazards are as follows:
l l l l l
The ECC route has poor stability or a long convergence time, or even oscillates. The remote loading speed is slow. The alarm reported to the T2000 is lost. The T2000 cannot log in to a certain NE. The SCC board of a certain NE resets abnormally.
Issue 02 (2009-02-25)
2-37
3 IP over DCC Solution
3
About This Chapter
IP over DCC Solution
The NEs use unified DCCs to transmit the data of the TCP/IP protocol by using the IP over DCC solution. In this way, the NMS can manage NEs. The IP over DCC solution applies to a network that comprises the OptiX transmission equipment and the third-party equipment that supports the IP over DCC function. This solution can also be applied to a network that comprises only the OptiX transmission equipment. 3.1 Feature Description This topic considers the application of the IP over DCC solution (when a network comprises the OptiX transmission equipment and the third-party equipment that supports the IP over DCC function) as an example to describe the IP over DCC solution. 3.2 Basic Concepts This topic describes the basic concepts that you should be familiar with before you use the IP over DCC solution. 3.3 Availability The IP over DCC solution requires the support of the applicable equipment and boards. 3.4 Relation with Other Features It is recommended that you adopt only one of the following solutions to form a DCN: HW ECC solution, IP over DCC solution, and OSI over DCC solution. 3.5 Realization Principle This topic describes how an NE transfers messages depending on the mode in which the T2000 accesses an NE. The realization principles in different modes vary slightly from each other. 3.6 Planning Guide When using the IP over DCC solution, plan the parameters of a DCN depending on the situation of the network. 3.7 Configuration Guide This topic describes the configuration flow and the corresponding configuration tasks of the IP over DCC solution. An example is provided as additional information to help understand the configuration. 3.8 Configuration Example This topic provides an example to describe how to configure the IP over DCC solution.
3.9 Maintenance Guide This topic describes the alarms and performance events relevant to the IP over DCC solution, and the problems that occur frequently during the application of the solution.
3-2
Issue 02 (2009-02-25)

This topic considers the application of the IP over DCC solution (when a network comprises the OptiX transmission equipment and the third-party equipment that supports the IP over DCC function) as an example to describe the IP over DCC solution. If the third-party equipment supports the IP over DCC function, the third-party equipment can communicate with the NMS through DCCs of the OptiX transmission equipment. See Figure 3-1 Figure 3-1 Application of the IP over DCC solution
T2000 Third-party NMS
Third-party transmission equipment OptiX transmission equipment Fiber Network cable
3.2 Basic Concepts

This topic describes the basic concepts that you should 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 Access Modes In the IP over DCC solution, there are two modes for the T2000 to access an NE, namely, gateway mode and direct connection mode.
3.2.1 IP over DCC Protocol Stack

The IP over DCC adopts the architecture of the standard TCP/IP protocol stack.
Figure 3-2 Architecture of the IP over DCC protocol stack

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 channels for data transmission for the data end equipment. Physical channels are classified into the following two categories:
l
DCC channel DCC channels use the DCC bytes in SDH frames, PDH microwave frames, or Hybrid microwave frames as the channels for the communication among NEs. In the IP over DCC solution,
In the case of a network that comprises only the OptiX transmission equipment, bytes D1 to D3 in SDH frames are generally used as DCC channels In the case of a network that comprises both OptiX transmission equipment and the third-party SDH equipment, the DCC bytes used by the third-party equipment (for example, bytes D1 to D3 or bytes D4 to D12) are used as DCC channels. In the PDH microwave frame, one DCC byte or three DCC bytes in the frame can be used as the DCC channel. In the Hybrid microwave frame, three DCC bytes in the frame can be used as DCC channels.
Ethernet physical channel The NE provides the Ethernet physical channel through the Ethernet NM port or the NE cascading port.
Data Link Layer

The main function of the data link layer is to provide reliable data transmission on physical links. In the case of DCCs, the NE adopts the PPP protocol to realize the data link layer function. The PPP protocol complies with RFC 1661.
3-4
Issue 02 (2009-02-25)
Network Layer
The main function of the network layer is to specify the network layer address for a network entity and to provide the transferring and addressing functions. The NE adopts the IP and the matching ARP and ICMP to realize the network layer functions.
Transport Layer
The main function of the transport layer is to provide the end-to-end communication service for the upper layer. The NE supports the connection-oriented TCP and the connectionless-oriented UDP.
Routing Protocols
Routing protocols belong to the scope of the application layer. The NE supports the two routing protocols, open shortest path first (OSPF) and routing information protocol (RIP). By default, the NE uses the OSPF protocol. The RIP protocol is used only when the interconnected thirdparty equipment does not support the OSPF protocol. The OSPF protocol is a dynamic routing protocol that is based on the link status. The OSPF protocol divides an autonomous system into several areas. Route nodes exchange routing information in an area. The route nodes at the edge of an area make summary and exchange 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 line port of the OptiX equipment is enabled with the OSPF protocol but the Ethernet port is not enabled with the OSPF protocol. Hence, to form a network through the Ethernet port, you need to modify the OSPF setting of the NE. In addition to the dynamic routing protocol, the NE supports static routes. Static routes are manually configured routes. Static routes have a higher priority than dynamic routes. When there is a route conflict, the equipment selects static routes.
3.2.2 Access Modes

In the IP over DCC solution, there are two modes for the T2000 to access an NE, namely, gateway mode and direct connection mode.
Gateway Mode
In the gateway mode, the T2000 accesses a non-gateway NE through the gateway NE. The gateway NE queries the core routing table of the application layer according to the ID of the NE to be accessed to obtain the corresponding route. The core routing table synthesizes the transport layer routing tables of all communication protocol stacks. Each route item includes the following:
l l l
ID of the destination NE Address of the transfer NE Communication protocol stack of the transfer NE
Issue 02 (2009-02-25)

l
Transfer distance
Direct Connection Mode

In the direct connection mode, the T2000 accesses an NE as the gateway NE. All transfer NEs on the access path query the IP routing table of the network layer according to the IP address of the NE to be accessed to obtain the corresponding route. The IP routing table is based on routing protocols. It includes both dynamic routes generated by routing protocols and static routes configured by operators. Each route item includes the following:
l l l l
Destination IP address Subnet mask IP address of the gateway Interface
When the T2000 adopts the direct connection mode to access an NE, there must be an IP route between the T2000 and the NE. In the IP over DCC solution, the T2000 can access any NE by using the direct connection mode, that is, it can consider any NE as the gateway NE. To improve the communication efficiency, however, there should not be a lot of NEs that are accessed in the direct connection mode in a network.
3.3 Availability
The IP over DCC solution requires the support of the applicable equipment and boards. Table 3-1 Availability of the IP over DCC solution Feature IP over DCC solution Applicable Board SCC (all the versions) Applicable Equipment IDU 605 IDU 610/620

It is recommended that you adopt only one of the following solutions to form a DCN: HW ECC solution, IP over DCC solution, and OSI over DCC solution. If you combine the IP over DCC solution with other solutions to form a network, note the following points:
l l l
The IP protocol stack of NEs can communicate with the HW ECC protocol stack. The IP protocol stack of NEs cannot communicate with the OSI protocol stack. If DCC bytes are used to transparently transmit NM messages when the OptiX equipment is used together with the third-party equipment to form a network, you can adopt the IP protocol stack to manage the OptiX equipment. It is, however, recommended that you use the HW ECC protocol.
3-6

l
If DCC bytes are used to transparently transmit NM messages through the external clock interface when the OptiX equipment is used together with the third-party equipment to form a network, you can adopt the IP protocol stack to manage the OptiX equipment. It is, however, recommended that you use the HW ECC protocol.

This topic describes how an NE transfers messages depending on the mode in which the T2000 accesses an NE. The realization principles in different modes vary slightly from each other.
Gateway Mode
Figure 3-3 illustrates how the IP over DCC solution transfers the messages originating from the T2000 to a non-gateway NE when the T2000 adopts the gateway mode to access the NE. Figure 3-3 Realization principle of message transferring (gateway mode)
Application TCP IP Application TCP IP TCP IP PPP Ethernet Ethernet DCC T2000 Gateway NE DCC Transfer NE DCC Destination NE IP PPP Application TCP IP PPP
The realization principle is as follows: 1. 2. 3. The T2000 transfers application layer messages to the gateway NE through the TCP connection between them. The gateway NE extracts the messages from the TCP/IP protocol stack and reports the messages to the application layer. The application layer of the gateway NE queries the address of the destination NE in the messages. If the address of the destination NE is not the same as the address of the local station, the gateway NE queries the core routing table of the application layer according to the address of the destination NE to obtain the corresponding route and the communication protocol stack of the transfer NE. As the communication protocol stack of the transfer NE in Figure 3-3 is IP, 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 NE IP address of the local station, the transfer NE queries the IP routing table according to the destination IP address to obtain the corresponding route, and then transfers the packet. After receiving the packet, the network layer of the destination NE reports the packet to the application layer through the transport layer because the destination IP address of the
4.
5.
Issue 02 (2009-02-25)
packet is the NE IP address of the local station. The application layer acts according to the message sent from the T2000.

Figure 3-4 illustrates how the IP over DCC solution transfers the messages originating from the T2000 to a destination NE when the T2000 adopts the direct connection mode to access the NE. Figure 3-4 Realization principle of message transferring (direct connection mode)
Application TCP IP IP PPP Ethernet Ethernet DCC T2000 Transfer NE DCC Transfer NE DCC Destination NE IP PPP Application TCP IP PPP
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.
3.6 Planning Guide

When using the IP over DCC solution, plan the parameters of a DCN depending on the situation of the network.
Prerequisite
Precautions
This guide focuses on the differences between planning the IP over DCC solution and planning the HW ECC solution. For the same parts, for example, for planning the external DCN, NE ID, and network division, see 2.6 Planning Guide.
Procedure
Step 1 According to the situation of the network, select a proper NE as the gateway NE. Adhere to the following principles when planning a gateway NE:
l
Select the NE that is the closest to the NMS, the central node of star services, or the NE that accesses the maximum number of DCCs, as the gateway NE if possible.
3-8

l
It is recommended that the number of the NEs in a subnet (which consists of one gateway NE (GNE) and non-GNEs managed by this GNE) does not exceed 50. The number of the NEs in this subnet cannot exceed 64.
Step 2 Plan DCCs. Adhere to the following principles when planning DCCs:
l
If the network comprises only the OptiX equipment, it is recommended that you use bytes D1 to D3 in SDH frames as DCCs. If the network comprises both OptiX equipment and the third-party SDH equipment, use the DCC bytes that the third-party equipment uses (for example, bytes D1 to D3 or D4 to D12) as DCCs. The PDH microwave always uses one DCC byte or three DCC bytes in PDH microwave frames as DCCs. The Hybrid microwave always uses three DCC bytes in Hybrid microwave frames as DCCs.
Step 3 Plan the IP addresses of NEs. Adhere to the following principles when planning the IP addresses of NEs:
l
The IP address, subnet mask, and default gateway of the gateway NE must meet the planning requirements of the external DCN. The non-gateway NEs managed by the same gateway NE can be in different IP network segments. The gateway NE and its managed non-gateway NEs cannot be in the same IP network segment. As shown in Figure 3-5, the gateway NE (NE101) is in the network segment 100.1.0.0 and its managed non-gateway NEs are in other network segments.
The IP addresses of the NEs that are interconnected with each other through Ethernet NM ports must belong to a network segment that is different from the network segment to which the IP addresses of the NEs that are connected to the previous NEs through transmission lines belong. As shown in Figure 3-5, NE105 and NE106 that are interconnected through the Ethernet NM ports are in the network segment 200.1.0.0, the NEs that NE105 connects are in the network segment 100.0.0.0, and the NEs that NE106 connects are in the network segment 200.0.0.0.
The subnet masks of the NEs that are in the same network segment must be the same.
Step 4 Plan IP routes. Adhere to the following principles when planning IP routes:
l l l
The gateway NE and its managed non-gateway NEs must be in the same OSPF area. The number of NEs in an OSPF area should not exceed 64. Plan static routes when there is no dynamic route for interconnection at the network layer between the T2000 and the gateway NE or between the T2000 and the NEs that need to be directly accessed by the T2000.
----End
Issue 02 (2009-02-25)
3-9
Example
Figure 3-5 Networking example for the IP over DCC solution
NE105 NE106 NE208
Third-party NMS NE104
NE207
T2000
NE101 NE102
NE103
Third-party transmission equipment OptiX transmission equipment Quidway 2501 Radio link Network cable Hub Fiber 2 Mbit/s channel
Figure 3-6 shows a transmission network that comprises both OptiX equipment and the thirdparty equipment that supports the IP over DCC feature. The steps to plan the DCN are as follows: 1. 2. 3. Select NE101 that is the closest to the NMS as the gateway NE. As the third-party equipment uses the DCC bytes D1 to D3, it is not required to modify the DCCs of the NEs. Allocate IDs and IP addresses for all the NEs according to the situation of the network. The subnet mask of all the NEs is 255.255.0.0.
3-10
Issue 02 (2009-02-25)
Figure 3-6 Allocation of IDs and IP addresses for all NEs

9-108 200.0.0.108 0.0.0.0 10.0.0.1/16 9-105 200.1.0.105 0.0.0.0 9-106 200.1.0.106 0.0.0.0 9-107 200.0.0.107 0.0.0.0
10.0.0.100/16
9-104 100.0.0.105 0.0.0.0 100.1.0.1/16 9-101 100.1.0.101 0.0.0.0
100.1.0.100/16
9-103 100.0.0.103 0.0.0.0 9-102 100.0.0.102 0.0.0.0
30.0.0.1/16 30.0.0.2/16 30.0.0.3/16 30.0.0.4/16
4.
Plan IP routes.
l
As the number of the NEs is smaller than 64 and all the NEs support the OSPF protocol, configure all the NEs to the same OSPF area. As the T2000 and the gateway NE (NE101) are in the same Ethernet network segment and the gateway NE can obtain the routes to all other NEs through the OSPF protocol, the T2000 can access any NE in the gateway mode, and there is no need to set any route. As there are routers between the third-party NMS and NE101, using only dynamic routes cannot achieve the connection between the third-party equipment and the NMS. Hence, it is necessary to set static routes on NE101, NE102, the T2000 server, and the routers.

This topic describes the configuration flow and the corresponding configuration tasks of the IP over DCC solution. An example is provided as additional information to help understand the configuration. 3.7.1 Configuration Flow The configuration of the IP over DCC solution consists of two parts, that is, the configuration at the near end of the NE by using the Web LCT and the creation of the NE topology on the T2000. 3.7.2 Querying IP Routes By querying IP routes, you can verify whether the configuration of the IP over DCC feature is correct and whether the DCC communication is normal. 3.7.3 Creating Static IP Routes When dynamic routes fail to meet the planning requirements, create the corresponding static IP routes manually.

The configuration of the IP over DCC solution consists of two parts, that is, the configuration at the near end of the NE by using the Web LCT and the creation of the NE topology on the T2000. Figure 3-7 Configuration flow for the IP over DCC solution
Start 1
Modify IDs and IP addresses for NEs
2 Configure DCCs for NEs 3 Check the IP routes of the gateway NE
IP static routes required? Yes Add IP static routes 5
No
Create NEs on the T2000
End
3-12
Issue 02 (2009-02-25)
Table 3-2 Description of the configuration flow of the IP over DCC solution Number 1 Description
l l
Each NE must be configured with an NE ID and an IP address. When setting the IP address information for the gateway NE, you may need to set the default gateway to reduce the number of static IP routes, in addition to setting the IP address and subnet mask. For information on modifying the ID of an NE, see 2.7.2 Modifying the NE ID. For information on modifying the IP address information of an NE, see 2.7.3 Modifying the Communication Parameters of an NE. The DCC protocol type of the line port should be set to IP. The DCC channel type of the SDH port should be the same as that of the third-party equipment. If the network comprises only the OptiX equipment, set the DCC channel type to D1-D3 (default value). Adjusting the DCC type of the PDH microwave port or the Hybrid microwave port manually is not required. For the configuration process, see 2.7.4 Configuring DCCs. In normal situations, the gateway NE should have the routes to all its managed non-gateway NEs and the route to the T2000. If certain routes are unavailable, request Huawei engineers to adjust the parameters of the OSPF protocol used by the NEs. For the querying process, see 3.7.2 Querying IP Routes.
l l
4 5
For the configuration process, see 3.7.3 Creating Static IP Routes. There are two methods to create an NE on the T2000.
l
3.7.2 Querying IP Routes

By querying IP routes, you can verify whether the configuration of the IP over DCC feature is correct and whether the DCC communication is normal.
Prerequisite
Issue 02 (2009-02-25)
3-13
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Stack Protocol Management from the Function Tree. Click the IP Route Management tab. Step 2 Check whether the IP routes and their parameters in the routing table are in accordance with the planning information. ----End
3.7.3 Creating Static IP Routes

When dynamic routes fail to meet the planning requirements, create the corresponding static IP routes manually.
Prerequisite
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Stack Protocol Management from the Function Tree. Click the IP Route Management tab. Step 2 Click New. The system displays the Create an IP Route dialog box. Step 3 Set the parameters of the static IP route.
Parameters
Parameter Destination Address Mask Value Range Default Value Description You can set this parameter to an IP address or an IP address range. This parameter specifies the subnet mask of the set Destination Address.
Issue 02 (2009-02-25)
3-14
Parameter Gateway IP
Value Range -
Default Value -
Description This parameter specifies the IP address of the gateway to which the set Destination Address corresponds, that is, the next-hop address.
NOTE
The created static route has a lower priority than a dynamic route.

This topic provides an example to describe how to configure the IP over DCC solution.
Precautions
NOTE
l l l
For the parameters in this example, refer to the example in 3.6 Planning Guide. This example provides only the configurations of the typical NEs: NE101, NE102, NE105, and NE106. The following steps are provided to configure the functions one by one. This is for convenience of description. In an actual configuration, perform the configuration for the NEs one by one.
Procedure
l l l l
The extended ID of NE101 is 9 and the ID is 101. The extended ID of NE102 is 9 and the ID is 102. The extended ID of NE105 is 9 and the ID is 105. The extended ID of NE106 is 9 and the ID is 106.
Step 2 Set the IP address information for the NEs. See 2.7.3 Modifying the Communication Parameters of an NE.
l
The IP address of NE101 is 100.1.0.101, the subnet mask is 255.255.0.0, and the default gateway is 0.0.0.0 (default value). The IP address of NE102 is 100.0.0.102, the subnet mask is 255.255.0.0, and the default gateway is 0.0.0.0 (default value). The IP address of NE105 is 200.1.0.105, the subnet mask is 255.255.0.0, and the default gateway is 0.0.0.0 (default value). The IP address of NE106 is 200.1.0.106, the subnet mask is 255.255.0.0, and the default gateway is 0.0.0.0 (default value). Set the DCC protocol type of all the line ports of all NEs to IP. Set the channel type of all SDH microwave ports of all NEs to D1-D3 (default value). Set the channel type of all PDH microwave ports of all NEs to the default value.
l l l
Step 4 Query the IP routes of NE101. See 3.7.2 Querying IP Routes.


l
The IP address of each non-gateway NE (for example, 100.0.0.102, 200.1.0.105, and 200.1.0.106) should have corresponding IP routes. The IP address of the T2000 server (10.1.0.100) should have corresponding routes. The IP address of the third-party equipment (for example, 30.0.0.4) should have corresponding IP routes.
NOTE
l l
If certain routes are unavailable, request Huawei engineers to adjust the parameters of the OSPF protocol used by the NEs.
Step 5 Set an IP static route at both NE101 and NE102. See 3.7.3 Creating Static IP Routes.
l
The parameters of the IP static route at NE101 are as follows:

Destination address: 10.0.0.0 Subnet mask: 255.255.0.0 Gateway: 100.1.0.1 Destination address: 10.0.0.0 Subnet mask: 255.255.0.0 Gateway: 100.1.0.101
The parameters of the IP static route at NE102 are as follows:

NOTE
Set the corresponding route on both the NMS of the third-party equipment and the router.
Step 6 Search and create NEs with 100.1.0.101 as the IP address of the gateway NE. See 2.7.8 Creating NEs by Using the Search Method.
NOTE
In the case of a planned non-gateway NE, set Gateway to the gateway NE to which it belongs.

This topic describes the alarms and performance events relevant to the IP over DCC solution, and the problems that occur frequently during the application of the solution. 3.9.1 Relevant Alarms and Events When there is a fault in the communication between the T2000 and an NE, the T2000 reports the corresponding alarm. 3.9.2 FAQs This topic lists the problems that occur frequently during the application of the IP over DCC solution.

Relevant Alarms
l
GNE_CONNECT_FAIL The GNE_CONNECT_FAIL alarm indicates that the connection between the T2000 and the gateway NE fails. When the connection between the T2000 and the gateway NE fails, the T2000 reports this alarm.
Relevant Events
None.
3.9.2 FAQs
This topic lists the problems that occur frequently during the application of the IP over DCC solution. 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 adopts the standard TCP/IP protocol stack. With the IP over DCC solution, the OptiX equipment easily interworks with the third-party equipment and hence the network management is simplified. The IP over DCC solution adopts the transfer function of the network layer of the protocol stack. Hence, no extra overhead and service channels are required. The IP over DCC solution allows different vendors to multiplex the same physical channels. The NMS of a vendor is not required to be directly connected to the equipment of the same 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
Q: Why does the T2000 always fail to log in to an NE? A: Common causes are as follows:
l
The communication connection between the T2000 and the gateway NE is faulty. To locate the fault, run the ping or tracert command on the T2000 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.
Issue 02 (2009-02-25)
3-17
Q: How does one use the IP over DCC solution to interconnect the OptiX equipment with the 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 the third-party equipment. Check the PPP protocol parameters with the maintenance staff of the third-party equipment. Check the parameters of the OSPF protocol with the maintenance staff of the 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 the third-party equipment to check whether there is a route to the interconnected NE. If no route is obtained, the PPP interconnection fails. 6. Query IP routes at the gateway NE to check whether 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.
3-18
Issue 02 (2009-02-25)
4
About This Chapter
OSI over DCC Solution
The NEs use unified DCCs to transmit the data of the OSI protocol by using the OSI over DCC solution. In this way, the NMS can manage NEs. The OSI over DCC solution applies to a network that comprises the OptiX equipment and the third-party equipment that supports the OSI over DCC function. 4.1 Feature Description This topic considers the application of the IP over DCC solution (when a network comprises the OptiX transmission equipment and the third-party equipment that supports the OSI over DCC function) as an example to describe the OSI over DCC solution. 4.2 Basic Concepts This topic describes the basic concepts that you should be familiar with before you use the OSI over DCC solution. 4.3 Availability The OSI over DCC solution requires the support of the applicable equipment and boards. 4.4 Relation with Other Features It is recommended that you adopt only one of the following solutions to form a DCN: HW ECC solution, IP over DCC solution, and OSI over DCC solution. 4.5 Realization Principle This topic describes how an NE transfers messages depending on the mode in which the T2000 accesses an NE. The realization principles in different modes vary slightly from each other. 4.6 Planning Guide When using the OSI over DCC solution, plan the parameters of a DCN according to the situation of the network. 4.7 Configuration Guide This topic describes the configuration flow and the corresponding configuration tasks of the OSI over DCC solution. An example is provided as additional information to help understand the configuration. 4.8 Configuration Example This topic provides an example to describe how to configure the OSI over DCC solution.
4.9 Maintenance Guide This topic describes the alarms and performance events relevant to the OSI over DCC solution, and the problems that occur frequently during the application of the solution.
4-2
Issue 02 (2009-02-25)

This topic considers the application of the IP over DCC solution (when a network comprises the OptiX transmission equipment and the third-party equipment that supports the OSI over DCC function) as an example to describe the OSI over DCC solution. If the third-party equipment supports the OSI over DCC function, the third-party equipment can communicate with the NMS through DCCs of the OptiX transmission equipment. See Figure 4-1. Figure 4-1 Application of the OSI over DCC solution
Third-party NMS
OSI DCN T2000
Third-party transmission equipment Radio link Fiber
OptiX transmission equipment Network cable
4.2 Basic Concepts

This topic describes the basic concepts that you should 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 Access Mode In the OSI over DCC solution, there are two modes for the T2000 to access an NE, namely, gateway mode and direct connection 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 Architecture of the OSI over DCC protocol stack

Transport layer Network layer Data link layer Ethernet Physical layer DCC TP4 IS-IS/ES-IS/CLNP LAPD
Physical Layer
The main function of the physical layer is to provide channels for data transmission, for the data end equipment. Physical channels are classified as follows:
l
DCC channel DCC channels use the DCC bytes in SDH frames or PDH microwave frames as the channels for the communication among NEs. In the OSI over DCC solution, for a network that comprises only the OptiX equipment, bytes D1 to D3 in SDH frames are generally used as DCC channels; for a network that comprises both OptiX equipment and the third-party SDH equipment, the DCC bytes used by the third-party equipment (for example, bytes D1 to D3 or bytes D4 to D12) are used as DCC channels. In the PDH microwave frame, one or three DCC bytes in the frame can be used as the DCC channel.
l l
The Hybrid microwave always uses three DCCs in Hybrid microwave frames as DCCs. Ethernet physical channel The NE provides the Ethernet physical channel through the Ethernet NM port or the NE cascading port.
Data Link Layer

The main function of the data link layer is to provide reliable data transmission on physical links. In the case of DCCs, the NE adopts the LAPD protocol to realize the data link layer function. The LAPD protocol complies with ITU-T Q.921. When using the LAPD protocol, you must set the LAPD role. In the case of the two ends of a DCC, set the LAPD role to Network at one end and to User at the other end.
Network Layer
The main function of the network layer is to specify the network layer address for a network entity and to provide the transferring and addressing functions. The NE adopts the ISO-defined connectionless network service (CLNS) to realize the network layer function. The CLNS comprises the following three protocols:

l
Connectionless network protocol (CLNP) The CLNP protocol complies with ISO 8473. It has functions similar to the IP in the TCP/ IP protocol stack. In the CLNP protocol, the network service access point (NSAP) works as the network layer address. The NSAP functions as the IP address in the IP protocol. The address format of the NSAP is as shown in Figure 4-3. Figure 4-3 Format of the NSAP address
IDP Higher order DSP AFI IDI+pad DFI ORG RES RD Area System ID 9 10 11 12 13 14 15 16 17 18 19
NSEL
DSP
Area address 1 2 3 4 5 6 7 8
20
The NE uses the simplified NSAP address. The simplified NSAP address includes only the following three parts:
Area ID The area ID refers to the area address shown in Figure 4-3 and has one to thirteen bytes. The area ID is used to address the routes between areas. The NSAPs of the NEs in the same L1 route area must have the same area ID but those in the same L2 route area can have different area IDs. You can manually set the area ID. The default value of the area ID is 0x47000400060001.
System ID The System ID refers to the system ID shown in Figure 4-3 and has six bytes. The System ID is used to address the routes within an area. The value of the first three bytes of the System ID of the OptiX equipment is always 0x08003E. The last three bytes are the NE ID.
NSEL The NSEL refers to the port ID of the network layer protocol. It has one byte. The NSEL of the OptiX equipment is always 0x1D.
IS-IS protocol In the CLNS, NEs are classified into intermediate systems (IS) and end systems (ES) according to the NE role. The IS is equivalent to the router in the TCP/IP protocol stack and the ES is equivalent to the host. The IS-IS protocol is a dynamic routing protocol between two ISes. It complies with ISO 10589 and functions as the OSPF protocol in the TCP/IP protocol stack. The IS-IS protocol supports the L1 and L2 layered routes. The NE whose role is L1 cannot be a neighbor of an NE in a different area and is involved only in the routes in its own area. It issues a default route that points to its closest L2 NE and accesses other areas through the default route. The NE whose role is L2 can be a neighbor of the L2 NE in a different area and can also be involved in the routes in the backbone area. The backbone area is formed by consecutive L2 NEs. In other words, the L2 NEs in the backbone area must be consecutive (connected). In the network as shown in Figure 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.
Issue 02 (2009-02-25)
4-5
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. Generally, 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 adopts the TP4 protocol to realize the transport layer function. The TP4 protocol complies with ISO 8073. It has functions similar to the TCP in the TCP/IP protocol stack.
4.2.2 Access Mode

In the OSI over DCC solution, there are two modes for the T2000 to access an NE, namely, gateway mode and direct connection mode.
Gateway Mode
In the gateway mode, the T2000 accesses a non-gateway NE through the gateway NE. The gateway NE queries the core routing table of the application layer according to the ID of the NE to be accessed to obtain the corresponding route.
The core routing table synthesizes the transport layer routing tables of all communication protocol stacks. Each route item includes the following:
l l l l
ID of the destination NE Address of the transfer NE Communication protocol stack of the transfer NE Transfer distance

In the direct connection mode, the T2000 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, the T2000 can access any NE by using the direct connection mode, that is, the T2000 can consider any NE as the gateway NE. To improve the communication efficiency, there should not be a lot of NEs that are accessed in the direct connection mode in a network.
4.3 Availability
The OSI over DCC solution requires the support of the applicable equipment and boards. Table 4-1 Availability of the OSI over DCC solution Feature OSI over DCC solution Applicable Board SCC (all the versions) Applicable Equipment IDU 610/620

It is recommended that you adopt only one of the following solutions to form a DCN: HW ECC solution, IP over DCC solution, and OSI over DCC solution.
If you combine the OSI over DCC solution with other solutions to form a network, note the following points:
l
The OSI protocol stack of NEs can communicate with the HW ECC protocol stack only in the same area of the L1 layer. The OSI protocol stack of NEs cannot communicate with the IP protocol stack. If DCC bytes are used to transparently transmit NM messages when the OptiX equipment is used together with the third-party equipment to form a network, you can adopt the OSI protocol stack to manage the OptiX equipment. It is, however, recommended that you use the HW ECC protocol. If DCC bytes are used to transparently transmit NM messages through the external clock interface when the OptiX equipment is used together with the third-party equipment to form a network, you can adopt the OSI protocol stack to manage the OptiX equipment. It is, however, recommended that you use the HW ECC protocol.
l l

This topic describes how an NE transfers messages depending on the mode in which the T2000 accesses an NE. The realization principles in different modes vary slightly from each other.
Gateway Mode
Figure 4-5 illustrates how the OSI over DCC solution transfers T2000 messages to a nongateway NE when the T2000 adopts the gateway mode to access the NE. Figure 4-5 Realization principle of message transferring (gateway mode)
Application TP4 ES-IS/CLNP Application TP4 TP4 IS-IS/CLNP LAPD DCC Transfer NE Application TP4 IS-IS/CLNP LAPD DCC Destination NE
ES-IS/CLNP IS-IS/CLNP LAPD
Ethernet
Ethernet DCC
T2000
Gateway NE
The realization principle is as follows: 1. As an ES, the T2000 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
2. 3.
4-8
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-5 is OSI, the gateway NE transfers the messages to the transfer NE through the OSI protocol stack. 4. 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 T2000.
5.

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

When using the OSI over DCC solution, plan the parameters of a DCN according to the situation of the network.
Prerequisite
Issue 02 (2009-02-25)
4-9
Precautions
This guide focuses on the differences between planning the OSI over DCC solution and planning the HW ECC solution. For the same parts, for example, for planning the NE ID and network division, see 2.6 Planning Guide.
Procedure
Step 1 Plan areas. Adhere to the following principles when planning areas:
l
It is recommended that the number of areas does not exceed 20. The maximum number of areas can be 32. It is recommended that the number of NEs in an area does not exceed 32. The maximum number of NEs in an area can be 50. Each area should have L2 NEs and the L2 NEs must be consecutive. The area ID of each area must be unique.
l l
Step 2 According to the situation of the network, select a proper NE as the gateway NE. Adhere to the following principles when planning a gateway NE:
l
If there are multiple areas, set a gateway NE for each area, and assign a priority to the L2 NE to be the gateway NE. It is recommended that the number of the NEs in a subnet (which consists of one gateway NE (GNE) and non-GNEs managed by this GNE) does not exceed 32. The number of the NEs in this subnet cannot exceed 50. Select the NE that is the closest to the NMS, the central node of star services, or the NE that accesses the maximum number of DCCs, as the gateway NE if possible.
Step 3 Plan the external DCN. Adhere to the following principles when planning an external DCN:
l
The bandwidth of the external DCN must not be lower than the DCC bandwidth that the network uses. The link at 256 kbit/s already meets the requirements. The router that the external DCN uses must be able to support the OSI protocol stack. The channel for the external DCN should be provided by another network (not the monitored network). Active and standby DCN routes or gateways should be provided for the external DCN if possible.
l l
l
If the network comprises only the OptiX equipment, it is recommended that you use bytes D1 to D3 in SDH frames as DCCs. If the network comprises both OptiX equipment and the third-party SDH equipment, use the DCC bytes that the third-party equipment uses (for example, bytes D1 to D3 or D4 to D12) as DCCs.
4-10

l
The LAPD role of a DCC must be set to User at one end and to Network at the other end of the DCC.
NOTE
It is not required to adjust the DCC type of the PDH microwave port manually.
----End
Example
Figure 4-7 Networking example for the OSI over DCC solution
NE302 NE303 NE304
Third-party NMS NE101 OSI DCN T2000
NE301
NE102 NE201
NE202 Third-party transmission equipment
OptiX transmission equipment Radio link Fiber Network cable
Figure 4-7 shows a transmission network that comprises both OptiX equipment and the thirdparty equipment that supports the OSI over DCC feature. The steps to plan the DCN are as follows: 1. Plan network areas according to the situation of the network. Considering the number of the NEs, divide the entire DCN into three areas to make the number of the NEs in each area smaller than 32. In addition, set the four NEs on the central ring as L2 NEs to ensure that each area has an L2 NE and the L2 NEs are consecutive.
Issue 02 (2009-02-25)
4-11
Figure 4-8 Allocation of NE areas

AREA ID: 0x394F1200
Area 3
Third-party NMS OSI DCN T2000 L2
L2 L2
L2
Area 2
Area 1
AREA ID: 0x394F1190 AREA ID: 0x394F1210
2.
Select the gateway NE. Select NE101, NE201, and NE301 as the gateway NEs to manage the OptiX NEs in their own areas.
3. 4.
Select the router that supports the OSI protocol stack to form the external DCN. Plan DCCs.
l
As the third-party equipment uses the DCC bytes D1 to D3, it is not required to modify the DCCs of the NEs. Set the LAPD role of each DCC to Network at the end nearer to the T2000 and to User at the other end of the DCC.

This topic describes the configuration flow and the corresponding configuration tasks of the OSI over DCC solution. An example is provided as additional information to help understand the configuration. 4.7.1 Configuration Flow The configuration of the OSI over DCC solution consists of two parts, that is, the configuration at the near end of the NE by using the Web LCT and the creation of the NE topology on the T2000. 4.7.2 Configuring the CLNS Role When the CLNS role of an NE is L1, the NE is involved in the routes in the area. When the CLNS role of an NE is L2, the NE is involved in the routes between areas. By default, the CLNS role of the OptiX equipment is L1.
4.7.3 Querying OSI Routes By querying OSI routes, you can verify whether the configuration of the OSI over DCC feature is correct and whether the DCC communication is normal.

The configuration of the OSI over DCC solution consists of two parts, that is, the configuration at the near end of the NE by using the Web LCT and the creation of the NE topology on the T2000. Figure 4-9 Configuration flow for the OSI over DCC solution
Start 1
Modify IDs and NSAP addresses for NEs
2 Configure DCCs for NEs 3 Configure the CLNS role 4 Query L1 routes and L2 routes 5
Create NEs on the T2000
End
Table 4-2 Description of the configuration flow of the OSI over DCC solution Number 1 Description
l l
Each NE must be configured with an NE ID and an NSAP address. When modifying an NSAP address, you only need to modify the area ID, and the other parts are automatically generated by the NE. For information on modifying the ID of an NE, see 2.7.2 Modifying the NE ID. For information on modifying the NSAP address information of an NE, see 2.7.3 Modifying the Communication Parameters of an NE.
4-13
Issue 02 (2009-02-25)
Number 2
Description
l l
The DCC protocol type of the line port should be set to OSI. In the case of the two ends of a DCC, set the LAPD role to User at one end and to Network at the other end. The DCC channel type of the SDH port should be the same as that of the third-party equipment. If the network comprises only the OptiX equipment, set the DCC channel type to D1-D3 (default value). It is not required to adjust the DCC type of the PDH microwave port manually. For the configuration process, see 2.7.4 Configuring DCCs. By default, the CLNS role of the OptiX equipment is L1. For the configuration process, see 4.7.2 Configuring the CLNS Role. 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. The gateway NE has the route to the T2000 or the routes to the L2 NEs that are in the same area as the T2000. The gateway NE has the routes to all non-gateway NEs. For the querying process, see 4.7.3 Querying OSI Routes.
l l
l l
l l

l
Before you create an NE, install the OSI protocol stack software on the T2000 server.
4.7.2 Configuring the CLNS Role

When the CLNS role of an NE is L1, the NE is involved in the routes in the area. When the CLNS role of an NE is L2, the NE is involved in the routes between areas. By default, the CLNS role of the OptiX equipment is L1.
Prerequisite
4-14
Issue 02 (2009-02-25)
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 "This operation will result in SCC warm reset that is service affecting. Are you sure to continue?" Step 5 Click Yes. ----End
Parameters
Parameter Configuration Role Value Range L2, L1 Default Value L1 Description
l
The NE whose Configuration Role is set to L1 cannot be a neighbor of an NE in a different area and is involved only in the routes in its own area. It issues a default route that points to its closest L2 NE and accesses other areas through the default route. The NE whose Configuration Role is set to L2 can be a neighbor of the L2 NE in a different area and can also be involved in the routes in the backbone area. The backbone area is formed by consecutive L2 NEs. That is, the L2 NEs in the backbone area must be consecutive (connected).
4.7.3 Querying OSI Routes

By querying OSI routes, you can verify whether the configuration of the OSI over DCC feature is correct and whether the DCC communication is normal.
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 Routing Table tab. Step 3 Check whether the information in Link Adjacency Table meets the planning requirements. Step 4 Click the L1 Routing tab to check whether the information of the L1 routes is correct. Step 5 Click the L2 Routing tab to check whether the information of the L2 routes is correct. ----End

This topic provides an example to describe how to configure the OSI over DCC solution.
Precautions
NOTE
l l
For the parameters in this example, refer to the example in 4.6 Planning Guide. This example provides only the configurations of the typical NEs: NE101, NE201, NE301, and NE302.
Procedure
l l l l
The extended ID of NE101 is 9 and the ID is 101. The extended ID of NE201 is 9 and the ID is 201. The extended ID of NE301 is 9 and the ID is 301. The extended ID of NE302 is 9 and the ID is 302.
Step 2 Set the NSAP address information for the NEs. See 2.7.3 Modifying the Communication Parameters of an NE.
l l l l
The area ID in the NSAP address of NE101 is 0x394F1190. The area ID in the NSAP address of NE201 is 0x394F1210. The area ID in the NSAP address of NE301 is 0x394F1200. The area ID in the NSAP address of NE302 is 0x394F1200.
l l
Set Protocol for all the line ports of all the NEs to IP. Set Channel Type for all the SDH microwave ports of all the NEs to D1-D3 (default value). Use the default channel type for all the PDH microwave ports. The CLNS role of NE201 and NE302 is L1 (default value). The CLNS role of NE101 and NE301 is L2.
Step 4 Configure the CLNS role for the NEs. See 4.7.2 Configuring the CLNS Role.
l l
Step 5 Query OSI routes. See 4.7.3 Querying OSI Routes.


l
In the L1 routing table, NE101, NE201, NE301, and NE302 have the routes to all the NEs that are in their respective areas. In the L2 routing table, NE101 and NE301 have the routes to other L2 NEs.
Step 6 Use the search method to create NEs on the T2000. See 2.7.8 Creating NEs by Using the Search Method. The search domains include the following:
l l l
The search domain with the NSAP address being 0x394F1190 The search domain with the NSAP address being 0x394F1200 The search domain with the NSAP address being 0x394F1210
NOTE
l l
Before you search NEs, first install the OSI protocol stack software on the T2000. In the case of a planned non-gateway NE, set Gateway to the gateway NE to which it belongs.

This topic describes the alarms and performance events relevant to the OSI over DCC solution, and the problems that occur frequently during the application of the solution. 4.9.1 Relevant Alarms and Events When there is a fault in the communication between the T2000 and an NE, the T2000 reports the corresponding alarm. 4.9.2 FAQs This topic lists the problems that occur frequently during the application of the OSI over DCC solution.

Relevant Alarms
l
Issue 02 (2009-02-25)
4-17
Relevant Events
None.
4.9.2 FAQs
This topic lists the problems that occur frequently during the application of the OSI over DCC solution. 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 adopts the standard OSI protocol stack. With the OSI over DCC solution, the OptiX equipment easily interworks with the third-party equipment and hence the network management is simplified. The OSI over DCC solution adopts the transfer function of the network layer of the protocol stack. Hence, no extra overhead and service channels are required. 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 must be installed with the OSI protocol stack software. The OSI network is not applied as widely as the TCP/IP network and there are not many OSI-based management tools.
Q: Why does the T2000 always fail to log in to an NE? A: Common causes are as follows:
l
The T2000 is not installed with the OSI protocol stack or the router does not support the OSI protocol stack. If this is the case, the T2000 fails to log in to all 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 the third-party equipment? A: The steps are as follows: 1. 2. Check the DCC bytes used by DCCs with the maintenance staff of the third-party equipment. Check the LAPD role and other LAPD parameters with the maintenance staff of the thirdparty equipment.
4-18
3. 4. 5.
Check the protocol parameters of the network layer such as the area ID in the NSAP address and the CLNS role with the maintenance staff of the 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 the third-party equipment to check whether there is an LAPD link to the interconnected NE. If no route is obtained, the LAPD protocol interconnection fails. Query the OSI routes of the OptiX NE that is in the same area as the third-party equipment to check whether there are L1 routes to the interconnected NE and other third-party equipment. If the 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 whether there is an L2 route to the thirdparty equipment. If no route is obtained, the interconnection of the network layer protocol fails.
6.
Issue 02 (2009-02-25)
4-19
5 DCC Transparent Transmission Solution
DCC Transparent Transmission Solution
About This Chapter

Vendors use different DCCs to transmit data by using the DCC transparent transmission solution. In this way, communication of NM messages is realized when the equipment of the vendor is used together with the third-party equipment to form a network. There is a limitation, however, because the NMS of a vendor can manage only the NEs of the vendor. 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 adopts different DCCs to transmit the NM messages of different vendors to realize the communication between NM messages. 5.2 Availability The DCC transparent transmission solution requires support of the applicable equipment and boards. 5.3 Relation with Other Features If you adopt the DCC transparent transmission solution to communicate NM messages when the OptiX equipment is used together with the third-party equipment to form a network, you can use any of the HW ECC protocol stack, IP protocol stack, and OSI protocol stack to manage the OptiX equipment. It is recommended that you use the HW ECC protocol stack. 5.4 Realization Principle The OptiX equipment realizes the transparent transmission of DCC through the overhead crossconnect matrix. 5.5 Planning Guide When using the DCC transparent transmission solution, plan the parameters of a DCN according to the situation of the network. 5.6 Configuration Flow The configuration of the DCC transparent transmission solution consists of two parts, that is, the configuration at the near end of the NE by using the Web LCT, and the creation of the NE topology on the T2000. 5.7 Configuration Example
Issue 02 (2009-02-25)
5-1
This topic provides an example to describe how to configure the DCC transparent transmission solution. 5.8 Maintenance Guide This topic describes the alarms and performance events relevant to the DCC transparent transmission solution, and the problems that occur frequently during the application of the solution.
5-2
Issue 02 (2009-02-25)

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 adopts different DCCs to transmit the NM messages of different vendors to realize the communication between NM messages. 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
The third-party equipment uses bytes D1 to D3 as DCCs. In this case, the OptiX equipment uses bytes D4 to D12 as DCCs. In addition, you need to add a route to transparently transmit bytes D4 to D12 in the transmission network of the third-party equipment. Figure 5-1 DCC transparent transmission solution when the OptiX equipment is at the edge of a network (1)
D4-D12 D4-D12
D4-D12 D4-D12
D4-D12
D4-D12
OptiX equipment
Third-party equipment
The third-party equipment uses bytes D4 to D12 as DCCs. In this case, the OptiX equipment still uses bytes D1 to D3 as DCCs. In addition, you need to add a route to transparently transmit bytes D1 to D3 in the transmission network of the third-party equipment.
Issue 02 (2009-02-25)
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
D1-D3
D1-D3
OptiX equipment
OptiX Equipment in the Center of a Network

In this networking scenario, there are two possibilities:
l
The third-party equipment uses bytes D1 to D3 as DCCs. In this case, the OptiX equipment uses bytes D4 to D12 as DCCs. In addition, you need to add a route to transparently transmit bytes D1 to D3. Figure 5-3 DCC transparent transmission solution when the OptiX equipment is in the center of a network (1)
D1-D3 D1-D3
D1-D3 D1-D3
D1-D3 D1-D3
OptiX equipment
5-4
Issue 02 (2009-02-25)
The third-party equipment uses bytes D4 to D12 as DCCs. In this case, the OptiX equipment still uses bytes D1 to D3 as DCCs. In addition, you need to add a route to transparently transmit bytes D4 to D12. 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
D4-D12 D4-D12
OptiX equipment
5.2 Availability
The DCC transparent transmission solution requires support of the applicable equipment and boards. Table 5-1 Availability of the DCC transparent transmission solution Feature DCC transparent transmission solution Applicable Board SCC (all the versions) Applicable Equipment IDU 610/620

If you adopt the DCC transparent transmission solution to communicate NM messages when the OptiX equipment is used together with the third-party equipment to form a network, you can use any of the HW ECC protocol stack, IP protocol stack, and OSI protocol stack to manage the OptiX equipment. It is recommended that you use the HW ECC protocol stack.
Issue 02 (2009-02-25)
5-5

The OptiX equipment realizes the transparent transmission of DCC through the overhead crossconnect matrix. In the receive direction: 1. The line board extracts the overhead bytes such as DCC bytes from the received SDH signals, forms a 2.048 Mbit/s overhead signal stream, and sends the overhead signal stream to the overhead cross-connect matrix of the SCC board through the overhead bus. The overhead cross-connect matrix transports the DCC bytes that the NE uses to the CPU and directly transports the DCC bytes that are to be transparently transmitted, to the overhead bus of the corresponding line board. The CPU processes the NM messages carried by the DCC bytes according to the protocol stack of the DCCs.
2.
3.
In the transmit direction: 1. The CPU of the SCC board encapsulates the NM messages into the DCC bytes according to the protocol stack and transmits the DCC bytes to the overhead cross-connect matrix of the SCC board. The overhead cross-connect matrix combines the DCC bytes sent from the CPU and other overhead bytes (including the DCC bytes sent from the other line boards and orderwire bytes) to form a 2.048 Mbit/s overhead signal stream, and then transmits the overhead signal stream to the corresponding line board. The line board extracts the overhead signal from the overhead signal stream, inserts the overhead signal into the SDH signal, and sends the SDH signal to other NEs.
2.
3.
Figure 5-5 illustrates how an NE uses bytes D1 to D3 as DCCs to transparently transmit bytes D4 to D12. Figure 5-5 Realization principle of the DCC transparent transmission
D4-D12 Overhead crossconnect matrix D1-D3 CPU Line board SCC board Line board
SDH signal
Overhead bus
Overhead bus
SDH signal
5.5 Planning Guide

When using the DCC transparent transmission solution, plan the parameters of a DCN according to the situation of the network.
Prerequisite
Precautions
This guide focuses on the differences between planning the DCC transparent transmission solution and planning the HW ECC solution. For the same parts, for example, for planning the gateway NE and external DCN, see 2.6 Planning Guide.
Procedure
l
If the third-party equipment uses bytes D1 to D3 as DCCs, the SDH port of the OptiX NE uses bytes D4 to D12 as DCCs. If the third-party equipment uses bytes D4 to D12 as DCCs, the SDH port of the OptiX NE uses bytes D1 to D3 as DCCs. The PDH microwave port or the Hybrid microwave port does not support DCC transparent transmission.
Step 2 Plan routes for DCC transparent transmission. ----End
Issue 02 (2009-02-25)
5-7
Example
Figure 5-6 Networking example for the DCC transparent transmission solution
Third-party NMS
NE1
T2000
NE4
NE2
NE3
OptiX transmission equipment Third-party transmission equipment
Network cable
Radio link
Fiber
Figure 5-6 shows a transmission network that comprises both OptiX equipment and the thirdparty equipment that supports the DCC transparent transmission feature. The steps to plan the DCN are as follows: 1. Plan DCCs. As the third-party equipment uses bytes D1 to D3 as DCCs, the OptiX NE uses bytes D4 to D12 as DCCs. 2. Allocate IDs for the NEs and configure the IP address for the gateway NE.
5-8
Issue 02 (2009-02-25)
Figure 5-7 Allocations of IDs and IP addresses for all NEs
T2000
9-1 10.0.0.1 0.0.0.0
9-4 129.9.0.4 0.0.0.0
9-2 129.9.0.2 0.0.0.0
9-3 129.9.0.3 0.0.0.0
3.
Configure NE1, NE2, NE3, and NE4 to transparently transmit bytes D1 to D3.
5.6 Configuration Flow

The configuration of the DCC transparent transmission solution consists of two parts, that is, the configuration at the near end of the NE by using the Web LCT, and the creation of the NE topology on the T2000.
Issue 02 (2009-02-25)
5-9
Figure 5-8 Configuration flow for the DCC transparent transmission solution
Start 1
Set IDs and IP addresses for NEs Configure DCCs for NEs Set DCC transparent transmission
Query ECC routes at the gateway NE
5 Create NEs on the T2000
End
Table 5-2 Description of the configuration flow of the DCC transparent transmission solution Number 1 Description
l
When setting the IP address information for the gateway NE, you may need to set the default gateway in addition to setting the IP address and subnet mask, depending on the situation of the external DCN. For information on configuring the ID of an NE, see 2.7.2 Modifying the NE ID. For information on configuring the IP address information of an NE, see 2.7.3 Modifying the Communication Parameters of an NE. The DCC protocol type of the line port should be set to HW ECC (default value). When the third-party equipment uses bytes D1 to D3 as DCCs, set the DCC channel type of the SDH port to D4-D12. When the third-party equipment uses bytes D4 to D12 as DCCs, set the DCC channel type of the SDH port to D1-D3. For the configuration process, see 2.7.4 Configuring DCCs.
5-10
Issue 02 (2009-02-25)
Number 3
Description
l
Set the DCC transparent transmission bytes used by the third-party equipment for all the NEs on the planned route. For the configuration process, see 2.7.6 Configuring DCC Transparent Transmission. There is an ECC route between the gateway NE and each of its managed non-gateway NEs. For the querying process, see 2.7.7 Querying ECC Routes.

l

This topic provides an example to describe how to configure the DCC transparent transmission solution.
Precautions
NOTE
l l
For the parameters in this example, refer to the example in 5.5 Planning Guide. This example provides only the configurations of the typical NEs: NE1 and NE3.
Procedure
l l
The extended ID of NE1 is 9 and the ID is 1. The extended ID of NE3 is 9 and the ID is 3.
Step 2 Set the IP address information for NE1. See 2.7.3 Modifying the Communication Parameters of an NE. The IP address of NE1 is 10.0.0.1, the subnet mask is 255.255.0.0, and the default gateway is 0.0.0.0 (default value). Step 3 Set DCCs for the NEs. See 2.7.4 Configuring DCCs.
l l l
Set the DCC protocol type of all the line ports of all NEs to HW ECC (default value). Set the DCC channel type of all SDH ports of all NEs to D4-D12. Set the channel type of all PDH microwave ports of all NEs to the default value.
Issue 02 (2009-02-25)
5-11
Step 4 Configure the transparent transmission between bytes D1 to D3 of the west line port of an NE and bytes D1 to D3 of the east line port of the NE. Perform the configuration for all NEs. See 2.7.6 Configuring DCC Transparent Transmission. Step 5 Query ECC routes at NE1. See 2.7.7 Querying ECC Routes. NE1 should have ECC routes to NE2, NE3, and NE4. Step 6 Search and create NEs with 10.1.0.1 as the IP address of the gateway NE. See 2.7.8 Creating NEs by Using the Search Method. All NEs can be successfully created. ----End

This topic describes the alarms and performance events relevant to the DCC transparent transmission solution, and the problems that occur frequently during the application of the solution. 5.8.1 Relevant Alarms and Events When there is a fault in the communication between the T2000 and an NE, the T2000 reports the corresponding alarm. 5.8.2 FAQs This topic lists the problems that occur frequently during the application of the DCC transparent transmission solution.

Relevant Alarms
l
Relevant Events
None.
5-12
Issue 02 (2009-02-25)
5.8.2 FAQs
This topic lists the problems that occur frequently during the application of the DCC transparent transmission solution. 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
This solution requires much less SCC resources because it need not implement complex protocol suites such as IP or OSI protocols. This solution facilitates operation because it incorporates easier data configuration when compared with the other two solutions.
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 does one 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 the third-party equipment to ensure that different vendors use different DCC bytes. Analyze the routes for DCC transparent transmission with the maintenance staff of the third-party equipment. Configure data according to the results and the network planning. Query ECC routes at the gateway NE. If there are no routes to non-gateway NEs, the interconnection fails.
Issue 02 (2009-02-25)
5-13
6 DCC Transparent Transmission Through the External Clock Interface Solution
DCC Transparent Transmission Through the External Clock Interface Solution
About This Chapter

The DCC bytes are placed in a specified E1 and then transmitted through the third-party network by using the DCC transparent transmission through the external clock interface solution. In this case, the transmission bandwidth of one E1 is occupied. Hence, this solution is applied only when the transmission path of NM messages exists in a PDH network or a network that does not support transparent transmission of DCC bytes. 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 way, DCC bytes can be transparently transmitted as long as the third-party network can transmit E1 services. 6.2 Availability The DCC transparent transmission through the external clock interface solution requires the support of the applicable equipment and boards. 6.3 Relation with Other Features If you adopt the DCC transparent transmission through the external clock interface solution to communicate NM messages when the OptiX equipment is used together with the third-party equipment to form a network, you can use any of the HW ECC protocol stack, IP protocol stack, and OSI protocol stack to manage the OptiX equipment. It is recommended that you use the HW ECC protocol stack. 6.4 Realization Principle The OptiX equipment realizes the transparent transmission of DCCs through the external clock interface by using the overhead cross-connect matrix. 6.5 Planning Guide When using the DCC transparent transmission through the external clock interface solution, plan the parameters of a DCN according to the situation of the network. 6.6 Configuration Flow This topic describes the added configuration for the DCC transparent transmission through the external clock interface solution based on the configuration for the HW ECC solution.
6.7 Configuration Example This topic provides an example to describe how to configure the DCC transparent transmission through the external clock interface solution. 6.8 Maintenance Guide This topic describes the alarms and performance events relevant to the DCC transparent transmission through the external clock interface solution, and the problems that occur frequently during the application of the solution.
6-2
Issue 02 (2009-02-25)

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 way, DCC bytes can be transparently transmitted as long as the 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 An NE is directly connected to the third-party network through the external clock interface. Indirect access mode An NE is connected to the third-party network through a 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 network External clock interface DCC bytes E1 cable
OptiX equipment
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 an E1 tributary board, and then configure cross-connections between the E1 service and the line board. Thus, the E1 service is accessed to the third-party network through the SDH interface. The third-party network then transmits the E1 as an ordinary service. Thus, DCC bytes are transparently transmitted between the two NEs.
Figure 6-2 Networking example for the DCC transparent transmission through the external clock interface solution (indirect access mode)
External clock interface E1 port of an E1 tributary board DCC bytes Fiber DCC bytes Fiber External clock interface E1 port of an E1 tributary board
SDH/PDH network
6.2 Availability
The DCC transparent transmission through the external clock interface solution requires the support of the applicable 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 SCC (all the versions) and PXC (all the versions) Applicable Equipment IDU 610/620

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

The OptiX equipment realizes the transparent transmission of DCCs through the external clock interface by using the overhead cross-connect matrix. In the receive direction: 1. The PXC board transmits the E1 service received on the external clock interface as 2.048 Mbit/s overhead signals to the overhead cross-connect matrix of the SCC board through the overhead bus. The overhead cross-connect matrix transports the DCC bytes that the NE uses to the CPU. The CPU processes the NM messages carried by the DCC bytes according to the protocol stack of the DCCs.
2. 3.
In the transmit direction:

1.
The CPU of the SCC board encapsulates the NM messages into the DCC bytes according to the protocol stack and transmits the DCC bytes to the overhead cross-connect matrix of the SCC board. The overhead cross-connect matrix combines the DCC bytes sent from the CPU and other overhead bytes (such as the overhead bytes used by orderwire services and synchronous/ asynchronous data services) to form a 2.048 Mbit/s overhead signal stream, and then transmits the overhead signal stream to the external clock interface. The external clock interface transmits the 2.048 Mbit/s overhead signals as an E1 service to the third-party network.
2.
3.
Figure 6-3 illustrates how an NE transparently transmits DCC bytes through the external clock interface. In this example, DCC bytes D1 to D3 carry the NM messages. Figure 6-3 Realization principle of the DCC transparent transmission through the external clock interface
External clock interface Overhead bus PXC board
Overhead crossconnect matrix D1-D3 CPU
SCC board
6.5 Planning Guide

When using the DCC transparent transmission through the external clock interface solution, plan the parameters of a DCN according to the situation of the network.
Prerequisite
Precautions
This guide provides the planning information for the DCC transparent transmission through the external clock interface solution based on the planning principles for the HW ECC solution. For the planning principles for the HW ECC solution, see 2.6 Planning Guide.
Procedure
Step 1 Plan the access mode.
l
When the OptiX equipment interconnects with the third-party network through E1 interfaces, adopt the direct access mode.
Issue 02 (2009-02-25)

l
When the OptiX equipment interconnects with the third-party network through other service interfaces, adopt the indirect access mode.
Step 2 Plan the DCC bytes that carry NM messages. Any two NEs that use the third-party network to transparently transmit DCC bytes must use the same DCC bytes. It is recommended that the NEs use DCC bytes D1 to D3. Step 3 Plan the transmission route of the E1 service that carries DCC bytes in the third-party network. In the case of the indirect access mode, you need to plan the ports and line timeslots for the E1 service. ----End
Example
Figure 6-4 Networking example for the DCC transparent transmission through the external clock interface solution
NE1 T2000
NE2
NE3 OptiX transmission equipment Third-party transmission equipment
NE4
Network cable Radio link
E1 cable Fiber
Figure 6-4 shows a transmission network that comprises the OptiX equipment and the thirdparty equipment. The third-party network provides NE1 with SDH optical interfaces and provides NE2 with E1 interfaces. The planning steps are as follows: 1. Plan the access mode. In the case of NE1, adopt the indirect access mode. In the case of NE2, adopt the direct access mode. 2. 3. Plan the DCC bytes that carry NM messages. NE1 and NE2 use bytes D1 to D3 to transmit NM messages. Plan the transmission route of the E1 service that carries DCC bytes in the third-party network.
6-6
In the case of NE1, connect the external clock interface of the PXC board in slot 1 (that is, 1-PXC-1) to E1 port 1 of the PO1 board in slot 4, and configure an E1 service from E1 port 1 to the external clock interface of NE2. The E1 service occupies VC-12 timeslot 1 of the SL1 board in slot 6 of NE1. The SL1 board in slot 6 is connected to the SDH interface of the third-party network.
6.6 Configuration Flow

This topic describes the added configuration for the DCC transparent transmission through the external clock interface solution based on the configuration for the HW ECC solution. Figure 6-5 Configuration flow for the DCC transparent transmission through the external clock interface solution
Start 1
Configure a DCC for the external clock interface
Is the indirect access mode used? Yes 2 Configure a cross-connection for the E1 service
No
End
Table 6-2 Description of the configuration flow of the DCC transparent transmission through the external clock interface solution Number 1 Description
l l l l
Set Enabled/Disabled of the used external clock interface to Enabled. It is recommended that you set Channel Type to D1-D3 (default value). It is recommended that you set Protocol Type to HW ECC (default value). For the configuration process, see 2.7.4 Configuring DCCs.
Create a bidirectional cross-connection between the specified timeslot of the E1 port that is connected to the external clock interface and the specified timeslot of the service port that is connected to the third-party network according to the planning information.
Issue 02 (2009-02-25)

This topic provides an example to describe how to configure the DCC transparent transmission through the external clock interface solution.
Precautions
NOTE
l l
For the parameters in this example, see the example in 6.5 Planning Guide. This example provides only the added configuration data for the DCC transparent transmission through the external clock interface solution based on the configuration data for the HW ECC solution.
Procedure
Step 1 Modify the DCC parameters of the 1-PXC-1 ports of NE1 and NE2. See 2.7.4 Configuring DCCs.
l l l
Set Enabled/Disabled to Enabled. Set Channel Type to D1-D3 (default value). Set Protocol Type to HW ECC (default value).
Step 2 Create a bidirectional cross-connection between E1 port 1 of the PO1 board in slot 4 of NE1 and VC-12 timeslot 1 of the SL1 board in slot 6 of NE1. ----End

This topic describes the alarms and performance events relevant to the DCC transparent transmission through the external clock interface solution, and the problems that occur frequently during the application of the solution. 6.8.1 Relevant Alarms and Events When there is a fault in the communication between the T2000 and an NE, the T2000 reports the corresponding alarm. 6.8.2 FAQs This topic lists the problems that occur frequently during the application of the DCC transparent transmission through the external clock interface solution.

Relevant Alarms
l
6-8
Issue 02 (2009-02-25)

l
Relevant Events
None.
6.8.2 FAQs
This topic lists the problems that occur frequently during the application of the DCC transparent transmission through the external clock interface solution. 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 ranges from 50 meters to 100 meters), use the extended ECC solution, that is, use a network cable to connect the Ethernet NM ports or NE cascading ports of the two NEs. When the distance between the two NEs exceeds the maximum transmission distance of a network cable but is less than the transmission distance of an E1 cable (the maximum transmission distance of an E1 cable is 300 meters), use the DCC transparent transmission through the external clock interface solution. This is because the extended ECC consumes much less system resources than the DCC transparent transmission through the external clock interface. Q: Can the external clock interface be used to transparently transmit orderwire overhead bytes when the DCC transparent transmission through the external clock interface solution is already applied? A: Yes, the external clock interface can be used to transparently transmit orderwire bytes when the DCC transparent transmission through the external clock interface solution is already applied. This is because the DCC bytes occupy only certain timeslots of the E1 service that is transmitted by the external clock interface. Hence, the other timeslots of the E1 service can be used to transparently transmit the overhead bytes used by orderwire calls, asynchronous data interface services, and synchronous data interface services. Q: Why does the configuration of the DCC transparent transmission through the external clock interface solution fail? A: Common causes are as follows:
l l
The external clock source mode or the external clock output mode is modified to 2 MHz. The wayside E1 service is configured.
Issue 02 (2009-02-25)
6-9
7 1+1 HSB
7
About This Chapter
7.1 Feature Description This topic describes the 1+1 HSB protection through its application.
1+1 HSB
1+1 HSB is a configuration mode of 1+1 protection. 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 by using the 1+1 HSB.
7.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the 1+1 HSB feature. 7.3 Availability The 1+1 HSB feature requires the support of the applicable equipment and boards. 7.4 Relation with Other Features The 1+1 HSB protection is related to the microwave work mode, 1+1 FD protection, 1+1 SD protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave. 7.5 Realization Principle The realization principle of the 1+1 HSB for the Hybrid microwave is different from the realization principle of the 1+1 HSB for the SDH/PDH microwave. 7.6 Planning Guide In the case of the radio links whose transmission performance is slightly affected by multipath fading, it is recommended that you adopt the 1+1 HSB protection configuration. 7.7 Configuration Guide The method for configuring the 1+1 HSB/FD/SD feature on the IDU 620 is different from the method for configuring the 1+1 HSB/FD/SD feature on the IDU 605 2B/2F. 7.8 Maintenance Guide This topic describes how to carry out the IF 1+1 protection switching, relevant alarms and events, and the problems that occur frequently during the application of the protection feature.
Issue 02 (2009-02-25)
7-1
7 1+1 HSB

This topic describes the 1+1 HSB protection through its application. Figure 7-1 shows application of the 1+1 HSB protection. Figure 7-1 1+1 HSB protection
Main channel Main channel
MODEM Service MODEM
Transmitter
Transmitter
MODEM Service
Transmitter
Transmitter
MODEM
Standby channel
Standby channel
In the case of the 1+1 HSB protection configuration, the main channel of the transmit end transmits the RF signal to the opposite end. the main channel and standby channel of receive end received the same RF signal respectively. When the main channel if faulty, the service unit of receive end receives the signal from the standby channel. In this manner, the protection switching is realized.
7.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the 1+1 HSB feature. 7.2.1 System Configuration The IDU 620 and IDU 605 2B/2F support the configuration of the 1+1 HSB protection. 7.2.2 Protection Type The 1+1 HSB protection is classified into the revertive mode and the non-revertive mode. 7.2.3 Switching Conditions The switching priority varies according to the switching condition. 7.2.4 Switching Impact The services are interrupted within the 1+1 HSB switching time (shorter than 500 ms).
7.2.1 System Configuration

The IDU 620 and IDU 605 2B/2F support the configuration of the 1+1 HSB protection.
Configuration of the IDU 620

The IDU 620 supports one or two 1+1 HSB protection groups. One 1+1 HSB protection group occupies one channel and consists of the following:

l l l
7 1+1 HSB
Two IF boards Two ODUs that are of the same type One antenna (with one hybrid coupler)
NOTE
l l
The IF board can be the IF0A board, IF0B board, IF1A board, IF1B board, IFH2 board or IFX board. The two IF boards that are in a 1+1 HSB protection group must work in the same radio work mode. The hybrid coupler can be balanced or unbalanced. Generally, the unbalanced hybrid coupler is used.
Figure 7-2 provides a typical configuration of one 1+1 HSB protection group on the IDU 620. Figure 7-2 Typical configuration of one 1+1 HSB protection group (IDU 620)
ODU
Hybrid coupler
Antenna
ODU
EXT IF FAN
Slot 20
Slot 7 Slot 5 Slot 3 Slot 1
EXT EXT EXT PH1 SCC
EXT IF PXC PXC

IDU 620
Configuration of the IDU 605 2B/2F

The IDU 605 2B/2F supports one 1+1 HSB protection group. One 1+1 HSB protection group occupies one channel and consists of the following:
l l l
One IDU 605 2B/2F Two ODUs that are of the same type One antenna (with one hybrid coupler)
NOTE
The hybrid coupler can be balanced or unbalanced. Generally, the unbalanced hybrid coupler is used.
Figure 7-3 provides a typical configuration of one 1+1 HSB protection group on the IDU 605 2B/2F.
Issue 02 (2009-02-25)
7-3
7 1+1 HSB
Figure 7-3 Typical configuration of one 1+1 HSB protection group (IDU 605 2B/2F)
ODU Hybrid coupler
Antenna
ODU
IDU 605 2B/2F
7.2.2 Protection Type

The 1+1 HSB protection is classified into the revertive mode and the non-revertive mode.
l
Revertive mode When an NE is in the switching state, the NE releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. The period from the time the former working channel is restored to normal to the time the NE releases the switching is called the wait to restore (WTR) time. To prevent frequent switching events due to an unstable working channel, it is recommended that you set the WTR time to five to twelve minutes.
Non-revertive mode When an NE is in the switching state, the NE keeps the current state unchanged unless another switching occurs even though the former working channel is restored to normal.
7.2.3 Switching Conditions

The switching priority varies according to the switching condition. Table 7-1 Switching conditions of the 1+1 HSB protection 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.
7-4
Issue 02 (2009-02-25)
7 1+1 HSB
Switching Condition Lockout switching (external switching)
Priority
Description In any state, a switching enters the lockout state. In the lockout state, no switching occurs until the lockout switching is cleared. If a 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 enters the forced switching state. If a 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 main board to the standby board. The switching then enters the automatic switching state. For the trigger conditions of the automatic switching, see Table 7-2.
Forced switching (external switching)
The main equipment is faulty.
Issue 02 (2009-02-25)
7-5
7 1+1 HSB
Switching Condition Reverse switching (valid only when the reverse switching is enabled)
Priority
Description When both the main IF board and the standby IF board at the sink end report service alarms, and send the alarms to the source end by using the MWRDI overhead in the microwave frame. If the source end is in the lockout switching state or in the 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 action occurs. The timer duration is the WTR time (in the revertive mode) or five minutes (in the non-revertive mode). After the reverse switching, the switching enters the RDI state. If a 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 enters the manual switching state.
Manual switching (external switching)
7-6
Issue 02 (2009-02-25)
7 1+1 HSB
Switching Condition Revertive switching (valid only in the revertive mode)
Priority
Description When the switching is in the automatic switching state and the former main equipment is already restored to normal for the WTR time, a revertive switching occurs. From the time the former main equipment is restored to normal to the time the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching enters the normal state.
Table 7-2 Trigger conditions of the automatic 1+1 HSB switching Switching Condition The hardware of the IF board or the IF unit is faulty. The hardware of the ODU is faulty. POWER_FAIL VOLT_LOS (IF board) RADIO_TSL_HIGH RADIO_TSL_LOW RADIO_RSL_HIGH TIF_INPWR_ABN CONFIG_NOSUPPOR R_LOC R_LOF R_LOS MW_LOF MW_RDI At the same priority Priority
7.2.4 Switching Impact

The services are interrupted within the 1+1 HSB switching time (shorter than 500 ms).
Issue 02 (2009-02-25)
7-7
7 1+1 HSB
7.3 Availability
The 1+1 HSB feature requires the support of the applicable equipment and boards. Table 7-3 Availability of the 1+1 HSB feature Feature Applicable Board IF0A/IF0B (all the versions) 1+1 HSB IF1A/IF1B (all the versions) IFX (all the versions) IFH2 (all the versions) IDU 620 Applicable Equipment IDU 605 2B/2F

The 1+1 HSB protection is related to the microwave work mode, 1+1 FD protection, 1+1 SD protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave.
l l
The 18)2E1,3.5MHz,QPSK work mode does not support 1+1 HSB protection. 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. Therefore, the four IF boards in two XPIC working groups can form two 1+1 HSB protection groups. The IF boards in a 1+1 HSB protection group cannot be configured to provide the N+1 protection. The radio link with the 1+1 HSB configuration can work only as the service sink of an SNCP service pair, and cannot work as the working source or the protection source. The Hybrid microwave supports the 1+1 HSB protection.

The realization principle of the 1+1 HSB for the Hybrid microwave is different from the realization principle of the 1+1 HSB for the SDH/PDH microwave. 7.5.1 SDH/PDH Microwave This topic considers the IDU 620 that is configured with one 1+1 HSB protection group as an example to describe the principle of the 1+1 HSB protection switching for the SDH/PDH microwave. 7.5.2 Hybrid Microwave This topic considers the IDU 620 that is configured with one 1+1 HSB protection group as an example to describe the principle of the 1+1 HSB protection switching for the Hybrid microwave.
7 1+1 HSB
7.5.1 SDH/PDH Microwave

This topic considers the IDU 620 that is configured with one 1+1 HSB protection group as an example to describe the principle of the 1+1 HSB protection switching for the SDH/PDH microwave.
Before the Switching

Figure 7-4 1+1 HSB realization principle (before the switching, in the transmit direction)
Main ODU Main Cross-connect IF board board Service board
Antenna
Hybrid coupler
Standby ODU
Standby IF board
In the transmit direction: 1. 2. 3. 4. The service board sends the received service signal to the cross-connect board. The cross-connect board transmits the service signal to both the main IF board and the standby IF board. The main IF board and the standby IF board send the processed analog IF 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 mutes (that is, the standby ODU does not send the RF signal).
Figure 7-5 1+1 HSB realization principle (before the switching, in the receive direction)
Antenna
Hybrid coupler
Standby ODU
Standby IF board
In the receive direction: 1. The hybrid coupler splits the RF signal received from the antenna to two signals and sends them to both the main ODU and the standby ODU.
Issue 02 (2009-02-25)
7 1+1 HSB
2. 3. 4. 5.
The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively. The main IF board and the standby IF board send the service signal to the cross-connect board. The cross-connect board selects the service signal from the main IF board and sends the signal to the service board. The service board sends the service signal to the equipment at the opposite end.
After the Switching

Figure 7-6 1+1 HSB realization principle (after the switching, in the receive direction)
Antenna
Hybrid coupler
Standby ODU
Standby IF board
Figure 7-7 1+1 HSB realization principle (after the switching, in the transmit direction)
Antenna
Hybrid coupler
Standby ODU
Standby IF board
After a 1+1 HSB switching:

l
In the receive direction, the cross-connect board selects the service signal from the standby IF board. In the transmit direction, the standby ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The main ODU mutes (that is, the main ODU does not send the RF signal).
NOTE
In the case of the IDU 605 2B/2F, the multiplexing sub-unit that is embedded in the IF unit replaces the crossconnect unit of the IDU 620 to realize the dual fed and selective receiving function.
7-10
Issue 02 (2009-02-25)
7 1+1 HSB
7.5.2 Hybrid Microwave

This topic considers the IDU 620 that is configured with one 1+1 HSB protection group as an example to describe the principle of the 1+1 HSB protection switching for the Hybrid microwave.

Figure 7-8 1+1 HSB realization principle (before the switching, in the transmit direction)
Main ODU Main IF board Cross-connect board Service board
Hybrid coupler Antenna
Standby ODU
Standby IF board
EMS6 board
In the transmit direction: 1. 2. 3. The service board multiplexes the received E1 service signal into the VC-4 and then sends the VC-4 to the cross-connect board. The cross-connect board transmits the E1 service signal tin the VC-4 o the main IF board and the standby IF board. The Ethernet service port of the main IF board is in LinkUp state, whereas the Ethernet service port of the standby IF board is in LinkDown state. The Ethernet board EMS6 transmits the Ethernet service to the Ethernet service port of the main IF board through the LAG function. The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service signal into the Hybrid microwave frame. The MUX unit of the standby IF board multiplexes the E1 service signal and Ethernet service signal into the non-standard Hybrid microwave frame. The IF processing units of the main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by their corresponding IF board and modulate the Hybrid microwave frame into the analog IF signal. Then, the IF processing units of the main IF board and the standby IF board send the analog IF signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal to the 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).
4.
5.
6.
Issue 02 (2009-02-25)
7-11
7 1+1 HSB
Figure 7-9 1+1 HSB realization principle (before the switching, in the receive direction)
Main ODU Hybrid coupler Antenna Main IF board Cross-connect board Service board
Standby ODU
Standby IF board
EMS6 board
In the receive direction: 1. 2. 3. 4. The hybrid coupler splits the RF signal received from the antenna into two signals and sends them to the main ODU and the standby ODU. The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively. The main IF board and the standby IF board demodulate the Hybrid frame from the IF signal. The MUX units of the main IF board and the standby IF board receive the Hybrid frame that is demultiplexed from their corresponding IF board and then separate the Hybrid frame into the E1 service signal and Ethernet service signal. The E1 service signal is transmitted to the cross-connect board after being multiplexed into the VC-4. The Ethernet service signal is transmitted to the Ethernet service port of the IF board. The cross-connect board receives the E1 service signal from the main IF board and crossconnects the service signal to the corresponding service board. The EMS6 board receives the Ethernet service signal from the main IF board because the Ethernet service port of the main IF board is in LinkUp state whereas the Ethernet service port of the standby IF board is in LinkDown state.
5.
6. 7.
7-12
Issue 02 (2009-02-25)
7 1+1 HSB
After the Switching

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

l
In the receive direction: The analog IF signal received at the standby IF board is separated into the E1 service signal and Ethernet service signal by the MUX unit. The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. The cross-connect board and the EMS6 board receive the service signal from the standby IF board.
In the transmit direction: The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. The IF processing units of the main IF board and the standby IF board modulate the Hybrid microwave frame that is multiplexed by the MUX unit of their corresponding IF board into the analog IF signal. The main IF board and
Issue 02 (2009-02-25)
7-13
7 1+1 HSB
the standby IF board send the analog IF signal to the main ODU and the standby ODU. The standby ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The main ODU is muted (that is, the main ODU does not transmit the RF signal).
NOTE
The two built-in IF units of the IDU 605 2F realize the functions of two IF boards of the IDU 620.
7.6 Planning Guide

In the case of the radio links whose transmission performance is slightly affected by multipath fading, it is recommended that you adopt the 1+1 HSB protection configuration.
Procedure
Plan the parameters relevant to the protection configuration.
l
If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the value to ten minutes. It is recommended that you enable the reverse switching. If reverse switching is enabled, and both the main IF board and the standby IF board at the sink end report a service alarm, a reverse switching occurs at the source end. In the case of the IDU 620, although the 1+1 HSB protection has no restriction on the slot of the IF board, it is recommended that you install a pair of main and standby IF boards in slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is the main board). In the case of the IDU 605 2B/2F, the active/standby relation of the IF unit is fixed. Hence, planning is not required.
----End

The method for configuring the 1+1 HSB/FD/SD feature on the IDU 620 is different from the method for configuring the 1+1 HSB/FD/SD feature on the IDU 605 2B/2F. 7.7.1 Creating IF 1+1 Protection In the case of the IDU 620, if the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1+1 protection group. 7.7.2 Modifying the Parameters of IF 1+1 Protection In the case of the IDU 605 2B/2F, the system automatically creates a 1+1 HSB protection group. The working mode and other parameters of the protection group can be modified.
7.7.1 Creating IF 1+1 Protection

In the case of the IDU 620, if the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1+1 protection group.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher.
7 1+1 HSB
The IF boards and their corresponding ODUs that form the IF 1+1 protection must be included in the NE Panel.
Background Information
When a 1+0 service is converted into a 1+1 service by configuring the 1+1 protection, the original services are not interrupted.
Precautions
The 18)2E1,3.5MHz,QPSK work mode does not support IF 1+1 protection. The following procedures consider the operation of the Web LCT as an example.
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 New. The system displays the Create IF 1+1 Protection dialog box. Step 3 Set the parameters of the IF 1+1 protection group.
Issue 02 (2009-02-25)
7-15
7 1+1 HSB
Parameters
Parameter Protection Group ID Value Range 1, 2 Default Value Description
l
If only one IF 1+1 protection group is to be created, it is recommended that you set Protection Group ID to 1. If two IF 1+1 protection groups are to be created, it is recommended that you set the Protection Group ID of the protection group that is formed by the IF boards in slots 5 and 7 to 1 and the Protection Group ID of the protection group that is formed by the IF boards in slots 6 and 8 to 2. In the 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. In the 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The remote end selects signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. In the 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced. The 1+1 FD protection mode and 1+1 SD protection mode are compatible with the 1+1 HSB switching function. Set this parameter according to the planning information.
Working Mode
HSB, FD, SD
HSB
7-16
Issue 02 (2009-02-25)
7 1+1 HSB
Parameter Revertive Mode
Value Range Revertive, NonRevertive
Default Value Revertive
Description
l
When this parameter is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. 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 use the default value. This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value. When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. When this parameter at the source end is set to Enable and the reverse switching conditions are met, the IF 1+1 protection switching occurs at the source end. This parameter is valid only when Working Mode is set to HSB or SD. It is recommended that you use the default value. In the 1+1 FD/SD mode, two IF boards should be installed as a pair in slots 5 and 7 (the IF board in slot 5 is recommended to be the main board) or in slots 6 and 8 (the IF board in slot 6 is recommended to be the main board). In the 1+1 HSB mode, the IF boards can be installed in slots 58. It is recommended that you install two IF boards in a pair in slots 5 and 7 (the IF board in slot 5 is the main board) or in
WTR Time (s)
300 to 720
600
Enable Reverse Switching
Enable, Disable
Enable
Working Board
IF ports
Issue 02 (2009-02-25)
7-17
7 1+1 HSB
Parameter Protection Board
Value Range
Default Value
Description slots 6 and 8 (the IF board in slot 6 is the main board).
NOTE
The parameters Working Mode, Revertive Mode, WTR Time (s), and Enable Reverse Switching must be set to the same values at both ends of a radio link hop.
Postrequisite
l
In the case of the 1+1 HSB protection and 1+1 SD protection, you need to configure the IF/ODU information of the active microwave link later. The standby microwave link automatically copies the related information of the active microwave link except the transmission status of the ODU. In the case of the 1+1 FD protection, you need to configure the IF/ODU information of the active microwave link and the information of the standby ODU later. The standby microwave link automatically copies the IF information of the active microwave link.
NOTE
The default transmission status of an ODU is Unmute. Hence, you do not need to configure the transmission status of the standby ODU after you create an IF 1+1 protection group.
7.7.2 Modifying the Parameters of IF 1+1 Protection

In the case of the IDU 605 2B/2F, the system automatically creates a 1+1 HSB protection group. The working mode and other parameters of the protection group can be modified.
Prerequisite
In the case of the IDU 605 2B/2F, the board installed in slot 8 is always the active IF board (this board corresponds to IF port "ODU-M" on the front panel of the IDU 605 2B/2F), and the board installed in slot 7 is always the standby IF board (this board corresponds to IF port "ODU-S" on the front panel of the IDU 605 2B/2F).
Precautions
The following procedures consider the operation of the Web LCT as an example.
7 1+1 HSB
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF 1+1 Protection tab. Step 3 Modify the parameters of the IF 1+1 protection.
Parameters
Parameter Working Mode Value Range HSB, FD, SD Default Value HSB Description
l
In the 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. In the 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The opposite end selects signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. In the 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced. The 1+1 FD protection mode and 1+1 SD protection mode are compatible with the 1+1 HSB switching function. Set this parameter according to the planning information.
Issue 02 (2009-02-25)
7-19
7 1+1 HSB
Description
l
When this parameter is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. 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 use the default value. This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value. When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. When this parameter at the source end is set to Enable and the reverse switching conditions are met, the IF 1+1 protection switching occurs at the source end. This parameter is valid only when Working Mode is set to HSB or SD. It is recommended that you use the default value.
WTR Time(s)
300 to 720
Enable, Disable
Enable
NOTE
Each of the following parameters should be set to the same value at the two ends of a microwave link: Working Mode, Revertive Mode, WTR Time (s), and Enable Reverse Switching.
Postrequisite
l
In the case of the 1+1 HSB protection and 1+1 SD protection, you need to configure the IF/ODU information of the active microwave link later. The standby microwave link automatically copies the related information of the active microwave link except the transmission status of the ODU.
7-20
Issue 02 (2009-02-25)

l
7 1+1 HSB
In the case of the 1+1 FD protection, you need to configure the IF/ODU information of the active microwave link and the information of the standby ODU later. The standby microwave link automatically copies the IF information of the active microwave link.
NOTE

This topic describes how to carry out the IF 1+1 protection switching, relevant alarms and events, and the problems that occur frequently during the application of the protection feature. 7.8.1 IF 1+1 Protection Switching The IF 1+1 protection switching is an important maintenance operation. 7.8.2 Relevant Alarms and Events When a 1+1 HSB switching occurs on IF boards, the system reports corresponding alarms and abnormal events. 7.8.3 FAQs This topic lists the problems that occur frequently during the application of the 1+1 HSB protection.
7.8.1 IF 1+1 Protection Switching

The IF 1+1 protection switching is an important maintenance operation.
Prerequisite
l l
An IF 1+1 protection group must be configured. The user must have the system level authority.
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 IF 1+1 Protection tab. Step 3 In Slot Mapping Relation, select the working unit or the protection unit of a protection group. Right-click on the selected unit and select the required switching mode from the displayed menu. The system displays a prompt dialog box. Step 4 Click Yes. The system displays a prompt dialog box indicating that the command is successfully issued. Step 5 Click OK. Step 6 Click Query. ----End
Issue 02 (2009-02-25)
7-21
7 1+1 HSB

When a 1+1 HSB switching occurs on IF boards, the system reports corresponding alarms and abnormal events.
Relevant Alarms
l
HSB_INDI (IDU 620) The HSB_INDI alarm indicates that the microwave equipment is switched. RPS_INDI (IDU 605 2B/2F) The RPS_INDI alarm indicates the microwave protection switching.
Relevant Abnormal Events

l
IF 1+1 protection switching This abnormal event indicates that the IF 1+1 protection switching occurs.
7.8.3 FAQs
This topic lists the problems that occur frequently during the application of the 1+1 HSB protection. Q: What states does the 1+1 HSB protection group have? A: The 1+1 HSB protection group has the following states:
l
Normal The state when no switching occurs or the state after a switching is cleared Automatic The state after a switching is triggered by an equipment fault Forced The state after a forced switching Manual The state after a manual switching Lockout The state after a lockout switching RDI The state after a reverse switching WTR The state that exists from the time the former active equipment is restored to normal to the time the revertive switching occurs in the revertive mode
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.
7-22
Issue 02 (2009-02-25)
7 1+1 HSB
Q: Why does the configuration of the 1+1 HSB protection fail? 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. The IF board functions as the working source or the protection source of the SNCP service.
l l
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. Q: In the case of the 1+1 HSB, how much is the difference between the RSL of the main link and the RSL of the standby link? A: An error of 2 dB exists between the RSL reported by the ODU and the actual RSL of the ODU. Hence, when different types of hybrid couplers are used in the 1+1 HSB configuration, the possible conditions are as follows:
l
When the unbalanced hybrid coupler is used, the insertion loss of the main link is 1.80.1 dB and the insertion loss of the standby link is 6.50.5 dB. Consider the difference between
Issue 02 (2009-02-25)
7 1+1 HSB
the RSL reported by the ODU and the actual RSL of the ODU. The difference between the RSL of the main link and the RSL of the standby link may be 0.1 dB to 9.3 dB.
l
When the balanced hybrid coupler is used, the insertion loss of the main link and the standby link is 3.30.5 dB. Consider the difference between the RSL reported by the ODU and the actual RSL of the ODU. The difference between the RSL of the main link and the RSL of the standby link may be 0 dB to 5 dB.
7-24
Issue 02 (2009-02-25)
8 1+1 FD
8
About This Chapter
8.1 Feature Description This topic describes the 1+1 FD protection through its application.
1+1 FD
1+1 FD is a configuration mode of 1+1 protection. In the 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 signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced.
8.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the 1+1 FD feature. 8.3 Availability The 1+1 FD feature requires the support of the applicable equipment and boards. 8.4 Relation with Other Features The 1+1 FD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave. 8.5 Realization Principle The realization principle of the 1+1 FD for the Hybrid microwave is different from the realization principle of the 1+1 FD for the SDH/PDH microwave. 8.6 Planning Guide If there are sufficient spectrum resources, it is recommended that you adopt the 1+1 FD protection configuration. 8.7 Configuration Guide The method for configuring the 1+1 HSB/FD/SD feature on the IDU 620 is different from the method for configuring the 1+1 HSB/FD/SD feature on the IDU 605 2B/2F. 8.8 Maintenance Guide This topic describes how to carry out the IF 1+1 protection switching, relevant alarms and events, and the problems that occur frequently during the application of the protection feature.
Issue 02 (2009-02-25)
8-1
8 1+1 FD

This topic describes the 1+1 FD protection through its application. Figure 8-1 shows the application of the 1+1 FD protection. Figure 8-1 1+1 FD protection
Main channel Main channel
MODEM
Transmitter F1 F1 F2
Transmitter
MODEM
Service MODEM Transmitter
F2
Service Transmitter MODEM
Standby channel
Standby channel
In the case of the 1+1 FD protection configuration, the main channel and the standby channel of the receive end receive RF signals of different frequencies which from the transmit end respectively. When the quality of the microwave signal received by the main antenna is degraded, bit errors occur in the service on the main channel. The service unit then receives the service signal from the standby channel to protect the service. In addition, the 1+1 FD protection supports the 1+1 HSB protection switching.
8.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the 1+1 FD feature. 8.2.1 System Configuration The IDU 620 and IDU 605 2B/2F support the configuration of the 1+1 FD protection. 8.2.2 Protection Type The 1+1 FD protection is classified into the revertive mode and the non-revertive mode. 8.2.3 Switching Conditions The 1+1 FD protection supports two types of switching: HSB switching and HSM switching. The two types of switching have different trigger conditions. 8.2.4 Switching Impact In the case of the HSB switching, the services are interrupted within the HSB switching time (shorter than 500 ms). In the case of the HSM switching, the services are not affected because it is a hitless switching.

The IDU 620 and IDU 605 2B/2F support the configuration of the 1+1 FD protection.
8 1+1 FD

The IDU 620 supports one or two 1+1 FD protection groups. One 1+1 FD protection group occupies two channels and consists of the following:
l l l
Two IF boards Two ODUs One antenna (with one balanced hybrid coupler) or two antennas
NOTE
l l
The IF board can be the IF0A board, IF0B board, IF1A board, IF1B board, IFH2 board, or IFX board. The two IF boards that are in a 1+1 FD protection group must work in the same radio work mode. 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 installed with one balanced hybrid coupler. Otherwise, use two antennas.
Figure 8-2 and Figure 8-3 provide two typical configurations of one 1+1 FD protection group on the IDU 620. Figure 8-2 Typical configuration 1 of one 1+1 FD protection group (IDU 620)
ODU
Hybrid coupler
Antenna
ODU
EXT IF FAN
Slot 20
EXT EXT EXT PH1 SCC
EXT IF PXC PXC

IDU 620
Issue 02 (2009-02-25)
8-3
8 1+1 FD
Figure 8-3 Typical configuration 2 of one 1+1 FD protection group (IDU 620)
ODU
Antenna
ODU
Antenna
EXT IF FAN
Slot 20
EXT EXT EXT PH1 SCC
EXT IF PXC PXC

IDU 620

The IDU 605 2B/2F supports one 1+1 FD protection group. One 1+1 FD protection group occupies two channels and consists of the following:
l l l
One IDU 605 2B/2F Two ODUs One antenna (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 installed with one balanced hybrid coupler. Otherwise, use two antennas.
Figure 8-4 and Figure 8-5 provide two typical configurations of one 1+1 FD protection group on the IDU 605 2B/2F.
8-4
Issue 02 (2009-02-25)
8 1+1 FD
Figure 8-4 Typical configuration 1 of one 1+1 FD protection group (IDU 605 2B/2F)
ODU Hybrid coupler
Antenna
ODU
IDU 605 2B/2F
Figure 8-5 Typical configuration 2 of one 1+1 FD protection group (IDU 605 2B/2F)
Antenna
ODU
Antenna
ODU
IDU 605 2B/2F

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 enables the former working channel to return to the normal state some time after the former working channel
Issue 02 (2009-02-25)
8-5
8 1+1 FD
is restored to normal. The period from the time the former working channel is restored to normal to the time the NE releases the switching is called the wait to restore (WTR) time. To prevent frequent switching events due to an unstable working channel, it is recommended that you set the WTR time to five to twelve minutes.
l
NOTE
Both the revertive mode and non-revertive mode are relevant only to the HSB switching (switching at the equipment side). In the case of the HSM switching (switching at the channel side), regardless of whether the revertive mode is set to revertive or non-revertive, the IF board attempts to perform a revertive switching every two minutes after an HSM switching.

The 1+1 FD protection supports two types of switching: HSB switching and HSM switching. The two types of switching have different trigger conditions.
HSB Switching Condition

The HSB switching is the switching that occurs at the equipment side. The equipment-side switching has the same switching action and switching impact as the 1+1 HSB switching but has different trigger conditions. Table 8-1 HSB switching conditions of the 1+1 FD protection Switching Condition Clear switching (external switching) Lockout 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, a switching enters the lockout state. In the lockout state, no switching occurs until the lockout switching is cleared. If a 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 enters the forced switching state.
8-6
Issue 02 (2009-02-25)
8 1+1 FD
Switching Condition The main equipment is faulty.
Priority
Description If a 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 main board to the standby board. The switching then enters the automatic switching state. For the trigger conditions of the automatic switching, see Table 8-2. If a switching is in the lockout or forced switching state, or if the current standby equipment is faulty, no switching occurs. Otherwise, the system switches services from the 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. When the switching is in the automatic switching state and the former main equipment is already restored to normal for a period lasting for the WTR time, the revertive switching occurs. From the time the former main equipment is restored to normal to the time the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching enters the normal state.
Revertive switching (valid only in the revertive mode)
Table 8-2 Trigger conditions of the automatic HSB switching Switching Condition The hardware of the IF board is faulty. The hardware of the ODU is faulty. Description At the same priority
Issue 02 (2009-02-25)
8-7
8 1+1 FD
Switching Condition POWER_FAIL VOLT_LOS (IF board) RADIO_TSL_HIGH RADIO_TSL_LOW RADIO_RSL_HIGH IF_INPWR_ABN CONFIG_NOSUPPORT MW_LOF MW_RDI R_LOC The IF connection cable is faulty.
Description
HSM Switching Condition

The HSM switching is the switching that occurs at the channel side. The channel-side switching is available in the following types:
l
Forced switching The forced switching refers to the HSM switching that occurs at the same time the HSB switching occurs. 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 by a service alarm. After the automatic switching, the IF board receives the baseband signal sent from its paired IF board. Table 8-3 Trigger conditions of the automatic HSM switching Switching Condition R_LOC R_LOF R_LOS MW_LOF MW_FECUNCOR B1_SD (when the IF board of the IDU 620 works in the PDH mode) B2_SD (when the IF board of the IDU 620 works in the SDH mode) Medium Low Priority High
8-8
Issue 02 (2009-02-25)
8 1+1 FD
Switching Condition MW_BER_SD (IDU 605 2B/2F)
Priority
NOTE
The trigger conditions of the automatic HSM switching are classified into three grades: high, medium, and low. If both the main IF board and the standby IF board have a service alarm, the switching occurs only when the alarm in the main IF board has a higher priority than the alarm in the standby IF board. For example, if the main IF board has the MW_FECUNCOR alarm and the standby IF board has the B2_SD alarm, the switching occurs. If both the main IF board and the standby IF board have only the MW_FECUNCOR alarm, no switching occurs.
l
Revertive switching After an automatic HSM switching, the IF board attempts to perform a revertive switching every two minutes. If there is no service alarm on the working channel at this time, the IF board releases the switching.

In the case of the HSB switching, the services are interrupted within the HSB switching time (shorter than 500 ms). In the case of the HSM switching, the services are not affected because it is a hitless switching.
8.3 Availability
The 1+1 FD feature requires the support of the applicable equipment and boards. Table 8-4 Availability of the 1+1 FD feature Feature 1+1 FD Applicable Board IF0A/IF0B (all the versions) IF1A/IF1B (all the versions) IFX (all the versions) IFH2 (all the versions) IDU 620 Applicable Equipment IDU 605 2B/2F

The 1+1 FD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave.
l l
The 18)2E1,3.5MHz,QPSK work mode does not support 1+1 FD protection. 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
Issue 02 (2009-02-25)
8 1+1 FD
into one 1+1 FD protection group. Therefore, the four IF boards in two XPIC working groups can form two 1+1 FD protection groups.
l
The IF boards in a 1+1 FD protection group cannot be configured to provide the N+1 protection. The radio link with the 1+1 FD configuration can work only as the service sink of an SNCP service pair, and cannot work as the working source or the protection source. The Hybrid microwave supports the 1+1 FD protection.

The realization principle of the 1+1 FD for the Hybrid microwave is different from the realization principle of the 1+1 FD for the SDH/PDH microwave. 8.5.1 SDH/PDH Microwave This topic considers the IDU 620 that is configured with one 1+1 FD protection group as an example to describe the principle of the 1+1 FD protection switching for the SDH/PDH microwave. 8.5.2 Hybrid Microwave This topic considers the IDU 620 that is configured with one 1+1 FD protection group as an example to describe the principle of the 1+1 FD protection switching for the Hybrid microwave.

This topic considers the IDU 620 that is configured with one 1+1 FD protection group as an example to describe the principle of the 1+1 FD protection switching for the SDH/PDH microwave.

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

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

8 1+1 FD
l
In the receive direction, the IF boards select their own service signal. The cross-connect board selects the signal from the standby IF board. In the transmit direction, no processing is required.
Figure 8-9 1+1 FD HSM realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
After a 1+1 FD HSM switching:

l
In the receive direction, the IF boards select the baseband signal from their own paired IF board. In the transmit direction, no processing is required.
NOTE
l l
The two built-in IF units of the IDU 605 2B/2F realize the functions of two IF boards of the IDU 620. The multiplexing sub-unit that is embedded in the IF unit of the IDU 605 2B/2F realizes the functions of the cross-connect board of the IDU 620.

This topic considers the IDU 620 that is configured with one 1+1 FD protection group as an example to describe the principle of the 1+1 FD protection switching for the Hybrid microwave.
8-12
Issue 02 (2009-02-25)
8 1+1 FD

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

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

l
In the transmit direction: The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. The IF processing units of the main IF board and the standby IF board modulate the Hybrid microwave frame that is multiplexed by the MUX unit of their corresponding IF board into the analog IF signal. The main IF board and the standby IF board send the analog IF signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal at frequency f1 to the main antenna and the standby ODU transmits the RF signal at frequency f2 to the standby antenna.
Issue 02 (2009-02-25)
8-15
8 1+1 FD
l
In the receive direction: The Hybrid microwave frame demultiplexed by the main IF board is transmitted to the standby IF board through the protection bus. The MUX unit of the main IF board receives the Hybrid microwave frame that is multiplexed by the main IF board and then separates the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The MUX unit of the standby IF board receives the Hybrid microwave frame that is multiplexed by the standby board and then separates the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. The cross-connect board and the EMS6 board receive the service signal from the standby IF board.
Figure 8-14 1+1 FD HSM realization principle (after the switching, in the receive direction)
Antenna
f2
Standby ODU
Standby IF board
EMS6 board
After a 1+1 FD HSM switching:

l l
In the transmit direction, no processing is required. In the receive direction: The MUX unit of the main IF board receives the demodulated Hybrid signal frame that is transmitted from the standby IF board through the protection bus and then separates the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The crossconnect board and the EMS6 board receive the service signal from the main IF board.
NOTE
8.6 Planning Guide

If there are sufficient spectrum resources, it is recommended that you adopt the 1+1 FD protection configuration.
Procedure

l
8 1+1 FD
If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the value to ten minutes. The spacing between the emission frequency of the main ODU and that of the standby ODU should be greater than 56 MHz to prevent adjacent-channel interference. In the case of the IDU 620, a pair of main and standby IF boards must be installed in slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is the main board). In the case of the IDU 605 2B/2F, the active/standby relation of the IF unit is fixed. Hence, planning is not required.
----End


Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The IF boards and their corresponding ODUs that form the IF 1+1 protection must be included in the NE Panel.
Precautions
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1 Protection from the Function Tree.
8 1+1 FD
Step 2 Click New. The system displays the Create IF 1+1 Protection dialog box. Step 3 Set the parameters of the IF 1+1 protection group.
Parameters
l
If only one IF 1+1 protection group is to be created, it is recommended that you set Protection Group ID to 1. If two IF 1+1 protection groups are to be created, it is recommended that you set the Protection Group ID of the protection group that is formed by the IF boards in slots 5 and 7 to 1 and the Protection Group ID of the protection group that is formed by the IF boards in slots 6 and 8 to 2.
8-18
Issue 02 (2009-02-25)
8 1+1 FD
Parameter Working Mode
Value Range HSB, FD, SD
Default Value HSB
Description
l
In the 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. In the 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The remote end selects signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. In the 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced. The 1+1 FD protection mode and 1+1 SD protection mode are compatible with the 1+1 HSB switching function. Set this parameter according to the planning information. 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 use the default value.
Revertive Mode
Revertive, NonRevertive
Revertive
Issue 02 (2009-02-25)
8-19
8 1+1 FD
Parameter WTR Time (s)
Default Value 600
Description
l
This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value. When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. When this parameter at the source end is set to Enable and the reverse switching conditions are met, the IF 1+1 protection switching occurs at the source end. This parameter is valid only when Working Mode is set to HSB or SD. It is recommended that you use the default value. In the 1+1 FD/SD mode, two IF boards should be installed as a pair in slots 5 and 7 (the IF board in slot 5 is recommended to be the main board) or in slots 6 and 8 (the IF board in slot 6 is recommended to be the main board). In the 1+1 HSB mode, the IF boards can be installed in slots 58. It is recommended that you install two IF boards in a pair in slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is the main board).
Enable, Disable
Enable
Working Board Protection Board
IF ports
NOTE
Postrequisite
l
8-20
Issue 02 (2009-02-25)

l
8 1+1 FD
NOTE

Prerequisite
Precautions
Procedure
Issue 02 (2009-02-25)
8-21
8 1+1 FD
Parameters
l
In the 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. In the 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The opposite end selects signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. In the 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced. The 1+1 FD protection mode and 1+1 SD protection mode are compatible with the 1+1 HSB switching function. Set this parameter according to the planning information. 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 use the default value.
Revertive Mode
Revertive, NonRevertive
Revertive
8-22
Issue 02 (2009-02-25)
8 1+1 FD
Parameter WTR Time(s)
Default Value -
Description
l
This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value. When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. When this parameter at the source end is set to Enable and the reverse switching conditions are met, the IF 1+1 protection switching occurs at the source end. This parameter is valid only when Working Mode is set to HSB or SD. It is recommended that you use the default value.
Enable, Disable
Enable
NOTE
Postrequisite
l
NOTE

This topic describes how to carry out the IF 1+1 protection switching, relevant alarms and events, and the problems that occur frequently during the application of the protection feature. 8.8.1 IF 1+1 Protection Switching The IF 1+1 protection switching is an important maintenance operation. 8.8.2 Relevant Alarms and Events
8 1+1 FD
When a 1+1 FD switching occurs on IF boards, the system reports corresponding alarms and abnormal events. 8.8.3 FAQs This topic lists the problems that occur frequently during the application of the 1+1 FD protection.

Prerequisite
l l
Procedure

When a 1+1 FD switching occurs on IF boards, the system reports corresponding alarms and abnormal events.
Relevant Alarms
l
HSB_INDI (IDU 620) The HSB_INDI alarm indicates that the microwave equipment is switched. HSM_INDI (IDU 620) The HSM_INDI alarm indicates that the microwave channel is switched. RPS_INDI (IDU 605 2B/2F) The RPS_INDI alarm indicates the microwave protection switching.

l
IF 1+1 protection switching

8-24
8 1+1 FD
This abnormal event indicates that the IF 1+1 protection switching occurs.
8.8.3 FAQs
This topic lists the problems that occur frequently during the application of the 1+1 FD protection. Q: What states does the 1+1 FD protection group have? A: At the equipment side, the 1+1 FD protection group has the following states:
l
Normal The state when no switching occurs or the state after a switching is cleared Automatic The state after a switching is triggered by an equipment fault Forced The state after a forced switching Manual The state after a manual switching Lockout The state after a lockout switching WTR The state that exists from the time the former active equipment is restored to normal to the time the revertive switching occurs in the revertive mode
At the channel side, the 1+1 FD protection group has the following states:
l
Normal The state when no switching occurs Forced The state after an HSB switching Automatic The state after an HSM switching is triggered by a service alarm
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
Issue 02 (2009-02-25)
8 1+1 FD
l
The IF board functions as the working source or the protection source of the SNCP service.
Q: Why the reverse switching cannot be set in the 1+1 FD mode? A: In the 1+1 FD mode, both the main ODU and the standby ODU are not muted. Hence, the source end cannot clear the service alarm at the sink end by switching the working ODU. The reverse switching is invalid for the 1+1 FD mode. Q: When radio links work as ECC links, why is the NMS unable to receive the abnormal HSB switching event of the non-gateway NE? A: When an HSB switching occurs, the ECC needs to reroute. As a result, the ECC between the gateway NE and the non-gateway NE is transiently interrupted and the switching event cannot be reported. Q: What methods should be used to handle a 1+1 FD protection switching failure? A: If the 1+1 FD protection switching fails, check whether alarms indicating abnormalities are reported on the standby IF board. If yes, handle these alarms. Then, manually perform the 1+1 FD protection switching again to check whether the 1+1 FD protection switching is normal.
8-26
Issue 02 (2009-02-25)
9 1+1 SD
9
About This Chapter
9.1 Feature Description This topic describes the 1+1 FD protection through its application.
1+1 SD
1+1 SD is a configuration mode of 1+1 protection. In the 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same RF signal. The equipment selects signals from the two received signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced.
9.2 Basic Concepts This topic describes the basic concept that you need to be familiar with before you use the 1+1 SD feature. 9.3 Availability The 1+1 SD feature requires the support of the applicable equipment and boards. 9.4 Relation with Other Features The 1+1 SD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave. 9.5 Realization Principle The realization principle of the 1+1 SD for the Hybrid microwave is different from the realization principle of the 1+1 SD for the SDH/PDH microwave. 9.6 Planning Guide In the case of the radio links whose transmission performance is significantly affected by multipath fading, it is recommended that you adopt the 1+1 SD protection configuration. 9.7 Configuration Guide The method for configuring the 1+1 HSB/FD/SD feature on the IDU 620 is different from the method for configuring the 1+1 HSB/FD/SD feature on the IDU 605 2B/2F. 9.8 Maintenance Guide This topic describes how to carry out the IF 1+1 protection switching, relevant alarms and events, and the problems that occur frequently during the application of the protection feature.
Issue 02 (2009-02-25)
9-1
9 1+1 SD

This topic describes the 1+1 FD protection through its application. Figure 9-1 shows the application of the 1+1 SD protection. Figure 9-1 1+1 SD protection
Main channel
T1 T2 T1
Main channel
T2
MODEM Service MODEM
Transmitter
Transmitter
MODEM Service
Transmitter
T2 T1
Transmitter
MODEM
Standby channel
Standby channel
In the case of the 1+1 SD protection configuration, 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 the space diversity, the signal that is received by the standby antenna may not be degraded. In this case, the service unit receives the service from the standby receive channel to protect the service. In addition, the 1+1 SD protection supports the 1+1 HSB protection switching.
9.2 Basic Concepts

This topic describes the basic concept that you need to be familiar with before you use the 1+1 SD feature. 9.2.1 System Configuration The IDU 620 and IDU 605 2B/2F support the configuration of the 1+1 SD protection. 9.2.2 Protection Type The 1+1 SD protection is classified into the revertive mode and the non-revertive mode. 9.2.3 Switching Conditions The 1+1 SD protection supports two types of switching: HSB switching and HSM switching. The two types of switching have different trigger conditions. 9.2.4 Switching Impact In the case of the HSB switching, the services are interrupted within the HSB switching time (shorter than 500 ms). In the case of the HSM switching, the services are not affected because it is a hitless switching.

The IDU 620 and IDU 605 2B/2F support the configuration of the 1+1 SD protection.
9 1+1 SD

The IDU 620 supports one or two 1+1 SD protection groups. One 1+1 SD protection group occupies one channel and consists of the following:
l l l
Two IF boards Two ODUs that are of the same type Two antennas
NOTE
The IF board can be the IF0A board, IF0B board, IF1A board, IF1B board, IFH2 board or IFX board. The two IF boards that are in a 1+1 SD protection group must work in the same radio work mode.
Figure 9-2 provides a typical configuration of one 1+1 SD protection group on the IDU 620. Figure 9-2 Typical configuration of one 1+1 SD protection group (IDU 620)
ODU
Antenna
ODU
Antenna
EXT IF FAN
Slot 20
EXT EXT EXT PH1 SCC
EXT IF PXC PXC

IDU 620

The IDU 605 2B/2F supports one 1+1 SD protection group. One 1+1 SD protection group occupies one channel and consists of the following:
l l l
One IDU 605 2B/2F Two ODUs that are of the same type Two antennas
Figure 9-3 provides a typical configuration of one 1+1 SD protection group on the IDU 605 2B/ 2F.
9 1+1 SD
Figure 9-3 Typical configuration of one 1+1 SD protection group (IDU 605 2B/2F)
Antenna
ODU
Antenna
ODU
IDU 605 2B/2F

The 1+1 SD protection is classified into the revertive mode and the non-revertive mode.
l
NOTE
Both the revertive mode and non-revertive mode are relevant only to the HSB switching (switching at the equipment side). In the case of the HSM switching (switching at the channel side), regardless of whether the revertive mode is set to revertive or non-revertive, the IF board attempts to perform a revertive switching every two minutes after an HSM switching.

The 1+1 SD protection supports two types of switching: HSB switching and HSM switching. The two types of switching have different trigger conditions.
HSB Switching Conditions

The HSB switching is the switching that occurs at the equipment side. The equipment-side switching has the same switching action and switching impact as the 1+1 HSB switching but has different trigger conditions.
9 1+1 SD
Table 9-1 HSB switching conditions of the 1+1 SD protection Switching Condition Clear switching (external switching) Lockout 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, a switching enters the lockout state. In the lockout state, no switching occurs until the lockout switching is cleared. If a 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 enters the forced switching state. If a 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 main board to the standby board. The switching then enters the automatic switching state. For the trigger conditions of the automatic switching, see Table 9-2.
The main equipment is faulty.
Issue 02 (2009-02-25)
9-5
9 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 a service alarm, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. If the sink end is in the lockout switching state or in the 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 action occurs. The timer duration is the WTR time (in the revertive mode) or five minutes (in the non-revertive mode). After the reverse switching, the switching enters the RDI state. If a 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 enters the manual switching state.
9-6
Issue 02 (2009-02-25)
9 1+1 SD
Priority
Description When the switching is in the automatic switching state and the former main equipment is already restored to normal for a period lasting for the WTR time, the revertive switching occurs. From the time the former main equipment is restored to normal to the time the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching enters the normal state.
Table 9-2 Trigger conditions of the automatic HSB switching Switching Condition The hardware of the IF board is faulty. The hardware of the ODU is faulty. POWER_FAIL VOLT_LOS (IF board) RADIO_TSL_HIGH RADIO_TSL_LOW RADIO_RSL_HIGH IF_INPWR_ABN CONFIG_NOSUPPORT Priority At the same priority
HSM Switching Conditions

The HSM switching is the switching that occurs at the channel side. The channel-side switching is available in the following types:
l
Forced switching The forced switching refers to the HSM switching that occurs at the same time the HSB switching occurs. After the forced switching, the IF board receives the baseband signal transmitted from this IF board.
Automatic switching The automatic switching refers to the HSM switching that is automatically triggered by a service alarm. After the automatic switching, the IF board receives the baseband signal transmitted from the IF board in the paired slot.
Issue 02 (2009-02-25)
9-7
9 1+1 SD
Table 9-3 Trigger conditions of the automatic HSM switching Switching Condition R_LOC R_LOF R_LOS MW_LOF MW_FECUNCOR B1_SD (when the IF board of the IDU 620 works in the PDH mode) B2_SD (when the IF board of the IDU 620 works in the SDH mode) MW_BER_SD (IDU 605 2B/2F) Medium Low Priority High
NOTE
The trigger conditions of the automatic HSM switching are classified into three grades: high, medium, and low. If both the main IF board and the standby IF board have a service alarm, the switching occurs only when the alarm in the main IF board has a higher priority than the alarm in the standby IF board. For example, if the main IF board has the MW_FECUNCOR alarm and the standby IF board has the B2_SD alarm, the switching occurs. If both the main IF board and the standby IF board have only the MW_FECUNCOR alarm, no switching occurs.
l
Revertive switching After an automatic HSM switching, the IF board attempts to perform a revertive switching every two minutes. If there is no service alarm on the working channel at this time, the IF board releases the switching.

In the case of the HSB switching, the services are interrupted within the HSB switching time (shorter than 500 ms). In the case of the HSM switching, the services are not affected because it is a hitless switching.
9.3 Availability
The 1+1 SD feature requires the support of the applicable equipment and boards. Table 9-4 Availability of the 1+1 SD feature Feature 1+1 SD Applicable Board IF0A/IF0B (all the versions) IF1A/IF1B (all the versions) Applicable Equipment IDU 605 2B/2F IDU 620
9-8
Issue 02 (2009-02-25)
9 1+1 SD
Feature
Applicable Board IFX (all the versions) IFH2 (all the versions)
Applicable Equipment

The 1+1 SD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave.
l l
The 18)2E1,3.5MHz,QPSK work mode does not support 1+1 SD protection. 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 SD protection group, but the two IF boards in different XPIC working groups can be configured into one 1+1 SD protection group. Therefore, the four IF boards in two XPIC working groups can 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 with the 1+1 SD configuration can work only as the service sink of an SNCP service pair, and cannot work as the working source or the protection source. The Hybrid microwave supports the 1+1 SD protection switching.

The realization principle of the 1+1 SD for the Hybrid microwave is different from the realization principle of the 1+1 SD for the SDH/PDH microwave. 9.5.1 SDH/PDH Microwave This topic considers the IDU 620 that is configured with one 1+1 SD protection group as an example to describe the principle of the 1+1 SD protection switching for the SDH/PDH microwave. 9.5.2 Hybrid Microwave This topic considers the IDU 620 that is configured with one 1+1 SD protection group as an example to describe the principle of the 1+1 SD protection switching for the Hybrid microwave.

This topic considers the IDU 620 that is configured with one 1+1 SD protection group as an example to describe the principle of the 1+1 SD protection switching for the SDH/PDH microwave.
Issue 02 (2009-02-25)
9-9
9 1+1 SD

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

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

Figure 9-6 1+1 SD HSB realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
Figure 9-7 1+1 SD HSB realization principle (after the switching, in the transmit direction)
Antenna Main ODU Main Cross-connect board IF board Service board
Antenna
Standby ODU
Standby IF board
After a 1+1 SD HSB switching:

l
In the receive direction, the IF boards select their own service signal. The cross-connect board selects the signal from the standby IF board. In the transmit direction, the standby ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The main ODU mutes (that is, the main ODU does not send the RF signal).
Issue 02 (2009-02-25)
9-11
9 1+1 SD
Figure 9-8 1+1 SD HSM realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
After a 1+1 SD HSM switching:

l
In the receive direction, the IF boards select the baseband signal from their own paired IF board. In the transmit direction, no processing is required.
NOTE
l l
The two built-in IF units of the IDU 605 2B/2F realize the functions of two IF boards of the IDU 620. The multiplexing sub-unit that is embedded in the IF unit of the IDU 605 2B/2F realizes the functions of the cross-connect board of the IDU 620.

This topic considers the IDU 620 that is configured with one 1+1 SD protection group as an example to describe the principle of the 1+1 SD protection switching for the Hybrid microwave.

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

Figure 9-11 1+1 SD HSB realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
EMS6 board
Figure 9-12 1+1 SD HSB realization principle (after the switching, in the transmit direction)
Antenna
Standby ODU
Standby IF board
EMS6 board
9-14
Issue 02 (2009-02-25)
9 1+1 SD
After a 1+1 SD HSB switching:

l
In the receive direction: The MUX unit of the standby IF board receives the Hybrid microwave frame that is multiplexed by the standby IF board. The cross-connect board receives the E1 service signal that is demultiplexed from the Hybrid microwave frame received at the standby IF board and cross-connects the E1 service signal to the corresponding service board. The EMS6 board receives the Ethernet service signal from the standby IF board because the Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state.
In the transmit direction: The Ethernet service port of the main IF board is in LinkDown state. The Ethernet service port of the standby IF board is in LinkUp state. The main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by the standby IF board and then transmit the modulated Hybrid microwave frame to the main ODU and the standby ODU respectively. The standby ODU transmits the RF signal to the antenna. The main ODU is muted (that is, the main ODU does not transmit the RF signal).
Figure 9-13 1+1 SD HSM realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
EMS6 board
After a 1+1 SD HSM switching:

l l
In the transmit direction, no processing is required. In the receive direction: The MUX unit of the main IF board receives the demodulated Hybrid signal frame that is transmitted from the standby IF board through the protection bus and then separates the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The crossconnect board and the EMS6 board receive the service signal from the main IF board.
NOTE
Issue 02 (2009-02-25)
9-15
9 1+1 SD
9.6 Planning Guide

In the case of the radio links whose transmission performance is significantly affected by multipath fading, it is recommended that you adopt the 1+1 SD protection configuration.
Procedure
l
There should be a height difference between the two antennas so that the dependence of the diversity-received microwave signals on the space is minimized. If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the value to ten minutes. It is recommended that you enable the reverse switching. If reverse switching is enabled, and both the main IF board and the standby IF board at the sink end report a service alarm, a reverse switching occurs at the source end. In the case of the IDU 620, a pair of main and standby IF boards must be installed in slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is the main board). In the case of the IDU 605 2B/2F, the active/standby relation of the IF unit is fixed. Hence, planning is not required.
----End


Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The IF boards and their corresponding ODUs that form the IF 1+1 protection must be included in the NE Panel.
9-16
Issue 02 (2009-02-25)
9 1+1 SD
Precautions
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 New. The system displays the Create IF 1+1 Protection dialog box. Step 3 Set the parameters of the IF 1+1 protection group.
Issue 02 (2009-02-25)
9-17
9 1+1 SD
Parameters
l
If only one IF 1+1 protection group is to be created, it is recommended that you set Protection Group ID to 1. If two IF 1+1 protection groups are to be created, it is recommended that you set the Protection Group ID of the protection group that is formed by the IF boards in slots 5 and 7 to 1 and the Protection Group ID of the protection group that is formed by the IF boards in slots 6 and 8 to 2. In the 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. In the 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The remote end selects signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. In the 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced. The 1+1 FD protection mode and 1+1 SD protection mode are compatible with the 1+1 HSB switching function. Set this parameter according to the planning information.
Working Mode
HSB, FD, SD
HSB
9-18
Issue 02 (2009-02-25)
9 1+1 SD
Description
l
When this parameter is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. 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 use the default value. This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value. When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. When this parameter at the source end is set to Enable and the reverse switching conditions are met, the IF 1+1 protection switching occurs at the source end. This parameter is valid only when Working Mode is set to HSB or SD. It is recommended that you use the default value. In the 1+1 FD/SD mode, two IF boards should be installed as a pair in slots 5 and 7 (the IF board in slot 5 is recommended to be the main board) or in slots 6 and 8 (the IF board in slot 6 is recommended to be the main board). In the 1+1 HSB mode, the IF boards can be installed in slots 58. It is recommended that you install two IF boards in a pair in slots 5 and 7 (the IF board in slot 5 is the main board) or in
WTR Time (s)
300 to 720
600
Enable, Disable
Enable
Working Board
IF ports
Issue 02 (2009-02-25)
9-19
9 1+1 SD
Parameter Protection Board
Value Range
Default Value
Description slots 6 and 8 (the IF board in slot 6 is the main board).
NOTE
Postrequisite
l
NOTE

Prerequisite
Precautions
9 1+1 SD
Procedure
Parameters
l
In the 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. In the 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The opposite end selects signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. In the 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced. The 1+1 FD protection mode and 1+1 SD protection mode are compatible with the 1+1 HSB switching function. Set this parameter according to the planning information.
Issue 02 (2009-02-25)
9-21
9 1+1 SD
Description
l
When this parameter is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. 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 use the default value. This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value. When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. When this parameter at the source end is set to Enable and the reverse switching conditions are met, the IF 1+1 protection switching occurs at the source end. This parameter is valid only when Working Mode is set to HSB or SD. It is recommended that you use the default value.
WTR Time(s)
300 to 720
Enable, Disable
Enable
NOTE
Postrequisite
l
9-22
Issue 02 (2009-02-25)

l
9 1+1 SD
NOTE

This topic describes how to carry out the IF 1+1 protection switching, relevant alarms and events, and the problems that occur frequently during the application of the protection feature. 9.8.1 IF 1+1 Protection Switching The IF 1+1 protection switching is an important maintenance operation. 9.8.2 Relevant Alarms and Events When a 1+1 SD switching occurs on IF boards, the system reports corresponding alarms and abnormal events. 9.8.3 FAQs This topic lists the problems that occur frequently during the application of the 1+1 SD protection.

Prerequisite
l l
Procedure
Issue 02 (2009-02-25)
9-23
9 1+1 SD

When a 1+1 SD switching occurs on IF boards, the system reports corresponding alarms and abnormal events.
Relevant Alarms
l
HSB_INDI (IDU 620) The HSB_INDI alarm indicates that the microwave equipment is switched. HSM_INDI (IDU 620) The HSM_INDI alarm indicates that the microwave channel is switched. RPS_INDI (IDU 605 2B/2F) The RPS_INDI alarm indicates the microwave protection switching.

l
IF 1+1 protection switching This abnormal event indicates that the IF 1+1 protection switching occurs.
9.8.3 FAQs
This topic lists the problems that occur frequently during the application of the 1+1 SD protection. Q: What states does the 1+1 SD protection group have? A: At the equipment side, the 1+1 SD protection group has the following states:
l
Normal The state when no switching takes place or the state after a switching is cleared Automatic The state after a switching is triggered by an equipment fault Forced The state after a forced switching RDI The state after a reverse switching Manual The state after a manual switching Lockout The state after a lockout switching WTR The state that exists from the time the former active equipment is restored to normal to the time the revertive switching takes place in the revertive mode
At the channel side, the 1+1 SD protection group has the following states:
l
Normal The state when no switching takes place
9-24
Issue 02 (2009-02-25)

l
9 1+1 SD
Forced The state after an HSB switching Automatic The state after an HSM switching is triggered by a service alarm
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 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 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 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. The IF board functions as the working source or the protection source of the SNCP service.
l l l
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 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 takes place, 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 does a switching event occur 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 also reports the same configuration alarm. As 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 methods should be used to handle a 1+1 SD protection switching failure?
9 1+1 SD
A: If the 1+1 SD protection switching fails, check whether alarms indicating abnormalities are reported on the standby ODU. If yes, handle these alarms. Then, manually perform the 1+1 SD protection switching again to check whether the 1+1 SD protection switching is normal.
9-26
Issue 02 (2009-02-25)
10 Cross-Polarization Interference Cancellation
10
About This Chapter
Cross-Polarization Interference Cancellation
Cross-polarization interference cancellation (XPIC) is a technology used together with cochannel dual-polarization (CCDP). The application of the two technologies doubles the wireless link capacity over the same channel. 10.1 Feature Description This topic considers the application of the XPIC as an example to describe the XPIC feature. 10.2 Basic Concepts This topic describes the basic concepts that you should be familiar with before you use the XPIC feature. 10.3 Availability The XPIC feature requires the support of the applicable equipment and boards. 10.4 Relation with Other Features The XPIC feature is related to the 1+1 protection configuration and ATPC feature. 10.5 Realization Principle The IFX boards of the OptiX RTN 600 receive signals in the horizontal and vertical directions. The signals in the two directions are then processed and the original signals are recovered. 10.6 Planning Guide Plan the XPIC parameters according to the situation of the microwave links. 10.7 Creating an XPIC Workgroup When two IFX boards that form an XPIC workgroup are installed on an IDU, you can create an XPIC workgroup to ensure that the XPIC workgroup is configured with the same work mode, transmission frequency, TX power, and ATPC attributes. 10.8 Maintenance Guide This topic describes the alarms and performance events relevant to the XPIC feature, and the problems that occur frequently during the application of the XPIC feature.
Issue 02 (2009-02-25)
10-1

This topic considers the application of the XPIC as an example to describe the XPIC feature. The application of the XPIC technology enables using the same channel bandwidth to transmit service signals whose capacity is two times the capacity of application without XPIC. The transmission of 2xSTM-1 signals in one direction of the radio link is considered as an example. When the XPIC technology is not used, the adjacent channel alternate polarization (ACAP) technology should be used in channel configuration. Thus, the bandwidth of two RF channels should be used to transmit these 2xSTM-1 signals. See Figure 10-1. When the XPIC technology is used, the bandwidth of one RF channel can transmit 2xSTM-1 signals by using the CCDP channel configuration mode. See Figure 10-2. Figure 10-1 Channel configuration in ACAP mode (without the application of the XPIC technology)
Site A IDU 620 STM-1 STM-1 ODU 2 ODU 1 f1 H V f2 f2 f2 ODU 2 STM-1 Site B ODU 1 IDU 620 STM-1
f1
f1
Figure 10-2 Channel configuration in CCDP mode (with the application of the XPIC technology)
Site A IDU 620 STM-1 STM-1 ODU 2 ODU 1 f1 H V f1 f1 ODU 2 Site B ODU 1 IDU 620 STM-1 STM-1
f1
f1
10.2 Basic Concepts

This topic describes the basic concepts that you should be familiar with before you use the XPIC feature. 10.2.1 CCDP and XPIC CCDP and XPIC are two technologies that are developed based on the polarization characteristics of microwaves. CCDP doubles the link capacity by transmitting two orthogonal
polarization waves over the same link, and XPIC cancels the cross-polarization interference between the two polarization waves. 10.2.2 System Configuration The IDU 620 support the XPIC configuration.
10.2.1 CCDP and XPIC

CCDP and XPIC are two technologies that are developed based on the polarization characteristics of microwaves. CCDP doubles the link capacity by transmitting two orthogonal polarization waves over the same link, and XPIC cancels the cross-polarization interference between the two polarization waves. Single-polarization transmission and CCDP transmission are two microwave transmission methods.
l
Single-polarization transmission adopts the horizontally polarized wave or the vertically polarized wave on one channel to transmit one channel of signals. See Figure 10-3. CCDP transmission adopts both the horizontally polarized wave and the vertically polarized wave on one channel to transmit two channels of signals. See Figure 10-4.
Therefore, CCDP transmission doubles the link capacity in single-polarization transmission. Figure 10-3 Single-polarization transmission
Figure 10-4 CCDP transmission
The ideal situation of CCDP transmission is that no interference exists between the two orthogonal signals though they are with the same frequency, and thus the receiver can easily recover the two signals. In actual engineering conditions, however, despite the orthogonality of the two signals, certain interference between the signals inevitably occurs, due to crosspolarization discrimination (XPD) of the antenna and channel degradation. To cancel the interference, the XPIC technology is adopted. In XPIC technology, the signals are received in the horizontal and vertical directions. The signals in the two directions are then processed and the original signals are recovered.
The characteristics of the XPIC function provided by the OptiX RTN 600 are as follows:
l l
The XPD tolerance is improved by about 20 dB and the notches performance is improved. The two receivers may not be synchronized, and therefore, they can be integrated in two NEs. The length of the IF cable between the IDU and ODU may differ and the maximum length difference is 12 meters. The XPIC function is realized by hardware.

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

Slot 20
EXT EXT EXT SD1 SCC
EXT IFX PXC PXC

IDU 620
XPIC Configuration Limitations

XPIC configuration has the following limitations:

l l l
XPIC supports the STM-1 microwave working mode only. Only IDU 620 is applicable. The ODU must adopt the separate mount mode, because the dual-polarized antenna is used.
10.3 Availability
The XPIC feature requires the support of the applicable equipment and boards. Table 10-1 Availability of the XPIC feature Feature XPIC Applicable Board IFX (all the versions) Applicable Equipment IDU 620

The XPIC feature is related to the 1+1 protection configuration and ATPC feature.
Relation with the 1+1 Protection Configuration

The two IFX boards in an XPIC working group cannot be configured into one 1+1 protection group, but the two IFX boards in different XPIC working groups can be configured into one 1 +1 protection group. Therefore, the four IFX boards in two XPIC working groups can form two 1+1 protection groups. Figure 10-6 provides an example of two XPIC groups forming two 1+1 protection groups. In this example, the service channels of the IFX boards in slots 5 and 6 form one XPIC group and the service channels of the IFX boards in slots 7 and 8 form another XPIC group. The service channels of the IFX boards in slots 5 and 7 form one 1+1 HSB protection group and the service channels of the IFX boards in slots 6 and 8 form another 1+1 HSB protection group. The services channels of the IFX boards in slots 5 and 6 are the main channels of the two 1+1 HSB protection groups. When the IFX board in slot 5 or the ODU to which the IFX board in slot 5 is connected is faulty, the HSB switching occurs on the equipment and the services are switched to the channels of the IFX board in slot 7. The fault also causes the loss of the XPIC signals sent by the IFX board in slot 5 to the IFX board in slot 6. As a result, the HSB switching occurs on the IFX board in slot 6 and the services are switched to the channels of the IFX board in slot 8. Thus, the services are switched from one XPIC group to another XPIC group.
Issue 02 (2009-02-25)
10-5
Figure 10-6 Typical XPIC configuration (1+1 protection configuration)

Dual-polarized antenna
ODU
ODU
Hybrid coupler ODU ODU

Hybrid coupler
EXT IFX FAN

Slot 20
EXT IFX EXT IFX SD1 SCC
EXT IFX PXC PXC

IDU 620
NOTE
Select balanced hybrid couplers to ensure, to the maximum extent, that the receiver power of the two ODUs that are in an XPIC group is the same.
Relation with the ATPC Feature

The transmit power of the two ODUs that are in an XPIC working group should be the same if possible. Hence, each of the ATPC parameters (ATPC enable status, ATPC upper threshold, ATPC lower threshold, and ATPC adjustment) should be set to the same value for the IFX boards that are in an XPIC working group.

The IFX boards of the OptiX RTN 600 receive signals in the horizontal and vertical directions. The signals in the two directions are then processed and the original signals are recovered.
10-6
Issue 02 (2009-02-25)
Figure 10-7 Realization principle of XPIC

Horizontal polarization Modem horizontal
XPIC module of IFX

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

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

Plan the XPIC parameters according to the situation of the microwave links.
Prerequisite
You must have an understanding of the microwave links.
Procedure
Plan XPIC parameters. Adhere to the following principles when planning the XPIC parameters:
l
When CCDP is applied to the STM-1 microwave links, the IFX boards must be installed and the XPIC function must be enabled. An XPIC working group must be configured to ensure that the XPIC working group is configured with the same working mode, transmission frequency, transmit power, and ATPC attributes. When the used ODUs support two T/R spacings, ensure that the two ODUs of an XPIC working group adopt the same T/R spacing.
Issue 02 (2009-02-25)

l
Determine the installation slot for the IFX board based on the requirement of the future upgrade.
If the 1+1 protection configuration is not required in the future upgrade, install IFX boards in slots 5 and 7 (the IFX board in slot 5 processes vertically polarized signals and the IFX board in slot 7 processes horizontally polarized signals) or in slots 6 and 8 (the IFX board in slot 6 processes vertically polarized signals and the IFX board in slot 8 processes horizontally polarized signals). If the configuration of two XPIC groups forming two 1+1 protection groups is required in the future upgrade, install IFX boards in slots 5 and 6 (the IFX board in slot 5 processes vertically polarized signals and the IFX board in slot 6 processes horizontally polarized signals) or in slots 7 and 8 (the IFX board in slot 7 processes vertically polarized signals and the IFX board in slot 8 processes horizontally polarized signals).
----End
10.7 Creating an XPIC Workgroup

When two IFX boards that form an XPIC workgroup are installed on an IDU, you can create an XPIC workgroup to ensure that the XPIC workgroup is configured with the same work mode, transmission frequency, TX power, and ATPC attributes.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The IFX boards and the ODUs to which the IFX boards are connected must be created. The XPIC Enabled parameter must be set to Enabled (default value) for the IFX boards.
Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the XPIC tab. Step 3 Click New. The Create XPIC Protection Group dialog box is displayed. Step 4 Set the parameters for the XPIC workgroup.
10-8
Issue 02 (2009-02-25)
Parameters
Parameter Polarization direction-V Polarization direction-H
l
Value Range IF ports of IFX boards
Default Value -
Description
l
Polarization direction-V and Polarization direction-H indicate the IF ports to which polarization direction V and polarization direction H correspond respectively. It is recommended that you install the two IFX boards that form an XPIC workgroup in the slots that are at the same layer or in the same column. Set the IF port on the IFX board that has a smaller slot number to Polarization direction-V and the IF port on the other IFX board to Polarization direction-H. Link ID-V and Link ID-H indicate the link IDs to which polarization direction V and polarization direction H correspond respectively. A Link ID is an identifier of a microwave link and is used to prevent the microwave 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,
10-9
Link ID-V
1 to 4094
Issue 02 (2009-02-25)
Parameter Link ID-H
Value Range
Default Value
Description the NE reports an MW_LIM alarm and inserts the AIS. Set these two parameters according to the planning information. These two parameters must be set to different values, but the Link ID-V must be set to the same value at the two ends of a link and the Link ID-H must also be set to the same value at the two ends of a link.
TX Power (dBm)
-10.0 to 35.0
The value of this parameter must not exceed the rated power range supported by the ODU. The TX power of the ODU must be set to the same value at the two ends of a microwave link. Set this parameter according to the planning information. The parameter specifies the channel center 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 greater than the difference between the upper TX frequency limit supported by the ODU and a half of the channel spacing. Set this parameter according to the planning information.
Transmission Frequency (MHz)
0 to 4294967.295
100
10-10
Issue 02 (2009-02-25)
Parameter Transmission Status
Value Range mute, unmute
Default Value mute
Description
l
When Transmission Status is set to mute, the transmitter of the ODU does not work but the ODU can normally receive microwave signals. When Transmission Status is set to unmute, the ODU normally transmits and receives microwave signals. In normal cases, set this parameter to unmute. This parameter specifies whether the ATPC function is enabled. The ATPC function enables the TX power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. In the case of areas where fast fading is severe, it is recommended that you set this parameter to Disabled. During commissioning, set this parameter to Disabled to ensure that the TX power is not changed. After the commissioning, re-set the ATPC attributes. When the ATPC function is enabled, if the RSL at the receive end is higher than the preset ATPC upper threshold at the receive end, the receiver notifies the transmitter to decrease the TX power according to the preset ATPC adjustment step at the transmit end until the RSL is lower than the ATPC upper threshold. Generally, ATPC Upper Threshold (dBm) should be 20 dB to 30 dB higher than ATPC Lower Threshold (dBm), and must not be less than 15 dB. If the difference between the upper threshold and the lower threshold is big, the number of ATPC adjustments is reduced and the system load is also reduced. If the difference between the upper threshold and the lower threshold is small, the TX power is adjusted in a timely manner and the interference to adjacent systems is reduced.
ATPC Enabled
Enabled, Disabled
Disabled
ATPC Upper Threshold (dBm)
-20 to -75
-45
Issue 02 (2009-02-25)
10-11
Parameter ATPC Lower Threshold (dBm)
Value Range -35 to -90
Default Value -70
Description
l
When the ATPC function is enabled, if the RSL at the receive end is lower than the preset ATPC lower threshold, the receiver notifies the transmitter to increase the TX power according to the preset ATPC adjustment step at the transmit end until the RSL is higher than the ATPC lower threshold. Generally, set this parameter to a value that is at least 10 dB greater than the receiver sensitivity to prevent sudden fast fading because sudden fast fading makes the RSL value lower than the receiver sensitivity. This parameter specifies the variation in the TX power caused by one ATPC adjustment. It is recommended that you set the value to 5.
ATPC Adjustment (dB)
1 to 5
NOTE
Each of the ATPC parameters must be set to the same value at the two ends of a microwave link.
Postrequisite
Generally, you do not need to configure the IF/ODU information after you configure an XPIC workgroup. You, however, need to set the T/R spacing used by the ODU in the IF/ODU Configuration tab page if the used ODU supports two T/R spacings.

This topic describes the alarms and performance events relevant to the XPIC feature, and the problems that occur frequently during the application of the XPIC feature. 10.8.1 Relevant Alarms and Events When XPIC signals are lost, the system reports an alarm. 10.8.2 FAQs This topic lists the problems that occur frequently during the application of the XPIC feature.

When XPIC signals are lost, the system reports an alarm.
Relevant Alarms
l
XPIC_LOS The XPIC_LOS alarm indicates that the XPIC compensation signal is lost.
10-12
Issue 02 (2009-02-25)

None.
10.8.2 FAQs
This topic lists the problems that occur frequently during the application of the XPIC feature. Q: What are the common causes of XPIC faults? A: Common causes are as follows:
l
The data is wrongly configured. The two IFX boards that form an XPIC group must be configured with the same working mode, transmission frequency, and T/R spacing.
Cables are wrongly connected. The provision of the XPIC feature involves the installation of IF cables, installation of XPIC cables, and separate mounting of ODUs. It is likely that the cables are wrongly connected, especially when the dual-NE configuration mode is adopted or XPIC groups are configured with the 1+1 protection. Divide the cables into two parts according to the polarization direction of signals and then check each part.
The polarization directions of dual-polarized antennas are not aligned. The XPD can reach the design value of the antennas only when the polarization directions of dual-polarized antennas are totally aligned.
Issue 02 (2009-02-25)
10-13
11 N+1 Protection
11
About This Chapter
N+1 Protection
The N+1 protection refers to the protection configuration in which N working channels in a microwave direction share one protection channel. 11.1 Feature Description This topic considers the application of the N+1 protection as an example to describe the N+1 protection. 11.2 Basic Concepts This topic describes the basic concepts that you should be familiar with before you use the N+1 protection. 11.3 Availability The N+1 protection feature requires the support of the applicable equipment and boards. 11.4 Relation with Other Features The N+1 protection is related to the 1+1 protection configurationand SNCP feature. 11.5 Realization Principle The N+1 protection uses the N+1 protection protocol to realize the switching. The N+1 protection protocol is similar to the 1:N linear multiplex section protection protocol. 11.6 Planning Guide When the OptiX RTN 600 transmits two or three STM-1 microwave services in the point-topoint mode, you can adopt the N+1 protection configuration. 11.7 Configuration Guide This topic describes the configuration flow and the corresponding configuration tasks of the N +1 protection mode. An example is provided as additional information to help understand the configuration. 11.8 Maintenance Guide This topic describes how to carry out the N+1 protection switching, relevant alarms and events, and the problems that occur frequently during the application of the protection feature.
Issue 02 (2009-02-25)
11-1
11 N+1 Protection

This topic considers the application of the N+1 protection as an example to describe the N+1 protection. The N+1 protection realizes protection for microwave channels. The IF board, ODU, and radio link on the working channel can be protected through the N+1 protection. The N+1 protection provides N working channels and one protection channel. When the working channel becomes faulty, the normal services on the working channel can be switched to the protection channel for transmission. When the working channel is restored to normal, the protection channel can transmit the extra services. Figure 11-1 shows the application of the N+1 protection. Figure 11-1 N+1 protection
Site A Normal service 1 Working channel 1 Site B Normal service1
...
Normal service N Extra service
Working channel N Protection channel
...
Protection switching Site A Normal service 1 Working channel 1 Site B Normal service1
...
...
11.2 Basic Concepts

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

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

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

Slot 20
EXT IF1B SL1 SD1 SCC
EXT IFIB PXC PXC

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

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

Two IDU 620 systems support one 3+1 protection group. One 3+1 protection group occupies four frequencies and consists of the following:
l l l l
Four IF boards (two for each NE) Four ODUs (two for each NE) Two SD1 boards (one for each NE) One dual-polarized antenna (with two balanced hybrid couplers)
11-4

NOTE
11 N+1 Protection
The IF board can be the IF1A board, IF1B board, or IFX board. As the XPIC function is not required, it is recommended that you use the IF1A board or the IF1B board.
Figure 11-4 provides a typical configuration of one 3+1 protection group. The configuration is as follows:
l
The two IF1B boards of the primary NE provide two working channels. The two IF1B boards of the secondary NE provide one working channel and one protection channel. The four channels are configured in the ACAP mode. See Figure 11-5. The radio receive power of the four channels should be the same if possible to reduce adjacent channel interference. That is, the ODU transmit power set for the four channels should be the same. The two SD1 boards in slots 6 and 8 of the primary NE access three working services and one extra service. One working service and the extra service are transferred to the secondary NE through the SD1 board in slot 4. The SD1 board in slot 4 of the secondary NE accesses the one working service and the extra service that are transferred from the primary NE.
NOTE
l l
You can use one SL4 board to replace the two SD1 boards in slots 6 and 8 of the primary NE to access the services, depending on the requirements.
Issue 02 (2009-02-25)
11-5
11 N+1 Protection
Figure 11-4 Typical configuration of one 3+1 protection group

ODU
ODU
Hybrid coupler ODU ODU

Hybrid coupler
EXT IF1B FAN

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

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

Working channel 1 V H Protection channel Working channel 3 Working channel 2
11-6
Issue 02 (2009-02-25)
11 N+1 Protection
Limitations of the N+1 Protection

The limitations of the N+1 protection are as follows:
l l l
The N+1 protection supports only the STM-1 radio working mode. The IDU must be the IDU 620. The ODUs must adopt the separate mounting mode due to the limitations of the dualpolarized antenna.

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

The N+1 protection can be triggered by local SF conditions, local SD conditions, local external switching requests, and byte K sent from the NE on the opposite side. This is similar to linear multiplex section protection. Table 11-1 Switching conditions of the N+1 protection Switching Condition Lockout of protection (external switching) Priority From top downwards, the priority is from the highest to the lowest. Description The lockout of protection blocks normal traffic signals from entering the protection channel but does not block traffic signals from being switched from the protection channel to the working channel. The signal fail condition in the protection channel is equivalent to the lockout of protection. Traffic signals on the working channel are forcibly switched to the protection channel.
Issue 02 (2009-02-25)
11-7
11 N+1 Protection
Switching Condition Signal fail (SF)
Priority
Description The SF on the working channel causes traffic signals to be switched to the protection channel. When there is the MW_LOF, R_LOC, R_LOF, R_LOS, MS_AIS, or B2_EXC alarm on the working channel, or when the hardware of an ODU or IF board is faulty, the SF switching is triggered. The SD on the working channel causes traffic signals to be switched to the protection channel. When there is the B2_SD alarm on the working channel, the SD switching is triggered. If a switching is in the lockout or forced switching state, or if the current standby equipment is faulty, no switching occurs. Otherwise, the system switches services from the active board to the standby board or from the standby board to the active board according to the command. The switching then enters the manual switching state. After traffic signals are switched to the protection channel due to the SF/SD condition on the working channel and the working channel is already restored to normal for the WTR time, a revertive switching occurs. From the time the former active equipment is restored to normal to the time the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching enters the normal state.
Signal degrade (SD)
11-8
Issue 02 (2009-02-25)
11 N+1 Protection
Switching Condition Exercise switching (external switching)
Priority
Description Traffic signals are not actually switched. The exercise functionality is used only to check whether an NE can normally carry out the N +1 protection protocol.
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 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 switching according to byte K sent from the NE at the opposite end, the NE determines the switching priority according to the bridge request code contained in byte K. For details, see 15.2.2 Meaning of Byte K.

The services are interrupted within the N+1 protection switching time (shorter than 50 ms). The extra services are interrupted from the time normal services are switched to the protection channel to the time the services are restored to the working channel.
11.3 Availability
The N+1 protection feature requires the support of the applicable equipment and boards. Table 11-2 Availability of the N+1 protection feature Feature N+1 protection Applicable Board IF1A/IF1B (all the versions) IFX (all the versions) Applicable Equipment IDU 620
NOTE
The Hybrid microwave does not support the N+1 protection.

The N+1 protection is related to the 1+1 protection configurationand SNCP feature.
l
The members of an N+1 protection group cannot be configured with the 1+1 protection.
Issue 02 (2009-02-25)
11 N+1 Protection
l
The radio link with the N+1 protection configuration can work only as the service sink of an SNCP service pair, and cannot work as the working source or the protection source.

The N+1 protection uses the N+1 protection protocol to realize the switching. The N+1 protection protocol is similar to the 1:N linear multiplex section protection protocol. 11.5.1 2+1 Protection Configuration In the case of 2+1 protection configuration, three IF boards form a 2+1 protection group to realize protection switching. 11.5.2 3+1 Protection Configuration In the case of the 3+1 protection configuration, the primary NE forms a 3+1 protection group to realize protection switching and the secondary NE forms two STM-1 REGs to realize transparent transmission of byte K.
11.5.1 2+1 Protection Configuration

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

PXC 4-SD1-1 5-IF1B-1 15-ODU
6-SL1-1
7-IF1B-1
17-ODU
4-SD1-2
8-IF1B-1
18-ODU
Working channel
Protection channel
11-10
Issue 02 (2009-02-25)
11 N+1 Protection
Figure 11-7 Realization principle of 2+1 protection (after the switching)

PXC 4-SD1-1 5-IF1B-1 15-ODU
6-SL1-1
7-IF1B-1
17-ODU
4-SD1-2
8-IF1B-1
18-ODU
Working channel
Protection channel
In this example, port 1 of the IF1B board in slot 5, port 1 of the IF1B board in slot 7, and port 1 of the IF1B board in slot 8 form a 2+1 protection group. When a working channel fails, the switching principle of the 2+1 protection configuration is as follows: 1. 2. Before the switching, the NE sends and receives normal traffic signals on the working channel, and sends and receives extra traffic signals on the protection channel. On detecting that the signals on a working channel fail (for example, the IF1B board in slot 5 detects that an MW_LOF alarm is generated on port 1), the IF board notifies the SCC board. The SCC board controls the PXC board to realize the transmission of the working traffic signals (port 1 of the SD1 board in slot 4) on the protection channel (port 1 of the IF1B board in slot 8). The SCC board also interacts with the NE on the opposite side through byte K to enable the NE on the opposite side to perform synchronous switching.
NOTE
3.
The interaction of byte K between NEs complies with the N+1 protection protocol, which is similar to the MSP protocol. For details, see Realization Principle of 1:N Linear MSP.
11.5.2 3+1 Protection Configuration

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

When the OptiX RTN 600 transmits two or three STM-1 microwave services in the point-topoint mode, you can adopt the N+1 protection configuration.
Procedure
Step 1 Select the 2+1 protection mode or 3+1 protection mode depending on the transmission capacity. Step 2 Plan the used channels.
l
It is recommended that you configure the channels in the ACAP mode.
Step 3 Plan the parameters relevant to the N+1 protection configuration.

l
Set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the value to ten minutes. It is recommended that you use SD as a switching condition.
----End

This topic describes the configuration flow and the corresponding configuration tasks of the N +1 protection mode. An example is provided as additional information to help understand the configuration. 11.7.1 Configuration Flow This topic describes the configuration flow for the N+1 protection mode. 11.7.2 Creating an N+1 Protection Group When the OptiX RTN 600 transmits two or three STM-1 microwave services in the point-topoint mode, you can adopt the N+1 protection configuration. 11.7.3 Creating REGs
11 N+1 Protection
In the case of the 3+1 protection, you need to configure REGs for the secondary NE. 11.7.4 Configuration Example This topic provides an example to describe how to configure the N+1 protection mode.

This topic describes the configuration flow for the N+1 protection mode. Figure 11-10 Configuration flow for the N+1 protection mode
Start 1
Create an N+1 protection group
Is the 3+1 protection mode used? Yes 2 Create REGs
No
End
Table 11-3 Description of the configuration flow of the N+1 protection mode Number 1 Description
l
In the case of the 3+1 protection, an N+1 protection group needs to be created only for the primary NE. For the configuration process, see 11.7.2 Creating an N+1 Protection Group. Create REGs between two IF boards of the secondary NE and two ports of the SD1 board that is connected to the primary NE. For the configuration process, see 11.7.3 Creating REGs.
11.7.2 Creating an N+1 Protection Group

When the OptiX RTN 600 transmits two or three STM-1 microwave services in the point-topoint mode, you can adopt the N+1 protection configuration.
Issue 02 (2009-02-25)
11-15
11 N+1 Protection
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The IF boards and the ODUs to which the IF boards are connected must be created. The STM-1 optical/electrical interface boards (only in the case of the primary NE that is to be configured with 3+1 protection) must be created. The IF boards must work in the STM-1 mode.
When an N+0 service is converted into an N+1 service by configuring the N+1 protection, the original services are not interrupted. The following procedures consider the operation of the Web LCT as an example.
Procedure
Step 1 In the NE Explorer, select the NE from the Function Tree and then choose Configuration > Link Configuration from the Function Tree. Click the N+1 Protection tab. Step 2 Click Create. The system displays the Create an N+1 Protection Group dialog box. Step 3 Set the attributes of the N+1 protection group. Step 4 Set the slot mapping relation. 1. 2. In Select Mapping direction, select Working Unit. In Select Mapping Mode, select the line port to which a working channel corresponds and click 3. 4. 5. .
Repeat Step 4.2 to select the line ports to which other working channels correspond. In Select Mapping direction, select Protection Unit. In Select Mapping Mode, select the line port to which the protection channel corresponds and click .
11-16
Issue 02 (2009-02-25)
11 N+1 Protection
Parameters
Parameter WTR Time(s) Value Range 300 to 720 Default Value 600 Description
l
When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value. When SD enable is set to Enabled, the B2_SD alarm is considered as a switching condition. It is recommended that you use the default value.
SD enable
Enabled, Disabled
Enabled
Issue 02 (2009-02-25)
11-17
11 N+1 Protection
Parameter Slot Mapping Relation
Value Range -
Default Value -
Description
l
In the case of 2+1 protection, map two IF ports as Working Unit and map the remaining IF port as Protection Unit. In the case of the 3+1 protection, it is recommended that you map the two IF ports and the first line port of the STM-1 optical/electrical interface board that is connected to the secondary NE as Working Unit, and map the other line port as Protection Unit.
NOTE
The N+1 protection groups of the equipment at both ends must have the same attributes.
11.7.3 Creating REGs

In the case of the 3+1 protection, you need to configure REGs for the secondary NE.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The IF boards and the ODUs to which the IF boards are connected must be created. The STM-1 optical/electrical interface board that is connected to the primary NE must be created. The IF boards must work in the STM-1 mode.
Context
In the case of the 3+1 protection, you need to two configure REGs for the secondary NE.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > REG Configuration from the Function Tree. Step 2 Click Create. The system displays the Create REG dialog box. Step 3 Set the SD Enabled parameter. Step 4 Set the slot mapping relation. 1. 2. In Slot Mapping Direction, select West Line. In Select Mapping Mode, select the line port to which the west line corresponds and click . 3.
11-18
In Slot Mapping Direction, select East Line.

11 N+1 Protection
4.
In Select Mapping Mode, select the line port to which the east line corresponds and click .
Step 5 Click OK. Step 6 Repeat Step 2 to Step 5, Create another REG.
Issue 02 (2009-02-25)
11-19
11 N+1 Protection
----End
Parameters
Parameter SD Enabled Value Range Enabled, Disabled Default Value Enabled Description
l
When this parameter is set to Enabled, the REG inserts an MS-AIS alarm when a B2_SD alarm is generated. It is recommended that you use the default value.
Slot Mapping Relation
It is recommended that you map the IF port as West Line and the port of the STM-1 optical/electrical interface board as East Line.
11-20
Issue 02 (2009-02-25)
11 N+1 Protection
11.7.4 Configuration Example

This topic provides an example to describe how to configure the N+1 protection mode.
Precautions
NOTE
l l
For the system configuration of this example, refer to the 3+1 protection configuration example provided in 11.2.1 System Configuration. The radio work mode of each IF board is already set to the STM-1 mode.
Procedure
Step 1 Configure port 1 of the IF1B board in slot 5 of the primary NE, port 1 of the IF1B board in slot 7 of the primary NE, and ports 1 and 2 of the SD1 board in slot 4 of the primary NE into a 3+1 protection group. For details, see 11.7.2 Creating an N+1 Protection Group. Step 2 Create an REG between port 1 of the IF1B board in slot 5 of the secondary NE and port 1 of the SD1 board in slot 4 of the secondary NE, and create another REG between port 1 of the IF1B board in slot 7 of the secondary NE and port 2 of the SD1 board in slot 4 of the secondary NE. For details, see 11.7.3 Creating REGs. ----End

This topic describes how to carry out the N+1 protection switching, relevant alarms and events, and the problems that occur frequently during the application of the protection feature. 11.8.1 Starting/Stopping the N+1 Protection Protocol If you first stop the N+1 protection protocol and then start it, the N+1 protection protocol can be restored to the initial state. 11.8.2 N+1 Protection Switching The N+1 protection switching is an important maintenance operation. 11.8.3 Relevant Alarms and Events When an N+1 protection switching occurs on IF boards, the system reports corresponding alarms and abnormal events. 11.8.4 FAQs This topic lists the problems that occur frequently during the application of the N+1 protection.
11.8.1 Starting/Stopping the N+1 Protection Protocol

If you first stop the N+1 protection protocol and then start it, the N+1 protection protocol can be restored to the initial state.
Prerequisite
l l
The N+1 protection group must be configured. The user must have the system level authority.
Issue 02 (2009-02-25)
11 N+1 Protection
Precautions
l l
Stopping the N+1 protection protocol causes the failure of the N+1 protection. When services are switched onto the protection channel, stopping the N+1 protection protocol causes the services to switch back to the working channel. At this time, if the working channel is normal, the services are transiently interrupted. If the working channel is faulty, the services are interrupted until the working channel is restored to normal or the N+1 protection protocol is started.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the N+1 Protection tab. Step 3 Select the N+1 protection group and click Start Protocol or Stop Protocol. The system then displays a dialog box indicating that the operation is successful. Step 4 Click OK. Step 5 Click Query. ----End
11.8.2 N+1 Protection Switching

The N+1 protection switching is an important maintenance operation.
Prerequisite
l l
The N+1 protection group must be configured. The user must have the system level authority.
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 N+1 Protection tab. Step 3 In Slot Mapping Relation, select a working unit or the protection unit of a protection group. Right-click on the selected unit and select the required switching mode from the displayed menu. The system then displays a dialog box indicating that the operation is successful. Step 4 Click Yes. Step 5 Click Query. ----End

When an N+1 protection switching occurs on IF boards, the system reports corresponding alarms and abnormal events.
11 N+1 Protection
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 N+1 protection protocol is manually stopped.

l
N+1 protection switching This abnormal event indicates that the N+1 protection switching occurs.
11.8.4 FAQs
This topic lists the problems that occur frequently during the application of the N+1 protection. Q: What switching states does the N+1 protection have? A: The N+1 protection has the following switching states:
l
Protocol is not started The state when the N+1 protection protocol is not started Protocol starting The state when the N+1 protection protocol is starting 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 exists 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 the forced switching cannot be carried out when the signal on the protection channel fails?
11 N+1 Protection
A: After the signal on the protection channel fails, the protection channel is locked out. As the lockout of the protection channel has a higher priority than the forced switching, the forced switching cannot be carried out. Q: Why does the creation of an N+1 protection group fail? A: Common causes are as follows: 1) The radio work mode of the IF board is not configured. 2) The radio work mode of the IF board is not the STM-1 mode.
11-24
Issue 02 (2009-02-25)
12 Automatic Transmit Power Control Function
12
Automatic Transmit Power Control Function
About This Chapter

The automatic transmit power control (ATPC) function is an important function of the radio transmission system. The ATPC function reduces the interference from a transmitter to adjacent systems and also reduces the residual bit error rate. 12.1 Feature Description The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. 12.2 Availability The ATPC feature requires the support of the applicable equipment and boards. 12.3 Relation with Other Features The ATPC feature is related to the XPIC and Hybrid microwave features. 12.4 Realization Principle The OptiX RTN 600 uses the ATPC overhead in the microwave frame to realize the ATPC function. 12.5 Planning Guide Plan the ATPC parameters according to the situation of the microwave links. 12.6 Configuring the ATPC Function To configure the ATPC function, set the ATPC attributes of the IF board. 12.7 Maintenance Guide This topic describes the alarms and performance events relevant to the ATPC function, and the problems that occur frequently during the application of the ATPC function.
Issue 02 (2009-02-25)
12-1

The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range.
Functions and Performance of ATPC

When the ATPC function is enabled, the following two cases are possible:
l
If the RSL at the receive end is lower than the preset ATPC lower threshold, the receiver notifies the transmitter to increase the transmit power according to the preset ATPC adjustment step at the transmit end until the RSL is higher than the ATPC lower threshold. If the RSL at the receive end is higher than the preset ATPC upper threshold, the receiver notifies the transmitter to decrease the transmit power according to the preset ATPC adjustment step at the transmit end until the RSL is lower than the ATPC upper threshold.
Table 12-1 provides the ATPC performance of the OptiX RTN 600. Table 12-1 ATPC performance ATPC Control Range Lower Threshold (dBm) 6 (SP ODU series) Rated minimum transmit power (HP/ SPA/LP ODU series) Upper Threshold (dBm) Rated maximum transmit power + 1.5 dB (SP ODU series) Rated maximum transmit power (HP/ SPA/LP ODU series) Value Range of the ATPC Adjustment Step (dB) 1 to 5 ATPC Adjustment Speed (dB/s)
10 (when the adjustment step is set to 1 dB) 20 (when the adjustment step is set to 2 dB) 30 (when the adjustment step is set to a value, which ranges from 3 dB to 5 dB)
Automatic ATPC Threshold Setting

The functions of the automatic ATPC threshold setting are 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.
12.2 Availability
The ATPC feature requires the support of the applicable equipment and boards.
Table 12-2 Availability of the ATPC feature Feature ATPC Applicable Board IF1A/IF1B (all the versions) IF0A/IF0B (all the versions) IFX (all the versions) IFH2 (all the versions) Applicable Equipment IDU 605 IDU 610/620 IDU 620

The ATPC feature is related to the XPIC and Hybrid microwave features.
l
The transmit power of the two ODUs that are in an XPIC working group should be the same if possible. Hence, each of the ATPC parameters (ATPC enable status, ATPC upper threshold, ATPC lower threshold, and ATPC adjustment) should be set to the same value for the IF boards that are in an XPIC working group. In the case of the Hybrid microwave, the AM switching is controlled through detection of the change in the ATPC information and returned microwave message.

The OptiX RTN 600 uses the ATPC overhead in the microwave frame to realize the ATPC function.
Issue 02 (2009-02-25)
12-3
Figure 12-1 ATPC realization principle

Transmitter Receiver RSL out of ATPC adjustment range
Microwave frame (ATPC overhead indicates to adjust the transmit power) Adjust the ODU power once according to the ATPC adjustment step Microwave frame (ATPC overhead indicates to adjust the transmit power) Adjust the ODU power once according to the ATPC adjustment step
Microwave frame (ATPC overhead indicates not to adjust the transmit power)
RSL within ATPC adjustment range
Does not adjust the ODU power
The realization principle is as follows: 1. 2. The receiver detects the RSL. After the ATPC function is enabled, when the RSL is lower than the lower ATPC threshold or higher than the upper ATPC threshold, the receiver sets the ATPC overhead in the microwave frame to be sent to the transmitter, to indicate an increase or decrease in the transmit power.
NOTE
To prevent continuous adjustment to ODU power at the transmit end from occupying a large number of resources, the receiver does not set the ATPC overhead in each microwave frame to indicate an increase or decrease in the transmit power. Instead, the receiver sets the ATPC overhead every several microwave frames.
3. 4.
The transmitter detects the ATPC overhead in the received microwave frame. When the transmitter detects that the ATPC overhead in a microwave frame indicates an increase or decrease in the transmit power, the transmitter increases or decreases the transmit power of the ODU according to the preset ATPC adjustment step. When the receiver detects that the RSL is within the ATPC adjustment range, the receiver sets the ATPC overhead in the microwave frame again to make the ATPC overhead indicate not to adjust the transmit power.
5.
12-4
Issue 02 (2009-02-25)
6.
When the transmitter does not detect the ATPC overhead that indicates an increase or decrease in the transmit power, the transmitter does not change the transmit power of the ODU.
12.5 Planning Guide

Plan the ATPC parameters according to the situation of the microwave links.
Prerequisite
You must have an understanding of the microwave links.
Procedure
Plan ATPC parameters. Adhere to the following principles when planning ATPC parameters:
l l l
Set ATPC parameters consistent at the two sides of a hop of microwave link. It is recommended that you disable the ATPC function for areas where fast fading is severe. To prevent that the RSL is lower than the receiver sensitivity caused by sudden fast fading, set the ATPC lower threshold 10 dB or more higher than the receiver sensitivity. Generally, the ATPC upper threshold should be 20 dB to 30 dB higher than the ATPC lower threshold, and must not be less than 15 dB. If the difference between the upper threshold and the lower threshold is big, the number of ATPC adjustments can be reduced and the system load can also be reduced. If the difference between the upper threshold and the lower threshold is small, the transmit power can be adjusted in a timely manner and the interference to adjacent systems can be reduced. It is recommended that you set the ATPC adjustment step to 5 dB.
----End
12.6 Configuring the ATPC Function

To configure the ATPC function, set the ATPC attributes of the IF board.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The related IF board must be added.
Precautions
l
In the case of the IF boards that are configured with the 1+1 protection, set only the ATPC attributes of the main IF board. The following procedure describes the configuration of ATPC parameters in the IF interface configuration dialog box of the IF board. You can also set ATPC parameters in the following configuration dialog boxes:
Issue 02 (2009-02-25)

Create an XPIC working group IF/ODU configuration
NOTE
In the IF/ODU configuration dialog box, the ATPC adjustment thresholds cannot be modified.
Procedure
Step 1 Select the IF board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the ATPC Attributes tab. Step 3 Set the ATPC attributes.
NOTE
The IF0 board of the IDU 605 1A/1B/2B does not support the ATPC Auto Enable.
Parameters
Parameter ATPC Enable Status Value Range Enabled, Disabled Default Value Disabled Description
l
This parameter specifies whether the ATPC function is enabled. The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. In the case of areas where fast fading is severe, it is recommended that you set this parameter to Disabled.
12-6
Issue 02 (2009-02-25)
Parameter ATPC Upper Threshold (dBm)
Value Range -20 to -75
Default Value -45
Description
l
When the ATPC function is enabled, if the RSL at the receive end is higher than the preset ATPC upper threshold at the receive end, the receiver notifies the transmitter to decrease the transmit power according to the preset ATPC adjustment step at the transmit end until the RSL is lower than the ATPC upper threshold. Generally, ATPC Upper Threshold (dBm) should be 20 dB to 30 dB higher than ATPC Lower Threshold (dBm), and must not be less than 15 dB. If the difference between the upper threshold and the lower threshold is big, the number of ATPC adjustments is reduced and the system load is also reduced. If the difference between the upper threshold and the lower threshold is small, the transmit power is adjusted in a timely manner and the interference to adjacent systems is reduced. When the ATPC function is enabled, if the RSL at the receive end is lower than the preset ATPC lower threshold, the receiver notifies the transmitter to increase the transmit power according to the preset ATPC adjustment step at the transmit end until the RSL is higher than the ATPC lower threshold. Generally, set this parameter to a value of 10 dB or greater than the receiver sensitivity to prevent sudden fast fading because sudden fast fading makes the RSL value lower than the receiver sensitivity. This parameter specifies the variation in the transmit power caused by one ATPC adjustment. It is recommended that you use the default value.
ATPC Lower Threshold (dBm)
-35 to -90
-70
ATPC Adjustment (dB)
1 to 5
Issue 02 (2009-02-25)
12-7
Parameter ATPC Auto Enable
Value Range Enabled, Disabled
Default Value Enabled
Description
l
The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. When the function is enabled, the manually set ATPC upper and lower thresholds are invalid. The equipment automatically uses the preset ATPC upper and lower thresholds based on the working mode of the IF board. When the function is disabled, the manually set ATPC upper and lower thresholds are used. The IF0 board of the IDU 605 1A/1B/2B does not support the ATPC Auto Enable.
NOTE
l l
Each of the ATPC parameters must be set to the same value at the two ends of a microwave link. During commissioning, set ATPC Enable Status to Disabled to ensure that the transmit power is not changed. After the commissioning, re-set the ATPC attributes.

This topic describes the alarms and performance events relevant to the ATPC function, and the problems that occur frequently during the application of the ATPC function. 12.7.1 Relevant Alarms and Events When the ATPC adjustment occurs, the related performance events are reported. 12.7.2 FAQs This topic lists the problems that occur frequently during the application of the ATPC function.

When the ATPC adjustment occurs, the related performance events are reported.
Relevant Alarms
None.
Relevant Performance Events

l l
ATPC_P_ADJUST stands for the positive ATPC adjustment event. ATPC_N_ADJUST stands for a negative ATPC adjustment event.
12-8
Issue 02 (2009-02-25)
12.7.2 FAQs
This topic lists the problems that occur frequently during the application of the ATPC function. Q: When the ATPC function is enabled, why is the RSL sometimes out of the ATPC threshold range? A: Possible causes are as follows:
l
The ATPC function is during the break time. To prevent continuous adjustments from occupying a large amount of system resources, the ATPC function does not always adjust the transmit power. There is a break between ATPC adjustments (the break time is about five minutes). Hence, the RSL may be out of the ATPC threshold range during the break time. The RSL falls within the ATPC threshold range after the break time.
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 out 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-02-25)
12-9
13 Hybrid Microwave
13
About This Chapter
Hybrid Microwave
The Hybrid microwave refers to the microwave that transmits E1 services and Ethernet services. 13.1 Feature Description This topic describes the application of the Hybrid microwave feature. 13.2 Basic Concepts This topic describes the basic concepts you need to be familiar with before you use the Hybrid microwave feature. 13.3 Availability The Hybrid microwave feature requires the support of the applicable equipment and boards. 13.4 Relation with Other Features The Hybrid microwave feature has relations with the 1+1 protection configuration, N+1 protection configuration, ATPC, XPIC, flow control, QoS, and LAG. 13.5 Realization Principle This topic describes the principle of the AM switching of the Hybrid microwave. 13.6 Planning Guide Focus on planning the AM attributes and QoS control when you plan the Hybrid microwave feature. 13.7 Configuration Guide The application of the Hybrid microwave requires the configuration of the AM attributes and QoS in addition to the configuration of the Hybrid microwave service. 13.8 Maintenance Guide This topic describes the configuration tasks relevant to the Hybrid microwave feature.
Issue 02 (2009-02-25)
13-1
13 Hybrid Microwave

This topic describes the application of the Hybrid microwave feature. Figure 13-1 shows the functional block diagram of the Hybrid microwave feature. E1 services and Ethernet services are multiplexed into Hybrid microwave frames at the local MUX unit. Then, the Hybrid frames are transmitted to the opposite end by the transmitter after being modulated by the MODEM unit. After the receiver at the opposite end receives the signals, the MODEM unit at the opposite end demodulates the signals into Hybrid microwave frames, which are finally separated into E1 services and Ethernet services by the DEMUX unit. Figure 13-1 Application of the Hybrid microwave feature
Ethernet E1 OH Ethernet E1 OH
E1 MUX Ethernet Microwave frame MODEM Transmitter Receiver MODEM Microwave frame DMUX
E1
Ethernet
OH: Overheads of the Hybrid microwave frame
The Hybrid microwave feature of the OptiX RTN 600 realizes optimization for service reliability and service capacity by using technologies such as combined transmission of E1 services and Ethernet services, adaptive modulation (AM), and Ethernet QoS control.
13.2 Basic Concepts

This topic describes the basic concepts you need to be familiar with before you use the Hybrid microwave feature. 13.2.1 Service Transmission Mode In the case of the Hybrid microwave, different Hybrid microwave frames are defined for different work modes. The accessed E1 services and Ethernet services are multiplexed into one Hybrid microwave frame. 13.2.2 AM The Hybrid microwave supports the AM technology. With the application of the AM technology, the Hybrid microwave uses the high-efficiency modulation scheme when the channel is of better quality. Hence, more user services can be transmitted and thus the transmission efficiency and spectrum utilization are improved. When the quality of the channel is degraded, the Hybrid microwave uses the low-efficiency modulation scheme, in which only the services of a high priority are transmitted. Hence, the anti-interference capability of links is enhanced and availability of the links on which the high-priority services are transmitted is ensured. 13.2.3 Working Mode When the AM function is enabled for the Hybrid microwave, the Hybrid microwave can select the best working mode from the working modes that are already set by the user according to the
13 Hybrid Microwave
condition of the channel. When the AM function is disabled, the Hybrid microwave uses the working mode that is set by the user. 13.2.4 QoS Control for Ethernet Services The Hybrid microwave provides various functions to ensure that Ethernet services can meet the requirements of variable transmission bandwidth due to the application of the AM technology, and thus to ensure the QoS of services.
13.2.1 Service Transmission Mode

In the case of the Hybrid microwave, different Hybrid microwave frames are defined for different work modes. The accessed E1 services and Ethernet services are multiplexed into one Hybrid microwave frame. The characteristics of the Hybrid microwave frame are as follows:
l l
The Hybrid microwave frame is transmitted at a fixed interval. The Hybrid microwave frame remains the frame length unchanged in the case of a certain modulation scheme or bandwidth. The E1 services that are multiplexed into the Hybrid microwave frame use a certain proportion of the bandwidth of this Hybrid microwave frame. That is, the bandwidth used by these E1 services in the Hybrid microwave frame is equal to the total bandwidth of these E1 services. Hence, characteristics of these E1 services transmitted over Hybrid microwave frames are the same as the characteristics of the E1 services transmitted over PDH microwave, and the TDM feature of the E1 services is not affected in the case of Hybrid microwave transmission. The Ethernet services that are multiplexed into the Hybrid microwave frame use the remaining bandwidth of this Hybrid microwave frame. This does not affect the Ethernet services because the Ethernet frames undergo certain encapsulation and adaptation processes. See Figure 13-2.
Figure 13-2 Multiplexing E1 services and Ethernet services into the Hybrid microwave frame
T
OH E1 E1 Ethernet
Features of Hybrid Microwave Service Access

Compared with the method of the IDU 605 1F/2F for accessing Hybrid microwave services, the IDU 620 accesses Hybrid microwave services in a different manner.
l
In the case of E1 services:
The IDU 620 accesses E1 services through the E1 service interface board, SDH/PDH service interface board, and microwave IF board in the other directions. The IDU 605 1F/2F accesses E1 services through the E1 service interface unit. The IDU 620 accesses Ethernet services through the FE interface or GE interface of the EMS6 board, or through the GE interface of the IFH2 board.
In the case of Ethernet services:
Issue 02 (2009-02-25)
13 Hybrid Microwave
The IDU 605 1F/2F accesses Ethernet services through the Ethernet interface of the equipment.
13.2.2 AM
The Hybrid microwave supports the AM technology. With the application of the AM technology, the Hybrid microwave uses the high-efficiency modulation scheme when the channel is of better quality. Hence, more user services can be transmitted and thus the transmission efficiency and spectrum utilization are improved. When the quality of the channel is degraded, the Hybrid microwave uses the low-efficiency modulation scheme, in which only the services of a high priority are transmitted. Hence, the anti-interference capability of links is enhanced and availability of the links on which the high-priority services are transmitted is ensured. E1 services are of the highest priority in the AM-based Hybrid microwave transmission. Ethernet services are classified into flows of different priorities based on the CoS technology. When the Hybrid microwave uses the lowest-efficiency modulation scheme, the equipment transmits E1 services only (if the service bandwidth is higher than the total bandwidth of the E1 services, the Ethernet services of a high priority can be transmitted). When the Hybrid microwave uses other modulation schemes, the increased bandwidth can be used to transmit Ethernet services. In this case, availability of the links on which the E1 services and Ethernet services of a high priority are transmitted can be ensured and the capacity for transmitting Ethernet services increases. Figure 13-3 shows the working principle of the Hybrid microwave that uses the AM technology. Figure 13-3 Working principle of the Hybrid microwave
256QAM QPSK 16QAM 64QAM 128QAM 256QAM Channel capability E1 services Ethernet services
Figure 13-3 shows the transmission mode of the Hybrid microwave. The orange column represents E1 services, and the blue column represents Ethernet services. When an Ethernet service is nearer the edge of the column, the priority of this Ethernet service is lower. As shown in Figure 13-3, the E1 services use a constant bandwidth irrespective of the real-time condition of the channel. Hence, the availability of E1 services is ensured. The bandwidth of the Ethernet services is variable depending on the condition of the channel. When the quality of the channel is degraded, the Ethernet services of a low priority are discarded.

NOTE
13 Hybrid Microwave
When only the Ethernet services are transmitted over the Hybrid microwave, the bandwidth originally used by the E1 services as shown in Figure 13-3 is allocated to the Ethernet services of a high priority.
The features of the AM function are as follows: 1. 2. 3. The AM function switches the modulation scheme step by step. The highest-efficiency modulation scheme and lowest-efficiency modulation scheme can be configured. The AM function retains the transmit frequency, receive frequency, and channel spacing when switching the modulation scheme. AM Mode is Asymmetric, an AM switching in one direction of the radio link does not trigger the AM switching in the other direction of the radio link.
13.2.3 Working Mode

When the AM function is enabled for the Hybrid microwave, the Hybrid microwave can select the best working mode from the working modes that are already set by the user according to the condition of the channel. When the AM function is disabled, the Hybrid microwave uses the working mode that is set by the user.
Radio Work Mode

Table 13-1 Radio work modes in the case of hybrid microwave frames Channel Spacing (MHz)a, b 7 7 7 7 7 7 14 (13.75) 14 (13.75) 14 (13.75) 14 (13.75) 14 (13.75) 14 (13.75) 28 (27.5) 28 (27.5) 28 (27.5)
Issue 02 (2009-02-25)
Modulation Scheme QPSK 16QAM 32QAM 64QAM 128QAM 256QAM QPSK 16QAM 32QAM 64QAM 128QAM 256QAM QPSK 16QAM 32QAM
Service Capacity (Mbit/s) 10 20 25 32 38 44 20 42 51 66 78 90 42 84 105
Maximum Number of E1s in servicec 5 10 12 15 18 21 10 20 24 31 37 43 20 40 50

13-5
13 Hybrid Microwave
Channel Spacing (MHz)a, b 28 (27.5) 28 (27.5) 28 (27.5) 56 56 56 56 56 56 40d
Modulation Scheme 64QAM 128QAM 256QAM QPSK 16QAM 32QAM 64QAM 128QAM 256QAM 64QAM
Service Capacity (Mbit/s) 133 158 183 84 168 208 265 313 363 -
Maximum Number of E1s in servicec 64 75 75 40 75 75 75 75 75 75
NOTE
l l l
a: The channel spacings 13.75 MHz and 27.5 MHz are applied to the 18 GHz frequency band. b: The channel spacings listed in the table are the minimum channel spacings supported by the OptiX RTN 600. The channel spacings larger than the values are also supported. c: The E1 services consume the corresponding bandwidth of the service capacity. After the E1 service capacity is deducted from the service capacity, the remaining bandwidth of the service capacity can be used for the Ethernet services. d: This modes are the super PDH modes that do not support the transmission of Ethernet services.
13.2.4 QoS Control for Ethernet Services

The Hybrid microwave provides various functions to ensure that Ethernet services can meet the requirements of variable transmission bandwidth due to the application of the AM technology, and thus to ensure the QoS of services. The AM function of the Hybrid microwave is related to the QoS processing for services. In the case of an AM switching, services should be processed according to different QoS levels and services of higher priority should lose any packet.
QoS Control of the IDU 620

In the case of the QoS control implemented by the IDU 620, two cases are available. When only the IFH2 board is used, the QoS control of the IDU 620 supports the following functions:
l l
Flow classification that complies with IEEE 802.1p. Four-level priority SP queue scheduling
When the EMS6 and IFH2 boards are used, the QoS control of the IDU 620 supports the following functions in addition to the functions that are supported when only the IFH2 board is used:

l
13 Hybrid Microwave
Flow classification The following flow classification modes are supported.

Flow classification based on PORT Flow classification based on PORT+CVLAN Flow classification based on PORT+SVLAN Flow classification based on PORT+CVLAN+SVLAN
l l l
CAR based on the flow CoS based on the flow Traffic shaping based on PORT
When the bandwidth on the air interface of the IDU 620 changes, the EMS6 is informed of this change through the in-band packet so that the EMS6 can control the bandwidth on the port.
NOTE
For details about the Ethernet QoS, see 21 QoS.
QoS Control of the IDU 605 1F/2F

The QoS control of the IDU 605 1F/2F is realized through the internal logic unit of the equipment. The QoS control of the IDU 605 1F/2F supports the following functions:
l l l
Flow classification based on PORT CAR based on the flow CoS based on the flow The CoS can be classified based on the VLAN priority or DSCP. Egress queue scheduling based on SP and WRR
13.3 Availability
The Hybrid microwave feature requires the support of the applicable equipment and boards. Table 13-2 Availability of the Hybrid microwave feature Feature Hybrid microwave Applicable Board IFH2 (all the versions) Applicable Equipment IDU 605 1F/2F IDU 620

The Hybrid microwave feature has relations with the 1+1 protection configuration, N+1 protection configuration, ATPC, XPIC, flow control, QoS, and LAG.
l
The Hybrid microwave feature is related to the IF 1+1 protection. Consider the IDU 620 as an example. If the Hybrid microwave requires the IF 1+1 protection, the EMS6 board is required. For how to connect the cables, see Figure 13-4.
Issue 02 (2009-02-25)
13 Hybrid Microwave
Figure 13-4 Cable connection when the 1+1 protection is configured for the Hybrid microwave
Network cable To the external equipment
IFH2 FAN
Slot 20
EMS6
Slot 8 Slot 6 Slot 4
IFH2 PXC PXC
SCC
Slot 2
IDU 620
l l
The Hybrid microwave supports the 1+1 HSB. For details, see 7 1+1 HSB. The Hybrid microwave supports the 1+1 FD. For details, see 8 1+1 FD. The Hybrid microwave supports the 1+1 SD. For details, see 9 1+1 SD.
The Hybrid microwave does not support the IF N+1 protection. The Hybrid microwave controls the transmit power of the ODU through the ATPC function. For details about the ATPC function, see 12 Automatic Transmit Power Control Function. The Hybrid microwave does not support the XPIC function. Ethernet services transmitted over the Hybrid microwave complies with the protocols that are related to the flow control function. For details about the flow control function, see 17.2.3 Flow Control Function. The Hybrid microwave controls the quality of the Ethernet services through the QoS function. For details about the QoS function, see 21 QoS. The Hybrid microwave realizes the IF 1+1 protection through the LAG function. For details about the LAG function, see 25 Link aggregation.
l l

This topic describes the principle of the AM switching of the Hybrid microwave. The AM engine is the core for controlling the AM switching. On the one hand, the AM engine communicates with the remote AM engine through the information channel that is provided by the radio link so that the transmit end is informed of the quality of the signals at the receive end. On the other hand, the AM engine determines the attributes of the modulation scheme that is switched to, based on the real-time quality of the link. When the switching of modulation scheme is required, the AM engine sends the AM switching indication signal to the Tx path.
AM Working Principle (Before the Switching)

1. The E1 services and Ethernet services are multiplexed into Hybrid microwave frames at the MUX unit.
13-8
13 Hybrid Microwave
2. 3.
The Hybrid microwave frames are transmitted to the opposite end over the Tx path after being modulated by the IF unit. The opposite end receives the IF signals from the Rx path. In addition, the opposite end checks the quality of the received signals based on the received signal to noise ratio (SNR). In the current working modulation scheme, the opposite end determines that the quality of the received signals is degraded if the value of the received SNR is lower than the threshold. Then, the opposite end sends signal quality indication signal to the AM engine. The AM engine at the opposite end sends the Hybrid microwave frame to the local end after the switching indication signal is placed into the overhead of the Hybrid microwave frame. The IF unit at the local end processes the received IF signals and sends the AM switching indication signal to the AM engine at the local end. The AM engine at the local end sends the switching indication signal to the service signal processing unit and IF signal modulation unit. Hence, the service signal transmission unit and IF signal modulation unit perform the switching of service frames and modulation schemes after N frames. See Figure 13-5.
4.
5. 6.
Figure 13-5 AM switching (before the switching)

Ethernet NxE1 OH
IF unit
Ethernet E1 MUX unit Microwave frame Tx path
IF unit
Rx path INDI AM engine INDI MUX unit Ethernet E1 Microwave frame MUX unit Ethernet E1
INDI AM engine SNR Ethernet E1 MUX unit INDI Rx path
AM message
SNR
Microwave frame
Tx path
Microwave frame
SNR: signal to noise ratio
INDI: Modulation scheme indication signal
AM Working Principle (After the Switching)

1. The bandwidth of the E1 services in the Hybrid microwave frame does not change after the modulation scheme changes. The multiplexing of Ethernet services of a high priority into the Hybrid microwave frame can be ensured because the Ethernet services are scheduled to different queues according to their priority levels. The remaining bandwidth of the Hybrid microwave frame can transmit the Ethernet services of a low priority. Due to the switching to the lower-efficiency modulation scheme, the bandwidth of the Ethernet services that are multiplexed at the MUX unit decreases. As a result, the bandwidth of the Hybrid microwave frame decreases. See Figure 13-6.
2.
Issue 02 (2009-02-25)
13-9
13 Hybrid Microwave
Figure 13-6 AM switching (after the switching)

Ethernet NxE1 OH
IF unit
Ethernet E1 MUX unit Microwave frame Tx path
IF unit
Rx path INDI AM engine INDI Tx path Microwave frame MUX unit Ethernet E1 Microwave frame MUX unit Ethernet E1
INDI AM engine SNR Ethernet E1 MUX unit INDI Rx path Microwave frame SNR: signal to noise ratio
AM Messages
SNR
INDI: Modulation scheme indication signal
3.
The change of modulation schemes implemented through the AM function is based on the frame boundary of the signal. The Rx path of the receive end sends the signal indicating the receive mode change of the current frame to the MUX unit when detecting the change of the modulation scheme. Hence, the MUX unit receives and processes service signals according to the new modulation scheme.
13.6 Planning Guide

Focus on planning the AM attributes and QoS control when you plan the Hybrid microwave feature.
Prerequisite
l
You must be familiar with the service condition and microwave environment of the Hybrid microwave feature. You must be familiar with the functions of the Hybrid microwave feature.
Procedure
Step 1 Determine whether the AM function is required. l If the Ethernet service needs to meet the requirement of the E1 service for availability, it is recommended that you do not enable the AM function. In addition, you need to determine a fixed modulation scheme according to the requirement for availability and the maximum service capacity. If the Ethernet service need not meet the requirement of the E1 service for availability (that is, a certain bandwidth can be discarded when the quality of the Ethernet signal is degraded), it is recommended that you enable the AM function.
Step 2 Optional: Plan the AM attributes. Adhere to the following principles when planning the AM attributes:

l
13 Hybrid Microwave
The bandwidth in the modulation scheme of the assured capacity should not be less than the sum of the bandwidth of the E1 services to be transmitted and the committed bandwidth of the Ethernet services that have the availability equal to the availability of the E1 service, such as the VoIP service and routing protocol packet. In this modulation scheme, the radio link should meet the requirement of these services for availability. The bandwidth in the modulation scheme of the full AM capacity should be more than the sum of the E1 services to be transmitted and the committed bandwidth of all the Ethernet services. In this modulation scheme, the radio link should meet the requirement of the Ethernet service that requires lower availability for availability.
Step 3 Optional: Plan the QoS function of the Ethernet services. Adhere to the following principles when planning the QoS function:
l
Work out the general QoS planning according to different QoS functions supported by the Hybrid microwave in the case of different configurations. It is recommended that you enable the CoS function for the Ethernet service ports on which the Hybrid microwave feature is enabled. Schedule the Ethernet service of a high priority to the queue of a high priority and the Ethernet service of a low priority to a queue of a low priority. Enable the CAR function for the Ethernet service ports that access Ethernet services. Hence, you can prevent the traffic accessed at these ports from exceeding the maximum traffic allocated to the Ethernet services by the Hybrid microwave feature.
----End

The application of the Hybrid microwave requires the configuration of the AM attributes and QoS in addition to the configuration of the Hybrid microwave service. When you configure the Hybrid microwave, do as follows:
l
For details on how to configure the Hybrid microwave service for the IDU 620, see in the OptiX RTN 600 IDU 610/620 Configuration Guide. For details on how to configure the Hybrid microwave service for the IDU 605, see in theOptiX RTN 600 IDU 605 Configuration Guide.

This topic describes the configuration tasks relevant to the Hybrid microwave feature. 13.8.1 Relevant Alarms and Events This topic lists the alarms and performance events that are only related to the Hybrid microwave when it is compared with the SDH/PDH microwave. 13.8.2 FAQs This topic lists the problems that occur frequently during the application of the Hybrid microwave feature.
Issue 02 (2009-02-25)
13-11
13 Hybrid Microwave

This topic lists the alarms and performance events that are only related to the Hybrid microwave when it is compared with the SDH/PDH microwave.
Relevant Alarms
PROT_CONN_ERR PROT_CONN_ERR indicates the abnormal connection of protection groups.
Relevant Performance Events

For RMON performance events, see 23.2.3 RMON Alarms and Performance Events. Other performance events related to the Hybrid microwave are as follows:
l l
QPSKWS: indicates the working second in the case of the QPSK modulation scheme. QAMWS16: indicates the working second in the case of the QAMWS16 modulation scheme. QAMWS32: indicates the working second in the case of the QAMWS32 modulation scheme. QAMWS64: indicates the working second in the case of the QAMWS64 modulation scheme. QAMWS128: indicates the working second in the case of the QAMWS128 modulation scheme. QAMWS256: indicates the working second in the case of the QAMWS256 modulation scheme.
13.8.2 FAQs
This topic lists the problems that occur frequently during the application of the Hybrid microwave feature. Q: What should be done when the modulation scheme switching of the Hybrid microwave fails? 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 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.
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.
13-12
Issue 02 (2009-02-25)

l
13 Hybrid Microwave
The user incorrectly considers that the receiver sensitivity is related to the AM switching. AM switching is realized through the detection of the SNR other than the detection of the RSL. If the SNR exceeds the specified threshold, the AM switching occurs though the RSL is higher than the receiver sensitivity.
Issue 02 (2009-02-25)
13-13
14 Sub-Network Connection Protection
14
Sub-Network Connection Protection
About This Chapter

The sub-network connection protection (SNCP) scheme protects the services that are across subnets. The subnet can be a chain, a ring, or a more complicated network. The OptiX IDU 610 supports a maximum of 84 SNCP groups and the OptiX IDU 620 supports a maximum of 210 SNCP groups. 14.1 Feature Description This topic considers the application of the SNCP as an example to describe the SNCP feature. 14.2 Basic Concepts This topic describes the basic concepts that you should be familiar with before you use the SNCP protection scheme. 14.3 Availability The SNCP solution requires the support of the applicable equipment and boards. 14.4 Relation with Other Features SNCP is related to the MSP, 1+1 protection, N+1 protection, XPIC, and Hybrid features. 14.5 Realization Principle SNCP is realized based on the dual fed and selective receiving mechanism. 14.6 Planning Guide In the case of a ring network (except service-distributed STM-4 or higher-rate ring networks) or a ring with chain network that comprises the OptiX RTN 600, it is recommended that you adopt SNCP as the protection scheme. When planning SNCP, first plan the trails of the working SNC and the protection SNC, and then plan the parameters. 14.7 Configuration Guide This topic describes the configuration tasks related to SNCP services. 14.8 Maintenance Guide This topic describes how to carry out an SNCP switching, relevant alarms and events, and the problems that occur frequently during the application of the protection feature.
Issue 02 (2009-02-25)
14-1

This topic considers the application of the SNCP as an example to describe the SNCP feature. The SNCP protection scheme, which requires one working subnetwork and one protection subnetwork, is to select one service from the dually transmitted services. The SNCP is applicable to the ring, intersecting rings, ring with a chain, or mesh network. Figure 14-1 shows the application of the SNCP. Figure 14-1 Sub-Network Connection Protection
Working SNC Trail source Trail sink
NE A Protection SNC
NE B
Protection switching
NE A Protection SNC
NE B
14.2 Basic Concepts

This topic describes the basic concepts that you should be familiar with before you use the SNCP protection scheme. 14.2.1 Protection Type SNCP is classified into the revertive mode and the non-revertive mode. 14.2.2 SNCP Service Pair An SNCP service pair is a basic unit of SNCP. It consists of a working source, a protection source, and a service sink.
14.2.3 Switching Condition The switching priority varies according to the switching condition. 14.2.4 Switching Impact The services are interrupted within the SNCP switching time (shorter than 50 ms).

SNCP is classified into the revertive mode and the non-revertive mode.
l
14.2.2 SNCP Service Pair

An SNCP service pair is a basic unit of SNCP. It consists of a working source, a protection source, and a service sink. Figure 14-2 SNCP service pair
Working source Protection source
Service sink
The working source and the protection source can be of the fiber line, STM-1e cable, or radio link, and can be of different line types. The service sink can be of any line or tributary type.

The switching priority varies according to the switching condition. Table 14-1 Switching conditions of SNCP 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.
Issue 02 (2009-02-25)
14-3
Switching Condition Lockout of protection (external switching)
Priority
Description The lockout of protection blocks normal traffic signals from entering the protection channel but does not block traffic signals from being switched from the protection channel to the working channel. The signal fail condition in the protection channel is equivalent to the lockout of protection. If a switching is in the lockout state, no forced switching occurs. Otherwise, the system switches services from the working SNC to the protection SNC or from the protection SNC to the working SNC according to the command. The switching then enters the forced switching state. If a switching is in the lockout or forced switching state, or if the signal of the protection SNC fails, no switching occurs. Otherwise, the system switches services from the working SNC to the protection SNC. The switching then enters the automatic switching state. For the trigger conditions of the automatic switching, see Table 14-2 and Table 14-3. If a 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 according to the command. The switching then enters the manual switching state.
Signal failure
14-4
Issue 02 (2009-02-25)
Priority
Description When the switching is in the automatic state and the working SNC is already restored to normal for the WTR time, a revertive switching occurs. From the time the working SNC is restored to normal to the time the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching enters the normal state.
NOTE
In the case of the revertive SNCP, if the services are currently on the protection trails, the services cannot be switched to the working trails when you perform the forced switching or manual switching.
Table 14-2 Trigger conditions of the automatic SNCP switching (VC-4 services) Switching Condition The hardware of the line board is faulty. R_LOS R_LOF R_LOC MS_AIS B2_EXC AU_LOP AU_AIS HP_LOM MW_LOF MW_LIM B3_EXC B3_SD HP_TIM HP_UNEQ
Issue 02 (2009-02-25)
Description Default condition Default condition Default condition Default condition Default condition Default condition Default condition Default condition Default condition Default condition (only if the IF board works as a line board) Default condition (only if the IF board works as a line board) Optional condition Optional condition Optional condition Optional condition
14-5

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. For the setting method, see 14.7.2 Setting the Automatic Switching Conditions of SNCP Services. By default, the optional conditions do not work as a switching condition.
Table 14-3 Trigger conditions of the automatic SNCP switching (VC-3/VC-12 services) Switching Condition The hardware of the line board is faulty. R_LOS R_LOF R_LOC MS_AIS B2_EXC AU_LOP AU_AIS HP_LOM MW_LOF MW_LIM TU_AIS TU_LOP Description Default condition Default condition Default condition Default condition Default condition Default condition Default condition Default condition Default condition Default condition (only if the IF board works as a line board) Default condition (only if the IF board works as a line board) Default condition Default condition

The services are interrupted within the SNCP switching time (shorter than 50 ms).
14.3 Availability
The SNCP solution requires the support of the applicable equipment and boards. Table 14-4 Availability of the SNCP solution Feature SNCP Applicable Board IF1A/IF1B (all the versions) SL1/SD1 (all the versions) SLE/SDE (all the versions)
Applicable Equipment IDU 610/620
Feature
Applicable Board IFX (all the versions) SL4 (all the versions)
Applicable Equipment IDU 620

SNCP is related to the MSP, 1+1 protection, N+1 protection, XPIC, and Hybrid features.
l
The MSP line can work only as the service sink of an SNCP service pair and cannot work as the working source or the protection source. The radio link with the 1+1 protection configuration can work only as the service sink of an SNCP service pair, and cannot work as the working source or the protection source. The radio link with the N+1 protection configuration can work only as the service sink of an SNCP service pair, and cannot work as the working source or the protection source. The radio link with the XPIC configuration can work only as the service sink of an SNCP service pair, and cannot work as the working source or the protection source. The Hybrid radio link can work only as the service sink of an SNCP service pair, and cannot work as the working source or the protection source.

SNCP is realized based on the dual fed and selective receiving mechanism.
NOTE
The following describes the switching principle of SNCP. The switching triggered by the signal failure of the working SNC is provided as an example.
Figure 14-3 SNCP realization principle (before the switching)

NE A Protection SNC
NE B
Issue 02 (2009-02-25)
14-7
Figure 14-4 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 both the working SNC and the protection SNC. On detecting that the signal of the working SNC fails, the line board of NE B reports the event to the SCC board. After confirming that the signal of the working SNC fails and that the signal of the protection SNC is normal, the SCC board of NE B enables the cross-connect board to complete the cross-connection between the protection SNC and the service sink.
14.6 Planning Guide

In the case of a ring network (except service-distributed STM-4 or higher-rate ring networks) or a ring with chain network that comprises the OptiX RTN 600, it is recommended that you adopt SNCP as the protection scheme. When planning SNCP, first plan the trails of the working SNC and the protection SNC, and then plan the parameters.
Procedure
Step 1 Plan the trails of the working SNC and the protection SNC. Adhere to the following principles when planning the trails:
l l
Do not overlap the working SNC and the protection SNC if possible. The OptiX RTN 600 does not support the line with the MSP, 1+1 protection configuration or N+1 protection configuration as the working source or the protection source of SNCP. It is recommended that the working SNC uses the line ports of one line board and the protection SNC uses those of another line board to prevent the situation in which the failure of a line board causes the protection to fail. If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the value to ten minutes.
Step 2 Plan the parameters relevant to the protection configuration.

l
----End

This topic describes the configuration tasks related to SNCP services. 14.7.1 Creating Cross-Connections for SNCP Services The cross-connection of SNCP services is a cross-connection that a working source and a protection source correspond to a service sink. 14.7.2 Setting the Automatic Switching Conditions of SNCP Services In the case of the SNCP services at the VC-4 level, you can set certain alarms as the automatic switching conditions. 14.7.3 Converting Normal Services into SNCP Services After converting the normal services into the SNCP services, you can convert the unidirectional cross-connection of the normal services into the unidirectional cross-connection in the receive direction of the SNCP services. 14.7.4 Converting SNCP Services into Normal Services After converting the SNCP services into the normal services, you can convert the SNCP crossconnection in the receive direction into the unidirectional cross-connection of the normal services.
14.7.1 Creating Cross-Connections for SNCP Services

The cross-connection of SNCP services is a cross-connection that a working source and a protection source correspond to a service sink.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The boards where the source and the sink are must be configured.
Precautions
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Cross-Connection Configuration from the Function Tree. Step 2 Optional: Click Scheme to change the VC-12 timeslot numbering policy used by the crossconnection.
Step 3 Click Create SNCP. The system displays the Create SNCP Service dialog box.
Step 4 Set the attributes of the SNCP protection group and the slot mapping relation of the SNCP service.
Step 5 Click OK.

NOTE
l l
When you create a cross-connection whose source or sink is the timeslots of an IF board, the creation may fail due to the limited number of licenses. The calculation of the required number of licenses is based on the total number of service timeslots of all the IF boards that are involved in cross-connections. In the case of the cross-connections of VC-3 or VC-4 services, the VC-3 or VC-4 services need to be converted into E1 services that have the same capacity. For example, the cross-connections of one E3 service from a PL3 board to an IF board require the number of licenses that are used for 21xE1. One VC-3 pass-through service between two IF boards requires the number of licenses that are used for 42xE1. The 8xE1 SNCP services from two IF boards to one PO1 board require the number of licenses that are used for 16xE1.
----End
Parameters
Parameter Service Type Value Range SNCP Default Value SNCP Description -
14-10
Issue 02 (2009-02-25)
Parameter Level
Value Range VC12, VC3, VC4
Default Value VC12
Description
l
Specifies the level of the crossconnection to be created. If the service is an E1 service or a data service that is bound with VC-12 paths, set this parameter to VC12. If the service is an E3/T3 service or a data service that is bound with VC-3 paths, set this parameter to VC3. If all the services in a VC-4 pass through the NE, set this parameter to VC4. 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 use the default value. When this parameter is set to Unidirectional, only the crossconnections in the SNCP receive direction are created. When this parameter is set to Bidirectional, both the crossconnections in the SNCP receive direction and the cross-connections in the SNCP transmit direction are created. It is recommended that you set this parameter to Bidirectional. When a line fault occurs, an NE can perform SNCP switching after a delay of time to prevent the situation where the NE performs SNCP switching and other protection switching at the same time. This parameter specifies the duration of the delay. It is recommended that you use the default value because the SNCP cannot co-exist with other protection switching modes in the OptiX RTN 600.
Revertive Mode
Non-Revertive, Revertive
Revertive
Direction
Unidirectional, Bidirectional
Unidirectional
Hold-off Time (100ms)
0 to 100
Issue 02 (2009-02-25)
14-11
Default Value 600
Description
l
This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value.
Source Slot Source Port Source VC4 Source Timeslot Range(e.g.1,3-6)
Indicates the source slot of the service. Specifies the port where the service source exists. Specifies the number of the VC-4 where the service source exists.
l
Specifies the timeslot range to which the service source corresponds. You can set this parameter to a number or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. In the case of an IF board that works in the PDH mode, the first to the nth E1s/ E3s transmitted by microwaves correspond to the first to the nth VC-12/ VC-3 timeslots respectively. Similarly, the first to the nth ports of an E1 interface board or an E3/T3 interface board correspond to the first to the nth VC-12/ VC-3 timeslots respectively.
Sink Slot Sink Port Sink VC4
Indicates the sink slot of the service. Specifies the port where the service sink exists. Specifies the number of the VC-4 where the service sink exists.
14-12
Issue 02 (2009-02-25)
Parameter Sink Timeslot Range(e.g.1,3-6)
Value Range -
Default Value -
Description
l
Specifies the timeslot range to which the service sink corresponds. You can set this parameter to a number or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. In the case of an IF board that works in the PDH mode, the first to the nth E1s/ E3s transmitted by microwaves correspond to the first to the nth VC-12/ VC-3 timeslots respectively. Similarly, the first to the nth ports of an E1 interface board or an E3/T3 interface board correspond to the first to the nth VC-12/ VC-3 timeslots respectively.
Postrequisite
If Direction is set to Unidirectional, the cross-connection only in the SNCP receive direction is created. Hence, you need to configure a unidirectional cross-connection between the service and the working trail, and later, a unidirectional cross-connection between the service and the protection trail.
14.7.2 Setting the Automatic Switching Conditions of SNCP Services

In the case of the SNCP services at the VC-4 level, you can set certain alarms as the automatic switching conditions.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. An SNCP protection group at the VC-4 level must be configured.
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. Double-click Initiation Condition to which the working service corresponds. The system displays the Initiation Condition dialog box. Step 3 Select SD switching conditions. Then, click OK.
Step 4 Select the SNCP protection group. Double-click Initiation Condition to which the protection service corresponds. The system displays the Initiation Condition dialog box. Step 5 Repeat Step 3. Step 6 Click Apply. The system displays a prompt box asking you whether to carry out the switching. Step 7 Click Yes. ----End
Parameters
Parameter HPUNEQ Value Range Selected, Not selected Default Value Not selected Description
l
When this item is selected, the SNCP service considers the HP_UNEQ alarm as an SD switching condition. It is recommended that you use the default value. When this item is selected, the SNCP service considers the HP_TIM alarm as an SD switching condition. It is recommended that you use the default value. When this item is selected, the SNCP service considers the B3_SD alarm as an SD switching condition. It is recommended that you use the default value. When this item is selected, the SNCP service considers the B3_EXC alarm as an SD switching condition. It is recommended that you use the default value.
HPTIM
Selected, Not selected
Not selected
B3SD
Not selected
B3EXC
Not selected
NOTE
It is recommended that you set Initiation Condition of the working service to be the same as Initiation Condition of the protection service.
14-14
Issue 02 (2009-02-25)
14.7.3 Converting Normal Services into SNCP Services

After converting the normal services into the SNCP services, you can convert the unidirectional cross-connection of the normal services into the unidirectional cross-connection in the receive direction of the SNCP services.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The unidirectional cross-connection of normal services must be configured and the source of the cross-connection must be a line board.
When this task is performed to convert a normal service into an SNCP service, the original services are not interrupted. The following procedures consider the operation of the Web LCT as an example.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Select the bidirectional cross-connection of the normal service in Cross-connection. Then, right-click and choose Expand from the shortcut menu. Step 3 Select the unidirectional cross-connection of the normal service in Cross-connection. Then, right-click and choose Convert to SNCP from the shortcut menu. Then, the Convert to SNCP service dialog box is displayed. Step 4 Set the attributes of the SNCP protection group and the slot mapping relation of the SNCP service.
Issue 02 (2009-02-25)
14-15
Parameters
Parameter Revertive Mode Value Range Non-Revertive, Revertive Default Value Revertive Description
l
When this parameter is set to Revertive, the NE that is in the switching state releases the switching and 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 use the default value.
14-16
Issue 02 (2009-02-25)
Parameter Hold-off Time (100ms)
Default Value 0
Description
l
When a line fault occurs, an NE can perform SNCP switching after a delay of time to prevent the situation where the NE performs SNCP switching and other protection switching at the same time. This parameter specifies the duration of the delay. It is recommended that you use the default value because the SNCP cannot co-exist with other protection switching modes in the OptiX RTN 600. This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value.
WTR Time(s)
300 to 720
600
Source Port Source VC4 Source Timeslot Range(e.g.1,3-6)
Specifies the port where the service source exists. Specifies the number of the VC-4 where the service source exists.
l
Specifies the timeslot range to which the service source corresponds. You can set this parameter to a number or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "" to indicate continuous numbers. For example, "1, 36" indicates numbers 1, 3, 4, 5, and 6. In the case of an IF board that works in the PDH mode, the first to the nth E1s/ E3s transmitted by microwaves correspond to the first to the nth VC-12/ VC-3 timeslots respectively. Similarly, the first to the nth ports of an E1 interface board or an E3/T3 interface board correspond to the first to the nth VC-12/ VC-3 timeslots respectively.
Sink Port Sink VC4
Specifies the port where the service sink exists. Specifies the number of the VC-4 where the service sink exists.
14-17
Issue 02 (2009-02-25)
Parameter Sink Timeslot Range(e.g.1,3-6)
Value Range -
Default Value -
Description
l
Specifies the timeslot range to which the service sink corresponds. You can set this parameter to a number or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "" to indicate continuous numbers. For example, "1, 36" indicates numbers 1, 3, 4, 5, and 6. In the case of an IF board that works in the PDH mode, the first to the nth E1s/ E3s transmitted by microwaves correspond to the first to the nth VC-12/ VC-3 timeslots respectively. Similarly, the first to the nth ports of an E1 interface board or an E3/T3 interface board correspond to the first to the nth VC-12/ VC-3 timeslots respectively.
Postrequisite
The SNCP service after the conversion is the SNCP service only in the receive direction. Later, you need to configure a unidirectional cross-connection between the service and the working trail, and a unidirectional cross-connection between the service and the protection trail. The normal service can be converted into the SNCP service both in the receive direction and the transmit direction only after the configuration.
14.7.4 Converting SNCP Services into Normal Services

After converting the SNCP services into the normal services, you can convert the SNCP crossconnection in the receive direction into the unidirectional cross-connection of the normal services.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The current service is transmitted in the working path. The SNCP cross-connection in the receive direction must be configured.
When this task is performed to convert an SNCP service into a normal service, the original services are not interrupted. The following procedures consider the operation of the Web LCT as an example.
14-18
Issue 02 (2009-02-25)
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 In the Auto-Created Cross-Connection pane, select the cross-connection and click To Normal. Step 3 In the Auto-Created Cross-Connection pane, select the cross-connection. Right-click and choose Change to Normal Service from the shortcut menu. Step 4 Choose Working or Protection from the displayed menu. l l To convert the cross-connection into a cross-connection between the working source and the service sink, choose Working. To convert the cross-connection into a cross-connection between the protection source and the service sink, choose Protection.
----End
Postrequisite
You need to delete the unidirectional cross-connection between the service and the working path or the unidirectional cross-connection between the service and the protection path. The SNCP service can be converted into the normal service both in the receive direction and the transmit direction only after the deletion.

This topic describes how to carry out an SNCP switching, relevant alarms and events, and the problems that occur frequently during the application of the protection feature. 14.8.1 SNCP Switching The SNCP switching is an important maintenance operation. 14.8.2 Relevant Alarms and Events When an SNCP switching occurs, the system reports corresponding alarms and abnormal events. 14.8.3 FAQs This topic lists the problems that occur frequently during the application of SNCP.
14.8.1 SNCP Switching

The SNCP switching is an important maintenance operation.
Prerequisite
l l
The SNCP protection group must be configured. The user must have the system level authority.
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. Right-click on the selected group and select the required switching mode. The system then displays a prompt dialog box. Step 3 Click Yes. Step 4 Click Query. ----End

When an SNCP switching occurs, the system reports corresponding alarms and abnormal events.
Relevant Alarms
l
PS The PS alarm indicates that a protection switching occurs.

l
SDH SNCP protection switching This abnormal event indicates that an SNCP switching occurs.
14.8.3 FAQs
This topic lists the problems that occur frequently during the application of SNCP. Q: What switching states does SNCP have? A: SNCP has the following switching states:
l
Normal The state when both the working SNC and the protection SNC are normal Automatic The state after an automatic switching triggered by the signal failure of the working SNC 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 from the time the working SNC is restored to normal to the time the revertive switching occurs in the revertive mode
Q: What are the differences between a two-fiber bidirectional MSP ring and an SNCP ring? A:
Item Protected object Protection level Protection mechanism Line rate
Two-Fiber Bidirectional MSP Ring A line Multiplex section level Shared protection STM-4 or an STM mode with a higher rate Ring switching The head end/tail end automatically performs bridging and switching according to the APS protocol. Generally, the head end/tail end is both the bridging node and the switching node. Relatively low
SNCP Ring Services between subnets VC-4 level, VC-3 level, or VC-12 level Dedicated protection PDH microwave, STM-1, or an STM mode with a higher rate Single-ended switching The transmit end is permanently bridged and the receive end is automatically switched.
Switching mode Bridging/Switching point
Reliability Maximum capacity
Relatively high
STM-N x n/2 (n represents STM-N the number of the nodes on a ring) 16 (at most) A ring network where services are distributed among NEs No restriction A ring network where services are centralized on a central NE
Number of the nodes on a ring network Application Scenario
Issue 02 (2009-02-25)
14-21
15 Linear Multiplex Section Protection
15
Linear Multiplex Section Protection
About This Chapter

The linear MSP 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 OptiX IDU 610 supports a maximum of two linear MSP groups for the STM-1 optical/ electrical line. The OptiX IDU 620 supports a maximum of five linear MSP groups, or a combination of three linear MSP groups for the optical/electrical line and one STM-4 linear MSP group. 15.1 Feature Description This topic considers the application of the linear MSP as an example to describe the linear MSP feature. 15.2 Basic Concepts This topic describes the basic concepts that you should be familiar with before you use the linear MSP protection scheme. 15.3 Availability The linear MSP solution requires the support of the applicable equipment and boards. 15.4 Relation with Other Features The linear MSP is related to the MSP ring and SNCP. 15.5 Realization Principle The 1+1 protection and the 1:N protection have different switching principles. 15.6 Planning Guide If the OptiX RTN 600 adopts the chain network that is formed through optical fibers or STM-1e cables, it is recommended that you adopt the linear MSP as the protection scheme. When planning the linear MSP, first plan the linear MSP mode, and then plan the parameters. 15.7 Creating Linear MSP To protect the services carried by the optical fibers or STM-1e cables between two nodes, configure the linear MSP. 15.8 Maintenance Guide
Issue 02 (2009-02-25)
15-1
This topic describes how to start and stop the linear MSP, and how to carry out a linear MSP switching. It also describes relevant alarms and events, and the problems that occur frequently during the application of the protection feature.
15-2
Issue 02 (2009-02-25)

This topic considers the application of the linear MSP as an example to describe the linear MSP feature. The linear MSP is applicable to the point-to-point network. The OptiX RTN 600 supports the 1 +1 linear MSP and 1:N linear MSP.
l
1+1 linear MSP To realize the 1+1 linear MSP, one working channel and one protection channel are required. When the working channel becomes unavailable, services are switched to the protection channel for transmission. Figure 15-1 shows the application of the 1+1 linear MSP. Figure 15-1 1+1 linear MSP
NE A Working channel NE B
Protection channel
Protection switching NE A Working channel NE B
Protection channel
1:N linear MSP To realize the 1:N linear MSP, N working channels and one protection channel are required. The working channels transmit normal services and the protection channel transmits extra services. 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 previously transmitted on this protection channel are interrupted. Figure 15-2 shows the application of the 1:N linear MSP.
Issue 02 (2009-02-25)
15-3
Figure 15-2 1:N linear MSP

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

This topic describes the basic concepts that you should be familiar with before you use the linear MSP protection scheme. 15.2.1 Protection Type The linear MSP can be classified in terms of the protection mechanism, switching mode, and revertive mode. 15.2.2 Meaning of Byte K The MSP protocol uses bytes K1 and K2 in the multiplex section overhead to transfer switching requests. 15.2.3 Switching Condition The linear MSP can be triggered by local SF conditions, local SD conditions, and local external switching requests. In the dual-ended mode, the local NE can perform switching according to byte K from the NE at the opposite end. 15.2.4 Switching Impact The services are interrupted within the linear MSP switching time (shorter than 50 ms). In the case of the 1:1 linear MSP, the extra services are interrupted from the time normal services are switched to the protection channel to the time the services are restored to the working channel.
15-4
Issue 02 (2009-02-25)

The linear MSP can be classified in terms of the protection mechanism, switching mode, and revertive mode. In terms of the protection mechanism, the linear MSP is classified into the dedicated protection and the shared protection.
l
Dedicated protection Dedicated protection refers to the case that 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 Shared protection refers to the case that 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.
In terms of the switching mode, the linear MSP is classified into the single-ended switching and the dual-ended switching.
l
Single-ended switching In the single-ended switching mode, the switching occurs only at one end and the state of the other end remains unchanged.
Dual-ended switching In the dual-ended switching mode, the switching occurs at both ends at the same time.
In terms of the revertive mode, the linear MSP is classified into the revertive mode and the nonrevertive mode.
l
Hence, the linear MSP is classified into the following eight 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
Issue 02 (2009-02-25)
The OptiX RTN 600 supports the following five linear MSP modes:
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 (N3) dual-ended revertive mode
The 1:N dual-ended revertive mode is switched according to the MSP protocol of the linear MSP described 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 the 1+1 single-ended mode does not use protocols.
NOTE
Huawei realizes two multiplex section protocols, the new protocol and the restructure protocol. The new protocol is more mature and the restructure protocol is in better compliance with the standards.
15.2.2 Meaning of Byte K

The MSP protocol uses bytes K1 and K2 in the multiplex section overhead to transfer switching requests. Table 15-1 Meaning of byte K (linear MSP) Byte K K1 (bit 1 to bit 4) K1 (bit 5 to bit 8) Meaning It carries the bridge request code, whose meaning is provided in Table 15-2. It carries the number of the traffic signal to which the bridge request corresponds. 0 represents the null signal, 114 represent normal traffic signals, and 15 represents the extra traffic signal (only in the case of 1:N). It carries the number of the traffic signal that bridges the local end and the channel. It has the same value range as K1 (bit 5 to bit 8). It carries the protection mode. 1 represents the 1:N mode. 0 represents the 1+1 mode. It carries the status. 000 represents the idle state, 111 represents the MS-AIS state, and 110 represents the MS-RDI state.
K2 (bit 1 to bit 4)
K2 (bit 5) K2 (bit 6 to bit 8)
NOTE
l l
In the case of the 1:N mode, the OptiX RTN 600 supports only the 1:N (N3) mode. In certain area applications, 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). ITUT G.841 provides no explicit requirements for the usage. By default, the OptiX RTN 600 does not support the function but you can make a modification by setting the function.
15-6
Issue 02 (2009-02-25)
Table 15-2 Bridge request code (linear MSP) Bit 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 Bit 2 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 Bit 3 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 Bit 4 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 Meaning Lockout of protection Forced switching Signal fail high priority Signal fail low priority Signal degrade high priority Signal degrade low priority Unused Manual switching Unused WTR Unused Exercise Unused Reverse request Do not revert No request
NOTE
l l
Reverse Request assumes the priority of the bridge request to which it is responding. By default, the OptiX RTN 600 uses 1101 (signal fail high priority) and 1011 (signal degrade high priority) as the SF/SD switching request. When interconnected with the third-party equipment, the OptiX RTN 600 can use 1100 (signal fail low priority) and 1010 (signal degrade low priority) as the SF/SD switching request after you make settings on the NMS.

The linear MSP can be triggered by local SF conditions, local SD conditions, and local external switching requests. In the dual-ended mode, the local NE can perform switching according to byte K from the NE at the opposite end.
Issue 02 (2009-02-25)
15-7
Table 15-3 Linear MSP switching conditions Switching Condition Lockout of protection (external switching) Priority From top downwards, the priority is from the highest to the lowest. Description The lockout of protection blocks normal traffic signals from entering the protection channel but does not block traffic signals from being switched from the protection channel to the working channel. The signal fail condition in the protection channel is equivalent to the lockout of protection. Traffic signals on the working channel are forcibly switched to the protection channel. The SF on the working channel causes traffic signals to be switched to the protection channel. When there is the R_LOC, R_LOF, R_LOS, MS_AIS or B2_EXC alarm on the working channel, the SF switching is triggered. The SD on the working channel causes traffic signals to be switched to the protection channel. When there is the B2_SD alarm on the working channel, the SD switching is triggered. If a switching is in the lockout or forced switching state, or if the current standby equipment is faulty, no switching occurs. Otherwise, the system switches services from the active board to the standby board or from the standby board to the active board according to the command. The switching then enters the manual switching state.
Signal fail (SF)
Signal degrade (SD)
15-8
Issue 02 (2009-02-25)
Priority
Description After traffic signals are switched to the protection channel due to the SF/SD condition on the working channel and the working channel is already restored to normal for the WTR time, a revertive switching occurs. From the time the former active equipment is restored to normal to the time the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching enters the normal state. Traffic signals are not actually switched. The exercise functionality is used only to check whether an NE can normally carry out the MSP protocol.
Exercise switching (external switching)
NOTE
l 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 higher priority preempts the channel. 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 byte K from the NE at the opposite end, the NE determines the switching priority according to the bridge request code contained in byte K. For the meaning of byte K, see 15.2.2 Meaning of Byte K.

The services are interrupted within the linear MSP switching time (shorter than 50 ms). In the case of the 1:1 linear MSP, the extra services are interrupted from the time normal services are switched to the protection channel to the time the services are restored to the working channel.
15.3 Availability
The linear MSP solution requires the support of the applicable equipment and boards.
Issue 02 (2009-02-25)
15-9
Table 15-4 Availability of the linear MSP solution Feature Linear MSP Applicable Board SL4 (all the versions) SL1/SD1 (all the versions) SLE/SDE (all the versions) Applicable Equipment IDU 620 IDU 610/620

The linear MSP is related to the MSP ring and SNCP.
l
The line that is configured with the linear MSP can work only as the sink of an SNCP service pair, and cannot work as the working source or the protection source. The line that is configured with the linear MSP cannot be configured to form an MSP ring.

The 1+1 protection and the 1:N protection have different switching principles. 15.5.1 1+1 Linear MSP The 1+1 linear MSP adopts the dual fed and selective receiving mechanism to realize the switching. 15.5.2 1:N Linear MSP The 1:N linear MSP adopts the automatic bridging mechanism to realize the switching.
15.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 describes the switching principle of the 1+1 linear MSP. The switching triggered by the signal failure on the working channel is provided as an example.
Figure 15-3 Realization principle of 1+1 linear MSP (before the switching)
NE B Working NE A
Protection Working
Protection Normal service
15-10
Issue 02 (2009-02-25)
Figure 15-4 Realization principle of 1+1 linear MSP (after the switching, in the single-ended mode)
NE B Working NE A
Protection Working
Figure 15-5 Realization principle of 1+1 linear MSP (after the switching, in the dual-ended mode)
NE B Working NE A
Protection Working
When the signal on the working channel fails, the switching principle in the single-ended mode is as follows: 1. 2. 3. Before the switching, the source sends traffic signals to both the working channel and the protection channel. The sink selects the traffic signals from the working channel. On detecting that the signal on the working channel fails, the line board at the sink in a certain direction (NE A) reports the event to the SCC board. After confirming that the signal on the working channel fails and that the signal on the protection channel is normal, the SCC board enables the cross-connect board to complete the cross-connection between the protection channel and the service sink.
When the signal on the working channel fails, the switching principle in the dual-ended mode is as follows:
1. 2.
Before the switching, the source sends traffic signals to both the working channel and the protection channel. The sink selects the traffic signals from the working channel. On detecting that the signal on the working channel fails, the sink in a certain direction (NE A) sends byte K to the source (NE B) on the protection channel (the request type is "signal fail"). NE B sends byte K to NE A also on the protection channel (the request type is "reverse request"). NE A receives the traffic signals from the protection channel. NE B also receives the traffic signals from the protection channel.
3. 4. 5.
15.5.2 1:N Linear MSP

The 1:N linear MSP adopts the automatic bridging mechanism to realize the switching.
NOTE
The following describes the switching principle of the 1:N linear MSP. The 1:1 linear MSP switching triggered by the signal failure on the working channel is provided as an example.
Figure 15-6 Realization principle of 1:1 linear MSP (before the switching)
NE B Working NE A
Protection Working
Protection Normal service Extra service
Figure 15-7 Realization principle of 1:1 linear MSP (after the switching)
NE B Working NE A
Protection Working
Protection Normal service Extra service
15-12
Issue 02 (2009-02-25)
When the signal on the working channel fails, the switching principle in the 1:1 mode is as follows: 1. 2. Before the switching, both the source and the sink send and receive normal traffic signals on the working channel, and send and receive extra traffic signals on the protection channel. On detecting that the signal on the working channel fails, the sink in a certain direction (NE A) sends byte K to the source (NE B) on the protection channel (the request type is "signal fail"). NE B performs a bridge of the normal traffic signals onto the protection channel and sends byte K to NE A on the protection channel (the request type is "reverse request"). NE A receives the normal traffic signals from the protection channel and performs a bridge of the normal traffic signals onto the protection channel. NE B receives the normal traffic 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.
15.6 Planning Guide

If the OptiX RTN 600 adopts the chain network that is formed through optical fibers or STM-1e cables, it is recommended that you adopt the linear MSP as the protection scheme. When planning the linear MSP, first plan the linear MSP mode, and then plan the parameters.
Procedure
Step 1 Plan the protection type of linear MSP. It is recommended that you select the 1+1 single-ended non-revertive mode or the 1:1 dualended revertive mode, depending on the requirements.
l
In the 1+1 single-ended non-revertive mode, the realization is simple and the switching speed is high. In addition, the equipment at both sides need not be interconnected. In the 1:N dual-ended revertive mode, extra services can be transmitted.

l
The MS protocols used at both sides must be consistent. It is recommended that you adopt the new protocol when both sides use the OptiX equipment. It is recommended that the working channel uses the line ports of one line board and the protection channel uses those of another line board to prevent the situation in which the failure of a line board causes the protection to fail. If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the value to ten minutes. It is recommended that you use SD as a switching condition.
----End
15.7 Creating Linear MSP

To protect the services carried by the optical fibers or STM-1e cables between two nodes, configure the linear MSP.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The boards where the working unit and the protection unit are located must be configured.
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 attributes of the linear MSP group.
NOTE
When Protection Type is set to 1:N Protection, the system displays the message "This service will change to extra service and protection switching will interrupt the service in the protection timeslot."
Step 4 Set the slot mapping relation. 1. 2. In Select Mapping direction, select West Working Unit. In Select Mapping Mode, select the line port to which the working channel corresponds and click 3. 4. .
In Select Mapping direction, select West Protection Unit. In Select Mapping Mode, select the line port to which the protection channel corresponds and click .
15-14
Issue 02 (2009-02-25)
Parameters
Parameter Protection Type Switching Mode Value Range 1+1 Protection, 1:N Protection
l
Default Value 1+1 Protection

l
Description
l
Single-Ended Switching, DualEnded Switching (1+1 protection) Dual-Ended Switching (1:N protection)
Single-Ended Switching (1+1 protection) Dual-Ended Switching (1:N protection)

l
In the single-ended mode, if the services on the working channels in a certain direction need to be switched, only the services on the working channels in the direction are switched to the protection channels. In the dual-ended mode, the services on the working channels in two directions are switched to the protection channels. When Revertive Mode is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. When Revertive Mode is set to NonRevertive, the NE that is in the switching state keeps the current state unchanged unless another switching occurs even
Issue 02 (2009-02-25)
15-15
Value Range
l
Default Value
l
Description though the former working channel is restored to normal.

l
Non-Revertive, Revertive (1+1 protection) Revertive (1:N protection)
Non-Revertive (1 +1 protection) Revertive (1:N protection)
When extra services need to be transmitted or several working channels exist, select 1:N protection. In the case of other situations, it is recommended that you select the 1+1 single-ended and non-revertive mode.
WTR Time(s)
300 to 720
600
This parameter is valid only when Revertive Mode is set to Revertive. When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. It is recommended that you use the default value. When SD enable is set to Enabled, the B2_SD alarm is considered as a switching condition. It is recommended that you use the default value. The new protocol is more mature than the restructure protocol but the restructure protocol is in better compliance with the standards than the new protocol. It is recommended that you select the new protocol. When the OptiX equipment is interconnected with the third-party equipment, select the restructure protocol if an interconnection problem occurs when the new protocol is adopted.
SD enable
Enabled, Disabled
Enabled
Protocol Type
New Protocol, Restructure Protocol
New Protocol
15-16
Issue 02 (2009-02-25)
Parameter SD/SF PRI Switching Tag
Value Range High priority, Low priority
Default Value High priority
Description
l
When this parameter is set to High priority, "1101" and "1011" are used as an SF/SD switching request. When this parameter is set to Low priority, "1100" and "1010" are used as an SF/SD switching request. It is recommended that you use the default value. When this parameter is set to Indicated, the MSP protocol uses K2 (bit 6 to bit 8) to indicate the switching mode (that is, uses code "100" to indicate the singleended mode and code "101" to indicate the dual-ended mode). When this parameter is set to Not indicated, the MSP protocol does not indicate the switching mode. It is recommended that you use the default value. In the case of 1+1 protection, only one line port can be mapped as West Working Unit; in the case of 1:N protection, a maximum of three line ports can be mapped as West Working Unit. Only one line port can be mapped as West Protection Unit. Ensure that the line port that is mapped as West Protection Unit and the line port that is mapped as West Working Unit are not on the same board, if possible.
Switching Mode Indication
Not indicated, Indicated
Not indicated (1 +1 protection) Indicated (1:N protection)
NOTE
Ensure that the MSP groups of the equipment at both ends of the linear multiplex section are set with the same attributes.
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.
Issue 02 (2009-02-25)
15-17

This topic describes how to start and stop the linear MSP, and how to carry out a linear MSP switching. It also describes relevant alarms and events, and the problems that occur frequently during the application of the protection feature. 15.8.1 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. 15.8.2 Linear MSP Switching The linear MSP switching is an important maintenance operation. 15.8.3 Relevant Alarms and Events When a linear MSP switching occurs, the system reports corresponding alarms and abnormal events. 15.8.4 FAQs This topic lists the problems that occur frequently during the application of the linear MSP.
15.8.1 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
A linear MSP group must be configured. The user must have the system level authority.
Precautions
l l
Stopping the linear MSP protocol causes the failure of the linear MSP. When services are switched onto the protection channel, stopping the linear MSP protocol causes the services to switch back to the working channel. At this time, if the working channel is normal, the services are transiently interrupted. If the working channel is faulty, the services are interrupted until the working channel is restored to normal or the linear MSP protocol is started.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree. Step 2 Select the linear MSP group and click Start Protocol or Stop Protocol. The system then displays a prompt dialog box. Step 3 Click OK. Step 4 Click Query. ----End
15.8.2 Linear MSP Switching

The linear MSP switching is an important maintenance operation.
Prerequisite
l l
A linear MSP group must be configured. The user must have the system level authority.
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 Slot Mapping Relation, select the working unit or the protection unit of a protection group. Right-click on the selected unit and select the required switching mode from the displayed menu. The system then displays a prompt dialog box. Step 3 Click Yes. Step 4 Click Query. ----End

When a linear MSP switching occurs, the system reports corresponding alarms and abnormal 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 service signal indicated by the sent K1 (bit 5 to bit 8) is not the same as that indicated by the received K2 (bit 1 to bit 4), the system 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) does not match that of the NE, the system reports the K2_M alarm.
LPS_UNI_BI_M The LPS_UNI_BI_M alarm indicates a mismatch of the single-ended/dual-ended mode of linear MSP. When the K2 (bit 6 to bit 8) is enabled to indicate the single-ended/dual-ended mode, if the received single-ended/dual-ended mode does not match the mode adopted by the NE, the system reports the LPS_UNI_BI_M alarm. This alarm applies only to the restructure protocol.
Issue 02 (2009-02-25)
15-19

l
Linear MSP protection switching This abnormal event indicates that a linear MSP protection switching occurs. No response from the remote end of the linear MSP This abnormal event indicates that the remote end does not respond to the linear MSP switching request sent by the local end.
15.8.4 FAQs
This topic lists the problems that occur frequently during the application of the linear MSP. 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 to the time the revertive switching occurs in the revertive mode
Q: What should be noted when the OptiX equipment is interconnected to the third-party equipment with the linear MSP applied? 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.
15-20

l
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 mode. ITU-T G.841 defines two priority levels for the SF and SD on byte K. By default, the OptiX equipment uses the SF and SD of the higher priority. If the third-party equipment uses the SF and SD of the lower priority, make modifications accordingly on the OptiX equipment. Check whether the third-party equipment uses the last three bits of byte K2 to indicate the single-ended/dual-ended mode. If yes, make modifications accordingly on the OptiX equipment.
Q: Why cannot the forced switching be carried out when the signal on the protection channel fails? A: After the signal on the protection channel fails, the protection channel is locked out. As the lockout of the protection channel has a higher priority than the forced switching, the forced switching cannot be carried out. Q: Why are the 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.
Issue 02 (2009-02-25)
15-21
16 Two-Fiber Bidirectional Ring MSP
16
Two-Fiber Bidirectional Ring MSP
About This Chapter

The two-fiber bidirectional ring MSP scheme is applicable to an SDH ring network of the STM-4 or higher level formed by fibers, and provides protection at the MS level for services between the nodes of a ring network. The IDU 620 supports a maximum of one STM-4 two-fiber bidirectional MSP ring. 16.1 Feature Description This topic considers the application of the two-fiber bidirectional MSP ring as an example to describe the two-fiber bidirectional MSP ring feature. 16.2 Basic Concepts This topic describes the basic concepts that you should be familiar with before you use the protection scheme of the two-fiber bidirectional MSP ring. 16.3 Availability The two-fiber bidirectional ring MSP needs the support of the corresponding equipment and boards. 16.4 Relation with Other Features The two-fiber bidirectional ring MSP is related to the linear MSP and SNCP. 16.5 Realization Principle The two-fiber bidirectional ring MSP adopts the automatic bridging mechanism between working channels and protection channels to realize the switching. 16.6 Planning Guide If the OptiX RTN 600 adopts the ring network that is formed by STM-4 fibers and the services are discrete services, it is recommended that you adopt the two-fiber bidirectional ring MSP as the protection scheme. 16.7 Configuring the Ring MSP If a ring network formed by STM-4 fibers is used and the services are discrete services, you can configure the ring MSP. 16.8 Maintenance Guide
Issue 02 (2009-02-25)
16-1
This topic describes how to start and stop the two-fiber bidirectional ring MSP, and how to carry out a two-fiber bidirectional ring MSP switching. It also describes relevant alarms and events, and the problems that occur frequently during the application of the protection feature.
16-2
Issue 02 (2009-02-25)

This topic considers the application of the two-fiber bidirectional MSP ring as an example to describe the two-fiber bidirectional MSP ring feature. On a two-fiber bidirectional MSP ring, the first half of VC-4s on each STM-N line is allocated to the working channel, and the other half of VC-4s is allocated to the protection channel. In normal cases, services are transmitted on the working channel. The services transmitted on two fibers flow in inverse directions. When a fiber cut occurs and the working channel becomes unavailable, the services on the two ends of the faulty point are both switched from the working channel of the faulty fiber to the protection channel of the reverse directional fiber for transmission. Figure 16-1 shows the application of the two-fiber bidirectional MSP ring. Figure 16-1 Two-fiber bidirectional MSP ring
NE A East West
West NE B East STM-4 two-fiber bidirectional MSP ring
East NE D West
West NE C
East
Protection swicthing
NE A East West
East NE D West
West NE C
Service between NE A and NE C
East
The two-fiber bidirectional MSP ring is applicable to the ring on which the services are distributed. When the services are converged on the ring, the maximum service capacity of this
ring is STM-N/2. When the services are evenly distributed on the ring, the maximum service capacity of this ring is M x STM-N/2, where M indicates the number of nodes on the ring.
16.2 Basic Concepts

This topic describes the basic concepts that you should be familiar with before you use the protection scheme of the two-fiber bidirectional MSP ring. 16.2.1 Protection Type The two-fiber bidirectional ring MSP is the most widely applied MSP type. 16.2.2 Meaning of Byte K The two-fiber bidirectional MSP ring is switched according to the MSP protocol described in ITU-T G.841. The MSP protocol uses bytes K1 and K2 in the multiplex section overhead to transfer switching requests. 16.2.3 Switching Condition Two-fiber bidirectional ring MSP can be triggered by local SF conditions, local SD conditions, local external switching requests, and byte K sent from the node on another ring network. 16.2.4 Switching Impact The services are interrupted within the MSP switching time (shorter than 50 ms). The extra services are interrupted from the time normal services are switched to the protection channel to the time the services are restored to the working channel.

The two-fiber bidirectional ring MSP is the most widely applied MSP type. The two-fiber bidirectional ring MSP has the following characteristics in terms of the protection type:
l
A ring network uses two fibers. One fiber is used to receive signals and the other fiber is used to transmit signals. Services are received and transmitted on the same route. The normal services between different nodes share the protection channel. The protection channel can be used to transfer extra services. In a two-fiber bidirectional MSP ring, the first half of the VC-4s are the working channels and the second half of the VC-4s are the protection channels. The two-fiber bidirectional ring MSP adopts the revertive mode. That is, an 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. The period from the time the former working channel is restored to normal to the time the NE releases the switching is called the wait-to-restore (WTR) time. To prevent frequent switching events due to an unstable working channel, it is recommended that you set the WTR time to five to twelve minutes.
l l
16.2.2 Meaning of Byte K

The two-fiber bidirectional MSP ring is switched according to the MSP protocol described in ITU-T G.841. The MSP protocol uses bytes K1 and K2 in the multiplex section overhead to transfer switching requests.
Table 16-1 Meaning of byte K (two-fiber bidirectional ring MSP) Byte K K1 (bit 1 to bit 4) K1 (bit 5 to bit 8) K2 (bit 1 to bit 4) K2 (bit 5) K2 (bit 6 to bit 8) Meaning It carries the switching request code, whose meaning is provided in Table 16-2. It carries the destination node ID. It carries the source node ID. 1 represents the long path and 0 represents the short path. It carries the status. 000 represents the idle state, 111 represents the MS-AIS state, 110 represents the MS-RDI state, 011 represents that extra traffic exists, 010 represents the bridging and switching, and 001 represents the bridging.a
NOTE
a: "Bridging" means that the equipment transmits the services that should be transmitted to the west (or east) working channels in normal cases to the east (or west) protection channels. "Switching" means that the equipment receives the services that should be received from the west (or east) working channels in normal cases from the east (or west) protection channels.
Table 16-2 Switching request code Bit 1 1 Bit 2 1 Bit 3 0 Bit 4 1 Meaning Forced switching_ring (FS_R) Signal fail_ring (SF_R) Signal degrade_ring (SD_R) Manual switching_ring (MS_R) WTR Exercise switching_ring (EXER_R) Reverse request_ring (RR_R)
1 1
0 0
1 0
1 0
0 0
1 0
0 1
1 1
Issue 02 (2009-02-25)
16-5
Bit 1 0
Bit 2 0
Bit 3 0
Bit 4 0
Meaning No request
NOTE
l l
A reverse request inherits the priority of the bridge request to which the reverse request responds. The other values of the bridge request code are used in the case of the two-fiber ring MSP, and hence, are not described here.

Two-fiber bidirectional ring MSP can be triggered by local SF conditions, local SD conditions, local external switching requests, and byte K sent from the node on another ring network. Table 16-3 Switching conditions of the two-fiber bidirectional ring MSP Switching Condition Lockout of protection (external switching) Priority From top downwards, the priority is from the highest to the lowest. Description The lockout of protection blocks normal traffic signals from entering the protection channel but does not block traffic signals from being switched from the protection channel to the working channel. The signal fail condition in the protection channel is equivalent to the lockout of protection. Traffic signals on the working channel are forcibly switched to the protection channel. The SF on the working channel causes traffic signals to be switched to the protection channel. When there is the R_LOC, R_LOF, R_LOS, MS_AIS or B2_EXC alarm on the working channel, the SF switching is triggered. The SD on the working channel causes traffic signals to be switched to the protection channel. When there is the B2_SD alarm on the working channel, the SD switching is triggered.
Issue 02 (2009-02-25)
Signal fail (SF)
Signal degrade (SD)
16-6
Switching Condition Manual switching (external switching)
Priority
Description If a switching is in the lockout or forced switching state, or if the current standby equipment is faulty, no switching occurs. Otherwise, the system switches services from the active board to the standby board or from the standby board to the active board according to the command. The switching then enters the manual switching state. After traffic signals are switched to the protection channel due to the SF/SD condition on the working channel and the working channel is already restored to normal for the WTR time, a revertive switching occurs. From the time the former active equipment is restored to normal to the time the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching enters the normal state. Traffic signals are not actually switched. The exercise functionality is used only to check if an NE can normally carry out the MSP protocol.
Exercise switching (external switching)
Issue 02 (2009-02-25)
16-7

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 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 switching according to byte K sent from another node NE, the NE determines the switching priority according to the bridge request code contained in byte K. For the meaning of byte K, see 16.2.2 Meaning of Byte K.

The services are interrupted within the MSP switching time (shorter than 50 ms). The extra services are interrupted from the time normal services are switched to the protection channel to the time the services are restored to the working channel.
16.3 Availability
The two-fiber bidirectional ring MSP needs the support of the corresponding equipment and boards. Table 16-4 Availability of the two-fiber bidirectional ring MSP Feature Two-fiber bidirectional ring MSP Applicable Board SL4 (all the versions) Applicable Equipment IDU 620

The two-fiber bidirectional ring MSP is related to the linear MSP and SNCP.
l l
The line of a two-fiber bidirectional MSP ring cannot be configured with the linear MSP. The line of a two-fiber bidirectional MSP ring can work only as the sink of an SNCP service pair, and cannot work as the working source or the protection source.

The two-fiber bidirectional ring MSP adopts the automatic bridging mechanism between working channels and protection channels to realize the switching.
NOTE
The following section describes the switching principle of the two-fiber bidirectional ring MSP. The protection switching triggered by a unidirectional signal failure on a two-fiber bidirectional MSP ring formed by four NEs is provided as an example.
16-8
Issue 02 (2009-02-25)
Figure 16-2 Realization principle of the two-fiber bidirectional ring MSP (before the switching)
NE A #1 VC-4 East West
East NE D West
West NE C
East Service between NE A and NE C
Figure 16-3 Realization principle of the two-fiber bidirectional ring MSP (after the switching)
NE A East West
West NE B East
#3VC-4 STM-4 two-fiber bidirectional MSP ring #3 VC-4
East NE D West
#1 VC-4
West NE C
East
Service from NE A to NE C
When the signal on the working channel fails, the switching principle of the two-fiber bidirectional ring MSP is as follows: 1. When the network is in the normal state, the service between NE A and NE C is transmitted in certain timeslots of the first VC-4 in the line. The service route is shown in Figure 16-2. On detecting that the signal on the working channel in the receive direction fails, the west line board of NE B sends byte K (the request type being SF_R and the state being MS-RDI) on the short path (NE B -> NE A) and also sends byte K (the request type being SF_R and the state being idle) on the long path (NE B -> NE C -> NE D -> NE A). After receiving byte K sent from NE B to NE A, NE C and NE D transparently transmit the received byte K. After receiving byte K on the short path, the east line board of NE A sends byte K (the request type being RR_R and the state being idle) on the short path (NE A -> NE B) and
2.
3. 4.
Issue 02 (2009-02-25)
also sends byte K (the request type being SF_R and the state being idle) on the long path (NE A -> NE D -> NE C -> NE B). 5. After receiving byte K on the long path, the west line board of NE A sends byte K (the request type being RR_R and the state being the bridging and switching) on the short path (NE A -> NE B) and also sends byte K (the request type being SF_R and the state being the bridging and switching) on the long path (NE A -> NE D -> NE C -> NE B). NE A enters the east switching state. That is, NE A receives the services that should be received from the east working channels in normal cases from the west protection channels, and transmits the services that should be transmitted to the east working channels in normal cases to the west protection channels. In the case of the service between NE A and NE C, NE A transmits the service to the first VC-4 path in the east direction in the normal state, but transmits the service to the third VC-4 path in the west direction in the east switching state. 6. After receiving byte K (the request type being SF_R and the state being the bridging and switching) sent from NE A to NE B, NE C and NE D enter the pass-through state. When NE C and NE D pass through byte K, NE C and NE D also pass through the information carried on the protection channels. After receiving byte K (the request type being SF_R and the state being the bridging and switching) sent from NE A, NE B sends byte K (the request type being SF_R and the state being the bridging and switching) on the long path (NE B -> NE C -> NE D -> NE A). NE B enters the west switching state. That is, NE A receives the services that should be received from the west working channels in normal cases from the east protection channels, and transmits the services that should be transmitted to the west working channels in normal cases to the east protection channels. In the case of the service between NE A and NE C, NE B receives the service from the first VC-4 path in the west direction and transmits the service to the first VC-4 in the east direction in the normal state, but receives the service from the third VC-4 path in the east direction and transmits the service to the first VC-4 path in the east direction in the west switching state.
7.
16.6 Planning Guide

If the OptiX RTN 600 adopts the ring network that is formed by STM-4 fibers and the services are discrete services, it is recommended that you adopt the two-fiber bidirectional ring MSP as the protection scheme.
Procedure
Step 1 Allocate a node ID to each NE.
l l
The number of NE nodes must not exceed 16. The value range of a node ID is from 0 to 15. In the case of a newly-built ring network, it is recommended that you set the node ID of the central station in the network to 0 and allocate node IDs to the other NEs one by one counterclockwise, with the node ID of each NE being one more than the node ID of the previous NE. If you add an NE in an existing ring network, it is recommended that you set the node ID of the new NE to the number that is one less than the maximum number of the nodes (including the new NE) in the ring network.
16-10

l
The MSP protocols used in a ring network must be consistent. It is recommended that you select the new protocol. Set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the value to ten minutes. It is recommended that you use SD as a switching condition.
----End
16.7 Configuring the Ring MSP

If a ring network formed by STM-4 fibers is used and the services are discrete services, you can configure the ring MSP.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The boards where the working unit and the protection unit are located must be configured.
When an unprotected service is converted into a ring MSP service by configuring the ring MSP, the original services are not interrupted.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ring MS from the Function Tree. Step 2 Click New. The system displays the message "This service will change to extra service and protection switching will interrupt the service in the protection timeslot." Step 3 Click OK. The system displays the Create a Ring Multiplex Section dialog box. Step 4 Set the attributes of the ring MSP protection group according to the networking plan. Step 5 Set the slot mapping relation. 1. 2. 3. Set Local Node, West Node, and East Node according to the networking plan. In Select Mapping Direction, select West Line 1. In Select Mapping Mode, select the line port to which the working channel corresponds and click 4. 5. .
In Select Mapping Direction, select East Line 1. In Select Mapping Mode, select the line port to which the protection channel corresponds and click .
Issue 02 (2009-02-25)
Parameters
Parameter Level Protection Type Local Node Value Range STM-4 2-fiber Bidirectional Multiplex Section 0 to 15 Default Value STM-4 2-fiber Bidirectional Multiplex Section 0 Description This parameter is prohibited from being modified. This parameter is prohibited from being modified.
l
This parameter specifies the node ID allocated to the local NE. The node ID of each NE must be unique.
West Node
0 to 15
This parameter specifies the node ID that is allocated to the NE to which the west line board of the local NE is connected. This parameter specifies the node ID that is allocated to the NE to which the east line board of the local NE is connected.
East Node
0 to 15
16-12
Issue 02 (2009-02-25)
Default Value 600
Description
l
When the time after the former working channel is restored to normal reaches the set value of this parameter, a revertive switching occurs. It is recommended that you use the default value. When SD enable is set to Enabled, the B2_SD alarm is considered as a switching condition. It is recommended that you use the default value. The new protocol is more mature than the restructure protocol but the restructure protocol is in better compliance with the standards than the new protocol. It is recommended that you select the new protocol. When the OptiX equipment is interconnected with the third-party equipment, select the restructure protocol if an interconnection problem occurs when the new protocol is adopted.
SD enable
Enabled, Disabled
Enabled
Protocol Type
New Protocol, Restructure Protocol
New Protocol
It is recommended that you map the line port of the SL4 board in slot 6 as West Line 1 and map the line port of the SL4 board in slot 8 as East Line 1.
l
Map as VC4
Not selected
If you select Map as VC4, the VC-4 is considered as the unit of the settings in the slot mapping relation. It is recommended that you use the default value.
NOTE
The protection groups of the NEs that form a ring multiplex section must be set with the same attributes except Local Node, West Node, and East Node.
Postrequisite
In the case of a two-fiber bidirectional MSP ring, you need to configure bidirectional crossconnections between the services and the timeslots of the working channel (the first half of the timeslots of the line port) later. If extra services need to be transmitted, you need to configure bidirectional cross-connections between the extra services and the timeslots of the protection channel (the second half of the timeslots of the line port).
Issue 02 (2009-02-25)
16-13

This topic describes how to start and stop the two-fiber bidirectional ring MSP, and how to carry out a two-fiber bidirectional ring MSP switching. It also describes relevant alarms and events, and the problems that occur frequently during the application of the protection feature. 16.8.1 Starting/Stopping the Ring MSP Protocol If you first stop the ring MSP protocol and then start it, the ring MSP status can be restored to the initial state. 16.8.2 Ring MSP Switching The ring MSP switching is an important maintenance operation. 16.8.3 Relevant Alarms and Events When a two-fiber bidirectional ring MSP switching occurs, the system reports corresponding alarms and abnormal events. 16.8.4 FAQs This topic lists the problems that occur frequently during the application of the two-fiber bidirectional ring MSP.
16.8.1 Starting/Stopping the Ring MSP Protocol

If you first stop the ring MSP protocol and then start it, the ring MSP status can be restored to the initial state.
Prerequisite
l l
A ring MSP group must be configured. The user must have the system level authority.
Precautions
l l
Stopping the ring MSP protocol causes the failure of the ring MSP. When services are switched onto the protection channel, stopping the ring MSP protocol causes the services to switch back to the working channel. At this time, if the working channel is normal, the services are transiently interrupted. If the working channel is faulty, the services are interrupted until the working channel is restored to normal or the protocol is started.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ring MS from the Function Tree. Step 2 Select the ring MSP group and click Start Protocol or Stop Protocol. The system then displays a dialog box indicating that the operation is successful. Step 3 Click OK. Step 4 Click Query. ----End
16.8.2 Ring MSP Switching

The ring MSP switching is an important maintenance operation.
Prerequisite
l l
A ring MSP group must be configured. The user must have the system level authority.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ring MS from the Function Tree. Step 2 In Slot Mapping Relation, select the working unit or the protection unit of a protection group. Right-click on the selected unit and select the required switching mode from the displayed menu. The system then displays a dialog box indicating that the operation is successful. Step 3 Click Yes. Step 4 Click Query. ----End

When a two-fiber bidirectional ring MSP switching occurs, the system reports corresponding alarms and abnormal 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.

l
MSP switching This abnormal event indicates that a ring MSP switching occurs. No response from the remote end of the ring MSP This abnormal event indicates that the remote end does not respond to the ring MSP switching request sent by the local end.
16.8.4 FAQs
This topic lists the problems that occur frequently during the application of the two-fiber bidirectional ring MSP. Q: How are the east and west of a ring network defined?
A: In the case of a ring network, two paths exist from one node to another node. To ensure the consistency of service routes, it is required that most of the services are configured to travel in one direction. The direction is called the primary direction of the services in the ring network. Generally, the primary direction is counterclockwise. If the line direction in which an NE sends services is the primary direction, the line direction is called the east. If the line direction in which the NE receives services is the primary direction, the line direction is called the west. That is, the services are sent in the east direction and received in the west direction. Q: What switching states does the two-fiber bidirectional ring MSP have? A: The two-fiber bidirectional ring MSP has the following switching states:
l
Protocol is not started The state when the MSP protocol is not started Protocol starting The state when the MSP protocol is starting Idle The normal state after the MSP protocol is started Switching This refers to the state after a switching event. In the case of east switching, the equipment receives the services that should be received from the west working channels in normal cases from the east protection channels, and transmits the services that should be transmitted to the west working channels in normal cases to the east working channels. In the case of west switching, the equipment receives the services that should be received from the east working channels in normal cases from the west protection channels, and transmits the services that should be transmitted to the east working channels in normal cases to the west protection channels.
Pass-through In the pass-through state, the cross-connections on the working channels remain unchanged, and the services on the protection channels in the east and west directions are passed through.
Q: What are the differences between a two-fiber bidirectional MSP ring and an SNCP ring? A: Item Protected object Protection level Protection mechanism Line rate Two-Fiber Bidirectional MSP Ring A line Multiplex section level Shared protection STM-4 or an STM mode with a higher rate Ring switching SNCP Ring Services between subnets VC-4 level, VC-3 level, or VC-12 level Dedicated protection PDH microwave, STM-1, or an STM mode with a higher rate Single-ended switching
Issue 02 (2009-02-25)
Switching mode
16-16
Item Bridging/Switching point
Two-Fiber Bidirectional MSP Ring The head end/tail end automatically performs bridging and switching according to the APS protocol. Generally, the head end/tail end is both the bridging node and the switching node. Relatively low
SNCP Ring The transmit end is permanently bridged and the receive end is automatically switched.
Reliability Maximum capacity
Relatively high
STM-N x n/2 (n represents STM-N the number of the nodes on a ring) 16 (at most) A ring network where services are distributed among NEs No restriction A ring network where services are centralized on a central NE
Number of the nodes on a ring network Application Scenario
Q: How does one handle a two-fiber bidirectional ring MSP switching failure? A: The steps are as follows: 1. Check the data configuration of the MSP, especially the node ID of each NE. The configuration of the 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 with reference to the alarm. 3. Check the MSP state of each NE. In the case of normal switching, the head-end/tail-end node is in the switching state and the intermediate node is in the pass-through state.
l
If an NE is in the abnormal state, stop the MSP protocol of the NE and then restart the MSP protocol. If several NEs are in the abnormal state, stop the MSP protocol of all the NEs on the ring network and then restart the MSP protocol.
Issue 02 (2009-02-25)
16-17
17 Features of Ethernet Ports
17
About This Chapter
Features of Ethernet Ports
To effectively work with the data communication equipment at the client side, the Ethernet port supports the auto-negotiation function, Jumbo frames, and flow control function. 17.1 Feature Description When the external port (namely, PORT) of the Ethernet service board is interconnected with the data communication equipment on the client side, you need to set the major attributes of the external port so that the Ethernet services on the client side can be accessed normally. 17.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the Ethernet port feature. 17.3 Availability The Ethernet port feature requires the support of the applicable equipment and boards. 17.4 Relation with Other Features The auto-negotiation function, Jumbo frames, and flow control function do not affect other features. 17.5 Realization Principle The auto-negotiation function and the flow control function comply with IEEE 802.3. 17.6 Planning Guide Before you plan Ethernet port features, obtain the information of the client-side equipment. 17.7 Configuration Guide This topic describes the configuration tasks relevant to the Ethernet port feature. 17.8 Maintenance Guide This topic describes the alarms and events relevant to the Ethernet port feature and the problems that occur frequently during the application of the feature.
Issue 02 (2009-02-25)
17-1

When the external port (namely, PORT) of the Ethernet service board is interconnected with the data communication equipment on the client side, you need to set the major attributes of the external port so that the Ethernet services on the client side can be accessed normally. The external port of the Ethernet service board is the external physical interface and is also called the user-side interface. The external port is used to access the Ethernet services on the user side. The features relevant to the external port of the Ethernet service board include the autonegotiation, Jumbo frame, and flow control.
Auto-Negotiation Function
The auto-negotiation function allows the network equipment to send information of its supported working mode to the opposite end on the network and to receive the corresponding information that the opposite end may transfer. The external port of the Ethernet service board and the data communication equipment at the opposite end must work in the same duplex mode and operate at the same rate. If the working modes at the two ends do not match, the transmission efficiency is reduced and the data may even be lost.
Jumbo Frames
An Ethernet frame requires that the maximum size of the payload must not exceed 1500 bytes. This requirement severely affects the transmission efficiency of certain high-speed data services. To improve the transmission efficiency, the Jumbo frame technology is developed. A Jumbo frame adopts the structure of an ordinary Ethernet frame but does not have a requirement for the maximum size of the payload. To differentiate a Jumbo frame from an ordinary Ethernet frame, we define the type field of a Jumbo frame as "0x8870".
Flow Control Function

When the data processing/transferring capability of the equipment fails to handle the flow received at the port, congestion occurs on the line. To reduce the number of discarded packets due to buffer overflow, proper flow control measures must be taken.
17.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the Ethernet port feature. 17.2.1 Auto-Negotiation Function The auto-negotiation function allows the network equipment to send information of its supported working mode to the opposite end on the network and to receive the corresponding information that the opposite end may transfer. 17.2.2 Jumbo Frames The maximum length of the payload of an Ethernet frame must not exceed 1500 bytes. This requirement greatly affects the transmission efficiency of certain high-speed data services. To improve the transmission efficiency, the Jumbo frame technology emerged.
17.2.3 Flow Control Function When the equipment fails to handle the flow received at the port due to poor data processing/ transferring capability, congestion occurs on the line. To reduce the number of discarded packets caused by buffer overflow, proper flow control measures must be taken.
17.2.1 Auto-Negotiation Function

The auto-negotiation function allows the network equipment to send information of its supported working mode to the opposite end on the network and to receive the corresponding information that the opposite end may transfer.
NOTE
The following sections describe the basic concepts related to the auto-negotiation function, including all the working modes. The working mode supported by each Ethernet port of the equipment may be different. For details, refer to 17.7.1 Configuring External Ethernet Ports.
Auto-Negotiation Function of FE Electrical Ports

In the case of FE electrical ports, there are four common working modes: 10M half-duplex, 10M full-duplex, 100M half-duplex, and 100M full-duplex. If the working mode of an Ethernet port does not match that of its opposite port, the two ports cannot communicate. With the autonegotiation function, however, the two ports can communicate with each other. The autonegotiation function uses fast link pulses and normal link pulses to transfer the negotiation information of the working mode to enable the working mode of the local Ethernet port to match the working mode of the opposite end. Table 17-1 lists the auto-negotiation rules of FE electrical ports. Table 17-1 Auto-negotiation rules of FE electrical ports (when the local port adopts the autonegotiation mode) Working Mode of the Opposite Port Auto-negotiation 10M half-duplex 10M full-duplex 100M half-duplex 100M full-duplex Auto-Negotiation Result 100M full-duplex 10M half-duplex 10M half-duplex 100M half-duplex 100M half-duplex
NOTE
From Table 17-1, it is evident that when the working mode of the opposite equipment is 10M full-duplex or 100M full-duplex, the auto-negotiation result cannot realize the matching between the working modes of both sides. As a result, certain packets are lost. Hence, when the working mode of the opposite equipment is 10M full-duplex or 100M full-duplex, set the working mode of the local equipment to 10M full-duplex or 100M fullduplex.
When the FE electrical ports on both sides are working in the auto-negotiation mode, the equipment on both sides can negotiate the flow control function through the auto-negotiation function.
Issue 02 (2009-02-25)
17-3
Auto-Negotiation Function of GE Electrical Ports

In the case of GE electrical ports, there are five working modes: 10M half-duplex, 10M fullduplex, 100M half-duplex, 100M full-duplex, and 1000M full-duplex. The auto-negotiation function of GE electrical ports is similar to the auto-negotiation function of FE electrical ports. Table 17-2 lists the auto-negotiation rules of GE electrical ports. Table 17-2 Auto-negotiation rules of GE electrical ports (when the local port adopts the autonegotiation mode) Working Mode of the Opposite Port Auto-negotiation (GE electrical port) Auto-negotiation (FE electrical port) 10M half-duplex 10M full-duplex 100M half-duplex 100M full-duplex 1000M full-duplex Auto-Negotiation Result 1000M full-duplex 100M full-duplex 10M half-duplex 10M half-duplex 100M half-duplex 100M half-duplex 1000M full-duplex
From Table 17-2, it is evident that when the working mode of the opposite equipment is 10M full-duplex or 100M full-duplex, the auto-negotiation result cannot realize the matching between the working modes of both sides. As a result, certain packets are lost. Hence, when the working mode of the opposite equipment is 10M full-duplex or 100M full-duplex, set the working mode of the local equipment to 10M full-duplex or 100M full-duplex. When the GE electrical ports on both sides are working in the auto-negotiation mode, the equipment on both sides can negotiate the flow control function through the auto-negotiation function.
Auto-Negotiation Function of GE Optical Ports

GE optical ports support only the 1000M full-duplex working mode. The auto-negotiation function of GE optical ports is used only for negotiating the flow control function.
NOTE
If the GE optical port of the equipment on one side works in the 1000M full-duplex mode and the GE optical port of the equipment on the other side works in the auto-negotiation mode, a link error occurs due to an autonegotiation failure, and as a result, a LINK_ERR alarm is generated.
17.2.2 Jumbo Frames

The maximum length of the payload of an Ethernet frame must not exceed 1500 bytes. This requirement greatly affects the transmission efficiency of certain high-speed data services. To improve the transmission efficiency, the Jumbo frame technology emerged. A Jumbo frame adopts the structure of a common Ethernet frame but does not have the requirement for the maximum length of the payload. Furthermore, the type field of the Jumbo frame is defined as 0x8870 to differentiate a Jumbo frame from a common Ethernet frame.
Both the EFT4 and EMS6 boards can receive and transmit the Jumbo frame whose length does not exceed 9600 bytes; however, the ways for these two boards to process the Jumbo frame are different.
l
The Ethernet port of the EFT4 board checks the type field in an Ethernet frame to determine whether the Ethernet frame is a Jumbo frame. If the Ethernet frame is a Jumbo frame, the maximum frame length is not restricted. The Ethernet port of the EMS6 board checks whether an Ethernet frame whose length exceeds 1536 bytes is a Jumbo frame. All the frames are restricted by the maximum frame length. VCTRUNKs 14 of the EFT4 board and VCTRUNKs 58 of the EMS6 board check whether an Ethernet frame is a Jumbo frame. If an Ethernet frame is not a Jumbo frame but its length exceeds the maximum frame length, the board discards the frame. VCTRUNKs 14 of the EMS6 board do not check Jumbo frames. The EMS6 board discards any frame whose length exceeds the maximum frame length. The maximum frame length (namely, the MTU), is a parameter of the Ethernet port. In the case of common Ethernet frames, the Ethernet service board discards the frame whose length exceeds the value of this parameter.
The default type field of a Jumbo frame is "0x8870".
17.2.3 Flow Control Function

When the equipment fails to handle the flow received at the port due to poor data processing/ transferring capability, congestion occurs on the line. To reduce the number of discarded packets caused by buffer overflow, proper flow control measures must be taken. The half-duplex Ethernet uses back pressure to control flow. The full-duplex Ethernet uses PAUSE frames to control flow. Currently, because the half-duplex Ethernet is seldom applied, the flow control function realized by the equipment is developed for only the full-duplex Ethernet. The full-duplex Ethernet flow control function realized by the equipment is classified into two types: auto-negotiation flow control and non-auto-negotiation flow control.
NOTE
The following sections describe the basic concepts related to the flow control function, including all the flow control modes. The flow control mode supported by each Ethernet port of the equipment may be different. For details, refer to 17.7.1 Configuring External Ethernet Ports.
Auto-Negotiation Flow Control

When the Ethernet port is working in the auto-negotiation mode, you can adopt the autonegotiation flow control function. The auto-negotiation flow control mode includes the following:
l
Asymmetric PAUSE toward the link partner In the case of congestion, the port can send PAUSE frames but cannot process received PAUSE frames.
Symmetric PAUSE The port can send and process PAUSE frames. Both asymmetric and symmetric PAUSE The port has the following three capabilities:
Issue 02 (2009-02-25)
17-5

l
Sends and processes PAUSE frames. Sends but does not process PAUSE frames. Processes but does not send PAUSE frames.
Disabled The port does not send or process PAUSE frames.
Non-Auto-Negotiation Flow Control

When the Ethernet port is working in a fixed working mode, you can adopt the non-autonegotiation flow control function. The non-auto-negotiation flow control modes includes the following:
l
Send only In case of congestion, the port can send PAUSE frames but cannot process received PAUSE frames.
Receive only In case of congestion, the port can process received PAUSE frames but cannot send PAUSE frames.
Send and receive The port can send PAUSE frames and can also process received PAUSE frames. Disabled The port does not send or process PAUSE frames.
17.3 Availability
The Ethernet port feature requires the support of the applicable equipment and boards. Table 17-3 Availability of the Ethernet port feature Feature Auto-negotiation Applicable Board EFT4 (all the versions) EMS6 (all the versions) IFH2 (all the versions) Jumbo frame EFT4 (all the versions) EMS6 (all the versions) Flow control EFT4 (all the versions) EMS6 (all the versions) IFH2 (all the versions)
17-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Applicable Equipment IDU 610/620 IDU 620 IDU 605 1F/2F IDU 620 IDU 610/620 IDU 620 IDU 610/620 IDU 620 IDU 605 1F/2F IDU 620
Issue 02 (2009-02-25)

The auto-negotiation function, Jumbo frames, and flow control function do not affect other features.

The auto-negotiation function and the flow control function comply with IEEE 802.3. 17.5.1 Auto-Negotiation Function The auto-negotiation function uses fast link pulses and normal link pulses to transfer information of the working mode in such a manner that no packet or upper layer protocol overhead is added. 17.5.2 Flow Control Function The Ethernet board adopts PAUSE frames to realize the flow control function.
17.5.1 Auto-Negotiation Function

The auto-negotiation function uses fast link pulses and normal link pulses to transfer information of the working mode in such a manner that no packet or upper layer protocol overhead is added.
NOTE
The following describes the realization principle of the auto-negotiation function. The auto-negotiation function of FE electrical ports is provided as an example.
The fast link pulse (FLP) is called the 10BASE-T link integrity test pulse sequence. Each device must be capable of issuing FLP bursts at power up, on command from management, or due to user interaction. The FLP burst consists of a series of link integrity test pulses that form an alternating clock/data sequence. Extraction of the data bits from the FLP burst yields a link code word that identifies the working modes supported by the remote device, as well as certain information used for the handshake mechanism of the auto-negotiation function. To maintain interoperability with existing 10BASE-T devices, the auto-negotiation function also supports the reception of 10BASE-T compliant link integrity test pulses. 10BASE-T link pulse activity is referred to as the normal link pulse (NLP) sequence. A device that fails to respond to the FLP burst sequence by returning only the NLP sequence is treated as a 10BASE-T compatible device. The first pulse in an FLP burst is defined as a clock pulse. Clock pulses within an FLP burst are spaced at 125 us. Data pulses occur in the middle of two adjacent clock pulses. The presence of a positive pulse represents a logic one and the absence of a pulse represents a logic zero. An FLP burst consists of 17 clock pulses and 16 data pulses (if all data bits are 1). The NLP waveform is simpler than the FLP waveform. The NLP sends a positive pulse every 16 ms when no data frame needs to be transmitted.
Issue 02 (2009-02-25)
17-7
Figure 17-1 Waveform of a single FLP

T3 T2 T1
Clock pulses
First bit on wire Data Encoding 1 D 0 T1: 100 ns 1 D 1 0 D 2 T2: 62.5 us 1 D 3 T3: 125 us
Figure 17-2 Consecutive FLP bursts and NLPs

T5 T4
FLP bursts
NLPs T4: 2 ms T5: 16 ms
17.5.2 Flow Control Function

The Ethernet board adopts PAUSE frames to realize the flow control function. The realization principle of the flow control function is as follows: 1. When congestion occurs in the receive queue of an Ethernet port (the data in the receive buffer exceeding a certain threshold) and the port is capable of sending PAUSE frames, the port sends a PAUSE frame to the opposite end. The pause-time value in the frame is N (0<N65535). After receiving the PAUSE frame, and being capable of processing PAUSE frames, the Ethernet port at the opposite end stops sending data within a specified period of time N (whose unit is the time needed for sending 521 bits). If the congestion at the receive port is cleared (the data in the receive buffer is below a certain threshold) but the pause-time does not end, the port sends a PAUSE frame whose pause-time is 0 to notify the opposite end to start sending data.
2.
3.
IEEE 802.3 defines the format of the PAUSE frame as follows:


l l l l l
Destination address: 01-80-C2-00-00-01 (multicast address) Source address: MAC address of the source port Type/Length: 88-08 (MAC control frame) MAC control opcode: 00-01 (PAUSE frame) MAC control parameter: pause-time (two bytes)
Figure 17-3 Structure of the PAUSE frame

Destination address Source address Type/Length MAC control opcode MAC control parameter (pause-time) 01-80-C2-00-00-01 XX-XX-XX-XX-XX-XX 88-08 00-01 XX-XX Reserved 6 octets 6 octets 2 octets 2 octets 2 octets
17.6 Planning Guide

Before you plan Ethernet port features, obtain the information of the client-side equipment.
Procedure
Step 1 Plan the working mode of the Ethernet port. Ensure that the working modes of the Ethernet ports at the two ends should be the same. Step 2 Plan the parameter MTU. In the case of the EFT4 board, adhere to the following principles when planning the MTU of the Ethernet port:
l
The MTU must be greater than the length of the maximum frame among all the L2 data frames that are to be transmitted. The value of the MTU ranges from 1518 to 1535 bytes. The default value of the MTU is 1522 bytes, which is the sum of the length of the maximum basic frame and the length of the VLAN label. The MTU is invalid for the Jumbo frame.
l l
In the case of the EMS6 board, adhere to the following principles when planning the MTU of the Ethernet port:

l
The MTU should be greater than the length of the maximum frame among all L2 data frames to be transmitted. The value of the MTU ranges from 1518 to 9600 bytes. The default value of the MTU is 1522 bytes, which is the sum of the length of the maximum basic frame and the length of the VLAN label. The MTU parameter restricts the maximum length of a Jumbo frame.
l l
Step 3 Plan the flow control parameters for the Ethernet port. Adhere to the following principles when planning the flow control parameters for the Ethernet port:
l l l
The flow control parameters are valid only for the full-duplex Ethernet. The flow control parameters are valid only for the Ethernet transparent transmission service. When the Ethernet port works in the auto-negotiation mode, use the auto-negotiation flow control parameter. When the Ethernet port works in a fixed working mode, use the non-auto-negotiation flow control parameter. The flow control parameters at both sides must match each other. The flow control function must not be enabled at one side and disabled at the other side. It is recommended that you enable the flow control function for the Ethernet board and for the opposite equipment on the network with flow bursts.
----End

This topic describes the configuration tasks relevant to the Ethernet port feature. 17.7.1 Configuring External Ethernet Ports When an NE uses the external ports (that is, PORTs) of the Ethernet boards to access Ethernet services, the attributes of the external ports need to be configured so that the external ports can work with the data communication equipment on the client side to provide the normal access to the Ethernet services. 17.7.2 Modifying the Type Field of Jumbo Frames By default, the type field of Jumbo frames processed by Ethernet boards is set to "0x8700".
17.7.1 Configuring External Ethernet Ports

When an NE uses the external ports (that is, PORTs) of the Ethernet boards to access Ethernet services, the attributes of the external ports need to be configured so that the external ports can work with the data communication equipment on the client side to provide the normal access to the Ethernet services.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet board must be included in the NE Panel.
Precautions
l
The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards EFT4 and EMS6.
Ethernet ports FE1FE4 of an EFT4 board correspond to PORT1PORT4 respectively. The EFT4 board does not support the setting of TAG attributes, network attributes, and advanced attributes. Ethernet ports FE1FE4 of an EMS6 board correspond to PORT1PORT4 respectively. Ports GE1 and GE2 of an EMS6 board correspond to PORT5 and PORT6 respectively.
The IDU 605 IF/2F supports the Ethernet board EMS4 (a logical board). Ethernet ports FE1FE3 of an EMS4 board (a logical board) correspond to PORT1PORT3 respectively. Port FE4/GE1 of an EMS4 board corresponds to PORT4.
The following procedures describe how to configure the external port of an EMS6 board. The EFT4 board does not support the configuration of the TAG attributes, network attributes, and advanced attributes. The Hybrid IF board (IFH2) provides the GE port for accessing Ethernet services and it supports certain Ethernet service access functions. The procedure for configuring the Ethernet port of the IFH2 board is similar to the procedure for configuring the external Ethernet port. The IFH2 board, however, supports the configuration of only the basic attributes and flow control function. The following procedures consider the operation of the Web LCT as an example.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select External Port.
NOTE
If you need to configure the attributes of the Ethernet port on the IFH2 board, select the IFH2 board in the NE Explorer.
Step 2 Set the basic attributes of the port. 1. 2. Click the Basic Attributes tab. Set the basic attributes of the port.
3. 1. 2.
Click Apply. Click the Flow Control tab. Set the flow control mode of the port.
Step 3 Set the flow control mode of the port.
3.
Click Apply.
Step 4 Optional: Set the TAG attributes of the port.

1. 2.
Click the TAG Attributes tab. Set the TAG attributes of the port.
3. 1. 2.
Click Apply. Click the Network Attributes tab. Set the network attributes of the port.
Step 5 Optional: Set the network attributes of the port.
3. 1. 2.
Click Apply. Click the Advanced Attributes tab. Set the advanced attributes of the port.
Step 6 Optional: Set the advanced attributes of the port.
3.
Click Apply.
----End
Parameters
Parameter Port Enabled Value Range Enabled, Disabled Default Value Disabled Description
l
In the case of the port that accesses services, set this parameter to Enabled. In the case of other ports, set this parameter to Disabled. If this parameter is set to Enabled for the port that does not access services, an ETH_LOS alarm may be generated.
17-12
Issue 02 (2009-02-25)
Parameter Working Mode
Value Range 10M Full-Duplex, 100M Full-Duplex, Auto-Negotiation (EFT4) 10M Half-Duplex, 10M Full-Duplex, 100M Half-Duplex, 100M Full-Duplex, 1000M FullDuplex, AutoNegotiation (EMS6) Auto-Negotiation, 10M Full-Duplex, 100M Full-Duplex, 1000M Full-Duplex (IFH2) 10M Half-Duplex, 10M Full-Duplex, 100M Half-Duplex, 100M Full-Duplex, Auto-Negotiation (a logical board EMS4, PORT1PORT3) 10M Half-Duplex, 10M Full-Duplex, 100M Half-Duplex, 100M Full-Duplex, 1000M FullDuplex, AutoNegotiation (a logical board EMS4, PORT4)
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 the 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 the full-duplex mode, set the working mode of the equipment on the local side to 10M Full-Duplex, 100M Full-Duplex, or 1000M Full-Duplex depending on the port rate of the equipment on the opposite side. When the equipment on the opposite side works in the half-duplex mode, set the working mode of the equipment on the local side to 10M Half-Duplex, 100M Half-Duplex, or Auto-Negotiation depending on the port rate of the equipment on the opposite side. The GE optical interface on the EMS6 board supports the 1000M full-duplex mode only.
Issue 02 (2009-02-25)
17-13
Parameter Maximum Frame Length
Value Range 15181535 (EFT4) 15189600 (EMS6) 1522/1632 (a logical board EMS4)
Default Value 1522
Description The value of this parameter should be greater than the maximum length of a frame among all the data frames to be transported. In the case of the EFT4 board, this parameter is invalid for Jumbo frames. In the case of the EMS6 board, this parameter has a restriction on Jumbo frames. If Jumbo frames are not considered and the accessed services are ordinary Ethernet frames that use VLAN tags or do not have VLAN tags, it is recommended that you use the default value. If the access services include services that use double tags such as QinQ services, it is recommended that you set this parameter to 1526. In the case of the IDU 605 1F/2F, set Maximum Frame Length of all the ports on the logical EMS4 board to the same value.
MAC Loopback
Non-Loopback, Inloop
Non-Loopback
When this parameter is set to Inloop, the Ethernet frame signals that are to be sent to the remote end are looped back. In normal cases, use the default value. When this parameter is set to Inloop, the Ethernet physical signals that are to be sent to the remote end are looped back. In normal cases, use the default value.
PHY Loopback
Non-Loopback, Inloop
Non-Loopback
17-14
Issue 02 (2009-02-25)
Parameter NonAutonegotiation Flow Control Mode
Value Range Disabled, Enable Symmetric Flow Control, Send Only, Receive Only (EFT4 and EMS6) Disabled, Enable Symmetric Flow Control (IFH2) Disabled, Enable (a logical board EMS4)
Default Value Disabled
Description
l
This parameter is used when Working Mode is not set to Auto-Negotiation. When this parameter is set to Enable Symmetric Flow Control, the port can send PAUSE frames and process received PAUSE frames. When this parameter is set to Send Only, the port can send PAUSE frames in the case of congestion but cannot process received PAUSE frames. When this parameter is set to Receive Only, the port can process received PAUSE frames but cannot send PAUSE frames in the case of congestion. When this parameter is set to Enable for the logical EMS4 board, the port can send PAUSE frames and process received PAUSE frames. The non-autonegotiation flow control mode of the equipment on the local side must match the non-autonegotiation flow control mode of the equipment on the opposite side. This parameter is used when Working Mode is set to Auto-Negotiation. When this parameter is set to Enable Symmetric Flow Control, the port can send and process PAUSE frames. When this parameter is set to Enable Dissymmetric Flow Control, the port can send PAUSE frames in the case of congestion but cannot process received PAUSE frames. When this parameter is set to Enable Symmetric/Dissymmetric Flow Control, the port can perform as follows:

Autonegotiation Flow Control Mode
Disabled, Enable Symmetric/ Dissymmetric Flow Control, Enable Symmetric Flow Control, Enable Dissymmetric Flow Control (EFT4 and EMS6) Disabled, Enable Symmetric Flow Control (IFH2) Disabled, Enable Symmetric Flow Control (a logical board EMS4)
Disabled
Sends and processes PAUSE frames. Sends but does not process PAUSE frames. Processes but does not send PAUSE frames.
The autonegotiation flow control mode of the equipment on the local side must match the autonegotiation flow control mode of the equipment on the opposite side.
Issue 02 (2009-02-25)
17-15
Parameter Entry Detection
Description
l
This parameter specifies whether to check the incoming packets from the port according to the TAG attributes. Set this parameter according to actual situations. When ports are configured with TAG flags, the ports process frames by using the methods provided in Table 17-4. 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 that do not have the VLAN tag (untagged frames), set this parameter to Access. When 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 using this parameter, see Table 17-4. Set this parameter according to actual situations. This parameter is valid only when TAG is set to Access or Hybrid. For using this parameter, see Table 17-4. When the VLAN priority is required to divide streams or to be used for other purposes, set this parameter according to actual situations. Generally, it is recommended that you use the default value.
TAG
Access, Tag Aware, Hybrid
Tag Aware
Default VLAN ID
1 to 4095
VLAN Priority
0 to 7
17-16
Issue 02 (2009-02-25)
Parameter Port Type
Value Range UNI, C-Aware, SAware
Default Value UNI
Description
l
When this parameter is set to UNI, the port processes data frames according to the tag attributes. When this parameter is set to C-Aware or S-Aware, the port does not process data frames according to the tag attributes but processes the data frames according to the way of processing QinQ services. In the case of QinQ services, set this parameter to the default value because the NE automatically sets network attributes according to the operation type that is set when the QinQ services are created.
Enabling Broadcast Packet Suppression
Enabled, Disabled
Disabled
This parameter specifies whether to restrict the traffic of broadcast packets according to the ratio of the broadcast packets to the total packets. When a broadcast storm may occur in the equipment on the opposite side, set this parameter to Enabled. The port discards the received broadcast packets when the ratio of the received broadcast packets to the total packets exceeds the value of this parameter. The value of this parameter should be greater than the ratio of the broadcast packets to the total packets when the broadcast storm does not occur. Generally, set this parameter to 30% or a greater value. Sets whether to enable loop detection, which is used to check whether a loop exists at the port.
Broadcast Packet Suppression Threshold
10% to 100%
30%
Loop Detection
Disabled, Enabled
Disabled
Table 17-4 Methods used by ports to process data frames Direction Type of Data Frame Tagged frame How to Process Tag aware The port receives the frame. Access The port discards the frame. Hybrida The port receives the frame.
Ingress
Issue 02 (2009-02-25)
17-17
Direction
Type of Data Frame Untagged frame
How to Process Tag aware The port discards the frame. Access The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. The port strips the VLAN tag from the frame and then transmits the frame. Hybrida The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame.
l
Egress
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.
NOTE
a: When the TAG attribute of a port on the EMS4 board (a logical board) that is supported by the IDU 605 1F/2F is set to Hybrid, the packet that is forwarded by this port remains the same as the packet that enters the bridge.
17.7.2 Modifying the Type Field of Jumbo Frames

By default, the type field of Jumbo frames processed by Ethernet boards is set to "0x8700".
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet board must be included in the slot layout.
Precautions
The EMS6 board supports the modification of the type field of Jumbo frames.
17-18
Issue 02 (2009-02-25)
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface Management > Jumbo Frame from the Function Tree. Step 2 Modify the type field of Jumbo frames.
Parameters
Parameter Jumbo Frame Value Range 00 00 to FF FF Default Value 88 70 Description This parameter specifies the type field of Jumbo frames. Set this parameter according to the type field of the accessed Jumbo frames.

This topic describes the alarms and events relevant to the Ethernet port feature and the problems that occur frequently during the application of the feature. 17.8.1 Relevant Alarms and Events When a feature of the Ethernet port becomes abnormal, the system reports corresponding alarms and RMON events. 17.8.2 FAQs This topic lists the problems that occur frequently during the application of the Ethernet port feature.

When a feature of the Ethernet port becomes abnormal, the system reports corresponding alarms and RMON events.
Relevant Alarms
l
ETH_LOS The ETH_LOS alarm indicates that the network port is disconnected. LINK_ERR The LINK_ERR alarm indicates that an error occurs on a data link. MOD_TYPE_MISMATCH
Issue 02 (2009-02-25)
The MOD_TYPE_MISMATCH alarm indicates that the modules at the ports do not match each other.
l
PORT_MODULE_OFFLINE The PORT_MODULE_OFFLINE alarm indicates that the port is not in position.
Relevant RMON Events

For RMON events, see the 23.2.3 RMON Alarms and Performance Events.
17.8.2 FAQs
This topic lists the problems that occur frequently during the application of the Ethernet port feature. Q: If the setting of the opposite equipment is unavailable, how does one find out whether the opposite Ethernet port is working in the 100M full-duplex mode or in the autonegotiation mode at the local station? A: The methods are as follows: 1. 2. 3. Set the working mode of the local Ethernet port to the auto-negotiation mode. Query the physical parameters of the local port on the NMS. If the local duplex mode is half-duplex, the working mode of the opposite Ethernet port is 100M full-duplex. Otherwise, the working mode of the opposite port is auto-negotiation.
Q: How does one determine that an Ethernet port receives a frame whose length is longer than the MTU? A: The methods are as follows: 1. 2. 3. Enable the RMON performance monitoring function for the Ethernet port. After traffic signals are transmitted for some time, check the value of the ETHOVER (received over-long packets) in the RMON performance event. If the value of the ETHOVER is not 0, the Ethernet port has received the frame whose length is greater than the MTU.
Q: How does one determine that an Ethernet port starts the flow control function? A: The methods are as follows: 1. 2. Enable the RMON performance monitoring function for the Ethernet port. After traffic signals are transmitted for some time, check the value of the RXPAUSE (received PAUSE frames) and the value of the TXPAUSE (sent PAUSE frames) in the RMON performance event. If the value of the RXPAUSE is not 0, the Ethernet port has received PAUSE frames. If the value of the TXPAUSE is not 0, the Ethernet port has sent PAUSE frames.
3.
17-20
Issue 02 (2009-02-25)
18 Encapsulation and Mapping of Ethernet Services
18
Encapsulation and Mapping of Ethernet Services
About This Chapter

To transparently transmit Ethernet frames through the optical transmission network and the radio transmission network, it is necessary to encapsulate the Ethernet frames and map them into VC containers at the access point. 18.1 Feature Description When an NE transmits Ethernet services to a microwave transmission network through an internal port (namely, VCTRUNK) of an Ethernet service board, you need to set the attributes of the internal port so that the Ethernet service board of the local NE can work with the Ethernet service board of the NE at the opposite end to realize the transmission of the Ethernet services on the microwave transmission network. 18.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the Ethernet service encapsulation and mapping feature. 18.3 Availability The Ethernet encapsulation and mapping feature requires the support of the applicable equipment and boards. 18.4 Relation with Other Features The Ethernet service encapsulation, virtual concatenation, and LCAS technology do not have any impact on other features. 18.5 Realization Principle This topic describes the realization of the encapsulation and mapping protocols of the Ethernet service, the relevant virtual concatenation, and the LCAS technology. 18.6 Planning Guide Before you plan the Ethernet encapsulation and mapping features, obtain the information of the opposite equipment. 18.7 Configuring the Internal Port of the Ethernet Board When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK) of an Ethernet board, the attributes of the internal port need to be set. Thus, the Ethernet board
works with the Ethernet board on the opposite side to realize the transmission of the Ethernet services in the network. 18.8 Maintenance Guide This topic describes how to increase/decrease the VCTRUNK bandwidth, the alarms and events relevant to the Ethernet service encapsulation and mapping, and the problems that occur frequently during the application of the feature.
18-2
Issue 02 (2009-02-25)

When an NE transmits Ethernet services to a microwave transmission network through an internal port (namely, VCTRUNK) of an Ethernet service board, you need to set the attributes of the internal port so that the Ethernet service board of the local NE can work with the Ethernet service board of the NE at the opposite end to realize the transmission of the Ethernet services on the microwave transmission network. The internal port of the Ethernet service board is the internal VCTRUNK interface and is also called the system-side interface in certain scenarios. The services are encapsulated and mapped at the internal port and are transmitted to the microwave transmission network, as shown in Figure 18-1. Figure 18-1 Internal port of the Ethernet service board
External port VCTRUNK port Backplane
Interface module
Service processing module
Encapsulation/ Mapping module
Interface conversion module
Crossconnect unit Crossconnect unit
Ethernet board
The features relevant to the external port of the Ethernet service board include the encapsulation and mapping protocol, virtual concatenation, and LCAS.
Encapsulation and Mapping Protocols

The Ethernet services are a type of packet services. The SDH optical transmission network and SDH/PDH microwave, however, realize transmission of data based on time division multiplexing. Hence, the Ethernet services can be transmitted on the transmission network only after transmission tunnels are established by using the encapsulation and mapping protocols.
Virtual Concatenation
The rate of the Ethernet service does not adapt to the rate of the standard VC container. Hence, if you directly map the Ethernet service data into a standard VC container, the transmission bandwidth is wasted to a great extent. To solve the problem, use the virtual concatenation technology to concatenate many standard VC containers to a large VC container that adapts to the rate of the Ethernet service.
LCAS
The LCAS is applied on the basis of virtual concatenation and can improve the performance of virtual concatenation. The LCAS can dynamically adjust the number of virtual containers for mapping required services to meet the bandwidth requirements of the application. As a result, the bandwidth utilization is improved.
18.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the Ethernet service encapsulation and mapping feature. 18.2.1 Encapsulation and Mapping Protocols Ethernet service is a type of packet switching service but SDH optical transmission and SDH/ PDH microwave transmission are both based on the TDMA. Therefore, tunnels must be set up for the transmission of the Ethernet service on the transmission network. 18.2.2 Virtual Concatenation The rate of the Ethernet service does not adapt to the rate of the standard VC container. Hence, if you directly map the Ethernet service data into a standard VC container, a large amount of transmission bandwidth is wasted. To solve this problem, use the virtual concatenation technology to concatenate many standard VC containers to a large VC container that adapts to the rate of the Ethernet service. 18.2.3 LCAS The link capacity adjustment scheme (LCAS) is applied on the basis of virtual concatenation and can improve the performance of virtual concatenation. The LCAS can dynamically adjust the number of virtual containers for mapping the required services, to meet the bandwidth requirements of the application. As a result, the bandwidth utilization ratio is improved.
18.2.1 Encapsulation and Mapping Protocols

Ethernet service is a type of packet switching service but SDH optical transmission and SDH/ PDH microwave transmission are both based on the TDMA. Therefore, tunnels must be set up for the transmission of the Ethernet service on the transmission network.
HDLC
The HDLC is a general data link control procedure. When using the HDLC protocol, the system encapsulates data services into HDLC-like frames as information bits and maps the frames to SDH VC containers.
LAPS
The LAPS is also a data link control procedure. It is developed based the HDLC. The LAPS complies with ITU-T X.86.
GFP
The GFP is the most widely applied general encapsulation and mapping protocol currently. It provides a general mechanism to adapt higher-layer client signal flows into the transport network and can map the variable-length payload into the byte-synchronized transport path. Client signals can be protocol data units (PDU-oriented, such as IP/PPP and Ethernet), block-code data (blockcode-oriented, such as FC and ESCON), or common bit streams. The GPF protocol complies with ITU-T G.7041. The GFP defines the following two modes to adapt to client signals:
l
Frame-mapping GFP (GFP-F)

18-4
The GFP-F is a PDU-oriented processing mode. It encapsulates the entire PDU into the GFP payload area and does not modify the encapsulated data. According to requirements, it determines whether to add a detection area for the payload area.
l
Transparent GFP (GFP-T) The GFP-T is a block-code (8B/10B code block) oriented processing mode. It extracts a single character from the received data block and maps the character into the fixed-length GFP frame.
All Ethernet boards of the OptiX RTN 600 use the GFP-F mode to perform encapsulation and mapping.
18.2.2 Virtual Concatenation

The rate of the Ethernet service does not adapt to the rate of the standard VC container. Hence, if you directly map the Ethernet service data into a standard VC container, a large amount of transmission bandwidth is wasted. To solve this problem, use the virtual concatenation technology to concatenate many standard VC containers to a large VC container that adapts to the rate of the Ethernet service. The concatenation is defined in ITU-T G.707. There are two concatenation methods: contiguous concatenation and virtual concatenation. Both methods provide concatenated bandwidth of X times Container-N at the path termination. Contiguous concatenation concatenates the contiguous C-4s in the same STM-N into an entire structure to be transported. It maintains the contiguous bandwidth throughout the whole transport. Virtual concatenation concatenates many individual VC containers (VC-12 containers, VC-3 containers, or VC-4 containers) into a bit virtual structure to be transported. The virtual concatenation breaks the contiguous bandwidth into individual VCs, transports the individual VCs, and recombines these VCs to a contiguous bandwidth at the end point of the transmission. In the case of the virtual concatenation, each VC container may be transported in different paths and there may be a transport delay difference between VC containers. Hence, there are difficulties in restoring the client signal. Virtual concatenation only requires that the path termination equipment provides the concatenation function and it can allocate bandwidth flexibly. Hence, virtual concatenation is a widely applied concatenation technology. Virtual concatenation is available in two types, virtual concatenation in a higher order path and virtual concatenation in a lower order path. A higher order virtual concatenation VC-4-Xv provides a payload area of X Container-4 (VC-4). The payload is mapped individually into X independent VC-4s. Each VC-4 has its own POH. Similarly, a lower order virtual concatenation VC-12-Xv provides a payload area of X Container-12 (VC-12). The payload is mapped individually into X independent VC-12s. Each VC-12 has its own POH, as does the virtual concatenation of VC-3s. Physical channels formed by virtual concatenation are called VCTRUNKs and are also called internal ports of the Ethernet board. The Ethernet board does not support VC-4-Xv.
18.2.3 LCAS
The link capacity adjustment scheme (LCAS) is applied on the basis of virtual concatenation and can improve the performance of virtual concatenation. The LCAS can dynamically adjust the number of virtual containers for mapping the required services, to meet the bandwidth requirements of the application. As a result, the bandwidth utilization ratio is improved. The LCAS technology has the following advantages:

l
The LCAS can dynamically adjust (add, delete, or modify) the service bandwidth without affecting the availability of the existing service. If there are failed physical channels in virtual concatenation, the LCAS shields these physical channels. Other physical channels in virtual concatenation can transfer services. Hence, this prevents a situation where the failure of a single physical channel causes interruption of services. After the failed physical channels are restored, they can transfer services.
18.3 Availability
The Ethernet encapsulation and mapping feature requires the support of the applicable equipment and boards. Table 18-1 Availability of the Ethernet encapsulation and mapping feature Feature Mapping protocol (GFP, HDLC, and LAPS) Virtual concatenation Applicable Board EFT4 (all the versions) EMS6 (all the versions) EFT4 (all the versions) EMS6 (all the versions) LCAS EFT4 (all the versions) EMS6 (all the versions) Applicable Equipment IDU 610/620 IDU 620 IDU 610/620 IDU 620 IDU 610/620 IDU 620

The Ethernet service encapsulation, virtual concatenation, and LCAS technology do not have any impact on other features.

This topic describes the realization of the encapsulation and mapping protocols of the Ethernet service, the relevant virtual concatenation, and the LCAS technology. 18.5.1 Encapsulation and Mapping The HDLC/LAPS/GFP protocol encapsulates and maps Ethernet frames as PDUs. 18.5.2 Virtual Concatenation The virtual concatenation is realized by using byte H4 or K4 as the virtual concatenation-specific multiframe indicator and sequence indicator. 18.5.3 LCAS The LCAS realizes the capacity adjustment of the virtual container by exchanging the control information between both the source and the sink side.
18.5.1 Encapsulation and Mapping

The HDLC/LAPS/GFP protocol encapsulates and maps Ethernet frames as PDUs.
Among the HDLC, LAPS, and GFP protocols, the GFP protocol is most widely applied. Hence, this topic takes the GFP protocol as an example to describe how Ethernet frames are encapsulated and mapped.
Structure of the GFP Frame

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

Octet transmission order 15 14 13 12 11 10 9 8 Bit number 5 6 7 1 6 2 5 3 PTI PFI UPI 4 4 3 5 2 6 1 7 0 Bit number 8 Octet transmission order EXI
The tHEC field protects the integrity of the type field by enabling both single-bit error correction and multi-bit error detection. The extension header field and eHEC field are used to support special data link header technologies and are seldom used in actual situations.
Type of the GFP Frame

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

The Ethernet board adopts the GFP-F adaptation mode to encapsulate Ethernet frames into the corresponding virtual container. The encapsulation process is as follows: 1. The Ethernet MAC octets from the destination address through the frame check sequence, inclusive, are placed in the GFP payload information field. Octet-alignment is maintained and bit identification within octets is maintained.
Issue 02 (2009-02-25)
18-9

Ethernet MAC frame

GFP frame PLI cHEC Type tHEC GFP extension header
Octets 7 1 6 6 2
4 1
Preamble Start of frame delimiter Destination Address (DA) Source Address (SA) Length/Type MAC client data Pad Frame Check Sequence (FCS) 2 3 4 5 6 7 8
Octets 2 2 2 2 0-60
GFP payload
Bits
Bits
2. 3. 4.
Calculate other fields of the GFP client data frame over the content of the payload. Scramble the core header and the payload area to maintain DC balance of the transported data. Map GFP client data frames into virtual containers and insert the Idle frame to realize the rate adaptation between the variable-length PDUs and the defined virtual containers.
The decapsulation process is as follows: 1. 2. 3. Check for a correct cHEC, byte by byte in the payload of the virtual container. Once a correct cHEC is detected, a GFP frame is found. Check for subsequent GFP frames frame by frame according to the PLI in the GFP frame and discard Idle frames. Descramble the payload area in the found GFP frame and extract the Ethernet MAC octets from the destination address through the frame check sequence, inclusive.
18.5.2 Virtual Concatenation

The virtual concatenation is realized by using byte H4 or K4 as the virtual concatenation-specific multiframe indicator and sequence indicator.
VC-4-Xv and VC-3-Xv

The virtual container that is formed by a VC-4-Xv/VC-3-Xv can be mapped into X individual VC-4/VC-3s which form the VC-4-Xv/VC-3-Xv. Each VC-4/VC-3 has its own POH. The POH has the same specifications as the ordinary VC-4 POH. The H4 byte in the POH is used for the virtual concatenation-specific multiframe indicator (MFI) and sequence indicator (SQ). The MFI indicates the position of a frame in the multiframe. Each frame sent by the source carries the MFI information. The sink combines the frames with the same MFI into the C-n-Xv. There are MFI-1 and MFI-2. The MFI-1 uses H4, bit 5 to bit 8 and counts from 0 to 15. The MFI-2 uses H4, bit 1 to bit 4 in frame 0 (MFI-2 bits 14) and 1 (MFI-2 bits 58). Hence, the MFI-2 counts from 0 to 255. The resulting overall multiframe is 4096 frames (= 512 ms) long. The SQ indicates the position of a frame in the C-n-Xv. The source inserts the SQ information into the frame according to the payload allocation sequence. The sink decides the sequence to extract the payload from the frames that form C-n-Xv according to the SQ. The SQ is transported in bits 1 to 4 of the H4 bytes, using frame 14 (SQ bits 1-4) and 15 (SQ bits 5-8) of MFI-1.
18-10
Issue 02 (2009-02-25)
Figure 18-4 VC-3-Xv/VC-4-Xv multiframe and sequence indicator

C-3-X/C-4-X 1 X C-3-Xv/C-4-Xv SQ = X-1 =0 SQ = 0 =0 MFI-1 = 0 X-1 MFI-2 = 0 =1 SQ = 0 =0 MFI-1 = 1 MFI-2 = 0
H
POH
POH
SQ = X-1 = 15 SQ = 0 MFI-1 = 15 = 0 MFI-2 = 0 X-1 SQ = 0 =0 MFI-1 = 0 = 15 MFI-2 = 1 SQ = X-1 = 15 SQ = 0 = 255 MFI-1 = 15 MFI-2 = 255 X-1 =0 SQ = 0 =0 MFI-1 = 0 MFI-2 = 0
H H
With the MFI and SQ, the sink can correctly restore the position of each frame in the C-n-Xv to avoid the frame alignment problem due to the different propagation delays of the frames.
VC-12-Xv
The virtual container that is formed by a VC-12-Xv can be mapped into X individual VC-12s which form the VC-12-Xv. Each VC-12 has its own POH. The POH has the same specifications as the ordinary VC-12 POH. Bit 2 of the K4 byte in the POH is used for the virtual concatenationspecific frame count and sequence indicator. Bit 2s of the K4 bytes in every 32 multiframes (one multiframe comprising four VC-12s) are extracted to form a 32-bit character string to express the frame count and sequence indicator. Bits 15 of the string express the frame count, whose value range is between 0 and 31. The structure formed by 32 multiframes has 128 frames. Hence, the resulting overall multiframe is 1096 frames (= 512 ms) long. Bits 611 of the string express the sequence indicator. The frame count/sequence indicator in the VC-12-Xv has the same usage as the multiframe indicator/ sequence indicator in the VC-4-Xv/VC-3-Xv.
18.5.3 LCAS
The LCAS realizes the capacity adjustment of the virtual container by exchanging the control information between both the source and the sink side.
Control Information
Synchronization of changes in the capacity of the transmitter (So) and the receiver (Sk) is achieved by a control packet. Each control packet describes the state of the link during the next
POH
POH
POH
Multiframe (MF)
POH
control packet. Changes are sent in advance so that the receiver can switch to the new configuration as soon as it arrives. The control packet is transported in byte H4 (higher order path) or bit 2 of byte K4 (lower order path). The control packet includes the following:
l
MFI or frame count MFI is used for the VC-4-Xv/VC-3-Xv and the frame count is used for the VC-12-Xv. Both are used to indicate the position of a multiframe. For the usage, see 18.5.2 Virtual Concatenation.
SQ SQ is used to indicate the position of a frame in the C-n-Xv. For the usage, see 18.5.2 Virtual Concatenation.
GID The GID is used for identification of the VCG. The GID bit of all members of the same VCG has the same value. The VCG refers to a group of co-located member trail termination functions that are connected to the same virtual concatenation link. The members of a VCG are the virtual containers that form the VCG. The VCG is equivalent to the generally spoken VCTRUNK.
Control field (CTRL) The control field is used to transfer the link information from the source to the sink. It must provide the status of the individual member of the link. Table 18-3 LCAS CTRL words Command FIXED ADD NORM EOS IDLE DNU Remarks This is an indication that this end uses fixed bandwidth (non-LCAS mode). This member is about to be added to the group. Normal transmission End of sequence indication and normal transmission This member is not part of the group or about to be removed. Do not use (the payload). The sink side reported FAIL status.
CRC The CRC check is performed on every control packet after it has been received, and the contents rejected if the test fails.
Member status field (MST) It reports the member status from the sink to the source. There are two states, OK and FAIL. Re-sequence acknowledge (RS-Ack) bit
18-12
When a change of the status of the members in a VCG is detected at the sink side, a notification to the source has to be performed by toggling (that is, change from '0' to '1' or from '1' to '0') the RS-Ack bit. The forward control packets from the source to the sink include the MFI, SQ, GID, CTRL, and CRC. The backward control packets from the sink to the source include the MST, RS-Ack, and CRC.
Capacity Adjustment Process

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

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

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

Before you plan the Ethernet encapsulation and mapping features, obtain the information of the opposite equipment.
Procedure
Step 1 Plan the Ethernet encapsulation and mapping protocol. Adhere to the following principles when planning the encapsulation and mapping of the Ethernet port:
l
Plan the same encapsulation and mapping protocol for both sides. It is recommended that you adopt the GFP protocol. The parameters of the encapsulation and mapping protocol at both sides should be consistent. It is recommended that you adopt the default parameters of the protocol.
Step 2 Plan VCTRUNKs. Adhere to the following principles when planning VCTRUNKs:
l
The capacity of VCTRUNKs should be determined by the actual bandwidth of the service needs. Bind only the paths in a VC-4 if possible. If the paths of several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. As each VC-4 of the Ethernet board can bind only VC-3 or VC-12, give priority to the VC-4s whose paths are already bound with the VC-12 or VC-3. As the VC-4-1 of the EFT4 board and EMS6 board can bind only VC-3 paths whereas the VC-4-2 can bind both VC-12 and VC-3 paths, give priority to the paths in the VC-4-1 if VC-3 paths are to be bound.
Step 3 Plan the LCAS. Adhere to the following principles when planning the LCAS:
l l
The LCAS at both sides must be enabled or disabled. If the LCAS is enabled at both sides, the used LCAS parameters at both sides must be consistent.
Issue 02 (2009-02-25)

l
If the opposite equipment is the third-party equipment and does not support the Huawei mode, set the LCAS mode to the standard mode. Otherwise, set the mode to the Huawei mode at both sides. It is recommended that you set the delay time to 2000 ms. It is recommended that you set the WTR time to 300 seconds. It is recommended that you disable the TSD.
l l l
----End
18.7 Configuring the Internal Port of the Ethernet Board

When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK) of an Ethernet board, the attributes of the internal port need to be set. Thus, the Ethernet board works with the Ethernet board on the opposite side to realize the transmission of the Ethernet services in the network.
Prerequisite
Precautions
The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards EFT4 and EMS6.
l
The EFT4 board supports VCTRUNKs 14, which are bound with PORTs 14 respectively. The EFT4 board does not support the setting of TAG attributes and network attributes. The EMS6 board supports VCTRUNKs 18. VCTRUNKs 18 determine the services to be transmitted depending on information of the created Ethernet services.
The following procedures describe how to configure the internal port of an EMS6 board. The EFT4 board does not support the configuration of the TAG attributes and network attributes.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Choose Internal Port. Step 2 Set the encapsulation and mapping protocol used by the port. 1. 2. Click the Encapsulation/Mapping tab. Set Mapping Protocol and the protocol parameters.
3.
18-16
Click Apply.
Step 3 Set the VC paths to be bound with the port. 1. 2. 3. 4. 5. Click the Bound Path tab. Click Configuration. The system displays the Bound Path Configuration dialog box. In Configurable Ports, select a VCTRUNK as the port to be configured. In Available Bound Paths, set Level and Direction of the bound paths. Select required items in Available Resources and Available Timeslots and click . 6. 7. Optional: Repeat Step 3.5 and bind other VCTRUNKs. Click OK.
Step 4 Configure the LCAS function for the port. 1. 2. Click the LCAS tab. Set the Enabling LCAS parameter and other LCAS parameters.
3.
Click Apply.
Step 5 Optional: Set the TAG attributes of the port. 1. 2. Click the TAG Attributes tab. Set the TAG attributes of the port.
Issue 02 (2009-02-25)
18-17
3. 1. 2.
Click Apply. Click the Network Attributes tab. Set the network attributes of the port.
Step 6 Optional: Set the network attributes of the port.
3.
Click Apply.
----End
Parameters
Parameter Mapping Protocol Scramble Value Range GFP, LAPS, HDLC Unscrambled, Scrambling Mode [X43+1], Scrambling Mode [X48+1] Yes, No Default Value GFP Scrambling Mode [X43+1] Description It is recommended that you use the default value.
l
This parameter specifies the scrambling polynomial used by the mapping protocol. It is recommended that you use the default value. This parameter is valid only when Mapping Protocol is set to LAPS or HDLC. When this parameter is set to Yes, the FCS is the result after you perform a negation operation for the CRC. When this parameter is set to No, the FCS is the CRC.
Set Inverse Value for CRC
Yes
18-18
Issue 02 (2009-02-25)
Parameter Check Field Length
Value Range FCS32, FCS16, No
Default Value FCS32
Description
l
When this parameter is set to FCS32, a 32-bit FCS is used. When this parameter is set to FCS16, a 16-bit FCS is used. When the Ethernet board uses the GFP mapping protocol, this parameter can be set to FCS32, FCS16, or No. When the Ethernet board uses the HDLC mapping protocol, this parameter can be set to FCS32 or FCS16. When the Ethernet board uses the LAPS mapping protocol, this parameter can be set to FCS32 or FCS16. It is recommended that you use the default value. When this parameter is set to Big endian, the least significant byte of the FCS is placed first and the most significant byte is placed last. When this parameter is set to Little endian, the most significant byte of the FCS is placed first and the least significant byte is placed last. It is recommended that you use the default value. This parameter specifies whether the GFP payload header contains the extension header and eHEC. It is recommended that you use the default value.
FCS Calculated Bit Sequence
Big endian, Little endian
l l
Big endian (GFP) Little endian (LAPS or HDLC)
Extension Header Option
No, Yes
No
Configurable Ports
VCTRUNKs
VCTRUNK 1
This parameter specifies the VCTRUNK whose VC paths are to be configured.
Issue 02 (2009-02-25)
18-19
Parameter Available Bound Paths
Value Range -
Default Value -
Description Adhere to the following principles to plan and set this parameter:
l
The capacity of VCTRUNKs should be determined by the actual bandwidth required by services. Bind only the paths in a VC-4 for a VCTRUNK if possible. If the paths in several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Hence, when a VCTRUNK needs to be bound with VC-3 paths, select VC-3 paths first from the VC-4 certain of whose VC-3 paths are already bound. When a VCTRUNK needs to be bound with VC-12 paths, select VC-12 paths first from the VC-4 certain of whose VC-12 paths are already bound. Give priority to the paths in the VC-4-1 if a VCTRUNK needs to be bound with VC-3 paths because the VC-4-1s of the EFT4 board and EMS6 board support only VC-3 paths whereas the VC-4-2s support both VC-12 paths and VC-3 paths. Generally, bidirectional paths are bound. This parameter specifies whether the LCAS function is enabled. The LCAS can dynamically adjust the number of virtual containers for mapping required services to meet the bandwidth requirements of the application. As a result, the bandwidth utilization ratio is improved.
Enabling LCAS
Enabled, Disabled
Disabled
18-20
Issue 02 (2009-02-25)
Parameter LCAS Mode
Value Range Huawei Mode, Standard Mode
Default Value Huawei Mode
Description
l
This parameter specifies the sequence in which the LCAS sink sends the MST control packet and Rs-Ack control packet. When this parameter is set to Huawei Mode, the LCAS sink first sends the RsAck and then sends the MST. When this parameter is set to Standard Mode, the LCAS sink first sends the MST and then sends the Rs-Ack. If the equipment on the opposite side is the third-party equipment and does not support the Huawei mode, it is recommended that you set this parameter to Standard Mode. Otherwise, set this parameter to Huawei Mode. When a member link is faulty, the LCAS performs switching after a delay of time to prevent the situation where an NE simultaneously performs a protection switching such as SNCP and performs an LCAS switching. This parameter specifies the duration of the delay. If the paths of the VCTRUNK are configured with protection, it is recommended that you set this parameter to 2000 ms. Otherwise, set this parameter to 0. When the time after a member link is restored to normal reaches the set value of this parameter, the VCG uses the restored member link. It is recommended that you use the default value. This parameter specifies whether the TSD is used as a condition for determining whether a member link is faulty. In the case of the VC-12, the TSD refers to the BIP_SD. In the case of the VC-3, the TSD refers to the B3_SD_VC3. It is recommended that you use the default value.
Hold Off Time (ms)
0, any integer that ranges from 2000 to 10000 and has a step of 100
2000
WTR Time(s)
0 to 720
300
TSD
Enabled, Disabled
Disabled
Issue 02 (2009-02-25)
18-21
Parameter Entry Detection
Description
l
This parameter specifies whether to check the incoming packets from the port according to the TAG attributes. Set this parameter according to actual situations. When ports are configured with TAG flags, the ports process frames by using the methods provided in Table 18-4. 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 that do not have the VLAN tag (untagged frames), set this parameter to Access. When 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 using this parameter, see Table 18-4. Set this parameter according to actual situations. This parameter is valid only when TAG is set to Access or Hybrid. For using this parameter, see Table 18-4. When the VLAN priority is required to divide streams or to be used for other purposes, set this parameter according to actual situations. Generally, it is recommended that you use the default value.
TAG
Access, Tag Aware, Hybrid
Tag Aware
Default VLAN ID
1 to 4095
VLAN Priority
0 to 7
18-22
Issue 02 (2009-02-25)
Parameter Port Type
Value Range UNI, C-Aware, SAware
Default Value UNI
Description
l
When this parameter is set to UNI, the port processes data frames according to the tag attributes. When this parameter is set to C-Aware or S-Aware, the port does not process data frames according to the tag attributes but processes the data frames according to the way of processing QinQ services. In the case of QinQ services, set this parameter to the default value because the NE automatically sets network attributes according to the operation type that is set when the QinQ services are created.
NOTE
The Mapping Protocol and protocol parameters set for VCTRUNKs at one end of a transmission line must be the same as the Mapping Protocol and protocol parameters set for VCTRUNKs at the other end of the transmission line. The Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at one end of a transmission line must be the same as the Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at the other end of the transmission line. The timeslots to which the paths bound with a VCTRUNK correspond must be the same at both ends of a transmission line.
Table 18-4 Methods used by ports to process data frames Direction Type of Data Frame Tagged frame Untagged frame How to Process Tag Aware The port receives the frame. The port discards the frame. Access The port discards the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. Hybrid The port receives the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame.
Ingress
Issue 02 (2009-02-25)
18-23
Direction
Type of Data Frame Tagged frame
How to Process 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
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.

This topic describes how to increase/decrease the VCTRUNK bandwidth, the alarms and events relevant to the Ethernet service encapsulation and mapping, and the problems that occur frequently during the application of the feature. 18.8.1 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth When the LCAS function is enabled on an NE, you can dynamically increase or decrease the VCTRUNK-bound paths to increase or decrease the bandwidth. The operation does not affect services. 18.8.2 Relevant Alarms and Events When the encapsulation and mapping of the Ethernet service becomes abnormal, the system reports corresponding alarms and abnormal events. 18.8.3 FAQs This topic lists the problems that occur frequently during the application of the Ethernet encapsulation and mapping feature.
18.8.1 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth

When the LCAS function is enabled on an NE, you can dynamically increase or decrease the VCTRUNK-bound paths to increase or decrease the bandwidth. The operation does not affect services.
Prerequisite
Procedure
Step 1 Select the Ethernet board from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select Internal Port. Step 2 Click the Bound Path tab. Step 3 Click Configuration. The system displays the Bound Path Configuration dialog box. Step 4 Optional: Dynamically increase the VCTRUNK bandwidth. 1. 2. 3. In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select desired items in Available Resources and Available Timeslots and click . 4. Optional: Repeat Step 4.3 and bind other VC paths.
Step 5 Optional: Dynamically decrease the VCTRUNK bandwidth. 1. 2. 3. Do not select the Display in Combination check box. Select the VC paths to be deleted in Selected Bound Paths and click Optional: Repeat Step 5.2 to delete other VC paths. .
Issue 02 (2009-02-25)
18-25
Parameters
For specific parameters, see 18.7 Configuring the Internal Port of the Ethernet Board.

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

l
LCAS event: Adding a member succeeded This abnormal event indicates that within the specified time (10 seconds), the member added into the VCTRUNK already carries traffic.
LCAS event: Adding a member timed out This abnormal event indicates that within the specified time (10 seconds), the member added into the VCTRUNK cannot carry traffic.
LCAS event: Deleting a member succeeded This abnormal event indicates that within the specified time (10 seconds), the member deleted from the VCTRUNK does not carry traffic any longer.
LCAS event: Deleting a member timed out and the member is forcedly deleted This abnormal event indicates that within the specified time (10 seconds), the LCAS fails to enable the VCTRUNK to delete the member and as a result the local end forcedly deletes the member.
LCAS event: Bandwidth restored This abnormal event indicates that the member whose link is faulty starts to carry traffic again.
18.8.3 FAQs
This topic lists the problems that occur frequently during the application of the Ethernet encapsulation and mapping feature.
None.
18-28
Issue 02 (2009-02-25)
19 VLAN
19
About This Chapter
VLAN
The Ethernet switching processing board supports the virtual local area network (VLAN) function that complies with IEEE 802.1q. 19.1 Feature Description According to specific rules, a real network topology can be divided into several logical subnets, which are referred to as VLANs. The broadcast packets of a VLAN can be transmitted only within this VLAN. That is, one VLAN corresponds to a specific broadcast domain. The VLAN allows users to solve the broadcast flooding problem at low costs. In addition, the VLAN offers several revolutionary benefits. 19.2 Basic Concepts This topic decribes the basic concepts that you need to be familiar with before you use the VLAN feature. 19.3 Availability The VLAN feature requires the support of the applicable equipment and boards. 19.4 Relation with Other Features The port whose VLAN feature is enabled cannot transparently transmit Ethernet services. 19.5 Realization Principle Realization of the VLAN function is related to the port attribute and service type. 19.6 Planning Guide Plan related parameters according to the specific application of VLAN. 19.7 Configuration Guide This topic describes the configuration flow and the corresponding configuration tasks of the EVPL service that uses the VLAN feature. Two examples are provided as a supplement to the configuration. 19.8 Configuration Example (PORT-Shared EVPL Service) This topic provides an example to describe how to configure the PORT-shared EVPL service 19.9 Configuration Example (VCTRUNK-Shared EVPL Service) This topic provides an example to describe how to configure the VCTRUNK-shared EVPL service.
19 VLAN
19.10 Maintenance Guide This topic describes the alarms and performance events relevant to the VLAN feature, and the problems that occur frequently during the application of the VLAN feature.
19-2
Issue 02 (2009-02-25)
19 VLAN

According to specific rules, a real network topology can be divided into several logical subnets, which are referred to as VLANs. The broadcast packets of a VLAN can be transmitted only within this VLAN. That is, one VLAN corresponds to a specific broadcast domain. The VLAN allows users to solve the broadcast flooding problem at low costs. In addition, the VLAN offers several revolutionary benefits.
Improving Bandwidth Utilization

The generation of a large number of unnecessary broadcast packets is avoided because the broadcast packets are forwarded within the range of a specific VLAN rather than on the entire LAN. This improves the bandwidth utilization. In addition, because a VLAN is actually a small broadcast domain, if the routing of a packet is not discovered, the switch transmits this packet only to the ports that belong to this VLAN rather than to all ports of the switch. Hence, the packet forwarding is restricted to a specific VLAN, which also improves the network utilization.
Isolating Users and Improving Network Security

The packets of a VLAN are forwarded within the range of this VLAN, but not forwarded to the network equipment of other VLAN users. Hence, using VLANs can isolate different users and can protect the privacy of user information.
Realizing Virtual Workgroups

The final goal of using VLANs is to establish the virtual workgroup model, that is, to establish a dynamic organization environment. This enables the members of the same VLAN to communicate with each other as if they were in the same VLAN, even when they move to other positions of the network. The broadcast packets are restricted to this VLAN without affecting the members of other VLANs. If the network location of one member is changed but the VLAN to which the member belongs is not changed, the configuration of this member can remain unchanged. If the physical location of one member is not changed but the VLAN to which the member belongs is changed, the network administrator needs to modify the configuration of this member. The virtual workgroup is a long-term goal, which requires support in other aspects.
19.2 Basic Concepts

This topic decribes the basic concepts that you need to be familiar with before you use the VLAN feature. 19.2.1 Frame Format To realize the VLAN function, IEEE 802.1q defines the Ethernet frame that contains the VLAN information, namely, the tagged frame. The tagged frame is also called the 802.1q frame. Compared with the common Ethernet frame, this type of frame is added with a 4-byte 802.1q header. 19.2.2 TAG Attribute Depending on the different methods for processing the tagged frame and the untagged frame, the TAG attribute of a switch port can be set to tag aware, access, and hybrid.
19 VLAN
19.2.3 Application A VLAN allows new application scenarios for the Ethernet private line (EPL) service and the Ethernet private LAN (EPLAN) service.
19.2.1 Frame Format

To realize the VLAN function, IEEE 802.1q defines the Ethernet frame that contains the VLAN information, namely, the tagged frame. The tagged frame is also called the 802.1q frame. Compared with the common Ethernet frame, this type of frame is added with a 4-byte 802.1q header. Figure 19-1 Tagged frame format
Destination address Source address 4 bytes 802.1q header FCS (CRC-32)
Length/Type
Data
TCI TPID 16 bits PCP 3 bits CFI 1 bit VID 12 bits
The 4-byte 802.1q header is divided into two parts: tag protocol identifier (TPID) and tag control information (TCI). The TCI is divided into three parts: user_priority, canonical format indicator (CFI), and VLAN identifier (VID).
l
TPID The TPID is a 2-byte field, and it identifies an Ethernet frame as a tagged frame. The value is always 0x8100. When the network equipment that cannot identify the tagged frame receives the tagged frame, the equipment discards this frame.
PCP The priority code point (PCP) identifies the priority of an Ethernet frame. This field can be used to provide the requirement for the service quality.
CFI The CFI is a 1-bit filed, and it is used in certain physical networks that adopt the ring topology. This field is not processed in the Ethernet.
VID The VLAN ID is a 12-bit field, and it indicates the VLAN that the frame belongs to. Restricted to the field length, the value of the VID ranges from 1 to 4095.
19.2.2 TAG Attribute

Depending on the different methods for processing the tagged frame and the untagged frame, the TAG attribute of a switch port can be set to tag aware, access, and hybrid.
19-4
Issue 02 (2009-02-25)
19 VLAN
Table 19-1 Data frame processing method of the switch port Direction Type of Frame Processing Method Tag Aware Ingress Tagged frame Untagged frame Receives the frame. Discards the frame. Access Discards the frame. Receives the frame after the untagged frame is added with the port VID (PVID). Transmits the frame after the PVID of the tagged frame is stripped. Hybrida Receives the frame. Receives the frame after the untagged frame is added with the PVID. Transmits the frame after the PVID of the tagged frame is stripped if the VID equals the PVID. Directly transmits the frame if the VID does not equal the PVID.
NOTE
Egress
Tagged frame
Transmits the frame.
l l
The untagged frame cannot be transmitted through the port. When the Ethernet switching board works in the Ethernet switching state, it can be considered as an Ethernet switch. In this case, the ports of the Ethernet switching board can be classified into two categories: the external port (PORT) and the internal port (VCTRUNK). Each port corresponds to a specific TAG attribute. When the Ethernet switching board works in the Ethernet transparent transmission state, it does not check the TAG attribute. Hence, the port transparently transmits the tagged frame and the untagged frame.
CAUTION
a:
When the TAG attribute of a port on the EMS4 board (a logical board) that is supported by the IDU 605 1F/2F is set to Hybrid, the packet that is forwarded by this port remains the same as the packet that enters the bridge.
19.2.3 Application
A VLAN allows new application scenarios for the Ethernet private line (EPL) service and the Ethernet private LAN (EPLAN) service. In the case of the EPL service, after the VLAN is adopted, the Ethernet board can divide the flow by port and VLAN ID other than only by port, which allows the development of the EPL service to the Ethernet virtual private line (EVPL) service. In the case of the EPLAN service,
19 VLAN
after the VLAN is adopted, the Ethernet board can create the 802.1q bridge, which allows the development of the EPLAN service to the Ethernet virtual private LAN (EVPLAN) service. This topic only describes the application of the VLAN in the EPL service. For details about the 802.1q bridge, see 20.2.1 Bridge.
PORT-Shared EVPL Service

Figure 19-2 shows an example of the PORT-shared EVPL service. The service between the headquarters and branch A is transmitted over the VLANs whose VIDs are from 100 to 110, and the service between the headquarters and branch B is transmitted over the VLANs whose VIDs are from 200 to 210. If the Ethernet board at NE1 supports VLAN, use an Ethernet port whose port attribute is tag aware to access the services from the headquarters. Then, map the services of different VLANs into different VCTRUNKs. In this way, the services of different VLANs are isolated during transmission. Figure 19-2 PORT-shared EVPL service
VLAN100-110 VLAN200-210 PORT1 Headquaters NE1 VLAN100-110 VCTRUNK1 NE2 VLAN200-210 VCTRUNK2 NE3 Branch B Branch A
VCTRUNK-Shared EVPL Service

Figure 19-3 shows an example of the VCTRUNK-shared EVPL service. Department A and department B at NE1 need to transmit services to their respective departments at NE2. If the Ethernet board supports VLAN, use two Ethernet ports at NE1 whose port attributes are access and that have different PVIDs to access the services of department A and department B at NE1. Then, map the services into the same VCTRUNK. In this way, the services of different VLANs are transmitted over the same VCTRUNK. Because the services of the two departments can share the bandwidth, the bandwidth utilization is improved. Figure 19-3 VCTRUNK-shared EVPL service
PORT1 VLAN100 NE1 VLAN200 PORT2 VCTRUNK1
VLAN100
PORT1 NE2
VLAN200 PORT2 B
19-6
Issue 02 (2009-02-25)
19 VLAN
19.3 Availability
The VLAN feature requires the support of the applicable equipment and boards. Table 19-2 Availability of the VLAN Feature VLAN Applicable Board EMS6 (all the versions) NOTE
a:
Applicable Equipment IDU 620 IDU 605 1F/2F a
IDU 605 1F/2F supports the LAN service that is based on the VLAN, but does not support the Ethernet line service.

The port whose VLAN feature is enabled cannot transparently transmit Ethernet services.

Realization of the VLAN function is related to the port attribute and service type. When the VLAN function is enabled, the switch processes a data frame as follows: 1. 2. Processes the data frame that is input into the switch through a port, according to the attribute of this port. For details, see Table 19-1. Forwards this data frame according to the service type.
l
In the case of the line service, the switch forwards this data frame to the corresponding ports based on the service configuration. In the case of the VLAN service, the switch forwards this data frame to the corresponding port based on the MAC address table. For details, see 20.5.1 Bridge.
3.
Processes the data frame that is output from this port on the switch, according to the attribute of this port. For details, see Table 19-1.
19.6 Planning Guide

Plan related parameters according to the specific application of VLAN.
Prerequisite
You must learn about the specific application of VLAN.
Precautions
NOTE
This topic describes the planning based on the cases in 19.2.3 Application.
Issue 02 (2009-02-25)
19-7
19 VLAN
Procedure
Step 1 According to the actual requirements, plan the line service type. When planning the line service type, adhere to the following principles:
l l
In the case of the point-to-point service, use the Ethernet transparent transmission service. If the service of the same PORT needs to be divided by VLAN and if the service frame is the tagged frame, use the PORT-shared EVPL service. If the services of different PORTs need to share one transmission channel and if the service frame is the untagged frame, use the VCTRUNK-shared EVPL service. In the case of other requirements that are not contained in the preceding description, use the QinQ service or Layer 2 switching service.
Step 2 Optional: Plan the PORT-shared EVPL service. When planning the PORT-shared EVPL service, adhere to the following principles:
l l
Set TAG of the PORT to Tag Aware. Allocate the VLAN service of this PORT to different VCTRUNKs by VLAN ID.
Step 3 Optional: Plan the VCTRUNK-shared EVPL service. When planning the VCTRUNK-shared EVPL service, adhere to the following principles:
l l
Set TAG of the PORT to Access. Because the PVIDs of different PORTs should be different, configure the PVIDs of PORTs by user. For example, if the PVIDs of the PORTs used by user A range from 100 to 199, the PVIDs of the PORTs used by user B should range from 200 to 299. The services of different PORTs should share one VCTRUNK.
----End

This topic describes the configuration flow and the corresponding configuration tasks of the EVPL service that uses the VLAN feature. Two examples are provided as a supplement to the configuration. 19.7.1 Configuration Flow This topic describes the configuration flow of the EVPL service that uses the VLAN feature. 19.7.2 Creating Ethernet Line Service To enable the Ethernet switching board to transmit the line service, perform certain operations to configure the related information, such as the service source and service sink.

This topic describes the configuration flow of the EVPL service that uses the VLAN feature.
19-8
Issue 02 (2009-02-25)
19 VLAN
Figure 19-4 Configuration flow of the EPL service that uses the VLAN feature (PORT-shared or VCTRUNK-shared EVPL service)
Start 1
Configure the Ethernet external port
Configure the Ethernet internal port
Create the Ethernet line service
4 Create the crossconnection of the Ethernet service End
Table 19-3 Configuration flow of the EVPL service that uses the VLAN feature (PORT-shared EVPL service) Number 1 Description
l
Set the TAG attributes of the PORT as follows:

Set TAG to Tag Aware. Set Ingress Check to Enabled.
For the configuration process, see 17.7.1 Configuring External Ethernet Ports. Configure one VCTRUNK corresponding to each data stream that is from the service of the PORT. Set the TAG attributes of the VCTRUNK as follows:

Set TAG to Tag aware. Set Ingress Check to Enabled.
For the configuration process, see 18.7 Configuring the Internal Port of the Ethernet Board. Configure the EVPL service from the PORT+VLAN to the specified VCTRUNK. For the configuration process, see 19.7.2 Creating Ethernet Line Service.
Issue 02 (2009-02-25)
19-9
19 VLAN
Number 4
Description Create the cross-connection from the paths that are bound to the VCTRUNK to the corresponding timeslots on the line.
Table 19-4 Configuration flow of the EVPL service that uses the VLAN feature (VCTRUNKshared EVPL service) Number 1 Description
l
Set the TAG attributes of the PORT as follows:

Set TAG to Access. Set Default VLAN ID of PORTs to different values. Set Ingress Check to Enabled.
For the configuration process, see 17.7.1 Configuring External Ethernet Ports. Configure a shared VCTRUNK. Set the TAG attributes of the VCTRUNK as follows: Set TAG to Tag aware. Set Ingress Check to Enabled. For the configuration process, see 18.7 Configuring the Internal Port of the Ethernet Board. Configure the EVPL service from the PORT to the specified VCTRUNK +VLAN. For the configuration process, see 19.7.2 Creating Ethernet Line Service.
l l l
Create the cross-connection from the paths that are bound to the VCTRUNK to the corresponding timeslots on the line.
NOTE
If the QoS of the EVPL service needs to be set, see 21 QoS.
19.7.2 Creating Ethernet Line Service

To enable the Ethernet switching board to transmit the line service, perform certain operations to configure the related information, such as the service source and service sink.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be added in the slot layout.
Precautions
l
This topic does not describe the method for creating the QinQ service.
19-10

l
19 VLAN
IDU 620 supports the Ethernet switching board EMS6. The EFT4 board is an Ethernet transparent transmission board, and the PORTs of the EFT4 board correspond to the VCTRUNKs. Hence, you do not need to create the Ethernet line service.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click New. The Create Ethernet Line Service dialog box is displayed. Step 3 Set the attributes of the Ethernet line service.
Step 4 Optional: Set the port attributes of the source port and sink port.
NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same as the result of directly setting the Ethernet service port attributes.
Step 5 Optional: Set the bound path. 1. 2. 3. 4. Click Configuration. The Bound Path Configuration dialog box is displayed. In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select required items in Available Resources and Available Timeslots and click . 5.
Issue 02 (2009-02-25)
Optional: Repeat Step 5.4 to bind other VC paths.

19 VLAN
NOTE
6.
Click OK.
Parameters
Parameter Service Type Value Range EPL, EVPL (QinQ) Default Value EPL Description When creating the non-QinQ private line service, set this parameter to EPL.
19-12
Issue 02 (2009-02-25)
19 VLAN
Parameter Direction
Value Range Unidirectional, Bidirectional
Default Value Bidirectional
Description
l
When setting this parameter to Unidirectional, create the service only from the service source to the service sink. That is, the service source is forwarded only to the sink port. When setting this parameter to Bidirectional, create the service from the service source to the service sink and the service from the service sink to the service source. That is, when the service source is forwarded to the sink port, the service sink is forwarded to the source port. Generally, it is recommended that you use the default value. This parameter indicates the port where the service source resides. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, use a specific PORT as the source port. You can set this parameter to null, a number, or several numbers. When setting this parameter to several numbers, use "," to separate these discrete values and use "" to indicate continuous numbers. For example, "1, 36" indicates numbers 1, 3, 4, 5, and 6. The number of VLANs set in this parameter should be the same as the number of VLANs set in Sink C-VLAN (e.g. 1,3-6). When you set this parameter to null, all the services of the source port work as the service source. When you set this parameter to a non-null value, only the services of the source port whose VLAN IDs are included in the set value of this parameter work as the service source. This parameter indicates the port where the service sink resides. Do not set the value of this parameter to the same as the value of Source Port. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, use a VCTRUNK as the sink port.
Source Port
A specific PORT or VCTRUNK
PORT1
Source C-VLAN (e.g. 1,3-6)
14095
Sink Port
PORT1
Issue 02 (2009-02-25)
19-13
19 VLAN
Parameter Sink C-VLAN (e.g. 1,3-6)
Value Range 14095
Default Value -
Description
l
You can set this parameter to null, a number, or several numbers. When setting this parameter to several numbers, use "," to separate these discrete values and use "" to indicate continuous numbers. For example, "1, 36" indicates numbers 1, 3, 4, 5, and 6. The number of VLANs set in this parameter should be the same as the number of VLANs set in Source CVLAN (e.g. 1,3-6). When you set this parameter to null, all the services of the sink port work as the service sink. When you set this parameter to a non-null value, only the services of the sink port whose VLAN IDs are included in the set value of this parameter work as the service sink.
Port Enabled TAG
Enabled, Disabled Access, Tag Aware, Hybrid
Tag Aware
When the source port or the sink port is set to a PORT, set Port Enabled to Enabled.
l
When all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware. When all of the accessed services are not frames with the VLAN tag (untagged frames), set this parameter to Access. When the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid.
Configurable Ports
VCTRUNKs
VCTRUNK 1
19-14
Issue 02 (2009-02-25)
19 VLAN
Value Range -
Default Value -
l
The capacity of VCTRUNKs should be determined by the actual bandwidth required by services. Bind only the paths in a VC-4 for a VCTRUNK if possible. If the paths in several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Hence, when a VCTRUNK needs to be bound with VC-3 paths, select VC-3 paths first from the VC-4 certain of whose VC-3 paths are already bound. When a VCTRUNK needs to be bound with VC-12 paths, select VC-12 paths first from the VC-4 certain of whose VC-12 paths are already bound. Give priority to the paths in the VC-4-1 if a VCTRUNK needs to be bound with VC-3 paths because the VC-4-1s of the EFT4 board and EMS6 board support only VC-3 paths whereas the VC-4-2s support both VC-12 paths and VC-3 paths. Generally, bidirectional paths are bound.
19.8 Configuration Example (PORT-Shared EVPL Service)

This topic provides an example to describe how to configure the PORT-shared EVPL service
Precautions
NOTE
l l
For details about the service configured in this example, refer to the description of the PORT-shared EVPL service in 19.2.3 Application. Because NE2 and NE3 in this example are both configured with the point-to-point EVPL service, only the configuration of NE1 is described here.
Procedure
Step 1 Set the port attributes of PORT. See 17.7.1 Configuring External Ethernet Ports. Set TAG attributes of PORT1 as follows:
l
Set TAG to Tag Aware.

Issue 02 (2009-02-25)
19 VLAN
l
Set Ingress Check to Enabled.
Step 2 Set the port attributes of VCTRUNK1 and VCTRUNK2. See18.7 Configuring the Internal Port of the Ethernet Board. Set the TAG attributes of VCTRUNK1 and VCTRUNK2 as follows:
l l
Set TAG to Tag Aware. Set Ingress Check to Enabled.
Step 3 Configure the EVPL service between PORT1 and VCTRUNK1. See19.7.2 Creating Ethernet Line Service. Set the parameters as follows:
l l l l
Set Source Port to PORT1. Set Source C-VLAN (e.g.1,3-6) to 100110. Set Sink Port to VCTRUNK1. Set Sink C-VLAN (e.g.1,3-6) to 100110.
Step 4 Configure the EVPL service between PORT1 and VCTRUNK2. See 19.7.2 Creating Ethernet Line Service. Set the parameters as follows:
l l l l
Set Source Port to PORT1. Set Source C-VLAN (e.g.1,3-6) to 200-210. Set Sink Port to VCTRUNK2. Set Sink C-VLAN (e.g.1,3-6) to 200-210.
Step 5 Create the cross-connection from the paths that are bound to the VCTRUNK to the corresponding timeslots on the line. ----End
19.9 Configuration Example (VCTRUNK-Shared EVPL Service)

This topic provides an example to describe how to configure the VCTRUNK-shared EVPL service.
Precautions
NOTE
l l
For details about the service configured in this example, refer to the description of the VCTRUNK-shared EVPL service in19.2.3 Application. Because the service configuration of NE1 is the same as the service configuration of NE2 in this example, only the configuration of NE1 is described here.
19-16
Issue 02 (2009-02-25)
19 VLAN
Procedure
Step 1 Set the port attributes of PORT1. See 17.7.1 Configuring External Ethernet Ports. Set the TAG attributes of PORT1 as follows:
l l l
Set TAG to Access. Set Default VLAN ID to 100. Set Ingress Check to Enabled.
Step 2 Set the port attributes of PORT2. See 17.7.1 Configuring External Ethernet Ports. Set the TAG attributes of PORT2 as follows:
l l l
Set TAG to Access. Set Default VLAN ID to 200. Set Ingress Check to Enabled.
l l l l
l l l l

This topic describes the alarms and performance events relevant to the VLAN feature, and the problems that occur frequently during the application of the VLAN feature. 19.10.1 Relevant Alarms and Events The VLAN feature may cause changes in RMON performance. 19.10.2 FAQs This topic lists the problems that occur frequently during the application of the VLAN feature.
19 VLAN

The VLAN feature may cause changes in RMON performance.
Relevant Alarms
None.

None.
Relevant RMON Performance Events

See 23.2.3 RMON Alarms and Performance Events.
19.10.2 FAQs
This topic lists the problems that occur frequently during the application of the VLAN feature. Q: Why should Ingress Check be set to Enabled when the VLAN feature is used? A: When Ingress Check is set to Enabled, the Ethernet switching board can check the VLAN tag according to TAG attributes. Q: What are the relations among the VLAN, C-VLAN, and S-VLAN? A: C-VLAN and S-VLAN are concepts that are used in the case of the QinQ service. The CVLAN refers to the VLAN on the client side, and the S-VLAN refers to the VLAN at the service layer of operators. The VLAN that is commonly used equals the C-VLAN of the QinQ service.
19-18
Issue 02 (2009-02-25)
20
About This Chapter
Layer 2 Switching
To realize the EPLAN service, the Ethernet switching and processing board can create one bridge or multiple bridges. Each bridge can realize the Layer 2 switching of packets among mounted ports and relevant features. 20.1 Feature Description The Layer 2 switching refers to the packet switching among switch ports by using the 802.1d, 802.1q, or 802.1ad algorithm. This topic describes the bridge, and the features relevant to the Layer 2 switching, such as STP/RSTP, IGMP Snooping, and broadcast packet suppression, which is the core of the Layer 2 switching. 20.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the Layer 2 switching feature. 20.3 Availability The Layer 2 switching feature requires the support of the applicable equipment and boards. 20.4 Relation with Other Features The Layer 2 switching has different relations with other features. 20.5 Realization Principle The bridge, STP/RSTP, and IGMP Snooping comply with the relevant IEEE standards. 20.6 Planning Guide Plan the relevant parameters of the Layer 2 switching service according to the actual situation of microwave links. 20.7 Configuration Guide This topic describes the configuration tasks relevant to the Layer 2 switching feature. 20.8 Maintenance Guide This topic describes the maintenance operations, alarms and performance events that are related to the Layer 2 switching, and the problems that occur frequently during the application of the Layer 2 switching.
Issue 02 (2009-02-25)
20-1

The Layer 2 switching refers to the packet switching among switch ports by using the 802.1d, 802.1q, or 802.1ad algorithm. This topic describes the bridge, and the features relevant to the Layer 2 switching, such as STP/RSTP, IGMP Snooping, and broadcast packet suppression, which is the core of the Layer 2 switching.
Bridge
A bridge refers to a functional unit that realizes the interconnection of two or more LANs. In the case of the Ethernet service boards that have the Layer 2 switching capability, the switching domain can be divided into multiple independent sub-switching domains. As a result, different bridges can access each other only when there are interconnected services. Each bridge is configured independently and uses VLANs independently. That is, different bridges can use the same VLAN.
STP/RSTP
Spanning Tree Protocol (STP) applies to a loop network to realize path redundancy backup by using certain algorithms. STP prunes a loop network into a tree network without loops. This helps to avoid proliferation and infinite loop of packets on the loop network. The rapid spanning tree protocol (RSTP) is an update version of the STP. Compared with the STP, the RSTP can stabilize the network topology more rapidly.
IGMP Snooping
If the multicast router exists on the network, the bridge can start the IGMP Snooping to realize the multicast function with the cooperation of the router.
Broadcast Packet Suppression

To prevent broadcast storm from flooding, enable the broadcast packet suppression function for an Ethernet port to limit the traffic of the broadcast packets that enter the Layer 2 switch.
20.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the Layer 2 switching feature. 20.2.1 Bridge A bridge refers to a functional unit that realizes the interconnection of two or more LANs. 20.2.2 STP/RSTP When the network topology of the Ethernet service forms loops, enable the STP or RSTP. 20.2.3 IGMP Snooping If the multicast router exists in the network, enable the IGMP Snooping for the bridge to realize the multicast function with the cooperation of the router. 20.2.4 Broadcast Packet Suppression
You can enable the broadcast packet suppression function that is based on the Ethernet port to prevent spreading of the broadcast storm, through restricting the traffic of the broadcast packet that enters the Layer 2 switch.
20.2.1 Bridge
A bridge refers to a functional unit that realizes the interconnection of two or more LANs.
VB and LP
VB, which is originally put forward by Huawei, is short for various bridge. In the case of the Ethernet boards that have the Layer 2 switching capability, the switching domain can be divided into multiple independent sub-switching domains. A VB contains several logic ports (LPs). By configuring the mounting relation, you can mount multiple external ports and VCTRUNK ports to one VB. One external port or VCTRUNK port cannot be mounted to different LPs on one VB. Figure 20-1 lists the relations among the VB, LP, external port, and VCTRUNK port. Figure 20-1 Relations among the VB, LP, external port, and VCTRUNK port
Ethernet Switching Board
VB1 PORT1 PORT2 LP1 LP2 LP3 LP4 LP5 LP6 VCTRUNK1 VCTRUNK2 VCTRUNK3
PORT3
Bridge Type
The Ethernet switching board supports three types of bridges: 802.1d bridge, 802.1q bridge, and 802.1ad bridge. As shown in Figure 20-2, the services on different 802.1d bridges are isolated, but the services of different VLANs on one bridge are not isolated. The services on different 802.1q bridges are isolated and the services of different VLANs on one bridge are also isolated. Figure 20-2 802.1d bridge and 802.1q bridge
VCTRUNK1 VCTRUNK2 VCTRUNK3 VCTRUNK4 VCTRUNK5 VCTRUNK6
PORT1 PORT2 PORT3 VLAN1 VLAN2 VLAN3 ... 802.1d bridge
PORT1 PORT2 PORT3
VLAN1 VLAN2
VLAN3 802.1q bridge
Logical port
Issue 02 (2009-02-25)
20-3
As shown in Figure 20-3, two conditions may occur for the 802.1ad bridge.
l
When Bridge Switch Mode is set to SVL/Ingress Filter Disable, the services on different bridges are isolated but the services of different S-VLANs on one bridge are not isolated. When Bridge Switch Mode is set to IVL/Ingress Filter Enable, the services on different bridges are isolated and the services of different S-VLANs on one bridge are also isolated.
Figure 20-3 802.1ad Bridge
PORT1 PORT2 PORT3 S-VLAN1 S-VLAN2 S-VLAN3 ... 802.1ad bridge IVL/Ingress Filter Enable
PORT1 PORT2 PORT3
S-VLAN1 S-VLAN2
S-VLAN3 802.1ad bridge
Logic Port
SVL/Ingress Filter Disable
Table 20-1 Three Types of Bridges Supported by the Ethernet Switching Board 802.1d Bridge Bridge switch mode VLAN filtering table Ingress filtering SVL/Ingress Filter Enable Not configured Disabled: Does not check the VLAN tag. 802.1q Bridge IVL/Ingress Filter Enable Required Enabled: Checks the VLAN tag. If the VLAN ID does not equal the VLAN ID of the port defined in the VLAN filtering table, the packet is discarded. IVLb 802.1ad Bridge SVL/Ingress Filter Disable Not configured Disabled: Does not check the VLAN tag. IVL/Ingress Filter Enable Required Enabled: Checks the SVLAN tag. If the VLAN ID does not equal the VLAN ID of the port defined in the VLAN filtering table, the packet is discarded. IVLb
Bridge learning mode
SVLa
SVLa
20-4
Issue 02 (2009-02-25)
802.1d Bridge Packet forwarding mode Obtains the packet forwarding port by querying the MAC address table, according to the destination MAC address of the packet. Forwards the broadcast packet to all the ports on the bridge.
802.1q Bridge Obtains the packet forwarding port by querying the MAC address table, according to the destination MAC address and VLAN ID of the packet. Forwards the broadcast packet to the ports that are specified in the VLAN filtering table. UNI
802.1ad Bridge Obtains the packet forwarding port by querying the MAC address table, according to the destination MAC address of the packet. Forwards the broadcast packet to all the ports on the bridge. Obtains the packet forwarding port by querying the MAC address table, according to the destination MAC address and VLAN ID of the packet. Forwards the broadcast packet to the ports that are specified in the S-VLAN filtering table. C-aware S-aware
Range of broadcasting
Mount port attribute
UNI
C-aware S-aware
NOTE
l l l
a: When the bridge uses the shared VLAN learning (SVL) mode, it creates an entry according to the source MAC address and the source port of a packet. This entry is valid to all VLANs. b: When the bridge uses the independent VLAN learning (IVL) mode, it creates an entry according to the source MAC address, VLAN ID, and source port of a packet. This entry is valid to only this VLAN. For details about the 802.1ad bridge, see 22.2.4 Application of the QinQ Technology in LAN Services.
MAC Address Table

Entries of a MAC address table provide the mapping relations between MAC addresses and ports. The entries can be classified into the following categories:
l
Dynamic entry A dynamic entry is obtained by a bridge through the SVL/IVL mode. The dynamic entry ages, and is lost after the Ethernet switching board is reset.
Static entry A static entry, which corresponds to a specific MAC address and port, is manually added by the network administrator into the MAC address table on the NM. A static entry is also called a unicast entry. The static entry does not age, and is not lost after the Ethernet switching board is reset.
Blacklist entry A blacklist entry is used to discard the data frame that contains the specified destination MAC address, that is, the MAC disabled entry. A blacklist entry is also called a blackhole entry. The blackhole entry is configured by the network administrator. The blackhole entry does not age, and is not lost after the Ethernet switching board is reset.
Issue 02 (2009-02-25)
20-5
NOTE
If one routing entry is not updated in a certain period, that is, if no new packet from this MAC address is received to enable the re-learning of this MAC address, this routing entry is automatically deleted. This mechanism is called aging, and this period is called aging time. The aging time of a MAC address table is 5 minutes by default. You can set this value on the NM. The number of entries in a MAC address table is limited. The MAC address capacity of each bridge in the case of the Ethernet switching board is 16K.
Hub/Spoke
In the case of the convergence service, the mutual access between the non-central stations and central stations is required but the access between non-central stations is not required. In this case, specify a mounted port as a Hub port or a Spoke port.
l
Hub port Hub ports can mutually access each other. Hub ports and Spoke ports can mutually access each other.
Spoke port Spoke ports cannot mutually access each other. Hub ports and Spoke ports can mutually access each other.
A mounted port is a Hub port by default.
20.2.2 STP/RSTP
When the network topology of the Ethernet service forms loops, enable the STP or RSTP.
STP
The spanning tree protocol (STP) is used in the looped network. This protocol realizes the routing redundancy by adopting certain algorithms and releases the looped network into loop-free tree network, thus preventing the packets from increasing and cycling in an endless manner in the looped network. The STP meets the following requirements:
l
Configures any activated topology of any bridge to a single spanning tree, and releases the redundant data loop if there is any between two stations in the network topology. Re-configures the spanning tree topology in the case of a bridge fault or an interrupted route, thus providing a certain protection, and prevents temporary data loops by automatically containing the bridges and ports of the bridges that are newly added into the LAN. Stabilizes the activated topology in a rapid manner. The finally activated topology can be predicted and repeated. In addition, the topology can be selected by managing the parameters of certain algorithms. Operations to the end stations are transparent. For example, the end stations are unaware of their attachment to a single LAN or a bridged LAN. A small part of the available bandwidth of the link is used to create or maintain the spanning tree, and the bandwidth does not increase with the expanding network size.
l l
The Ethernet switching board supports the STP, which complies with IEEE 802.1d.
RSTP
The rapid spanning tree protocol (RSTP) is an optimized version of STP. Compared to the STP, the RSTP can stabilize the network topology in a shorter time. The RSTP is compatible with the STP. These two topologies can be identified by the bridge that uses the RSTP for calculating the spanning tree. The Ethernet switching board supports the RSTP, which complies with IEEE 802.1w.
20.2.3 IGMP Snooping

If the multicast router exists in the network, enable the IGMP Snooping for the bridge to realize the multicast function with the cooperation of the router.
Multicast Protocol
The multimedia network applications, such as video conference, E-learning, and video on demand (VOD) service, require that the information is transmitted from one source to multiple destinations, that is, transmitted in one-to-many transmission mode. Because the data traffic of the multimedia information is large, simulating the one-to-many transmission through one-toone mode occupies a large volume of bandwidth. In addition, information flooding is generated if the broadcast 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 the 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, with unlimited 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. The IP multicast protocol is classified into two categories: communication protocol among the multicast routers and the protocol among the multicast routers, hosts, and Layer 2 switches.
l
The communication protocol among multicast routers is used to obtain the multicast routing information. This type of protocol contains the protocol independent multicast-dense mode (PIM-DM), protocol independent multicast-sparse mode (PIM-SM), and distance vector multicast routing protocol (DVMRP). The protocol among the multicast routers, hosts, and Layer 2 switches is used to forward the multicast packet according to the multicast routing information. This type of protocol contains the Internet group management protocol (IGMP), IGMP Snoop, IGMP Proxy, and Cisco group management protocol (CGMP). IGMP is a Layer 3 multicast protocol, and IGMP Snooping, IGMP Proxy, and CGMP are Layer 2 multicast protocols.
IGMP
The IGMP contained in the TCP/IP suite is used to manage members of the IP multicast group. It 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 of accepting the information from this multicast group through this protocol. The router periodically queries whether a member of a specific group in the LAN is activated through this protocol (that is,
whether the member of a specific multicast group still exists in the network segment), and thus collects and maintains the member relations of groups that are connected to the router. By using this mechanism, the multicast router establishes 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. The router uses the IP multicast address to forward multicast packets. 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, the switch broadcasts the multicast packet at Layer 2 if the bridge disables the Layer 2 multicast protocol. See Figure 20-4. 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 relations between group members and switch ports and thus can forward the packet only to the ports that have group members. Figure 20-4 Transmission of the multicast packet (with IGMP Snooping 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
20-8
Issue 02 (2009-02-25)
Figure 20-5 Transmission of the multicast packet (with IGMP Snooping 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
The IGMP Snooping creates and maintains the mapping relations between group members and switch ports by sensing the IGMP packet. After the IGMP Snooping is enabled, the bridge considers the port that receives the IGMP request as the router port. When detecting the response that is transmitted to the router port, the bridge adds the port that receives the response and the router port into a specific multicast group. When detecting that a certain port in a multicast group does not respond to the IGMP request for consecutive times and that the times exceed the threshold, the bridge deletes this port from the multicast group. After the IGMP Snooping is enabled, when receiving the multicast packet, the bridge queries the multicast table in which the source port is the router port. 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. Three versions of IGMP requests are available, and they are, V1, V2, and V3. The Ethernet switching board can process versions V1 and V2. The Ethernet switching board also supports the aging of the router port and multicast table item.
NOTE
If a router port is not updated in a certain period (that is, no IGMP request from this port is received), all the multicast tables that are related to this router port are deleted. This mechanism is called aging, and this period is called aging time. The aging time of a router port is 5 minutes by default. You cannot set this value on the NM. Similarly, the multicast table item (that is, multicast group) ages. The aging time is 8 minute by default. You can set this value on the NM.
20.2.4 Broadcast Packet Suppression

You can enable the broadcast packet suppression function that is based on the Ethernet port to prevent spreading of the broadcast storm, through restricting the traffic of the broadcast packet that enters the Layer 2 switch. Based on the ratio of the number of broadcast packets to the total number of packets, the broadcast packet suppression function determines whether the system restricts the broadcast traffic. When
the ratio of the number of broadcast packets to the total number of packets exceeds the value set by the user, the system discards the broadcast traffic to decrease the ratio of the broadcast packets so that the ratio is in a reasonable range. In this manner, the broadcast storm can be prevented and the network congestion is avoided, which ensures the normal operation of the network. PORTs of the Ethernet switching board support the broadcast packet suppression function.
20.3 Availability
The Layer 2 switching feature requires the support of the applicable equipment and boards. Table 20-2 Availability of Layer 2 Switching Feature Bridge (802.1q bridge and 802.1d bridge) Bridge (802.1ad bridge) STP/RSTP IGMP Snooping Broadcast packet suppression EMS6 (all the versions) IDU 620 IDU 605 1F/2F Applicable Board EMS6 (all the versions) EMS6 (all the versions) Applicable Equipment IDU 620 IDU 605 1F/2F IDU 620

The Layer 2 switching has different relations with other features.
l l l l l
The port that is used by the bridge cannot be configured with the line service. The STP/RSTP is applicable only to the bridge. The IGMP Snooping is applicable only to the bridge. The broadcast packet suppression function is applicable only to the PORT on the bridge. The port on the bridge supports the QoS function.

The bridge, STP/RSTP, and IGMP Snooping comply with the relevant IEEE standards. 20.5.1 Bridge A bridge forwards a packet according to the entry of a MAC address table. 20.5.2 STP/RSTP The realization of the STP complies with IEEE 802.1d, and the realization of the RSTP complies with IEEE 802.1w. 20.5.3 IGMP Snooping
The IGMP Snooping establishes and creates the mapping relations between the group members and switch ports by sensing the IGMP packet. This ensures that the multicast packet is transmitted only to the ports that are connected to the multicast users.
20.5.1 Bridge
A bridge forwards a packet according to the entry of a MAC address table. A bridge forwards a packet as follows: 1. In the case of an 802.1q bridge, it checks the VLAN ID of a data frame that is received at the port. If the VLAN ID of this frame does not equal the VLAN ID of the port that is defined in the VLAN filter table, the bridge discards this frame. If the broadcast packet suppression function of the bridge port is enabled and the traffic of the broadcast packet exceeds the pre-set threshold value, the port discards the received broadcast frame. If the IGMP Snooping protocol of the bridge is enabled, the bridge processes the IGMP packet and multicast packet that are received at the port, according to the principle described in 20.5.3 IGMP Snooping. If the bridge receives the multicast packet but the IGMP Snooping protocol is disabled, it forwards the multicast packet among all the ports of the bridge or among all the mounted ports of the VLAN (excluding the source port). According to the learning mode, the bridge adds or updates the entry corresponding to the source MAC address of the data frame in the MAC address table, and thus establishes the mapping relation between the MAC address and the receive port. The bridge checks the MAC address table according to the destination MAC address of the data frame.
l
2.
3.
4.
5.
6.
If the blacklist entry corresponding to the destination MAC address exists, the bridge discards this data frame. If the dynamic entry or the static entry corresponding to the destination MAC address exists, the bridge forwards this data frame to the destination port indicated by the entry. If no corresponding entry exists, the bridge forwards the packet among all the ports of the bridge or among all the mounted ports of the VLAN (excluding the source port), according to the bridge type (802.1d bridge or 802.1q bridge).
7.
The bridge needs to determine whether the source port and the destination port are Hub or Spoke when forwarding the data frame. If the source port is the Hub port, the bridge forwards the packet to the Hub port and the Spoke port. If the source port is the Spoke port, the bridge forwards the packet to the Hub port.
NOTE
If the STP or the RSTP of the bridge is enabled, only the port in the forwarding state can forward the data frame.
20.5.2 STP/RSTP
The realization of the STP complies with IEEE 802.1d, and the realization of the RSTP complies with IEEE 802.1w.
Basic Concepts
l
Bridge protocol data unit (BPDU)

Issue 02 (2009-02-25)
The STP transmits the BPDU among pieces of equipment to determine the network topology. The BPDU contains adequate information that is required to implement the calculation of the spanning tree. The BPDU is classified into the following categories:
Configuration BPDU (CBPDU) The CBPDU refers to a packet that is used to calculate the spanning tree and maintain the spanning tree topology. The CBPDU contains the root bridge ID, root path cost, designated bridge ID, designated port ID, and related timing information.
Topology change Notification BPDU (TCN BPDU) The TCN BPDU refers to a packet that is used to notify the relevant equipment of the network topology change in the case of topology change.
Bridge ID The bridge ID is used to indicate a bridge. The bridge ID is 64-bit long. The most significant 16 bits indicate the priority of the bridge, and the least significant 48 bits indicate the MAC address of a certain bridge port. In the STP, the bridge ID also indicates the priority of the bridge. The smaller the value of the bridge ID, the higher the priority.
Port ID The port ID is used to indicate a port on the bridge. The port ID is 16-bit long. The most significant eight bits indicate the priority of the port, and the least significant eight bits indicate the port number. In the STP, the port ID also indicates the priority of the port. The smaller the value of the port ID, the higher the priority.
Root bridge In a network that enables the STP, only one root bridge exists. The root bridge is selected based on the running of the STP. The bridge with the smallest bridge ID is selected as the root bridge. When a network that enables the STP is stabilized, only the root bridge generates and transmits the CBPDU periodically. Other bridges only relay the CBPDU. This can ensure a stable network topology. If the network topology is changed, the root bridge may also change.
Root port The root port refers to a port on the bridge that transmits/receives frames to/from the root bridge. Each non-root bridge has only one root port. The root port is selected based on the running of the STP. The port of a bridge whose root path cost is the smallest is selected as the root port. If more than one port whose root path cost is the smallest exist, the port with the smallest port ID is selected as the root port.
Designated port The designated port refers to a port of a LAN that transmits/receives frames to/from the root bridge. Each LAN has only one designated port. The designated port is selected based on the running of the STP. The port that is connected to the LAN and whose root path cost is the smallest is selected as the designated port. If more than one port whose root path cost is the smallest exist and if these ports are on different bridges, the port whose bridge ID is the smallest is selected as the designated port. If more than one port whose root path cost is the smallest exist and if these ports are on the same bridge, the port with the smallest port ID is selected as the designated port.
Path cost The path cost is used to indicate the status of the network that is connected to the port. The higher the rate of the port, the smaller the path cost.
Root path cost

20-12
The root path cost refers to the cost of the path from a certain port to the root bridge. That is, the sum of path cost of all the passed ports from this port to the root bridge.
l
Port state In a network that enables the STP, the port state can be 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 blocking state, it does not learn the MAC address and does not forward the user packet.
Listening It is a transitional state. A port in the listening state transmits, receives, and processes the BPDU. When a port is in the listening state, it neither learns the MAC address nor forwards the user packet.
Learning It is a transitional state. A port in the learning state transmits, receives, and processes the BPDU. When a port is in the learning state, it learns the MAC address but does not forward the user packet.
Forwarding A port in the forwarding state transmits, receives, and processes the BPDU. When a port is in the learning state, it learns the MAC address and forwards the user packet.
Disabled A port in the disabled state does not forward frames, and does not implement the spanning tree algorithm and STP.
Timer Port timers are classified into the following categories:
Hold timer The hold timer is used to measure the interval between two CBPDU transmissions. The timeout value is the Hold Time of the bridge.
Message age timer The message age timer is used to measure the age of the CBPDU packet recorded by a port. When the age of the CBPDU packet stored by the bridge exceeds the Message Age parameter, the bridge discards the packet. The Message Age parameter determines the initialization age when the CBPDU packet is stored in the bridge. The Message Age parameter is 0 when the root bridge generates the packet. Each time the packet is forwarded to a port, a fixed increment value is added to the Message Age parameter.
Forward delay timer The forward delay timer is used to measure the holding time of a port in the listening state and in the learning state. When the listening state remains for a period that is the same as the value of the Forward Delay parameter, the port state is changed to learning. When the learning state remains for a period that is the same as the value of the Forward Delay parameter, the port state is changed to forwarding.
Bridge timers are classified into the following categories:
Hello timer The hello timer is used to measure the interval when the bridge transmits the CBPDU packet. The timeout value is the Bridge Hello Time of the bridge.
Topology change notification timer

Issue 02 (2009-02-25)
The topology change notification timer indicates the duration when the bridge periodically transmits the TCN. The timer is used to notify the designated bridge in the LAN that is attached to the root port of the bridge of any detected topology change. The timeout value is the Bridge Hello Time of the bridge.
Topology change timer In the case of the root bridge, when receiving the TCN, the bridge transmits the TCN after the topology change is complete and the time period indicated by the topology change timer times out. The timeout value is the Topology Change Time of the bridge.
NOTE
The Max Age, Hello Time, and Forward Delay parameters that are used by different bridges are unified to the values of these three parameters that are used by the root bridge, by mutually transmitting the CBPDU.
STP Algorithm
The STP algorithm is conducted 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 of the CBPDU is 0. Each port transmits the CBPDU periodically, and the period is the Hello Time of the bridge. The bridge compares the information about the CBPDU that is received at the port with the CBPDU information that is stored by that port. The bridge compares the information that is carried by the CBPDU as follows: (1) The bridge first compares the root bridge IDs. The smaller the ID, the better. (2) If the root bridge IDs are the same, the bridge compares the root path cost values. The smaller the root path cost, the better. (3) If the root path cost values are the same, the bridge compares the designated bridge IDs. The smaller the designated bridge ID, the better. (4) If the designated bridge IDs are the same, the bridge compares the designated port IDs. The smaller the designated port ID, the better. 3. If the information about the CBPDU that is received at the port is better, the bridge replaces the information about the CBPDU that is originally stored by the port. If the root bridge ID or the root path cost in the information about the CBPDU that replaces the information about the CBPDU originally stored by the port is smaller than the information originally stored by the port, the bridge needs to process this new CBPDU as follows:
l
2.
The bridge stores the information about 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 equals the sum of the root path cost of the port that stores the packet 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 equals the sum of the root path cost of the bridge and the path cost of the port). The designated port relays the CBPDU.
If the information about the CBPDU that is received at the port is worse than the information about the CBPDU that is stored by the port, the port transmits the CBPDU that is stored as a response.
4. 5. 6.
If the bridge maintains a root bridge ID that is the same as its bridge ID and if the root path cost is 0, the bridge is a root bridge. The root bridge sets the path cost of each port to 0. If the bridge is a non-root bridge, it considers the port that receives the best CBPDU information as the root port. If the 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 the port are the same as the designated bridge ID and port ID recorded by the port. The root bridge ID recorded by the port is different from the root bridge ID of the bridge. The root path cost of the port (sum of the root path cost of the bridge and the path cost of the port) is smaller than the root path cost recorded by the port. The root path cost of the port is the same as the root path cost recorded by the port, but the bridge ID is smaller than the designated bridge ID of the port. The root path cost of the port is the same as the root path cost 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.
l l
7.
When the Forward Delay parameter set for the listening state timer of the port expires, the states of the root port and the designated port transition to learning. When the learning state remains for a period that is the same as the value of the Forward Delay parameter, the states of the root port and the designated port transition to forwarding. The states of these ports whose states are not changed to forwarding transition to blocking. If a trail becomes faulty, the root port on this trail no longer receives new CBPDUs, and therefore, the original CBPDU is discarded due to timeout. In this case, the calculation of the spanning tree is conducted again, and a new trail will be available 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 classified into the following categories: root port, designated port, alternate port, and backup port. The alternate port refers to a port that is in the blocking state due to the learning of the BPDU transmitted by other bridges. The backup port refers to a port that is in the blocking state due to the learning of the BPDU transmitted by the bridge the port resides in.
Classification of port states The blocking, listening, and disabled states are combined into the discarding state in the RSTP.
Rapid transition of port states To support the rapid transition of port states, the RSTP defines the point-to-point attribute of a port and an edge port.
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 actual working mode of the port is full-duplex, the actual pointto-point attribute of the port is "true". If the actual working mode of the port is half-
Issue 02 (2009-02-25)
20-15
duplex, 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 port whose point-to-point attribute is "true" can transmit the rapid transition request and response.
Edge port The edge port refers to the bridge port that is connected only to the LAN. If a port is set to an edge port and if this port can receive the BPDU, the port is actually an edge port. If the port role of this edge port is a designated port, the port can realize the rapid state transition.
The rapid transition among port states can be classified into the rapid port state transition of the root port, rapid port state transition of the designated port, and the rapid port state transition of the alternate port and backup port.
Rapid port state transition of the root port A root port that does not function as a backup port recently (that is, in a recent period that is less than double times of the Hello Time) transition to the forwarding state without any delay, and this root port enables the designated port that functions as the root port recently (that is, in a recent period that is less than Forward Delay) to transition to the discarding state.
Rapid port state transition of the designated port If an edge port is also a designated port, the port state transitions to the forwarding state without any delay. The designated port whose actual point-to-point attribute is "true" can realize the rapid transition among port states through rapid switching between the request process and response process.
Rapid port state transition of the alternate port and the backup port The port state of the alternate port and the backup port transitions to the disabled state without any delay.
20.5.3 IGMP Snooping

The IGMP Snooping establishes and creates the mapping relations between the group members and switch ports by sensing the IGMP packet. This ensures that the multicast packet is transmitted only to the ports that are connected to the multicast users.
Basic Concepts
l
Router port The router port refers to a port that connects to a multicast router. Multicast member port The multicast member port refers to a port that connects to a multicast group member. The multicast group member refers to a host that joins a multicast group.
Multicast group The multicast group records the mapping relations among the router ports, MAC multicast addresses, and multicast group members. A multicast group is also called a multicast table item.
Maximum query response time When transmitting the IGMP specific query packet to the multicast member port, the 802.1q bridge starts the maximum query response timer. If the bridge does not receive the IGMP response packet within the maximum query response time, the bridge adds one to the no-
20-16
Issue 02 (2009-02-25)
response times of the port. When the no-response times of the port exceeds the pre-set threshold, the bridge deletes the multicast member from the multicast group.
l
IGMP general query packet The IGMP general query packet refers to a packet that is transmitted by a multicast router to the multicast group members. The IGMP general query packet is used to query which multicast groups have members.
IGMP specific query packet The IGMP specific query packet refers to a packet that is transmitted by a 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 a multicast router. The IGMP report packet is used to apply for the joining of a multicast group or to respond to the IGMP query packet.
Processing Flow
The 802.1q bridge processes the IGMP Snooping as follows: 1. If receiving the IGMP general query packet or the IGMP specific query packet, the bridge 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 already learnt, the bridge re-sets the aging time of the router port. If this port is not learnt, the bridge records the port as the router port and starts the aging timer of the port. (3) If the received packet is the IGMP specific query packet and the port that receives this packet is already recorded as the router port, the bridge broadcasts this packet in the specific multicast group and starts the timer for the maximum query response time if the multicast group that is specified in this packet exists. Otherwise, the bridge broadcasts this packet in the VLAN domain of the 802.1q bridge. 2. If receiving the IGMP report packet, the bridge 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 establishes the mapping relations among the router ports, MAC multicast addresses, and multicast group members by considering this port as the multicast member port. If this multicast record is not learnt and this port is not contained in the multicast member ports of the multicast group, the multicast group adds this port as the multicast member port. If this multicast record is learnt, the bridge re-sets the counting of no-response times for this multicast member. 3. If receiving the multicast packet, the bridge processes this packet as follows:
l l
The bridge queries the multicast table that uses the router port as the source port. 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 in the VLAN range depending on the NM setting.
Issue 02 (2009-02-25)
4.
The bridge processes the aging as follows.

l
If the maximum query response time times out, the bridge adds one to the no-response times of the multicast member. If the no-response times of a multicast member exceeds the threshold, the bridge deletes this multicast member port. If a multicast group does not have any multicast member port, the bridge deletes this multicast group.
The 802.1d bridge processes the IGMP Snooping similarly. The difference is as follows: The 802.1d learns the packet by using the SVL mode other than by using the IVL mode, and the 802.1d bridge broadcasts the packet without the restriction of the VLAN domain.
Version
Three versions of IGMP requests are available, and they are, V1, V2, and V3. The Ethernet switching board can process versions V1 and V2. V2 is compatible with V1. Compared with V1, V2 is improved as follows:
l
Supports the multicast group leave packet. This packet can efficiently decrease the delay generated in the process of deleting the multicast group.
Supports the specific query packet. This packet allows broadcasting the IGMP query packet in the specific multicast group.
20.6 Planning Guide

Plan the relevant parameters of the Layer 2 switching service according to the actual situation of microwave links.
Prerequisite
You must learn the situation of the microwave links.
Procedure
Step 1 Plan the bridge. Adhere to the following principles when planning the bridge:
l
Using the 802.1q bridge is a priority. If the conditions of the VLAN that is used by the user are not known and if the user does not require the isolation of the data among VLANs, you can also use the 802.1d bridge. If the Layer 2 switching services from several branch nodes are converged at a convergence node, set this convergence node to Hub and set these branch nodes to Spoke. In the case of the multipoint-to-multipoint Layer 2 switching service, set each node to Hub.
Step 2 Plan the MAC address table. Adhere to the following principles when planning the MAC address table:

l
If the node that only receives data frames exists in the network, configure the corresponding VLAN unicast entry. If certain nodes are not allowed to transmit data frames, configure the corresponding MAC disabled entries for the bridge that accesses these nodes. Set the aging time of the MAC address table to the same value as the aging time of the interconnected Ethernet equipment. It is recommended that you set the aging time of the MAC address table to 5 minutes (default value).
Step 3 Plan the STP/RSTP. Adhere to the following principles when planning the STP/RSTP:
l
In the service networking process, it is recommended that you prevent the loop from forming in the case of the Layer 2 service and thus avoid enabling the STP or RSTP. If the loop is already formed in the service networking, you must enable the STP or RSTP. The protocol type should be set according to the requirement of the interconnected Ethernet equipment. It is recommended that you use the RSTP. The bridge priority, port priority, and port path cost should be set according to the requirement of the interconnected Ethernet equipment. Use the default values, unless otherwise specified. The Max Age, Hello Time, and Forward Delay parameters should be set to the same values as these parameters of the interconnected Ethernet equipment. Use the default values, unless otherwise specified.
Step 4 Plan the IGMP Snooping protocol. Adhere to the following principles when planning the IGMP Snooping protocol:
l
If the IGMP multicast router exists in the interconnected Ethernet network, enable the IGMP Snooping protocol according to the requirement of the router. Otherwise, do not enable the IGMP Snooping protocol. Set the processing method for the unknown multicast packet and multicast aging time according to the requirement of the IGMP multicast router. It is recommended that you use the default values.
----End

This topic describes the configuration tasks relevant to the Layer 2 switching feature. 20.7.1 Creating the Ethernet LAN Service To enable the Ethernet switching board to transmit the LAN service, perform certain operations to create the bridge and set the attributes of the bridge and to configure the mounted ports of the bridge. 20.7.2 Modifying the Mounted Port of a Bridge This operation enables the user to modify the mounted port of a bridge, the enabled state of the mounted port, and Hub/Spoke attribute of the port. 20.7.3 Creating the VLAN Filter Table You need to create the VLAN filter table for the bridge when you create the EVPLAN service. 20.7.4 Creating the Entry of a MAC Address Table Manually The bridge can obtain the dynamic entry of a MAC address table by using the SVL or IVL mode. In addition, you can manually add the entry of a MAC address table. The manually created
entries of a MAC address table can be classified into two categories: unicast entry (that is, static entry) and disabled entry (that is, blacklist entry). 20.7.5 Modifying the Aging Time of the MAC Address Table Entry In the case of the Ethernet switching board, the aging time of a MAC address table entry is 5 minutes by default. 20.7.6 Configuring the Spanning Tree Protocol In the case of the Layer 2 service, if the loop is formed, enable the STP or RSTP for the bridge and set bridge parameters and port parameters. 20.7.7 Configuring the IGMP Snooping Protocol If the bridge accesses a LAN where the IGMP multicast server exists, you can enable the IGMP Snooping protocol and configure the method for processing the unknown multicast packet. 20.7.8 Modifying the Aging Time of the Multicast Table Item In the case of the Ethernet switching board, the aging time of a multicast table item is 8 minutes by default. 20.7.9 Configuring the Broadcast Packet Suppression Function When the broadcast packet suppression function is enabled, the port discards the newly received broadcast packets when the bandwidth used by the received broadcast packets exceeds the preset broadcast packet suppression threshold of the port.
20.7.1 Creating the Ethernet LAN Service

To enable the Ethernet switching board to transmit the LAN service, perform certain operations to create the bridge and set the attributes of the bridge and to configure the mounted ports of the bridge.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout.
Precautions
l l l
The IDU 620 supports the Ethernet switching board EMS6. The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board). The following procedures consider the operation of the Web LCT as an example.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Click New. The Create Ethernet LAN Service dialog box is displayed. Step 3 Set the attributes of the bridge according to the bridge type.
l
Set the attributes of the 802.1q bridge.

20-20
Set the attributes of the 802.1d bridge.
Step 4 Configure the mounted ports of the bridge. 1. 2. Click Configure Mounted Port. The VB Mount Port Configuration dialog box is displayed. Select a port from the ports listed in Available Mounted Ports, and then click . 3. Optional: Repeat Step 4.2 to select other mounted ports.
Issue 02 (2009-02-25)
20-21
4.
Click OK.
Step 5 Optional: If any VCTRUNK is mounted to the VB, configure the VC paths that are bound to the VCTRUNK. 1. 2. 3. 4. Click Configuration. The Bound Path Configuration dialog box is displayed. In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select required items in Available Resources and Available Timeslots and click . 5. Optional: Repeat Step 5.4 to bind other VC paths.
20-22
Issue 02 (2009-02-25)
NOTE
6.
Click OK.
Parameters
Parameter VB Name Value Range Default Value Description This parameter is a string that describes the bridge. It is recommended that you set this string to a value that contains the specific purpose of the bridge.
Issue 02 (2009-02-25)
20-23
Parameter VB Type
Value Range 802.1q, 802.1d, 802.1ad (EMS6) 802.1q, 802.1d (a logical board EMS4)
Default Value 802.1q
Description
l
When setting this parameter to 802.1q, create the 802.1q bridge. When setting this parameter to 802.1d, create the 802.1d bridge. Using the 802.1q bridge is a priority. If the conditions of the VLAN that is used by the user are not known and if the user does not require the isolation of the data among VLANs, you can also use the 802.1d bridge. This task describes only how to create the 802.1d bridge and how to create the 802.1q bridge. When the bridge uses the SVL mode, all the VLANs share one MAC address table. When the bridge uses the IVL mode, all the VLANs correspond to their respective MAC address tables. If the ingress filter is enabled, the VLAN tag is checked at the ingress port. If the VLAN ID does not equal the VLAN ID of the port defined in the VLAN filtering table, the packet is discarded. If the ingress filter is disabled, the preceding described check is not conducted. Only the port that is selected as the mounted port of a bridge functions in the packet forwarding process of the bridge. Set this parameter according to actual situations.
Bridge Switch Mode
IVL/Ingress Filter Enable (802.1q), SVL/Ingress Filter Disable (802.1d)
IVL/Ingress Filter Enable (802.1q), SVL/Ingress Filter Disable (802.1d)
Mount Port
Configurable Ports
Mount each VCTRUNK of the port.
20-24
Issue 02 (2009-02-25)
Value Range -
Default Value -
l
The capacity of VCTRUNKs should be determined by the actual bandwidth of the service needs. Bind only the paths in a VC-4 if possible. If the paths of several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Hence, when a VCTRUNK needs to be bound with VC-3 paths, select VC-3 paths first from the VC-4 certain of whose VC-3 paths are already bound; when a VCTRUNK needs to be bound with VC-12 paths, select VC-12 paths first from the VC-4 certain of whose VC-12 paths are already bound. As the VC-4-1s of the EFT4 board and EMS6 board support only VC-3 paths whereas the VC-4-2s support both VC-12 paths and VC-3 paths, give priority to the paths in the VC-4-1 if a VCTRUNK needs to be bound with VC-3 paths. Generally, bidirectional paths are bound.
20.7.2 Modifying the Mounted Port of a Bridge

This operation enables the user to modify the mounted port of a bridge, the enabled state of the mounted port, and Hub/Spoke attribute of the port.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The Ethernet LAN service must be created.
Precautions
The IDU 620 supports the Ethernet switching board EMS6. The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board). The following procedures consider the operation of the Web LCT as an example.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select the bridge that is already created, and click the Service Mount tab. Step 3 Modify the mounted port of this bridge and the related attributes of the mounted port.
To change the port that is connected to the 802.1q bridge, click the corresponding Mount Port. After selecting the corresponding option from the drop-down list, click Apply. To change the port that is connected to the 802.1ad bridge, click Configure Mount. After changing the settings in the dialog box that is displayed, click OK. ----End
Parameters
Parameter VB Port Mount Port Value Range 1 to 14 Unconnected, a specific PORT, a specific VCTRUNK, IFUP1 Default Value Description This parameter specifies the ID of the logical port of the bridge.
l
Only the port that is selected as the mounted port of a bridge functions in the packet forwarding process of the bridge. Set this parameter according to actual situations.
Port Enabled Hub/Spoke
Enabled, Disabled Hub, Spoke
Enabled Hub
Set Port Enabled to Enabled. Otherwise, the port cannot forward the service.
l
The Spoke ports cannot access each other. The Hub port and the Spoke port can access each other. The Hub ports can access each other. Set this parameter according to actual situations.
20-26
Issue 02 (2009-02-25)
Parameter TAG
Value Range Access, Tag Aware, Hybrid
Default Value Tag Aware
Description
l
When ports are configured with TAG flags, the ports process frames by using the methods provided in Table 18-4. 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 that do not have the VLAN tag (untagged frames), set this parameter to Access. When the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid. The Ethernet ports of different types support different working modes. When the equipment on the opposite side works in the auto-negotiation mode, set the working mode of the equipment on the local side to Auto-Negotiation. When the equipment on the opposite side works in the full-duplex mode, set the working mode of the equipment on the local side to 10M Full-Duplex, 100M Full-Duplex, or 1000M Full-Duplex depending on the port rate of the equipment on the opposite side. When the equipment on the opposite side works in the half-duplex mode, set the working mode of the equipment on the local side to 10M Half-Duplex, 100M Half-Duplex, or Auto-Negotiation depending on the port rate of the equipment on the opposite side.
Working Mode
10M Half-Duplex, 10M Full-Duplex, 100M Half-Duplex, 100M Full-Duplex, Auto-Negotiation (a logical board EMS4, PORT1 PORT3) 10M Half-Duplex, 10M Full-Duplex, 100M Half-Duplex, 100M Full-Duplex, 1000M FullDuplex, AutoNegotiation (a logical board EMS4, PORT4) 10M Half-Duplex, 10M Full-Duplex, 100M Half-Duplex, 100M Full-Duplex, 1000M FullDuplex, AutoNegotiation (EMS6)
Auto-Negotiation
20.7.3 Creating the VLAN Filter Table

You need to create the VLAN filter table for the bridge when you create the EVPLAN service.
Prerequisite
The EVPLAN service must be created.
Precautions
The IDU 620 supports the Ethernet switching board EMS6. The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select the bridge that is already created, and click the VLAN Filtering tab. Step 3 Create the VLAN filter table. 1. 2. 3. Click New. The Create VLAN dialog box is displayed. Set VLAN ID (e.g:1,3-6). Select a port from the ports listed in Available forwarding ports, and then click . 4. Optional: Repeat Step 3.3 to select other forwarding ports.
5.
Click OK.
----End
Parameters
Parameter VLAN ID (e.g: 1,3-6) Value Range 14095 Default Value Description
l
You can set this parameter to a number or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "" to indicate continuous numbers. For example, "1, 36" indicates numbers 1, 3, 4, 5, and 6. Set this parameter according to actual situations. The packets can be forwarded between the selected forwarding ports only. The ports that are in selected forwarding ports can forward only the packet that carries the VLAN ID (e.g:1,3-6) tag. These ports discard the packet that carries other VLAN tags. The broadcast packet that is transmitted by the ports in selected forwarding ports is broadcast only to the ports included in selected forwarding ports.
Selected forwarding ports
This parameter indicates the ports that are mounted to a bridge.
20.7.4 Creating the Entry of a MAC Address Table Manually

The bridge can obtain the dynamic entry of a MAC address table by using the SVL or IVL mode. In addition, you can manually add the entry of a MAC address table. The manually created entries of a MAC address table can be classified into two categories: unicast entry (that is, static entry) and disabled entry (that is, blacklist entry).
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The Ethernet LAN service must be created. The VLAN filter table must be created.
Precautions
Issue 02 (2009-02-25)
20-29
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Optional: Create the unicast entry manually. 1. 2. 3. Select the bridge that is already created, and click the VLAN Unicast tab. Click New. The Create VLAN Unicast dialog box is displayed. Set the parameters of the unicast entry.
4. 1. 2. 3.
Click OK. Select the bridge that is already created, and click the Disable MAC Address tab. Click New. The Disable MAC Address Creation dialog box is displayed. Set the parameters of the disabled entry.
Step 3 Optional: Create the disabled entry manually.
4.
Click OK.
----End
20-30
Issue 02 (2009-02-25)
Parameters
Parameter VLAN ID Value Range 14095 Default Value Description
l
In the case of the 802.1d bridge and the 802.1ad bridge, this parameter is invalid if the SVL mode is used. The set entry applies to all the VLANs. In the case of the 802.1q bridge and the 802.1ad bridge, the set entry applies only to the VLAN whose ID is equal to the set value of this parameter if the IVL mode is used. Set this parameter according to actual situations.
MAC Address Physical Port
Each port that is mounted to a bridge
Set this parameter according to actual situations. This parameter indicates the Ethernet port corresponding to a MAC address. Set this parameter according to actual situations.
20.7.5 Modifying the Aging Time of the MAC Address Table Entry
In the case of the Ethernet switching board, the aging time of a MAC address table entry is 5 minutes by default.
Prerequisite
Precautions
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2 Switching Management > Aging Time from the Function Tree. Step 2 Modify the aging time of the MAC address table entry. 1. 2.
Issue 02 (2009-02-25)
Double-click MAC Address Aging Time corresponding to this Ethernet switching board. The MAC Address Aging Time dialog box is displayed. Set the duration and unit of the aging time.
3.
Click OK.
Parameters
Parameter MAC Address Aging Time Value Range 1 Min to 120 Day Default Value 5 Min Description
l
If one entry is not updated in a certain period, that is, if no new packet from this MAC address is received to enable the relearning of this MAC address, 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 MAC address table entries that are outdated, which exhausts the resources of the MAC address forwarding table. If this parameter is set to a very small value, the bridge may delete the MAC address table entry that is needed, which reduces the forwarding efficiency. It is recommended that you use the default value.
20.7.6 Configuring the Spanning Tree Protocol

In the case of the Layer 2 service, if the loop is formed, enable the STP or RSTP for the bridge and set bridge parameters and port parameters.
Prerequisite
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Step 2 Optional: Set the enabled status of the protocol. 1. 2. Click the Protocol Enable tab. Configure parameters of the enabled protocol.
3. 1. 2.
Click Apply. Click the Bridge Parameter tab. Set bridge parameters.
Step 3 Optional: Set bridge parameters.
3. 1. 2.
Click Apply. Click the Port Parameter tab. Set port parameters.
Step 4 Optional: Set port parameters.
3. 1. 2.
Click Apply. Click the Point to Point Attribute tab. Set the point-to-point attribute.
Step 5 Optional: If you are enabling the RSTP, set the point-to-point attribute of the Ethernet port.
3.
Click Apply.
----End
Issue 02 (2009-02-25)
20-33
Parameters
Parameter Protocol Enabled Value Range Enabled, Disabled Default Value Disabled Description
l
This parameter determines whether to enable the spanning tree protocol. It is recommended that you do not enable the STP or RSTP in the service networking process, because this can prevent the Layer 2 service from forming the loop. If the loop is already formed in the service networking, you must start the STP or RSTP. This parameter is valid only when Protocol Enabled is set to Enabled. The protocol type should be set according to the requirement of the interconnected Ethernet equipment. Generally, it is recommended that you use the default value. The most significant 16 bits of the bridge ID indicates the priority of the bridge. The smaller the value of this parameter, the higher the priority and the higher the possibility that the bridge is 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. This parameter indicates the interval of transmitting the CBPDU packet of 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 Type
STP, RSTP
RSTP
Priority (Bridge Parameter)
061440
32768
Hello Time (s)
110
20-34
Issue 02 (2009-02-25)
Parameter Max Age (s)
Value Range 640
Default Value 20
Description
l
This parameter indicates 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 indicates the holding time of a port in the listening state and in the learning state. The greater the value, the longer the delay time of the network state change. Hence, the topology changes are slower and the recovery in the case of faults is slower.
Forward Delay (s)
430
15
TxHoldCout (Times/s) Admin Edge Attribute
110
This parameter indicates the number of times the port transmits the CBPDU in every second.
l
Enabled, Disabled
Disabled
This parameter is valid only when the RSTP is used. This parameter determines whether to set the port to an edge port. The edge port refers to the bridge port that is connected only to the LAN. The edge port receives the BPDU and does not transmit the BPDU. This parameter is set to Enabled only when the Ethernet port of the Ethernet board is directly connected to the data communication terminal equipment, such as a computer. In other cases, it is recommended that you use the default value.
Issue 02 (2009-02-25)
20-35
Parameter Auto Edge Detection
Description
l
This parameter is valid only when Admin Edge Attribute is set to Enabled. When this parameter is set to Enabled, if the bridge detects that this port is connected to the port of other bridges, the RSTP considers this port as a non-edge port. If Admin Edge Attribute is set to Enabled, set this parameter to Enabled. In other cases, it is recommended that you use the default value. This parameter determines whether the STP or RSTP of the port is enabled. When this parameter is set to Disabled, the port does not process and transmit the BPDU. It is recommended that you use the default value. 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 eight bits of the port ID indicate the port priority. The smaller the value of this parameter, the higher the priority.
Protocol Enabled
Enabled, Disabled
Enabled
Port Path Cost
165535
Priority (Port Parameter)
0240
128
20-36
Issue 02 (2009-02-25)
Parameter Point-to-Point Attribute
Value Range Adaptive connection, Link connection, Shared media
Default Value Adaptive connection
Description
l
This parameter is valid only when the RSTP is used. If this parameter 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 actual working mode of the port is full-duplex, the actual point-topoint attribute of the port is "true". If the actual working mode of the port is halfduplex, the actual point-to-point attribute of the port is "false". If this parameter is set to Link connection, the actual point-to-point attribute of the port is "true". If this parameter is set to Shared media, the actual point-to-point attribute of the port is "false". Only the port whose point-to-point attribute is "true" can transmit the rapid transition request and response. It is recommended that you use the default value.
NOTE
l l
In the service networking process, it is recommended that you prevent the loop from forming in the case of the Layer 2 service and thus avoid enabling the STP or RSTP. Because the RSTP and STP are complicated, it is recommended that you negotiate with the engineer in charge of maintaining the opposite Ethernet equipment and set the related parameters as instructed, before enabling the STP or RSTP.
20.7.7 Configuring the IGMP Snooping Protocol

If the bridge accesses a LAN where the IGMP multicast server exists, you can enable the IGMP Snooping protocol and configure the method for processing the unknown multicast packet.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The Ethernet LAN service must be created. The VLAN filter table must be created.
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Step 2 Click the Protocol Enable tab. Step 3 Set the information related to the IGMP Snooping protocol.
Parameters
Parameter Protocol Enable Value Range Enabled, Disabled Default Value Disabled Description
l
This parameter determines 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. This parameter is valid only when Protocol Enabled is set to Enabled. If the 802.1q bridge or the 802.1ad bridge receives a multicast packet whose multicast address has no mapping item in the multicast table (that is, this multicast packet is an unknown multicast packet), this parameter indicates the method for processing this packet. When this parameter is set to Yes, The unknown multicast packet is discarded. When this parameter is set to No, the unknown multicast packet is broadcast in the VLAN. Set this parameter according to the requirement of the IGMP multicast server.
Discard the Packet
Yes, No
Yes
20.7.8 Modifying the Aging Time of the Multicast Table Item

In the case of the Ethernet switching board, the aging time of a multicast table item is 8 minutes by default.
20-38
Issue 02 (2009-02-25)
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The Ethernet LAN service must be created. The IGMP Snooping protocol of the bridge must be enabled.
Precautions
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Step 2 Click the Aging Time tab. Step 3 Modify the aging time of the multicast table item.
Issue 02 (2009-02-25)
20-39
Parameters
Parameter Multicast Aging Time (Min) Value Range 1120 Default Value 8 Description
l
When a table item is not updated in a certain period (that is, no IGMP request from this multicast address is received), this table item is automatically deleted. This mechanism is called aging, and this period is called aging time. If this parameter is set to a very large value, the bridge stores excessive multicast table items that are outdated, which exhausts the resources of the multicast table. If this parameter is set to a very small value, the bridge may delete the multicast table item that is needed, which reduces the forwarding efficiency.
20.7.9 Configuring the Broadcast Packet Suppression Function

When the broadcast packet suppression function is enabled, the port discards the newly received broadcast packets when the bandwidth used by the received broadcast packets exceeds the preset broadcast packet suppression threshold of the port.
Prerequisite
Precautions
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Then, select External Port. Step 2 Click the Advanced Attributes tab. Step 3 Set Enabling Broadcast Packet Suppression and Broadcast Packet Suppression Threshold.
Parameters
Parameter Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold Value Range Disabled Enabled 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 30% Default Value Disabled Description This parameter specifies whether to enable the broadcast packet suppression function. When the broadcast packet suppression function is enabled, the port discards the newly received broadcast packets when the bandwidth used by the received broadcast packets exceeds the preset broadcast packet suppression threshold of the port.

This topic describes the maintenance operations, alarms and performance events that are related to the Layer 2 switching, and the problems that occur frequently during the application of the Layer 2 switching. 20.8.1 Querying the Actual Capacity of the MAC Address Table and the Dynamic Entry By querying the actual capacity of the MAC address table and the dynamic entry, you can learn about the MAC address learning situation of the bridge. 20.8.2 Querying the Running Information About the Spanning Tree Protocol The running information about the spanning tree protocol includes the bridge running information and port running information. 20.8.3 Querying the Running Information About the IGMP Snooping Protocol The running information about the IGMP Snooping protocol includes the current multicast router port and multicast table item. 20.8.4 Relevant Alarms and Events The Layer 2 switching feature may cause changes in RMON performance. 20.8.5 FAQs This topic lists the problems that occur frequently during the application of the Layer 2 switching feature.
20.8.1 Querying the Actual Capacity of the MAC Address Table and the Dynamic Entry
By querying the actual capacity of the MAC address table and the dynamic entry, you can learn about the MAC address learning situation of the bridge.
Prerequisite
Precautions
The IDU 620 supports the Ethernet switching board EMS6, which supports the querying of the VLAN MAC address table capacity and the self-learning MAC address. The IDU 605 IF/2F supports the Ethernet switching board EMS4 (a logical board), which supports the querying of the self-learning MAC address only.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Query the actual capacity of the MAC address table. 1. 2. 3. Select the bridge that is already created, and click the VLAN MAC Address Table Capacity tab. Click Query. View the actual capacity of the MAC address table.
Step 3 Query the actual capacity of the MAC address table. 1. 2. Select the bridge that is already created, and click the Self-learning MAC Address tab. Optional: Click First page, Previous, or Next to view the dynamic entries of the MAC address table by page.
----End
20.8.2 Querying the Running Information About the Spanning Tree Protocol
The running information about the spanning tree protocol includes the bridge running information and port running information.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The Ethernet LAN service must be created. The STP or RSTP of the bridge must be enabled.
Precautions
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Step 2 Query the bridge running information. 1. 2. 3. Click the Bridge Running Info tab. Click Query. View the bridge running information.
Step 3 Query the port running information. 1. 2. 3. Click the Port Running Info tab. Click Query. View the port running information.
----End
20.8.3 Querying the Running Information About the IGMP Snooping Protocol
The running information about the IGMP Snooping protocol includes the current multicast router port and multicast table item.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The Ethernet LAN service must be created. The IGMP Snooping protocol of the bridge must be enabled.
Precautions
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Step 2 Query the information about the router port. 1. 2. 3.
Issue 02 (2009-02-25)
Click the Multicast Router Port Management tab. Click Query. View the information about the router port.
Step 3 Query the information about the multicast table item. 1. 2. 3. Click the Multicast Table Item tab. Click Query. View the information about the multicast table item.
----End

The Layer 2 switching feature may cause changes in RMON performance.
Relevant Alarms
None.

None.

For details, see 23.2.3 RMON Alarms and Performance Events.
20.8.5 FAQs
This topic lists the problems that occur frequently during the application of the Layer 2 switching feature. Q: Why should you prevent the Layer 2 switching service from forming the loop in the service networking? A: When the loop is formed in the case of the Layer 2 switching service, you must enable the STP or RSTP. The following problems may occur when the STP or RSTP is enabled:
l
If the loop is formed, the transmission network can protect the service at the physical layer (for example, MSP or SNCP). When the protection at the physical layer is initiated, this type of protection can restore the service more quickly than re-stabilizing the network topology by enabling the STP or RSTP. In this case, the STP or RSTP cannot protect the service according to the requirement and even increases the service interruption time. The spanning tree algorithm is complicated, and thus obtaining the specific service flow is difficult. In addition, the algorithm occupies a large number of NE resources.
Q: Why is the preset broadcast packet suppression threshold different from the threshold actually measured by the meter? A: That the preset threshold is slightly different from the actually measured threshold is normal. This is affected by the chip processing precision.
20-44
Issue 02 (2009-02-25)
21 QoS
21
About This Chapter
QoS
In legacy IP networks, all packets are processed according to the first in first out (FIFO) and best effort strategies. This method cannot meet the requirement of the new service for the bandwidth, delay, and delay jitter. Hence, the QoS technology is developed. 21.1 Feature Description QoS refers to the ability of the communication network to ensure the expected service quality in the aspects of 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 expected service class. 21.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the QoS feature. 21.3 Availability The QoS feature requires the support of the applicable equipment and boards. 21.4 Relation with Other Features In the case of the 605 1F/2F Ethernet port, the broadcast packet suppression function and the CAR function are mutually exclusive, and cannot be used at the same time. 21.5 Realization Principle This topic describes the flow of processing the QoS, and algorithms that are used for the CAR, traffic shaping, and egress queue scheduling. 21.6 Planning Guide Plan related parameters according to the specific application of the QoS feature. 21.7 Configuration Guide This topic describes the configuration tasks relevant to the QoS feature. 21.8 Maintenance Guide This topic describes the alarms and performance events relevant to the QoS feature, and the problems that occur frequently during the application of the QoS feature.
Issue 02 (2009-02-25)
21-1
21 QoS

QoS refers to the ability of the communication network to ensure the expected service quality in the aspects of 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 expected service class. Newly emerging services have special requirements for transmission performances such as the bandwidth, delay, and delay jitter. The traditional network in the best effort service mode, 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 21-1 shows, when congestion occurs on a network, how packets are transmitted through an interface that does not support QoS. Figure 21-1 FIFO queue
Packets to be transmitted through the interface Queue FIFO Out-of-queue grooming Packets transmitted out of the interface
The urgency of packets decreases from left to right.
All packets to be transmitted through this interface enter the tail of the FIFO queue according to the sequence of their arrival at the interface. The interface transmits these packets from the head of the queue. The packets are not differentiated during the transmission, and the quality of packet transmission is not guaranteed. Figure 21-1 uses the PQ to support QoS packet transmission. Figure 21-2 SP queue
Packets to be transmitted through the interface Queue Classification Queue 8 Queue 7 Queue 6 Priority Highest High Low Out-of-queue grooming Packets transmitted out of the interface
Queue 1 Lowest
...
21-2
Issue 02 (2009-02-25)
21 QoS
After packets arrive at the interface, the packets are classified first and then enter the tail of a queue according to the classification. The interface transmits the packets in the queue with high priority first, and then transmits the packets in the queue with low priority. In this way, the packets with higher priority are always transmitted first and these packets have a short delay. In addition, the performance specifications of these packets, including the packet loss ratio and the delay jitter, can also be guaranteed. The Ethernet switching board provides the following QoS functions: flow classification, committed access rate (CAR), class of service (CoS), and traffic shaping. These functions comply with IEEE 802.1p, RFC 2697, RFC 2698, RFC 2309, RFC 2597, and RFC 2598.
21.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the QoS feature. 21.2.1 Flow Classification Flow refers to a collection of packets with the same characteristics. In the case of the Ethernet switching board, the flow refers to a packet collection that corresponds to the same QoS operations. Flow classification means, according to certain rules, classifying a packet into several flow types on which different QoS operations are performed. Flow classification is a prerequisite and basis for the QoS operations. 21.2.2 CAR CAR is a type of traffic policing technology. After the flow classification, the CAR assesses the rate of the traffic in a certain period (including the rate in the long term and in the short term). The CAR sets the packet whose rate does not exceed the specified rate to high priority and discards the packet whose rate exceeds the specified rate or downgrades this type of packet, thus restricting the traffic into the transmission network. 21.2.3 CoS By using the CoS, the packets in a flow can be scheduled to different queues of different priorities and can be processed according to the priority of each queue. This ensures that the packets of different priorities can be processed according to different QoS requirements. 21.2.4 Traffic Shaping The traffic shaping can restrict the traffic and burst of a connection in a network, and thus enables the packet to be transmitted at an even rate. The Ethernet switching board shapes the irregular traffic or the traffic that does not conform to the specified traffic characteristics based on the generic traffic shaping (GTS) technology.
21.2.1 Flow Classification

Flow refers to a collection of packets with the same characteristics. In the case of the Ethernet switching board, the flow refers to a packet collection that corresponds to the same QoS operations. Flow classification means, according to certain rules, classifying a packet into several flow types on which different QoS operations are performed. Flow classification is a prerequisite and basis for the QoS operations. The flow type is based on the associated Ethernet service type of the flow. The flow types that are supported by Ethernet switching board EMS6 are as follows:
21 QoS
l
Port flow The packets from a certain port are classified as a type of flow. The associated Ethernet service of this flow type is the line service that uses this port as the service source. The Layer 2 switching service can also be classified as a port flow.
Port + VLAN flow The packets that are from a certain port with a specified VLAN ID are classified as a type of flow. The associated Ethernet service of this flow type is the line service that uses this port + VLAN as the service source.
Port + S-VLAN flow The packets that are from a certain port and have a specified S-VLAN are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on QinQ) or EVPLAN service (based on the 802.1ad bridge) that uses this port + S-VLAN as the service source.
Port + C-VLAN + S-VLAN flow The packets that are from a certain port and have a specified C-VLAN + S-VLAN are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on QinQ) or EVPLAN service (based on the 802.1ad bridge) that uses this port + C-VLAN + S-VLAN as the service source.
NOTE
IDU 605 1F/2F supports only port flow.
21.2.2 CAR
CAR is a type of traffic policing technology. After the flow classification, the CAR assesses the rate of the traffic in a certain period (including the rate in the long term and in the short term). The CAR sets the packet whose rate does not exceed the specified rate to high priority and discards the packet whose rate exceeds the specified rate or downgrades this type of packet, thus restricting the traffic into the transmission network. The Ethernet switching board processes the flow whose CAR feature is enabled as follows:
l
When the rate of packets is not more than the set committed information rate (CIR), these packets pass the restriction of the CAR and are forwarded first even in the case of network congestion. When the rate of packets exceeds the set peak information rate (PIR), the packets whose rate is higher than the PIR are directly discarded. When the rate of packets is higher than the CIR but is not higher than the PIR, the packets whose rate is higher than the CIR can pass the restriction of the CAR and are colored yellow, which enables these packets to be discarded first in case of network congestion. When the rate of packets that pass the restriction of the CAR is not higher than CIR in a certain period, certain packets can burst and these packets can be forwarded first even in case of network congestion. The maximum traffic of burst packets is determined by the committed burst size (CBS). The CBS contains two parts: fixed part and variable part. The fixed part is determined by the CIR and the variable part is set on the NM. When the rate of the packets that pass the restriction of the CAR is higher than the CIR but is not higher than the PIR, certain packets can burst and are marked yellow, which enables these packets to be discarded first in case of network congestion. The maximum traffic of burst packets is determined by the maximum burst size (MBS). The MBS contains two
21-4
21 QoS
parts: fixed part and variable part. The fixed part is determined by the PIR and the variable part is set on the NM.
NOTE
The CIR and PIR of IDU 605 1F/2F must be set to be the same and the CBS and PBS cannot be set.
21.2.3 CoS
By using the CoS, the packets in a flow can be scheduled to different queues of different priorities and can be processed according to the priority of each queue. This ensures that the packets of different priorities can be processed according to different QoS requirements. Each port on the Ethernet switching board EMS6 that is supported by the IDU 620 provides eight outgoing queues with the CoS priorities from 0 to 7. If the traffic shaping feature of all the queues is enabled or disabled, the queue with CoS priority 7 is a strict priority (SP) queue, and the other queues with CoS priorities 0 to 6 are weighted round robin (WRR) queues. The weight proportion of these WRR queues (with priorities from 0 to 6 respectively) is 1:2:4:8:16:32:64. If the traffic shaping feature of certain queues is enabled, according to the preset CIR, bandwidth is allocated first to the queue whose traffic shaping feature is enabled. By using the SP + WRR algorithm, the remaining bandwidth is allocated to the queues whose traffic shaping is disabled. The Ethernet port on the IFH2 board that is supported by the IDU 620 provides four outgoing queues. The corresponding CoS priorities are 0-3 respectively and the queue scheduling mode is SP. The higher the CoS priority, the higher the queue priority. The IFH2 board supports only the CoS type of VLAN priority. The data frames that do not carry the VLAN tag are scheduled to the queue with the lowest priority by default. The Ethernet port on the IDU 605 1F/2F provides four outgoing queues. The corresponding CoS priorities are 0-3 respectively. The higher the CoS priority, the higher the queue priority. The queue scheduling mode is SP or WRR (the weight proportion is 1:2:4:8). These two scheduling modes cannot be used at the same time. Table 21-1 lists the CoS types that are supported by the equipment. Table 21-1 CoS Type CoS Type Description IDU 620 EMS6 Simple If the CoS type of a flow is set to simple, all the packets in this flow are directly scheduled to a specified outgoing queue. Supports IFH2 Does not support Does not support IDU 605 1F/2F
Issue 02 (2009-02-25)
21-5
21 QoS
CoS Type
Description
IDU 620 EMS6 IFH2 Supports
IDU 605 1F/2F
VLAN priority
If the CoS type of a flow is set to VLAN priority, the packets in this flow are scheduled to a specified outgoing queue according to user priority in the VLAN tag. If the CoS type of a flow is set to differentiated services code point (DSCP), the packets in this flow are scheduled to a specified outgoing queue according to the DSCP in the IP tags of these packets.
Supports
Supports
DSCP
Supports
Does not support
Supports
NOTE
In the case of the simple type, the maximum number of CoSs supported by the EMS6 board is 8. In the case of the VLAN priority type, the maximum number of CoSs supported by the EMS6 board is 6. In the case of the DSCP type, the maximum number of CoSs supported by the EMS6 board is 6. The EMS4 board (a logical board) that is used on the IDU 605 1F/2F supports one board-level CoS.
21.2.4 Traffic Shaping

The traffic shaping can restrict the traffic and burst of a connection in a network, and thus enables the packet to be transmitted at an even rate. The Ethernet switching board shapes the irregular traffic or the traffic that does not conform to the specified traffic characteristics based on the generic traffic shaping (GTS) technology. In the case of the port queue whose traffic shaping feature is enabled, the Ethernet switching board processes the packets as follows before they enter the queue:
l
When the rate of the packets is not more than the set CIR, these packets directly enter the egress queue. When the rate of the packets is more than the set PIR, these packets enter the buffer. When the buffer overflows, the packets are discarded. When the rate of the packets is more than the CIR but not more than the PIR, the packets whose rate is more than the CIR enter the buffer of the CIR. When the buffer overflows,
21-6
21 QoS
these packets are marked yellow and enter the egress queue. In this case, these packets are discarded in the case of queue congestion.
l
When the rate of the packets that pass the restriction of the traffic shaping in a certain period is not more than the CIR, certain burst packets enter the egress queue. The maximum traffic of the burst packets is determined by the CBS. The value of the CBS is determined by the CIR, and cannot be set. When the rate of the packets that pass the restriction of the traffic shaping in a certain period is more than the CIR but not more than the PIR, certain burst packets enter the buffer of the CIR. The maximum traffic of the burst packets is determined by the MBS. The value of the MBS is determined by the PIR, and cannot be set.
As is evident from the preceding processing mechanism, the difference of the traffic shaping from the CAR is as follows:
l
In the processing of the CAR, the packet that does not conform to the traffic characteristics is downgraded in priority or directly discarded. In the processing of the traffic shaping, the packet that does not conform to the traffic characteristics is stored in the buffer. The packet is downgraded in priority or directly discarded only when the buffer overflows.
21.3 Availability
The QoS feature requires the support of the applicable equipment and boards. Table 21-2 Availability of the QoS Feature Feature QoS Traffic classification Applicable Board EMS6 (all the versions) CAR EMS6 (all the versions) CoS EMS6 (all the versions) IFH2 (all the versions) Traffic shaping EMS6 (all the versions) Applicable Equipment IDU 620 IDU 605 1F/2F IDU 620 IDU 605 1F/2F IDU 620 IDU 605 1F/2F IDU 620 IDU 620

In the case of the 605 1F/2F Ethernet port, the broadcast packet suppression function and the CAR function are mutually exclusive, and cannot be used at the same time.
Issue 02 (2009-02-25)
21-7
21 QoS

This topic describes the flow of processing the QoS, and algorithms that are used for the CAR, traffic shaping, and egress queue scheduling. 21.5.1 CAR The CAR uses the dual token bucket three color marker algorithm. 21.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 token bucket in the algorithm used by the traffic shaping. 21.5.3 Egress Queue Scheduling An egress guarantees the scheduling priority, probability, and bandwidth by using the shaping and the CoS methods.
21.5.1 CAR
The CAR uses the dual token bucket three color marker algorithm.
Token Bucket Algorithm

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

Figure 21-4 shows the basic principle of the dual token bucket three color marker algorithm that is used by the CAR. Figure 21-4 Basic principle of the algorithm that is used by the CAR
...
PIR
...
CIR
Classification
Tp
Tc
This algorithm uses two token buckets Tc and Tp, and marks colors for packets according to the situations when these packets pass the token bucket.
NOTE
In the case of the EMS6 board, the marked colors are only internal tags and do not change original priorities of packets.
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 equals the CBS. The packet is placed into the Tp token bucket at the rate of PIR, and the capacity of the Tp token bucket equals the MBS.
A packet is marked as follows:

l
If a packet obtains the Tc token, this packet is marked green. This kind of packet can pass the restriction of the CAR and is 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 kind of packet can pass the restriction of the CAR but is discarded first in the case of network congestion.
If a packet does not obtain the Tp token, this packet is marked red. This kind of packet is directly discarded.
Issue 02 (2009-02-25)
21-9
21 QoS
21.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 token bucket in the algorithm used by the traffic shaping. Figure 21-5 shows the basic principle of the dual token bucket three color marker algorithm that is used by the traffic shaping.
NOTE
In the case of the EMS6 board, the marked colors are only internal tags and do not change original priorities of packets.
Figure 21-5 Basic principle of the algorithm that is used by the traffic shaping
Tp buffer queue
Tp token bucket
This algorithm uses two token buckets Tc and Tp, and places packets into different queues according to the situations when these packets pass the token bucket. The parameters of these two token buckets are as follows:
l
The packet is placed into the Tc token bucket at the rate of CIR, and the capacity of the Tc token bucket equals the CBS. The packet is placed into the Tp token bucket at the rate of PIR, and the capacity of the Tp token bucket equals the EBS.
...
PIR
Tc buffer queue
Tc token bucket
...
CIR
A packet is placed into a queue as follows:

l l
If a packet obtains the Tc token, this packet is directly placed into the egress queue. If a packet obtains the Tp token but does not obtain the Tc token, this packet is placed into the Tc buffer queue. When the Tc buffer queue overflows, the overflow packet is marked yellow and then enters the egress queue, which indicates that the packet is discarded first in the case of network congestion.
If a packet does not obtain the Tp token, this packet is placed into the Tp buffer queue. When the Tp buffer queue overflows, the overflow packet is directly discarded.
21.5.3 Egress Queue Scheduling

An egress guarantees the scheduling priority, probability, and bandwidth by using the shaping and the CoS methods.
21 QoS
Basic Concepts
Port available bandwidth: The system allocates bandwidth to a port.
l
For an external Ethernet port, the port available bandwidth is determined by the working mode of the port. For example, if the working mode of a port is 1000M full duplex, the available bandwidth of the port is 1000 Mbit/s. For a VCTRUNK port, the available bandwidth is determined by the total bandwidth of the virtual concatenation (VC) paths that is bound to the port virtual concatenation group (VCG).
SP Queue Scheduling Algorithm

Figure 21-6 illustrates the strict-priority (SP) queue scheduling algorithm. Figure 21-6 SP queue
Packets to be transmitted through the interface Queue Classification Queue 8 Queue 7 Queue 6 Priority Highest High Low Out-of-queue grooming Packets transmitted out of the interface
Queue 1 Lowest
The SP queue 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. This is an important feature for a key service. 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 way, if packets of key service are put into queues with high priority and packets of non-key services (such as E-mail service) into queues with lower priority, the packets of key service can be sent first and the packets of non-key service are sent when the data of key service is not processed. The disadvantage of the SP scheduling algorithm is as follows: if there are packets existing in the queues with high priority when congestion occurs, packets in the queues with low priority cannot be transmitted all the time.
...
WRR Scheduling Algorithm

Figure 21-7 illustrates the weighted round robin (WRR) scheduling algorithm.
21 QoS
Figure 21-7 WRR scheduling algorithm

Packets to be transmitted through the interface Queue Classification Queue 4 Queue 3 Queue 2 Queue 1 Weight 50 30 10 10 Out-of-queue grooming Packets transmitted out of the interface
The WRR scheduling algorithm divides each port into several 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 configure the w3, w2, w1, and w0 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 100M port and the weights of its four queues are set to 50, 30, 10, and 10 (corresponding to w3, w2, w1, and w0 respectively) by the WRR scheduling algorithm, then a minimum of 10 Mbit/s bandwidth is guaranteed for the queue with the lowest priority. This prevents the disadvantage that in the SP queue scheduling, packets in the queues with lower priority may fail to obtain service for a long time. Another advantage of WRR scheduling is that, 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 of the next queue are scheduled immediately. In this way, the bandwidth resources can be fully utilized.
SP+WRR scheduling algorithm

As shown in Figure 21-8, by combining the advantages of the SP and WRR algorithms, the SP +WRR scheduling algorithm sets one of the outgoing queues as an SP queue. In this way, packets in this queue are always scheduled first, which ensures that 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.
21-12
Issue 02 (2009-02-25)
21 QoS
Figure 21-8 SP+WRR scheduling algorithm

Queues Packets that need to be sent from this port
Classification
Weight Strict priority 64 32 Egress scheduling Packets that leave this port
Queue 8 Queue 7 Queue 6
Queue 1
Queue where packets are arranged according to emergency level in a descending order from left to right
Use the port that supports eight outgoing queues as an example.

l
Queue 8 (whose CoS value is 7) uses the SP algorithm. When there are packets existing in this queue, these packets are transmitted first. When there is no packet existing in this queue, the packets in other queues can be transmitted. Service time segment is allocated to each queue of queues 1-7 (whose CoS values 0-6 respectively) according to the weight proportions 1:2:4:8:16:32:64, and at each time segment the packets in the corresponding queue are transmitted. If there is no packet existing in the queue that corresponds to a time segment, this time segment is neglected and the packets in the queue that corresponds to the next time segment are transmitted. For example, if the port that supports four queues is used as an example and the 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 432443414342434.
...
1
If the traffic shaping of some queues is enabled, according to the set CIR, the bandwidth is first allocated to the queue whose traffic shaping is enabled. By using the preceding algorithm, the remaining bandwidth is allocated to the queue whose traffic shaping is disabled. For example, the traffic shaping of queues 5 and 7 is enabled, 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 weight proportion is 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 algorithms. 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 weight proportion 1:2:4:8:32 of these queues. When congestion occurs on the outgoing queues, the packet that is colored yellow in the CAR or in the traffic shaping is first discarded.
21.6 Planning Guide

Plan related parameters according to the specific application of the QoS feature.
Issue 02 (2009-02-25)
21-13
21 QoS
Prerequisite
l
You must know the type and specific situation of the Ethernet service that requires the QoS application. You must know the functions of the QoS feature.
Procedure
Step 1 Select the proper QoS function according to the requirement. Adhere to the following principles when selecting the QoS function:
l l
First select the CAR. This can control the service traffic on the ingress side. In the case of the important service that requires to improve the traffic fluctuation, select the traffic shaping function. If differentiated services are required for different service types or different user classes, select the CoS function.
Step 2 Optional: Plan the CAR. Adhere to the following principles when planning the CAR:
l l
Bind a CAR to a flow. Do not bind a CAR to multiple flows. The sum of CIRs of all the CARs that are associated with a particular PORT or VCTRUNK should not exceed the physical bandwidth of that particular PORT or VCTRUNK.
Step 3 Optional: Plan the traffic shaping and CoS. Adhere to the following principles when planning the traffic shaping and CoS:
l
Allocate the service of low delay or the service of low delay commitment (such as the signaling data, VoIP data, and network management protocol packet) into the queues of strict priority. Allocate the service that does not require low delay or that does not provide low delay commitment (such as the Internet service) into the WRR queue. The sum of CIRs of all the queues that are associated with a particular PORT or VCTRUNK should not exceed the physical bandwidth of that particular PORT or VCTRUNK. Plan the parameters of the traffic shaping according to the traffic characteristics, thus preventing the buffer from overflowing frequently.
----End

This topic describes the configuration tasks relevant to the QoS feature. 21.7.1 Creating a Flow In the case of the Ethernet switching board, a flow refers to the collection of packets on which the same QoS operation is performed. Creating a flow is the prerequisite for performing CAR and CoS operations. 21.7.2 Creating the CAR CAR is a type of traffic policing technologies. After the flow classification, the CAR assesses the rate of the traffic in a certain period (including in the long term and in the short term). The
21 QoS
CAR sets the packet whose rate does not exceed the specified rate to high priority and discards the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus restricting the traffic into the transmission network. 21.7.3 Creating the CoS By using the CoS, the packets in a flow can be scheduled to different queues of different priorities and can be processed according to the priority of each queue. This ensures that the packets of different priorities can be processed according to different QoS requirements. 21.7.4 Binding the CAR/CoS To enable the CAR or CoS function, bind the corresponding flow to the created CAR/CoS. 21.7.5 Configuring the Traffic Shaping The traffic shaping can restrict the traffic and burst of a connection in a network, and thus enables the packets to be transmitted at an even rate. 21.7.6 Configuring the CoS of the IFH2 Board The IFH2 board supports scheduling packets into different queues according to the corresponding user priority levels in the VLAN tags. 21.7.7 Setting the Queue Scheduling Mode The IDU 605 1F/2F supports the setting of the board-level queue scheduling mode of the EMS4 board (a logical board).
21.7.1 Creating a Flow

In the case of the Ethernet switching board, a flow refers to the collection of packets on which the same QoS operation is performed. Creating a flow is the prerequisite for performing CAR and CoS operations.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The associated Ethernet service must be created.
Precautions
The IDU 620 supports the Ethernet switching board EMS6. The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board), which supports the creation of port flow only.
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the Flow Configuration tab. Step 3 Click New. The New Flow dialog box is displayed.
21 QoS
Step 4 Set the flow parameters.
Parameters
Parameter Flow Type Value Range Port Flow, Port +VLAN Flow, Port +SVLAN Flow, Port+CVLAN +SVLAN Flow Default Value Port Flow Description Port flow: The packets from a certain port are classified as a type of flow. The Ethernet service associated with this flow type is the line service or Layer 2 switching service that uses this port as the service source. Port+VLAN flow: The packets that are from a certain port and have a specified VLAN ID are classified as a type of flow. The associated Ethernet service of this flow type is the line service that uses this port+VLAN as the service source. Port+SVLAN flow: The packets that are from a certain port and have a specified SVLAN ID are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on QinQ) or EVPLAN service (based on the 802.1ad bridge) that uses this port + S-VLAN as the service source. Port+CVLAN+SVLAN flow: The packets that are from a certain port and have a specified CVLAN+SVLAN are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on QinQ) or EVPLAN service (based on the 802.1ad bridge) that uses this port + C-VLAN + S-VLAN as the service source.
21-16
Issue 02 (2009-02-25)
21 QoS
Parameter Port
Value Range PORT1PORT6, VCTRUNK1 VCTRUNK8 (EMS6) PORT1PORT4 (EMS4)
Default Value PORT1
Description
l
When the associated service is the line service, set this parameter to the source port or sink port of the associated Ethernet service. When the associated service is the Layer 2 switching service, set this parameter to a mounted port of the bridge. This parameter is valid only when Flow Type is set to Port+VLAN Flow. Set this parameter to the source VLAN of the associated Ethernet service. This parameter is valid only when Flow Type is set to Port+SVLAN+CVLAN Flow. Set this parameter to the source C-VLAN of the associated Ethernet service. This parameter is valid only when Flow Type is set to Port+SVLAN Flow or set to Port+SVLAN+CVLAN Flow Set this parameter to the source S-VLAN of the associated Ethernet service.
VLAN ID
14095
C-VLAN
14095
S-VLAN
14095
Postrequisite
After creating a flow, bind it to the corresponding CAR or CoS operation as required.
21.7.2 Creating the CAR

CAR is a type of traffic policing technologies. After the flow classification, the CAR assesses the rate of the traffic in a certain period (including in the long term and in the short term). The CAR sets the packet whose rate does not exceed the specified rate to high priority and discards the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus restricting the traffic into the transmission network.
Prerequisite
Precautions
The IDU 620 supports the Ethernet switching board EMS6. The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board). In the case of the EMS4 board, the values of the CIR and PIR should be set the same and the setting of the CBS and MBS is not supported.
21 QoS
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the CAR Configuration tab. Step 3 Click New. The New Car dialog box is displayed. Step 4 Set the CAR parameters.
Parameters
Parameter CAR ID Value Range 165535 (EMS6) 11024 (a logical board EMS4) Enabled/Disabled Enabled, Disabled Disabled Default Value Description This parameter identifies a CAR operation, and is used to bind a flow to an associated CAR operation. This parameter determines whether to enable the CAR operation performed on the flow bound to the CAR.
l
Committed Information Rate (kbit/s)
An integer ranging from 0 to 1048576, with a step of 64
When the rate of the packets is not more than the CIR, these packets pass the restriction of the CAR and are forwarded first even in the case of network congestion. The value of this parameter should not be more than the PIR.
21-18
Issue 02 (2009-02-25)
21 QoS
Parameter Committed Burst Size (kbyte)a
Value Range 01024
Default Value 0
Description When the rate of the packets that pass the restriction of the CAR is not more than the CIR in a certain period, certain packets can burst and can pass the restriction of the CAR. These packets can be forwarded first even in the case of network congestion. The maximum traffic of the burst packets is determined by the CBS. Note that the CBS has an inherent size, and this parameter indicates the increment value only. The inherent size of the CBS is determined by the CIR. The greater the CIR, the greater the CBS.
l
Peak Information Rate (kbit/s)a
When the rate of the packets is more than the PIR, these packets that exceed the rate restriction are directly discarded. When the rate of the packets is more than the CIR but is not more than the PIR, the packets whose rate is more than the CIR can pass the restriction of the CAR and are marked yellow, which enables these packets to be discarded first in the case of network congestion. The value of this parameter should not be more than the bandwidth at the port.
Maximum Burst Size (kbyte)a
01024
When the rate of the packets that pass the restriction of the CAR is more than the CIR but is not more than the PIR, certain packets can burst and are marked yellow, which enables these packets to be discarded first in the case of network congestion. The maximum traffic of the burst packets is determined by the set MBS. Note that the MBS has an inherent size, and this parameter indicates the increment value only. The inherent size of the MBS is determined by the PIR. The greater the PIR, the greater the MBS.
Issue 02 (2009-02-25)
21-19
21 QoS
NOTE
a: In the case of the IDU 605 1F/2F, the values of the CIR and PIR should be set the same and the setting of the CBS and MBS is not supported.
Postrequisite
After creating the CAR, bind the flow to the corresponding CAR operation as required.
21.7.3 Creating the CoS

By using the CoS, the packets in a flow can be scheduled to different queues of different priorities and can be processed according to the priority of each queue. This ensures that the packets of different priorities can be processed according to different QoS requirements.
Prerequisite
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the CoS Configuration tab. Step 3 Click New. The New CoS dialog box is displayed. Step 4 Set the CoS parameters.
21-20
Issue 02 (2009-02-25)
21 QoS
Parameters
Parameter CoS ID Value Range 165535 Default Value 1 Description This parameter identifies a CoS operation, and is used to bind a flow to an associated CoS operation. In the case of the EMS4 board (logical board), only one CoS can be created. When the CoS is bound, this CoS operation is valid for all the ports on the board.
Issue 02 (2009-02-25)
21-21
21 QoS
Parameter CoS Type
Value Range In the case of the EMS6 board:

l l l
Default Value -
Description
l
simple VLAN priority DSCP

l
If the CoS type of a flow is set to simple, all the packets in this flow are directly scheduled to a specified egress queue. If the CoS type of a flow is set to VLAN priority, the packets in this flow are scheduled to specified egress queues according to the user priorities specified in the VLAN tags of these packets. If the CoS type of a flow is set to DSCP, the packets in this flow are scheduled to specified egress queues according to differentiated services code point (DSCP) in the IPv6 tags of these packets.
In the case of the EMS4 board (a logical board):

l l
VLAN priority DSCP
CoS Priority
In the case of the EMS6 board: 07 In the case of the EMS4 board (a logical board): 03
This parameter specified which queue a packet is scheduled to. In the case of the EMS6 board:
l
Each port on the EMS6 board supports eight egress queues, and the CoS priorities of these eight queues are from 0 to 7. If the traffic shaping feature of all the queues is enabled or disabled, the queue whose CoS priority is 7 is an SP queue, and the other queues whose priorities are from 0 to 6 are WRR queues. The weighted proportion of these WRR queues are 1:2:4:8:16:32:64 (from priority 0 to priority 6). If the traffic shaping feature of certain queues is enabled, the bandwidth is allocated first to the queue whose traffic shaping feature is enabled, according to the set CIR. The remaining bandwidth is allocated to the queues whose traffic shaping is disabled, according to the SP +WRR algorithm.
In the case of the EMS4 board (a logical board):

l
The Ethernet port on the EMS4 board supports four egress queues, and the CoS priorities of these four queues are from 0 to 3. When the CoS priority is higher, the priority of the queue is higher. When the WRR algorithm is used, the weighted proportion of the queues whose CoS priorities are from 03 is 1:2:4:8.
21-22
Issue 02 (2009-02-25)
21 QoS
Postrequisite
After creating the CoS, bind the flow to the corresponding CoS operation as required.
21.7.4 Binding the CAR/CoS

To enable the CAR or CoS function, bind the corresponding flow to the created CAR/CoS.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet switching board must be included in the slot layout. The flow and CAR/CoS must be created.
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS Management > Flow Management . Step 2 Click the Flow Configuration tab. Step 3 Bind the CAR/CoS.
Parameters
Parameter Bound CAR Value Range Default Value Description This parameter indicates the CAR ID corresponding to a CAR operation. Different CAR IDs should be bound to different flows, even though the parameters of the CAR operations are the same.
Issue 02 (2009-02-25)
21-23
21 QoS
Parameter Bound CoS
Value Range -
Default Value -
Description This parameter indicates the CoS ID corresponding to a CoS operation. In the case of the EMS6 board, different CoS IDs should be bound to different flows, even though the parameters of the CoS operations are the same. In the case of the EMS4 board (logical board), only one CoS can be created. When the CoS is bound, this CoS operation is valid for all the ports on the board.
21.7.5 Configuring the Traffic Shaping

The traffic shaping can restrict the traffic and burst of a connection in a network, and thus enables the packets to be transmitted at an even rate.
Prerequisite
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS Management > Port Shaping Management from the Function Tree. Step 2 In Port List, select a port. Step 3 Set the traffic shaping information about the port queue.
Parameters
Parameter Port Value Range A specific PORT or VCTRUNK Default Value Description This parameter indicates the port whose traffic is shaped.
Issue 02 (2009-02-25)
21-24
21 QoS
Parameter Enabled/Disabled
Description
l
This parameter determines whether to enable the traffic shaping of an egress queue. If the traffic shaping feature of certain queues is enabled, the bandwidth is allocated first to the queue whose traffic shaping feature is enabled, according to the set CIR. The remaining bandwidth is allocated to the queues whose traffic shaping is disabled, according to the SP +WRR algorithm. When the rate of the packets is not more than the CIR, these packets directly enter the egress queue. The value of this parameter should not be more than the PIR. When the rate of the packets is more than the PIR, the packets that exceed the rate restriction are directly discarded. When the rate of the packets is more than the CIR but not more than the PIR, the packets whose rate is more than the CIR enter the buffer of the CIR. When the buffer overflows, the packets are marked yellow and enter the egress queue, which enables these packets to be discarded first in the case of queue congestion. The value of this parameter should not be more than the bandwidth at the port.
CIR (kbit/s)
PIR (kbit/s)
21.7.6 Configuring the CoS of the IFH2 Board

The IFH2 board supports scheduling packets into different queues according to the corresponding user priority levels in the VLAN tags.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The IFH2 board must be added in the NE Panel.
Procedure
Step 1 Select the IFH2 board in the NE Explorer. Then, choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Set CoS Priority for User Priority 0 in the VLAN Tag to User Priority 7 in the VLAN Tag.
21 QoS
Parameters
Parameter CoS Parameter Value Range User Priority 0 in the VLAN Tag. User Priority 1 in the VLAN Tag, User Priority 2 in the VLAN Tag, User Priority 3 in the VLAN Tag, User Priority 4 in the VLAN Tag, User Priority 5 in the VLAN Tag, User Priority 6 in the VLAN Tag, User Priority 7 in the VLAN Tag 03 Default Value Description This parameter specifies the data flows. The IFH2 boards supports differentiating the data flows according to the user priority levels in the VLAN tags of packets.
CoS Priority
This parameter specifies the queue to which a packet should be scheduled. The IFH2 board supports four queues. The corresponding CoS priority levels that correspond to the four queues are 0 3 and the scheduling scheme is SP. The higher the CoS priority, the higher is the queue priority.
21.7.7 Setting the Queue Scheduling Mode

The IDU 605 1F/2F supports the setting of the board-level queue scheduling mode of the EMS4 board (a logical board).
Prerequisite
21 QoS
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS Management > Board Shaping Management from the Function Tree. Step 2 Select a board-level Queue Scheduling Mode. Step 3 Click Apply. ----End
Parameters
Parameter Queue Scheduling Mode Value Range WRR, SP Default Value WRR Description
l
If this parameter is set to SP, the SP algorithm is used for the service grooming on egress ports on the EMS4 board (a logical board). The higher is the priority of the CoS corresponding to the queue, the higher is the priority of the queue. If this parameter is set to WRR, the WRR algorithm is used for the service grooming on egress ports on the EMS4 board (a logical board). The weight proportion of the four queues is 1:2:4:8.

This topic describes the alarms and performance events relevant to the QoS feature, and the problems that occur frequently during the application of the QoS feature. 21.8.1 Relevant Alarms and Events The QoS feature may cause changes in RMON performance. 21.8.2 FAQs This topic lists the problems that occur frequently during the application of the QoS feature.

The QoS feature may cause changes in RMON performance.
Relevant Alarms
None.

None.

21 QoS
21.8.2 FAQs
This topic lists the problems that occur frequently during the application of the QoS feature. Q: Why is the Ethernet service interrupted after the traffic shaping is enabled? A: Generally, this problem occurs because the CIR and PIR are not configured. By default, the CIR and PIR are 0. Q: Why is the rate limitation result calculated by the preset CIR different from the rate limitation result that is actually measured by the meter? A: It is normal that a slight difference lies between the rate limitation result calculated by 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.
21-28
Issue 02 (2009-02-25)
22 QinQ
22
About This Chapter
QinQ
The Ethernet switching processing board supports the line services that are based on QinQ (802.1q in 802.1q). The function complies with IEEE 802.1q and IEEE 802.1ad. 22.1 Feature Description QinQ provides a Layer 2 virtual private network (VPN) solution that is much cheaper and easier than provided by multi-protocol label switch (MPLS). By using the VLAN QinQ technology, the data packets carry two VLAN tags to distinguish different services. This changes the limitation that only one VLAN tag is used to mark the data packets, and increases the number of VLAN IDs. The inner VLAN is called the C-VLAN, representing the customer VLAN. The outer VLAN is called S-VLAN, representing the service provider VLAN. 22.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the QinQ feature. 22.3 Availability The QinQ technology is applicable to the Ethernet private line service and the Ethernet LAN service. 22.4 Relation with Other Features The QinQ technology is applied to the Ethernet line service and LAN service of the Ethernet switching board. 22.5 Realization Principle The attributes of QinQ packets are closely related to the port attributes and service type. 22.6 Planning Guide Plan related parameters according to the specific application of the QinQ feature. 22.7 Configuration Guide This topic describes the configuration flow and the corresponding configuration tasks of the QinQ line service. An example is provided as additional information to help understand the configuration. 22.8 Configuration Example (EVPL Services Based on QinQ) This topic provides an example to describe how to configure QinQ line services.
22 QinQ
22.9 Configuration Example (EVPLAN Services Based on the IEEE 802.1ad Bridge) This topic considers an example to describe how to configure the EVPLAN services that are based on the IEEE 802.1ad bridge. 22.10 Maintenance Guide This topic describes the alarms and performance events relevant to the QinQ feature, and the problems that occur frequently during the application of the QinQ feature.
22-2
Issue 02 (2009-02-25)
22 QinQ

QinQ provides a Layer 2 virtual private network (VPN) solution that is much cheaper and easier than provided by multi-protocol label switch (MPLS). By using the VLAN QinQ technology, the data packets carry two VLAN tags to distinguish different services. This changes the limitation that only one VLAN tag is used to mark the data packets, and increases the number of VLAN IDs. The inner VLAN is called the C-VLAN, representing the customer VLAN. The outer VLAN is called S-VLAN, representing the service provider VLAN. The functions of the QinQ technology are as follows:
l
With the application of the QinQ technology, the number of VLAN IDs can reach 4096 x 4096. This solves the problem that the number of VLAN IDs cannot meet the requirement. Operators can plan VLAN resources independently and flexibly, thus simplifying network configuration and maintenance. The QinQ technology, providing a cheaper and simpler L2 VPN solution, replaces the MPLS technology. The QinQ technology enables the expansion of Ethernet services from local area networks (LANs) to wide area networks (WANs).
The QinQ technology complies with the following standards:

l l
IEEE 802.1q IEEE 802.1ad
22.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the QinQ feature. 22.2.1 Frame Format The QinQ technology defines three types of Ethernet frames: Ethernet frame with only a CTAG, Ethernet frame with a C-TAG and an S-TAG, and Ethernet frame with only an S-TAG. 22.2.2 Network Attributes The network attribute of each port (PORT or VCTRUNK) can be set to UNI, C-aware, or Saware depending on how the port processes the C-TAG and S-TAG. 22.2.3 Application of the QinQ Technology in Line Services Introduction of the QinQ technology provides many new applications for line services. 22.2.4 Application of the QinQ Technology in LAN Services The use of the QinQ technology provides the application of the EVPLAN service that is based on the 802.1ad bridge.
22.2.1 Frame Format

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

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

In the case of an Ethernet frame that contains a C-TAG and an S-TAG, the S-TAG is added before the C-TAG. The differences between the S-TAG and the C-TAG are as follows:
l
The TPID is different. As defined in IEEE 802.1ad, the value of the TPID in the S-TAG is 0x88a8, whereas the value of the TPID in the C-TAG is 0x8100.
NOTE
The TPID in the S-TAG that is supported by the Ethernet switching board has the same value as the TPID in the C-TAG. The TPID value is 0x8100. The TPID value in the S-TAG can be modified. For details, see 22.7.3 Modifying the Type Field of QinQ Frames.
l
The drop eligible indicator (DEI) replaces the CFI. The DEI works with the PCP to indicate the priority of the S-TAG.
Figure 22-2 Format of the Ethernet frame with a C-TAG and an S-TAG
4 bytes Destination address Source address S-TAG C-TAG Length/Type Data FCS (CRC-32)
TCI TPID 16 bits PCP 3 bits DEI 1 bit VID 12 bits
22-4
Issue 02 (2009-02-25)

NOTE
22 QinQ
Certain vendors use the Ethernet frames each of which contains a C-TAG and an S-TAG but whose type field is not set to 0x8100. To ensure that the OptiX RTN 600 can be interconnected with the equipment of the vendors, the Ethernet switching board of Huawei supports manual setting of the type field.
Ethernet Frame with Only an S-TAG

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

The network attribute of each port (PORT or VCTRUNK) can be set to UNI, C-aware, or Saware depending on how the port processes the C-TAG and S-TAG.
UNI Port
A UNI port verifies and processes the outer tag of an Ethernet frame according to the TAG attributes of the port. UNI ports cannot be used in the case of QinQ services.
C-Aware Port
A C-aware port is in an equivalent position as a UNI port in a network. A C-aware port considers that an accessed packet does not contain an S-TAG. C-aware ports can be used in the case of QinQ services.
NOTE
l l l
C-TAG frames and untagged frames can normally enter and exit C-aware ports. When an S-TAG frame enters and exits a C-aware port, the port processes the S-TAG as a C-TAG. When a frame that contains an S-TAG and a C-TAG enters and exits a C-aware port, the port processes the S-TAG as a C-TAG and does not process the inner C-TAG.
S-Aware Port
An S-aware port is in an equivalent position as a NNI port in a network. An S-aware port considers that an accessed packet contains an S-TAG. S-aware ports can be used in the case of QinQ services.
22 QinQ
NOTE
l l l l
S-TAG frames or the frames that contain an S-TAG and a C-TAG can normally enter and exit S-aware ports. When a C-TAG frame enters and exits an S-aware port, the port processes the C-TAG frame as an S-TAG frame. When an untagged frame enters and exits an S-aware port, the port discards the frame. When a frame that contains an S-TAG and a C-TAG enters and exits an S-aware port of an EMS6 board, the port processes only the S-TAG and does not process the inner C-TAG.
22.2.3 Application of the QinQ Technology in Line Services

Introduction of the QinQ technology provides many new applications for line services.
Line Services Between C-Aware Ports

The line services between C-aware ports have two applications. Table 22-1 Line services between C-aware ports Type of Packet (Type of Source Port) Data frames that contain a C-VLAN tag (C-aware port) Data frames that contain a C-VLAN tag or do not contain a C-VLAN tag (Caware port) Operation Type Direction Description
Transparently transmit C-VLAN
Unidirectional/ Bidirectional
Transparently transmits packets according to the CVLAN. Transparently transmits packets.
Transparently transmit C-VLAN
Unidirectional/ Bidirectional
Line Services Between a C-Aware Port and an S-Aware Port

The line services between a C-aware port and an S-aware port have three applications. Table 22-2 Line services between a C-aware port and an S-aware port Type of Packet (Type of Source Port) Data frames that contain a CVLAN tag (Caware port) Operation Type Direction Description
Add S-VLAN
Unidirectional
Transmits packets according to the C-VLAN and adds an S-VLAN tag to each packet.
22-6
Issue 02 (2009-02-25)
22 QinQ
Type of Packet (Type of Source Port)
Operation Type
Direction
Description
Bidirectional
In the case of the service from a Caware port to an S-aware port, the port transmits the packets according to the C-VLAN and adds an SVLAN tag to each packet. In the case of the service from an Saware port to a C-aware port, the port transmits the packets according to the C-VLAN and strips the SVLAN tag from each packet.
Data frames that contain a CVLAN tag or do not contain a CVLAN tag (Caware port)
Add S-VLAN
Unidirectional Bidirectional
Transmits packets and adds an SVLAN tag to each packet. In the case of the service from a Caware port to an S-aware port, the port adds an S-VLAN tag to each packet. In the case of the service from an Saware port to a C-aware port, the port strips the S-VLAN tag from each packet.
S-TAG or STAG + C-TAG (S-aware port)
Strip S-VLAN
Unidirectional
Transmits packets according to the S-VLAN and strips the S-VLAN tag from each packet.
NOTE
The priority of the S-VLAN tag added by the "Add S-VLAN" operation is 0 by default. The priority can be set.
Line Services Between S-Aware Ports

The line services between S-aware ports have two applications. Table 22-3 Line services between S-aware ports Type of Packet (Type of Source Port) S-TAG or STAG + C-TAG (S-aware port) Operation Type Direction Description
Transparently transmit SVLAN Translate SVLAN
Unidirectional/ Bidirectional Unidirectional/ Bidirectional
Transparently transmits packets according to the S-VLAN. Transmits packets according to the S-VLAN, which is translated.
22-7
Issue 02 (2009-02-25)
22 QinQ
22.2.4 Application of the QinQ Technology in LAN Services

The use of the QinQ technology provides the application of the EVPLAN service that is based on the 802.1ad bridge. The IEEE 802.1ad bridge supports the data frame that has double VLAN tags. The outer VLAN tag (namely, S-VLAN tag) is used to isolate VLANs. The IEEE 802.1ad bridge supports only the port whose network attribute is set to C-aware or S-aware. The IEEE 802.1ad bridge supports the following two switching modes. For details, refer to Table 22-4. 1. The IEEE 802.1ad bridge does not check the contents of the VLAN tags in the data frames that enter the bridge but performs Layer 2 switching according to the destination MAC addresses of the data frames. The IEEE 802.1ad bridge checks the contents of the VLAN tags in the data frames that enter the bridge and performs Layer 2 switching according to the destination MAC addresses and S-VLAN IDs of the data frames.
2.
Table 22-4 Characteristics of the IEEE 802.1ad bridge Bridge Type Bridge Switch Mode Bridge Learning Mode SVL IVL Ingress Filter
IEEE 802.1ad bridge
SVL/Ingress Filter Disable IVL/Ingress Filter Enable
Disabled Enabled
The C-aware ports are used to add and strip the S-VLAN tags. The S-aware ports are used to transparently transmit the S-VLAN tags. The ports that are mounted to the IEEE 802.1ad bridge support the following operation types:
l l l l
Add S-VLAN base for port Add S-VLAN base for port and C-VLAN Mount port Mount port and base for port and S-VLAN
This topic describes the four operation types when Bridge Switch Mode of the IEEE 802.1ad bridge is set to IVL/Ingress Filter Enabled.
LAN Services That Enter and Exit the C-Aware Port

Table 22-5 lists the applications of the LAN services that enter and exit the C-aware port.
22-8
Issue 02 (2009-02-25)
22 QinQ
Table 22-5 LAN services that enter and exit the IEEE 802.1ad bridge through the C-aware port Type of Data Frame Data frames that contain a CVLAN tag or do not contain a CVLAN tag Operation Type Add S-VLAN Base for Port Direction Ingress Description 1. When the data frames enter the bridge through the C-aware port, the data frames are added with the preset S-VLAN tag. 2. After the data frames enter the bridge, the data frames are forwarded in the bridge according to the S-VLAN filtering table. Egress When the data frames leave the bridge through the C-aware port, the S-VLAN tag is stripped. 1. The entry detection is performed for the data frames according to the C-VLAN tag. 2. The corresponding S-VLAN tags are added to the data frames according to the mapping relation between the C-VLAN tags and the S-VLAN tags of the data frames (a). If the mapping relation does not exist, the data frames are discarded. 3. After the data frames enter the bridge, the data frames are forwarded in the bridge according to the S-VLAN filtering table. Egress When the data frames leave the bridge through the C-aware port, the S-VLAN tag is stripped.
Data frames that contain a CVLAN tag
Add S-VLAN Base for Port and C-VLAN
Ingress
NOTE
a:
The same C-aware port supports the mapping of different C-VLAN tags to the same S-VLAN tag. For example, the data frames whose C-VLAN IDs are 1, 2, and 3 can be added with the same S-VLAN tag whose ID is 100. The same C-aware port supports the mapping of different C-VLAN tags to different S-VLAN tags. For example, the data frames whose C-VLAN IDs are 1, 2, and 3 can be added with the S-VLAN tags whose IDs are 100, 200, and 300 respectively. The same C-aware port does not support the mapping of the same C-VLAN tag to different S-VLAN tags at the same time. For example, the data frame whose C-VLAN ID is 1 cannot be added with the S-VLAN tags whose IDs are 100, 200, and 300 at the same time.
Issue 02 (2009-02-25)
22-9
22 QinQ
LAN Services That Enter and Exit the S-Aware Port

Table 22-6 lists the applications of the LAN services that enter and exit the S-aware port. Table 22-6 LAN services that enter and exit the IEEE 802.1ad bridge through the S-aware port Type of Data Frame Data frames that contain an SVLAN tagb Operation Type Mount Port Direction Ingress Description 1. The data frames that enter the bridge through the S-aware port are not filtered. 2. After the data frames enter the bridge, the data frames are forwarded in the bridge according to the S-VLAN filtering table. Egress When the data frames leave the bridge through the S-aware port, the data frames are transparently transmitted. 1. The entry filtering is performed according to the preset S-VLAN tag. The data frames that do not belong to the S-VLAN are discarded. 2. After the data frames enter the bridge, the data frames are forwarded in the bridge according to the S-VLAN filtering table. Egress When the data frames leave the bridge through the S-aware port, the data frames are transparently transmitted.
Mount Port and Base for Port and S-VLAN
Ingress
NOTE
b:
The data frame that enters the S-aware port must contain an S-VLAN tag. Otherwise, the port discards the data frame.
22.3 Availability
The QinQ technology is applicable to the Ethernet private line service and the Ethernet LAN service.
22-10
Issue 02 (2009-02-25)
22 QinQ
Table 22-7 Availability of the QinQ feature Feature EVPL (QinQ) EVPLAN (IEEE 802.1ad bridge) Applicable Board EMS6 (all the versions) Applicable Equipment IDU 620

The QinQ technology is applied to the Ethernet line service and LAN service of the Ethernet switching board.
Relation with Other Features

QinQ is applied to the Layer 2 Switching, namely, the EVPLAN (802.1ad bridge) service.

The attributes of QinQ packets are closely related to the port attributes and service type.
Realization of QinQ in the Ethernet Line Service

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

This section, using the EVPLAN (802.1ad bridge) service illustrated in Figure 22-5 as an example, describes how data frames are processed on the 802.1ad bridge. Figure 22-5 Example of the EVPLAN (802.1ad bridge) service
NE1 VoIP NE3
PORT1 VCTRUNK1
Node B1
PORT1
Service C-VLAN 10 VoIP 20 HSI
HSI
PORT2
NE2
VCTRUNK2
Node B2
PORT1
Service C-VLAN VoIP 30 HSI 40

NE1 PORT1 Node B1
NE3:EMS6 S-VLAN 100 PORT1 VoIP S-VLAN 200 PORT2 HSI VCTRUNK1
VCTRUNK2
NE2 PORT1
Node B2
802.1ad bridge PORT Strip S-VLAN Label C-VLAN(10/30) Data(VoIP) C-VLAN(20/40) Data(HSI) Add S-VLAN Label S-VLAN(100) S-VLAN(200) C-VLAN(10/30) Data(VoIP) C-VLAN(20/40) Data(HSI) VCTRUNK Strip S-VLAN Label C-VLAN(10/30) Data(VoIP) C-VLAN(20/40) Data(HSI)
As shown in Figure 22-5, the transmission network needs to carry the voice over IP (VoIP) service and the high speed Internet (HSI) service. The VoIP service and the HSI service of Node B1 and Node B2 that are connected to NE1 and NE2 respectively use different C-VLANs that have been planned. To mark and schedule the VoIP service and the HSI service in a unified manner on the aggregation node NE3, on the transmission network the planned S-VLAN tags are added to the two types of services from the user side.
22 QinQ
On the network, NE3 processes the data frames as follows: 1. 2. 3. 4. The VoIP service and the HSI service of Node B1 and Node B2 are transparently transmitted to NE3 through NE1 and NE2 respectively. NE3 adds S-VLAN tag 100 to the VoIP service of Node B1, Node B2, and VoIP server (with the C-VLANs 10 and 30). NE3 adds S-VLAN tag 200 to the HSI service of Node B1, Node B2, and HSI server (with the C-VLANs 20 and 40). After these data frames carrying the S-VLAN tag enter the 802.1ad bridge, the Layer 2 switching is performed according to the Ethernet port specified in the S-VLAN filtering table. When the data frames carrying the S-VLAN tag leave the bridge from the corresponding port due to being forwarded, the S-VLAN tag is removed.
22.6 Planning Guide

Plan related parameters according to the specific application of the QinQ feature. 22.6.1 EVPL Services Based on QinQ Plan related parameters according to the specific application of the QinQ technology in the EVPL service. 22.6.2 EVPLAN Services Based on the IEEE 802.1ad Bridge Plan related parameters according to the application of the QinQ technology in the LAN services.
22.6.1 EVPL Services Based on QinQ

Plan related parameters according to the specific application of the QinQ technology in the EVPL service.
Prerequisite
You must have understood the specific applications of the QinQ feature.
Procedure
Step 1 Plan the network attributes of the ports according to the actual requirements. Adhere to the following principles when planning the network attributes of the ports:
l
If packets need to be forwarded according to C-VLAN tags or C-VLAN tags need to be translated, select the line services between C-aware ports. If S-VLAN tags need to be added/stripped, select the line services between a C-aware port and an S-aware port. If packets need to be forwarded according to S-VLAN tags or S-VLAN tags need to be translated, select the line services between S-aware ports.
Step 2 Select a QinQ operation type according to the actual requirements. Adhere to the following principles when planning the QinQ operation type:
l
Check whether operations are based on ports, based on ports + C-VLAN, or based on ports + S-VLAN.
Issue 02 (2009-02-25)
22 QinQ
l
Check whether unidirectional operations or bidirectional operations are required.
Step 3 Allocate S-VLAN tags for customers. Adhere to the following principles when planning S-VLAN tags:
l l
The S-VLAN tag allocated to each customer must be unique. If a customer requires multiple S-VLAN tags, allocate a section of consecutive S-VLAN tags to the customer. For example, allocate 100109 to customer a and 110119 to customer b.
----End
Example
The following describes how to plan QinQ line services. The QinQ services illustrated in Figure 22-4 are provided as an example. The ports used in this example are shown in Figure 22-6. Figure 22-6 Ports used by the QinQ line services
PORT1
NE1
Service network A NE2 NE3 Service network B VCTRUNK1 NE4 PORT1
PORT2
VCTRUNK1 VCTRUNK1 VCTRUNK2 VCTRUNK2
VCTRUNK1
PORT2
1.
Plan the network attributes of the ports. In the case of NE1 and NE4, plan the network attribute of the related PORTs as C-Aware and the network attribute of the related VCTRUNKs as S-Aware because NE1 and NE4 need to add/remove S-VLAN tags. In the case of NE2 and NE3, plan the network attribute of the related VCTRUNKs as SAware because NE2 and NE3 need to forward packets according to S-VLAN tags.
2.
Plan QinQ operation types. In the case of NE1 and NE4, select the bidirectional "Add S-VLAN" operation because NE1 and NE4 can forward all the packets based on ports and do not need to recognize the packet type. In the case of NE2, select the bidirectional "Transparently transmit S-VLAN" operation because NE2 needs to transparently transmit packets according to S-VLAN tags. In the case of NE3, select the bidirectional "Translate S-VLAN" operation because NE3 needs to translate S-VLAN tags according to S-VLAN tags and does not translate S-VLAN tags based on ports.
3.
Plan S-VLAN tags.
22-14
Issue 02 (2009-02-25)
22 QinQ
Plan S-VLAN tags on an overall basis. The S-VLAN tags allocated to customer a and customer b by service provider A are 100 and 110 respectively, and the S-VLAN tags allocated to customer a and customer b by service provider B are 200 and 210 respectively.
22.6.2 EVPLAN Services Based on the IEEE 802.1ad Bridge

Plan related parameters according to the application of the QinQ technology in the LAN services.
Prerequisite
You must be familiar with the specific application of the QinQ feature.
Procedure
Step 1 Plan the network attributes of the ports that are mounted to the IEEE 802.1ad bridge according to the actual requirements. Adhere to the following principles when planning the network attributes of the ports:
l
If the packets that enter the port do not contain a VLAN tag or contain a C-VLAN tag, plan the network attribute of the port as C-Aware. If the packets that enter the port contain an S-VLAN tag, plan the network attribute of the port as S-Aware.
Step 2 Select a QinQ operation type according to the actual requirements. Adhere to the following principles when planning the QinQ operation type:
l
In the case of the C-aware port, select "Add S-VLAN Base for Port" or "Add S-VLAN Base for Port and C-VLAN". For details, refer to Table 22-5. In the case of the S-aware port, select "Mount Port" or "Mount Port and Base for Port and S-VLAN". For details, refer to Table 22-6.
Step 3 Allocate S-VLAN tags to customers or service types. Adhere to the following principles when planning S-VLAN tags:
l l
The S-VLAN tag allocated to each customer or each service type must be unique. If a customer or service type requires multiple S-VLAN tags, allocate a section of consecutive S-VLAN tags to the customer or service type. For example, allocate S-VLAN tags 100109 to customer A or service type A (for example, VoIP services), and allocate S-VLAN tags 110119 to customer B or service type B (for example, HSI services).
----End
Example
This topic considers the EVPLAN services (IEEE 802.1ad bridge) that are illustrated in Figure 22-5 as an example to describe the planning method. 1. Plan the network attributes of the ports. Plan the network attributes of PORT1, PORT2, VCTRUNK1, and VCTRUNK2 as CAware because NE3 needs to add and strip S-VLAN tags. Plan the network attributes of the related PORTs as UNI because NE2 and NE3 need to transparently transmit the services.
22 QinQ
2.
Plan QinQ operation types. Planning NE3 is more complicated than planning NE1 and NE2. Port PORT1 PORT2 VCTRUNK1 Accessed Service VoIP services HSI services VoIP services of node B1 (CVLAN 10) HSI services of node B1 (CVLAN 20) VCTRUNK2 VoIP services of node B2 (CVLAN 30) HSI services of node B2 (CVLAN 40) In the case of NE1 and NE2, you need not plan QinQ operation types because NE1 and NE2 transparently transmit the Ethernet services. Add S-VLAN Base for Port and C-VLAN Planned Operation Type Add S-VLAN Base for Port Add S-VLAN Base for Port Add S-VLAN Base for Port and C-VLAN
3.
Plan S-VLAN tags. Plan S-VLAN tags on an overall basis. The S-VLAN tag allocated to the VoIP services (CVLAN IDs being 10 and 30) is 100 and the S-VLAN tag allocated to the HSI services (CVLAN IDs being 20 and 40) is 200 on the transport network side.

This topic describes the configuration flow and the corresponding configuration tasks of the QinQ line service. An example is provided as additional information to help understand the configuration. 22.7.1 Configuration Flow (EVPL Services Based on QinQ) This topic describes the configuration flow of the EVPL service that is based on QinQ. 22.7.2 Configuration Flow (EVPLAN Services Based on the IEEE 802.1ad Bridge) This topic describes the configuration flow of the EVPLAN service that is based on the 802.1ad bridge. 22.7.3 Modifying the Type Field of QinQ Frames By default, the type field (that is, the TPID in an S-TAG) of QinQ frames processed by Ethernet switching boards is set to "0x8100". 22.7.4 Creating QinQ Line Services To enable the Ethernet switching board to transmit QinQ line services, perform this task to configure the related information such as service source and service sink. 22.7.5 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge To enable the Ethernet switching board to transmit the EVPLAN services that are based on the IEEE 802.1ad bridge, you need to create the bridge, set the attributes of the bridge, select the ports that are mounted to the bridge, and select the operation type.
22-16
Issue 02 (2009-02-25)
22 QinQ
22.7.1 Configuration Flow (EVPL Services Based on QinQ)

This topic describes the configuration flow of the EVPL service that is based on QinQ. Figure 22-7 Configuration flow for the QinQ line service
Start
Is the type field of QinQ frames processed by the interconnected equipment set to "0x8100"? No Modify the type field of QinQ frames
Yes
Configure the external port of the Ethernet board
Configure the internal port of the Ethernet board
4 Create QinQ line services 5
Create cross-connections for Ethernet services
End
Table 22-8 Description of the configuration flow of the QinQ line service Number 1 2 Description For the configuration flow, see 22.7.3 Modifying the Type Field of QinQ Frames. For the configuration flow, see 17.7.1 Configuring External Ethernet Ports.
Issue 02 (2009-02-25)
22-17
22 QinQ
Number 3 4 5
Description For the configuration flow, see 18.7 Configuring the Internal Port of the Ethernet Board. For the configuration flow, see 22.7.4 Creating QinQ Line Services. Create the cross-connection from the paths that are bound to the VCTRUNK to the corresponding timeslots on the line.
NOTE
To configure the QoS feature for the QinQ line service, see 21 QoS.
22.7.2 Configuration Flow (EVPLAN Services Based on the IEEE 802.1ad Bridge)
This topic describes the configuration flow of the EVPLAN service that is based on the 802.1ad bridge.
22-18
Issue 02 (2009-02-25)
22 QinQ
Figure 22-8 Configuration flow for the EVPLAN service that is based on the 802.1ad bridge
Start
Is the type field of QinQ frames processed by the interconnected equipment set to "0x8100"? No 1 Modify the type field of QinQ frames
Yes
2 Configure the external port of the Ethernet board 3 Configure the internal port of the Ethernet board 4 Create the EVPLAN services based on IEEE 802.1ad bridge 5 Create the VLAN filter table 6 Modify the Hub/Spoke attribute of the port mounted to a bridge 7
Create cross-connections for Ethernet services
End
Table 22-9 Description of the configuration flow of the EVPLAN service that is based on the 802.1ad bridge Number 1 Description For the configuration process, see 22.7.3 Modifying the Type Field of QinQ Frames.
Issue 02 (2009-02-25)
22 QinQ
Number 2 3 4 5 6
Description For the configuration process, see 17.7.1 Configuring External Ethernet Ports. For the configuration process, see 18.7 Configuring the Internal Port of the Ethernet Board. For the configuration process, see 22.7.5 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge. For the configuration process, see 20.7.3 Creating the VLAN Filter Table. For the configuration process, see 20.7.2 Modifying the Mounted Port of a Bridge. If the communication between ports needs to be isolated, you need to set the Hub/Spoke attribute to "Spoke". In this case, Step 6 is required.
Create the cross-connection from the paths that are bound to the VCTRUNK to the corresponding timeslots on the line.
NOTE
l l
To configure the Layer 2 switching feature for the EVPLAN services that are based on the IEEE 802.1ad bridge, see 20 Layer 2 Switching. To configure the QoS feature for the EVPLAN services that are based on the IEEE 802.1ad bridge, see 21 QoS.
22.7.3 Modifying the Type Field of QinQ Frames

By default, the type field (that is, the TPID in an S-TAG) of QinQ frames processed by Ethernet switching boards is set to "0x8100".
Prerequisite
Precautions
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Advanced Attributes > QinQ Type AreaSettings from the Function Tree. Step 2 Modify the type field of QinQ frames.
22-20
Issue 02 (2009-02-25)
22 QinQ
Parameters
Parameter QinQ Type Area (Hexadecimal) Value Range 81 00, 98 A8, 91 00 Default Value 81 00 Description This parameter specifies the type field of QinQ frames. Set this parameter according to the type field of the accessed QinQ frames.
22.7.4 Creating QinQ Line Services

To enable the Ethernet switching board to transmit QinQ line services, perform this task to configure the related information such as service source and service sink.
Prerequisite
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Select Display QinQ Shared Service. Step 3 Click New. The system displays the Create Ethernet Line Service dialog box. Step 4 Set the attributes of the Ethernet line service.
Issue 02 (2009-02-25)
22-21
22 QinQ
Step 5 Optional: Set the port attributes of the source port and sink port.
NOTE
The result of configuring the port attributes during the Ethernet line service configuration process is the same as the result of directly configuring the Ethernet service port attributes.
Parameters
Parameter Service Type Value Range EPL, EVPL(QinQ) Default Value EPL Description When creating the QinQ line service, set this parameter to EVPL(QinQ).
22-22
Issue 02 (2009-02-25)
22 QinQ
Parameter Direction
Value Range Unidirectional, Bidirectional
Default Value Bidirectional
Description
l
When this parameter is set to Unidirectional, only the service from the service source to the service sink is created. When this parameter is set to Bidirectional, both the service from the service source to the service sink and the service from the service sink to the service source are created. Generally, it is recommended that you use the default value. For the meanings of the values, see 22.2.3 Application of the QinQ Technology in Line Services. Set this parameter according to actual situations.
Operation Type
Transparently transmit C-VLAN, Translate C-VLAN, Add S-VLAN, Transparently transmit S-VLAN, Translate S-VLAN, Strip S-VLAN (only for unidirectional services) A specific PORT or VCTRUNK
Add S-VLAN
Source Port
PORT1
This parameter indicates the port where the service source resides. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific PORT as the source port. You can set this parameter to null, a number, or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "" to indicate continuous numbers. For example, "1, 36" indicates numbers 1, 3, 4, 5, and 6. The number of C-VLANs set in this parameter should be the same as the number of C-VLANs set in Sink CVLAN (e.g. 1,3-6). When you set this parameter to null, all the services of the source port work as the service source. When you set this parameter to a non-null value, only the services of the source port whose C-VLAN IDs are included in the set value range of this parameter work as the service source.
Source C-VLAN (e.g. 1,3-6)
1 to 4095
Issue 02 (2009-02-25)
22-23
22 QinQ
Parameter Source S-VLAN
Default Value -
Description
l
This parameter must be set to a numerical value. Only the services of the source port whose S-VLAN IDs are equal to the value of this parameter work as the service source. This parameter indicates the port where the service sink resides. Do not set the value of this parameter to the same as the value of Source Port. When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific VCTRUNK as the sink port. You can set this parameter to null, a number, or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "" to indicate continuous numbers. For example, "1, 36" indicates numbers 1, 3, 4, 5, and 6. The number of VLANs set in this parameter should be the same as the number of VLANs set in Source CVLAN (e.g. 1,3-6). When you set this parameter to null, all the services of the sink port work as the service sink. When you set this parameter to a non-null value, only the services of the sink port whose C-VLAN IDs are included in the set value range of this parameter work as the service sink. This parameter must be set to a numerical value. Only the services of the sink port whose S-VLAN IDs are equal to the value of this parameter work as the service sink.
Sink Port
PORT1
Sink C-VLAN (e.g. 1,3-6)
1 to 4095
Sink S-VLAN
1 to 4095
22-24
Issue 02 (2009-02-25)
22 QinQ
Parameter S-VLAN Priority
Value Range AUTO, Priority0 Priority7
Default Value AUTO
Description
l
This parameter is valid only when Operation Type is set to Add SVLAN. This parameter specifies the priority of the newly added S-VLAN tag. When this parameter is set to AUTO, the priority of the S-VLAN tag is 0. When QoS operations do not need to be performed according to the S-VLAN priority, it is recommended that you use the default value.
Port Enabled
Enabled, Disabled
When the source port or the sink port is set to a PORT, set Port Enabled to Enabled.
22.7.5 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge
To enable the Ethernet switching board to transmit the EVPLAN services that are based on the IEEE 802.1ad bridge, you need to create the bridge, set the attributes of the bridge, select the ports that are mounted to the bridge, and select the operation type.
Prerequisite
Precautions
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Click New. The Create Ethernet LAN Service dialog box is displayed. Step 3 Set the attributes of the IEEE 802.1ad bridge.
Issue 02 (2009-02-25)
22-25
22 QinQ
Step 4 Configure service mounting relations. 1. 2. 3. Click Configure Mount. Set the parameters for configuring mounted services. Click Add Mount Port.
4. 5.
Repeat Step 4.2 to Step 4.3 to add the other mount ports. Click OK.
Step 5 Optional: If any VCTRUNK is mounted to the VB, configure the VC paths that are bound to the VCTRUNK. 1. 2. 3. 4. Click Configuration. The Bound Path Configuration dialog box is displayed. In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select the required items in Available Resources and Available Timeslots and click . 5. Optional: Repeat Step 5.4 to bind other VC paths.
22-26
Issue 02 (2009-02-25)
22 QinQ
NOTE
The result of setting the port attributes during the configuration of the private network service is consistent with the result of directly setting the attributes of the Ethernet service port.
6.
Click OK.
----End
Parameters
Parameter VB Name Value Range Default Value Description This parameter is a string that describes the bridge. It is recommended that you set this string to a value that contains the specific purpose of the bridge.
l
VB Type
802.1q, 802.1d, 802.1ad
802.1q
In this example, the IEEE 802.1d bridge and IEEE 802.1q bridge need not be created. Hence, do not set VB Type to 802.1d or 802.1q.
Issue 02 (2009-02-25)
22-27
22 QinQ
Parameter Bridge Switch Mode
Value Range IVL/Ingress Filter Enable SVL/Ingress Filter Disable
Default Value IVL/Ingress Filter Enable
Description
l
When the bridge uses the SVL mode, all the VLANs share one MAC address table. When the bridge uses the IVL mode, all the VLANs correspond to their respective MAC address tables. If the ingress filter is enabled, the VLAN tag is checked at the ingress port. If the VLAN ID is not equal to the VLAN ID of the port defined in the VLAN filtering table, the packet is discarded. If the ingress filter is disabled, the preceding described check is not conducted.
Operation Type
Add S-VLAN Base for Port Add S-VLAN Base for Port and CVLAN Mount Port Mount Port and Base for Port and SVLAN
Add S-VLAN Base for Port
For the meaning of each operation type, see 22.2.4 Application of the QinQ Technology in LAN Services.
VB Port Mount Port
This parameter specifies the ID of the logical port of the bridge. Select the external physical port or internal VCTRUNK port of the Ethernet switching board that is mounted to the IEEE 802.1ad bridge. This parameter is valid only when Operation Type is set to Add S-VLAN Base for Port and C-VLAN. This parameter specifies the mapping relation between the C-VLAN tag carried by the data frame and the S-VLAN tag to be added.
C-VLAN
14095
22-28
Issue 02 (2009-02-25)
22 QinQ
Parameter S-VLAN
Value Range 14095
Default Value -
Description
l
When Operation Type is set to Add SVLAN Base for Port, this parameter specifies that the data frames that enter the IEEE 802.1ad bridge need to be added with the S-VLAN tag. When Operation Type is set to Add SVLAN Base for Port and C-VLAN, this parameter and C-VLAN specify the mapping relation between the S-VLAN tag to be added and the C-VLAN tag carried by the data frame that enters the IEEE 802.1ad bridge. When Operation Type is set to Mount Port, this parameter is invalid. When Operation Type is set to Mount Port and Base for Port and S-VLAN, this parameter specifies the S-VLAN tag to be carried by the data frames that enter the IEEE 802.1ad bridge.
Configurable Ports
Mount each VCTRUNK of the port.
Issue 02 (2009-02-25)
22-29
22 QinQ
Value Range -
Default Value -
Description Adhere to the following principles when planning and setting this parameter:
l
The capacity of VCTRUNKs should be determined by the actual bandwidth of the service needs. Bind only the paths in a VC-4 if possible. If the paths of several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Hence, when a VCTRUNK needs to be bound with VC-3 paths, select VC-3 paths first from the VC-4 certain of whose VC-3 paths are already bound; when a VCTRUNK needs to be bound with VC-12 paths, select VC-12 paths first from the VC-4 certain of whose VC-12 paths are already bound. The VC-4-1s of the EMS6 board support only VC-3 paths, whereas the VC-4-2s of the EMS6 board support both VC-12 paths and VC-3 paths. Hence, give priority to the paths in the VC-4-1 if a VCTRUNK needs to be bound with VC-3 paths. Generally, bidirectional paths are bound.
22.8 Configuration Example (EVPL Services Based on QinQ)

This topic provides an example to describe how to configure QinQ line services.
Precautions
NOTE
For details on the services configured in this example, see the description of the EVPL service that is based on QinQ in 22.6.1 EVPL Services Based on QinQ.
Procedure
Step 1 Set the attributes of the ports of NE1 and NE4. For details, see 17.7.1 Configuring External Ethernet Ports. Step 2 Set the attributes of the VCTRUNKs of NE1NE4. For details, see 18.7 Configuring the Internal Port of the Ethernet Board.
22 QinQ
Step 3 Configure a QinQ service from PORT1 to VCTRUNK1 of NE1. For details, see 22.7.4 Creating QinQ Line Services. Set the parameters as follows:
l l l l l l l
Set Direction to Bidirectional. Set Operation Type to Add S-VLAN. Set Source Port to PORT1. Do not set Source C-VLAN (e.g. 1,3-6). Set Sink Port to VCTRUNK1. Do not set Sink C-VLAN (e.g. 1,3-6). Set Sink S-VLAN to 100.
Step 4 Configure a QinQ service from PORT2 to VCTRUNK1 of NE1. For details, see 22.7.4 Creating QinQ Line Services. Set the parameters as follows:
l l l l l l l
Set Direction to Bidirectional. Set Operation Type to Add S-VLAN. Set Source Port to PORT2. Do not set Source C-VLAN (e.g. 1,3-6). Set Sink Port to VCTRUNK1. Do not set Sink C-VLAN (e.g. 1,3-6). Set Sink S-VLAN to 110.
Step 5 Configure the QinQ services of NE4. For details, see Steps Step 3Step 4. Step 6 Configure the QinQ service to which the traffic stream of customer a at NE2 corresponds. For details, see 22.7.4 Creating QinQ Line Services. Set the parameters as follows:
l l l l l l
Set Direction to Bidirectional. Set Operation Type to Transparently transmit S-VLAN. Set Sink Port to VCTRUNK1. Set Source S-VLAN to 100. Set Sink Port to VCTRUNK2. Set Sink S-VLAN to 100.
Step 7 Configure the QinQ service to which the traffic stream of customer b at NE2 corresponds. For details, see 22.7.4 Creating QinQ Line Services. Set the parameters as follows:
l l l l
Set Direction to Bidirectional. Set Operation Type to Transparently transmit S-VLAN. Set Sink Port to VCTRUNK1. Set Source S-VLAN to 110.
Issue 02 (2009-02-25)
22 QinQ
l l
Set Sink Port to VCTRUNK2. Set Sink S-VLAN to 110.
Step 8 Configure the QinQ service to which the traffic stream of customer a at NE3 corresponds. For details, see 22.7.4 Creating QinQ Line Services. Set the parameters as follows:
l l l l l l
Set Direction to Bidirectional. Set Operation Type to Translate S-VLAN. Set Source Port to VCTRUNK2. Set Source S-VLAN to 100. Set Sink Port to VCTRUNK1. Set Sink S-VLAN to 200.
Step 9 Configure the QinQ service to which the traffic stream of customer b at NE3 corresponds. For details, see 22.7.4 Creating QinQ Line Services. Set the parameters as follows:
l l l l l l
Set Direction to Bidirectional. Set Operation Type to Translate S-VLAN. Set Source Port to VCTRUNK2. Set Source S-VLAN to 110. Set Sink Port to VCTRUNK1. Set Sink S-VLAN to 210.
22.9 Configuration Example (EVPLAN Services Based on the IEEE 802.1ad Bridge)
This topic considers an example to describe how to configure the EVPLAN services that are based on the IEEE 802.1ad bridge.
Precautions
NOTE
For details on the services configured in this example, refer to the example described in 22.6.2 EVPLAN Services Based on the IEEE 802.1ad Bridge. The following configuration flow is based on the configuration of services on convergence node NE3.
Procedure
Step 1 Set Network Attributes of PORT1 and PORT2 of the Ethernet switching board of NE3 to CAware. For details, see 17.7.1 Configuring External Ethernet Ports.
22 QinQ
Step 2 Set Network Attributes of VCTRUNNK1 and VCTRUNK2 of the Ethernet switching board of NE3 to C-Aware. For details, see 18.7 Configuring the Internal Port of the Ethernet Board. Step 3 Configure the EVPLAN services that are based on the IEEE 802.1ad bridge for NE3. For details, see 22.7.5 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge. Set the parameters for the IEEE 802.1ad bridge as follows:
l l l l l
Set VB Name to VB1. Set VB Type to 802.1ad. Set Bridge Switch Mode to IVL\Ingress Filter Enable. Bridge Learning Mode is set to IVL automatically. Ingress Filter is set to Enabled automatically.
Set the parameters for service mounting as follows: Parameter Operation Type VB Port Mount Port C-VLAN S-VLAN Parameter Value Add S-VLAN Base for Port 1 PORT1 100 2 PORT2 200 Add S-VLAN Base for Port and CVLAN 3 VCTRUNK1 10 100 20 200 4 VCTRUNK2 30 100 40 200
Step 4 Create the VLAN filtering table. For details, see 20.7.3 Creating the VLAN Filter Table. Set the parameters for the VLAN filtering table of the VoIP services as follows:
l l
Set VLAN ID to 100. Select the corresponding forwarding ports, including PORT1, VCTRUNK1, and VCTRUNK2.
Set the parameters for the VLAN filtering table of the HSI services as follows:
l l
Set VLAN ID to 200. Select the corresponding forwarding ports, including PORT2, VCTRUNK1, and VCTRUNK2.

This topic describes the alarms and performance events relevant to the QinQ feature, and the problems that occur frequently during the application of the QinQ feature. 22.10.1 Relevant Alarms and Events
22 QinQ
The QinQ feature may cause changes in RMON performance. 22.10.2 FAQs This topic lists the problems that occur frequently during the application of the QinQ feature.

The QinQ feature may cause changes in RMON performance.
Relevant Alarms
None.

None.

22.10.2 FAQs
This topic lists the problems that occur frequently during the application of the QinQ feature. Q: Why does the interconnection of QinQ line services with the equipment of other vendors fail? A: Common causes are as follows:
l
The QinQ type field (that is, the TPID in an S-TAG) varies between the equipment of different vendors. The OptiX equipment uses "0x8100". The standards for the QinQ feature are being developed. The principles for adding tags are different between vendors.
22-34
Issue 02 (2009-02-25)
23 Remote Monitoring Feature
23
About This Chapter
Remote Monitoring Feature
The remote 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. 23.1 Feature Description The RMON feature is based on the management information base (MIB) in the architecture of the simple network management protocol (SNMP). Through the RMON function, you can monitor the performance of the Ethernet port as you monitor the performance of the SDH/PDH port. 23.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the RMON feature. 23.3 Availability The RMON feature requires the support of the applicable equipment and boards. 23.4 Relation with Other Features As a basic function of the Ethernet board, the RMON function does not have impact on other Ethernet features. The other Ethernet features, however, have impact on the performance data of the RMON function. In addition, the port on the device that supports the hybrid microwave feature supports the RMON function. 23.5 Realization Principle The RMON agent is embedded in an Ethernet board. The Web LCT server or T2000 server functions as the NMS. The NMS exchanges data information with the agent through basic SNMP commands. Thus, the statistical network data is collected. 23.6 Planning Guide Plan related parameters according to the specific application of the RMON function. 23.7 Configuration Guide The RMON function need not be configured and can be directly used. 23.8 Maintenance Guide
Issue 02 (2009-02-25)
23-1
This topic describes how to use the RMON function and describes the problems that occur frequently during the application of the RMON function.
23-2
Issue 02 (2009-02-25)

The RMON feature is based on the management information base (MIB) in the architecture of the simple network management protocol (SNMP). Through the RMON function, you can monitor the performance of the Ethernet port as you monitor the performance of the SDH/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. Therefore, the RMON should provide the following functions:
l
Storage of statistical data at the agent end; offline operations on the network management station (NMS) History data storage This facilitates fault diagnosis. Error detection and reporting Multiple management stations
l l
To implement the preceding functions, the RMON defines a series of statistical formats and functions to realize the data exchange between the control stations and detection stations that comply with the RMON standards, and thus to implement management on the Ethernet port. The RMON provides flexible detection modes and control mechanisms to meet the requirements of different networks. Furthermore, the RMON provides the function of error diagnosis of the entire network, and the functions of planning and receiving of the performance events. The RMON complies with RFC 1757 and RFC 2819.
23.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the RMON feature. 23.2.1 SNMP Currently, the 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, diagnose a fault, plan capacity, and generate a report on any node in the network. 23.2.2 RMON Management Groups The Ethernet board provides the following RMON management groups specified in IETF RFC2819: statistics group, history group, alarm group, and history control group. 23.2.3 RMON Alarms and Performance Events RMON events include RMON alarms and RMON events.
23.2.1 SNMP
Currently, the 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, diagnose a fault, plan capacity, and generate a report on any node in the network.
Architecture of the SNMP

The SNMP is divided into the network management station (NMS) and the agent.
l
NMS The NMS is a workstation where the client program runs. When the RMON function is used, the Web LCT or T2000 server functions as the NMS.
Agent The agent is the server software that runs on the network equipment. When the RMON function is used, the agent is embedded in the Ethernet board.
The NMS can send the GetRequest, GetNextRequest, or SetRequest packet to the agent. After receiving such a request packet, the agent reads or writes the packet according to the type of the packet, generates the Response packet, and sends the Response packet to the NMS. 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 OptiX RTN 600 can be connected to a wide variety of equipment without a block.
MIB
In SNMP packets, managed variables 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.
23.2.2 RMON Management Groups

The Ethernet board provides the following RMON management groups specified in IETF RFC2819: statistics group, history group, alarm group, and history control group.
Statistics Group
The statistics group counts the absolute performance values from the time the statistics group is created until the current time. The Ethernet board supports port-based statistics groups. In the case of a board, you can create a statistics group for only one port. The sampling interval of a statistics group can be set. The value range of the sampling interval is from 1 second to 100 seconds. For the performance entries that can be added to a statistics group, see 23.2.3 RMON Alarms and Performance Events.
23-4
Issue 02 (2009-02-25)
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 board supports port-based alarm groups. You can create only one alarm group for a board. The number of alarm entries in an alarm group 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, see 23.2.3 RMON Alarms and Performance Events.
History Control Group

The history control group specifies the methods of monitoring history performance data. The Ethernet board 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 board. 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 board 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 board 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 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.
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 performance entries that can be added into a statistics group.
Issue 02 (2009-02-25)
23-5

l
Query conditions This specifies the relative time to which the history performance data corresponds. 1 represents the oldest item. You can query a maximum of ten entries at a time.
23.2.3 RMON Alarms and Performance Events

RMON events include RMON alarms and RMON events. Table 23-1 RMON alarms(IDU 610/620) Alarm Name DropEvent UndersizePkts OversizePkts Fragments Jabbers FCSErrors Description Number of packet loss events exceeding the threshold Number of undersized packets exceeding the threshold Number of oversized packets exceeding the threshold Number of fragment packets exceeding the threshold Number of jabber packets exceeding the threshold Number of packets with FCS errors exceeding the threshold EMS6 and EFT4 Source EMS6, EFT4, and IFH2
Table 23-2 RMON alarms(IDU 605) Alarm Name DropEvent FCSErrors Description Number of packet loss events exceeding the threshold Number of packets with FCS errors exceeding the threshold Source EMS4
Table 23-3 RMON performance events(IDU 610/620) Performa nce Category Basic performanc e Performance Name Source
Packets received (packets) Packets received (64 bytes in length) (packets) Packets received (65127 bytes in length) (packets)
EMS6, EFT4, and IFH2
23-6
Issue 02 (2009-02-25)
Performa nce Category
Performance Name
Source
Packets received (128255 bytes in length) (packets) Packets received (256511 bytes in length) (packets) Packets received (5121023 bytes in length) (packets) Packets received (10241518 bytes in length) (packets) Packet loss events (times) Bytes received (bytes) Oversized packets received (packets) Undersized packets received (packets) Multicast packets received (packets) Broadcast packets received (packets) Undersized error packets received (packets) Collisions (times) Fragments received (packets) Oversized error packets received (packets) FCS and alignment error packets (packets) Extended performanc e Packets transmitted (64 bytes in length) (packets) Packets transmitted (65127 bytes in length) (packets) Packets transmitted (128255 bytes in length) (packets) Packets transmitted (256511 bytes in length) (packets) Packets transmitted (5121023 bytes in length) (packets) Packets transmitted (10241518 bytes in length) (packets)
IFH2 EMS6 and EFT4
EFT4 EMS6, EFT4, and IFH2
Performance Name
Source
Packets received and transmitted (64 bytes in length) (packets) Packets received and transmitted (65 127 bytes in length) (packets) Packets received and transmitted (128255 bytes in length) (packets) Packets received and transmitted (256511 bytes in length) (packets) Packets received and transmitted (5121023 bytes in length) (packets) Packets received and transmitted (10241518 bytes in length) (packets) Unicast packets transmitted (packets) Pause frames received (frames) Pause frames transmitted (frames) FCS error frames (frames) Oversized packets transmitted (packets) Packets transmitted (packets) Bytes transmitted (bytes) Packets received (1519 bytes to the MTU in length) (packets) Packets transmitted (1519 bytes to the MTU in length) (packets) Packets received and transmitted (1519 bytes to the MTU in length) (packets) Transmitting packet loss events (packets) Unicast packets received (packets) Multicast packets transmitted (packets) Broadcast packets transmitted (packets) EMS6 and EFT4 IFH2
23-8
Issue 02 (2009-02-25)
Performance Name
Source
Rate of good full-frame bytes received (bytes/second) Rate of good full-frame bytes transmitted (bytes/second) Good full-frame bytes received (bytes) Good full-frame bytes transmitted (bytes) Control frames received (frame) Control frames transmitted (frame) Alignment error frames (frame) Frames properly transmitted after only one collision (frame) Frames properly transmitted after multiple collisions (frame) Late collisions (times) Frames unsuccessfully transmitted after successive collisions (frame) Delayed frames (frame) VCG performanc e Full-frame bytes received (bytes) Full-frame bytes transmitted (bytes) Packets received (packets) Packets transmitted (packets) Good packets received (packets) Good packets transmitted (packets) Rate of good full-frame bytes received (bytes/second) Rate of good full-frame bytes transmitted (bytes/second) EMS6
Issue 02 (2009-02-25)
23-9
Table 23-4 RMON performance events(IDU 605) Performa nce Category Basic performanc e Performance Name Source
Packets received (64 bytes in length) (packets) Packets received (65127 bytes in length) (packets) Packets received (128255 bytes in length) (packets) Packets received (256511 bytes in length) (packets) Packets received (5121023 bytes in length) (packets) Packets received (10241518 bytes in length) (packets) Packet loss events (times) Multicast packets received (packets) Broadcast packets received (packets) Undersized packets received (packets) Oversized packets received (packets) Bytes received (bytes) Packets received (packets) Fragments received (packets) Oversized error packets received (packets) Collisions (times)
EMS4
Extended performanc e
Packets transmitted (64 bytes in length) (packets) Packets transmitted (65127 bytes in length) (packets) Packets transmitted (128255 bytes in length) (packets) Packets transmitted (256511 bytes in length) (packets)
EMS4
23-10
Issue 02 (2009-02-25)
Performance Name
Source
Packets transmitted (5121023 bytes in length) (packets) Packets transmitted (10241518 bytes in length) (packets) Packets received and transmitted (64 bytes in length) (packets) Packets received and transmitted (65 127 bytes in length) (packets) Packets received and transmitted (128255 bytes in length) (packets) Packets received and transmitted (256511 bytes in length) (packets) Packets received and transmitted (5121023 bytes in length) (packets) Packets received and transmitted (10241518 bytes in length) (packets) Unicast packets transmitted (packets) Pause frames received (frames) Pause frames transmitted (frames) FCS error frames (frames) Oversized packets transmitted (packets) Packets transmitted (packets) Bytes transmitted (bytes) Unicast packets received (packets) Multicast packets transmitted (packets) Broadcast packets transmitted (packets) Rate of good full-frame bytes received (bytes/second) Rate of good full-frame bytes transmitted (bytes/second) Good full-frame bytes received (bytes)
Performance Name
Source
Good full-frame bytes transmitted (bytes) Control frames received (frames) Control frames transmitted (frames) Alignment error frames (frames) Frames properly transmitted after only one collision (frames) Frames properly transmitted after multiple collisions (frames) Late collisions (times) Frames unsuccessfully transmitted after successive collisions (frames) Delayed frames (frames)
NOTE
The ports of the EMS6, EFT4, and IFH2 boards support the basic performance and the extended performance. The VCTRUNK of the EMS6 board supports the VCG performance. The VCTRUNK of the EFT4 board, however, does not support the RMON performance.The ports and the IFUP of the IDU 605 1F/2F support the basic performance and the extended performance.
23.3 Availability
The RMON feature requires the support of the applicable equipment and boards. Table 23-5 Availability of the RMON Feature Feature RMON Applicable Board EFT4 (all the versions) EMS6 (all the versions) IFH2 (all the versions) Applicable Equipment IDU 610/620 IDU 620 IDU 620 IDU 605 1F/2F
23-12
Issue 02 (2009-02-25)

NOTE
l l l l
The EFT4 board supports the RMON of PORTs only. The EMS6 board supports the RMON of PORTs and VCTRUNK. The IFH2 board supports the RMON of PORTs only. The IDU 605 1F/2F board supports the RMON of PORTs and IFUP.

As a basic function of the Ethernet board, the RMON function does not have impact on other Ethernet features. The other Ethernet features, however, have impact on the performance data of the RMON function. In addition, the port on the device that supports the hybrid microwave feature supports the RMON function.

The RMON agent is embedded in an Ethernet board. The Web LCT server or T2000 server functions as the NMS. The NMS exchanges data information with the agent through basic SNMP commands. Thus, the statistical network data is collected.
Statistics Group
The processing flow is as follows: 1. 2. 3. A maintenance engineer clicks Resetting begins. The NMS sends the corresponding request packet to the RMON agent. The RMON agent embedded in the Ethernet board resets the corresponding current performance counting register and returns the corresponding response packet to the NMS according to the information of the statistics group in the request packet. The NMS sends a request packet to the RMON agent at sampling intervals. 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 processing flow is as follows: 1. 2.
Issue 02 (2009-02-25)
The maintenance engineer clicks Apply. The NMS sends the corresponding request packet to the RMON agent.
3. 4. 5.
The RMON agent embedded in the Ethernet board monitors the corresponding alarm object according to the information of the alarm group in the request packet. When the alarm object crosses the 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 processing flow is as follows: 1. 2. 3. The maintenance engineer clicks Apply. The NMS sends the corresponding request packet to the RMON agent. The RMON agent embedded in the Ethernet board periodically counts the performance value of the monitored object and stores the performance value in the corresponding history performance register according to the information of the history control group in the request packet.
History Group
The processing flow 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 board queries the history performance registers that meet the requirements and returns the performance values in the registers to the NMS through the response packet according to the information of the history group in the request packet.
23.6 Planning Guide

Plan related parameters according to the specific application of the RMON function.
Prerequisite
l l
You must have an understanding of the functions of the RMON management groups. You must have an understanding of the meanings of the statistical items.
Procedure
Step 1 Select proper RMON management groups according to the actual requirements. Adhere to the following principles when selecting RMON management groups:
l
When you need to monitor the current performance of a port in real time, select the statistics group. When you need to monitor certain performance items of a port in the long term, select the alarm group. When you need to perform a statistical analysis on the performance of a port over a past period of time, select the history group and history control group.
23-14
Step 2 Select proper statistical items. Adhere to the following principles when selecting statistical items:
l
When you need to analyze the exceptions that occur on a port, select the following statistical items: fragments, undersize packets received, FCS errors, pause frames received, pause frames transmitted, and others. When you need to analyze the traffic on a port, select the following statistical items: octets received, octets transmitted, and others. When you need to analyze the information on packet transmitting and packet receiving on a port, select the following statistical items: packets received, packets transmitted, and others. When you need to analyze the types of the transmitted and received packets on a port, select the following statistical items: unicast packets received, unicast packets transmitted, multicast packets received, multicast packets transmitted, broadcast packets received, broadcast packets transmitted, and others.
----End

The RMON function need not be configured and can be directly used.

This topic describes how to use the RMON function and describes the problems that occur frequently during the application of the RMON function. 23.8.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. 23.8.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. 23.8.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. 23.8.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. 23.8.5 FAQs This topic lists the problems that occur frequently during the application of the RMON function.
23.8.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port
After you configure an RMON statistics group for an Ethernet port, you can browse the realtime statistical performance data of the port.
Prerequisite
The Ethernet board must be included in the slot layout. You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher.
Procedure
Step 1 Select the Ethernet board 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
Parameters
Parameter Sampling Interval Display Accumulated Value Value Range 5 seconds to 150 seconds Selected, Not selected Default Value 5 Not selected Description This parameter specifies the period of sampling the performance data. This parameter specifies whether the displayed performance value is the increment of the register value compared with the register value at the end of the previous sampling interval or the current absolute value of the register.
23.8.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
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Performance > RMON Performance from the Function Tree.
Step 2 Click the Alarm Group tab. Step 3 Set the required parameters for the alarm group. Step 4 Click Apply. ----End
Parameters
Parameter Sampling Interval (s) Report Mode Value Range 5 to 150 Report All, Report in Case of Upper ThresholdCrossing, Report in Case of Lower Threshold-Crossing 1 to 4294967295 0 to 4294967294 Enabled, Disabled Default Value 5 Report All Description This parameter specifies the period of sampling the performance data. This parameter specifies the mode in which an alarm event is reported when the performance data crosses a threshold.
Upper Threshold Lower Threshold Monitor Status
1 0 Disabled
This parameter specifies the upper threshold for the performance data. This parameter specifies the lower threshold for the performance data. This parameter specifies whether to monitor the alarm object.
23.8.3 Configuring a History Control Group

When configuring a history control group for an Ethernet port, you configure how the history performance data of the port is monitored. The Ethernet board monitors the history performance data of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50 history performance data items.
Prerequisite
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the History Control Group tab. Step 3 Set the required parameters for the history control group.
Parameters
Parameter History Table Type Value Range 30-Second, 30Minute, Custom Period1, Custom Period2
l
Default Value 30-Second
Description This parameter specifies the period of sampling the history performance data.
Sampling Interval (s)
30043200 (custom period 1) 30086400 (custom period 2)
900 (custom period 1) 86400 (custom period 2)
This parameter is valid only when History Table Type is set to Custom Period1 or Custom Period2. This parameter specifies the period of sampling the performance data. This parameter specifies the number of performance data items. This parameter specifies whether to monitor the object.
Number of Items Monitor Status
1 to 50 Enabled, Disabled
50 Disabled
23.8.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
The Ethernet board must be included in the slot layout. You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The monitored objects and the corresponding history table type must be set in the History Control Group tab.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the History Group tab. Step 3 Set the required parameters for the history group. Step 4 Click Query. ----End
Parameters
Parameter History Table Type Value Range 30-Second, 30Minute, Custom Period1, Custom Period2 1 to 50 Default Value 30-Second Description This parameter specifies the period of sampling the history performance data.
Start Item
This parameter specifies the item from which the system queries the history performance data. 1 represents the oldest item. This parameter specifies the item after which the system stops querying the history performance data. The value of this parameter must not be more than the sum of Start Item and 9.
End Item
1 to 50
23.8.5 FAQs
This topic lists the problems that occur frequently during the application of the RMON function. Q: How does one use the statistical items obtained by using the RMON function? A: The statistical items obtained by using the RMON function are primarily applied in the following scenarios:
l
Analyzing the exceptions that occur on a port Focus on the following statistical items that indicate exceptions:
Fragments Generally, a mismatch between working modes causes the occurrence of fragments. Fragments occur most commonly when the working mode at one end is set to autonegotiation but the working mode at the other end is set to full-duplex.
Undersized packets received When undersized packets occur, first check whether the port modes match each other, then check the quality of 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.
Oversize packets received Generally, the setting of the maximum frame length to a very small value causes the occurrence of oversize packets.
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.
Pause frames received and pause frames transmitted

Issue 02 (2009-02-25)
When pause frames occur, first check whether the flow control function is correctly set, and then adjust the service traffic or perform traffic shaping to prevent the traffic on ports from being controlled.
Alignment errored frames If the AligErrOv performance event occurs, check whether the packets transmitted from the peer contain errored code by using the tester. If errored code exists, rectify the fault in the peer first. After the fault in the peer is rectified, check whether the local end reports the alarms such as ETH_LOS and errored code, which are caused by great attenuation or damage of external lines. At last, check whether the board reports the alarms such as HARD_BAD, which indicates the board or chip fault.
Analyzing the information on packet transmitting and packet receiving on each port of a service For example, when two PORTs share one VCTRUNK to provide a line service, you can count the packets received on the two PORTs and compare the total number of the received packets with the number of the packets transmitted by the VCTRUNK to determine whether packet loss occurs.
Analyzing the traffic on a port For example, in the case of a transparently transmitted service from a PORT to VCTRUNK, you can count the bytes received and the bytes transmitted on the PORT and compare the number of the bytes with the bandwidth of the VCTRUNK to determine whether the bandwidth bound to the VCTRUNK is proper.
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 received packets and calculate the ratio of the broadcast packets to the received packets to determine whether broadcast storm occurs on the peer equipment.
23-20
Issue 02 (2009-02-25)
24 ETH OAM
24
About This Chapter
ETH OAM
Ethernet OAM detects and monitors the connectivity and performance of the trails of services by using outband packets. Therefore, services are not affected. 24.1 Feature Introduction Ethernet OAM enhances the Ethernet Layer 2 maintenance to strongly support the service continuity verification, service deployment commissioning and network fault locating. The Ethernet board provides complete Ethernet OAM solutions according to the standards that are defined in the IEEE 802.1ag and IEEE 802.3ah protocols. 24.2 Basic Concept This topic describes certain basic concepts required for the application of Ethernet OAM features. 24.3 Availability The ETH-OAM feature requires the support of the applicable equipment and boards. 24.4 Relations with Other Features Ethernet OAM does not affect other Ethernet features. 24.5 Function Implementation Ethernet OAM realizes different OAM operations through different OAM packets. 24.6 Planning Guide When the IEEE 802.1ag OAM protocol is used, you need to plan maintenance points (MPs) according to services. When the IEEE 802.3ah OAM protocol is used, you can directly perform the desired OAM operations without planning MPs. 24.7 Using the IEEE 802.1ag OAM By using the IEEE 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner. 24.8 IEEE 802.1ag OAM Example Different maintenance points (MPs) are configured according to different Ethernet services. 24.9 Using the IEEE 802.3ah OAM By using the IEEE 802.1ag OAM, you can maintain the Ethernet link in a point-to-point manner. 24.10 Maintenance Guide
24 ETH OAM
This topic describes the alarms and performance events relevant to the ETH-OAM feature, and the problems that occur frequently during the application of the ETH-OAM feature.
24-2
Issue 02 (2009-02-25)
24 ETH OAM
24.1 Feature Introduction

Ethernet OAM enhances the Ethernet Layer 2 maintenance to strongly support the service continuity verification, service deployment commissioning and network fault locating. The Ethernet board provides complete Ethernet OAM solutions according to the standards that are defined in the IEEE 802.1ag and IEEE 802.3ah protocols. As a protocol based on the MAC layer, Ethernet OAM checks Ethernet links by transmitting OAM protocol packets. Compared with the transmission medium, this protocol is independent. The OAM packets are processed only at the MAC layer, having no impact at other layers in the Ethernet. Moreover, as a low-rate protocol, the Ethernet OAM protocol occupies low bandwidth. Thus, this protocol does not affect services carried on the link. Compared with the traditional Ethernet maintenance and fault location, the features of Ethernet OAM are as follows:
l l
As a low rate protocol, the Ethernet OAM protocol uses very little network bandwidth. Hence, this function does not affect services transmitted by the link. You can perform the OAM on the services that are encapsulated in different formats by using the Ethernet OAM, which is irrelevant to the Ethernet encapsulation formats. You can perform the OAM, however, on only the services of the same encapsulation format by using traditional test frames. The current frame test method is based on only the encapsulation format where the data of the same type is contained. Thus, this test method is not applicable to other encapsulation formats (such as GFP encapsulation format and HDLC encapsulation format) where the data of different types is contained. The current port loopback function focuses on all packets at the port. Thus, the loopback cannot be performed for a specific service selectively. Ethernet OAM can detect hardware faults. Ethernet OAM can detect and locate faults automatically.
l l l
The OptiX RTN equipment provides the Ethernet OAM solution based on the IEEE 802.1ag and IEEE 802.3ah protocols, as shown in Figure 24-1. Figure 24-1 Ethernet OAM solution
IEEE 802.3ah IEEE 802.1ag IEEE 802.3ah
Transmission Network
Client-side Ethernet Equipment RTN Equipment
Issue 02 (2009-02-25)
24-3
24 ETH OAM
IEEE 802.1ag OAM focuses on the maintenance of end-to-end Ethernet links. Based on services, IEEE 802.1ag OAM realizes the end-to-end check by detecting each maintenance domain successively. That is, it performs segmental management on each network segment that is involved in the same service in the network. IEEE 802.3ah OAM focuses on the point-to-point Ethernet link maintenance between two sets of directly-connected equipment in Ethernet in the first mile (EFM). 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, fault check, remote loopback and selfloop check.
24.2 Basic Concept

This topic describes certain basic concepts required for the application of Ethernet OAM features. 24.2.1 IEEE 802.1ag OAM Management IEEE 802.1ag OAM focuses on the maintenance of the end-to-end Ethernet links. By defining the maintenance domain (MD), maintenance association (MA), and maintenance point (MP), IEEE 802.1ag OAM can manage service flows by segment and by layer. 24.2.2 IEEE 802.1ag OAM Operation The Ethernet board supports the IEEE 802.1ag Ethernet OAM operations as follows: continuity check (CC), link trace (LT), loopback (LB), ping, alarm indication signal (AIS) activation, and performance check. 24.2.3 IEEE 802.3ah OAM Operations The Ethernet board supports the IEEE 802.3ah Ethernet OAM operations as follows: OAM autodiscovery, link event notification, error frame monitoring, remote loopback, and self-loop test.
24.2.1 IEEE 802.1ag OAM Management

IEEE 802.1ag OAM focuses on the maintenance of the end-to-end Ethernet links. By defining the maintenance domain (MD), maintenance association (MA), and maintenance point (MP), IEEE 802.1ag OAM can manage service flows by segment and by layer. As a protocol based on the MAC layer, the Ethernet service OAM detects Ethernet links by transmitting OAM packets. The OAM packets are processed at only the MAC layer. The Ethernet service OAM defines the following concepts.
l l
Maintenance domain (MD): The MD is a network that requires the OAM. Maintenance association (MA): The MA can be considered as a service-related domain, which consists of many maintenance end points (MEPs) and Maintenance intermediate points (MIPs). Maintenance point (MP): The MP include MEPs and MIPs.
Maintenance end point (MEP): The MEP is the transmitting and terminating points of all OAM packets. It is relevant to services. In a network, the MA and MEP ID can uniquely determine an MEP. Maintenance intermediate point (MIP): For the non-standard protocol, the MIP can respond to and forward LB and LT packets, but can only forward CC packets. For the
24-4
24 ETH OAM
standard protocol, the MIP can forward CC and LB packets, but respond to and forward LT packets.
Maintenance Domain
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. 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 the collection of all maintenance points (MP) in a service application. The MPs include the maintenance association end points (MEP) and maintenance association intermediate points (MIP). For the management segment to be maintained, establish MEPs at two 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, including MEPs and MIPs. Based on relations and responses among these maintenance points, the state of the whole management segment is under control. In this way, the fault detection and location are realized.
Maintenance Association
An MA is a part of an MD. An MD can be divided into one MA or multiple MAs. In the network of a carrier, a VLAN is corresponding to a service instance. On the equipment, a VLAN is corresponding to an MA or multiple MAs. By dividing MAs, you can check the connectivity of the network that transmits a certain service instance and detect faults of the network. The level of an MA is the same as the level of the MD to which the MA belongs.
Maintenance Point
The maintenance point (MP) refers to function entity of IEEE 802.1ag OAM, including the maintenance end point (MEP) and maintenance intermediate point (MIP). Each maintenance point has a maintenance point identification (MPID), and this ID is unique in the entire network. The information of each maintenance point is recorded in the MAC address table, maintenance point table and route table. The key contents contained in the MP configuration information are the service type, service ID and VLAN tag. In the case of nonstandard MP, once a maintenance point is created successfully, it transmits the protocol packets where the MP information is contained to the entire network periodically in the form of broadcasting. After receiving these protocol packets, other maintenance points record the information for backup.
l
Maintenance association End Points The MEP defines the start position of the maintenance domain. The MEP is the transmitting and terminating points of all OAM packets. It is relevant to services. In a network, the MA and MEP ID can uniquely determine an MEP. As shown in Figure 24-2, the MEP is always marked by an arrow. The direction of arrow indicates the direction of the MEP. An MEP has following features.
It must allow all service packets to pass through the point, neglecting their directions.
Issue 02 (2009-02-25)
24 ETH OAM
It must check all OAM message packets that pass through the MEP in the direction of the arrow.
It allows the OAM message packets whose levels are higher than the level of this MEP layer to pass through the point directly without further check. It terminates all message packets whose levels are lower than or equals to the level of this MEP layer.
It must check all OAM message packets that pass through this MEP in the reverse direction of the arrow.
It allows the OAM message packets whose levels are higher than the level of this MEP layer to pass through the point directly without further check. It processes the OAM message packets that belong to this MEP layer. It terminates all message packets whose levels are lower than the level of this MEP layer.
It generates the OAM message packets whose level is equal to the MEP level at this layer, and transmits these packets in the specified direction.
Maintenance association Intermediate Points As shown in Figure 24-2, the MIP is always marked by an ellipse. Moreover, the MIP has no direction. An MIP should have following features.

It must allow all service packets to pass through this MIP. It must check all OAM message packets that pass through this MIP. It must allow the OAM message packets whose levels are higher than the level of this MEP layer to pass through the MIP. According to some special operational codes or destination MAC addresses, choose one of the following processing methods.

Transparent transmission Transparent transmission and processing Extract and process all OAM message packets that belong to this MIP layer
According to some special operational codes, discard all OAM message packets whose level is lower than the level of this MIP layer.
NOTE
Only the MEP can initiate the OAM operations, while the MIP cannot initiate any OAM operation or send any OAM packet.
Layered Management
IEEE 802.1ag OAM adds the management level fields to OAM protocol packets. In this way, 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. Moreover, the management of different service traffics can be realized as well. Figure 24-2shows the logical diagram of the maintenance domain layer relation.
24-6
Issue 02 (2009-02-25)
24 ETH OAM
Figure 24-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. Eight maintenance entities (ME) levels correspond to the user, supplier or operator accordingly. In the case of non-standard MP (Huawei MP)
l l l
ME levels for the user: 0, 1, 2 ME levels for the supplier: 3, 4 ME levels for the operator: 5, 6, 7
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 for maintenance points at different layers to process OAM protocol packets are as follows.
l
For the OAM protocol packets whose level is higher, the maintenance point processes them transparently. For the OAM protocol packets whose level is lower, the maintenance point discards them directly. For the OAM protocol packets whose level is the same, the maintenance point gives response or ends the packets accordingly to messages types of the OAM protocol packets.
24.2.2 IEEE 802.1ag OAM Operation

The Ethernet board supports the IEEE 802.1ag Ethernet OAM operations as follows: continuity check (CC), link trace (LT), loopback (LB), ping, alarm indication signal (AIS) activation, and performance check.
24 ETH OAM
Continuity Check
The connectivity between maintenance end points (MEPs) are detected through continuity check messages (CCMs) that are transmitted between MEPs periodically. This detection is named as continuity check (CC). You can check the link status in one direction by performing the CC. The application scenario is as follows: The link status is checked in real time.
l
After receiving the CCM packets from the source MEP, the sink MEP directly enables the CC function that focuses on this source MEP. If the sink MEP fails to receive the CCM packets from the source MEP within a check period, the non-standard MP reports the EX_ETHOAM_CC_LOS alarm automatically until the link is recovered, and the standard MP reports the ETH_CFM_LOS alarm. That is, the sink MEP does not clear the alarm until it receives the CCM packets from the sink MEP.
Loopback Test
The loopback (LB) can be used to test the state of any MP link from the source MEP to the maintenance domain. The application scenario is as follows: The location or check is performed on one end.
l
The loopback (LB) can be used to test the state of any node link from the source to the maintenance domain. For the non-standard MP, as the sink MP can be the MIP, the loopback can be used to locate the faults. Compared with the continuity test, the loopback test is not a continuous test. Thus, you need start the test manually each time.
Link Trace Test

Compared with the LB test, the link trace (LT) test provides enhanced fault locating capability. That is, the faulty network segment can be located the first time in the LT test. The application scenario is as follows: The fault is located on site.
PING
OAM ping test provides the online test. By using this function, you can simulate the packet loss ratio and delay period of a service, which are caused by bit errors. Besides the continuity test, the OAM-Ping test further manages the performance of the Ethernet link at the MAC layer. The application scenario is as follows: The service performance is checked in real time.
l
The OMA_Ping test provides a method to test the in-service packet loss ratio and hold-off time that result from bit errors. Compared with the continuity test, the OAM_Ping test provides more detailed and accurate OAM information. In this case, the OAM not only ensures the service continuity, but also detects the packet loss and service delay to a greater extent.
AIS Activation
The alarm indication signal (AIS) is used to report errors to a superstratum node during Ethernet OAM. When the AIS is active, errors can be reported. If the AIS is inactive, errors cannot be reported.
24 ETH OAM
Performance Check
After the connectivity between the MPs of the processing boards of Ethernet services is checked, the performance check realizes the on-line test of the packet loss ratio and delay time of the services.
24.2.3 IEEE 802.3ah OAM Operations

The Ethernet board supports the IEEE 802.3ah Ethernet OAM operations as follows: OAM autodiscovery, link event notification, error frame monitoring, remote loopback, and self-loop test.
OAM Auto-Discovery
By exchanging the information OAM protocol data unit (OAMPDU) periodically, the equipment at local end is informed that the opposite end supports the IEEE 802.3ah OAM protocol. The application scenario is as follows: OAM auto-discovery is a prerequisite to realize the link performance monitoring and remote loopback. The following functions are available at the port only when the OAM auto-discovery succeeds: link performance monitoring and loopback. If the OAM auto-discovery fails, the ETHOAM_DISCOVER_FAIL alarm is reported.
Link Performance Monitoring

Link performance monitoring is used to monitor the bit error performance (error frames or error signals). When the local end detects that the bit errors cross the threshold, the bit error event is transmitted to the opposite end over the specified OAMPDU. In this case, the opposite end reports the alarm accordingly. To perform performance statistics from different aspects, the link performance monitoring is classified into bit error frame event monitoring, error frame second event monitoring, error frame period event monitoring.
l
Triggering condition of error frame events: Within a period of the error frame monitor window, the number of actually received error frames is larger than the configured threshold value.
NOTE
The period of the error frame monitor window indicates the time period for each error frame statistics.
l
Triggering condition of error frame second events: Within the specific seconds, the detected error frame seconds is larger than defined threshold value.
NOTE
When the error frame number is larger than 0 within a second, this second is called an error frame second.
l
Triggering condition of error frame period events: Among the received frames of a specific amount, the number of error frames is larger than defined threshold value.
Application scenarios are as follows:

l
The link performance monitoring function is used to precisely analyze and monitor the link performance within a specific range. According to actual requirements, you can configure window values and threshold values of three link performance events respectively on the Web LCT. In this case, whether the link performance degrades to the threshold can be detected.
Issue 02 (2009-02-25)
24 ETH OAM
Remote Loopback
The OAM entity at the local end transmits the loopback control OAMPDU packets to the remote OAM for applying for the loopback. According to loopback data analysis, the fault locating and link performance test are performed. The IDU 620 do not support responding the remote loopback, the IDU 605 support responding the remote loopback. The application scenario is as follows: The loopback is a method to locate the faults and test the performance. Compare the number of transmitted packets with that of received packets in loopback. The result can be used to detect link performance and link faults in this link bidirectionally from the loopback initiation end to the loopback response end.
Self-Loop Test
After the self-loop test function is enabled on an Ethernet service processing board, you can detect the self-loop that occurs when the fiber in the transmit direction of a port is connected to the same port in the receive direction, and the intra-board loopback between two connected port on the same board. The application scenario is as follows: When the self-loop function is enabled at all ports on the equipment, the ring network that is available during the networking can be detected. Moreover, the ETHOAM_SELF_LOOP alarm is reported.
24.3 Availability
The ETH-OAM feature requires the support of the applicable equipment and boards. Table 24-1 Availability of the ETH-OAM Feature Feature IEEE 802.1ag ETHOAM IEEE 802.3ah ETHOAM Applicable Board EMS6 (all the versions) EMS6 (all the versions) Applicable Equipment IDU 620 IDU 605 1F/2F IDU 620 IDU 605 1F/2F
24.4 Relations with Other Features

Ethernet OAM does not affect other Ethernet features.
24.5 Function Implementation

Ethernet OAM realizes different OAM operations through different OAM packets. 24.5.1 802.1ag OAM When the IEEE 802.1ag OAM protocol is used, OAM operations are realized through the exchange of OAMPDUs between MPs. 24.5.2 802.3ah OAM
24 ETH OAM
When the IEEE 802.3ah OAM protocol is used, OAM operations are realized through the exchange of OAMPDUs between the equipment at both ends of a link.
24.5.1 802.1ag OAM

When the IEEE 802.1ag OAM protocol is used, OAM operations are realized through the exchange of OAMPDUs between MPs. Figure 24-3 shows the IEEE 802.1ag OAMPDU. Figure 24-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
l l l l l
OAM Mac destination address: Indicates the MAC address of the destination MP. 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. The standard IEEE The packet type of 802.1ag OAM protocol is 0x8902. The non-standard (Huawei, Draft 3.0)IEEE The packet type of 802.1ag OAM protocol is 0x8809. OAM type: Indicates that the MP differs and responds to various OAM operations according to types of OAM packets. OAM For mapping relation between values and OMA packet types, refer to Table 24-2. Table 24-2 Mapping relation between values and OMA packet types (non-standard MP) OAM Type 1 2 3 OAMPDU Loopback message (LBM) Link trace message (LTM) Continuity check message (CCM)
Usage Loopback test Link trace test Continuity test

24-11
Issue 02 (2009-02-25)
24 ETH OAM
OAM Type 4 5 6 7 8
OAMPDU MAC query Loopback return (LBR) Link trace reply (LTR) MacAck MacBroadcast
Usage MAC address query Loopback test Link trace test MAC address confirmation notification MAC address broadcast
Continuity Check
The source MEP constructs the continuity check message (CCM) packets and transmits them periodically. After receiving the CCM packets from the source MEP, the sink MEP directly enables the CC function that focuses on this source MEP. If the sink MEP fails to receive the CCM packets from the source MEP within a check period, it reports the alarm automatically until the link is recovered. That is, the sink MEP does not clear the alarm until it receives the CCM packets from the sink MEP. As shown inFigure 24-4, the CC function of the MEP1 is enabled. The MEP1 transmits the CCM packets externally. After receiving the first CCM packet, the MEP2, MEP3 and MEP4 in the same maintenance domain start the timer respectively to receive all CCM packets from the MEP1 periodically. Once the link is faulty, the sink MEP fails to receive the CCM packets within a check period. In this case, the sink MEP reports the EX_ETHOAM_CC_LOS alarm. The alarm is not cleared until the link is recovered. Figure 24-4 Continuity check diagram
MEP1
VB
MEP2 MEP4 VB VB MEP3
When the CC function is enabled at MEP1, MEP2, MEP3 and MEP4 at the same time, each MEP is both the source end and sink end for the CC function. In this way, the bidirectional continuity test is realized.
NOTE
Only the MEP can enable the continuity check and be the receive respond end for the check.
24-12
Issue 02 (2009-02-25)
24 ETH OAM
Loopback Test
Based on the bidirectional service, the loopback is a test performed manually at a time. The source MEP constructs the loopback message (LBM) packets and adds the destination MP (MIP or MEP) IDs to the packets. When the packets are transmitted, the timer is started. After receiving the LBM packets, the sink MP constructs the loopback return (LBR) packets and transmits them back to the source MEP. In this case, the loopback succeeds. If the source MEP timer expires and fails to receive the LBR from the sink MP, the loopback fails. As shown in Figure 24-5, the MEP1 transmits the LBM packets to the sink MEP2. After receiving the packets, the MIP2 and MIP3 in the same maintenance domain detect that the sink MPIDs contained in the packets are different from those of them. In this case, the MIP2 and MIP3 transparently transmit the packets. After receiving the packets, the sink MEP2 transmits the LBR packets back to the source MEP1. At this moment, the loopback is complete. Figure 24-5 Loopback test diagram
MEP1
MIP2 LBM LBR
MIP3
MEP4
NOTE
For the non-standard IEEE 802.1ag OAM, only the MEP can initiate the loopback test, while both the MEP and MIP can be the receive end in the test.
Link Trace Test

The source MEP constructs the link trace message (LTM) packets and adds the ID of the sink MEP to the packets for transmission. At the same time, the timer is started. All MIPs that belong to this maintenance domain in the link continuously transmit the packets to the sink MEP. At the same time, a link trace replay (LTR) packet is transmitted back to the source MEP. After the sink MEP receives the LTM packets, the packet transmission is complete. Then the sink MEP transmits LTR packets back to the sink. In this case, the link trace test is successful. If the source MEP timer expires and fails to receive the LTR from the sink MEP, the loopback fails. Additionally, the parameter hop is added to the packet that is transmitted back. The hop is used to indicate the MP ID of the returned maintenance point in the link during the link trace test. If the first MP passed through the LTM is on the same board with the source MP, the hop starts from 0 and accumulates in the sequence. Otherwise, the hop starts from 1.
24 ETH OAM
The function of the link trace test is similar to the function of the loopback test. The difference lies in the response to the LBM frames. In the loopback test, only the sink MP responds to the LBM frames. In the link trace test, all MPs in the link respond to the LTM frames. According to these response messages, all MIPs that are involved from the source MEP to the destination MEP can be recognized, as shown in Figure 24-6. Figure 24-6 Link trace test diagram
MEP1
1
MIP2
MIP3
MEP4 LTR
4
LTM LTR LTM LTR
LTM
1. 2. 3. 4.
The source MEP1 transmits the LTM packets to the destination MEP4. After receiving the LTM packets, the MIP2 transmits the LTR packets to the source MEP1 and forwards the LTM packets at the same time. After receiving the LTM packets, the MIP3 transmits the LTR packets to the source MEP1 and forwards the LTM packets at the same time. After receiving the LTM packets, the destination MEP4 concludes the LTM packets and transmits the LTR packets to the source MEP1.
NOTE
Only the MEP can initiate the link trace test and be the termination of the test.
OAM_Ping Test
The OAM_Ping test includes:
l
MPID-Ping: In the case that both the Ethernet service processing boards of Huawei equipment at two ends support the IEEE 802.1ag OAM protocol, the ping test is initiated from the maintenance point on the local Ethernet service processing board to that on the opposite board. IP-Ping: In the case that both the equipment at two ends supports the ARP protocol and ICMP protocol, only the Huawei equipment can initiate the ping test. Moreover, the Huawei equipment does not respond to the ping test of the opposite end.
The transmit end in OAM_Ping acquires the IP address of the maintenance point first, and then constructs the ARP packets and ICMP packets for transmission. The maintenance point that receives the ARP packets or ICMP packets analyzes the packets and then transmits the response packets back to the transmit end. After receiving the response packets, the OAM_Ping transmit end reports the test results of the OAM_Ping according to the information contained in the response packets. The results include the packet loss ratio and delay information.
24 ETH OAM
24.5.2 802.3ah OAM

When the IEEE 802.3ah OAM protocol is used, OAM operations are realized through the exchange of OAMPDUs between the equipment at both ends of a link. Figure 24-7 shows IEEE 802.3ah OAMPDUs. Figure 24-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
Mac Destination Address: Indicates the low-speed protocol multicast address whose value is fixed to 0x01-80-C2-00-00-02. Mac Source Address: Indicates the MAC address of the port. Type: Indicates the low-speed protocol type whose value is fixed to 0x8809. Subtype: Indicates that the specified type of the low-speed protocol is IEEE 802.3ah OAM, which is fixed to 0x03. Flags Filed: Includes some important state information such as link fault, dying gasp, critical event. The realization of the fault locating 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 corresponding to OAM auto-discovery, link performance monitoring and remote loopback respectively. For the mapping relation between code values and OAM packet types, see Table 24-3.
l l l
Issue 02 (2009-02-25)
24-15
24 ETH OAM
Table 24-3 Mapping relation between code values and OAM packet types Code 0x00 0x01 OAMPDU Information Event notification Usage Exchanges the OAM information at the local end and opposite end. Notifies the opposite equipment that bit error performance events occur on the link. Applies for one or multiple specific MIB information. Responds to one or multiple specific MIB information. Enables or disables the remote OAM loopback. Reserved. Indicates the selective extended OAMPDU function used by different equipment manufacturers. Reserved.
0x02 0x03 0x04 0x05 0xFD 0xFE
Variable request Variable response Loopback control Reserved Organization specific
0xFF
l
Reserved
Data/Pad Field: Indicates the OAMPDU data whose fields can be extended, with a length range from 42 bytes to 1496 types. When the OAMPDU packet length is less than the minimum 64 bytes, the extended bytes are contained in the field. Frame check sequence
Auto-Discovery
As shown in Figure 24-8, the Code filed of the OAMPDU is 0x00. This indicates that the OAMPDU is the information OAMPDU and used for OAM auto-discovery.
24-16
Issue 02 (2009-02-25)
24 ETH OAM
Figure 24-8 Packet format of the information OAMPDU

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

1 1 1 2 Information Type Information Length OUI Organization Specific Value 0xFE
ORGANIZATION SPECIFIC INFORMATION TLV
The Data field of the information OAMPDU includes local information type-length-value (TLV) domain and remote information type-length-value (TLV) domain. A OAM configuration byte is contained in the TLV domain. When the link is normal, successful OAM auto-discovery depends on information of bit digits in the OAM configuration bytes. Also, the information of bit digits decides what functions are performed after OAM auto-discovery succeeds. Table 24-4 lists details of OAM configuration bytes.
Issue 02 (2009-02-25)
24-17
24 ETH OAM
Table 24-4 Details of OAM configuration bytes Bit Digit 7 to 5 Name Reserved Description Sets reserved bits to 0 when the OAMPDU is transmitted and ignores these bits in receiving.
l
Variable Retrieval
Sets the value to 1, which indicates that the data terminal equipment (DTE) supports the transmission of the variable response OAMPDU. Sets the value to 0, which indicates that the DTE does not support the transmission of the variable response OAMPDU. Sets the value to 1, which indicates that the DTE supports the monitoring on bit error performance (error frames or error signals) of links. When bit errors cross the threshold, the bit error event is transmitted to the opposite end over the specified OAMPDU. Sets the value to 0, which indicates that the DTE does not support the monitoring on bit error performance of links.
Link Events
24-18
Issue 02 (2009-02-25)
24 ETH OAM
Bit Digit 2
Name OAM Remote Loopback Support
Description
l
Sets the value to 1, which 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. Sets the value to 0, which indicates that the DTE does not support the remote loopback. Sets the value to 1, which indicates that the local end can transmit the OAMPDU packets to the local end when the fault occurs in the receive direction. Sets the value to 0, which indicates that the local end cannot transmit the OAMPDU packets to the local end when the route is faulty in the receive direction. Sets the value to 1, which indicates that the OAM mode of the DTE is set to Active. Sets the value to 0, which indicates that the OAM mode of the DTE is set to Passive. When the local end works in the passive mode, some OAM functions cannot be enabled. For details, see Table 24-5.
Unidirectional Support
OAM Mode
Issue 02 (2009-02-25)
24-19
24 ETH OAM
Table 24-5 Mapping relation between OAM working modes and OAM functions OAM Capability OAM Mode Active Mode Initiates OAM autodiscovery process Reacts to OAM autodiscovery process Required to send information OAMPDUs. Permitted to send event notification OAMPDUs Permitted to send variable request OAMPDUs Permitted to send variable response OAMPDUs Permitted to send loopback control OAMPDUs Reacts to loopback control OAMPDUs Permitted to send organization specific OAMPDUs Yes Yes Yes Yes Yes Yes Yes Yes Yes Passive Mode No Yes Yes Yes No Yes No Yes Yes
When the IEEE 802.3ah OAM protocol is enabled for the port on the Ethernet service processing board, the information OAMPDU is broadcast periodically. At the same time, the information OAMPDU from the opposite port is received and processed. In this way, two peer ends exchange the OAM information (including OAM configuration information and OAM state information) to establish the OAM connection between two ends.
Link Performance Monitoring

As shown in Figure 24-9 the Code filed of the OAMPDU is 0x01. This indicates that the OAMPDU is the event notification OAMPDU and used for notifying the bit error performance event mutually.
24-20
Issue 02 (2009-02-25)
24 ETH OAM
Figure 24-9 Packet format of event notification OAMPDU

Octets 2 1 1 2 8 8 8 8 4 Fields Sequence Number SEQUENCE NUMBER Event Type Event Length Event Time Stamp Errored Svmbol Window Errored Svmbol Threshol Errored Svmbol Error Running Total Event Running Total Fixed Values
0x01 0x28
Octets 6 6 2 1 2 1
Fields Destination Address Source Address Length/Type Subtype Flags Code
Fixed Values 01-80-c2-00-00-02
88-09 0x03
ERRORED SYMBOL PERIOD EVENT 1 Event Type 0x02 1 Event Length 0x1A 2 Event Time Stamp 2 Errored Frame Window 4 Errored Frame Threshol 4 Errored Frames 8 Error Running Total 4 Event Running Total 1 1 2 4 4 4 8 4 ERRORED FRAME ENENT Event Type 0x03 Event Length 0x1 Event Time Stamp C Errored Frame Window Errored Frame Threshol Errored Frames Error Running Total Event Running Total
0x01
42-1496 Data/Pad 4 FCS
ENENT NOTIFICATION OAMPDU
ERRORED FRAME PERIOD EVENT 1 Event Type 0x04 1 Event Length 0x12 2 Event Time Stamp 2 Err.Fr.Sec.Sum.Window 2 Err.Fr.Sec.Sum.Threshol 2 Err.Fr.Sec.Summary 4 Error Running Total 4 Event Running Total ERRORED FRAME SECONDS SUMMARY 1 Event Type 0xF 1 Event Length E 3 OUI x Organization Specific Value ORGANIZATION SPECIFIC EVENT
To perform performance statistics from different aspects, the link performance monitoring is classified into bit error event monitoring, error frame second event monitoring, error frame period event monitoring.
l
Triggering condition of error frame events: Within a period of the error frame monitor window, the number of actually received error frames is larger than the configured threshold value.
Issue 02 (2009-02-25)
24-21
24 ETH OAM
l
Triggering condition of error frame second events: Within the specific seconds, the detected error frame seconds is larger than defined threshold value. Triggering condition of error frame period events: Among the received frames of a specific amount, the number of error frames is larger than defined threshold value.
When the IEEE 802.3ah OAM protocol is enabled at a port, the protocol queries the RMON statistic count of the hardware chip periodically to acquire the information such as the number of accurate packets and the number of error packets. You can find out whether the preceding three performance events occur or not according to corresponding processing of these information. In the case that a performance event occurs, the opposite end is informed of this event over the event notification OAMPDU. After receiving the notification, the opposite equipment reports the ETHOAM_RMT_SD alarm for maintenance personnel to perform troubleshooting.
Remote Loopback
As shown in Figure 24-10, the code filed of the OAMPDU is 0x04. This indicates that the OAMPDU is the loopback control OAMPDU and used for the loopback test. Figure 24-10 Packet format of the loopback control OAMPDU
Octets 6 6 2 1 2 1 1+41 4 Fields Destination Address Source Address Length/Type Subtype Flags Code Data/Pad FCS 0x04 88-09 0x03 Octets 1 Fields Remote Loopback Command Fixed Values 0x01 Fixed Values 01-80-c2-00-00-02
ENABLE REMOTE LOOPBACK COMMAND

1 Remote Loopback Command 0x02
LOOPBACK CONTROL OAMPDU
DISABLE REMOTE LOOPBACK COMMAND
The loopback transmit end transmits the loopback control OAMPDU packets to the opposite end first. After receiving the packets, the opposite end checks whether it can respond to the remote loopback first. If it can respond to the remote loopback, the opposite end starts remote loopback and transmits a response packet back to the end that initiates the loopback at the same time. After receiving the response packets from the response end, the transmit end analyzes the packets to confirm that the opposite end is in the response loopback state. Then the transmit end starts the loopback. In this way, the whole process of loopback initiation is complete.
Self-Loop Test
The self-loop test is a function developed by Huawei on the basis of IEEE 802.3ah protocol.
24 ETH OAM
The self-loop test packets are constructed as the IEEE 802.3ah OAM protocol packets, with a packet type of protocol reservation type 6. The first eight significant reserved bits in the flag fields are used to carry the ID of the transmit port. When the self-loop test is enabled at a port, the specified self-loop check packets are transmitted from the port. One packet is transmitted each second. When a port receives the self-loop check packets, it compares the source MAC address carried in the packets with its own MAC address. If the former MAC address is the same with the later, it indicates that the local port and the opposite port are located in the same Ethernet service processing board. At this moment, further compare IDs of two ports. If the IDs are the same, they are the same port actually. In this case, this indicates the port self-loop. If the IDs are different, it indicates the intra-board port self-loop.
24.6 Planning Guide

When the IEEE 802.1ag OAM protocol is used, you need to plan maintenance points (MPs) according to services. When the IEEE 802.3ah OAM protocol is used, you can directly perform the desired OAM operations without planning MPs. 24.6.1 IEEE 802.1ag OAM When the IEEE 802.1ag OAM protocol is used, you need to plan OAM maintenance points (MPs) according the requirements of services and then select appropriate OAM operations. 24.6.2 IEEE 802.3ah OAM When the IEEE 802.3ah OAM protocol is used, you need to select appropriate OAM operation as required.
24.6.1 IEEE 802.1ag OAM

When the IEEE 802.1ag OAM protocol is used, you need to plan OAM maintenance points (MPs) according the requirements of services and then select appropriate OAM operations.
Prerequisite
You must learn about the functions of the IEEE 802.1ag OAM.
Procedure
Step 1 Create MPs as required. To select appropriated MPs, comply with the following principles:
l
An MP is created on the basis of a service flow. The MPs of the same level in a service flow form a maintenance domain (MD) so that the service flow can be maintained. When an MP is created, the MD to which the MP belongs is defined.

The MP ID must be unique in a network. The levels of the MPs in an MD must be the same.
During the OAM test, the MPs for a service flow must be within the same MD. In an existing MD for a certain service flow, if you create an MP of the same level or a higher level, the original MD is damaged and thus the OAM test fails.
Step 2 Optional: Select detection functions as required.

24 ETH OAM
OAM Type CC LB LT Ping test
Usage Checks the unidirectional continuity. Checks the directional continuity. Locates the fault. Checks the packet loss ratio and delay of the service between the Ethernet equipment and the datacom equipment Checks the packet loss ratio and delay of the service between the Ethernet equipment
Application Scenario Real-time link state check Fault locating or detecting at a single end On-site fault locating Real-time service performance check
Performance check
Real-time service performance check
----End
24.6.2 IEEE 802.3ah OAM

When the IEEE 802.3ah OAM protocol is used, you need to select appropriate OAM operation as required.
Prerequisite
You must learn about the functions of the IEEE 802.3ah OAM.
Procedure
Step 1 Plan the settings of the link event notification. After the auto-discovery succeeds, the protocol automatically monitors the link performance of the link. If Remote Alarm Support for Link Event is set to Enabled, when detecting that the error frames or error signals cross the threshold, the protocol sends a message about the link performance event to the opposite equipment. After receiving the message, the opposite equipment reports an alarm indicating the link performance event. If detecting a link cut in the receive direction of the local equipment, the protocol sends a message about the fiber cut to the opposite equipment. After receiving the message, the opposite equipment reports an alarm indicating the remote link fault. Step 2 Plan the settings of the remote loopback. To detect the link status from the local equipment to the opposite equipment, you can initiate the loopback operation at the local equipment. After the opposite equipment successfully responds to the loopback, the local equipment and the opposite equipment are in the Initiate Loopback at Local status and the Respond Loopback of Remote status respectively. At this time, you can send data services at a certain rate from the local equipment, and then check the RMON statistics of transmitted and received data services. By comparing the count of transmitted services and the count of received services, you can determine the link performance.

NOTE
24 ETH OAM
The RTN equipment can not respond the loopback applying of the OAM entity.
Step 3 Plan the settings of the self-loop detection. Enable the self-loop detection function for all the external physical ports on the local equipment. Step 4 Select appropriate OAM functions as required. Table 24-6 Application scenarios for various functions of IEEE 802.3ah OAM OAM Type Link performance monitoring Usage Detects the bit error performance (error frames or error signals) in the link on the receive side of the local equipment, and informs the opposite equipment of the faults. Detects faults on the local equipment and informs the opposite equipment of the faults. Locates fault points and tests the link performance. Detects the port loopback and board loopback. Application Scenario Monitoring link service performance in a real-time manner
Fault locating
Monitoring the faults on the opposite equipment in a realtime manner Locating problems on site Detecting the loopback
Remote loopback Self-Loop detection
----End
24.7 Using the IEEE 802.1ag OAM

By using the IEEE 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner. 24.7.1 Configuration Flow This topic describes the flow of configuring the IEEE 802.1ag OAM. 24.7.2 Creating MDs A maintenance domain (MD) defines the scope and level of the Ethernet OAM. The MDs of different levels and scopes can provide differentiated OAM services to users. 24.7.3 Creating MAs A maintenance domain (MD) can be divided into several independent maintenance associations (MA). By creating MAs, operators can associate specific Ethernet services with the MAs for easy Ethernet OAM operation. 24.7.4 Creating MPs The functions of the IEEE 802.1ag OAM can be used only after MPs are created. 24.7.5 Performing a Continuity Check After the continuity check (CC) test, the unidirectional link status can be checked automatically and periodically. After the CC test is started at the source, if the link is fault, the source equipment reports the EX_ETHOAM_CC_LOS(Huawei MP) or ETH_CFM_LOS(Standard MP) alarm.
24 ETH OAM
24.7.6 Performing a Loopback Check During a loopback (LB) check, you can check the bidirectional connectivity between the source MEP and any MP in the same traffic stream. 24.7.7 Performing a Link Trace Check Based on the loopback (LB) test, the link trace (LT) test further improves the capability to locate faults. That is, the faulty network segment can be located through only one test. 24.7.8 Activating the AIS After the maintenance point (MP) where the AIS is active detects a fault, the MP transmits the AIS packet to superstratum MP for the notification of the fault. 24.7.9 Performing a Ping Test By using Layer 3 ARP and ICMP packets, the ping test checks the connectivity between the processing board of an Ethernet service and the data communications equipment, such as a switch and router, the packet loss ratio of a service, and the delay time. 24.7.10 Performing Performance Detection After the connectivity between the MPs of the processing boards of Ethernet services is checked, the performance detection realizes the on-line test of the packet loss ratio and delay time of the services.

This topic describes the flow of configuring the IEEE 802.1ag OAM. Figure 24-11 IEEE 802.1ag OAM configuration flow
Start
(1)
Create maintenance domain Create maintenance associations Create maintenance point
(2) (3)
(4)
Activate AIS
(5)
CCtest
(6)
LB test
(7)
LT test
(8)
Ping test
(9)
Performe Performance Detection
End
NOTE
Before using the IEEE 802.1ag OAM, you must create bidirectional Ethernet services. The unidirectional Ethernet service does not support the IEEE 802.1 ag OAM.
24-26
Issue 02 (2009-02-25)
24 ETH OAM
Table 24-7 Descriptions of the IEEE 802.1ag OAM configuration flow Mark (1) (2) (3) (4) (5) (6) (7) (8) (9) Description For the configuration process, see 24.7.2 Creating MDs. For the configuration process, see 24.7.3 Creating MAs. For the configuration process, see 24.7.4 Creating MPs. For the configuration process, see 24.7.8 Activating the AIS. For the configuration process, see 24.7.5 Performing a Continuity Check. For the configuration process, see 24.7.6 Performing a Loopback Check. For the configuration process, see 24.7.7 Performing a Link Trace Check. For the configuration process, see 24.7.9 Performing a Ping Test. For the configuration process, see 24.7.10 Performing Performance Detection.
24.7.2 Creating MDs

A maintenance domain (MD) defines the scope and level of the Ethernet OAM. The MDs of different levels and scopes can provide differentiated OAM services to users.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The board that supports the creation of the MD must be created.
Procedure
Step 1 In the NE Explorer interface, select an NE, and choose Configuration > Ethernet Maintenance > Ethernet Service OAMfrom the Function Tree. Step 2 In the right-hand pane, click OAM Configuration to display the OAM Configuration dialog box.
Issue 02 (2009-02-25)
24-27
24 ETH OAM
NOTE
In this user interface, you can maintain or delete OAM MDs.
Step 3 Click New and select Create MD from the drop-down list. Step 4 In the New Maintenance Domain dialog box displayed, configure the corresponding parameters.
Step 5 Click Apply. Step 6 Click Close. ----End
Parameters
Field Maintenance Domain Name Maintenance Association Name Value For example: MD1 Default Description Displays or sets the maintenance domain name. Displays or sets the maintenance association name.
For example: MA1
24-28
Issue 02 (2009-02-25)
24 ETH OAM
Field Maintenance Domain Level
Value Consumer High(7), Consumer Middle (6), Consumer Low (5), Provider High (4), Provider Low(3), Operator High(2), Operator Middle(1), Operator Low(0) Consumer High(7), Consumer Middle (6), Consumer Low (5), Provider High (4), Provider Low(3), Operator High(2), Operator Middle(1), Operator Low(0)
Default Operator Low(0)
Description Displays or sets the maintenance domain level. The greater the value, the higher the priority.
Maintenance Level
Operator Low(0)
The priority of the MP is the priority of the MD. The greater the value, the higher the priority.
24.7.3 Creating MAs

A maintenance domain (MD) can be divided into several independent maintenance associations (MA). By creating MAs, operators can associate specific Ethernet services with the MAs for easy Ethernet OAM operation.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. Ethernet services must be already created. The MD must be created.
Procedure
Step 1 In the NE Explorer interface, select an NE, and choose Configuration > Ethernet Maintenance > Ethernet Service OAMfrom the Function Tree. Step 2 Click OAM Configuration in the right window to display the OAM Configuration dialog box.
NOTE
In this user interface, you can create or delete OAM maintenance Association (MAs).
Step 3 Click New, select Create MA from the drop-down list.
Step 4 In the dialog box of New Maintenance Association displayed, configure the OAM parameters.
24 ETH OAM
Step 5 ClickApply. The Operation Result dialog box is displayed, indicating that the operation was successful. Step 6 Click Close. ----End
Parameters
Field Maintenance Domain Name Value For example: MD1 Default Description Displays or sets the maintenance domain name.
NOTE The Huawei MP do not need to create MD. When creating MP, please select NULL.
Maintenance Association Name
For example: MA1
Displays or sets the maintenance association name.

NOTE The Huawei MP do not need to create MA. When creating MP, please select NULL.
Maintenance Domain Level
Consumer High(7), Consumer Middle (6), Consumer Low (5), Provider High (4), Provider Low(3), Operator High(2), Operator Middle(1), Operator Low(0)
Operator Low(0)
Displays or sets the maintenance domain level. The greater the value, the higher the priority.
24.7.4 Creating MPs

The functions of the IEEE 802.1ag OAM can be used only after MPs are created.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet service must be created and activated. The MA and MD must be created before creating a stadard MP.
24 ETH OAM
Precaution
In an OAM test, all maintenance points that are involved in the operating of the same service flow must be in the same maintenance domain. In an existing maintenance domain involved in the same service flow, creating a maintenance point of the same level or a higher level may damage the existing maintenance domain. As a result, the OAM test fails.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Click New and the Create MP dialog box is displayed. Complete the information.
NOTE
l l
VLAN ID: Leave this field blank for PORT services. For PORT+VLAN services, set the VLAN ID of the services to be monitored. Service Direction: Only MEPs have the directions. Set the direction from the external physical port to the system-side VCTRUNK port as the SDH direction, and from the system-side VCTRUNK port to the external physical port as the IP direction. MIPs can only be set as bidirectional. . If the data is from the exterior board, the MP direction is IP. The MIPs can be only bidirectional.
Step 3 Optional: Click Advanced. In the dialog box displayed, set the corresponding parameters and click OK.
NOTE
If an MEP is created, you can choose whether to perform the following configuration.
l l
Activate the CC and configure the sending period of the CC test. Set the timeout time for the LB or LT test.
Step 4 Click OK. A prompt appears telling you that the operation was successful. Click Close to finish the operation. ----End
Parameters
Field Node Value slot-board-port Default Description Selects the port where you want to create an MP.
Issue 02 (2009-02-25)
24-31
24 ETH OAM
Field VLAN ID
Value 0 to 4095
Default -
Description Configure the ID of the VLAN to which the service of the MP belongs. The information is contained in the OAM data packet. The MPs with the same VLAN ID in an MD can communicate with each other. The MP ID (Ethernet OAM) specifies the flag that uniquely identifies a maintenance point. The bytes from higher bits to lower bits are respectively described here. The first byte indicates the network number. The second byte indicates the number of the node in the local network. The third and forth bytes indicate the ID of the maintenance point on the network node. The maintenance point ID must be unique in the entire network. The Type (Ethernet OAM) specifies the maintenance point type defined in IEEE 802.1ag. MEP stands for Maintenance association End Point, and MIP stands for Maintenance association Intermediate Point. The priority of the MP is the priority of the MD. The greater the value, the higher the priority.
MP ID
Standard MP: 00-00-0000 to FF-FF-1FFF Huawei MP: 00-00-0000 to FF-FF-FF00
Type
MEP, MIP
MEP
Level
Consumer High (7), Consumer Middle(6), Consumer Low (5), Provider High(4), Provider Low (3), Operator High(2), Operator Middle(1), Operator Low (0) SDH, IP, Bidirectional
Operator Low (0)
Direction
Sets the transmit direction of OAM frames. Select SDH, WDM, IP for MEP nodes, and Bidirectional for MIP nodes.
24-32
Issue 02 (2009-02-25)
24 ETH OAM
Field CC Status
Value Activate, Inactivate
Default Inactivate
Description The CC Status (Ethernet OAM) parameter specifies whether to activate the connectivity check (CC) function at a maintenance point. Sets the LB test timeout.
LB Timeout (ms) LT Timeout (ms) CCM Sending Period(ms)
3000-60000, in increments of 100 3000-60000, in increments of 100 In the case of a standard MP, 1000, 10000, 6000, 600000 In the case of a Huawei MP, 1000 to 60000.
5000
5000
Sets the LT test timeout.
In the case of a standard MP, 1000. In the case of a Huawei MP, 5000.
Sets the time interval for sending the CCM packet at the maintenance point where the CC test is performed.
l
If the time interval is very short, excessive service bandwidths are occupied. If the time interval is very long, the CC test is less sensitive to the service interruption. Thus, the default value is recommended.
24.7.5 Performing a Continuity Check

After the continuity check (CC) test, the unidirectional link status can be checked automatically and periodically. After the CC test is started at the source, if the link is fault, the source equipment reports the EX_ETHOAM_CC_LOS(Huawei MP) or ETH_CFM_LOS(Standard MP) alarm.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The MEP maintenance point must be created. Only the MEP can have the CC test enabled and work as the receiving and responding end in the test.
Context
l
During the CC check, the source MEP constructs and transmits CC frames periodically. The destination MEP receives the CC frames and starts the CC check. If the destination MEP does not receive the CC frames from the source within a specified period of time (for example, 3.5 times the transmit period), the standard MP automatically reports the ETH_CFM_LOS alarm and the Huawei MP automatically reports the EX_ETHOAM_CC_LOC alarm.
Issue 02 (2009-02-25)
24 ETH OAM
Performing a CC check does not affect the service.
Procedure
Step 1 In the NE Explorer, click an Ethernet board and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and select Activate CC. A prompt appears telling you that the operation was successful. Click Close.
l l
Alternatively, you can select a node, right-click, and then choose Activate CC from the shortcut menu to start the CC test. You can select a node, right-click, and then choose Inactivate CC from the shortcut menu to stop the CC test.
NOTE
Before you perform the check, set an appropriate CCM Sending Period (ms) as required.
----End
24.7.6 Performing a Loopback Check

During a loopback (LB) check, you can check the bidirectional connectivity between the source MEP and any MP in the same traffic stream.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The source and sink MEPs, and MIPs in the same maintenance domain must be created. Only MEPs can initiate the LB test, and the MEP can work as the receive end in the test. For the non-standard protocol, the MIP also can work as the receive end in the test. The CC function must be enabled before the LB test can be performed on a standard MP.
Context
During the LB check, the source MEP constructs and transmits the LBM frames and starts the timer. If the destination MP receives the LBM frames, it sends the LBR frames back to the source MEP. This indicates that the loopback is successful. If the source MEP timer times out, it indicates that the loopback fails.
24-34
Issue 02 (2009-02-25)
24 ETH OAM
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and select Start LB. The LB Test dialog box is displayed. Step 3 Enter the LB test source maintenance point ID and sink maintenance point ID. Step 4 Click Start LB and the check result is displayed.
TIP
Alternatively, you can select a node, right-click, and then choose Start LB from the shortcut menu to start the LB test.
NOTE
Before you perform the check, set an appropriate LB Timeout(ms) as required.
----End
Parameters
Field Source MP ID Sink MP ID Test Result Value For example: 00-00-0001 For example: 00-00-0002 Succeeded, Failed Default Description Displays the source MP of the LB test. Displays the sink MP of the LB test. Displays the test result after an LB test or LT test is performed. Sets to test based on the MAC address or not.
NOTE You can perform the MAC address-based LB test on only standard MPs.
Test based on the MAC Address
Checked, Unchecked
Unchecked
Sink MP MAC Address
For example: 00-01-00-0F-00-00
Displays the Sink MP MAC Address.
24.7.7 Performing a Link Trace Check

Based on the loopback (LB) test, the link trace (LT) test further improves the capability to locate faults. That is, the faulty network segment can be located through only one test.
Prerequisite
24 ETH OAM
The source and sink MEPs, and MIPs in the same maintenance domain must be created. Only MEPs can initiate the LT test and work as the termination point in the test. In the case of a standard MP, you must activate CC before LT check.
Context
l
During the LT check, the source MEP constructs and transmits LTM frames and starts the timer. All the MPs that receive the LTM frames send the LTR frame response. According to the LTR frame response, you can verify all the MIPs that pass from the source MEP to the destination MEP.
Performing an LT check does not affect the service.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and select Start LT. The LT Test dialog box is displayed. Step 3 Enter the LT test source maintenance point ID and sink maintenance point ID. Step 4 Click Start LT and the check result is displayed.
TIP
Alternatively, you can select a node, right-click, and then choose Start LT from the shortcut menu to start the LT test.
NOTE
Before you perform the check, set an appropriate LT Timeout(ms) as required.
----End
Parameters
Field Source MP ID Responding MP ID Value For example: 00-00-0001 For example: 00-00-0002 Default Description Displays the source MP in the LT test. Displays the ID of the responded MP in the LT test.
24-36
Issue 02 (2009-02-25)
24 ETH OAM
Field Responding MP Type
Value MEP, MIP
Default -
Description The Responding MP Type (Ethernet LT Test) parameter specifies the type of the responding maintenance point in each LT test. The Hop Count (Ethernet LT Test) parameter specifies the number of hops from the maintenance source endpoint to a maintenance intermediate point, namely, the number of responding intermediate points from the maintenance source point to a certain responding point.
Hop Count
For example: 1
Test Result
Succeeded, Failed
The Test Result (LB and LT Test) parameter specifies the result derived from the LB or LT test each time.
24.7.8 Activating the AIS

After the maintenance point (MP) where the AIS is active detects a fault, the MP transmits the AIS packet to superstratum MP for the notification of the fault.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The source and sink MEPs and MIP must be created in the same maintenance domain (MD).
Procedure
Step 1 In the NE Explorer, select the Ethernet board, choose the Configuration > Ethernet Maintenance > Ethernet Service OAM from the function tree.
Issue 02 (2009-02-25)
24-37
24 ETH OAM
Step 2 Select the node to be monitored. Double-click AIS Activation State and then select Active or Deactive, or right-click the AIS Activation State and then choose Active or Deactive from the shortcut menu. Step 3 Click Apply. ----End
Parameters
Field AIS Activation State Client Layer Level Value Active, Inactive 1 to 7 Default Inactive 7 Description Displays or sets AIS activation state. Displays or sets the level of the MP where AIS fault messages are suppressed. If Level of the MP is set to Operator High(2) and Client Layer Level to 4, this MP reports AIS packets to only the MP whose Level is Provider Low(3) or Level is higher than Consumer Low(5).
NOTE Usually, if the Level of an MP is set to n, its Client Layer Level is set to n+1.
AIS Period(ms)
1000,60000
Displays or sets AIS period.
24.7.9 Performing a Ping Test

By using Layer 3 ARP and ICMP packets, the ping test checks the connectivity between the processing board of an Ethernet service and the data communications equipment, such as a switch and router, the packet loss ratio of a service, and the delay time.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The OAM maintenance node of a service must be created for an Ethernet board. The type of the maintenance node is MEP. The MEP where the ping test is initiated must be created on an external physical port.
24 ETH OAM
The tag attribute of the external physical port where the MEP resides must be Access.
Context
l
The ping test can be initiated only from the Ethernet service processing board to the interconnected data communication equipment. The ping test is performed in the direction from the board to which the MEP belongs to the interconnected data communication equipment of the board. A legal IP address is allocated to the MEP, and the IP addresses of the MEP and the interconnected data communication equipment must be in the same network segment. By default, the IP address of an MP is 0.0.0.0. The IP address of an MP cannot be any of the following:

Zero address: 0.*.*.* Local loopback address: 127.*.*.* Multicast address: 224.0.0.0 - 239.255.255.255 Reserved address: 240.0.0.0 - 255.255.255.255 Network address: *.*.*.0 Broadcast address: *.*.*.255
Performing a ping test does not affect the service.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Optional: Click Query to query OAM information from the NE. Step 3 Select a node, click OAM Operation and select Start Ping. The Ping Test window is displayed.
TIP
To display the Ping Test window, you can also right-click a node and choose Start Ping from the shortcut menu.
Step 4 Set Send Mode.

l l
Burst Mode, you need to set Frame Length, Timeout, and Ping Attempts. If you select Continue Mode, you need to set Frame Length, and Timeout.
Step 5 In the IP Address Configuration area, set Destination IP Address and Local IP Address.
NOTE
l l
The value entered in Local IP Address is the IP address of the local maintenance point. Set legal IP addresses for Local IP Address and Destination IP Address and make sure that the two IP addresses in the same network segment.
Step 6 Click Start Ping and view the returned result in the Detail pane. ----End
Issue 02 (2009-02-25)
24-39
24 ETH OAM
Parameters
Field Send Mode Value Burst Mode, Continue Mode Default Continue Mode Description Specifies a mode in which ping test packets are sent.
l
When the parameter is set to Continue Mode, test packets can be continuously sent, unless you stop the sending operation. When the parameter is set to Burst Mode, the sending times can be set.
Packet Length
64 to 1522 bytes (EMS6) 64 to 1514 bytes (EMS4) In step length of 1
64
The Packet Length (Ping Test) parameter specifies the maximum length of the Ping packets if the Ping operation is initiated at a maintenance endpoint. Sets the length of the transmitted frame. The minimum frame length is 64 bytes.
Timeout
3-60, in step length of 1
The Timeout (Ping Test) parameter specifies the waiting period in which no response message is received from the opposite end after a maintenance point initiates the Ping test. In this case, the maintenance point regards that the Ping test fails. This waiting period is called the Ping timeout time.
24-40
Issue 02 (2009-02-25)
24 ETH OAM
Field Ping Attempts
Value 1 to 1000 times
Default
Description The number of attempts to send ping test packets if you set Send Mode to Burst Mode. If you set Send Mode to Continue Mode, this parameter cannot be edited.
Destination IP Address
For example, 129.9.0.123
The value of Destination IP Address can only be the IP address of the data communication equipment (such as a switch or router) that is interconnected to the data board. The ping test can be initiated only from the data board to the interconnected data communication equipment. The value of Local IP Address is the IP address of the maintenance point on the data board. The information returned after you perform a ping test.
Local IP Address
For example, 129.9.0.123
Detail
The information returned after you perform a ping test.
24.7.10 Performing Performance Detection

After the connectivity between the MPs of the processing boards of Ethernet services is checked, the performance detection realizes the on-line test of the packet loss ratio and delay time of the services.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The source and sink MEPs, and MIPs in the same maintenance domain must be created.
Issue 02 (2009-02-25)
24-41
24 ETH OAM
Context
l
The source maintenance point that initiates a performance test must be an MEP. The sink maintenance point that responds to the performance test can be an MEP or MIP. Performing performance detection does not affect the service.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Optional: Click Query to query OAM information from the NE. Step 3 Select a node, click OAM Operation and select Performance Detect. The Performance Detect window is displayed.
TIP
To display the Performance Detect window, you can also right-click a node and choose Performance Detect from the shortcut menu.
Step 4 Set Send Mode.

l l
Burst Mode, you need to set Frame Length, Timeout, and Detect Attempts. If you select Continue Mode, you need to set Frame Length, and Timeout.
Step 5 In the Maintenance Point area, set Source MP ID and Destination MP ID. Step 6 Click Start Detect and view the returned result in the Detail pane. ----End
Parameters
Field Send Mode Value Burst Mode, Continue Mode Default Description Specifies a mode in which performance detection packets are sent. Specifies the length of a performance detection packet.
Frame Length
64 to 1522 bytes (EMS6) 64 to 1514 bytes (EMS4) In step length of 1
Timeout Detect Attempts
3 to 60 seconds 1-1000, in step length of 1
Specifies the timeout time. Specifies the detection attempts for performing performance detection defined in IEEE 802.1ag.
Issue 02 (2009-02-25)
24-42
24 ETH OAM
Field Source MP ID
Value For example: 00-00-0001
Default -
Description Specifies the ID of the maintenance point that sends detection packets. Specifies the ID of the maintenance point that receives detection packets. Specifies the information returned after you perform performance detection.
Destination MP ID
For example: 00-00-0002
Detail
24.8 IEEE 802.1ag OAM Example

Different maintenance points (MPs) are configured according to different Ethernet services.
Configuration Example of the IDU 605

For configuration details of the MP of an Ethernet service, see OptiX RTN 605 Radio Transmission System Configuration Guide.
Configuration Example of the IDU 610/620

For configuration details of the MP of an Ethernet service, see OptiX RTN 600 Radio Transmission System Configuration Guide.
24.9 Using the IEEE 802.3ah OAM

By using the IEEE 802.1ag OAM, you can maintain the Ethernet link in a point-to-point manner. 24.9.1 Configuration Flow This topic describes the flow of configuring the IEEE 802.3ah OAM. 24.9.2 Enabling the Auto-Discovery Function of OAM 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. 24.9.3 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. 24.9.4 Modifying the Parameters of the OAM Error Frame Monitoring Threshold The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link performance. Usually, the default value is used. You can modify the value according to the situation of the link. 24.9.5 Performing the Remote Loopback
24 ETH OAM
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. 24.9.6 Enabling the Self-Loop Detection After enabling the self-loop detection on an Ethernet port, you can check the loopback of the port and the loopback between the port and other Ethernet ports on the board.

This topic describes the flow of configuring the IEEE 802.3ah OAM.
24-44
Issue 02 (2009-02-25)
24 ETH OAM
Figure 24-12 IEEE 802.3ah OAM configuration flow

Start
Check whether loopback is set on the port. Yes Enable the self-loop detection Enabling the auto-discovery function of OAM
No
(1) (2)
Fault detection automatically starts
Link performance detection automatically starts Whether to notify the opposite end of the detected performance thresholdcrossing Yes
(3)
Perform the remote loopback
Whether to notify the opposite end of the detected fault Yes
No
No
Loopback is successful
No
Yes Cancel remote loopback
(4)
Enabling the link event notification
(4)
Enabling the link event notification
Whether modify the error frame monitoring threshold
No
(5)
Yes Modify the parameters of the OAM error frame monitoring threshold
End
Issue 02 (2009-02-25)
24-45
24 ETH OAM
Table 24-8 Descriptions of the IEEE 802.3ah OAM configuration flow Mark (1) (2) Description For the configuration process, see 24.9.6 Enabling the Self-Loop Detection. For the configuration process, see 24.9.2 Enabling the Auto-Discovery Function of OAM. For the configuration process, see 24.9.5 Performing the Remote Loopback. For the configuration process, see 24.9.3 Enabling the Link Event Notification. For the configuration process, see 24.9.4 Modifying the Parameters of the OAM Error Frame Monitoring Threshold.
(3) (4) (5)
24.9.2 Enabling the Auto-Discovery Function of OAM

The IEEE 802.3ah OAM is realized based on the OAM auto-discovery. After the OAM autodiscovery succeeds, the equipment automatically monitors the fault and performance of the link.
Prerequisite
Context
The OAM auto-discovery is realized through the auto-negotiation between the local equipment and the opposite equipment. If the negotiation fails, the local equipment reports an alarm. After the OAM auto-discovery succeeds, the link performance is performed according to the error frame threshold. You can set the error frame threshold on the Web LCT.
l
The OAM mode includes the active mode and the passive mode. For two interconnected systems, the OAM mode of one system must be the active mode. Otherwise, the OAM auto-discovery fails. if the OAM modes of the two systems are both active modes, a link fault occurs, or one system fails to receive the OAM protocol message, an alarm is reported, indicating that the OAM auto-discovery fails.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Click .
Step 2 Click the OAM Parameter tab, Set OAM Working Mode. In the Enable OAM Protocol dropdown list, select Enabled.
24 ETH OAM
Step 3 Click Apply. Step 4 Click the Remote OAM Parameter tab. Click Query. ----End
Parameters
Field Port Enable OAM Protocol Value For example: PORT1 Enabled, Disabled Default Disabled Description Displays the port name. The Enable OAM Protocol parameter specified whether the end-to-end OAM protocol (namely, the IEEE 802.3ah protocol) is enabled at a port. After the OAM protocol is enabled, the current Ethernet port starts to use the preset mode to create the OAM connection with the opposite end.
Issue 02 (2009-02-25)
24-47
24 ETH OAM
Field OAM Working Mode
Value Active, Passive
Default Active
Description The OAM Working Mode parameter specifies a negotiation mode specified in IEEE 802.3ah Standard.? negotiation mode of IEEE 802.3ah. It involves two modes: Passive and Active. The port for which this field is set to Active can initiates the OAM connection. The port for which this field is set to Passive can only wait for the opposite end to send the OAM connection request.
Remote Alarm Support for Link Event
Enabled, Disabled
Enabled
The Remote Alarm Support for Link Event parameter specifies whether to report the detected link events (for example, Error Frame Period Threshold, Error Frame Monitor Threshold, and Error Frame Second Threshold) to the opposite end. Displays the maximum OAM packet length.
Max. OAM Packet Length (byte)
For example: 1000
24-48
Issue 02 (2009-02-25)
24 ETH OAM
Field Loopback Status
Value Initiate Loopback at Local, Respond Loopback of Remote, NonLoopback
Default Non-Loopback
Description The Loopback Status (OAM Parameter) parameter specifies whether a port on the board is in the loopback state. If yes, the port is in the Initiate Loopback at Local or Respond Loopback of Remote state.
24.9.3 Enabling the Link Event Notification

After the link event notification is enabled on the local equipment, if the OAM detects a link fault and link performance event, the opposite equipment is informed.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. Make sure that the OAM auto-discovery succeeds.
Context
When the OAM auto-discovery succeeds at the two ends, the link fault detection and performance detection are automatically started.
l
To report the detected link fault event to the opposite equipment, Remote Alarm Support for Link Event must be set to Enabled for the local equipment. To report the detected link fault event to the opposite equipment, the following operations must be performed for the local equipment.

Set Remote Alarm Support for Link Event to Enabled. Set Error Frame Period Window (Frame) and Error Frame Monitor Threshold.
After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if the opposite end detects link performance degradation, you can query the ETHOAM_RMT_SD alarm , which is reported on the local end, by using the Web LCT. Based on the alarm, you can determine the type of the link performance event. After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if the opposite equipment detects a link fault event or encounters a fault that makes the equipment fail to be restored (such as a power failure), you can query the ET_RMT_CRIT_FAULT alarm, which is reported at the local end, by using the Web LCT. Based on the alarm, you can determine the fault type.
Issue 02 (2009-02-25)
24-49
24 ETH OAM
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Maintenance > Ethernet Port OAM. Click .
Step 2 Click the OAM Parameter tab. Set Remote Alarm Support for Link Event to Enabled.
Parameters
Field Port Enable OAM Protocol Value For example: PORT1 Enabled, Disabled Default Disabled Description Displays the port name. The Enable OAM Protocol parameter specified whether the end-to-end OAM protocol (namely, the IEEE 802.3ah protocol) is enabled at a port. After the OAM protocol is enabled, the current Ethernet port starts to use the preset mode to create the OAM connection with the opposite end.
24-50
Issue 02 (2009-02-25)
24 ETH OAM
Field OAM Working Mode
Default Active
Description The OAM Working Mode parameter specifies a negotiation mode specified in IEEE 802.3ah Standard.? negotiation mode of IEEE 802.3ah. It involves two modes: Passive and Active. The port for which this field is set to Active can initiates the OAM connection. The port for which this field is set to Passive can only wait for the opposite end to send the OAM connection request.
Remote Alarm Support for Link Event
Enabled, Disabled
Enabled
The Remote Alarm Support for Link Event parameter specifies whether to report the detected link events (for example, Error Frame Period Threshold, Error Frame Monitor Threshold, and Error Frame Second Threshold) to the opposite end. Displays the maximum OAM packet length.
For example: 1000
Issue 02 (2009-02-25)
24-51
24 ETH OAM
Field Loopback Status
Value Initiate Loopback at Local, Respond Loopback of Remote, NonLoopback
Default Non-Loopback
Description The Loopback Status (OAM Parameter) parameter specifies whether a port on the board is in the loopback state. If yes, the port is in the Initiate Loopback at Local or Respond Loopback of Remote state.
24.9.4 Modifying the Parameters of the OAM Error Frame Monitoring Threshold
The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link performance. Usually, the default value is used. You can modify the value according to the situation of the link.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The IEEE 802.3ah OAM function must be enabled on the remote equipment.
Context
After the OAM auto-discovery succeeds, set Error Frame Period Window (Frame) and Error Frame Monitor Threshold, and set Remote Alarm Support for Link Event to Enabled for the local equipment. If the local equipment detects a link event in the receive direction, it informs the opposite equipment of the link event. If the remote alarm for the link event is also supported on the opposite end, the opposite equipment can also inform the local equipment of the link event that is detected on the side of the opposite end. Then, the ETHOAM_RMT_SD alarm is reported on the local end, prompting the maintenance personnel to handle the link event.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Click the OAM Error Frame Monitor tab.
24-52
Issue 02 (2009-02-25)
24 ETH OAM
Step 2 Select a port and set the error frame monitoring parameters. Step 3 Click Apply. A prompt appears indicating that the operation was successful. Step 4 Click Close. ----End
Parameter Description
Field Error Frame Monitor Window (ms) Value 100060000, in increments of 100 Default Description In the specified Error Frame Monitor Window (ms), if the number of error frames exceeds the specified Error Frame Monitor Threshold (Entries) due to the link degradation, the link event alarm is reported. Sets the monitoring threshold of error frames.
Error Frame Monitor Threshold (Entries) Error Frame Period Window (frame)
14294967295, in increments of 1 1488 892800000 (EMS6) 148889280000 (EMS4) in increments of 1
In the specified Error Frame Period Window (frame), if the number of error frames exceeds the specified Error Frame Period Threshold (frame) due to the link degradation, the link event alarm is reported. Sets the monitoring threshold of the error frame period.
Error Frame Period Threshold (frame) Error Frame Second Window (s)
1892800000, in increments of 1 10900, in increments of 1
If any error frame occurs in one second, this second is an error frame second. If the number of error frame seconds in the Error Frame Second Window(s) period exceeds the specified Error Frame Second Threshold (s), the link event alarm is reported.
Error Frame Second Threshold (s)
1900, in increments of 1
Sets the threshold for monitoring the error frame seconds.
Issue 02 (2009-02-25)
24-53
24 ETH OAM
24.9.5 Performing the Remote Loopback

After the Ethernet port on the local equipment sends data to the port on the interconnected equipment, the local end can request the opposite end to return the data.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. Make sure that the OAM auto-discovery succeeds. For the equipment where the loopback is initiated, OAM Working Mode must be set to Active. The equipment that responds to the loopback must have the capability of supporting the remote loopback.
Context
l
The IDU 620 do not support responding the remote loopback, and the IDU 605 support responding the remote loopback. If a port is capable of responding to loopbacks, it enters the Respond Loopback of Remote state and reports the loopback responding alarm when receiving the command of enabling the remote loopback function sent from the opposite OAM port. In this case, the equipment that initiates the loopback enters the initiate loopback at local state and reports the loopback initiating alarm. After the remote loopback function is enabled, normally, service packets, except the OAMPDU, are looped back at the remote end. After using the remote loopback function to complete the fault locating and the link performance detection, you should disable the remote loopback function at the end where the loopback is initiated and then restore the services. At this time, the alarm is automatically cleared.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Maintenance > Ethernet Port OAM. Click .
Step 2 Click OAM Parametertab. Select the port that needs to initiate a loopback, and choose Enable Remote Loopback from the drop-down list of OAM. Step 3 Click Apply. ----End
Parameters
Field Port Value For example: PORT1 Default Description Displays the port name.
Issue 02 (2009-02-25)
24-54
24 ETH OAM
Field Remote OAM Working Mode Remote Alarm Support for Link Event Remote Side Loopback Response Unidirectional Operation
Default -
Description Queries the working mode of the OAM at the opposite port. Sets whether the local link event can be notified to the opposite end. Queries the loopback response at the opposite port. Displays whether the unidirectional operation is supported. Displays the maximum OAM packet length.
Disabled, Enabled
Disabled, Enabled
Disabled, Enabled
For example: 1000
24.9.6 Enabling the Self-Loop Detection

After enabling the self-loop detection on an Ethernet port, you can check the loopback of the port and the loopback between the port and other Ethernet ports on the board.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. All the external physical ports of the Ethernet service processing board are enabled.
Context
When the self-loop detection is enabled for an external physical port, if the self-loop situation occurs at the port, the ETHOAM_SELF_LOOP alarm is reported.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Interface Management > Ethernet Interface . Click Step 2 Configure the external physical port. 1. 2. Select External Port. Click the Advanced Attributes tab. Set Loop Detection to Enabled. .
Issue 02 (2009-02-25)
24-55
24 ETH OAM
3.
Click Apply.
----End
Parameters
Field Port Value PORTn Default Description Displays the PORT port. The letter n indicates the port number. Enables or disables broadcast packet suppression. When the broadcast packet suppression function is enabled, if the broadcast packet occupies a bandwidth that exceeds the overall bandwidth of the port x the suppression threshold, the broadcast packet is suppressed. Sets whether to enable loop detection, which is used to check whether a loop exists at the port.
Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold
Disabled, Enabled
Disabled
10% to 100%
Loop Detection
Disabled, Enabled
Disabled

This topic describes the alarms and performance events relevant to the ETH-OAM feature, and the problems that occur frequently during the application of the ETH-OAM feature. 24.10.1 Relevant Alarms and Events If an NE detects an abnormality by using ETH-OAM operations, the NE reports the corresponding alarm.
24 ETH OAM
24.10.2 FAQs This topic lists the problems that occur frequently during the application of the ETH-OAM feature.

If an NE detects an abnormality by using ETH-OAM operations, the NE reports the corresponding alarm.
Relevant Alarms
l
ETHOAM_RMT_LOOP The ETHOAM_RMT_LOOP alarm indicates that a remote loopback is initiated when the point-to-point Ethernet OAM function is enabled. When the local equipment initiates a remote loopback or responds to the remote loopback initiated by the equipment at the opposite end, the system reports this alarm.
ETHOAM_RMT_SD The ETHOAM_RMT_SD alarm indicates that the performance of the remote Ethernet is degraded when the point-to-point Ethernet OAM function is enabled. When the port on which the OAM protocol is enabled receives the link event notification packet sent by the opposite end, the system reports this alarm.
ETHOAM_RMT_CRIT_FAULT The ETHOAM_RMT_CRIT_FAULT alarm indicates that a critical fault alarm occurs at the opposite end when the point-to-point Ethernet OAM function is enabled. When the port on which the OAM protocol is enabled receives the OAM packet that contains critical fault information sent by the opposite end, the system reports this alarm.
ETHOAM_DISCOVER_FAIL The ETHOAM_DISCOVER_FAIL alarm indicates a discovery failure when the point-topoint Ethernet OAM function is enabled. When the negotiation between the port on which the OAM protocol is enabled and the equipment at the opposite end fails, the system reports this alarm.
ETHOAM_SELF_LOOP The ETHOAM_SELF_LOOP alarm indicates that a MAC port is looped back when the point-to-point Ethernet OAM function is enabled. When a MAC port of a board receives the OAM protocol packets sent by the MAC port or the board after the loopback detection function is enabled, the system reports this alarm.
EX_ETHOAM_CC_LOS The EX_ETHOAM_CC_LOS alarm indicates that the periodical continuity check packet is lost. When the sink maintenance point does not receive the continuity check packet sent by the same source maintenance point within a period (3.5 times of the time that the source maintenance point uses to send the continuity check packet), the system reports this alarm.
EX_ETHOAM_MPID_CNFLCT The EX_ETHOAM_MPID_CNFLCT alarm indicates that the IDs of the maintenance points are repeated. When a maintenance point receives the packets sent by the maintenance point that has the same ID and the two maintenance points are in the same maintenance domain, the system reports this alarm.
ETH_CFM_LOC
Issue 02 (2009-02-25)
24 ETH OAM
The ETH_CFM_LOC alarm indicates the loss of continuity. When the system does not receive the continuity check message (CCM) sent by the remote maintenance point within 3.5 times of the continuity check period, the system reports this alarm.
l
ETH_CFM_MISMERGE The ETH_CFM_MISMERGE alarm indicates an incorrect connection. When the system receives a message that indicates a mismatch of maintenance association (MA) IDs or receives a low-level CCM, the system reports this alarm.
ETH_CFM_RDI The ETH_CFM_RDI alarm indicates that the receive end of the remote maintenance point fails. When the system receives a CCM that contains the RDI sent by the remote end, the system reports this alarm.
ETH_CFM_UNEXPERI The ETH_CFM_UNEXPERI alarm indicates that an incorrect frame is received. When the system receives an invalid CCM, the system reports this alarm.

None.
24.10.2 FAQs
This topic lists the problems that occur frequently during the application of the ETH-OAM feature. None.
24-58
Issue 02 (2009-02-25)
25 Link aggregation
25
About This Chapter
Link aggregation
Link aggregation allows multiple links that are attached to the same equipment to be aggregated to form a link aggregation group (LAG) so that the bandwidths and availability of the links increase. The aggregated links can be considered as a single logical link. 25.1 Overview Link aggregation allows multiple links that are attached to the same equipment to be aggregated to form a link aggregation group (LAG) so that the bandwidths and availability of the links increase. The aggregated links can be considered as a single logical link. 25.2 Basic Concepts This topic describes the types of aggregation, load sharing modes, and Link Aggregation Control Protocol (LACP). 25.3 Availability The LAG feature requires the support of the applicable equipment and boards. 25.4 Relation with Other Features This section describes related Ethernet features that an LAG affects. 25.5 Principle The LACP protocol is used to realize dynamic aggregation and de-aggregation of Ethernet links. The LACP protocol is developed based on IEEE 802.3ad. 25.6 Service Planning Service planning involves planning the services in detail based on the service requirements before the creation of the services. Service planning information helps users configure the services. Service planning includes obtaining the networking information and requirements and planning the configuration data. 25.7 Creating a LAG Link aggregation allows all the members in a LAG to share the incoming and outgoing service loads, thus increasing bandwidth. In addition, the members in the same LAG provide backup to each other dynamically. This increases the availability of the connection. 25.8 Maintenance Guide
Issue 02 (2009-02-25)
25-1
25 Link aggregation
This topic describes the alarms and performance events relevant to the LAG feature, and the problems that occur frequently during the application of the LAG feature.
25-2
Issue 02 (2009-02-25)
25 Link aggregation
25.1 Overview
Link aggregation allows multiple links that are attached to the same equipment to be aggregated to form a link aggregation group (LAG) so that the bandwidths and availability of the links increase. The aggregated links can be considered as a single logical link. The LAG aggregates multiple physical links to form a logical link that is at a higher rate. 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 each link corresponds to a port in an Ethernet. As shown in Figure 25-1, link aggregation provides the following functions:
l
Increased bandwidth The LAG provides the telecom operators with a cost-effective method of increasing the link bandwidth. The telecom operators 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 provide backup to each other dynamically. When a link fails, another link in the LAG quickly replaces the failed link. The process in which link aggregation starts the backup link relates only to the links in the same LAG and does not relate to the links that are not in the LAG.
Figure 25-1 Link aggregation group

Link 1 Link 2 Ethernet packets Link 3 LAG Ethernet packets
Standard and protocol compliance The LAG feature complies with the IEEE 802.3ad Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications.
25.2 Basic Concepts

This topic describes the types of aggregation, load sharing modes, and Link Aggregation Control Protocol (LACP). 25.2.1 LAG Types
25 Link aggregation
The network management system (NMS) supports manual aggregation and static aggregation. The LAG supports the load sharing mode and the load non-sharing mode. 25.2.2 Port Types In an LAG, the ports supports two types: main port and slave port. 25.2.3 Switching Conditions A service is switched between ports when a port fails or the key chip of a port is faulty. 25.2.4 Switching Impact The switching of the ports in an LAG does not generate bit errors.
25.2.1 LAG Types

The network management system (NMS) supports manual aggregation and static aggregation. The LAG supports the load sharing mode and the load non-sharing mode.
Types of Aggregation
Link aggregation is available in the following two types:
l
Manual aggregation A user manually creates a LAG. When a user adds or deletes a member port, the LACP protocol is disabled. A port can be in the up or down state. The system determines whether to perform aggregation depending on the physical status of a port (up or down). Manual aggregation is not as accurate or effective as static aggregation in controlling link aggregation.
Static aggregation A user manually creates a LAG. When a user adds or deletes a member port, the LACP protocol is enabled. A port can be in the selected, unselected, or standby state. The equipment exchanges aggregation information by using the LACP protocol to reach agreement on aggregation. Static aggregation is more accurate and more effective than manual aggregation in controlling link aggregation.
Load Sharing Modes

The LAG supports the following load sharing modes:
l
Load sharing mode 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 increases. When a member in a LAG changes or a certain link fails, the traffic is re-allocated automatically.
Load non-sharing mode 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 the hot standby mechanism. This is because when an active link in a LAG fails, the system selects a link among the standby links in the LAG as an active link to replace the failed link.
25.2.2 Port Types

In an LAG, the ports supports two types: main port and slave port.

NOTE
25 Link aggregation
l l l
All ports in an LAG must be on the same processing board or interface board. The main port number cannot appear in the slave port number list. A slave port can be added to an LAG only when no service is configured for the port. A main port can be added to an LAG even if you configure services for the port, and the services of the port are not affected. You can modify or query the attributes of a main port. You cannot set the logical attributes of a slave port, but can query it. FE port and GE port can not in the same LAG.
l l
Main Port
The Main Port indicates the LAG member port available for creating services. Each LAG has only one main port. If the load sharing parameter is set to Non-Sharing, the main port carries the services. When the main port becomes faulty, the services are switched to and carried by the slave port. Every Ethernet port on the NE can be used as the main port.
Slave Port
The slave ports in a link aggregation group are fixed. Unless they are manually modified, the system does not automatically add them to or delete them from the link aggregation group. Add the relevant slave port to the link aggregation group as required.

A service is switched between ports when a port fails or the key chip of a port is faulty.
Switching Conditions
When an LAG is used, an alarm as described in Table 25-1 occurs and is reported to the Web LCT. The Web LCT analyzes the alarm and then switches the service between ports. Table 25-1 Trigger conditions of an LAG switching Switching Conditions LAG_PORT_F AIL LAG_VC_POR T_FAIL Condition Description The port of an LAG fails. The VCG port of an LAG fails. Cause
l l l l l
The port is in the link down or disable state. The port is in the half-duplex mode. The port does not receive the LACP packet. The self-loop is performed on the port. Other unknown causes
25-5
Issue 02 (2009-02-25)
25 Link aggregation

The switching of the ports in an LAG does not generate bit errors.
25.3 Availability
The LAG feature requires the support of the applicable equipment and boards. Table 25-2 Availability of the LAG feature Feature LAG Applicable Board EMS6 (all the versions) Applicable Equipment IDU 620 IDU 605 1F/2F

This section describes related Ethernet features that an LAG affects.
l l l
The FE and GE ports cannot be converged on the Web LCT. When an LAG works in the load sharing mode, the correctness of the QoS is affected. When hybrid radio services use the 1+1 IF protection, the IFH2 board must be interconnected with the EMS6 board. In addition, the non-load-sharing manual convergence function and non-revertive modeis enabled on the interconnected port of the EMS6 board.
25.5 Principle
The LACP protocol is used to realize dynamic aggregation and de-aggregation of Ethernet links. The LACP protocol is developed based on IEEE 802.3ad. The LACP protocol is developed based on IEEE 802.3ad and performs the following functions:
l
The LACP protocol provides the data switching equipment with a standard negotiation mode. Hence, the system automatically forms aggregation links according to its configuration and enables the aggregation links to transmit and receive data. After an aggregation link is formed, the LACP protocol maintains the status of the aggregation link. When the aggregation conditions change, the LACP protocol automatically adjusts or releases the LAG.
As shown in Figure 25-2, 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. Each LACP packet contains the system priority, system MAC address, port priority, port number, and operational key. The operational key reflects the aggregation capability of the port. The key value is determined by certain factors such as the physical characteristics of the port (for example, rate and duplex), configuration constraints set by the network administrator, characteristics of the port, and limitations of the port.
25-6
25 Link aggregation
2.
After equipment B receives an LACP packet from equipment A, equipment B compares the information in the LACP packet with the information stored 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 stored by the other ports and selects the ports that can be aggregated. Equipment A and equipment B reach agreement on the ports that can be added into a LAG, and then, form a LAG.
3.
4.
Figure 25-2 Application of the LACP protocol

Equipment A Equipment B
PORT1 PORT2 PORT3 PORT4
PORT1 PORT2 PORT3 PORT4
The characteristics of the LACP protocol are as follows:

l
The systems realize auto-negotiation by exchanging LACP packets. Each LACP packet contains the configuration and current status of the system that sends the LACP packet. The LACP packets are sent in any of the following modes:
Event triggering mode A change in the local status or local configuration triggers the generation and sending of a new LACP packet.
Periodical sending mode When an aggregation link works stably, the system periodically sends the current state to maintain the aggregation link.
The LACP packet is not numbered. Hence, both parties use the timer and periodical sending mechanism, instead of the detection and re-transmission of lost packets mechanism, to prevent loss of information. The number of LACP packets that are sent in one second does not exceed five.
25.6 Service Planning

Service planning involves planning the services in detail based on the service requirements before the creation of the services. Service planning information helps users configure the services. Service planning includes obtaining the networking information and requirements and planning the configuration data.
Issue 02 (2009-02-25)
25-7
25 Link aggregation
Networking and Requirements

Link aggregation allows multiple links that are attached to the same equipment to be aggregated to form a LAG so that the bandwidths and availability of the links increase. The aggregated links can be considered as a single logical link. The LAG applies to Ethernet ports. As shown in Figure 25-3, NE1 is connected to the equipment on the user side through three data links. The three data links form a LAG to increase the bandwidths and availability of the links. The service requirements are as follows:
l l
Three 100 Mbit/s links must be available between NE1 and the equipment on the user side. The three links must be aggregated into a 300 Mbit/s link.
Figure 25-3 Networking diagram of a LAG

NE1 User side LAG Link 1 Link 2 Link 3
Data link
Service Planning
The engineering design department plans the services based on the engineering requirements and provides detailed planning information. The networking as shown in Figure 25-3 is considered as an example. Table 25-3 lists the planned LAG parameters and their values. Table 25-3 Panned LAG parameters and their value Parameter LAG No. LAG Name LAG Type Load Sharing System Priority Main Port Slave Ports Port Priority of PORT5 Port Priority of PORT6 Port Priority of PORT7
25-8
Value 1 LAG1 Static Sharing 0 PORT5 PORT6 and PORT7 1 2 3

Issue 02 (2009-02-25)
25 Link aggregation
25.7 Creating a LAG

Link aggregation allows all the members in a LAG to share the incoming and outgoing service loads, thus increasing bandwidth. In addition, the members in the same LAG provide backup to each other dynamically. This increases the availability of the connection.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The physical network topology must be established. Ethernet boards must be created.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Step 2 Click the Link Aggregation Group Management tab. Step 3 Click New and the Create Link Aggregation Group dialog box is displayed. Set the parameters.
Step 4 Click OK.

25 Link aggregation
Step 5 Optional: Click the Link Aggregation Parameters tab. Set Port Priority and System Priority.
NOTE
l l
The port ID consists of Port and Port Priority. The port that has the smallest port ID in a LAG has the priority to be aggregated first. The system ID consists of System Priority and System MAC Address. When the system negotiates with the remote system, the system with the smallest ID has the priority to choose the port. In this example, the system refers to the board, and the system MAC address refers to the MAC address of the board. The factory-set MAC address is globally unique and cannot be modified.
----End
Parameters
Field LAG No. Value An integer from 1 to 7(EMS6) An integer from 1 to 2(EMS4) LAG Name For example: LAG_1 Displays the LAG name. Default Description Displays the LAG number.
25-10
Issue 02 (2009-02-25)
25 Link aggregation
Field LAG Type
Value Manual, Static
Default Manual
Description
l
Static: If this value is selected, you can manually create an LAG with the LACP protocol. You can verify the working status (selected or standby) of ports in the LAG. A port can be in the Selected, Unselected, or Standby state. The convergence information is exchanged among the different equipment through the LACP protocol, so that the convergence information can be consistent. Manual: If this value is selected, you can manually create an LAG with no LACP protocol. The port can be in the UP or DOWN state. According to the physical (UP or DOWN) state of the port, you can determine whether to perform a convergence.
In the case of the LAG that is created for the IF 1+1 protection, this parameter is set to Manual. In other situations, set this parameter according to the requirements
Issue 02 (2009-02-25)
25-11
25 Link aggregation
Field
Value
Default
Description of the opposite equipment.
Load Sharing
Sharing, NonSharing
Sharing
Sharing: If this value is selected, each member link of an LAG has traffic at the same time and shares loads together. The load sharing can increase a higher bandwidth for the link. When the LAG members change, or certain links fail, the system automatically reallocates the traffic. Non-Sharing: Only one member link of an LAG has traffic, and other links are standby. In this case, a type of hot backup mechanism is provided. When the active link of an LAG fails, the system chooses one link from the standby links of the LAG and activates it, to suppress the link failure.
In the case of the LAG that is created for the IF 1+1 protection, this parameter is set to Non-Sharing. In other situations, set this parameter according to the requirements of the opposite equipment.
25-12
Issue 02 (2009-02-25)
25 Link aggregation
Field Main Port
Value For example: PORT1
Default -
Description The main port in an LAG.

l
In the case of the LAG that is created for the IF 1 +1 protection, you need to select the port that is interconnected with the active IF board IFH2 for this parameter. In other situations, set this parameter according to the requirements of the opposite equipment.
After an LAG is created, you can add Ethernet services to the main port only. Services cannot be added to a slave port. When the Load Sharing parameter is set to Non-Sharing, all services are transmitted on the link to which the main port is connected. The links to which other slave ports are connected function as protection links.
Issue 02 (2009-02-25)
25-13
25 Link aggregation
Field Slave Port
Value -
Default -
Description The slave port in an LAG. The parameter specifies that a link aggregation group is manually created rather than being automatically created by the system. A link aggregation group contains main ports and slave ports. The slave ports in a link aggregation group are fixed. Unless they are manually modified, the system does not automatically add them to or delete them from the link aggregation group.
25-14
Issue 02 (2009-02-25)
25 Link aggregation
Field Status
Value Unknown, In Service, Out of Service
Default -
Description The parameter specifies the state, which is derived from logical computation, of each member ports in a link aggregation group.
l
If you do not query an LAG, the port status is Unknown. If the port is the actually working port and services are forwarded at the port, the port status is In Service. If the port is the standby port and no service is forwarded at the port, the port status is Out of Service. In the case of the LAG that is created for the IF 1 +1 protection, you need to select the port that is interconnected with the standby IF board IFH2 for this parameter. In other situations, set this parameter according to the requirements of the opposite equipment.
Available Slave Ports
For example: PORT2
Selected Slave Ports
For example: PORT2
Displays the port that is selected as a slave port.
Issue 02 (2009-02-25)
25-15
25 Link aggregation
Field Port Priority
Value 0-65535, in step length of 1
Default 32768
Description This parameter is valid only when the LAG Type of an LAG is set to Static. This parameter indicates the priorities of the ports in an LAG as defined in the LACP protocol. The smaller the value, the higher the priority. When ports are added into an LAG, the port with highest priority is preferred to transmit services.
25-16
Issue 02 (2009-02-25)
25 Link aggregation
Field System Priority
Value 0-65535, in step length of 1
Default 32768
Description This parameter is valid only when the LAG Type of an LAG is set to Static. This parameter indicates the priority of an LAG. The smaller the value, 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 computation result based on the logic that is selected by the LAG with the higher system priority is considered as the result of both LAGs. If the priorities of both LAGs are the same, the system MAC addresses are compared. Then, the computation result based on the logic that is selected by the LAG with lower system MAC address is considered as the result of both LAGs.
System MAC Address

NOTE
For example: 00-16EC-FA-AC-0A
Displays the system MAC address.
For different boards, the value ranges of the port and system priorities are different.

This topic describes the alarms and performance events relevant to the LAG feature, and the problems that occur frequently during the application of the LAG feature. 25.8.1 Relevant Alarms and Events
25 Link aggregation
If a port in a LAG fails, the corresponding alarm is reported. 25.8.2 FAQs This topic lists the problems that occur frequently during the application of the LAG feature.

If a port in a LAG fails, the corresponding alarm is reported.
Relevant Alarms
l
LAG_PORT_FAIL The LAG_PORT_FAIL alarm indicates that a PORT in an Ethernet LAG fails. When a PORT in a LAG is unavailable, the system reports this alarm.
LAG_VC_PORT_FAIL The LAG_VC_PORT_FAIL alarm indicates that a VCG port in a LAG fails. When a VCTRUNK port in a LAG is unavailable, the system reports this alarm.

None.
25.8.2 FAQs
This topic lists the problems that occur frequently during the application of the LAG feature. None.
25-18
Issue 02 (2009-02-25)
26 Link State Pass Through
26
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 at two ends in the transmission network of starting the backup network at the earliest time for communication, thus making sure the normal transmission of the important data. 26.1 Feature Description LPT is a service-based protection scheme, supporting the Ethernet line service of the point-topoint and point-to-multipoint. 26.2 Availability The LPT feature requires the support of the applicable equipment and boards. 26.3 Relation with Other Features LPT only used in the Ethernet private line service of the point-to-point and point-to-multipoint. The Ethernet port supports the auto-negotiation function. 26.4 Realization Principle LPT is realized by transmitting different packets that varies according to different types of faults. 26.5 Planning Guide You need to plan the LPT according to the specific service. 26.6 LPT Configuration When enabling the LPT function for an Ethernet service, you need to configure the LPT port and the related information. 26.7 Maintenance Guide This topic describes the alarms and performance events relevant to the LPT feature, and the problems that occur frequently during the application of the LPT feature.
Issue 02 (2009-02-25)
26-1

LPT is a service-based protection scheme, supporting the Ethernet line service of the point-topoint and point-to-multipoint. The link state pass through (LPT) is used to detect and report the faults that occur at the service access node and in the intermediate transmission network. The LPT notifies the equipment at two ends in the transmission network of starting the backup network at the earliest time for communication, thus making sure the normal transmission of the important data.
LPT Application
As a link-based protection scheme, the LPT passes through states of the point-to-point link and point-to-multipoint link. In this way, the LPT makes sure the network level protection for the transmission of point-to-point private line services and for the transmission of the point-tomultipoint convergence services.
l
The following description is based on the point-to-point networking. Figure 26-1 shows the point-to-point networking.
Figure 26-1 Point-to-Point LPT networking diagram
Backup network
Service Network Router A Access NE1 Node Link 1 Working Link Protection Link
NE2
Access Node Link 2
Router B
In normal situations, data of router A and router B is exchanged over the network service equipment. In the diagram preceding, the network equipment refers to the Huawei OptiX RTN equipment, namely NE1 and NE2. When faults occur at the link between router A and router B, the communication between router A and router B is interrupted. For the important user, 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 network to make sure the communication.
When the LPT function is enabled, the OptiX equipment detects and reports the faults at the service access node and in the intermediate network. Then the data communication equipment such as routers switches to the backup network at the earliest time for communication, thus making sure the normal transmission of the important data.
l
The following description is based on the point-to-multipoint networking. Figure 26-2 shows the point-to-multipoint networking.
Figure 26-2 Point-to-Multipoint LPT networking diagram
Backup network
Port1 Port3 Service network NE2
Port2
Router B
Port1 Router A NE1
Port2 Port1
Port2 Port3 NE3 Backup network Router C
Protection link Working link
Router D
Normally, the data among router A, router B, router C and router D is transmitted through a server network. When the link between router A and NE1 becomes faulty, router A fails to communicate with router B, router C and router D. When the link fault occurs, the important data of VIP users must still be normally transmitted. Hence, the system should detect and notify the fault in time, and start the backup network to retain communication.
LPT Capability
When the LPT function is enabled, the notification interval is less than two seconds after the fault occurs.
LPT Bearer Mode

To meet a condition that the LPT frame can pass through different Layer 2 networks, the LPT is defined at Layer 2.5. In this case, the LPT can be carried by the medium access control (MAC) frame and generic framing procedure (GFP) management frame.
The LPT bearer mode varies with the different LPT packets. When the bearer mode of the received LPT packets is not consistent with that of the equipment at the receive end, the LPT packet is discarded.
26.2 Availability
The LPT feature requires the support of the applicable equipment and boards. Table 26-1 Availability of the LPT feature Feature Point-to-point LPT feature Point-to-multipoint LPT feature Applicable Board SL61EFT4VER.B SL61EMS6VER.B SL61EMS6VER.B Applicable Equipment IDU 610/620 IDU 620 IDU 620

LPT only used in the Ethernet private line service of the point-to-point and point-to-multipoint. The Ethernet port supports the auto-negotiation function. The EMS6 board can only support LPT in Ethernet Over SDH, and can not support LPT in Native Ethernet.

LPT is realized by transmitting different packets that varies according to different types of faults. 26.4.1 Point-to-Point Service In the case of a point-to-point service, the LPT function is realized differently in the following two scenarios: the access point is faulty and the transmission network is faulty. 26.4.2 Point-to-Multipoint Service In the case of a point-to-multipoint service, the LPT function is realized differently in the following two scenarios: the access point is faulty and the transmission network is faulty.
26.4.1 Point-to-Point Service

In the case of a point-to-point service, the LPT function is realized differently in the following two scenarios: the access point is faulty and the transmission network is faulty.
Point-to-Point LPT Service Network Fault

l
Fault locating
Access Node 1 Service Equipment A Broken Service Network Broken Service Equipment B Access Node 2
26-4
Issue 02 (2009-02-25)
Both service equipment A and B detect that the service network is unavailable and then transmit the Broken packets to the opposite ends respectively. At the same time, equipment A and B cut the connection to local users.
NOTE
If the service network fault is bidirectional, service equipment A and B can detect the fault in the service network. As a result, either of the two sets of the equipment can cut the connection between the local end and the user, and transmit the Broken packets to the opposite end at the same time. If the service network fault is unidirectional, for example, if the link in the direction from service equipment A to B is faulty, only service equipment A can detect the service network fault. In this case, service equipment A cuts the connection between the local end and access node 1 and transmits the Broken packets to equipment B in the direction from equipment A to B over the service network where no fault occurs. After receiving the Broken packets, service equipment B cuts the connection between the local end and access node 2. In this way, the fault in the service network is detected. According to different transmission modes, the Broken packets can be transmitted through specific GFP management frames or MAC frames.
l l
Link restoration
Non_ Broken Non_ Broken Service Equipment B
Access Node 1
Service Equipment A
Service Network
Access Node 2
Both service equipment A and B detects that the service network is recovered, and then notify the opposite end that the link is recovered by transmitting the Non_Broken packets respectively. At the same time, equipment A and B recover the connection with local users.
Access Node 1
Service Equipment A
Service Network
Service Equipment B
Access Node 2
Service equipment A and B recovers the local link when any of the following condition is satisfied. 1. Equipment A and B receive the Non_Broken packets transmitted by the opposite ends respectively. 2. Timeout occurs for waiting the Broken frame.
Point-to-Point LPT Access Node Link Fault

l
Fault locating
Report the link fault alarm Access Node 1 Service Equipment A Service Network Broken Disconnect the link and report the LPT_RFI alarm Service Equipment B Access Node 2
1.
Service equipment A detects that the link at the access node is faulty, and then reports the alarm of the fault that occurs at the local end. At the same time, equipment A transmits the Broken control frame to equipment B.
Issue 02 (2009-02-25)
2.
l
After receiving the Broken control frame, service equipment B disconnects the local end and reports the LPT_RFI alarm at the same time. Link restoration
Clear the link fault alarm Service Network Service Equipment A Non_Broken Service Equipment B Recover the link Access Node 2
Access Node 1
1. 2.
Service equipment A detects that the link at the access node is recovered, and then transmits the Non_Broken control frame to service equipment B. After receiving the Non_Broken control frame, service equipment B recovers the connection at the local end.
26.4.2 Point-to-Multipoint Service

In the case of a point-to-multipoint service, the LPT function is realized differently in the following two scenarios: the access point is faulty and the transmission network is faulty.
Prerequisite
NOTE
The point-to-multipoint LPT function processes faults in unidirectional service network and bidirectional service network by using the same means.
Point-to-Multipoint LPT Service Network Fault

l
Fault locating
Disconnect the link and report the LPT_RFI alarm Broken Service Equipment B Access Node 1
Disconnect the link and report the LPT_RFI alarm Convergence Node Service Equipment A
Broken
Disconnect the link and report the LPT_RFI alarm Service Access Equipment Node 2 C
The bidirectional fault occurs in the service network between service equipment A and B. In this case, equipment A and B cut the local connections respectively and report the LPT_RFI alarms. At the same time, equipment A transmits the Broken packets to equipment C. In this case, service equipment C cuts the local connection and reports the LPT_RFI alarm.
l
Link restoration
26-6
Issue 02 (2009-02-25)

Recover the link and clear the LPT_RFI alarm Service Access Equipment Node 1 B Recover the link and clear the LPT_RFI alarm Service Access Equipment Node 2 C
Recover the link and clear the LPT_RFI alarm Convergence Node Service Equipment A
Non_Broken
Non_Broken
The bidirectional fault is cleared in the service network between service equipment A and B. In this case, equipment A and B recovers the local connections respectively and report the clearance of the LPT_RFI alarms. At the same time, equipment A transmits the Non-Broken packets to equipment C. In this case, service equipment C recovers the connection to the local end and then reports the clearance of the LPT_RFI alarm.
Point-to-Multipoint LPT Access Node Link Fault at the Convergence Node Side
l
Fault locating
Disconnect the link and report the LPT_RFI alarm Report the link fault alarm Convergence Node Broken Service Equipment A Broken Service Equipment B Access Node 1
Disconnect the link and report the LPT_RFI alarm Service Access Equipment Node 2 C
Service Equipment A that connects to the convergence node detects that the link at the access node is faulty, and then reports the alarm of the fault that occurs at the local end. At the same time, service equipment A transmits Broken packets to service equipment B and C. After receiving the packets, equipment B and C disconnect the local end. In this case, equipment B and C report the LPT_RFI alarms.
l
Link restoration
Service Equipment B Recover the link Access Node 1
Non_Broken Clear the link fault alarm Service Convergence Equipment Node A Non_Broken
Service Equipment C
Recover the link
Access Node 2
Service Equipment A that connects to the convergence node detects the link restoration at the access nod, and then reports the clearance of the local fault alarm. At the same time, service equipment A transmits Non-Broken packets to service equipment B and C. After receiving the
packets, equipment B and C recover the connections to the local end. In this case, equipment B and C report the clearance of LPT_RFI alarms.
Point-to-Multipoint LPT Access Node Link Fault at the Access Node Side
l
Scenario 1
Fault locating
Disconnect the link and report the LPT_RFI alarm Service Equipment B Report the link fault alarm Access Node 1
Broken Service Equipment A Broken
Convergence Node
Service Equipment C
Report the link fault alarm Access Node 2
1.
Service equipment B that connects to access node 1 detects that the link at the access node is faulty, and then reports the alarm of the local access node fault. At the same time, equipment B transmits the Broken packets to service equipment A. After receiving the packets, equipment A reports the LPT_RFI alarm and transmits the Broken packets to equipment C at the same time. In this case, service equipment C disconnects the local end and reports the LPT_RFI alarm. Link restoration
Service Equipment B Clear the link fault alarm Access Node 1
2. 3.
Convergence Node
Recover the link
Non_Broken Service Equipment A Non_Broken
Service Equipment C
Recover the link
Access Node 2
1.
Service equipment B that connects to access node 1 detects that the link at the access node is restored, and then reports the clearance of the local fault alarm. At the same time, equipment B transmits the Non-Broken packets to service equipment A. After receiving the packets, equipment A recovers the connection to the local end and then reports the clearance of the LPT_RFI alarm. At the same time, equipment A transmits the Broken packets to equipment C. In this case, service equipment C recovers the connection to the local end and then reports the clearance of the LPT_RFI alarm. Fault locating
2.
3.
l
Scenario 2
26-8
Issue 02 (2009-02-25)

Disconnect the link and report the LPT_RFI alarm Convergence Node Service Equipment A Broken
Service Equipment B
Access Node 1 Report the link fault alarm Access Node 2
Service Equipment C
Access Node 3
Service equipment C that connects to access node 2 detects that the link at the access node is faulty, and then reports the alarm of the fault that occurs at the local end. At the same time, equipment C transmits the Broken packets to service equipment A. In this case, service equipment A disconnects the local end and reports the LPT_RFI alarm.
Disconnect the link and report the LPT_RFI alarm Broken Convergenc e Node Service Equipment A Broken_Ack Service Equipment C Service Equipment B Access Node 1
Access Node 2
Access Disconnect the Node 3 link and report the LPT_RFI alarm
After receiving the Broken packets where the response confirmation frame is contained, service equipment A transmits the Broken packets to service equipment B. After receiving the Broken_Ack packets, service equipment C disconnects the access node 3 and reports the LPT_RFI alarm. After recovering the Broken packets from equipment A, service equipment B disconnects the local end and reports the LPT_RFI alarm.
Link restoration
Recover the link and clear the LPT_RFI alarm Service Equipment B Service Equipment A Non_Broken Service Equipment C Recover the link Access Node 1
Convergence Node
Access Node 2
Access Node 3
Service Equipment C that connects to the access node 2 detects the link at the access node is restored, and then reports the clearance of the fault alarm at the local end. At the same
time, service equipment C transmits Non-Broken packets to service equipment A. After receiving the packets, equipment A recovers the local connection and reports the clearance of the LPT_RFI alarm.
Recover the link and clear the LPT_RFI alarm Access Node 1
Non_Broken Convergence Node Service Equipment A Non_Broken_Ack
Service Equipment B
Service Equipment C Recover the link and clear the LPT_RFI alarm
Access Node 2
Access Node 3
After receiving the Non_Broken packets where the response confirmation frame is contained, service equipment A transmits the Non_Broken packets to service equipment B. After receiving the Non_Broken_Ack packets, service equipment C recovers the connection to access node 3 and reports the clearance of the LPT_RFI alarm. After recovering the Non_Broken packets from equipment A, service equipment B disconnects the local end and reports the clearance of the LPT_RFI alarm.
26.5 Planning Guide

You need to plan the LPT according to the specific service.
Prerequisite
You must have an understanding of the specific application of the LPT.
Context
NOTE
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. Therefore, you can select only one configuration mode to realize the LPT function.
Procedure
Step 1 According to the actual requirements, plan the type of the private line service. l l l The configured data services are of the transparent transmission type. In the case of the point-to-point service, it is recommended to use the Ethernet transparent transmission service. Before you configure the point-to-multipoint service, the data service must be of the tree topology, which is the same as the topology of the LPT.
Step 2 Plan the direction in which the service is transparently transmitted. l This parameter is valid only when you configure a point-to-point LPT. It indicates the direction of the EPL services that are transparently transmitted on the port.
26-10
In the case of a pair of the PORT port and VCTRUNK port, you can set the direction to positive or negative. When the source port is a PORT port and the sink port is a VCTRUNK port, the direction is positive. When the source port is a VCTRUNK port and the sink port is a PORT port, the direction is negative.
Step 3 Plan the delay time for a PORT port or a VCTRUNK port. l l You can set Prot-Type Port Hold-Off Time(ms) and VCTRUNK Port Hold-Off Time (ms) only when the LPT pass-through is enabled. When the LPT switching is enabled, the port informs the opposite end after the hold-off time.
Step 4 Plan the port for the convergence point. l l l l The port for the convergence point is applicable to the point-to-multipoint LPT. The port for the convergence point can be set to a PORT or VCTRUNK port. When the port for the convergence point is set to a PORT port, the port for the access point is a VCTRUNK port. When the port for the convergence point is set to a VCTRUNK port, the port for the access point is a PORT port.
Step 5 Plan the carrying mode. l l l The carrying mode can be set to GFP or MAC carrying mode. You can select a value as required. When the port for the convergence point is set to a PORT port, the Bearer Mode parameter does not need be set. When the port for the convergence point is set to a VCTRUNK port, you need to set the Bearer Mode parameter.
Step 6 Plan the port for the access point. l l l l The port for the access point is applicable to the point-to-multipoint LPT. The port for the access point can be set to a PORT or VCTRUNK port. When the port for the access point is set to a PORT port, the port for the convergence point is a VCTRUNK port. When the port for the access point is set to a VCTRUNK port, the port for the convergence point is a PORT port.
----End
26.6 LPT Configuration

When enabling the LPT function for an Ethernet service, you need to configure the LPT port and the related information.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The Ethernet data board supports the LPT function. The port-based Ethernet private line service must be created and activated.
The data service is configured as the pure transparent service.
Precautions
NOTE
l l
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On one board, you can select only one configuration mode to realize the LPT function. The data service of the point-to-point LPT is configured as the pure transparent service.
CAUTION
Before configuring the point-to-multipoint LPT function, make sure that the following two conditions are met. Otherwise, the services may be interrupted.
l l
The data services are displayed in the tree topology. The data service topology is consistent with that of the LPT.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Interface Management > LPT Management from the Function Tree. Step 2 Optional: Configuring Point-to-Point LPT. 1. 2. Click Query. The Operation Result dialog box is displayed. Click Close. Select a PORT and a VCTRUNK port, and then set the following parameters.
NOTE
If LPT is enabled, you can set Prot-Type Port Hold-Off Time(ms) and VCTRUNK Port HoldOff Time(ms) as required.
3. 4. 5.
Click Apply and a prompt appears telling you the operation was successful. Click Close. Repeat Steps 1 through 2 to configure point-to-point LPT for the opposite NE.
Step 3 Optional: Configuring Point-to-Multipoint LPT. 1. 2. 3. Click Advanced Configuration. In the LPT Management window, click New. In the Create LPT window, select Port from the Convergence Point pane, and set HoldOff Time(ms).
26-12
Issue 02 (2009-02-25)
NOTE
If the port at the convergence point is a VCTRUNK port, you need to set Bearer Mode.
4.
In the Access Point pane, select an appropriate Port and click . Double-click Bearer Mode and select an appropriate bearer mode from the drop-down list.
NOTE
l l
If the port at the convergence point is not a VCTRUNK port, do not set Bearer Mode. If you want to modify Bearer Mode, you can modify it in the Modify LPT window.
5. 6.
Click OK. Click Close in the Operation Result dialog box. Repeat Steps 1 and Steps 3 to configure point-to-multipoint LPT for other NEs.
----End
Parameter
Table 26-2 Parameter of the Point-to-Point LPT Field Port Value For example: PORT1 For example: VCTRU NK1 Default Description The external port of board.
VCTRUNK Port
The VCTRUNK port where EPL services are transparently transmitted.
Issue 02 (2009-02-25)
26-13
Field Direction
Value Positive, Reverse
Default -
Description The direction of the EPL services that are transparently transmitted. The direction is Positive if the source port is a PORT port and the sink port is a VCTRUNK port. The direction is Reverse if the source port is a VCTRUNK port and the sink port is a PORT port.
LPT Bearer Mode
Yes, No GFP (HUAW EI), Ethernet 0 to 10000
No GFP(HUAWEI)
Sets whether to use LPT. This parameter is valid only when the LPT occurs. The bearer mode of LPT frames.
Port-Type Port Hold Off Time(ms)
100
This parameter is valid only when the LPT occurs. When the LPT switching is enabled, the port informs the opposite end after the hold-off time.
VCTRUNK Port Hold Off Time(ms)
0 to 10000
100
This parameter is valid only when the LPT occurs. When the LPT switching is enabled, the port informs the opposite end after the hold-off time.
Table 26-3 Parameter of the Point-to-Multipoint LPT Field Convergence Point Port Value PORT1 to PORT6, VCTRUNK1 to VCTRUNK8 GFP (HUAWEI), Ethernet Default PORT1 Description The port where the convergence point resides. The bearer mode of the port where the access point resides. This parameter can be edited only when it is supported by a board.
Bearer Mode
GFP (HUAWEI)
26-14
Issue 02 (2009-02-25)
Field Hold Off Time (ms)
Value 0 to 10000
Default 0
Description If LPT switching is enabled, the port notifies the opposite end after the holdoff time. The port where the access point resides. The bearer mode of the port where the access point resides. This parameter can be edited only when it is supported by a board.
Access Point
Port
PORT1 to PORT6, VCTRUNK1 to VCTRUNK8 GFP (HUAWEI), Ethernet
Bearer Mode
GFP (HUAWEI)

This topic describes the alarms and performance events relevant to the LPT feature, and the problems that occur frequently during the application of the LPT feature. 26.7.1 Relevant Alarms and Events If the LPT function detects a service network fault or an NE receives a notification of an LPT fault, the NE reports the corresponding alarm. 26.7.2 FAQs This topic lists the problems that occur frequently during the application of the LPT feature.

If the LPT function detects a service network fault or an NE receives a notification of an LPT fault, the NE reports the corresponding alarm.
Relevant Alarms
l
LPT_INEFFECT The LPT_INEFFECT alarm indicates that the LPT function fails. When the LPT function is configured on a board that does not support the LPT function, the system reports this alarm.
LPT_RFI
Issue 02 (2009-02-25)
26-15
The LPT_RFI alarm indicates a remote LPT failure. When the LPT function detects that the remote port fails or the LPT service network where the remote port exists fails, the system reports this alarm.

None.
26.7.2 FAQs
This topic lists the problems that occur frequently during the application of the LPT feature. None.
26-16
Issue 02 (2009-02-25)
27 Synchronous Ethernet
27
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. 27.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 line and transmit data by using the clock signal to realize the transfer of the clock signal. 27.2 Availability The synchronous Ethernet feature requires the support of the applicable equipment and boards. 27.3 Relation with Other Features The synchronous Ethernet feature does not affect the other features. 27.4 Realization Principle The realization of the synchronous Ethernet feature complies with ITU-T G.8261. 27.5 Planning Guide Plan the synchronous Ethernet according to the actual application. 27.6 Configuration Guide By default, the NEs consider that all the Ethernet links provide the clock signal. Hence, you need only to configure the clock source for the NEs that require the synchronous Ethernet clock. 27.7 Maintenance Guide This topic describes the maintenance operations and alarms that are related to the synchronous Ethernet feature, and the problems that occur frequently during the application of the synchronous Ethernet feature.
Issue 02 (2009-02-25)
27-1

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 line and transmit data by using the clock signal to realize the transfer of the clock signal.
Application of the Synchronous Ethernet

The OptiX RTN 600 radio transmission system provides the mobile communication network with backhaul links. Currently, the synchronous Ethernet links are used to transfer the clock signal in the wireless access network so that the reliable transfer of the clock signal is ensured. As shown in Figure 27-1, the synchronous Ethernet provided by the microwave transmission equipment realizes the transfer of the timing information between the RNC equipment and node B. Figure 27-1 Application of the synchronous Ethernet in the wireless access network
NE2 FE Node B FE/GE NE1
FE
RNC
Ethernet clock signal Node B Ethernet link
Performance of the Synchronous Ethernet

The synchronous Ethernet complies with ITU-T G.8261. The clock signal recovered by the synchronous Ethernet meets the requirement of 50 ppb frequency accuracy.
27.2 Availability
The synchronous Ethernet feature requires the support of the applicable equipment and boards. Table 27-1 Availability of the synchronous Ethernet feature Feature Synchronous Ethernet feature Applicable Board IFH2 (all the versions) Applicable Equipment IDU 620 IDU 605 1F/2F
Issue 02 (2009-02-25)
27-2

The synchronous Ethernet feature does not affect the other features.

The realization of the synchronous Ethernet feature complies with ITU-T G.8261. As shown in Figure 27-2, the microwave equipment performs the following operations to realize the synchronous Ethernet function: 1. 2. The data sub-system extracts the clock information (namely, recovery clock) from the packets that the upstream Ethernet port receives. The data sub-system sends the Ethernet recovery clock to the clock processing module. Then, the clock processing module locks the Ethernet recovery clock to the local system clock and provides the system synchronous clock. The system synchronous clock provides a reference clock for the other modules of the system and the services (for example, microwave services or node B that is interconnected with the downstream Ethernet port) so that the system is synchronized with the Ethernet.
3.
Issue 02 (2009-02-25)
27-3
Figure 27-2 Realization principle of the synchronous Ethernet
Microwave services
Orderwire NMS ...
CPU sub-system
IF sub-system
Orderwire and auxiliary interface module
Other modules
System synchronous clock
Local system clock Clock processing module
Ethernet recovered clock Ethernet services Data sub-system
27.5 Planning Guide

Plan the synchronous Ethernet according to the actual application.
Prerequisite
You must be familiar with the function and application of the synchronous Ethernet.
27-4
Issue 02 (2009-02-25)
Procedure
Select the board that accesses the Ethernet clock as the current clock source of the NE according to the actual networking situation. Adhere to the following principles:
l
In the case of NE1 that uses the Ethernet board to access the upstream clock source (RNC), select the clock source recovered by the Ethernet board as the current clock source of NE1. For details, see Figure 27-1. In the case of NE2 that transfers the clock source through the radio link, select the clock source recovered by the IF board that accesses the microwave services as the current clock source of NE2. For details, see Figure 27-1.
----End

By default, the NEs consider that all the Ethernet links provide the clock signal. Hence, you need only to configure the clock source for the NEs that require the synchronous Ethernet clock.
l
In the case of the IDU 620, see 27.6.1 Configuring the Clock Sources to configure the Ethernet clock source. In the case of the IDU 605 1F/2F, see 27.6.2 Configuring the Ethernet Clock Source to configure the Ethernet clock source.
27.6.1 Configuring the Clock Sources This topic describes how to configure the clock source according to the planned the clock synchronization scheme, thus ensuring that all the NEs in a network trace the same clock. 27.6.2 Configuring the Ethernet Clock Source Configure the Ethernet clock source of the IDU 605 1F/2F according to the planned clock synchronization strategy to ensure that all the NEs in the network trace the same clock.
27.6.1 Configuring the Clock Sources

This topic describes how to configure the clock source according to the planned the clock synchronization scheme, thus ensuring that all the NEs in a network trace the same clock.
Prerequisite
You must be an NM user with "NE operator" authority or higher. That is, you must be an NE user with "Operation Level" authority or higher. The PXC boards and input/output clock source boards must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock Source Priority from the Function Tree. Step 2 Click Create. The Add Clock Source dialog box is displayed.
Step 3 Select the clock sources.
TIP
By pressing the Ctrl key, you can select multiple clock sources at one time.
Step 4 Click OK. Step 5 Optional: Repeat Step 2 to Step 4 to add other clock sources. Step 6 Optional: Select a clock source and click or to adjust the priority level of this clock source. The clock priority levels are arranged in the descending order from the first row to the last row. The internal clock source is fixed with the lowest priority. Step 7 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external clock sources.
27-6
Issue 02 (2009-02-25)
Parameters
Parameter Clock Source Value Range Default Value Description
l
External clock source 1 indicates the external clock source at the port of the PXC board in slot 1. External clock source 2 indicates the external clock source at the port of the PXC board in slot 3. IFH2-1(SDH) indicates the microwave clock source. IFH2-2(ETH) indicates the clock source of the synchronous Ethernet. The internal clock source is fixed with the lowest priority and indicates that the NE works in the free-run mode. Determine the clock sources and the corresponding clock source priority levels according to the clock synchronization schemes. This parameter indicates the type of the external clock source signal. Set this parameter depending on the external clock signal. Generally, the external clock signal is a 2 Mbit/s signal. This parameter is valid only when External Clock Source Mode is set to 2 Mbit/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 need to be set only when the SSM or extended SSM is enabled. Generally, the external clock sources use the SA4 to pass the SSM.
External Clock Source Mode
2 Mbit/s, 2 MHz
2 Mbit/s
Synchronization Status Byte
SA4SA8
SA4
27.6.2 Configuring the Ethernet Clock Source

Configure the Ethernet clock source of the IDU 605 1F/2F according to the planned clock synchronization strategy to ensure that all the NEs in the network trace the same clock.
Prerequisite
Issue 02 (2009-02-25)
27-7
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock Source Priority from the Function Tree. Step 2 Set Use the clock source of the data port. Step 3 Click Apply. ----End
Parameters
Parameter Use the clock source of the data port Value Range Yes, No Default Value No Description When this parameter is set to Yes, the IDU 605 1F/2F traces the clock source that is recovered from the signal flow on the Ethernet PORT.

This topic describes the maintenance operations and alarms that are related to the synchronous Ethernet feature, and the problems that occur frequently during the application of the synchronous Ethernet feature. 27.7.1 Checking the Clock Synchronization Status You can know the current running status of a clock and the traced clock source information by checking the clock synchronization status. 27.7.2 Relevant Alarms and Events If an abnormality occurs when the Ethernet link functions as the clock source, the NE reports the corresponding alarm. 27.7.3 FAQs This topic lists the problems that occur frequently during the application of the synchronous Ethernet feature.
27.7.1 Checking the Clock Synchronization Status

You can know the current running status of a clock and the traced clock source information by checking the clock synchronization status.
Prerequisite
l l
The communication between the Web LCT and the NE must be normal. You must be an NM user with "NE monitor" authority or higher.
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer. Step 2 Choose Configuration > Clock > Clock Synchronization Status from the Function Tree.
Step 3 Click Query to query the clock synchronization status of the NE. ----End

If an abnormality occurs when the Ethernet link functions as the clock source, the NE reports the corresponding alarm.
Relevant Alarms
l
EXT_SYNC_LOS The EXT_SYNC_LOS alarm indicates that the external clock source is lost. If the Ethernet clock is configured as an external clock source in the clock source priority list, the system reports this alarm when the system detects that the external clock source does not exist or fails.
LTI The LTI alarm indicates the loss of synchronization source.When all the synchronization sources of an NE (including the Ethernet clock source) are lost, the NE reports this alarm.

None.
27.7.3 FAQs
This topic lists the problems that occur frequently during the application of the synchronous Ethernet feature. Q: Does the synchronous Ethernet support the transmission of the clock quality information? A: The synchronous Ethernet does not support the transmission of the clock quality information because the Hybrid microwave does not support the transmission of the S1 byte.
Issue 02 (2009-02-25)
27-9
28 Glossary
28
Terms are listed in an alphabetical order. A ACAP ATPC AM
Glossary
The Adjacent Channel Alternate Polarization (ACAP) operation provides orthogonal polarizations between two adjacent communication channels. Automatic Transmit Power Control. A method of automatically adjusting the transmit power at the opposite end based on the transmit signal detected at the receiver. Refers to the adaptive modulation (AM) technology that implements automatic adjustment of the coding scheme and modulation scheme.
C CCDP The co-channel dual polarization (CCDP) operation provides two parallel communication channels over the same link with orthogonal polarizations, thus doubling the link capacity.
E ETH-OAM Being in compliance with the MAC-layer protocol, the ETH-OAM function checks the Ethernet link by transmitting the OAM protocol packet.
F FD Frequency Diversity. Two or more microwave frequencies with certain frequency space are used to transmit/receive the same signal and selection is then performed between the two signals to ease the impact of fading.
Issue 02 (2009-02-25)
28-1
28 Glossary
Hybrid microwave
Refers to the microwave system that can transmit mixed E1 and Ethernet services, never changes the feature of the E1 and Ethernet services in transmission.
I IDU IGMP Indoor Unit. The indoor unit implements accessing, multiplexing/ demultiplexing, and IF processing for services. Internet Group Management Protocol. The Protocol is used by IPv4 systems (hosts and routers) to report their IP multicast group memberships to any neighboring multicast routers. IGMP Snooping is the process of listening to IGMP traffic. IGMP snooping, as implied by the name, is a feature that allows the switch to "listen in" on the IGMP conversation between hosts and routers by processing the layer 3 IGMP packets sent in a multicast network.
IGMP Snooping
L LCAS Link Capacity Adjustment Scheme. A solution features flexible bandwidth and dynamic adjustment. In addition, it provides a failure tolerance mechanism, which enhances the viability of virtual concatenations and enables the dynamic adjustment to bandwidth (non-service affecting).
M MSP Multiplex section protection. The function performed to provide capability for switching a signal between and including two MST functions, from a "working" to a "protection" channel.
N N+1 protection A microwave link protection system that employs N working channels and one protection channel.
O ODU QoS Outdoor Unit. The outdoor unit implements frequency conversion and amplification for RF signals. Indicates the quality of Ethernet services.
P PDH Plesiosynchronous Digital Hierarchy. 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.
28-2
Issue 02 (2009-02-25)
28 Glossary
Q QinQ The QinQ, a Layer 2 tunnel protocol developed based on the IEEE 802.1Q encapsulation, allows for individual VLANs with extra tag information to traverse the backbone networks and thus provides Layer 2 VPN tunnels for users.
R RSTP Rapid Spanning Tree Protocol. The protocol is an evolution of the Spanning Tree Protocol, providing for faster spanning tree convergence after a topology change.
S SD Space Diversity. Two or more antennas separated by a specific distance 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. Synchronous Digital Hierarchy. A hierarchical set of digital transport structures, standardized for the transport of suitably adapted payloads over physical transmission networks. Subnetwork connection protection. A working subnetwork connection is replaced by a protection subnetwork connection if the working subnetwork connection fails, or if its performance falls below a required level. The Spanning Tree Protocol (STP), defined in the IEEE Standard 802.1D, is an OSI layer-2 protocol that ensures a loop free topology for any bridged LAN.
SDH
SNCP
STP
T T2000 A subnet management system (SNMS). In the telecommunication management network architecture, the T2000 is located between the NE level and network level, which can supports all NE level functions and part of the network level management functions.
Issue 02 (2009-02-25)
28-3
29 Acronyms and Abbreviations
29
A AM APS ARP ATPC AU
Acronyms and Abbreviations
Acronyms and abbreviations are listed in alphabetical order.
Adaptive Modulation Automatic Protection Switching Address Resolution Protocol Automatic Transmit Power Control Administrative Unit
B BER BIP BPDU Bit Error Rate Bit-Interleaved Parity Bridge Protocol Data Unit
C CAR CBS CCDP CGMP CIR CLNP CLNS CoS CPU Committed Access Rate Committed Burst Size Co-Channel Dual Polarization Cisco Group Management Protocol committed information rate connectionless network protocol Connectionless Network Service Class of Service Central Processing Unit
Issue 02 (2009-02-25)
29-1
CRC CVLAN C-VLAN
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 EPL EPLAN ES-IS EVPL Embedded Control Channel Ethernet Private Line Ethernet Private LAN End System to Intermediate System Ethernet Virtual Private Line
F FCS FD FE FIFO FLP FTP Frame Check Sequence Frequency Diversity Fast Ethernet First In First Out Fast Link Pulse file transfer protocol
G GE GFP GTS GUI Gigabit Ethernet Generic Framing Procedure Generic Traffic Shaping Graphical User Interface
29-2
Issue 02 (2009-02-25)
H HDLC HSB HSM High level Data Link Control procedure Hot Standby Hitless Switch Mode
I ICMP IDU IEEE IETF IF IGMP IP IPv6 IS-IS ISO ITU-T IVL Internet Control Message Protocol Indoor Unit 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 LAPS LCAS LCT LMSP Local Area Network Link Access Procedure on the D channel Link Access Procedure-SDH Link Capacity Adjustment Scheme Generation-Local Craft Terminal Linear Multiplex Section Protection
M MAC MBS MDI MIB

Issue 02 (2009-02-25)
Medium Access Control Maximum Burst Size Medium Dependent Interface Management Information Base
MPLS MSP MTU
multiprotocol label switching Multiplex Section Protection 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
O ODU OSI OSPF Outdoor Unit Open Systems Interconnection Open Shortest Path First
P PDH PIM-DM PIM-SM PPP Plesiochronous Digital Hierarchy Protocol Independent Multicast-Dense Mode Protocol Independent Multicast-Sparse Mode Point-to-Point Protocol
Q QinQ QoS 802.1Q in 802.1Q Quality of Service
R RF RFC RIP RMON RSL radio frequency Request For Comment Routing Information Protocol Remote Monitoring Received Signal Level
29-4
Issue 02 (2009-02-25)
RSTP RTN
Rapid Spanning Tree Protocol Radio Transmission Node
S SD SDH SNC SNCP SNMP SNR STM STM-1 STM-1e STM-1o STM-4 STM-N STP SVL Space Diversity Synchronous Digital Hierarchy SubNetwork Connection Sub-Network Connection Protection Simple Network Management Protocol Signal-to-Noise Ratio Synchronous Transport Module SDH Transport Module -1 STM-1 Electrical Interface STM-1 Optical Interface SDH Transport Module -4 SDH Transport Module -N Spanning Tree Protocol Shared VLAN Learning
T TCI TCP TU Tag Control Information Transfer Control Protocol Tributary Unit
U UDP UNI User Datagram Protocol user-network interface
V VC VC12 VC-12 Virtual Container Virtual Container -12 Virtual Container -12
Issue 02 (2009-02-25)
29-5
VC3 VC-3 VC4 VC-4 VCG VLAN VoIP VPN
Virtual Container -3 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
29-6
Issue 02 (2009-02-25)

RTN 620 Feature

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

RTN 620 Feature

Încărcat de

Drepturi de autor:

Formate disponibile

OptiX RTN 600 Radio Transmission System V100R003

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

Huawei Technologies Co., Ltd.

Trademarks and Permissions

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

OptiX RTN 600 Radio Transmission System Feature Description

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

OptiX RTN 600 Radio Transmission System Feature Description

4 OSI over DCC Solution.............................................................................................................4-1

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

OptiX RTN 600 Radio Transmission System Feature Description

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

OptiX RTN 600 Radio Transmission System Feature Description

10 Cross-Polarization Interference Cancellation...................................................................10-1

OptiX RTN 600 Radio Transmission System Feature Description

12 Automatic Transmit Power Control Function..................................................................12-1

14 Sub-Network Connection Protection.................................................................................14-1

15 Linear Multiplex Section Protection...................................................................................15-1

OptiX RTN 600 Radio Transmission System Feature Description

16 Two-Fiber Bidirectional Ring MSP....................................................................................16-1

17 Features of Ethernet Ports.....................................................................................................17-1

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

OptiX RTN 600 Radio Transmission System Feature Description

18 Encapsulation and Mapping of Ethernet Services...........................................................18-1

OptiX RTN 600 Radio Transmission System Feature Description

23 Remote Monitoring Feature.................................................................................................23-1

OptiX RTN 600 Radio Transmission System Feature Description

OptiX RTN 600 Radio Transmission System Feature Description

26 Link State Pass Through.......................................................................................................26-1

OptiX RTN 600 Radio Transmission System Feature Description

29 Acronyms and Abbreviations..............................................................................................29-1

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

OptiX RTN 600 Radio Transmission System Feature Description

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

OptiX RTN 600 Radio Transmission System Feature Description

OptiX RTN 600 Radio Transmission System Feature Description

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

OptiX RTN 600 Radio Transmission System Feature Description

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

OptiX RTN 600 Radio Transmission System Feature Description

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

OptiX RTN 600 Radio Transmission System Feature Description

About This Document

About This Document

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

About This Document

OptiX RTN 600 Radio Transmission System Feature Description

Chapter 3 IP over DCC Solution

4 OSI over DCC Solution

10 Cross-Polarization Interference Cancellation 11 N+1 Protection

12 Automatic Transmit Power Control Function 13 Hybrid Microwave

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

OptiX RTN 600 Radio Transmission System Feature Description

About This Document

Chapter 17 Features of Ethernet Ports

18 Encapsulation and Mapping of Ethernet Services 19 VLAN

21 QoS 22 QinQ 23 Remote Monitoring Feature 24 ETH OAM

25 Link aggregation 26 Link State Pass Through 27 Synchronous Ethernet

28 Glossary 29 Acronyms and Abbreviations

About This Document

OptiX RTN 600 Radio Transmission System Feature Description

Updates in Issue 02 (2009-02-25)

Updates in Issue 01 (2008-09-20)