RTN 600-Feature Description(V100R002_02)

OptiX RTN 600 Radio Transmission System

V100R002

Feature Description

Issue 02

Date 2008-06-20

Part Number 00425658

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For anyassistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright © Huawei Technologies Co., Ltd. 2008. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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. NoticeThe information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

http://www.huawei.com

mailto:[email protected]

Contents

About This Document ....................................................................................................................1

1 Introduction to the DCN...........................................................................................................1-11.1 Constitution of the DCN.................................................................................................................................1-21.2 Huawei DCN Solution....................................................................................................................................1-3

2 HW ECC Solution......................................................................................................................2-12.1 Feature Description.........................................................................................................................................2-2

2.1.1 HW ECC Protocol Stack........................................................................................................................2-22.1.2 Extended ECC........................................................................................................................................2-4

2.2 Availability......................................................................................................................................................2-62.3 Relation with Other Features...........................................................................................................................2-72.4 Realization Principle.......................................................................................................................................2-7

2.4.1 How to Establish ECC Routes...............................................................................................................2-72.4.2 How to Transfer Messages.....................................................................................................................2-92.4.3 Extended ECC......................................................................................................................................2-10

2.5 Planning Guide..............................................................................................................................................2-102.6 Configuration Guide......................................................................................................................................2-14

2.6.1 Configuration Flow..............................................................................................................................2-142.6.2 Modifying the NE ID...........................................................................................................................2-162.6.3 Modifying the Communication Parameters of an NE..........................................................................2-182.6.4 Configuring DCCs................................................................................................................................2-192.6.5 Configuring the Extended ECC............................................................................................................2-212.6.6 Configuring DCC Transparent Transmission......................................................................................2-222.6.7 Querying ECC Routes..........................................................................................................................2-232.6.8 Creating NEs Using the Search Method..............................................................................................2-242.6.9 Creating NEs Using the Manual Method.............................................................................................2-262.6.10 Configuration Example......................................................................................................................2-29

2.7 Maintenance Guide.......................................................................................................................................2-312.7.1 Relevant Alarms and Events................................................................................................................2-312.7.2 FAQs....................................................................................................................................................2-31

3 IP over DCC Solution................................................................................................................3-13.1 Feature Description.........................................................................................................................................3-2

3.1.1 IP over DCC Protocol Stack...................................................................................................................3-2

OptiX RTN 600 Radio Transmission SystemFeature Description Contents

Issue 02 (2008-06-20) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

i

3.1.2 Access Modes.........................................................................................................................................3-33.2 Availability......................................................................................................................................................3-43.3 Relation with Other Features...........................................................................................................................3-43.4 Realization Principle.......................................................................................................................................3-53.5 Planning Guide................................................................................................................................................3-63.6 Configuration Guide........................................................................................................................................3-9

3.6.1 Configuration Flow................................................................................................................................3-93.6.2 Querying IP Routes..............................................................................................................................3-113.6.3 Creating Static IP Routes.....................................................................................................................3-113.6.4 Configuration Example........................................................................................................................3-12


4 OSI over DCC Solution.............................................................................................................4-14.1 Feature Description.........................................................................................................................................4-2

4.1.1 OSI over DCC Protocol Stack................................................................................................................4-24.1.2 Access Mode..........................................................................................................................................4-4

4.2 Availability......................................................................................................................................................4-54.3 Relation with Other Features...........................................................................................................................4-64.4 Realization Principle.......................................................................................................................................4-64.5 Planning Guide................................................................................................................................................4-74.6 Configuration Guide......................................................................................................................................4-10

4.6.1 Configuration Flow..............................................................................................................................4-104.6.2 Configuring the CLNS Role.................................................................................................................4-124.6.3 Querying OSI Routes...........................................................................................................................4-134.6.4 Configuration Example........................................................................................................................4-13


5 DCC Transparent Transmission Solution.............................................................................5-15.1 Feature Description.........................................................................................................................................5-35.2 Availability......................................................................................................................................................5-55.3 Relation with Other Features...........................................................................................................................5-55.4 Realization Principle.......................................................................................................................................5-55.5 Planning Guide................................................................................................................................................5-65.6 Configuration Guide........................................................................................................................................5-8

5.6.1 Configuration Flow................................................................................................................................5-85.6.2 Configuration Example........................................................................................................................5-10


ContentsOptiX RTN 600 Radio Transmission System

Feature Description

ii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

6 DCC Transparent Transmission Through the External Clock Interface Solution........6-16.1 Feature Description.........................................................................................................................................6-36.2 Availability......................................................................................................................................................6-46.3 Relation with Other Features...........................................................................................................................6-46.4 Realization Principle.......................................................................................................................................6-46.5 Planning Guide................................................................................................................................................6-56.6 Configuration Guide .......................................................................................................................................6-7

6.6.1 Configuration Flow................................................................................................................................6-76.6.2 Configuration Example..........................................................................................................................6-8

6.7 Maintenance Guide.........................................................................................................................................6-86.7.1 Relevant Alarms and Events..................................................................................................................6-86.7.2 FAQs......................................................................................................................................................6-9

7 1+1 HSB........................................................................................................................................7-17.1 Feature Description.........................................................................................................................................7-2

7.1.1 System Configuration.............................................................................................................................7-27.1.2 Protection Type......................................................................................................................................7-37.1.3 Switching Condition...............................................................................................................................7-37.1.4 Switching Impact....................................................................................................................................7-5

7.2 Availability......................................................................................................................................................7-57.3 Relation with Other Features...........................................................................................................................7-67.4 Realization Principle.......................................................................................................................................7-67.5 Planning Guide................................................................................................................................................7-87.6 Configuration Guide........................................................................................................................................7-8

7.6.1 Creating IF 1+1 Protection.....................................................................................................................7-97.6.2 Modifying the Parameters of IF 1+1 Protection...................................................................................7-12

7.7 Maintenance Guide.......................................................................................................................................7-147.7.1 IF 1+1 Protection Switching................................................................................................................7-157.7.2 Relevant Alarms and Events................................................................................................................7-157.7.3 FAQs....................................................................................................................................................7-15

8 1+1 FD...........................................................................................................................................8-18.1 Feature Description.........................................................................................................................................8-2


8.2 Availability......................................................................................................................................................8-78.3 Relation with Other Features...........................................................................................................................8-88.4 Realization Principle.......................................................................................................................................8-88.5 Planning Guide..............................................................................................................................................8-108.6 Configuration Guide......................................................................................................................................8-10

8.6.1 Creating IF 1+1 Protection...................................................................................................................8-118.6.2 Modifying the Parameters of IF 1+1 Protection...................................................................................8-11



iii


9 1+1 SD...........................................................................................................................................9-19.1 Feature Description.........................................................................................................................................9-2


9.2 Availability......................................................................................................................................................9-69.3 Relation with Other Features...........................................................................................................................9-79.4 Realization Principle.......................................................................................................................................9-79.5 Planning Guide................................................................................................................................................9-99.6 Configuration Guide......................................................................................................................................9-10

9.6.1 Creating IF 1+1 Protection...................................................................................................................9-109.6.2 Modifying the Parameters of IF 1+1 Protection...................................................................................9-10


10 Cross-Polarization Interference Cancellation...................................................................10-110.1 Feature Description.....................................................................................................................................10-2

10.1.1 CCDP and XPIC.................................................................................................................................10-210.1.2 System Configuration.........................................................................................................................10-3

10.2 Availability..................................................................................................................................................10-410.3 Relation with Other Features.......................................................................................................................10-510.4 Realization Principle...................................................................................................................................10-610.5 Planning Guide............................................................................................................................................10-710.6 Creating an XPIC Protection Group............................................................................................................10-810.7 Maintenance Guide...................................................................................................................................10-12

10.7.1 Relevant Alarms and Events............................................................................................................10-1210.7.2 FAQs................................................................................................................................................10-13

11 N+1 Protection........................................................................................................................11-111.1 Feature Description.....................................................................................................................................11-2

11.1.1 System Configuration.........................................................................................................................11-211.1.2 Protection Type..................................................................................................................................11-511.1.3 Switching Condition...........................................................................................................................11-511.1.4 Switching Impact................................................................................................................................11-7

11.2 Availability..................................................................................................................................................11-711.3 Relation with Other Features.......................................................................................................................11-7


Feature Description

iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

11.4 Realization Principle...................................................................................................................................11-711.4.1 2+1 Protection Configuration.............................................................................................................11-711.4.2 3+1 Protection Configuration.............................................................................................................11-9

11.5 Planning Guide..........................................................................................................................................11-1111.6 Configuration Guide..................................................................................................................................11-11

11.6.1 Configuration Flow..........................................................................................................................11-1111.6.2 Creating an N+1 Protection Group...................................................................................................11-1211.6.3 Creating REGs..................................................................................................................................11-1411.6.4 Configuration Example....................................................................................................................11-16

11.7 Maintenance Guide...................................................................................................................................11-1611.7.1 Starting/Stopping the N+1 Protection Protocol................................................................................11-1611.7.2 N+1 Protection Switching................................................................................................................11-1711.7.3 Relevant Alarms and Events............................................................................................................11-1711.7.4 FAQs................................................................................................................................................11-18

12 Automatic Transmit Power Control Function..................................................................12-112.1 Feature Description.....................................................................................................................................12-212.2 Availability..................................................................................................................................................12-212.3 Relation with Other Features.......................................................................................................................12-312.4 Realization Principle...................................................................................................................................12-312.5 Planning Guide............................................................................................................................................12-412.6 Configuring the ATPC Function.................................................................................................................12-412.7 Maintenance Guide ....................................................................................................................................12-7

12.7.1 Relevant Alarms and Events..............................................................................................................12-712.7.2 FAQs..................................................................................................................................................12-7

13 Sub-Network Connection Protection.................................................................................13-113.1 Feature Description.....................................................................................................................................13-2

13.1.1 Protection Type..................................................................................................................................13-213.1.2 SNCP Service Pair.............................................................................................................................13-213.1.3 Switching Condition...........................................................................................................................13-213.1.4 Switching Impact................................................................................................................................13-5

13.2 Availability..................................................................................................................................................13-513.3 Relation with Other Features.......................................................................................................................13-513.4 Realization Principle...................................................................................................................................13-513.5 Planning Guide............................................................................................................................................13-613.6 Configuration Guide....................................................................................................................................13-7

13.6.1 Creating Cross-Connections for SNCP Services...............................................................................13-713.6.2 Setting the Automatic Switching Conditions of SNCP Services.....................................................13-1113.6.3 Converting Normal Services to SNCP Services..............................................................................13-1313.6.4 Converting SNCP Services to Normal Services..............................................................................13-16

13.7 Maintenance Guide...................................................................................................................................13-1613.7.1 SNCP Switching...............................................................................................................................13-1613.7.2 Relevant Alarms and Events............................................................................................................13-17



v

13.7.3 FAQs................................................................................................................................................13-17

14 Linear Multiplex Section Protection...................................................................................14-114.1 Feature Description.....................................................................................................................................14-2

14.1.1 Protection Type..................................................................................................................................14-214.1.2 Meaning of Byte K.............................................................................................................................14-314.1.3 Switching Condition...........................................................................................................................14-414.1.4 Switching Impact................................................................................................................................14-6

14.2 Availability..................................................................................................................................................14-614.3 Relation with Other Features.......................................................................................................................14-614.4 Realization Principle...................................................................................................................................14-6

14.4.1 1+1 Linear MSP.................................................................................................................................14-614.4.2 1:N Linear MSP.................................................................................................................................14-8

14.5 Planning Guide............................................................................................................................................14-914.6 Creating Linear MSP.................................................................................................................................14-1014.7 Maintenance Guide...................................................................................................................................14-14

14.7.1 Starting/Stopping the Linear MSP Protocol.....................................................................................14-1414.7.2 Linear MSP Switching.....................................................................................................................14-1414.7.3 Relevant Alarms and Events............................................................................................................14-1514.7.4 FAQs................................................................................................................................................14-16

15 Two-Fiber Bidirectional Ring MSP....................................................................................15-115.1 Feature Description.....................................................................................................................................15-2

15.1.1 Protection Type..................................................................................................................................15-215.1.2 Meaning of Byte K.............................................................................................................................15-215.1.3 Switching Condition...........................................................................................................................15-315.1.4 Switching Impact................................................................................................................................15-5

15.2 Availability..................................................................................................................................................15-515.3 Relation with Other Features.......................................................................................................................15-515.4 Realization Principle...................................................................................................................................15-515.5 Planning Guide............................................................................................................................................15-715.6 Creating a Ring Multiplex Section..............................................................................................................15-815.7 Maintenance Guide...................................................................................................................................15-11

15.7.1 Starting/Stopping the Ring MSP Protocol.......................................................................................15-1115.7.2 Ring MSP Switching........................................................................................................................15-1115.7.3 Relevant Alarms and Events............................................................................................................15-1215.7.4 FAQs................................................................................................................................................15-12

16 Features of Ethernet Ports.....................................................................................................16-116.1 Feature Description.....................................................................................................................................16-2

16.1.1 Auto-Negotiation Function................................................................................................................16-216.1.2 Jumbo Frames....................................................................................................................................16-316.1.3 Flow Control Function.......................................................................................................................16-4

16.2 Availability..................................................................................................................................................16-5


Feature Description

vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

16.3 Relation with Other Features.......................................................................................................................16-516.4 Realization Principle...................................................................................................................................16-5

16.4.1 Auto-Negotiation Function................................................................................................................16-616.4.2 Flow Control Function.......................................................................................................................16-7

16.5 Planning Guide............................................................................................................................................16-816.6 Configuration Guide....................................................................................................................................16-9

16.6.1 Configuring the External Port of the Ethernet Board.........................................................................16-916.6.2 Modifying the Type Field of Jumbo Frames....................................................................................16-15

16.7 Maintenance Guide...................................................................................................................................16-1616.7.1 Relevant Alarms and Events............................................................................................................16-1616.7.2 FAQs................................................................................................................................................16-16

17 Encapsulation and Mapping of Ethernet Services...........................................................17-117.1 Feature Description.....................................................................................................................................17-3

17.1.1 Encapsulation and Mapping Protocols...............................................................................................17-317.1.2 Virtual Concatenation........................................................................................................................17-317.1.3 LCAS..................................................................................................................................................17-4


17.4.1 Encapsulation and Mapping...............................................................................................................17-517.4.2 Virtual Concatenation........................................................................................................................17-917.4.3 LCAS................................................................................................................................................17-10

17.5 Planning Guide..........................................................................................................................................17-1417.6 Configuring the Internal Port of the Ethernet Board.................................................................................17-1517.7 Maintenance Guide...................................................................................................................................17-23

17.7.1 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth....................................................17-2317.7.2 Relevant Alarms and Events............................................................................................................17-2417.7.3 FAQs................................................................................................................................................17-26

18 VLAN........................................................................................................................................18-118.1 Feature Description.....................................................................................................................................18-2

18.1.1 Purpose...............................................................................................................................................18-218.1.2 Frame Format.....................................................................................................................................18-218.1.3 TAG Attribute....................................................................................................................................18-318.1.4 Application.........................................................................................................................................18-4


18.6.1 Configuration Flow............................................................................................................................18-718.6.2 Creating Ethernet Line Service..........................................................................................................18-918.6.3 Configuration Example (PORT-Shared EVPL Service)..................................................................18-12



vii

18.6.4 Configuration Example (VCTRUNK-Shared EVPL Service).........................................................18-1318.7 Maintenance Guide...................................................................................................................................18-15

18.7.1 Relevant Alarms and Events............................................................................................................18-1518.7.2 FAQs................................................................................................................................................18-15

19 Layer 2 Switching...................................................................................................................19-119.1 Feature Description.....................................................................................................................................19-2

19.1.1 Bridge ................................................................................................................................................19-219.1.2 STP/RSTP..........................................................................................................................................19-419.1.3 IGMP Snooping..................................................................................................................................19-5


19.4.1 Bridge ................................................................................................................................................19-819.4.2 STP/RSTP..........................................................................................................................................19-819.4.3 IGMP Snooping................................................................................................................................19-13

19.5 Planning Guide..........................................................................................................................................19-1519.6 Configuration Guide..................................................................................................................................19-16

19.6.1 Creating the Ethernet LAN Service..................................................................................................19-1619.6.2 Modifying the Mounted Port of a Bridge.........................................................................................19-2219.6.3 Creating the VLAN Filter Table......................................................................................................19-2319.6.4 Creating the Entry of a MAC Address Table Manually ..................................................................19-2519.6.5 Modifying the Aging Time of the MAC Address Table Entry........................................................19-2619.6.6 Configuring the Spanning Tree Protocol ........................................................................................19-2719.6.7 Configuring the IGMP Snooping Protocol.......................................................................................19-3219.6.8 Modifying the Aging Time of the Multicast Table Item..................................................................19-33

19.7 Maintenance Guide...................................................................................................................................19-3519.7.1 Querying the Actual Capacity of the MAC Address Table and the Dynamic Entry.......................19-3519.7.2 Querying the Running Information About the Spanning Tree Protocol..........................................19-3519.7.3 Querying the Running Information About the IGMP Snooping Protocol ......................................19-3619.7.4 Relevant Alarms and Events............................................................................................................19-3719.7.5 FAQs................................................................................................................................................19-37

20 QoS............................................................................................................................................20-120.1 Feature Description.....................................................................................................................................20-2

20.1.1 Flow Classification.............................................................................................................................20-220.1.2 CAR....................................................................................................................................................20-220.1.3 CoS.....................................................................................................................................................20-320.1.4 Traffic Shaping...................................................................................................................................20-4


20.4.1 CAR....................................................................................................................................................20-520.4.2 Traffic Shaping...................................................................................................................................20-6


Feature Description

viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

20.4.3 Egress Queue Scheduling...................................................................................................................20-720.5 Planning Guide............................................................................................................................................20-820.6 Configuration Guide....................................................................................................................................20-9

20.6.1 Creating a Flow..................................................................................................................................20-920.6.2 Creating the CAR.............................................................................................................................20-1220.6.3 Creating the CoS..............................................................................................................................20-1520.6.4 Binding the CAR/CoS......................................................................................................................20-1720.6.5 Configuring the Traffic Shaping......................................................................................................20-18


21 QinQ.........................................................................................................................................21-121.1 Feature Description.....................................................................................................................................21-2

21.1.1 Functionality.......................................................................................................................................21-221.1.2 Frame Format.....................................................................................................................................21-221.1.3 Network Attributes.............................................................................................................................21-421.1.4 Application of the QinQ Technology in Line Services......................................................................21-4


21.6.1 Configuration Flow............................................................................................................................21-921.6.2 Modifying the Type Field of QinQ Frames.....................................................................................21-1121.6.3 Creating QinQ Line Services...........................................................................................................21-1121.6.4 Configuration Example....................................................................................................................21-15


22 Remote Monitoring Feature.................................................................................................22-122.1 Feature Description.....................................................................................................................................22-2

22.1.1 SNMP.................................................................................................................................................22-222.1.2 RMON Management Groups.............................................................................................................22-222.1.3 List of RMON Alarm Entries and List of RMON Performance Entries............................................22-4

22.2 Availability..................................................................................................................................................22-622.3 Relation with Other Features.......................................................................................................................22-722.4 Realization Principle...................................................................................................................................22-722.5 Planning Guide............................................................................................................................................22-822.6 Configuration Guide....................................................................................................................................22-922.7 Maintenance Guide.....................................................................................................................................22-9

22.7.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port.....................................22-922.7.2 Configuring an Alarm Group for an Ethernet Port..........................................................................22-10



ix

22.7.3 Configuring a History Control Group..............................................................................................22-1122.7.4 Browsing the Performance Data in the History Group of an Ethernet Port.....................................22-1222.7.5 FAQs................................................................................................................................................22-13

A Glossary.....................................................................................................................................A-1

B Acronyms and Abbreviations.................................................................................................B-1

Index.................................................................................................................................................i-1


Feature Description

x Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

Figures

Figure 1-1 DCN....................................................................................................................................................1-2Figure 2-1 Architecture of the HW ECC protocol stack .....................................................................................2-2Figure 2-2 Networking for the extended ECC (using a network cable)...............................................................2-5Figure 2-3 Networking for the extended ECC (using a hub)............................................................................... 2-5Figure 2-4 Networking for the extended ECC (using network cables to connect NEs in series)........................ 2-6Figure 2-5 Networking example for establishing ECC routes ............................................................................2-8Figure 2-6 Realization principle of message transferring (HW ECC).................................................................2-9Figure 2-7 Networking example for the HW ECC solution...............................................................................2-13Figure 2-8 Allocation of IDs/IP addresses for all NEs.......................................................................................2-14Figure 2-9 Configuration flow for the HW ECC solution .................................................................................2-15Figure 3-1 Architecture of the IP over DCC protocol stack ................................................................................3-2Figure 3-2 Realization principle of message transferring (gateway mode)......................................................... 3-5Figure 3-3 Realization principle of message transferring (direct connection mode)...........................................3-6Figure 3-4 Networking example for the IP over DCC solution...........................................................................3-8Figure 3-5 Allocation of IDs/IP addresses for all NEs.........................................................................................3-9Figure 3-6 Configuration flow for the IP over DCC solution ...........................................................................3-10Figure 4-1 Architecture of the OSI over DCC protocol stack .............................................................................4-2Figure 4-2 Format of the NSAP address..............................................................................................................4-3Figure 4-3 Layered routes of IS-IS protocol routes (L2 not consecutive)........................................................... 4-4Figure 4-4 Realization principle of message transferring (gateway mode)......................................................... 4-6Figure 4-5 Realization principle of message transferring (direct connection mode)...........................................4-7Figure 4-6 Networking example for the OSI over DCC solution........................................................................ 4-9Figure 4-7 Allocation of NE areas ....................................................................................................................4-10Figure 4-8 Configuration flow for the OSI over DCC solution ........................................................................4-11Figure 5-1 DCC transparent transmission solution when the OptiX equipment is at the edge of a network (1)...............................................................................................................................................................................5-3Figure 5-2 DCC transparent transmission solution when the OptiX equipment is at the edge of a network (2)...............................................................................................................................................................................5-4Figure 5-3 DCC transparent transmission solution when the OptiX equipment is in the center of a network (1)...............................................................................................................................................................................5-4Figure 5-4 DCC transparent transmission solution when the OptiX equipment is in the center of a network (2)...............................................................................................................................................................................5-5Figure 5-5 Realization principle of the DCC transparent transmission .............................................................. 5-6Figure 5-6 Networking example for the DCC transparent transmission solution ...............................................5-7

OptiX RTN 600 Radio Transmission SystemFeature Description Figures


xi

Figure 5-7 Allocations of IDs and IP addresses for all NEs.................................................................................5-8Figure 5-8 Configuration flow for the DCC transparent transmission solution ..................................................5-9Figure 6-1 Networking example for the DCC transparent transmission through the external clock interface solution(direct access mode)..............................................................................................................................................6-3Figure 6-2 Networking example for the DCC transparent transmission through the external clock interface solution(indirect access mode)...........................................................................................................................................6-4Figure 6-3 Realization principle of the DCC transparent transmission through the external clock interface...............................................................................................................................................................................6-5Figure 6-4 Networking example for the DCC transparent transmission through the external clock interface solution...............................................................................................................................................................................6-6Figure 6-5 Configuration flow for the DCC transparent transmission through the external clock interface solution...............................................................................................................................................................................6-7Figure 7-1 Typical configuration of one 1+1 HSB protection group (IDU 620).................................................7-2Figure 7-2 Typical configuration of one 1+1 HSB protection group (IDU 605 2B)...........................................7-3Figure 7-3 1+1 HSB realization principle (before the switching, in the transmit direction)...............................7-6Figure 7-4 1+1 HSB realization principle (before the switching, in the receive direction).................................7-7Figure 7-5 1+1 HSB realization principle (after the switching, in the receive direction)....................................7-7Figure 7-6 1+1 HSB realization principle (after the switching, in the transmit direction)..................................7-8Figure 8-1 Typical configuration 1 of one 1+1 FD protection group (IDU 620).................................................8-2Figure 8-2 Typical configuration 2 of one 1+1 FD protection group (IDU 620).................................................8-3Figure 8-3 Typical configuration 1 of one 1+1 FD protection group (IDU 605 2B)...........................................8-4Figure 8-4 Typical configuration 2 of one 1+1 FD protection group (IDU 605 2B)...........................................8-4Figure 8-5 1+1 FD realization principle (before the switching, in the transmit direction)..................................8-8Figure 8-6 1+1 FD realization principle (before the switching, in the receive direction)....................................8-9Figure 8-7 1+1 FD HSB realization principle (after the switching, in the receive direction)..............................8-9Figure 8-8 1+1 FD HSM realization principle (after the switching, in the receive direction)...........................8-10Figure 9-1 Typical configuration of one 1+1 SD protection group (IDU 620)....................................................9-2Figure 9-2 Typical configuration of one 1+1 SD protection group (IDU 605 2B)..............................................9-3Figure 9-3 1+1 SD realization principle (before the switching, in the transmit direction)..................................9-7Figure 9-4 1+1 SD realization principle (before the switching, in the receive direction)....................................9-8Figure 9-5 1+1 SD HSB realization principle (after the switching, in the receive direction)..............................9-8Figure 9-6 1+1 SD HSB realization principle (after the switching, in the transmit direction)............................9-9Figure 9-7 1+1 SD HSM realization principle (after the switching, in the receive direction).............................9-9Figure 10-1 Single-polarization transmission....................................................................................................10-2Figure 10-2 CCDP transmission.........................................................................................................................10-2Figure 10-3 Typical configuration of XPIC (single-NE configuration).............................................................10-3Figure 10-4 Typical configuration of XPIC (dual-NE configuration)...............................................................10-4Figure 10-5 Typical XPIC configuration (1+1 protection configuration)..........................................................10-6Figure 10-6 Realization principle of XPIC........................................................................................................10-7Figure 11-1 Typical configuration of one 2+1 protection group........................................................................11-3Figure 11-2 Typical channel configuration of one 2+1 protection group..........................................................11-3Figure 11-3 Typical configuration of one 3+1 protection group........................................................................11-4Figure 11-4 Typical channel configuration of one 3+1 protection group..........................................................11-5Figure 11-5 Realization principle of 2+1 protection (before the switching)......................................................11-8

FiguresOptiX RTN 600 Radio Transmission System

Feature Description

xii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

Figure 11-6 Realization principle of 2+1 protection (after the switching).........................................................11-8Figure 11-7 Realization principle of 3+1 protection (before the switching)......................................................11-9Figure 11-8 Realization principle of 3+1 protection (after the switching).......................................................11-10Figure 11-9 Configuration flow for the N+1 protection mode.........................................................................11-12Figure 12-1 ATPC realization principle.............................................................................................................12-3Figure 13-1 SNCP service pair...........................................................................................................................13-2Figure 13-2 SNCP realization principle (before the switching).........................................................................13-6Figure 13-3 SNCP realization principle (after the switching)............................................................................13-6Figure 14-1 Realization principle of 1+1 linear MSP (before the switching)....................................................14-7Figure 14-2 Realization principle of 1+1 linear MSP (after the switching, in the single-ended mode)............14-7Figure 14-3 Realization principle of 1+1 linear MSP (after the switching, in the dual-ended mode)...............14-7Figure 14-4 Realization principle of 1:1 linear MSP (before the switching).....................................................14-8Figure 14-5 Realization principle of 1:1 linear MSP (after the switching)........................................................14-9Figure 15-1 Realization principle of the two-fiber bidirectional ring MSP (before the switching)...................15-6Figure 15-2 Realization principle of the two-fiber bidirectional ring MSP (after the switching)......................15-6Figure 16-1 Waveform of a single FLP..............................................................................................................16-6Figure 16-2 Consecutive FLP bursts and NLPs ................................................................................................16-7Figure 16-3 Structure of the PAUSE frame.......................................................................................................16-7Figure 17-1 Structure of the GFP frame ............................................................................................................17-6Figure 17-2 GFP type field format.....................................................................................................................17-7Figure 17-3 VC-3-Xv/VC-4-Xv multiframe and sequence indicator ..............................................................17-10Figure 17-4 Capacity adjustment process (addition of a member) ..................................................................17-12Figure 17-5 Capacity adjustment process (deletion of a member) ..................................................................17-12Figure 17-6 Capacity adjustment process (one member link restored after a failure).....................................17-13Figure 18-1 Tagged frame format......................................................................................................................18-3Figure 18-2 PORT-shared EVPL service...........................................................................................................18-5Figure 18-3 VCTRUNK-shared EVPL service..................................................................................................18-5Figure 18-4 Configuration flow of the EPL service that uses the VLAN feature (PORT-shared or VCTRUNK-shared EVPL service) .........................................................................................................................................18-7Figure 19-1 802.1d bridge and 802.1q bridge....................................................................................................19-2Figure 19-2 Transmission of the multicast packet (with IGMP Snooping disabled).........................................19-6Figure 19-3 Transmission of the multicast packet (with IGMP Snooping enabled)..........................................19-6Figure 20-1 Basic principle of the token bucket algorithm................................................................................20-5Figure 20-2 Basic principle of the algorithm that is used by the CAR..............................................................20-6Figure 20-3 Basic principle of the algorithm that is used by the traffic shaping...............................................20-7Figure 20-4 Basic principle of the egress queue algorithm................................................................................20-8Figure 21-1 Format of the Ethernet frame with only a C-TAG.........................................................................21-2Figure 21-2 Format of the Ethernet frame with a C-TAG and an S-TAG.........................................................21-3Figure 21-3 Format of the Ethernet frame with only an S-TAG........................................................................21-3Figure 21-4 Example of QinQ services..............................................................................................................21-7Figure 21-5 Ports used by the QinQ line services..............................................................................................21-8Figure 21-6 Configuration flow for the QinQ line service...............................................................................21-10

OptiX RTN 600 Radio Transmission SystemFeature Description Figures


xiii

Tables

Table 2-1 Availability of the HW ECC solution..................................................................................................2-7Table 2-2 Description of the configuration flow of the HW ECC solution ......................................................2-15Table 3-1 Availability of the IP over DCC solution.............................................................................................3-4Table 3-2 Description of the configuration flow of the IP over DCC solution .................................................3-10Table 4-1 Availability of the OSI over DCC solution..........................................................................................4-5Table 4-2 Description of the configuration flow of the OSI over DCC solution ..............................................4-11Table 5-1 Availability of the DCC transparent transmission solution.................................................................5-5Table 5-2 Description of the configuration flow of the DCC transparent transmission solution ........................5-9Table 6-1 Availability of the DCC transparent transmission through the external clock interface solution........6-4Table 6-2 Description of the configuration flow of the DCC transparent transmission through the external clockinterface solution...................................................................................................................................................6-7Table 7-1 Switching conditions of the 1+1 HSB protection................................................................................7-4Table 7-2 Trigger conditions of the automatic 1+1 HSB switching ....................................................................7-5Table 7-3 Availability of the 1+1 HSB feature....................................................................................................7-6Table 8-1 HSB switching conditions of the 1+1 FD protection...........................................................................8-5Table 8-2 Trigger conditions of the automatic HSB switching ...........................................................................8-6Table 8-3 Trigger conditions of the automatic HSM switching ..........................................................................8-6Table 8-4 Availability of the 1+1 FD feature.......................................................................................................8-7Table 9-1 HSB switching conditions of the 1+1 SD protection...........................................................................9-4Table 9-2 Trigger conditions of the automatic HSB switching ...........................................................................9-5Table 9-3 Trigger conditions of the automatic HSM switching ..........................................................................9-6Table 9-4 Availability of the 1+1 SD feature.......................................................................................................9-7Table 10-1 Availability of the XPIC feature......................................................................................................10-5Table 11-1 Switching conditions of the N+1 protection....................................................................................11-5Table 11-2 Availability of the N+1 protection feature.......................................................................................11-7Table 11-3 Description of the configuration flow of the N+1 protection mode...............................................11-12Table 12-1 ATPC performance..........................................................................................................................12-2Table 12-2 Availability of the ATPC feature.....................................................................................................12-2Table 13-1 Switching conditions of SNCP.........................................................................................................13-2Table 13-2 Trigger conditions of the automatic SNCP switching (VC-4 services)...........................................13-3Table 13-3 Trigger conditions of the automatic SNCP switching (VC-3/VC-12 services)...............................13-4Table 13-4 Availability of the SNCP solution....................................................................................................13-5Table 14-1 Meaning of byte K (linear MSP)......................................................................................................14-3Table 14-2 Bridge request code (linear MSP)....................................................................................................14-4

OptiX RTN 600 Radio Transmission SystemFeature Description Tables


xv

Table 14-3 Linear MSP switching conditions....................................................................................................14-5Table 14-4 Availability of the linear MSP solution........................................................................................... 14-6Table 15-1 Meaning of byte K (two-fiber bidirectional ring MSP)...................................................................15-2Table 15-2 Switching request code.................................................................................................................... 15-3Table 15-3 Switching conditions of the two-fiber bidirectional ring MSP........................................................15-3Table 15-4 Availability of the two-fiber bidirectional ring MSP.......................................................................15-5Table 16-1 Auto-negotiation rules of FE electrical ports (when the local port adopts the auto-negotiation mode).............................................................................................................................................................................16-2Table 16-2 Auto-negotiation rules of GE electrical ports (when the local port adopts the auto-negotiation mode).............................................................................................................................................................................16-3Table 16-3 Availability of the Ethernet port feature.......................................................................................... 16-5Table 16-4 Methods used by ports to process data frames...............................................................................16-15Table 17-1 Availability of the Ethernet encapsulation and mapping feature.....................................................17-5Table 17-2 UPI values of the client management frame.................................................................................... 17-8Table 17-3 LCAS CTRL words .......................................................................................................................17-11Table 17-4 Methods used by ports to process data frames...............................................................................17-22Table 18-1 Data frame processing method of the switch port............................................................................18-3Table 18-2 Availability of the VLAN feature....................................................................................................18-5Table 18-3 Configuration flow of the EVPL service that uses the VLAN feature (PORT-shared EVPL service).............................................................................................................................................................................18-8Table 18-4 Configuration flow of the EVPL service that uses the VLAN feature (VCTRUNK-shared EVPL service).............................................................................................................................................................................18-8Table 19-1 Comparison between the 802.1d bridge and the 802.1q bridge.......................................................19-2Table 19-2 Availability of the Layer 2 switching feature ..................................................................................19-7Table 20-1 Availability of the QoS feature........................................................................................................20-4Table 21-1 Line services between C-aware ports...............................................................................................21-5Table 21-2 Line services between a C-aware port and an S-aware port............................................................ 21-5Table 21-3 Line services between S-aware ports...............................................................................................21-6Table 21-4 Availability of the QinQ feature...................................................................................................... 21-6Table 21-5 Description of the configuration flow of the QinQ line service.....................................................21-10Table 22-1 List of RMON alarm entries............................................................................................................ 22-4Table 22-2 List of RMON performance entries................................................................................................. 22-4Table 22-3 Availability of the RMON feature................................................................................................... 22-7

TablesOptiX RTN 600 Radio Transmission System

Feature Description

xvi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

About This Document

PurposeThis document describes the main features of the OptiX RTN 600 radio transmission system. Itprovides readers a comprehensive knowledge on the functionality, principle, configuration, andmaintenance of the product features.

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

OptiX RTN 600 V100R002

OptiX iManager T2000 V200R006C03

Intended AudienceThis document is advanced reading material for the personnel who work with the OptiX RTN600. Before reading this document, the audience should have basic understanding of the OptiXRTN 600.

OrganizationThis document consists of 13 chapters and is organized as follows.

Chapter Content

1 Introduction to the DCN Introduces the DCN and DCN solutions.

OptiX RTN 600 Radio Transmission SystemFeature Description About This Document


1

Chapter Content

2 HW ECC Solution Describes the functionality, principle, configurationoperations, and maintenance operations of the HW ECCsolution.

3 IP over DCC Solution Describes the functionality, principle, configurationoperations, and maintenance operations of the IP over DCCsolution.

4 OSI over DCC Solution Describes the functionality, principle, configurationoperations, and maintenance operations of the OSI over DCCsolution.

5 DCC TransparentTransmission Solution

Describes the functionality, principle, configurationoperations, and maintenance operations of the DCCtransparent transmission solution.

6 DCC TransparentTransmission Through theExternal Clock InterfaceSolution

Describes the functionality, principle, configurationoperations, and maintenance operations of the DCCtransparent transmission through the external clock interfacesolution.

7 1+1 HSB Describes the functionality, principle, configurationoperations, and maintenance operations of the 1+1 HSBprotection scheme.

8 1+1 FD Describes the functionality, principle, configurationoperations, and maintenance operations of the 1+1 FDprotection scheme.

9 1+1 SD Describes the functionality, principle, configurationoperations, and maintenance operations of the 1+1 SDprotection scheme.

10 Cross-PolarizationInterference Cancellation

Describes the functionality, principle, configurationoperations, and maintenance operations of the XPIC scheme.

11 N+1 Protection Describes the functionality, principle, configurationoperations, and maintenance operations of the N+1 protectionscheme.

12 Automatic TransmitPower Control Function

Describes the functionality, principle, configurationoperations, and maintenance operations of the ATPC.

13 Sub-NetworkConnection Protection

Describes the functionality, principle, configurationoperations, and maintenance operations of the SNCP scheme.

14 Linear MultiplexSection Protection

Describes the functionality, principle, configurationoperations, and maintenance operations of the linear MSPscheme.

15 Two-Fiber BidirectionalRing MSP

Describes the functionality, principle, configurationoperations, and maintenance operations of the two-fiberbidirectional ring MSP scheme.

About This DocumentOptiX RTN 600 Radio Transmission System

Feature Description

2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

Chapter Content

16 Features of EthernetPorts

Describes the functionality, principle, configurationoperations, and maintenance operations of the auto-negotiation function, Jumbo frames, and flow controlfunction of the Ethernet port.

17 Encapsulation andMapping of EthernetServices

Describes the functionality, principle, configurationoperations, and maintenance operations of the encapsulationand mapping technology, the related virtual concatenationtechnology and the LCAS technology of Ethernet services.

18 VLAN Describes the functionality, principle, configurationoperations, and maintenance operations of the VLANscheme.

19 Layer 2 Switching Describes the functionality, principle, configurationoperations, and maintenance operations of the two layerswitching scheme.

20 QoS Describes the functionality, principle, configurationoperations, and maintenance operations of the QoS scheme.

21 QinQ Describes the functionality, principle, configurationoperations, and maintenance operations of the QinQ scheme.

22 Remote MonitoringFeature

Describes the functionality, principle, configurationoperations, and maintenance operations of the RMONscheme.

A Glossary Lists the terms used in this document.

B Acronyms andAbbreviations

Lists the acronyms and abbreviations used in this document.

Conventions

Symbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.



3

Symbol Description

Indicates a potentially hazardous situation, which if notavoided, 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 supplementimportant points of the main text.

General ConventionsThe general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are inCourier New.

GUI ConventionsThe GUI conventions that may be found in this document are defined as follows.

Convention Description

Boldface Buttons, menus, parameters, tabs, windows, and dialog titles are inboldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">" signs. Forexample, choose File > Create > Folder.

Update HistoryUpdates between document versions are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

Updates in Issue 02 (2008-06-20)Known defects are modified as required.

About This DocumentOptiX RTN 600 Radio Transmission System

Feature Description

4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

Updates in Issue 01 (2008-05-20)Initial release.



5

1 Introduction to the DCN

About This Chapter

The network management system (NMS) establishes communication with a transmissionnetwork element (NE) through the data communication network (DCN) to manage and maintainthe NE.

1.1 Constitution of the DCNIn a DCN, both the NMS and NE are nodes of the DCN. The DCN between the NMS and NEsis called the external DCN, and the DCN between NEs is called the internal DCN.

1.2 Huawei DCN SolutionFor a variety of networks comprised of the transmission equipment, the OptiX transmissionequipment of Huawei provides multiple DCN solutions.

OptiX RTN 600 Radio Transmission SystemFeature Description 1 Introduction to the DCN


1-1

1.1 Constitution of the DCNIn a DCN, both the NMS and NE are nodes of the DCN. The DCN between the NMS and NEsis called the external DCN, and the DCN between NEs is called the internal DCN.

Figure 1-1 DCN

External DCN

Internal DCN

NMS

LAN switchRouter

OptiX optical transmission equipment

OptiX radio transmission equipment

External DCNIn an actual network, the NMS and NEs may be located on different floors of a building, or indifferent buildings, or even in different cities. Hence, an external DCN that is comprised of thedata communication equipment such as LAN switches and routers is required to connect theNMS and the NEs.

As the external DCN involves data communication knowledge, no detailed description isprovided in this document. Unless otherwise specified, the DCN mentioned in this documentrefers to the internal DCN.

1 Introduction to the DCNOptiX RTN 600 Radio Transmission System

Feature Description

1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

Internal DCN

In an internal DCN, an NE uses the DCC bytes of the overhead as the physical channels of theDCN.

l When the D1 byte of the PDH microwave overhead is used, a bandwidth of 64 kbit/s canbe provided for the DCN.

l When three D1–D3 bytes of the PDH microwave overhead is used, a bandwidth of 192kbit/s can be provided for the DCN.

l When the D1–D3 bytes of the SDH regenerator section overhead (RSOH) are used, abandwidth of 192 kbit/s can be provided for the DCN.

l When the D4–D12 bytes of the SDH multiplex section overhead (MSOH) are used, abandwidth of 576 kbit/s can be provided for the DCN.

l When the D1–D12 bytes of the SDH section overhead are used, a bandwidth of 768 kbit/s can be provided for the DCN.

NOTE

l In the PDH microwave frame, the DCC byte is self-defined.

l In the SDH microwave frame, the defined DCC byte complies with the SDH overhead specifications.

1.2 Huawei DCN SolutionFor a variety of networks comprised of the transmission equipment, the OptiX transmissionequipment of Huawei provides multiple DCN solutions.

HW ECC Solution

When the network is comprised of only the OptiX transmission equipment, the HW ECC solutionis the first choice.

With the HW ECC solution, NEs transmit the data that supports the HW ECC protocol throughDCCs. Hence, the solution features easy configuration and convenient application. As the HWECC protocol is a private protocol, however, the network management problem cannot be solvedwhen the network is comprised of the OptiX equipment and third-party equipment.

For details on the HW ECC solution, see 2 HW ECC Solution.

IP over DCC Solution

When the network is comprised of the OptiX transmission equipment and the third-partyequipment 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 is comprised of only the OptiXtransmission equipment.

With the IP over DCC solution, NEs transmit the data that supports the TCP/IP protocol throughDCCs. As the TCP/IP is a standard protocol stack, the network management problem is solvedwhen the network is comprised of the OptiX equipment and third-party equipment. Theconfiguration, however, is more complicated than the HW ECC solution.

For details on the IP over DCC solution, see 3 IP over DCC Solution.

OptiX RTN 600 Radio Transmission SystemFeature Description 1 Introduction to the DCN


1-3

OSI over DCC SolutionWhen the network is comprised of the OptiX transmission equipment and the third-partyequipment that supports the OSI over DCC function, the OSI over DCC solution is the firstchoice.

With the OSI over DCC solution, NEs transmit the data that supports the open systeminterconnection (OSI) protocol through DCCs. As the OSI protocol is a standard protocol, thenetwork management problem is solved when the network is comprised of the OptiX equipmentand third-party equipment. The configuration, however, is more complicated than both the HWECC solution and the IP over DCC solution.

For details on the OSI over DCC solution, see 4 OSI over DCC Solution.

DCC Transparent Transmission SolutionWhen the network is comprised of the OptiX transmission equipment and the third-party SDHequipment that does not support the IP over DCC function or the OSI over DCC function, useDCC 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 vendors' equipment is used togetherwith third-party equipment to form a network. As the NMS of a vendor can manage only theNEs of the vendor, however, there is a great limitation.

For details on the DCC transparent transmission solution, see 5 DCC TransparentTransmission Solution.

DCC Transparent Transmission Through the External Clock Interface SolutionWhen a PDH network or a network that does not support transparent transmission of DCC bytesexists on the transmission path of NM messages, use the DCC transparent transmission throughthe external clock interface solution.

With the DCC transparent transmission through the external clock interface solution, DCC bytesare loaded into the timeslots of the E1 provided by the external clock interface and third-partyequipment transmits the E1 as an ordinary E1 service. When this solution is applied, thetransmission 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.

NOTE

l The IDU 610/620 supports the five solutions.

l The IDU 605 supports only the HW ECC solution and the IP over DCC solution.

1 Introduction to the DCNOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

2 HW ECC Solution

About This Chapter

By use of the HW ECC solution, NEs use unified DCCs to transmit the data of the HW ECCprotocol. In this way, the NMS can manage NEs. The HW ECC solution applies to a networkthat is comprised of only the OptiX transmission equipment.

2.1 Feature DescriptionThis topic describes the HW ECC protocol stack and the extended ECC.

2.2 AvailabilityThe HW ECC solution requires support of the involved equipment and boards.

2.3 Relation with Other FeaturesIt is recommended that you adopt only one of the HW ECC solution, IP over DCC solution, andOSI over DCC solution to form a DCN.

2.4 Realization PrincipleThis topic describes how to establish ECC routes, transfer messages, and realize the extendedECC in the HW ECC solution.

2.5 Planning GuideWhen using the HW ECC solution, plan the parameters of an ECC network according to thesituation of the network.

2.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of the HWECC solution. An example is provided as a supplement to the configuration.

2.7 Maintenance GuideThis topic describes alarms and performance events relevant to the HW ECC solution, andproblems that occur frequently during the application of the solution.

OptiX RTN 600 Radio Transmission SystemFeature Description 2 HW ECC Solution


2-1

2.1 Feature DescriptionThis topic describes the HW ECC protocol stack and the extended ECC.

2.1.1 HW ECC Protocol StackITU-T G.784 defines the architecture of the ECC protocol stack based on the OSI seven layerreference model. The HW ECC protocol stack is based on the ECC protocol stack.

Figure 2-1 Architecture of the HW ECC protocol stack

Application layer

Presentation layer

Session layer

Transport layer

Network layer

Data link layer

Physical layer

HW ECCprotocol stack OSI model

Transport layer

Network layer

Media accesslayer

Physical layer

Physical Layer

The main function of the physical layer is to control physical channels. The physical layerperforms 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 portcorresponds. The status information includes the following:

– Port enabled state

– Used overhead byte

– Link status information

l Provides the data communication service.

– The physical layer receives the data of the physical channel and transfers the data to theupper layer.

– The physical layer receives the data frames transferred from the upper layer and sendsthem to physical channels.

Physical channels are classified into the following two categories:

2 HW ECC SolutionOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

l DCC channelDCC channels use the DCC bytes in SDH frames or PDH microwave frames as the channelsfor communication among NEs. In the HW ECC solution:– SDH line ports generally use bytes D1 to D3 as DCC channels.

– When the IF1A/B board transmits 16xE1 signals or higher-capacity PDH microwavesignals, 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 signals, theIF1A/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 asDCC channels.

l Extended channelExtended channels use the Ethernet as a channel for communication among NEs.

Media Access LayerThe main function of the media access layer (MAC layer) is to activate and close physical DCCsbetween the physical layer and the network layer. The MAC layer performs the followingfunctions:

l Establishes and maintains the MAC connection between adjacent NEs.When there is a reachable physical channel between two adjacent NEs, the MAC layerestablishes a MAC connection between the NEs. Each MAC connection includes theaddress of the opposite NE, the ID of the physical channel, the connection timer, and otherinformation. 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 cancommunicate through the ECC, even if many ports of the two NEs that support the DCCare interconnected.

– The physical channel of the current MAC connection is also the current ECC route.

l Provides the data communication service.– The MAC layer receives the data frame transferred from the physical layer. If the

destination address is the local station, the MAC layer transfers the data frame to thenetwork layer. Otherwise, the MAC layer discards the data frame.

– The MAC layer sends the data frame from the network layer. If the destination addressof the data frame has a MAC connection, the MAC layer sends the data frame to thecorresponding physical channel in the physical layer through the MAC connection.Otherwise, the MAC layer discards the data frame.

Network LayerThe main function of the network layer (NET layer) is to provide the route addressing functionfor data frames and the route management function for the DCC communication network. TheNET layer performs the following functions:

l Establishes and maintains ECC routes.The NET layer establishes and maintains the NET layer routing table. Each route itemincludes the following information:



2-3

– 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 automaticallyestablished route is 4 by default. The system always selects the route with the highestpriority.)

– Mode (0 represents the automatic route and 1 represents the manual route)

l Provides the data communication service.– The NET layer receives the packet transferred from the MAC layer. If the destination

address of the packet is the local station, the NET layer transfers the packet to thetransport layer. Otherwise, the NET layer requests the MAC layer to transfer the packetto the transfer station according to the route item that matches the destination addressin the NET layer routing table.

– The NET layer sends the packet from the transport layer. The NET layer requests theMAC layer to transfer the packet to the transfer station according to the route item thatmatches the destination address of the packet in the NET layer routing table.

Transport LayerThe main function of the transport layer (L4 layer) is to provide the end-to-end communicationservice for the upper layer. As communication between the OptiX equipment and the NMS iscontrolled by the end-to-end connection-oriented service in the application layer, the L4 layerprovides only the end-to-end connectionless communication service, that is, transparent datatransfer 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.1.2 Extended ECCThe HW ECC protocol supports the use of the Ethernet as extended channels for ECCtransmission. Hence, when there is no DCC between two or more NEs, connect the EthernetNM ports or NE cascading ports of the NEs to realize communication through extended ECCs.

Networking ModeThere are two networking modes for the extended ECC:

l Using the network cableUse a network cable to directly connect the Ethernet NM ports or NE cascading ports ofthe two NEs.

l Using the hubUse a hub or other data equipment to connect the Ethernet NM ports of related NEs.


Feature Description


Issue 02 (2008-06-20)

Figure 2-2 Networking for the extended ECC (using a network cable)

Network cable

T2000

Figure 2-3 Networking for the extended ECC (using a hub)

Network cable

Hub

T2000

The Ethernet NM port and the NE cascading port of the OptiX RTN 600 are equivalent to twoports on a hub. Hence, you can use network cables to connect NEs in series. Such seriesconnection is equivalent to the hub connection.



2-5

Figure 2-4 Networking for the extended ECC (using network cables to connect NEs in series)

Networkcable

T2000

Networkcable

CAUTIONl 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 NE isrepeatedly SCC reset.

l As both the Ethernet NM port and the NE cascading port of the OptiX RTN 600 have theMDI and MDI-X adaptive capability, either a straight-through cable or a crossover cable canbe used as the network cable for the extended ECC.

Extension ModeThere are two extension modes for the extended ECC:

l Automatic modeOn an Ethernet, the NE with the largest IP address is automatically considered the serverand other NEs are automatically clients. The NEs automatically establish TCP connectionsbetween the server and clients and also establish corresponding MAC connectionsaccording to the TCP connections. In the automatic mode, the server and clients need notbe manually specified.

l Specified modeIn the manual mode, NEs establish TCP connections between the server and clientsaccording to the server, clients, IDs of connecting ports, which are set manually, and otherinformation that is entered manually. They then establish corresponding MAC connectionsaccording to the TCP connections.

NOTE

l By default, the automatic ECC extension mode of the OptiX RTN 600 is disabled.

l The maximum number of clients to be accessed through the extended ECC is 4.

2.2 AvailabilityThe HW ECC solution requires support of the involved equipment and boards.


Feature Description


Issue 02 (2008-06-20)

Table 2-1 Availability of the HW ECC solution

Feature Applicable Board Applicable Equipment

HW ECC solution (includingthe extended ECC)

– IDU 605

SCC (all the versions) IDU 610/620

2.3 Relation with Other FeaturesIt is recommended that you adopt only one of the HW ECC solution, IP over DCC solution, andOSI over DCC solution to form a DCN.

If you combine the HW ECC solution with other solutions to form a network, note the followingpoints:

l The HW ECC protocol stack of NEs can communicate with the IP protocol stack.

l The HW ECC protocol stack of NEs can communicate with the OSI protocol stack in thesame area in the L1 layer.

l If DCC bytes are used to transparently transmit NM messages when the OptiX equipmentis used together with third-party equipment to form a network, it is recommended that youadopt the HW ECC protocol to manage the OptiX equipment.

l If DCC bytes are used to transparently transmit NM messages through the external clockinterface when the OptiX equipment is used together with third-party equipment to form anetwork, it is recommended that you adopt the HW ECC protocol to manage the OptiXequipment.

2.4 Realization PrincipleThis topic describes how to establish ECC routes, transfer messages, and realize the extendedECC in the HW ECC solution.

2.4.1 How to Establish ECC RoutesThe HW ECC solution adopts the shortest path first algorithm to establish ECC routes. In thiscontext, the shortest path refers to the path with minimum number of stations.

The following describes how an NE establishes ECC routes:

1. The physical layer of an NE maintains the status information of the DCC to which eachline port corresponds.

2. The MAC layer of the NE establishes the MAC connection to the adjacent NE.

The steps are as follows:

(1) The NE broadcasts the connection request frame (MAC_REQ) to the adjacent NE ina periodical manner.

(2) On receiving the MAC_REQ, the adjacent NE returns the connection response frame(MAC_RSP).



2-7

(3) If the MAC_RSP is received within the specified time, the NE establishes a MACconnection to the adjacent NE.

3. The NET layer of the NE establishes the NET layer routing table.The steps are as follows:

(1) According to the status of the MAC connection, the NE establishes an initial NETlayer routing table.

(2) The NE broadcasts its routing table to the adjacent NE in a periodical manner throughthe routing response message.

(3) The adjacent NE refreshes its NET layer routing table according to the received routingresponse message and the shortest path first algorithm.

(4) At the next route broadcasting time, the NE broadcasts its current NET layer routingtable to the adjacent NE.

Figure 2-5 Networking example for establishing ECC routes

NE1

NE2

NE3

NE5

NE4

The following describes how to establish ECC routes between NEs. The network shown inFigure 2-5 is provided as an example.

1. The physical layer of each NE maintains the status information of the DCC to which eachline 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 to the adjacent NE.NE1 is taken as an example to describe how to establish the MAC connection.

(1) NE1 broadcasts the frame MAC_REQ to NE2 and NE5 in a periodical manner throughits two available DCCs. The frame MAC_REQ contains the ID of NE1.

(2) On receiving the frame MAC_REQ, NE2 and NE5 return their respective MAC_RSPframes. The frame MAC_RSP from NE2 contains the ID of NE2 and the frameMAC_RSP from NE5 contains the ID of NE5.

(3) On receiving the MAC_RSP frames, NE1 establishes a MAC connection to NE2 anda MAC connection to NE5 according to the NE ID, DCC that reports the frame, andother information.

3. The NET layer of the NE establishes the NET layer routing table.NE1 is taken as an example to describe how to establish the NET layer routing table.


Feature Description


Issue 02 (2008-06-20)

(1) According to the status of the MAC connection, NE1 establishes an initial NET layerrouting 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 therouting response message.

(3) On receiving the routing response message from NE1, NE2 and NE5 refresh theirrespective NET layer routing tables. After the refreshing, in the NET layer routingtable of NE2, there is a route to NE5 and the transfer NE is NE1; in the NET layerrouting table of NE5, there is also a route to NE2 and the transfer NE is also NE1.Similarly, NE1 also adds the routes to NE3 and NE4 in its NET layer routing tableaccording to the routing response messages from NE2 and NE5. There are two routesbetween NE1 and NE3. The distance of the route whose transfer NE is NE2 is 1 andthat of the route whose transfer NE is NE5 is 2. Hence, according to the shortest pathfirst principle, only the route whose transfer NE is NE2 is retained in the NET layerrouting 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 NE1and NE2 fails. In this case, NE1 refreshes the routes to NE2 and NE3 in its NET layerrouting table according to the routing response message from NE5. Hence, the routesto NE2 and NE3 are re-established. In this way, the ECC route is protected.

2.4.2 How to Transfer MessagesIn the HW ECC solution, the messages between NEs are transferred in the NET layer of theNEs.

Figure 2-6 illustrates how the HW ECC solution transfers the messages originating from theT2000 to a destination NE.

Figure 2-6 Realization principle of message transferring (HW ECC)

DCC

MAC

NET

Ethernet

TCP

Application

Ethernet

TCP

Application

DCC

MAC

NET

L4

DCC

MAC

NET

L4

Application

T2000 Gateway NE Transfer NE Destination NE

IP IP

The realization principle is as follows:

1. The T2000 transfers application layer messages to the gateway NE through the TCPconnection between them.

2. The gateway NE extracts the messages from the TCP/IP protocol stack and reports themessages to the application layer.

3. The application layer of the gateway NE queries the address of the destination NE in themessages. If the address of the destination NE is not that of the local station, the gatewayNE queries the core routing table of the application layer according to the address of thedestination NE to obtain the corresponding route and the communication protocol stack ofthe transfer NE. As the communication protocol stack of the transfer NE in Figure 2-6 is



2-9

HW ECC, the gateway NE transfers the messages to the transfer NE through the HW ECCstack.

4. On receiving the packet that encapsulates the messages, the NET layer of the transfer NEqueries the address of the destination NE of the packet. If the address of the destination NEis not that of the local station, the transfer NE queries the NET layer routing table accordingto the address of the destination NE to obtain the corresponding route and then transfersthe packet.

5. On receiving the packet, the NET layer of the destination NE reports the packet to theapplication layer through the L4 layer because the address of the destination NE of thepacket is that of the local station. The application layer acts according to the message sentfrom the T2000.

NOTE

The core routing table synthesizes the transport layer routing tables of all communication protocol stacks. Eachroute item includes the following:

l ID of the destination NE

l Address of the transfer NE

l Communication protocol stack of the transfer NE

l Transfer distance

2.4.3 Extended ECCThe extended ECC realizes the MAC connection between adjacent NEs by using the TCPconnection.

Automatic Mode


1. Each NE obtains the IP addresses of other NEs that are in the same Ethernet through theaddress resolution protocol (ARP).

2. The NE with the largest IP address automatically becomes the server and senses the TCPrequests from the clients.

3. Other NEs automatically become clients and send TCP connection requests to the server.

4. On receiving the TCP connection request from a client, the server establishes thecorresponding TCP connection.

5. The NEs use the TCP connection as a MAC connection to realize ECC communication.

Specified Mode

The realization principle of specified mode is basically the same as that of automatic mode. Thedifference is that in the specified mode, the server, clients, and IDs of connecting ports aremanually specified.

2.5 Planning GuideWhen using the HW ECC solution, plan the parameters of an ECC network according to thesituation of the network.


Feature Description


Issue 02 (2008-06-20)

PrerequisiteYou must have an understanding of the network and the engineering requirements.

Procedure

Step 1 According to the situation of the network, select a proper NE as the gateway NE.

Follow these two 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 thataccesses the maximum number of DCCs, as the gateway NE if possible.

l Set two gateway NEs, one active and one standby, for an ECC subnet if possible.

NOTE

An ECC subnet is an ECC network that is comprised of a gateway NE and those non-gateway NEs thatcommunicate with the T2000 through the gateway NE. An ECC network can consist of one or more ECCsubnets.

Step 2 Plan the external DCN according to the position of the gateway NE and the T2000.

Follow these five principles when planning an external DCN:

l The bandwidth of the external DCN must not be lower than the DCC bandwidth that thenetwork uses. The link at 256 kbit/s already meets the requirements.

l For the consideration of stability and security, it is recommended that you do not use theoffice LAN or Internet as the transmission channel of the external DCN.

l It is recommended that you use the 2 Mbit/s channel to transport the external DCN. TheQuidway 2501 or other equivalent router is recommended.

l The channel for the external DCN should be provided by other network (not the monitorednetwork). 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 monitorednetwork.

l Provide active and standby DCN routes or gateways for the external DCN if possible.

Step 3 Plan the IDs of NEs.

Follow these four principles when planning NE IDs:

l The IDs of the NEs in a DCN should not be repeated.

l When the number of existing NEs does not exceed the range represented by the basic ID, donot use the extended ID if possible.

l For a newly built network, it is recommended that you follow a certain rule to allocate NEIDs.– For a ring network, it is recommended that you allocate NE IDs in turn, in the direction

of the primary ring (counterclockwise).– For a chain/tree network, it is recommended that you allocate NE IDs in turn from the

core to the edges.l For the NEs that are added on an existing network, allocate unused IDs to them.

Step 4 Plan the IP addresses of NEs.

Follow these three principles when planning the IP addresses of NEs:



2-11

l The IP address, subnet mask, and default gateway of the gateway NE must meet the planningrequirements of the external DCN.

l Ensure that the IP addresses of the NEs that use the extended ECC are in the same networksegment.

l Except the gateway NE, set the IP addresses of NEs according to the NE IDs.

NOTE

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.

l By default, the subnet mask is 255.255.0.0.

Step 5 Optional: If the extended ECC is to be used, plan the information of the extended ECC.

Follow these seven principles when planning the extended ECC:

l Ensure that the IP addresses of the NEs that use the extended ECC are in the same networksegment.

l If you use a hub to connect NEs or use network cables to connect NEs in series to form anetwork through the extended ECC, there must be no network loop in the Ethernet.

l If you use a hub to connect NEs to form a network through the extended ECC, do not connectother extra equipment to the hub.

l The number of clients to be accessed through the extended ECC should not exceed 4.

l It is recommended that you use the specified mode to extend the ECC. Do not use theautomatic mode.

l When several gateway NEs are connected to the T2000 through a hub, do not use theautomatic ECC extension function of the gateway NEs.

l When you use the specified mode to extend the ECC, it is recommended that you specify theNE near the T2000 as the server of the TCP connection and specify other NEs as clients. Setthe port ID to any number between 1601 and 1699.

Step 6 Optional: Plan the ECC network division solution.

Follow these five 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 numberof NEs in an ECC subnet must not exceed 100.

l When the number of NEs in an ECC network exceeds 50, it is recommended that you addgateway NEs to divide the network into several ECC subnets.

l The DCCs between ECC subnets should be prohibited.

l When dividing an ECC network, you are required to plan the corresponding external DCNs.

l The division of an ECC network should not impair the existing ECC route restoration(protection) capability.

----End


Feature Description


Issue 02 (2008-06-20)

Example

Figure 2-7 Networking example for the HW ECC solution

FiberRadio link

Network cable 2 Mbit/s channel

OptiX optical transmission equipment

OptiX radio transmission equipment

Quidway 2501 Hub

T2000

NE101

NE104

NE102

NE103

NE201

NE106

NE202

NE203

NE204

NE205

NE206

Figure 2-7 shows a transmission network that is only comprised of the OptiX equipment. Thesteps to plan the DCN are as follows:

1. As there are more than 40 sets of optical transmission equipment and also more than 70sets of radio transmission equipment, divide the ECC network to two ECC subnetsaccording to the type of equipment.

2. Select the central node of the optical transmission service NE101 and the central node ofthe radio transmission service NE202 as the gateway NE.

3. As the T2000 and NE202 are located in different sites, use a router Quidway 2501 to buildthe external DCN between them.

4. Allocate IDs and IP addresses for all the NEs according to the situation of the network.



2-13

Figure 2-8 Allocation of IDs/IP addresses for all NEs

9-10110.0.0.101

0.0.0.0

9-102129.9.0.102

0.0.0.0

11.0.0.1/16

10.0.0.100/16

10.0.0.1/16

9-104129.9.0.104

0.0.0.0

Extended ID-Basic IDIP addressGateway

9-106129.9.0.106

0.0.0.0

9-20211.0.0.20211.0.0.1

9-201129.9.0.201

0.0.0.0

9-103129.9.0.103

0.0.0.0

9-206129.9.0.206

0.0.0.0

9-205129.9.0.205

0.0.0.09-204129.9.0.204

0.0.0.0

9-203129.9.0.203

0.0.0.0

5. Plan the extended ECC.As there is no DCC between NE204 and NE205 and also between NE204 and NE206, usenetwork cables to connect the Ethernet NE port and the NE cascading port to extend theECC.Use the manual mode to extend the ECC. Set the parameters as follows:l server: 129.9.0.204

l client: 129.9.0.205, 129.9.0.206

l 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". Setthe bytes D1 to D3 on the ring to pass through NE201 to ensure that the protection of theECC routes on the ring is not affected.

2.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of the HWECC solution. An example is provided as a supplement to the configuration.

2.6.1 Configuration FlowThe configuration of the HW ECC solution consists of two parts, that is, the configuration at thenear end of the NE using the Web LCT and the creation of the NE topology on the T2000.


Feature Description


Issue 02 (2008-06-20)

Figure 2-9 Configuration flow for the HW ECC solution

Start

Modify IDs and IPaddresses for NEs

Configure DCCs forNEs

Extended ECCrequired?

DCCtransparent

transmissionrequired?

Configureextended ECCs

Configure DCCtransparent

transmission

Create NEs on theT2000

End

1

2

3

4

6

Yes

Yes

No

No

Query ECC routes atthe gateway NE

5

Table 2-2 Description of the configuration flow of the HW ECC solution

Number Description

① l When setting the IP address information for the gateway NE, you may needto set the default gateway, in addition to setting the IP address and subnetmask, depending on the situation of the external DCN.

l For the process of modifying the ID of an NE, see 2.6.2 Modifying the NEID.

l For the process of modifying the IP address information of an NE, see 2.6.3Modifying the Communication Parameters of an NE.



2-15

Number Description

② l The Protocol Type of the line port should be set to HW ECC (defaultvalue).

l The Channel Type of the SDH port should be set to D1-D3 (default value).

l The DCC type of the PDH microwave port adjusts automatically accordingto the radio work mode and the type of the equipment on the opposite side.Hence, manual intervention is not required.

l When dividing an ECC network, set the enable status of the DCC betweenECC subnets to Disable.

l For the configuration process, see 2.6.4 Configuring DCCs.

③ l Set the ECC extended mode to Specified mode.

l For the NE that is selected as the server, set the Port at the server side.

l For the NEs that are planned as clients, set the Opposite IP and Port at theclient 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.

l For the configuration process, see 2.6.5 Configuring the ExtendedECC.

④ l The IDU 605 does not support DCC transparent transmission.

l For the configuration process, see 2.6.6 Configuring DCC TransparentTransmission.

⑤ l An ECC route exists between the gateway NE and each of its managednon-gateway NEs.

l No ECC route exists between the gateway NE and each of other NEs inECC subnets.

l ECC routes follow the shortest path first principle.

l For the querying process, see 2.6.7 Querying ECC Routes.

⑥ 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.6.8 Creating NEs Using the SearchMethod.

l Create NEs one by one by using the manual method.For the configuration process, see 2.6.9 Creating NEs Using the ManualMethod.

2.6.2 Modifying the NE IDModify the NE ID according to the engineering planning to ensure that each NE ID is unique.The modification does not affect services but affects communication between the Web LCT andthe NE.


Feature Description


Issue 02 (2008-06-20)

Prerequisitel The user must log in to the NE.

l The user must have the system level authority.

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > NEAttribute 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.

----End

ParametersParameter Value Range Default Value Description

New ID 1 to 49135 - l The new ID refers to the basic ID. Whenthe extended ID is not used, the basic IDof an NE within any network that ismanaged by an NMS must be unique.

l Set this parameter according to theplanning of the DCN.

New Extended ID 1 to 254 9 l When the number of existing NEs doesnot exceed the range represented by thebasic ID, do not modify the extended ID.

l It is recommended that you use thedefault value.

NOTE

The NE ID has 24 bits. The highest eight bits represent the subnet ID (or the extended ID) and the lowest 16bits represent the basic ID. For example, if the ID of an NE is 0x090001, the subnet ID of the NE is 9 and thebasic ID is 1.

PostrequisiteAfter the modification of the NE ID, create the NE and log in to the NE again. Then, you canestablish communication between the NE and the Web LCT.



2-17

2.6.3 Modifying the Communication Parameters of an NEThe communication parameters of an NE include the IP address of the NE, the extended ID, thegateway IP, the subnet mask, and the NSAP address.



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.

Step 3 Click Apply.

----End


IP - Before an NE isdelivered from thefactory, the IPaddress of the NE isset to 129.9.0.x,where x representsthe preset basic ID ofthe NE.

In the case of the HW ECC solution, followthese three principles when setting the IPaddress:l The IP address, subnet mask, and default

gateway of the gateway NE must meet theplanning requirements of the externalDCN.

l Ensure that the IP addresses of the NEsthat use the extended ECC are in the samenetwork segment.

l Set the IP addresses of the NEs except thegateway NE according to the NE IDs.More specifically, set the IP address ofsuch an NE to 0x81000000+ID. Forexample, if the NE ID is 0x090001, setthe IP address to 129.9.0.1.

Gateway IP - 0.0.0.0

Subnet Mask - 255.255.0.0

Extended ID 1 to 254 9 l When the number of existing NEs doesnot exceed the range represented by thebasic ID, do not modify the extended ID.



Feature Description


Issue 02 (2008-06-20)

Parameter Value Range Default Value Description

NSAP Address - - This parameter is valid only when the OSIover DCC solution is applied. Thisparameter is used to set only the area ID ofan NSAP address. The other parts of theNSAP address are automatically generatedby the NE.

2.6.4 Configuring DCCsTo meet the NM requirements of a complicated network, it is necessary to set the channel typeand protocol type of the DCC according to the network planning.



Precautions

The IDU 610/620 can simultaneously support twelve channels comprising byte D1, twelvechannels comprising bytes D1 to D3, six channels comprising bytes D4 to D12, and two channelscomprising bytes D1 to D12. If the DCC communication configuration already exceeds therestriction, close or adjust the DCCs of certain ports, depending on the actual situation. The IDU605 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 > DCCManagement 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. Select the DCC to be modified and click Delete.2. Click Create.

The system displays the Create dialog box.3. Set the DCC.



2-19

4. Click OK.

Step 3 Optional: Modify the enable status of a DCC.1. Double-click the cell in the Enable Status column to which the DCC corresponds. Set the

required state in the drop-down box.2. Click Apply.

----End


Port Line ports, externalclock interface

- The IDU 605 does not support the externalclock interface.

Enabled/Disabled Enabled, Disabled Enabled (in the caseof line ports)Disabled (in the caseof the external clockinterface)

It is recommended that you use the defaultvalue except in the following cases:l Set Enabled/Disabled of the port that is

connected to another ECC subnet toDisabled.

l Set Enabled/Disabled of the port that isconnected to a third-party network butdoes not transmit NM messages toDisabled.

l When the DCC transparent transmissionthrough the external clock interfacesolution is applied, set Enabled/Disabled of the used external clockinterface to Enabled.

Channel Type D1-D1, D1-D3, D4-D12, D1-D12

D1-D1 (when theIF1A/B boardtransmits PDHmicrowave signalsof a capacity lessthan 16xE1 signals)D1-D3 (in othercases)

It is recommended that you use the defaultvalue except the following cases:l When the IP over DCC solution or OSI

over DCC solution is applied, setChannel Type of the SDH line ports tothe same value as the channel type ofthird-party network.

l When the DCC transparent transmissionsolution is applied, the channel type of theSDH line ports must not conflict with thechannel type of the third-party network.

Protocol Type HW ECC, TCP/IP,OSI

HW ECC It is recommended that you use the defaultvalue except the following cases:l When the IP over DCC solution is

applied, set Protocol Type to TCP/IP.l When the OSI over DCC solution is

applied, set Protocol Type to OSI.


Feature Description


Issue 02 (2008-06-20)


LAPD Role User, Network User l This parameter is valid only whenProtocol Type is set to OSI.

l Set LAPD Role to User at one end of aDCC and to Network at the other end ofthe DCC.

2.6.5 Configuring the Extended ECCWhen there is no DCC between two or more NEs, connect the Ethernet NM ports or NE cascadingports on the SCC boards of the NEs to realize communication through the extended ECC.



Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > ECCManagement 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.

Step 4 Click Apply.The system displays the prompt "This operation will reset communication between NEs. Areyou sure to continue?"

Step 5 Click OK.

----End


ECC ExtendedMode

Auto mode,Specified mode

Specified mode It is recommended that you use the defaultvalue.

Port (on the serverside)

1601 to 1699 1601 l This parameter is valid only when ECCExtended Mode is set to Specifiedmode.

l Set this parameter only when the NEfunctions as the server of the extendedECC. Generally, select the NE that is thenearest to the T2000 as the server.

l Set this parameter to a value in the rangefrom 1601 to 1699.



2-21


Opposite IP (on theclient side)

- - l This parameter is valid only when ECCExtended Mode is set to Specifiedmode.

l Set this parameter only when the NEfunctions 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.

l Set Opposite IP and Port to the IPaddress and port number of the server NErespectively.

Port (on the clientside)

1601 to 1699 1601

2.6.6 Configuring DCC Transparent TransmissionThe OptiX equipment supports the DCC transparent transmission function. With this function,the equipment can transparently transmit NM messages when the OptiX equipment is usedtogether with other equipment to form a network and can also transparently transmit themanagement messages between ECC subnets.



Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCCManagement 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 dialogbox.

Step 4 Set the parameters of the DCC transparent transmission byte.


Feature Description


Issue 02 (2008-06-20)

Step 5 Click OK.

----End


Source Timeslot/Porta

Line ports - -

TransparentTransmission ofOverhead Byte atSource Port

D1, D2, D3, D4, D5,D6, D7, D8, D9,D10, D11, D12, E1,E2, F1, X1, X2, X3,X4b

D1 l Only one overhead byte can be selectedat one time.

l X1, X2, X3, and X4 represent the self-defined overhead bytes that are usedwhen asynchronous data services aretransmitted.

l The overhead byte cannot be the byte thatis used (for example, the byte used by aDCC that is used).

Sink Timeslot/Porta Line ports - -

TransparentTransmission ofOverhead Byte atSink Port

D1, D2, D3, D4, D5,D6, D7, D8, D9,D10, D11, D12, E1,E2, F1, X1, X2, X3,X4b

D1 l Only one overhead byte can be selectedat one time.

l The overhead byte cannot be the byte thatis used (for example, the byte used by aDCC that is used).

l Generally, Transparent Transmissionof Overhead Byte at Sink Port is set tothe same value as TransparentTransmission of Overhead Byte atSource Port. These two parameters,however, can be set to different values.

NOTE

l a: The system establishes a bidirectional cross-connection between the overhead byte at the source port andthe overhead byte at the sink port. Hence, you can set a port to be a source port or a sink port.

l b: When an IF port works in the PDH mode, the number of the overhead bytes that can be used is less thanthe number of the listed overhead bytes.

2.6.7 Querying ECC RoutesBy querying ECC routes, you can verify whether the ECC configuration is correct and whetherDCC communication is normal.





2-23

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECCLink Management from the Function Tree.

Step 2 Check whether the ECC routes and their parameters in NE ECC Link Management List arein accordance with the planning.

----End

2.6.8 Creating NEs Using the Search MethodThe T2000 can find all NEs that communicate with a specific gateway NE by using the IP addressof the gateway NE, the IP address range of the gateway NE, or the NSAP address. In addition,the T2000 can create the found NEs in batches. Compared with the method of manually creatingNEs, this method is faster and more reliable.

Prerequisitel The user must log in to the T2000.

l The user must have the "NE and network operator" authority or higher.

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

The system displays the Input Search Domain dialog box.2. 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 found NEs.


Feature Description


Issue 02 (2008-06-20)

Step 5 Create NEs.1. Select an uncreated NE from the NE Found list.2. Select the corresponding Gateway of the NE.3. Click Create NE.

The system displays the Create NE dialog box.4. Specify User Name and Password.5. Click OK.

The icon of the created NE is displayed in the Main Topology.

Step 6 Optional: Repeat Step 5 to create other uncreated NEs.

----End


Address type (in theInput SearchDomain dialog box)

IP Address of GNE,NSAP Address, IPAddress Range ofGNE

IP Address Range ofGNE

l When the OSI over DCC solution isapplied, select NSAP Address.

l If the IP address of the gateway NE isknown, select IP Address of GNE.

l If the IP address of the gateway NE isunknown and only the IP address rangeof the gateway NE is known, select IPAddress Range of GNE.

Search address (inthe Input SearchDomain dialog box)

- 129.9.255.255(when Addresstype is set to IPAddress Range ofGNE)- (in the case of othersituations)

l When Address type is set to NSAPAddress, set the search address to theNSAP address of the gateway NE.

l When Address type is set to IP Addressof GNE, set the search address to the IPaddress of the gateway NE.

l When Address type is set to IP AddressRange of GNE, set the search address tothe broadcast address of the networksegment to which the gateway NEbelongs.

User name (in theInput SearchDomain dialog box)

- root This parameter specifies the user name ofthe gateway NE. It is recommended that youuse the default value.

Password (in theInput SearchDomain dialog box)

- password The default password of user root ispassword.



2-25


GNE ID - - l This parameter specifies the identifier ofthe gateway to which the NE to be createdbelongs. The identifier is represented by"NE" + "Extended ID" + "-" + "Basic ID".

l If you set GNE ID to the ID of the NE tobe created, the NE to be created is createdas a gateway NE.

l When the NE to be created can belong toseveral gateway NEs, exercise cautionwhen selecting a gateway NE accordingto the planning information for the ECCnetwork.

All NEs use thesame User andPassword (in theCreate NE dialogbox)

Selected, Notselected

Selected When All NEs use the same User andPassword is selected, you can use UserName and Password to log in to all the NEs.

User Name (in theCreate NE dialogbox)

- - You can use root as the user name at the firstlogin.

Password (in theCreate NE dialogbox)

- - The default password of user root ispassword.

NOTE

l When Address type is set to NSAP Address, ensure that the T2000 is installed with the OSI protocol stacksoftware.

l When Address type is set to IP Address of GNE or IP Address Range of GNE, and the T2000 server andgateway NE are not in the same network segment, ensure that the IP routes of the network segments to whichthe T2000 server and gateway NE belong are configured on the T2000 and related routers.

2.6.9 Creating NEs Using the Manual MethodUsing the manual method, you can only create NEs one by one. The manual method, unlike thesearch method, does not allow the creation of NEs in batches.

Prerequisitel The user must log in to the T2000.

l The user must have the "NE and network operator" authority or higher.

l The NE to be created must have normal communication with the T2000.

l If the NE to be created is a non-gateway NE, the gateway NE to which the NE to be createdbelongs must be created.


Feature Description


Issue 02 (2008-06-20)

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

The Gateway Type parameter is set toGateway

Go to the next step.

The Gateway Type parameter is set to Non-Gateway

Select the gateway to which the NE belongs,and go to Step 6.

Step 5 Specify the protocol and IP address that the NE uses.

If ... Then ...

If the Protocol parameter is set to IP Enter the IP Address of the NE.

If the Protocol parameter is set to OSI Enter the NSAP Address of the NE.



2-27

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

Parameters


ID 1 to 49135 - This parameter specifies the basic ID of theNE to be created. The NE ID that consistsof the basic ID and extended ID is theidentifier of the NE on the T2000.

Extended ID 1 to 254 9 This parameter specifies the extended ID ofthe NE to be created. Generally, theextended ID is set to 9.

Name - - The Name of each NE must be unique. It isrecommended that you set Name to acharacter string that includes the location ofthe NE, the ID of the NE, or othermeaningful information.

Gateway Type Gateway, Non-Gateway

Non-Gateway l If the NE to be created is a gateway NE,set Gateway Type to Gateway.

l If the NE to be created is a non-gatewayNE, set Gateway Type to Non-Gateway.

l If the NE to be created can function as agateway NE or a non-gateway NE, setGateway Type according to the planninginformation for the DCN.


Feature Description


Issue 02 (2008-06-20)


Affiliated Gateway - - When Gateway Type is set to Non-Gateway, set the gateway NE to which theNE to be created belongs.

Protocol IP, OSI IP l When Gateway Type is set toGateway, you need to set this parameter.

l When the OSI over DCC solution isapplied, set this parameter to OSI.

l In the case of other situations, set thisparameter to IP.

IP Address - - This parameter specifies the IP address ofthe NE to be created. When Protocol is setto IP, you need to set this parameter.

NSAP Address - - This parameter specifies the NSAP addressof the NE to be created. When Protocol isset to OSI, you need to set this parameter.You only need to set the area ID, and theother parts are automatically generated bythe NE.

NOTE

l When Protocol is set to OSI, ensure that the T2000 is installed with the OSI protocol stack software.

l 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 areconfigured on the T2000 and related routers.

2.6.10 Configuration ExampleThis topic provides an example to describe how to configure the HW ECC solution.

PrecautionsNOTE

l For the parameters in this example, refer to the example in 2.5 Planning Guide.

l This example provides only the configurations of the typical NEs: NE101, NE201, NE202, NE204, andNE205.

Procedure

Step 1 Set IDs for the NEs. See 2.6.2 Modifying the NE ID.l The extended ID of NE101 is 9 and the ID is 101.

l The extended ID of NE201 is 9 and the ID is 201.





2-29


Step 2 Set the IP address information for the NEs. See 2.6.3 Modifying the CommunicationParameters 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).l The IP address of NE201 is 129.9.0.201, the subnet mask is 255.255.0.0, and the default


gateway is 11.0.0.1.l 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).

Step 3 Set DCCs for the NEs. See 2.6.4 Configuring DCCs.l Set the Protocol Type of all line ports of all NEs to HW ECC (default value).

l Set the Channel Type of all SDH ports of all NEs to D1-D3 (default value).

l Set Channel Type of all PDH microwave ports of all NEs to the default value.

l Set Enable Status of the DCCs of both the east and west line ports on the ring of NE201 toDisable.

Step 4 Set the extended ECC parameters of NE204 and NE205. See 2.6.5 Configuring the ExtendedECC.l Set ECC Extended Mode of both NE204 and NE205 to Specified mode.

l For NE204, set Port in the Set Server field to 1601.

l For NE205, set Opposite IP to 129.9.0.204 and Port to 1601 in the Set Client field.

Step 5 Configure transparent transmission between bytes D1 to D3 of the west line port of NE201 andbytes D1 to D3 of the east line port of NE201. See 2.6.6 Configuring DCC TransparentTransmission.

Step 6 Query the ECC routes of NE101 and NE202. See 2.6.7 Querying ECC Routes.l At NE101, there is no route to NE201, NE202, NE204, and NE205.

l At NE202, there is a route to NE201 and the transfer NE is NE201.



Step 7 Use the search method to create NEs on the T2000. See 2.6.8 Creating NEs Using the SearchMethod.

The search domains are as follows:

l The search domain with the gateway NE whose IP address is 10.0.0.101

l 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 onboth the T2000 and the corresponding router to ensure that the TCP/IP communication between them is normal.


Feature Description


Issue 02 (2008-06-20)

All NEs can be successfully created.

----End

2.7 Maintenance GuideThis topic describes alarms and performance events relevant to the HW ECC solution, andproblems that occur frequently during the application of the solution.

2.7.1 Relevant Alarms and EventsWhen there is a fault in communication between the T2000 and an NE, the T2000 reports thecorresponding alarm.

Relevant Alarmsl GNE_CONNECT_FAIL

The GNE_CONNECT_FAIL alarm indicates that the connection to the gateway NE fails.When the connection between the T2000 and the gateway NE fails, the T2000 reports thisalarm.

l NE_COMMU_BREAKThe NE_COMMU_BREAK alarm indicates that communication with the NE isinterrupted. When communication between the T2000 and the NE is interrupted, the T2000reports this alarm.

l NE_NOT_LOGINThe NE_NOT_LOGIN alarm indicates that the login to the NE fails. When the T2000cannot log in to the NE, the T2000 reports this alarm.

Relevant EventsNone.

2.7.2 FAQsThis topic lists the problems that occur frequently during the application of the HW ECCsolution.

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.

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

l NE IDs conflict.

l When the T2000 connects several gateway NEs using a hub, the gateway NEs start theautomatic ECC extension function.



2-31

Q: Why does the T2000 frequently fail to log in to NEs?


l The T2000 itself is faulty.If this is the case, the T2000 should fail to log in to all NEs.

l The IP addresses of gateway NEs conflict.If this is the case, the T2000 should fail to log in to all the NEs of an ECC subnet.

l An ECC subnet is of a large scale.If this is the case, the T2000 should fail 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 ECCfrequently reset?


l The LAN to which the NE is connected accesses unknown equipment, resulting in a conflictbetween the NE and the equipment.

l There is a loop in the LAN to which the NE is connected (especially when there is a loopbetween the Ethernet NM port and the NE cascading port), resulting in a network storm.

Q: What hazards will an ECC subnet of a large scale bring?

A: Main hazards are as follows:

l The ECC route has a poor stability or a long convergence time, or even oscillates.

l The remote loading speed is slow.

l The alarm reported to the T2000 is lost.

l The T2000 cannot log in to a certain NE.

l The SCC board of a certain NE abnormally resets.


Feature Description


Issue 02 (2008-06-20)

3 IP over DCC Solution

About This Chapter

By use of the IP over DCC solution, NEs use unified DCCs to transmit the data of the TCP/IPprotocol. In this way, the NMS can manage NEs. The IP over DCC solution applies to a networkthat is comprised of the OptiX transmission equipment and the third-party equipment thatsupports the IP over DCC function. This solution also can be applied to a network that is onlycomprised of the OptiX transmission equipment.

3.1 Feature DescriptionThis topic describes the IP over DCC protocol stack and the modes in which the T2000 accessesan NE in the IP over DCC solution.

3.2 AvailabilityThe IP over DCC solution requires support of the involved equipment and boards.

3.3 Relation with Other FeaturesIt is recommended that you adopt only one of the following solutions to form a DCN: HW ECCsolution, IP over DCC solution, or OSI over DCC solution.

3.4 Realization PrincipleHow an NE transfers messages depends on the mode in which the T2000 accesses an NE. Therealization principles in different modes slightly vary from each other.

3.5 Planning GuideWhen using the IP over DCC solution, plan the parameters of a DCN depending on the situationof the network.

3.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of the IPover DCC solution. An example is provided as a supplement to the configuration.

3.7 Maintenance GuideThis topic describes alarms and performance events relevant to the IP over DCC solution, andproblems that occur frequently during the application of the solution.

OptiX RTN 600 Radio Transmission SystemFeature Description 3 IP over DCC Solution


3-1

3.1 Feature DescriptionThis topic describes the IP over DCC protocol stack and the modes in which the T2000 accessesan NE in the IP over DCC solution.

3.1.1 IP over DCC Protocol StackThe IP over DCC adopts the architecture of the standard TCP/IP protocol stack.

Figure 3-1 Architecture of the IP over DCC protocol stack

OSPF/RIP

TCP/UDP

IP

Ethernet

Transport layer

Network layer

Physical layer

PPPData link layer

Routing protocol

DCC

Physical Layer

The main function of the physical layer is to provide channels for data transmission for the dataend equipment.

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 channelsfor communication among NEs. In the IP over DCC solution, for a network that is onlycomprised of the OptiX equipment, bytes D1 to D3 in SDH frames are generally used asDCC channels; for a network that is comprised of both OptiX equipment and third-partySDH equipment, the DCC bytes used by the third-party equipment (for example, bytes D1to D3 or bytes D4 to D12) are used as DCC channels. In the PDH microwave frame, oneor three DCC bytes in the frame can be used as the DCC channel.

l Ethernet physical channel

The NE provides the Ethernet physical channel through the Ethernet NM port or the NEcascading port.

Data Link Layer

The main function of the data link layer is to provide reliable data transmission on physical links.

For DCCs, the NE adopts the PPP protocol to realize the data link layer function. The PPPprotocol complies with RFC 1661.

3 IP over DCC SolutionOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

Network LayerThe main function of the network layer is to specify the network layer address for a networkentity 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 LayerThe main function of the transport layer is to provide the end-to-end communication service forthe upper layer. The NE supports the connection-oriented TCP and the connectionless-orientedUDP.

Routing ProtocolsRouting protocols belong to the scope of the application layer. The NE supports the two routingprotocols, 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 third-party equipment does not support the OSPF protocol.

The OSPF protocol is a dynamic routing protocol that is based on the link status. The OSPFprotocol divides an autonomous system into several areas. Route nodes exchange routinginformation in an area. The route nodes at the edge of an area make summary and exchangeinformation with the routers in other areas. Areas are identified by area IDs. The area ID has thesame format as the IP address.

Currently, the OSPF protocol of the OptiX equipment supports only the routes within an areaand does not support the routes between areas. Hence, the gateway NE and all its managed non-gateway NEs must be in the same OSPF area. By default, the line port of the OptiX equipmentis 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 theNE.

In addition to the dynamic routing protocol, the NE supports static routes. Static routes aremanually configured routes. Static routes have a lower priority than dynamic routes. When thereis a route conflict, the equipment selects dynamic routes.

3.1.2 Access ModesIn the IP over DCC solution, there are two modes for the T2000 to access an NE, gateway modeand direct connection mode.

Gateway ModeIn the gateway mode, the T2000 accesses a non-gateway NE through the gateway NE. Thegateway NE queries the core routing table of the application layer according to the ID of the NEto be accessed to obtain the corresponding route.

The core routing table synthesizes the transport layer routing tables of all communicationprotocol stacks. Each route item includes the following:l ID of the destination NE





3-3

l Transfer distance

Direct Connection ModeIn the direct connection mode, the T2000 accesses an NE as the gateway NE. All transfer NEson the access path query the IP routing table of the network layer according to the IP address ofthe NE to be accessed to obtain the corresponding route.

The IP routing table is based on routing protocols. It includes both dynamic routes generated byrouting protocols and static routes configured by operators. Each route item includes thefollowing:

l Destination IP address

l Subnet mask

l IP address of the gateway

l Interface

When the T2000 adopts the direct connection mode to access an NE, there must be an IP routebetween the T2000 and the NE.

In the IP over DCC solution, theoretically, the T2000 can access any NE using the directconnection mode, that is, it can consider any NE as the gateway NE. To improve thecommunication efficiency, however, there should not be too many NEs that are accessed in thedirect connection mode in a network.

3.2 AvailabilityThe IP over DCC solution requires support of the involved equipment and boards.

Table 3-1 Availability of the IP over DCC solution


IP over DCC solution – IDU 605



If you combine the IP over DCC solution with other solutions to form a network, note thefollowing points:

l The IP protocol stack of NEs can communicate with the HW ECC protocol stack.

l The IP protocol stack of NEs cannot communicate with the OSI protocol stack.

l If DCC bytes are used to transparently transmit NM messages when the OptiX equipmentis used together with third-party equipment to form a network, you can adopt the IP protocol


Feature Description


Issue 02 (2008-06-20)

stack to manage the OptiX equipment, but it is recommended that you use the HW ECCprotocol.

l If DCC bytes are used to transparently transmit NM messages through the external clockinterface when the OptiX equipment is used together with third-party equipment to form anetwork, you can adopt the IP protocol stack to manage the OptiX equipment, but it isrecommended that you use the HW ECC protocol.


Gateway Mode

Figure 3-2 illustrates how the IP over DCC solution transfers the messages originating from theT2000 to a non-gateway NE when the T2000 adopts the gateway mode to access the NE.

Figure 3-2 Realization principle of message transferring (gateway mode)

DCC

PPP

IP

Ethernet

IP

TCP

Application

Ethernet

IP

TCP

Application

DCC

PPP

IP

TCP

DCC

PPP

IP

TCP

Application



1. The T2000 transfers application layer messages to the gateway NE through the TCPconnection between them.

2. The gateway NE extracts the messages from the TCP/IP protocol stack and reports themessages to the application layer.

3. The application layer of the gateway NE queries the address of the destination NE in themessages. If the address of the destination NE is not that of the local station, the gatewayNE queries the core routing table of the application layer according to the address of thedestination NE to obtain the corresponding route and the communication protocol stack ofthe transfer NE. As the communication protocol stack of the transfer NE in Figure 3-2 isIP, the gateway NE transfers the messages to the transfer NE through the IP protocol stack.

4. On receiving the packet that encapsulates the messages, the network layer of the transferNE queries the destination IP address of the packet. If the destination IP address is not theNE IP address of the local station, the transfer NE queries the IP routing table accordingto the destination IP address to obtain the corresponding route, and then transfers the packet.

5. On receiving the packet, the network layer of the destination NE reports the packet to theapplication layer through the transport layer because the destination IP address of the packet



3-5

is the NE IP address of the local station. The application layer acts according to the messagesent from the T2000.

Direct Connection Mode

Figure 3-3 illustrates how the IP over DCC solution transfers the messages originating from theT2000 to a destination NE when the T2000 adopts the direct connection mode to access the NE.

Figure 3-3 Realization principle of message transferring (direct connection mode)

DCC

PPP

IP

Ethernet

IP

TCP

Application

Ethernet

IP

DCC

PPP

DCC

PPP

IP

TCP

Application

T2000 Transfer NE Transfer NE Destination NE

Different from the gateway mode, the original gateway NE in the direct connection mode actsas an ordinary transfer NE and the message transferring is realized at the network layer.

3.5 Planning GuideWhen using the IP over DCC solution, plan the parameters of a DCN depending on the situationof the network.

Prerequisite

You must have an understanding of the network and the engineering requirements.

Precautions

This guide focuses on the differences between planning the IP over DCC solution and planningthe HW ECC solution. For the same parts, for example, for planning the external DCN, planningthe NE ID, and planning network division, see 2.5 Planning Guide.

Procedure


Follow these two principles when planning a gateway NE:


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 inthis subnet cannot exceed 64.


Feature Description


Issue 02 (2008-06-20)

Step 2 Plan DCCs.

Follow these three principles when planning DCCs:

l If the network is only comprised of the OptiX equipment, it is recommended that you usebytes D1 to D3 in SDH frames as DCCs.

l If the network is comprised of both OptiX equipment and third-party SDH equipment, usethe DCC bytes that the third-party equipment uses (for example, bytes D1 to D3 or D4 toD12) as DCCs.

NOTE

The DCC type of the PDH microwave port does not require manual intervention.

Step 3 Plan the IP addresses of NEs.

Follow these five principles when planning the IP addresses of NEs:

l The IP address, subnet mask, and default gateway of the gateway NE must meet the planningrequirements of the external DCN.

l The non-gateway NEs managed by the same gateway NE can be in different IP networksegments.

l The gateway NE and its managed non-gateway NEs cannot be in the same IP networksegment.As shown in Figure 3-5, the gateway NE (NE101) is in the network segment 100.1.0.0 andits managed non-gateway NEs are in other network segments.

l The IP addresses of the NEs that are interconnected with each other through Ethernet NMports must belong to a network segment that is different from the network segment to whichthe IP addresses of the NEs that are connected to the previous NEs through transmission linesbelong.As shown in Figure 3-5, NE105 and NE106 that are interconnected through the EthernetNM ports are in the network segment 200.1.0.0, the NEs that NE105 connects are in thenetwork segment 100.0.0.0, and the NEs that NE106 connects are in the network segment200.0.0.0.

l The subnet masks of the NEs that are in the same network segment must be the same.

Step 4 Plan IP routes.

Follow these three principles when planning IP routes:

l The gateway NE and its managed non-gateway NEs must be in the same OSPF area.

l The number of NEs in an OSPF area should not exceed 64.

l Plan static routes when there is no dynamic route for interconnection at the network layerbetween the T2000 and the gateway NE or between the T2000 and the NEs that need to bedirectly accessed by the T2000.

----End



3-7

Example

Figure 3-4 Networking example for the IP over DCC solution

NE101

NE102

NE104

NE105 NE106

NE207Third-party

NMS

NE208

T2000 NE103

FiberRadio link

Network cable 2 Mbit/s channel

Third-party transmission equipment

OptiX transmission equipment

Quidway 2501 Hub

Figure 3-4 shows a transmission network that is comprised of both OptiX equipment and thethird-party equipment that supports the IP over DCC feature. The steps to plan the DCN are asfollows:

1. Select NE101 that is the closest to the NMS as the gateway NE.2. As the third-party equipment uses the DCC bytes D1 to D3, it is unnecessary to modify the

DCCs of the NEs.3. Allocate IDs and IP addresses for all the NEs according to the situation of the network. The

subnet mask of all the NEs is 255.255.0.0.


Feature Description


Issue 02 (2008-06-20)

Figure 3-5 Allocation of IDs/IP addresses for all NEs


100.1.0.100/16

10.0.0.1/16

10.0.0.100/16

100.1.0.1/16

30.0.0.2/16

30.0.0.1/16

30.0.0.3/16

30.0.0.4/16

9-102100.0.0.102

0.0.0.0

9-103100.0.0.103

0.0.0.0

9-104100.0.0.105

0.0.0.0

9-105200.1.0.105

0.0.0.0

9-106200.1.0.106

0.0.0.0

9-108200.0.0.108

0.0.0.0

9-107200.0.0.107

0.0.0.0

9-101100.1.0.101

0.0.0.0

4. Plan IP routes.l As the number of the NEs is smaller than 64 and the NEs all support the OSPF protocol,

configure all NEs to the same OSPF area.l 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.

l As there are routers between the third-party NMS and NE101, using only dynamic routescannot 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.

3.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of the IPover DCC solution. An example is provided as a supplement to the configuration.

3.6.1 Configuration FlowThe configuration of the IP over DCC solution consists of two parts, that is, the configurationat the near end of the NE using the Web LCT and the creation of the NE topology on the T2000.



3-9

Figure 3-6 Configuration flow for the IP over DCC solution

Start

Modify IDs and IPaddresses for NEs


IP static routesrequired?

Add IP static routes

Create NEson the T2000

End

1

2

4

5

Yes

No

Check the IP routesof the gateway NE

3

Table 3-2 Description of the configuration flow of the IP over DCC solution

Number Description

① l Each NE must be configured with an NE ID and an IP address.

l When setting the IP address information for the gateway NE, you may needto set the default gateway to reduce the number of static IP routes, inaddition to setting the IP address and subnet mask.


l For the process of modifying the IP address information of an NE, see 2.6.3Modifying the Communication Parameters of an NE.


Feature Description


Issue 02 (2008-06-20)

Number Description

② l The DCC protocol type of the line port should be set to IP.

l The DCC channel type of the SDH port should be the same as that of third-party equipment. If the network is only comprised of the OptiX equipment,set the DCC channel type to D1-D3 (default value).

l The DCC type of the PDH microwave port does not require manualintervention.


③ l In normal situations, the gateway NE should have the routes to all itsmanaged non-gateway NEs and the route to the T2000.

l If certain routes are unavailable, request Huawei engineers to adjust theparameters of the OSPF protocol used by the NEs.

l For the querying process, see 3.6.2 Querying IP Routes.

④ For the configuration process, see 3.6.3 Creating Static IP Routes.

⑤ There are two methods to create an NE on the T2000.l Create NEs in batches by using the search method.



3.6.2 Querying IP RoutesBy querying IP routes, you can verify whether the configuration of the IP over DCC feature iscorrect and whether DCC communication is normal.



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

----End

3.6.3 Creating Static IP RoutesWhen dynamic routes fail to meet the planning requirements, manually create the correspondingstatic IP routes.



3-11



Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP StackProtocol Management from the Function Tree. Click the IP Route Management tab.

Step 2 Click New. The system displays the Create an IP Route dialog box.

Step 3 Set the parameters of the static IP route.

Step 4 Click OK.

----End

Parameters


Destination Address - - You can set this parameter to an IP addressor an IP address range.

Mask - - This parameter specifies the subnet mask ofthe set Destination Address.

Gateway IP - - This parameter specifies the IP address ofthe gateway to which the set DestinationAddress corresponds, that is, the next-hopaddress.

NOTE

The created static route has a lower priority than a dynamic route.

3.6.4 Configuration ExampleThis topic provides an example to describe how to configure the IP over DCC solution.


Feature Description


Issue 02 (2008-06-20)

PrecautionsNOTE


l This example provides only the configurations of the typical NEs, NE101, NE102, NE105, and NE106.

l For convenience of description, the following steps are described for functions one after another. In an actualconfiguration, carry out the configuration for NEs one after another.

Procedure





Step 2 Set the IP address information for the NEs. See 2.6.3 Modifying the CommunicationParameters 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).

Step 3 Set DCCs for the NEs. See 2.6.4 Configuring DCCs.l Set the DCC protocol type of all line ports of all NEs to IP.

l Set the channel type of all SDH microwave ports of all NEs to D1-D3 (default value).

l Set the channel type of all PDH microwave ports of all NEs to the default value.

Step 4 Query the IP routes of NE101. See 3.6.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.l The IP address of the T2000 server (10.1.0.100) should have corresponding routes.

l The IP address of the third-party equipment (for example, 30.0.0.4) should havecorresponding IP routes.

NOTE

If certain routes are unavailable, request Huawei engineers to adjust the parameters of the OSPF protocol usedby the NEs.

Step 5 Set an IP static route at both NE101 and NE102. See 3.6.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



3-13

– Gateway: 100.1.0.1

l The parameters of the IP static route at NE102 are as follows:– Destination address: 10.0.0.0

– Subnet mask: 255.255.0.0

– Gateway: 100.1.0.101

NOTE

Set the corresponding route on both the NMS of the third-party equipment and the router.

Step 6 Search and create NEs with 100.1.0.101 as the IP address of the gateway NE. See 2.6.8 CreatingNEs Using the Search Method.

NOTE

For a planned non-gateway NE, set Gateway to the gateway NE to which it belongs, instead of itself.


----End

3.7 Maintenance GuideThis topic describes alarms and performance events relevant to the IP over DCC solution, andproblems that occur frequently during the application of the solution.







3.7.2 FAQsThis topic lists the problems that occur frequently during the application of the IP over DCCsolution.


Feature Description


Issue 02 (2008-06-20)

Q: Compared with other solutions for communicating NM information, what advantagesdoes 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 overDCC solution, the OptiX equipment easily interworks with third-party equipment andhence the network management is simplified.

l The IP over DCC solution adopts the transfer function of the network layer of the protocolstack. Hence, no extra overhead and service channel are needed.

l The IP over DCC solution allows different vendors to multiplex the same physical channels.

l The NMS of a vendor need not be directly connected to the equipment of the vendor.

l The IP over DCC function supports the automatic rerouting function and hence can protectthe channel that transmits the management information.

l The IP over DCC solution enables the development of management tools that are based onthe mature IP protocol stack, for example, FTP and Telnet.



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.

l The IP route between the gateway NE and a non-gateway NE is faulty.To locate the fault, check the IP route between the gateway NE and the non-gateway NE.

Q: How does one use the IP over DCC solution to interconnect the OptiX equipment withthird-party equipment?

A: The steps are as follows:

1. Check the DCC bytes used by DCCs with the maintenance staff of third-party equipment.2. Check the PPP protocol parameters with the maintenance staff of third-party equipment.3. Check the parameters of the OSPF protocol with the maintenance staff of third-party

equipment.4. Configure data according to the negotiated protocol parameters and the network planning.5. Query IP routes at the NE that is interconnected to 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 interconnectedNE and a route to other third-party equipment.If no route is obtained, the OSPF protocol interconnection fails.



3-15

4 OSI over DCC Solution

About This Chapter

By use of the OSI over DCC solution, NEs use unified DCCs to transmit the data of the OSIprotocol. In this way, the NMS can manage NEs. The OSI over DCC solution applies to a networkthat is comprised of the OptiX equipment and the third-party equipment that supports the OSIover DCC function.

4.1 Feature DescriptionThis topic describes the OSI over DCC protocol stack and the modes in which the T2000 accessesan NE in the OSI over DCC solution.

4.2 AvailabilityThe OSI over DCC solution requires support of the involved equipment and boards.



4.5 Planning GuideWhen using the OSI over DCC solution, plan the parameters of a DCN according to the situationof the network.

4.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of the OSIover DCC solution. An example is provided as a supplement to the configuration.

4.7 Maintenance GuideThis topic describes alarms and performance events relevant to the OSI over DCC solution, andproblems that occur frequently during the application of the solution.

OptiX RTN 600 Radio Transmission SystemFeature Description 4 OSI over DCC Solution


4-1

4.1 Feature DescriptionThis topic describes the OSI over DCC protocol stack and the modes in which the T2000 accessesan NE in the OSI over DCC solution.

4.1.1 OSI over DCC Protocol StackThe OSI over DCC adopts the architecture of the standard OSI protocol stack.

Figure 4-1 Architecture of the OSI over DCC protocol stack

TP4

IS-IS/ES-IS/CLNP

Ethernet

Transport layer

Network layer

Physical layer

LAPDData link layer

DCC

Physical Layer

The main function of the physical layer is to provide channels for data transmission, for the dataend 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 channelsfor communication among NEs. In the OSI over DCC solution, for a network that is onlycomprised of the OptiX equipment, bytes D1 to D3 in SDH frames are generally used asDCC channels; for a network that is comprised of both OptiX equipment and third-partySDH equipment, the DCC bytes used by the third-party equipment (for example, bytes D1to D3 or bytes D4 to D12) are used as DCC channels. In the PDH microwave frame, oneor three DCC bytes in the frame can be used as the DCC channel.

l Ethernet physical channel

The NE provides the Ethernet physical channel through the Ethernet NM port or the NEcascading port.

Data Link Layer

The main function of the data link layer is to provide reliable data transmission on physical links.

For DCCs, the NE adopts the LAPD protocol to realize the data link layer function. The LAPDprotocol complies with ITU-T Q.921.

When using the LAPD protocol, you are required to set the LAPD role. For the two ends of aDCC, set the LAPD role to Network at one end and to User at the other end.

4 OSI over DCC SolutionOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

Network LayerThe main function of the network layer is to specify the network layer address for a networkentity and to provide the transferring and addressing functions.

The NE adopts the ISO-defined connectionless network service (CLNS) to realize the networklayer function. The CLNS is comprised of the following three protocols:

l Connectionless network protocol (CLNP)The CLNP protocol complies with ISO 8473. It has functions similar to the IP in the TCP/IP protocol stack. In the CLNP protocol, the network service access point (NSAP) worksas the network layer address.The NSAP functions as the IP address in the IP protocol. Its address format is as shown inFigure 4-2.

Figure 4-2 Format of the NSAP address

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 1921 20

Area address

Higher order DSP

IDP DSP

System ID

AFI IDI+pad DFI ORG RES RD Area

NSEL

The NE uses the simplified NSAP address. The simplified NSAP address includes only thefollowing three parts:– Area ID

The area ID refers to the area address shown in Figure 4-2 and has one to thirteen bytes.The area ID is used to address the routes between areas. The NSAPs of the NEs in thesame L1 route area must have the same area ID but those in the same L2 route area canhave different area IDs. You can manually set the area ID. The default value of the areaID is 0x47000400060001.

– System IDThe System ID refers to the system ID shown in Figure 4-2 and has six bytes. TheSystem ID is used to address the routes within an area. The value of the first three bytesof the System ID of the OptiX equipment is always 0x08003E. The last three bytes arethe NE ID.

– NSELThe NSEL refers to the port ID of the network layer protocol. It has one byte. The NSELof the OptiX equipment is always 0x1D.

l IS-IS protocolIn 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 stackand the ES is equivalent to the host.The IS-IS protocol is a dynamic routing protocol between one IS and another. It complieswith 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 aneighbor of an NE in a different area and is involved only in the routes in its own area. Itissues a default route that points to its closest L2 NE and accesses other areas through the



4-3

default route. The NE whose role is L2 can be a neighbor of the L2 NE in a different areaand can also be involved in the routes in the backbone area. The backbone area is formedby consecutive L2 NEs. In other words, the L2 NEs in the backbone area must beconsecutive (connected). In the network as shown in Figure 4-3, as the L2 NEs in thebackbone area are not consecutive, the NEs in area 4 are isolated from the NEs in otherareas. By default, the role of the OptiX equipment is L1.

Figure 4-3 Layered routes of IS-IS protocol routes (L2 not consecutive)

Area 1

Area 3

Area 4

Area 2

L2

Backbone

L1OSI DCN

T2000

NOTE

L2 NEs are classified into two categories, the NE with only the L2 role and the NE with both the L2 roleand the L1 role. In general, an L2 NE has the L1 role.

l ES-IS protocol

The ES-IS protocol is a dynamic routing protocol between the ES and the IS. It complieswith 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 forthe upper layer. The NE adopts the TP4 protocol to realize the transport layer function. The TP4protocol complies with ISO 8073. It has functions similar to the TCP in the TCP/IP protocolstack.

4.1.2 Access ModeIn the OSI over DCC solution, there are two modes for the T2000 to access an NE, gatewaymode and direct connection mode.


Feature Description


Issue 02 (2008-06-20)

Gateway ModeIn the gateway mode, the T2000 accesses a non-gateway NE through the gateway NE. Thegateway NE queries the core routing table of the application layer according to the ID of the NEto be accessed to obtain the corresponding route.

The core routing table synthesizes the transport layer routing tables of all communicationprotocol stacks. Each route item includes the following:l ID of the destination NE



l Transfer distance

Direct Connection ModeIn the direct connection mode, the T2000 accesses an NE as the gateway NE. All transfer NEson the access path query the L1 routing table and L2 routing table of the network layer accordingto 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 Destination System ID

l Cost

l Adjacency No.

Each route item in the L2 routing table includes the following:

l Destination Area ID

l Cost

l Adjacency No.

NOTE

The adjacency No. is the ID of an LAPD connection. You can query the link adjacency table of the data linklayer to obtain the mapping relation between the adjacency No. and the LAPD connection.

In the OSI over DCC solution, theoretically, the T2000 can access any NE using the directconnection mode, that is, the T2000 can consider any NE as the gateway NE. To improve thecommunication efficiency, there should not be too many NEs that are accessed in the directconnection mode in a network.

4.2 AvailabilityThe OSI over DCC solution requires support of the involved equipment and boards.

Table 4-1 Availability of the OSI over DCC solution


OSI over DCC solution SCC (all the versions) IDU 610/620



4-5


If you combine the OSI over DCC solution with other solutions to form a network, note thefollowing points:

l The OSI protocol stack of NEs can communicate with the HW ECC protocol stack only inthe same area in the L1 layer.

l The OSI protocol stack of NEs cannot communicate with the IP protocol stack.

l If DCC bytes are used to transparently transmit NM messages when the OptiX equipmentis used together with third-party equipment to form a network, you can adopt the OSIprotocol stack to manage the OptiX equipment, but it is recommended that you use the HWECC protocol.

l If DCC bytes are used to transparently transmit NM messages through the external clockinterface when the OptiX equipment is used together with third-party equipment to form anetwork, you can adopt the OSI protocol stack to manage the OptiX equipment, but it isrecommended that you use the HW ECC protocol.


Gateway Mode

Figure 4-4 illustrates how the OSI over DCC solution transfers T2000 messages to a non-gateway NE when the T2000 adopts the gateway mode to access the NE.

Figure 4-4 Realization principle of message transferring (gateway mode)

Ethernet

ES-IS/CLNP

TP4

Application

Ethernet

ES-IS/CLNP

TP4

Application

DCC

LAPD

IS-IS/CLNP

DCC

LAPD

IS-IS/CLNP

TP4

Application


TP4

DCC

LAPD

IS-IS/CLNP


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 thegateway NE through the TP4 connection.


Feature Description


Issue 02 (2008-06-20)

2. The gateway NE extracts the messages from the OSI protocol stack and reports themessages to the application layer.

3. The application layer of the gateway NE queries the address of the destination NE in themessages. If the address of the destination NE is not that of the local station, the gatewayNE queries the core routing table of the application layer according to the address of thedestination NE to obtain the corresponding route and the communication protocol stack ofthe transfer NE. As the communication protocol stack of the transfer NE in Figure 4-4 isOSI, the gateway NE transfers the messages to the transfer NE through the OSI protocolstack.

4. On receiving the packet that encapsulates the messages, the network layer of the transferNE queries the destination NSAP address of the packet. If the NSAP address is not that ofthe local station, the transfer NE queries the L1 routing table or the L2 routing tableaccording to the destination NSAP address to obtain the corresponding route, and thentransfers the packet.

5. On receiving the packet, the network layer of the destination NE reports the packet to theapplication layer through the transport layer because the destination NSAP address of thepacket is the address of the local station. The application layer acts according to the messagesent from the T2000.

Direct Connection Mode

Figure 4-5 illustrates how the OSI over DCC solution transfers T2000 messages to a destinationNE when the T2000 adopts the direct connection mode to access the NE.

Figure 4-5 Realization principle of message transferring (direct connection mode)

Ethernet

ES-IS/CLNP

TP4

Application

Ethernet

IS-IS/ES-IS/CLNP

DCC

LAPD

DCC

LAPD

IS-IS/CLNP

TP4

Application

T2000 Transfer NE Transfer NE Destination NE

DCC

LAPD

IS-IS/CLNP

Different from the gateway mode, the original gateway NE in the direct connection mode actsas an ordinary transfer NE and the message transferring is realized at the network layer.

4.5 Planning GuideWhen using the OSI over DCC solution, plan the parameters of a DCN according to the situationof the network.

Prerequisite

You must have an understanding of the network and the engineering requirements.



4-7

Precautions

This guide focuses on the differences between planning the OSI over DCC solution and planningthe HW ECC solution. For the same parts, for example, for planning the NE ID and planningnetwork division, see 2.5 Planning Guide.

Procedure

Step 1 Plan areas.

Follow these four principles when planning areas:

l It is recommended that the number of areas does not exceed 20. The maximum number ofareas can be 32.

l It is recommended that the number of NEs in an area does not exceed 32. The maximumnumber of NEs in an area can be 50.

l Each area should have L2 NEs and the L2 NEs must be consecutive.

l The area ID of each area must be unique.


Follow these three 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 NEto be the gateway NE.

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 32. The number of the NEs inthis subnet cannot exceed 50.


Step 3 Plan the external DCN.

Follow these four principles when planning an external DCN:

l The bandwidth of the external DCN must not be lower than the DCC bandwidth that thenetwork uses. The link at 256 kbit/s already meets the requirements.

l The router that the external DCN uses must be able to support the OSI protocol stack.

l The channel for the external DCN should be provided by another network (not the monitorednetwork).

l Active and standby DCN routes or gateways should be provided for the external DCN ifpossible.

Step 4 Plan DCCs.

Follow these two principles when planning DCCs:

l If the network is only comprised of the OptiX equipment, it is recommended that you usebytes D1 to D3 in SDH frames as DCCs.

l If the network is comprised of both OptiX equipment and third-party SDH equipment, usethe DCC bytes that the third-party equipment uses (for example, bytes D1 to D3 or D4 toD12) as DCCs.


Feature Description


Issue 02 (2008-06-20)

l The LAPD role of a DCC must be set to User at one end and to Network at the other end ofthe DCC.

NOTE

The DCC type of the PDH microwave port does not require manual intervention.

----End

Example

Figure 4-6 Networking example for the OSI over DCC solution

FiberRadio link

NE101

NE102

NE301

NE302 NE303

Third-partyNMS

T2000

NE304

OSI DCN

Network cable

NE201

NE202



Figure 4-6 shows a transmission network that is comprised of both OptiX equipment and thethird-party equipment that supports the OSI over DCC feature. The steps to plan the DCN areas 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 thenumber of the NEs in each area smaller than 32. In addition, set the four NEs on the centralring as L2 NEs to ensure that each area has an L2 NE and the L2 NEs are consecutive.



4-9

Figure 4-7 Allocation of NE areas

AREA ID: 0x394F1190 AREA ID: 0x394F1210

AREA ID: 0x394F1200

Area 1

Area 2

Area 3

Third-partyNMS

T2000

OSI DCN

L2

L2

L2

L2

2. Select the gateway NE.Select NE101, NE201, and NE301 as the gateway NEs to manage the OptiX NEs in theirown areas.

3. Select the router that supports the OSI protocol stack to form the external DCN.4. Plan DCCs.

l As the third-party equipment uses the DCC bytes D1 to D3, it is unnecessary to modifythe DCCs of the NEs.

l Set the LAPD role of each DCC to Network at the end nearer to the T2000 and toUser at the other end of the DCC.

4.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of the OSIover DCC solution. An example is provided as a supplement to the configuration.

4.6.1 Configuration FlowThe configuration of the OSI over DCC solution consists of two parts, that is, the configurationat the near end of the NE using the Web LCT and the creation of the NE topology on the T2000.


Feature Description


Issue 02 (2008-06-20)

Figure 4-8 Configuration flow for the OSI over DCC solution

Start

Modify IDs andNSAP addresses

for NEs


Create NEs on theT2000

End

1

2

5

Configure the CLNSrole

3

Query L1 routes andL2 routes

4

Table 4-2 Description of the configuration flow of the OSI over DCC solution

Number Description

① l Each NE must be configured with an NE ID and an NSAP address.

l When modifying an NSAP address, you only need to modify the area ID,and the other parts are automatically generated by the NE.


l For the process of modifying the NSAP address information of an NE, see2.6.3 Modifying the Communication Parameters of an NE.

② l The DCC protocol type of the line port should be set to OSI.

l For the two ends of a DCC, set the LAPD role to User at one end and toNetwork at the other end.

l The DCC channel type of the SDH port should be the same as that of third-party equipment. If the network is only comprised of the OptiX equipment,set the DCC channel type to D1-D3 (default value).

l The DCC type of the PDH microwave port does not require manualintervention.




4-11

Number Description

③ l By default, the CLNS role of the OptiX equipment is L1.

l For the configuration process, see 4.6.2 Configuring the CLNS Role.

④ l The L1 routing table of the L1 NE has the routes to all the NEs in the area.

l The L1 routing table of the L2 NE has the routes to all the NEs in the area.The L2 routing table of the L2 NE has the routes to other L2 NEs.

l The gateway NE has the route to the T2000 or the routes to the L2 NEsthat are in the same area as the T2000.

l The gateway NE has the routes to all non-gateway NEs.

l For the querying process, see 4.6.3 Querying OSI Routes.




Before you create an NE, install the OSI protocol stack software on the T2000server.

4.6.2 Configuring the CLNS RoleWhen the CLNS role of an NE is L1, the NE is involved in the routes in the area. When theCLNS role of an NE is L2, the NE is involved in the routes between areas. By default, the CLNSrole of the OptiX equipment is L1.



Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSIManagement from the Function Tree.

Step 2 Click the Network Layer Parameters tab.

Step 3 Set the CLNS role of the NE.

Step 4 Click Apply.The system displays the prompt "This operation will result in SCC warm reset that is serviceaffecting. Are you sure to continue?"


Feature Description


Issue 02 (2008-06-20)

Step 5 Click Yes.

----End


Configuration Role L2, L1 L1 l The NE whose Configuration Role is setto L1 cannot be a neighbor of an NE in adifferent area and is involved only in theroutes in its own area. It issues a defaultroute that points to its closest L2 NE andaccesses other areas through the defaultroute.

l The NE whose Configuration Role is setto L2 can be a neighbor of the L2 NE ina different area and can also be involvedin the routes in the backbone area. Thebackbone area is formed by consecutiveL2 NEs. That is, the L2 NEs in thebackbone area must be consecutive(connected).

4.6.3 Querying OSI RoutesBy querying OSI routes, you can verify whether the configuration of the OSI over DCC featureis correct and whether DCC communication is normal.



Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSIManagement from the Function Tree.

Step 2 Click the Routing Table tab.

Step 3 Check whether the information in Link Adjacency Table meets the planning.

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

4.6.4 Configuration ExampleThis topic provides an example to describe how to configure the OSI over DCC solution.



4-13

PrecautionsNOTE


l This example provides only the configurations of the typical NEs, NE101, NE201, NE301, and NE302.

Procedure





Step 2 Set the NSAP address information for the NEs. See 2.6.3 Modifying the CommunicationParameters of an NE.l The area ID in the NSAP address of NE101 is 0x394F1190.

l The area ID in the NSAP address of NE201 is 0x394F1210.



Step 3 Set DCCs for the NEs. See 2.6.4 Configuring DCCs.l Set Protocol for all the line ports of all the NEs to IP.

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

Step 4 Configure the CLNS role for the NEs. See 4.6.2 Configuring the CLNS Role.l The CLNS role of NE201 and NE302 is L1 (default value).

l The CLNS role of NE101 and NE301 is L2.

Step 5 Query OSI routes. See 4.6.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.l 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.6.8 Creating NEs Using the SearchMethod.

The search domains include the following:

l The search domain with the NSAP address being 0x394F1190



NOTE

l Before you search NEs, first install the OSI protocol stack software on the T2000.

l For a planned non-gateway NE, set Gateway to the gateway NE to which it belongs, instead of itself.


Feature Description


Issue 02 (2008-06-20)


----End

4.7 Maintenance GuideThis topic describes alarms and performance events relevant to the OSI over DCC solution, andproblems that occur frequently during the application of the solution.







4.7.2 FAQsThis topic lists the problems that occur frequently during the application of the OSI over DCCsolution.

Q: Compared with other solutions for communicating NM information, what advantagesand 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 overDCC solution, the OptiX equipment easily interworks with third-party equipment andhence the network management is simplified.

l The OSI over DCC solution adopts the transfer function of the network layer of the protocolstack. Hence, no extra overhead and service channel are needed.

l The OSI over DCC solution allows different vendors to multiplex the same physicalchannels.

l The NMS of a vendor need not be directly connected to the equipment of the vendor.



4-15

l The OSI over DCC function supports the automatic rerouting function and hence canprotect the channel that transmits the management information.

The disadvantages are as follows:

l The external DCN must use the router that supports the OSI protocol stack. In addition, theNM server need be installed with the OSI protocol stack software.

l The OSI network is not applied as wide as the TCP/IP network and there are not many OSI-based management tools.



l The T2000 is not installed with the OSI protocol stack or the router does not support theOSI protocol stack.If this is the case, the T2000 should fail to log in to all NEs.

l OSI routes fail.To locate the fault, query OSI routes on the NE.

Q: How does one use the OSI over DCC solution to interconnect the OptiX equipment withthird-party equipment?


1. Check the DCC bytes used by DCCs with the maintenance staff of third-party equipment.2. Check the LAPD role and other LAPD parameters with the maintenance staff of third-party

equipment.3. Check the protocol parameters of the network layer like the area ID in the NSAP address

and the CLNS role with the maintenance staff of third-party equipment.4. Configure data according to the negotiated protocol parameters and the network planning.5. Query the link adjacency table at the NE that is interconnected to 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.

6. Query the OSI routes of the OptiX NE that is in the same area as third-party equipment tocheck whether there are L1 routes to the interconnected NE and other third-party equipment.If third-party equipment is an L2 NE, it is necessary to query the OSI routes of the OptiXNE that is also an L2 NE to check whether there is an L2 route to the third-party equipment.If no route is obtained, the interconnection of the network layer protocol fails.


Feature Description


Issue 02 (2008-06-20)

5 DCC Transparent Transmission Solution

About This Chapter

By use of the DCC transparent transmission solution, vendors use different DCCs to transmitdata. In this way, communication of NM messages is realized when the vendors' equipment isused together with third-party equipment to form a network. As the NMS of a vendor can manageonly the NEs of the vendor, however, there is a great limitation.

5.1 Feature DescriptionIn general, the transmission equipment uses only bytes D1 to D3 as DCCs and does not use otherDCC bytes. Based on this characteristic, the DCC transparent transmission solution adoptsdifferent DCCs to transmit the NM messages of different vendors to realize communicationbetween NM messages.

5.2 AvailabilityThe DCC transparent transmission solution requires support of the involved equipment andboards.

5.3 Relation with Other FeaturesIf you adopt the DCC transparent transmission solution to communicate NM messages whenthe OptiX equipment is used together with third-party equipment to form a network, you canuse any of the HW ECC protocol stack, IP protocol stack, and OSI protocol stack to manage theOptiX equipment. It is recommended that you use the HW ECC protocol stack.

5.4 Realization PrincipleThe OptiX equipment realizes the transparent transmission of DCC through the overhead cross-connect matrix.

5.5 Planning GuideWhen using the DCC transparent transmission solution, plan the parameters of a DCN accordingto the situation of the network.

5.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of theDCC transparent transmission solution. An example is provided as a supplement to theconfiguration.

5.7 Maintenance Guide

OptiX RTN 600 Radio Transmission SystemFeature Description 5 DCC Transparent Transmission Solution


5-1

This topic describes alarms and performance events relevant to the DCC transparent transmissionsolution, and problems that occur frequently during the application of the solution.

5 DCC Transparent Transmission SolutionOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

5.1 Feature DescriptionIn general, the transmission equipment uses only bytes D1 to D3 as DCCs and does not use otherDCC bytes. Based on this characteristic, the DCC transparent transmission solution adoptsdifferent DCCs to transmit the NM messages of different vendors to realize communicationbetween NM messages.

When DCC bytes are used to transparently transmit NM messages, there are two networkingscenarios:

l The OptiX equipment is at the edge of a network.

l The OptiX equipment is in the center of a network.

OptiX Equipment at the Edge of a NetworkIn this networking scenario, there are two possibilities:

l Third-party equipment uses bytes D1 to D3 as DCCs.In this case, the OptiX equipment uses bytes D4 to D12 as DCCs. In addition, you need toadd a route to transparently transmit bytes D4 to D12 in the transmission network of thethird-party equipment.

Figure 5-1 DCC transparent transmission solution when the OptiX equipment is at the edgeof a network (1)

D4-D12

D4-D12D4-D12

D4-D12D4-D12

D4-D12

OptiX equipment Third-partyequipment

l 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 needto add a route to transparently transmit bytes D1 to D3 in the transmission network of thethird-party equipment.



5-3

Figure 5-2 DCC transparent transmission solution when the OptiX equipment is at the edgeof a network (2)

D1-D3

D1-D3

D1-D3


D1-D3

D1-D3 D1-D3

OptiX Equipment in the Center of a NetworkIn this networking scenario, there are two possibilities:

l Third-party equipment uses bytes D1 to D3 as DCCs.In this case, the OptiX equipment uses bytes D4 to D12 as DCCs. In addition, you need toadd a route to transparently transmit bytes D1 to D3.

Figure 5-3 DCC transparent transmission solution when the OptiX equipment is in thecenter of a network (1)

D1-D3

D1-D3D1-D3

D1-D3


D1-D3

D1-D3

l 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 needto add a route to transparently transmit bytes D4 to D12.


Feature Description


Issue 02 (2008-06-20)

Figure 5-4 DCC transparent transmission solution when the OptiX equipment is in thecenter of a network (2)

D4-D12

D4-D12D4-D12

D4-D12


D4-D12

D4-D12

5.2 AvailabilityThe DCC transparent transmission solution requires support of the involved equipment andboards.

Table 5-1 Availability of the DCC transparent transmission solution


DCC transparenttransmission solution


5.3 Relation with Other FeaturesIf you adopt the DCC transparent transmission solution to communicate NM messages whenthe OptiX equipment is used together with third-party equipment to form a network, you canuse any of the HW ECC protocol stack, IP protocol stack, and OSI protocol stack to manage theOptiX equipment. It is recommended that you use the HW ECC protocol stack.

5.4 Realization PrincipleThe OptiX equipment realizes the transparent transmission of DCC through the overhead cross-connect matrix.

In the receive direction:



5-5

1. The line board extracts the overhead bytes such as DCC bytes from the received SDHsignals, forms a 2.048 Mbit/s overhead signal stream, and sends the overhead signal streamto the overhead cross-connect matrix of the SCC board through the overhead bus.

2. The overhead cross-connect matrix transports the DCC bytes that the NE uses to the CPUand directly transports the DCC bytes that are to be transparently transmitted, to theoverhead bus of the corresponding line board.

3. The CPU processes the NM messages carried by the DCC bytes according to the protocolstack of the DCCs.

In the transmit direction:

1. The CPU of the SCC board encapsulates the NM messages into the DCC bytes accordingto the protocol stack and transmits the DCC bytes to the overhead cross-connect matrix ofthe SCC board.

2. The overhead cross-connect matrix combines the DCC bytes sent from the CPU and otheroverhead bytes (including the DCC bytes sent from the other line boards and orderwirebytes) to form a 2.048 Mbit/s overhead signal stream, and then transmits the overhead signalstream to the corresponding line board.

3. The line board extracts the overhead signal from the overhead signal stream, inserts theoverhead signal into the SDH signal, and sends the SDH signal to other NEs.

Figure 5-5 illustrates how an NE uses bytes D1 to D3 as DCCs to transparently transmit bytesD4 to D12.

Figure 5-5 Realization principle of the DCC transparent transmission

Overhead cross-connect matrix

CPU

Overheadbus

OverheadbusD1-D3

SCCboard

Lineboard

Lineboard

SDHsignal

SDHsignal

D4-D12

5.5 Planning GuideWhen using the DCC transparent transmission solution, plan the parameters of a DCN accordingto the situation of the network.


PrecautionsThis guide focuses on the differences between planning the DCC transparent transmissionsolution and planning the HW ECC solution. For the same parts, for example, for planning thegateway NE and planning the external DCN, see 2.5 Planning Guide.


Feature Description


Issue 02 (2008-06-20)

Procedure

Step 1 Plan DCCs.

Follow these three principles when planning DCCs:

l If third-party equipment uses bytes D1 to D3 as DCCs, the SDH port of the OptiX NE usesbytes D4 to D12 as DCCs.

l If third-party equipment uses bytes D4 to D12 as DCCs, the SDH port of the OptiX NE usesbytes D1 to D3 as DCCs.

l The DCC type of the PDH microwave port of the IDU 610/620 adjusts automaticallyaccording to the radio work mode and the type of the equipment on the opposite side. Hence,manual intervention is not required.

Step 2 Plan routes for DCC transparent transmission.

----End

Example

Figure 5-6 Networking example for the DCC transparent transmission solution

NE1

NE2

NE4

NE3

Third-partyNMS

T2000

FiberRadio linkNetwork cable



Figure 5-6 shows a transmission network that is comprised of both OptiX equipment and thethird-party equipment that supports the DCC transparent transmission feature. The steps to planthe DCN are as follows:



5-7

1. Plan DCCs.As the third-party equipment uses bytes D1 to D3 as DCCs, the OptiX NE uses bytes D4to D12 as DCCs.

2. Allocate IDs for the NEs and configure the IP address for the gateway NE.

Figure 5-7 Allocations of IDs and IP addresses for all NEs

T2000

9-110.0.0.10.0.0.0

9-4129.9.0.40.0.0.0


9-2129.9.0.20.0.0.0

9-3129.9.0.30.0.0.0

3. Configure NE1, NE2, NE3, and NE4 to transparently transmit bytes D1 to D3.

5.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of theDCC transparent transmission solution. An example is provided as a supplement to theconfiguration.

5.6.1 Configuration FlowThe configuration of the DCC transparent transmission solution consists of two parts, that is,the configuration at the near end of the NE using the Web LCT, and the creation of the NEtopology on the T2000.


Feature Description


Issue 02 (2008-06-20)

Figure 5-8 Configuration flow for the DCC transparent transmission solution

Start

Set IDs and IPaddresses for NEs

ConfigureDCCs for NEs

Query ECC routes at thegateway NE

1

2

4

Set DCC transparenttransmission

3

Create NEs on the T2000

End

5

Table 5-2 Description of the configuration flow of the DCC transparent transmission solution

Number Description

① l When setting the IP address information for the gateway NE, you may needto set the default gateway in addition to setting the IP address and subnetmask, depending on the situation of the external DCN.

l For the process of configuring the ID of an NE, see 2.6.2 Modifying theNE ID.

l For the process of configuring the IP address information of an NE, see2.6.3 Modifying the Communication Parameters of an NE.

② l The DCC protocol type of the line port should be set to HW ECC (defaultvalue).

l When third-party equipment uses bytes D1 to D3 as DCCs, set the DCCchannel type of the SDH port to D4-D12.

l When third-party equipment uses bytes D4 to D12 as DCCs, set the DCCchannel type of the SDH port to D1-D3.

l The DCC type of the PDH microwave port of the IDU 610/620 adjustsautomatically according to the radio work mode and the type of theequipment on the opposite side. Hence, manual intervention is not required.




5-9

Number Description

③ l Set the DCC transparent transmission bytes used by third-party equipmentfor all the NEs on the planned route.

l For the configuration process, see 2.6.6 Configuring DCC TransparentTransmission.

④ l There is an ECC route between the gateway NE and each of its managednon-gateway NEs.

l For the querying process, see 2.6.7 Querying ECC Routes.




5.6.2 Configuration ExampleThis topic provides an example to describe how to configure the DCC transparent transmissionsolution.

PrecautionsNOTE


l This example provides only the configurations of the typical NEs, NE1 and NE3.

Procedure

Step 1 Set IDs for the NEs. See 2.6.2 Modifying the NE ID.



Step 2 Set the IP address information for NE1. See 2.6.3 Modifying the Communication Parametersof an NE.

The IP address of NE1 is 10.0.0.1, the subnet mask is 255.255.0.0, and the default gateway is0.0.0.0 (default value).

Step 3 Set DCCs for the NEs. See 2.6.4 Configuring DCCs.

l Set the DCC protocol type of all line ports of all NEs to HW ECC (default value).

l Set the DCC channel type of all SDH ports of all NEs to D4-D12.

l Set the channel type of all PDH microwave ports of all NEs to the default value.


Feature Description


Issue 02 (2008-06-20)

Step 4 Configure transparent transmission between bytes D1 to D3 of the west line port of an NE andbytes D1 to D3 of the NE's east line port. Carry out the configuration for all NEs. See 2.6.6Configuring DCC Transparent Transmission.

Step 5 Query ECC routes at NE1. See 2.6.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.6.8 CreatingNEs Using the Search Method.All NEs can be successfully created.

----End

5.7 Maintenance GuideThis topic describes alarms and performance events relevant to the DCC transparent transmissionsolution, and problems that occur frequently during the application of the solution.






Relevant Events

None.

5.7.2 FAQsThis topic lists the problems that occur frequently during the application of the DCC transparenttransmission solution.

Q: Compared with other solutions for communicating NM information, what advantagesand disadvantages does the DCC transparent transmission solution have?

A: The advantages are as follows:



5-11

l This solution requires much less SCC resources because it need not implement complexprotocol suites such as IP or OSI protocols.

l This solution facilitates easy operation because it incorporates easier data configurationwhen compared with the other two solutions.

The disadvantages are as follows:

l The NMS of each vendor can be accessed to the DCN only through its own NE.

l Only DCC bytes can be transparently transmitted.

l The automatic rerouting function is weak.

Q: How does one use the DCC transparent transmission solution to interconnect the OptiXequipment with third-party equipment?


1. Check the DCC bytes used by DCCs with the maintenance staff of third-party equipmentto ensure that different vendors use different DCC bytes.

2. Analyze the routes for DCC transparent transmission with the maintenance staff of third-party equipment.

3. Configure data according to the negotiated results and the network planning.4. Query ECC routes at the gateway NE.

If there are no routes to non-gateway NEs, the interconnection fails.


Feature Description


Issue 02 (2008-06-20)

6 DCC Transparent Transmission Through theExternal Clock Interface Solution

About This Chapter

By use of the DCC transparent transmission through the external clock interface solution, DCCbytes are placed in a specified E1 and then transmitted through third-party network. In this case,the transmission bandwidth of one E1 is occupied. Hence, this solution is applied only when aPDH network or a network that does not support transparent transmission of DCC bytes existson the transmission path of NM messages.

6.1 Feature DescriptionBy using the DCC transparent transmission through the external clock interface solution, DCCbytes are loaded into the timeslots of the E1 provided by the external clock interface and thentransmitted. In this way, DCC bytes can be transparently transmitted as long as third-partynetwork can transmit E1 services.

6.2 AvailabilityThe DCC transparent transmission through the external clock interface solution requires supportof the involved equipment and boards.

6.3 Relation with Other FeaturesIf you adopt the DCC transparent transmission through the external clock interface solution tocommunicate NM messages when the OptiX equipment is used together with third-partyequipment 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 HWECC protocol stack.

6.4 Realization PrincipleThe OptiX equipment realizes the transparent transmission of DCCs through the external clockinterface by using the overhead cross-connect matrix.

6.5 Planning GuideWhen using the DCC transparent transmission through the external clock interface solution, planthe parameters of a DCN according to the situation of the network.

6.6 Configuration GuideThis topic describes the configuration flow of the DCC transparent transmission through theexternal clock interface solution. An example is provided as a supplement to the configuration.

OptiX RTN 600 Radio Transmission SystemFeature Description

6 DCC Transparent Transmission Through the ExternalClock Interface Solution


6-1

6.7 Maintenance GuideThis topic describes alarms and performance events relevant to the DCC transparent transmissionthrough the external clock interface solution, and problems that occur frequently during theapplication of the solution.




Issue 02 (2008-06-20)

6.1 Feature DescriptionBy using the DCC transparent transmission through the external clock interface solution, DCCbytes are loaded into the timeslots of the E1 provided by the external clock interface and thentransmitted. In this way, DCC bytes can be transparently transmitted as long as third-partynetwork can transmit E1 services.

There are two networking scenarios for the DCC transparent transmission through the externalclock interface solution:

l Direct access mode

An NE is directly connected to third-party network through the external clock interface.

l Indirect access mode

An NE is connected to 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 third-party network is a PDH network that provides E1 interfaces for the OptiX NEs at both ends. Inthis case, you can directly connect an E1 cable that connects to an external clock interface to thethird-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 directaccess mode is to use an E1 cable to directly connect the external clock interfaces of two OptiXNEs.

Figure 6-1 Networking example for the DCC transparent transmission through the external clockinterface solution (direct access mode)

PDH network

E1 cableDCC bytes DCC bytes

E1 cable

OptiX equipment

External clockinterface


Indirect Access Mode

Figure 6-2 provides a networking example of the indirect access mode. In this example, thethird-party network is an SDH/PDH hybrid network. PDH signals are transmitted on thetransmission path although the network provides SDH optical interfaces for the OptiX NEs atboth ends. In this case, first use an E1 cable to connect the external clock interface to an E1 portof an E1 tributary board, and then configure cross-connections between the E1 service and theline 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 aretransparently transmitted between the two NEs.




6-3

Figure 6-2 Networking example for the DCC transparent transmission through the external clockinterface solution (indirect access mode)

SDH/PDH network

Fiber

DCC bytesExternal clock

interface

E1 port of an E1tributary board Fiber

DCC bytesExternal clock

interface

E1 port of an E1tributary board

6.2 AvailabilityThe DCC transparent transmission through the external clock interface solution requires supportof the involved equipment and boards.

Table 6-1 Availability of the DCC transparent transmission through the external clock interfacesolution


DCC transparenttransmission through theexternal clock interfacesolution

SCC (all the versions) andPXC (all the versions)

IDU 610/620

6.3 Relation with Other FeaturesIf you adopt the DCC transparent transmission through the external clock interface solution tocommunicate NM messages when the OptiX equipment is used together with third-partyequipment 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 HWECC protocol stack.

6.4 Realization PrincipleThe OptiX equipment realizes the transparent transmission of DCCs through the external clockinterface by using the overhead cross-connect matrix.


1. The PXC board transmits the E1 service received on the external clock interface as 2.048Mbit/s overhead signals to the overhead cross-connect matrix of the SCC board throughthe overhead bus.

2. The overhead cross-connect matrix transports the DCC bytes that the NE uses to the CPU.

3. The CPU processes the NM messages carried by the DCC bytes according to the protocolstack of the DCCs.





Issue 02 (2008-06-20)

1. The CPU of the SCC board encapsulates the NM messages into the DCC bytes accordingto the protocol stack and transmits the DCC bytes to the overhead cross-connect matrix ofthe SCC board.

2. The overhead cross-connect matrix combines the DCC bytes sent from the CPU and otheroverhead 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 thentransmits the overhead signal stream to the external clock interface.

3. The external clock interface transmits the 2.048 Mbit/s overhead signals as an E1 serviceto third-party network.

Figure 6-3 illustrates how an NE transparently transmits DCC bytes through the external clockinterface. 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 clockinterface

Overhead cross-connect matrix

CPU

Overheadbus

SCC board

PXC board


D1-D3

6.5 Planning GuideWhen using the DCC transparent transmission through the external clock interface solution, planthe parameters of a DCN according to the situation of the network.


PrecautionsThis guide provides the planning information for the DCC transparent transmission through theexternal clock interface solution based on the planning principles for the HW ECC solution. Forthe planning principles for the HW ECC solution, see 2.5 Planning Guide.

Procedure

Step 1 Plan the access mode.l When the OptiX equipment interconnects with third-party network through E1 interfaces,

adopt the direct access mode.l When the OptiX equipment interconnects with third-party network through other service

interfaces, adopt the indirect access mode.

Step 2 Plan the DCC bytes that carry NM messages.




6-5

Any two NEs that use third-party network to transparently transmit DCC bytes must use thesame 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 third-party network.

In the case of the indirect access mode, you need to plan the ports and line timeslots for the E1service.

----End

Example

Figure 6-4 Networking example for the DCC transparent transmission through the external clockinterface solution

NE1 NE2

NE4

T2000



NE3

E1 cable

FiberRadio link

Network cable

Figure 6-4 shows a transmission network that is comprised of the OptiX equipment and third-party equipment. The third-party network provides NE1 with SDH optical interfaces andprovides 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 directaccess mode.

2. Plan the DCC bytes that carry NM messages.

NE1 and NE2 use bytes D1 to D3 to transmit NM messages.

3. Plan the transmission route of the E1 service that carries DCC bytes in the third-partynetwork.

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 port1 to the external clock interface of NE2. The E1 service occupies VC-12 timeslot 1 of the




Issue 02 (2008-06-20)

SL1 board in slot 6 of NE1. The SL1 board in slot 6 is connected to the SDH interface ofthe third-party network.

6.6 Configuration GuideThis topic describes the configuration flow of the DCC transparent transmission through theexternal clock interface solution. An example is provided as a supplement to the configuration.

6.6.1 Configuration FlowThis topic describes the added configuration for the DCC transparent transmission through theexternal 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 clockinterface solution

Start

Configure a DCC for theexternal clock interface

1

Configure a cross-connection for the E1 service

2

Is theindirect access mode

used?

No

End

Yes

Table 6-2 Description of the configuration flow of the DCC transparent transmission throughthe external clock interface solution

Number Description

① l Set Enabled/Disabled of the used external clock interface to Enabled.

l It is recommended that you set Channel Type to D1-D3 (default value).

l It is recommended that you set Protocol Type to HW ECC (default value).

l For the configuration process, See 2.6.4 Configuring DCCs.

② Create a bidirectional cross-connection between the specified timeslot of theE1 port that is connected to the external clock interface and the specifiedtimeslot of the service port that is connected to third-party network accordingto the planning information.




6-7

6.6.2 Configuration ExampleThis topic provides an example to describe how to configure the DCC transparent transmissionthrough the external clock interface solution.

PrecautionsNOTE

l For the parameters in this example, see the example in 6.5 Planning Guide.

l This example provides only the added configuration data for the DCC transparent transmission through theexternal 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.6.4 ConfiguringDCCs.l Set Enabled/Disabled to Enabled.

l Set Channel Type to D1-D3 (default value).

l 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 andVC-12 timeslot 1 of the SL1 board in slot 6 of NE1.

----End

6.7 Maintenance GuideThis topic describes alarms and performance events relevant to the DCC transparent transmissionthrough the external clock interface solution, and problems that occur frequently during theapplication of the solution.









Issue 02 (2008-06-20)


6.7.2 FAQsThis topic lists the problems that occur frequently during the application of the DCC transparenttransmission through the external clock interface solution.

Q: Which of the DCC transparent transmission through the external clock interfacesolution and the extended ECC solution is used to transfer NM messages between two NEswhen 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 portsor NE cascading ports of the two NEs. When the distance between the two NEs exceeds themaximum transmission distance of a network cable but is less than the transmission distance ofan E1 cable (the maximum transmission distance of an E1 cable is 300 meters), use the DCCtransparent transmission through the external clock interface solution. This is because theextended ECC consumes much less system resources than the DCC transparent transmissionthrough the external clock interface.

Q: Can the external clock interface be used to transparently transmit orderwire overheadbytes when the DCC transparent transmission through the external clock interfacesolution is already applied?

A: Yes, the external clock interface can be used to transparently transmit orderwire bytes whenthe DCC transparent transmission through the external clock interface solution is alreadyapplied. This is because the DCC bytes occupy only certain timeslots of the E1 service that istransmitted by the external clock interface. Hence, the other timeslots of the E1 service can beused to transparently transmit the overhead bytes used by orderwire calls, asynchronous datainterface services, and synchronous data interface services.

Q: Why does the configuration of the DCC transparent transmission through the externalclock interface solution fail?


l The external clock source mode or the external clock output mode is modified to 2 MHz.

l The wayside E1 service is configured.




6-9

7 1+1 HSB

About This Chapter

1+1 HSB is a configuration mode of 1+1 protection. With 1+1 HSB, the equipment provides a1+1 hot standby configuration for the IF board and ODU at the two ends of each hop of a radiolink to realize the protection.

7.1 Feature DescriptionThis topic describes the system configuration, protection type, switching condition, andswitching impact of the 1+1 HSB protection.

7.2 AvailabilityThe 1+1 HSB feature requires support of the involved equipment and boards.

7.3 Relation with Other FeaturesThe 1+1 HSB protection is related to the 1+1 FD protection, 1+1 SD protection, XPIC feature,N+1 protection, and SNCP.

7.4 Realization PrincipleThis topic considers the IDU 620 that is configured with one 1+1 HSB protection group as anexample to describe the principle of the 1+1 HSB protection switching.

7.5 Planning GuideFor the radio links whose transmission performance is slightly affected by multipath fading, itis recommended that you adopt the 1+1 HSB protection configuration.

7.6 Configuration GuideThe method for configuring the 1+1 HSB/FD/SD feature on the IDU 620 is different from themethod for configuring the 1+1 HSB/FD/SD feature on the IDU 605 2B.

7.7 Maintenance GuideThis topic describes how to carry out IF 1+1 protection switching, relevant alarms and events,and problems that occur frequently during the application of the protection feature.

OptiX RTN 600 Radio Transmission SystemFeature Description 7 1+1 HSB


7-1

7.1 Feature DescriptionThis topic describes the system configuration, protection type, switching condition, andswitching impact of the 1+1 HSB protection.

7.1.1 System ConfigurationThe IDU 620 and IDU 605 2B support the configuration of the 1+1 HSB protection.

Configuration of the IDU 620The IDU 620 supports one to two 1+1 HSB protection groups. One 1+1 HSB protection groupoccupies one channel and consists of the following:

l Two IF boards

l Two ODUs that are of the same type

l One antenna (with one hybrid coupler)

NOTE

l The IF board can be the IF0A board, IF0B board, IF1A board, IF1B board, or IFX board. The two IF boardsthat are in a 1+1 HSB protection group must work in the same radio work mode.

l The hybrid coupler can be balanced or unbalanced. Generally, the unbalanced hybrid coupler is used.

Figure 7-1 provides a typical configuration of one 1+1 HSB protection group on the IDU 620.

Figure 7-1 Typical configuration of one 1+1 HSB protection group (IDU 620)

FAN

Slot 20

EXT Slot 7

EXT Slot 5

PXC Slot 3

PXC Slot 1

EXT Slot 8

EXT Slot 6

EXT Slot 4

SCC Slot 2

IF

IF

PH1

ODU

ODU

IDU 620

AntennaHybridcoupler

Configuration of the IDU 605 2BThe IDU 605 2B supports one 1+1 HSB protection group. One 1+1 HSB protection groupoccupies one channel and consists of the following:

7 1+1 HSBOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

l One IDU 605 2B


l One antenna (with one hybrid coupler)

NOTE

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

Figure 7-2 Typical configuration of one 1+1 HSB protection group (IDU 605 2B)

ODU

ODU

IDU 605 2B


7.1.2 Protection TypeThe 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 formerworking channel to return to the working state some time after the former working channelis restored to normal. The period from the time the former working channel is restored tonormal until 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 isrecommended that you set the WTR time to five to twelve minutes.

l Non-revertive mode

When an NE is in the switching state, the NE keeps the state of the former working channelunchanged even though it is restored to normal unless another switching occurs.

7.1.3 Switching ConditionThe switching priority varies according to the switching condition.



7-3

Table 7-1 Switching conditions of the 1+1 HSB protection

Switching Condition Priority Description

Clear switching(external switching)

From topdownwards, thepriority isfrom thehighest tothe lowest.

All external switching states are cleared.

Lockout switching(external switching)

In any state, a switching enters the lockout state. Inthe lockout state, no switching occurs until thelockout switching is cleared.

Forced switching(external switching)

If a switching is in the lockout state, no forcedswitching occurs. Otherwise, the system switchesservices from the active board to the standby boardor from the standby board to the active boardaccording to the command. The switching thenenters the forced switching state.

The active equipment isfaulty.

If a switching is in the lockout or forced switchingstate, or if the current standby equipment is faulty,no HSB switching occurs. Otherwise, the systemswitches services from the active board to thestandby board. The switching then enters theautomatic switching state. For the trigger conditionsof the automatic switching, see Table 7-2.

Reverse switching (validonly when the reverseswitching is enabled)

When both the main IF board and the standby IFboard at the sink end report a service alarm, theysend the alarms to the source end using the MWRDIoverhead in the microwave frame. If the sink end isin the lockout switching state or in the forcedswitching state, or if the current standby equipmentis faulty, no reverse switching occurs. Otherwise, theHSB switching occurs at the source end after thereverse switching timer expires. The reverseswitching timer restarts after you successfully add aprotection group or if an HSB switching actionoccurs. The timer duration is the WTR time (in therevertive mode) or five minutes (in the non-revertivemode). After the reverse switching, the switchingenters the RDI state.

Manual switching(external switching)

If a switching is in the lockout, forced switching, orRDI state, or if the current standby equipment isfaulty, no switching occurs. Otherwise, the systemswitches services from the active board to thestandby board or from the standby board to the activeboard according to the command. The switchingthen enters the manual switching state.


Feature Description


Issue 02 (2008-06-20)


Revertive switching(valid only in therevertive mode)

When the switching is in the automatic switchingstate and the former active equipment is alreadyrestored to normal for the WTR time, a revertiveswitching occurs. Within the period from the timethe former active equipment is restored to normaluntil the time the revertive switching occurs, theswitching is in the WTR state. After the revertiveswitching, the switching enters the normal state.

Table 7-2 Trigger conditions of the automatic 1+1 HSB switching

Switching Condition Priority

The hardware of the IF board or the IF unit isfaulty.

At the same priority

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

R_LOC

R_LOF

R_LOS

MW_LOF

7.1.4 Switching ImpactWithin the 1+1 HSB switching time (shorter than 500 ms), services are interrupted.

7.2 AvailabilityThe 1+1 HSB feature requires support of the involved equipment and boards.



7-5

Table 7-3 Availability of the 1+1 HSB feature


1+1 HSB – IDU 605 2B

IF0A/IF0B (all the versions) IDU 620

IF1A/IF1B (all the versions)

IFX (all the versions)

7.3 Relation with Other FeaturesThe 1+1 HSB protection is related to the 1+1 FD protection, 1+1 SD protection, XPIC feature,N+1 protection, and SNCP.l The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD,

or 1+1 SD. The configuration mode in one direction can be different from that in anotherdirection.

l The two IF boards in an XPIC working group cannot be configured into one 1+1 HSBprotection group, but the two IF boards in different XPIC working groups can be configuredinto one 1+1 HSB protection group. Therefore, the four IF boards in two XPIC workinggroups can form two 1+1 HSB protection groups.

l The IF boards in a 1+1 HSB protection group cannot be configured to provide N+1protection.

l The radio link with 1+1 HSB configuration can work only as the service sink of an SNCPservice pair, and cannot work as the working source or protection source.

7.4 Realization PrincipleThis topic considers the IDU 620 that is configured with one 1+1 HSB protection group as anexample to describe the principle of the 1+1 HSB protection switching.

Before the Switching

Figure 7-3 1+1 HSB realization principle (before the switching, in the transmit direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

Hybridcoupler

MainODU

StandbyODU

Antenna



Feature Description


Issue 02 (2008-06-20)

1. The service board sends the received service signal to the cross-connect board.2. The cross-connect board transmits the service signal to both the main IF board and the

standby IF board.3. The main IF board and the standby IF board send the processed analog IF signal to the main

ODU and the standby ODU respectively.4. The main ODU outputs the RF signal to the hybrid coupler, which sends the RF signal to

the antenna. The standby ODU mutes (that is, does not send the RF signal).

Figure 7-4 1+1 HSB realization principle (before the switching, in the receive direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

Hybridcoupler

MainODU

StandbyODU

Antenna


1. The hybrid coupler splits the RF signal received from the antenna to two signals and sendsthem to both the main ODU and the standby ODU.

2. The main ODU and the standby ODU send the processed analog IF signal to the main IFboard and the standby IF board respectively.

3. The main IF board and the standby IF board send the service signal to the cross-connectboard.

4. The cross-connect board selects the service signal from the main IF board and sends thesignal to the service board.

5. The service board sends the service signal to the equipment at the opposite end.

After the Switching

Figure 7-5 1+1 HSB realization principle (after the switching, in the receive direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

Hybridcoupler

MainODU

StandbyODU

Antenna



7-7

Figure 7-6 1+1 HSB realization principle (after the switching, in the transmit direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

Hybridcoupler

MainODU

StandbyODU

Antenna

After a 1+1 HSB switching:

l In the receive direction, the cross-connect board selects the service signal from the standbyIF board.

l In the transmit direction, the standby ODU outputs the RF signal to the hybrid coupler,which sends the RF signal to the antenna. The main ODU mutes (that is, does not send theRF signal).

NOTE

In the case of the IDU 605 2B, the multiplexing sub-unit that is embedded in the IF unit replaces the cross-connect unit of the IDU 620 to realize the dual fed and selective receiving function.

7.5 Planning GuideFor the radio links whose transmission performance is slightly affected by multipath fading, itis 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 in the range from fiveminutes to twelve minutes. It is recommended that you set the value to ten minutes.

l It is recommended that you enable the reverse switching. If reverse switching is enabled, andboth the main IF board and the standby IF board at the sink end report a service alarm, areverse switching occurs at the source end.

l In the case of the IDU 620, although the 1+1 HSB protection has no restriction on the slotof the IF board, it is recommended that you install a pair of main and standby IF boards inslots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot6 is the main board). In the case of the IDU 605 2B, the active/standby relation of the IF unitis fixed. Hence, planning is not required.

----End



Feature Description


Issue 02 (2008-06-20)

7.6.1 Creating IF 1+1 ProtectionIn the case of the IDU 620, if the microwave link adopts 1+1 HSB/FD/SD protection, you needto create the corresponding IF 1+1 protection group.

Prerequisitel The IF boards and their corresponding ODUs that form the IF 1+1 protection must be

included in the slot layout.l The user must have the system level authority.

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LinkConfiguration from the Function Tree.

Step 2 Click the IF 1+1 Protection tab.

Step 3 Click New.The system displays the Create IF 1+1 Protection dialog box.

Step 4 Set the parameters of the IF 1+1 protection group.

Step 5 Click OK.

----End



7-9


Protection Group ID 1, 2 - l If only one IF 1+1 protection group is tobe created, it is recommended that you setProtection Group ID to 1.

l If two IF 1+1 protection groups are to becreated, it is recommended that you setthe Protection Group ID of theprotection group that is formed by the IFboards in slots 5 and 7 to 1 and theProtection Group ID of the protectiongroup that is formed by the IF boards inslots 6 and 8 to 2.

Working Mode HSB, FD, SD HSB l In the 1+1 HSB protection mode, theequipment provides a 1+1 hot standbyconfiguration for the IF board and ODUat the two ends of each hop of a radio linkto realize the protection.

l In the 1+1 FD protection mode, thesystem uses two channels that have afrequency spacing between them, totransmit and receive the same signal. Theopposite end selects signals from the tworeceived signals. With the 1+1 FDprotection, the impact of the fading onsignal transmission is reduced.

l In the 1+1 SD protection mode, thesystem uses two antennas that have aspace distance between them, to receivethe same signal. The equipment selectssignals from the two received signals.With the 1+1 SD protection, the impactof the fading on signal transmission isreduced.

l The 1+1 FD protection mode and 1+1 SDprotection mode are compatible with the1+1 HSB switching function.

l Set this parameter according to theplanning information.


Feature Description


Issue 02 (2008-06-20)


Revertive Mode Revertive, Non-Revertive

Revertive l When this parameter is set to Revertive,the NE that is in the switching statereleases the switching and enables theformer working channel to return to theworking state some time after the formerworking channel is restored to normal.

l When this parameter is set to Non-Revertive, the NE that is in the switchingstate keeps the state of the formerworking channel unchanged even thoughthe former working channel is restored tonormal unless another switching occurs.


WTR Time (s) 300 to 720 600 l This parameter is valid only whenRevertive Mode is set to Revertive.

l When the time after the former workingchannel is restored to normal reaches theset wait-to-restore (WTR) time, arevertive switching occurs.


Enable ReverseSwitching

Enable, Disable Enable l When both the main IF board and thestandby IF board at the sink end report aservice alarm, they send the alarms to thesource end by using the MWRDIoverhead in the microwave frame. Whenthis parameter at the source end is set toEnable and the reverse switchingconditions are met, the IF 1+1 protectionswitching occurs at the source end.

l This parameter is valid only whenWorking Mode is set to HSB or SD.


Working Board IF ports - Two IF boards should be installed as a pairin slots 5 and 7 (the IF board in slot 5 is themain board) or in slots 6 and 8 (the IF boardin slot 6 is the main board).

Protection Board

NOTE

Each of the following parameters should be set to the same value at the two ends of a microwave link: WorkingMode, Revertive Mode, WTR Time (s), and Enable Reverse Switching.



7-11

Postrequisitel 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 linkautomatically copies the related information of the active microwave link except thetransmission status of the ODU.

l In the case of the 1+1 FD protection, you need to configure the IF/ODU information of theactive microwave link and the information of the standby ODU later. The standbymicrowave 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 transmissionstatus of the standby ODU after you create an IF 1+1 protection group.

7.6.2 Modifying the Parameters of IF 1+1 ProtectionIn the case of the IDU 605 2B, the system automatically creates a 1+1 HSB protection group.The working mode and other parameters of the protection group can be modified.

PrerequisiteThe user must have the system level authority.

ContextIn the case of the IDU 605 2B, the board installed in slot 8 is always the active IF board (thisboard corresponds to IF port "ODU2" on the front panel of the IDU 605 2B), and the boardinstalled in slot 7 is always the standby IF board (this board corresponds to IF port "ODU1" onthe front panel of the IDU 605 2B).

Procedure



Step 3 Modify the parameters of the IF 1+1 protection.

Step 4 Click OK.

----End


Feature Description


Issue 02 (2008-06-20)


Working Mode HSB, FD, SD HSB l In the 1+1 HSB protection mode, theequipment provides a 1+1 hot standbyconfiguration for the IF board and ODUat the two ends of each hop of a radio linkto realize the protection.

l In the 1+1 FD protection mode, thesystem uses two channels that have afrequency spacing between them, totransmit and receive the same signal. Theopposite end selects signals from the tworeceived signals. With the 1+1 FDprotection, the impact of the fading onsignal transmission is reduced.

l In the 1+1 SD protection mode, thesystem uses two antennas that have aspace distance between them, to receivethe same signal. The equipment selectssignals from the two received signals.With the 1+1 SD protection, the impactof the fading on signal transmission isreduced.

l The 1+1 FD protection mode and 1+1 SDprotection mode are compatible with the1+1 HSB switching function.


Revertive Mode Revertive, Non-Revertive






7-13


WTR Time(s) 300 to 720 600 l This parameter is valid only whenRevertive Mode is set to Revertive.



Enable ReverseSwitching

Enabled, Disabled Enabled l When both the main IF board and thestandby IF board at the sink end report aservice alarm, they send the alarms to thesource end by using the MWRDIoverhead in the microwave frame. Whenthis parameter at the source end is set toEnable and the reverse switchingconditions are met, the IF 1+1 protectionswitching occurs at the source end.

l This parameter is valid only whenWorking Mode is set to HSB or SD.


NOTE

Each of the following parameters should be set to the same value at the two ends of a microwave link: WorkingMode, Revertive Mode, WTR Time (s), and Enable Reverse Switching.

Postrequisitel 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 linkautomatically copies the related information of the active microwave link except thetransmission status of the ODU.

l In the case of the 1+1 FD protection, you need to configure the IF/ODU information of theactive microwave link and the information of the standby ODU later. The standbymicrowave 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 transmissionstatus of the standby ODU after you create an IF 1+1 protection group.



Feature Description


Issue 02 (2008-06-20)

7.7.1 IF 1+1 Protection SwitchingThe IF 1+1 protection switching is an important maintenance operation.

Prerequisitel An IF 1+1 protection group must be configured.


Procedure



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

7.7.2 Relevant Alarms and EventsWhen a 1+1 HSB switching occurs on IF boards, the system reports corresponding alarms andabnormal events.

Relevant Alarmsl HSB_INDI

The HSB_INDI alarm indicates that the microwave equipment is switched.l RPS_INDI(IDU 605 2B)

The RPS_INDI alarm indicates the microwave protection switching.

Relevant Abnormal Eventsl IF 1+1 protection switching

This abnormal event indicates that the IF 1+1 protection switching occurs.

7.7.3 FAQsThis topic lists the problems that occur frequently during the application of the 1+1 HSBprotection.

Q: What states does the 1+1 HSB protection group have?

A: The 1+1 HSB protection group has the following states:



7-15

l NormalThe state when no switching occurs or the state after a switching is cleared

l AutomaticThe state after a switching is triggered by an equipment fault

l ForcedThe state after a forced switching

l ManualThe state after a manual switching

l LockoutThe state after a lockout switching

l RDIThe state after a reverse switching

l WTRThe state that exists from the time the former active equipment is restored to normal untilthe 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 IFinterface 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 mainODU. But, it is necessary to set the Configure Transmission Status of both the main ODU andthe standby ODU to Unmute on the NMS.

Q: Why does the configuration of the 1+1 HSB protection fail?


l The IF board and the corresponding ODU that form the 1+1 HSB protection are not includedin the slot layout.

l The standby IF board is configured with services.

l The IF board functions as the working source or protection source of the SNCP service.

Q: In the revertive mode, why does the switching fail to restore after the switching entersthe RDI state?

A: The revertive mode is invalid for the reverse switching. That is, although both the active andstandby equipment are normal, the system does not switch the new standby equipment to activeafter a reverse switching.

Q: When radio links work as ECC links, why is the NMS unable to receive the abnormalHSB switching event of the non-gateway NE?

A: When an HSB switching occurs, the ECC needs to reroute. As a result, the ECC between thegateway NE and the non-gateway NE is transiently interrupted and the switching event cannotbe reported.

Q: When the main ODU is configured with the 1+1 HSB protection, why is not theequipment switched when a switching event is reported after the main ODU reports aconfiguration alarm?


Feature Description


Issue 02 (2008-06-20)

A: For the 1+1 HSB protection group, the system automatically copies the data of the main ODUto the standby ODU. Hence, when the main ODU reports a configuration alarm, the standbyODU also reports the same configuration alarm. As both the main and the standby ODUs reporta configuration alarm, no switching occurs in the equipment. To notify the user that the ODUconfiguration 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 ismuted. Otherwise, the signal emitted by the standby ODU interferes with the signal of the mainODU.



7-17

8 1+1 FD

About This Chapter

1+1 FD is a configuration mode of 1+1 protection. In the 1+1 FD protection mode, the systemuses two channels that have a frequency spacing between them, to transmit and receive the samesignal. The opposite end selects signals from the two received signals. With the 1+1 FDprotection, the impact of the fading on signal transmission is reduced

8.1 Feature DescriptionThis topic describes the system configuration, protection type, switching condition, andswitching impact of the 1+1 FD protection.

8.2 AvailabilityThe 1+1 FD feature requires support of the involved equipment and boards.

8.3 Relation with Other FeaturesThe 1+1 FD protection is related to the 1+1 HSB protection, 1+1 SD protection, XPIC feature,N+1 protection, and SNCP.

8.4 Realization PrincipleThis topic considers the IDU 620 that is configured with one 1+1 FD protection group as anexample to describe the principle of the 1+1 FD protection switching.

8.5 Planning GuideIf there are enough spectrum resources, it is recommended that you adopt the 1+1 FD protectionconfiguration.



OptiX RTN 600 Radio Transmission SystemFeature Description 8 1+1 FD


8-1

8.1 Feature DescriptionThis topic describes the system configuration, protection type, switching condition, andswitching impact of the 1+1 FD protection.

8.1.1 System ConfigurationThe IDU 620 and IDU 605 2B support the configuration of the 1+1 FD protection.

Configuration of the IDU 620

The IDU 620 supports one to two 1+1 FD protection groups. One 1+1 FD protection groupoccupies two channels and consists of the following:

l Two IF boards

l Two ODUs

l One antenna (with one balanced hybrid coupler) or two antennas

NOTE

l The IF board can be the IF0A board, IF0B board, IF1A board, IF1B board, or IFX board. The two IF boardsthat are in a 1+1 FD protection group must work in the same radio work mode.

l If the two transmit frequencies used by the FD configuration are within the frequency combining range ofone hybrid coupler, use one antenna that is installed with one balanced hybrid coupler. Otherwise, use twoantennas.

Figure 8-1 and Figure 8-2 provide two typical configurations of one 1+1 FD protection groupon the IDU 620.

Figure 8-1 Typical configuration 1 of one 1+1 FD protection group (IDU 620)

FAN

Slot 20

EXT Slot 7

EXT Slot 5

PXC Slot 3

PXC Slot 1

EXT Slot 8

EXT Slot 6

EXT Slot 4

SCC Slot 2

IF

IF

PH1

ODU

ODU

IDU 620


8 1+1 FDOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

Figure 8-2 Typical configuration 2 of one 1+1 FD protection group (IDU 620)

FAN

Slot 20

EXT Slot 7

EXT Slot 5

PXC Slot 3

PXC Slot 1

EXT Slot 8

EXT Slot 6

EXT Slot 4

SCC Slot 2

IF

IF

PH1

ODU

ODU

IDU 620

Antenna

Antenna

Configuration of the IDU 605 2BThe IDU 605 2B supports one 1+1 FD protection group. One 1+1 FD protection group occupiestwo channels and consists of the following:

l One IDU 605 2B

l Two ODUs

l 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 onehybrid coupler, use one antenna that is installed with one balanced hybrid coupler. Otherwise, use two antennas.

Figure 8-3 and Figure 8-4 provide two typical configurations of one 1+1 FD protection groupon the IDU 605 2B.



8-3

Figure 8-3 Typical configuration 1 of one 1+1 FD protection group (IDU 605 2B)

ODU

ODU

IDU 605 2B


Figure 8-4 Typical configuration 2 of one 1+1 FD protection group (IDU 605 2B)

ODU

ODU

IDU 605 2B

Antenna

Antenna

8.1.2 Protection TypeThe 1+1 FD protection is classified into the revertive mode and the non-revertive mode.l Revertive mode



Feature Description


Issue 02 (2008-06-20)


When an NE is in the switching state, the NE keeps the state of the former working channelunchanged even though it is restored to normal, unless another switching occurs.

NOTE

Both the revertive mode and non-revertive mode are relevant only to the HSB switching (switching at theequipment side). For the HSM switching (switching at the channel side), regardless of whether the revertivemode is set to revertive or non-revertive, the IF board attempts to conduct a revertive switching every two minutesafter an HSM switching.

8.1.3 Switching ConditionThe 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-sideswitching has the same switching action and switching impact as the 1+1 HSB switching buthas different trigger conditions.

Table 8-1 HSB switching conditions of the 1+1 FD protection












If a switching is in the lockout or forced switchingstate, or if the current standby equipment is faulty,no switching occurs. Otherwise, the system switchesservices from the active board to the standby boardor from the standby board to the active boardaccording to the command. The switching thenenters the manual switching state.



8-5




Table 8-2 Trigger conditions of the automatic HSB switching

Switching Condition Description

The hardware of the IF board is faulty. At the same priority


POWER_FAIL

VOLT_LOS (IF board)

RADIO_TSL_HIGH

RADIO_TSL_LOW

RADIO_RSL_HIGH

IF_INPWR_ABN

CONFIG_NOSUPPORT

HSM Switching Condition

The HSM switching is the switching that occurs at the channel side. The channel-side switchingis available in the following types:

l Forced switchingThe forced switching refers to the HSM switching that occurs at the same time the HSBswitching occurs. After the forced switching, the IF board receives its own baseband signal.

l Automatic switchingThe automatic switching refers to the HSM switching that is automatically triggered by aservice alarm. After the automatic switching, the IF board receives the baseband signal sentfrom its paired IF board.

Table 8-3 Trigger conditions of the automatic HSM switching


R_LOC High


Feature Description


Issue 02 (2008-06-20)


R_LOF

R_LOS

MW_LOF

MW_FECUNCOR Medium

B1_SD (when the IF board of the IDU 620works in the PDH mode)

Low

B2_SD (when the IF board of the IDU 620works in the SDH mode)

MW_BER_SD (IDU 605 2B)

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 occursonly when the alarm in the main IF board has a higher priority than the alarm in the standby IF board. Forexample, if the main IF board has the MW_FECUNCOR alarm and the standby IF board has the B2_SDEalarm, the switching occurs; if both the main IF board and the standby IF board have only theMW_FECUNCOR alarm, no switching occurs.

l Revertive switchingAfter an automatic HSM switching, the IF board attempts to conduct a revertive switchingevery two minutes. If there is no service alarm on the active channel at this time, the IFboard releases the switching.

8.1.4 Switching ImpactIn the case of the HSB switching, within the HSB switching time (shorter than 500 ms), servicesare interrupted. In the case of the HSM switching, services are not affected as it is a hitlessswitching.

8.2 AvailabilityThe 1+1 FD feature requires support of the involved equipment and boards.

Table 8-4 Availability of the 1+1 FD feature


1+1 FD – IDU 605 2B






8-7

8.3 Relation with Other FeaturesThe 1+1 FD protection is related to the 1+1 HSB protection, 1+1 SD protection, XPIC feature,N+1 protection, and SNCP.l The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD,


l The two IF boards in an XPIC working group cannot be configured into one 1+1 FDprotection group, but the two IF boards in different XPIC working groups can be configuredinto one 1+1 FD protection group. Therefore, the four IF boards in two XPIC workinggroups can form two 1+1 FD protection groups.

l The IF boards in a 1+1 FD protection group cannot be configured to provide N+1 protection.

l The radio link with 1+1 FD configuration can work only as the service sink of an SNCPservice pair, and cannot work as the working source or protection source.

8.4 Realization PrincipleThis topic considers the IDU 620 that is configured with one 1+1 FD protection group as anexample to describe the principle of the 1+1 FD protection switching.


Figure 8-5 1+1 FD realization principle (before the switching, in the transmit direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

MainODU

StandbyODU

Antenna

Antenna

f1

f2


1. The service board sends the received service signal to the cross-connect board.2. The cross-connect board transmits the service signal to both the main IF board and the

standby IF board.3. The main IF board and the standby IF board send the processed analog IF signal to the main

ODU and the standby ODU respectively.4. The main ODU and the standby ODU output RF signals at different frequencies and send

the signals to their respective antennas.


Feature Description


Issue 02 (2008-06-20)

Figure 8-6 1+1 FD realization principle (before the switching, in the receive direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

MainODU

StandbyODU

Antenna

Antenna


1. The antennas receive RF signals and send the signals to their respective ODUs.2. The main ODU and the standby ODU send the processed analog IF signal to the main IF

board and the standby IF board respectively.3. The multiplex unit of the IF board sends the processed baseband signal to itself and to the

multiplex unit of its paired board.4. The main IF board and the standby IF board select their own baseband signal.5. The cross-connect board selects the service signal from the main IF board and sends the

signal to the service board.6. The service board sends the service signal to the equipment at the opposite end.

After the Switching

Figure 8-7 1+1 FD HSB realization principle (after the switching, in the receive direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

MainODU

StandbyODU

Antenna

Antenna

After a 1+1 FD HSB switching:

l In the receive direction, the IF boards select their own service signal. The cross-connectboard selects the signal from the standby IF board.

l In the transmit direction, no processing is needed.



8-9

Figure 8-8 1+1 FD HSM realization principle (after the switching, in the receive direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

MainODU

StandbyODU

Antenna

Antenna

After a 1+1 FD HSM switching:

l In the receive direction, the IF boards select the baseband signal from their own paired IFboard.


NOTE

l The two built-in IF units of the IDU 605 2B realize the functions of two IF boards of the IDU 620.

l The multiplexing sub-unit that is embedded in the IF unit of the IDU 605 2B realizes the functions of thecross-connect board of the IDU 620.

8.5 Planning GuideIf there are enough spectrum resources, it is recommended that you adopt the 1+1 FD protectionconfiguration.

Procedure

Plan the parameters relevant to the protection configuration.


l The spacing between the emission frequency of the main ODU and that of the standby ODUshould be greater than 56 MHz to prevent adjacent-channel interference.

l In the case of the IDU 620, a pair of main and standby IF boards must be installed in slots 5and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 isthe main board). In the case of the IDU 605 2B, the active/standby relation of the IF unit isfixed. Hence, planning is not required.

----End



Feature Description


Issue 02 (2008-06-20)


For the configuration process, see 7.6.1 Creating IF 1+1 Protection.


For the configuration process, see 7.6.2 Modifying the Parameters of IF 1+1 Protection.



For the operation process, see 7.7.1 IF 1+1 Protection Switching.

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


The HSB_INDI alarm indicates that the microwave equipment is switched.l HSM_INDI

The HSM_INDI alarm indicates that the microwave channel is switched.l RPS_INDI(IDU 605 2B)




8.7.3 FAQsThis topic lists the problems that occur frequently during the application of the 1+1 FDprotection.

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:



8-11

l NormalThe state when no switching occurs or the state after a switching is cleared





l WTRThe state that exists from the time the former active equipment is restored to normal untilthe time the revertive switching occurs in the revertive mode

At the channel side, the 1+1 FD protection group has the following states:

l NormalThe state when no switching occurs

l ForcedThe state after an HSB switching

l AutomaticThe 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 IFinterface of the standby IF board?

A: It is unnecessary. The system automatically copies the data of the main IF board to the standbyIF board. But, it is necessary to configure the ODU interface data of both the main ODU andthe standby ODU on the NMS.

Q: Why does the configuration of the 1+1 FD protection fail?


l The IF board and the corresponding ODU that form the 1+1 FD protection are not includedin the slot layout.

l The main IF board and the standby IF board are not configured in paired slots.



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, thesource end cannot clear the service alarm at the sink end by switching the working ODU. Thereverse switching is invalid for the 1+1 FD mode.



Feature Description


Issue 02 (2008-06-20)

A: When an HSB switching occurs, the ECC needs to reroute. As a result, the ECC between thegateway NE and the non-gateway NE is transiently interrupted and the switching event cannotbe reported.



8-13

9 1+1 SD

About This Chapter

1+1 SD is a configuration mode of 1+1 protection. In the 1+1 SD protection mode, the systemuses two antennas that have a space distance between them, to receive the same signal. Theequipment selects signals from the two received signals. With the 1+1 SD protection, the impactof the fading on signal transmission is reduced.

9.1 Feature DescriptionThis topic describes the system configuration, protection type, switching condition, andswitching impact of the 1+1 SD protection.

9.2 AvailabilityThe 1+1 SD feature requires support of the involved equipment and boards.

9.3 Relation with Other FeaturesThe 1+1 SD protection has different relationships with different protection features.

9.4 Realization PrincipleThis topic considers the IDU 620 that is configured with one 1+1 SD protection group as anexample to describe the principle of the 1+1 SD protection switching.

9.5 Planning GuideFor the radio links whose transmission performance is significantly affected by multipath fading,it is recommended that you adopt the 1+1 SD protection configuration.



OptiX RTN 600 Radio Transmission SystemFeature Description 9 1+1 SD


9-1

9.1 Feature DescriptionThis topic describes the system configuration, protection type, switching condition, andswitching impact of the 1+1 SD protection.

9.1.1 System ConfigurationThe IDU 620 and IDU 605 2B support the configuration of the 1+1 SD protection.

Configuration of the IDU 620The IDU 620 supports one to two 1+1 SD protection groups. One 1+1 SD protection groupoccupies one channel and consists of the following:

l Two IF boards


l Two antennas

NOTE

The IF board can be the IF0A board, IF0B board, IF1A board, IF1B board, or IFX board. The two IF boardsthat are in a 1+1 SD protection group must work in the same radio work mode.

Figure 9-1 provides a typical configuration of one 1+1 SD protection group on the IDU 620.

Figure 9-1 Typical configuration of one 1+1 SD protection group (IDU 620)

FAN

Slot 20

EXT Slot 7

EXT Slot 5

PXC Slot 3

PXC Slot 1

EXT Slot 8

EXT Slot 6

EXT Slot 4

SCC Slot 2

IF

IF

PH1

ODU

ODU

IDU 620

Antenna

Antenna

Configuration of the IDU 605 2BThe IDU 605 2B supports one 1+1 SD protection group. One 1+1 SD protection group occupiesone channel and consists of the following:

9 1+1 SDOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

l One IDU 605 2B


l Two antennas

Figure 9-2 provides a typical configuration of one 1+1 SD protection group on the IDU 605 2B.

Figure 9-2 Typical configuration of one 1+1 SD protection group (IDU 605 2B)

ODU

ODU

IDU 605 2B

Antenna

Antenna

9.1.2 Protection TypeThe 1+1 SD protection is classified into the revertive mode and the non-revertive mode.l Revertive mode


l Non-revertive modeWhen an NE is in the switching state, the NE keeps the state of the former working channelunchanged even though it is restored to normal, unless another switching occurs.

NOTE

Both the revertive mode and non-revertive mode are relevant only to the HSB switching (switching at theequipment side). For the HSM switching (switching at the channel side), regardless of whether the revertivemode is set to revertive or non-revertive, the IF board attempts to conduct a revertive switching every two minutesafter an HSM switching.

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



9-3

HSB Switching ConditionThe HSB switching is the switching that occurs at the equipment side. The equipment-sideswitching has the same switching action and switching impact as the 1+1 HSB switching buthas different trigger conditions.

Table 9-1 HSB switching conditions of the 1+1 SD protection











Reverse switching (validonly when the reverseswitching is enabled)

When both the main IF board and the standby IFboard at the sink end report a service alarm, theysend the alarms to the source end using the MWRDIoverhead in the microwave frame. If the sink end isin the lockout switching state or in the forcedswitching state, or if the current standby equipmentis faulty, no reverse switching occurs. Otherwise, theHSB switching occurs at the source end after thereverse switching timer expires. The reverseswitching timer restarts after you successfully add aprotection group or if an HSB switching actionoccurs. The timer duration is the WTR time (in therevertive mode) or five minutes (in the non-revertivemode). After the reverse switching, the switchingenters the RDI state.


Feature Description


Issue 02 (2008-06-20)



If a switching is in the lockout, forced switching, orRDI state, or if the current standby equipment isfaulty, no switching occurs. Otherwise, the systemswitches services from the active board to thestandby board or from the standby board to the activeboard according to the command. The switchingthen enters the manual switching state.



Table 9-2 Trigger conditions of the automatic HSB switching


The hardware of the IF board is faulty. At the same priority


POWER_FAIL

VOLT_LOS (IF board)

RADIO_TSL_HIGH

RADIO_TSL_LOW

RADIO_RSL_HIGH

IF_INPWR_ABN

CONFIG_NOSUPPORT

HSM Switching ConditionThe HSM switching is the switching that occurs at the channel side. The channel-side switchingis available in the following types:

l Forced switchingThe forced switching refers to the HSM switching that occurs at the same time the HSBswitching occurs. After the forced switching, the IF board receives its own baseband signal.

l Automatic switching



9-5

The automatic switching refers to the HSM switching that is automatically triggered by aservice alarm. After the automatic switching, the IF board receives the baseband signal sentfrom its paired IF board.

Table 9-3 Trigger conditions of the automatic HSM switching


R_LOC High

R_LOF

R_LOS

MW_LOF

MW_FECUNCOR Medium

B1_SD (when the IF board of the IDU 620works in the PDH mode)

Low

B2_SD (when the IF board of the IDU 620works in the SDH mode)

MW_BER_SD (IDU 605 2B)

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 occursonly when the alarm in the main IF board has a higher priority than the alarm in the standby IF board. Forexample, if the main IF board has the MW_FECUNCOR alarm and the standby IF board has the B2_SDEalarm, the switching occurs; if both the main IF board and the standby IF board have only theMW_FECUNCOR alarm, no switching occurs.

l Revertive switchingAfter an automatic HSM switching, the IF board attempts to conduct a revertive switchingevery two minutes. If there is no service alarm on the active channel at this time, the IFboard releases the switching.

9.1.4 Switching ImpactIn the case of the HSB switching, within the HSB switching time (shorter than 50 ms), servicesare interrupted. In the case of the HSM switching, services are not affected as it is a hitlessswitching.

9.2 AvailabilityThe 1+1 SD feature requires support of the involved equipment and boards.


Feature Description


Issue 02 (2008-06-20)

Table 9-4 Availability of the 1+1 SD feature


1+1 SD – IDU 605 2B




9.3 Relation with Other FeaturesThe 1+1 SD protection has different relationships with different protection features.l The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD,


l The two IF boards in an XPIC working group cannot be configured into one 1+1 SDprotection group, but the two IF boards in different XPIC working groups can be configuredinto one 1+1 SD protection group. Therefore, the four IF boards in two XPIC workinggroups can form two 1+1 SD protection groups.

l The IF boards in a 1+1 SD protection group cannot be configured to provide N+1 protection.

l The radio link with 1+1 SD configuration can work only as the service sink of an SNCPservice pair, and cannot work as the working source or protection source.

9.4 Realization PrincipleThis topic considers the IDU 620 that is configured with one 1+1 SD protection group as anexample to describe the principle of the 1+1 SD protection switching.


Figure 9-3 1+1 SD realization principle (before the switching, in the transmit direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

MainODU

StandbyODU

Antenna

Antenna


1. The service board sends the received service signal to the cross-connect board.



9-7

2. The cross-connect board transmits the service signal to both the main IF board and thestandby IF board.

3. The main IF board and the standby IF board send the processed analog IF signal to the mainODU and the standby ODU respectively.

4. The main ODU outputs the RF signal to the hybrid coupler, which sends the RF signal tothe antenna. The standby ODU mutes (that is, does not send the RF signal).

Figure 9-4 1+1 SD realization principle (before the switching, in the receive direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

MainODU

StandbyODU

Antenna

Antenna


1. The antennas receive RF signals and send the signals to their respective ODUs.2. The main ODU and the standby ODU send the processed analog IF signal to the main IF

board and the standby IF board respectively.3. The multiplex unit of the IF board sends the processed baseband signal to itself and to the

multiplex unit of its paired board.4. The main IF board and the standby IF board select their own baseband signal.5. The cross-connect board selects the service signal from the main IF board and sends the

signal to the service board.6. The service board sends the service signal to the equipment at the opposite end.

After the Switching

Figure 9-5 1+1 SD HSB realization principle (after the switching, in the receive direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

MainODU

StandbyODU

Antenna

Antenna


Feature Description


Issue 02 (2008-06-20)

Figure 9-6 1+1 SD HSB realization principle (after the switching, in the transmit direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

MainODU

StandbyODU

Antenna

Antenna

After a 1+1 SD HSB switching:

l In the receive direction, the IF boards select their own service signal. The cross-connectboard selects the signal from the standby IF board.

l In the transmit direction, the standby ODU outputs the RF signal to the hybrid coupler,which sends the RF signal to the antenna. The main ODU mutes (that is, does not send theRF signal).

Figure 9-7 1+1 SD HSM realization principle (after the switching, in the receive direction)

Serviceboard

Cross-connectboard

MainIF board

StandbyIF board

MainODU

StandbyODU

Antenna

Antenna

After a 1+1 SD HSM switching:

l In the receive direction, the IF boards select the baseband signal from their own paired IFboard.


NOTE

l The two built-in IF units of the IDU 605 2B realize the functions of two IF boards of the IDU 620.

l The multiplexing sub-unit that is embedded in the IF unit of the IDU 605 2B realizes the functions of thecross-connect board of the IDU 620.

9.5 Planning GuideFor the radio links whose transmission performance is significantly affected by multipath fading,it is recommended that you adopt the 1+1 SD protection configuration.

ProcedurePlan the parameters relevant to the protection configuration.



9-9

l There should be a height difference between the two antennas to make the diversity-receivedmicrowave signals with a little dependence on the space.


l It is recommended that you enable the reverse switching. If reverse switching is enabled, andboth the main IF board and the standby IF board at the sink end report a service alarm, areverse switching occurs at the source end.

l In the case of the IDU 620, a pair of main and standby IF boards must be installed in slots 5and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 isthe main board). In the case of the IDU 605 2B, the active/standby relation of the IF unit isfixed. Hence, planning is not required.

----End



For the configuration process, see 7.6.1 Creating IF 1+1 Protection.


For the configuration process, see 7.6.2 Modifying the Parameters of IF 1+1 Protection.



For the operation process, see 7.7.1 IF 1+1 Protection Switching.

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



Feature Description


Issue 02 (2008-06-20)

The HSB_INDI alarm indicates that the microwave equipment is switched.l HSM_INDI

The HSM_INDI alarm indicates that the microwave channel is switched.l RPS_INDI(IDU 605 2B)




9.7.3 FAQsThis topic lists the problems that occur frequently during the application of the 1+1 SDprotection.

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 NormalThe state when no switching takes place or the state after a switching is cleared



l RDIThe state after a reverse switching



l WTRThe state that exists from the time the former active equipment is restored to normal untilthe 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 NormalThe state when no switching takes place

l ForcedThe state after an HSB switching

l AutomaticThe 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 IFinterface of the standby IF board and the ODU interface of the standby ODU?



9-11

A: It is unnecessary. The system automatically copies the data of the main IF board and the mainODU. But, it is necessary to set the Configure Transmission Status of both the main ODU andthe standby ODU to Unmute on the NMS.

Q: Why does the configuration of the 1+1 SD protection fail?


l The IF board and the corresponding ODU that form the 1+1 SD protection are not includedin the slot layout.

l The main IF board and the standby IF board are not configured in paired slots.



Q: In the revertive mode, why does the switching fail to restore after the switching entersthe RDI state?

A: The revertive mode is invalid for the reverse switching. That is, although both the active andstandby equipment are normal, the system does not switch the new standby equipment to activeafter a reverse switching.


A: When an HSB switching takes place, the ECC needs to reroute. As a result, the ECC betweenthe gateway NE and the non-gateway NE is transiently interrupted and the switching eventcannot be reported.

Q: When the main ODU is configured with the 1+1 SD protection, why does a switchingevent occur when there is no actual switching being performed if the main ODU reports aconfiguration alarm?

A: For the 1+1 SD protection group, the system automatically copies the data of the main ODUto the standby ODU. Hence, when the main ODU reports a configuration alarm, the standbyODU also reports the same configuration alarm. As both the main and the standby ODUs reporta configuration alarm, a switching does not occur on the equipment. To notify the user that theODU 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.


Feature Description


Issue 02 (2008-06-20)

10 Cross-Polarization InterferenceCancellation

About This Chapter

Cross-polarization interference cancellation (XPIC) is a technology used together with co-channel dual-polarization (CCDP). The application of the two technologies doubles the wirelesslink capacity over the same channel.

10.1 Feature DescriptionThis topic describes CCDP and XPIC, and the system configuration for XPIC.

10.2 AvailabilityThe XPIC feature requires support of the involved equipment and boards.

10.3 Relation with Other FeaturesThe XPIC feature is related to the 1+1 protection configuration, , and ATPC feature.

10.4 Realization PrincipleThe 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.5 Planning GuidePlan XPIC parameters according to the situation of microwave links.

10.6 Creating an XPIC Protection GroupWhen two IFX boards that form an XPIC protection group are installed on an IDU, you cancreate an XPIC protection group to ensure that the XPIC protection group is configured with thesame working mode, transmission frequency, transmit power, and ATPC attributes.

10.7 Maintenance GuideThis topic describes alarms and performance events relevant to the XPIC feature, and problemsthat occur frequently during the application of the XPIC feature.

OptiX RTN 600 Radio Transmission SystemFeature Description 10 Cross-Polarization Interference Cancellation


10-1

10.1 Feature DescriptionThis topic describes CCDP and XPIC, and the system configuration for XPIC.

10.1.1 CCDP and XPICCCDP and XPIC are two technologies that are developed based on the polarizationcharacteristics of microwave. CCDP doubles the link capacity by transmitting two orthogonalpolarization waves over the same link, and XPIC cancels the cross-polarization interferencebetween the two polarization waves.

Single-polarization transmission and CCDP transmission are two microwave transmissionmethods.

l Single-polarization transmission provides one channel with horizontal or verticalpolarization for transmitting one signal. See Figure 10-1.

l CCDP transmission provides two channel over the same link with orthogonal polarizationsfor transmitting two signals. See Figure 10-2.

Therefore, CCDP transmission doubles the link capacity in single-polarization transmission.

Figure 10-1 Single-polarization transmission

Figure 10-2 CCDP transmission

The ideal situation of CCDP transmission is that no interference exists between the twoorthogonal signals though they are with the same frequency, and thus the receiver can easilyrecover the two signals. In actual engineering conditions, however, despite the orthogonality ofthe two signals, certain interference between the signals inevitably occurs, due to cross-polarization discrimination (XPD) of the antenna and channel degradation. To cancel theinterference, the XPIC technology is adopted. In XPIC technology, the signals are received inthe horizontal and vertical directions. The signals in the two directions are then processed andthe original signals are recovered.

The characteristics of the XPIC function provided by the OptiX RTN 600 are as follows:

l The XPD tolerance is improved by about 20 dB and the notches performance is improved.

10 Cross-Polarization Interference CancellationOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

l The two receivers may not be synchronized, and therefore, they can be integrated in twoNEs respectively. The length of the IF cable between the IDU and ODU may differ and themaximum length difference is 12 meters.

l The XPIC function is realized by hardware.

10.1.2 System ConfigurationAn XPIC system has two configuration modes: single-NE configuration and dual-NEconfiguration.

Single-NE Configuration

When single-NE configuration is applied, the system supports one or two XPIC pairs. The XPICpair is configured as follows:

l Two IFX boards

l Two ODUs

l One dual-polarized antenna

Figure 10-3 shows the typical configuration of the XPIC when a single NE is configured withone XPIC pair. The two IFX boards are connected by an IF jumper for transmitting the XPICcancellation signal to each other.

Figure 10-3 Typical configuration of XPIC (single-NE configuration)

FAN

Slot 20

EXT Slot 7

EXT Slot 5

PXC Slot 3

PXC Slot 1

EXT Slot 8

EXT Slot 6

EXT Slot 4

SCC Slot 2

IFX

IFX

SD1

ODU

ODU

IDU 620

Dual-polarizedantenna

Dual-NE Configuration

When dual-NE configuration is applied, the system supports one to four XPIC pairs. The XPICpair is configured as follows:

l Two IFX boards (respectively installed in the two NEs)



10-3

l Two ODUs (respectively installed in the two NEs)

l One dual-polarized antenna (shared by the two NEs)

Figure 10-4 shows the typical configuration of the XPIC when two NEs are configured withone XPIC pair. The two IFX boards are connected by an XPIC cancellation signal cable fortransmitting the XPIC cancellation signal to each other.

Figure 10-4 Typical configuration of XPIC (dual-NE configuration)

IDU 620

FAN

Slot 20

EXT Slot 7

EXT Slot 5

PXC Slot 3

PXC Slot 1

EXT Slot 8

EXT Slot 6

EXT Slot 4

SCC Slot 2

IFX

SL1

FAN

Slot 20

EXT Slot 7

EXT Slot 5

PXC Slot 3

PXC Slot 1

EXT Slot 8

EXT Slot 6

EXT Slot 4

SCC Slot 2

IFX

SL1


ODU

ODU

IDU 620

XPIC Configuration LimitationsXPIC configuration has the following limitations:

l XPIC supports the STM-1 microwave working mode only.

l Only IDU 620 is applicable.

l The ODU must adopt the separate mount mode, because the dual-polarized antenna is used.

10.2 AvailabilityThe XPIC feature requires support of the involved equipment and boards.


Feature Description


Issue 02 (2008-06-20)

Table 10-1 Availability of the XPIC feature


XPIC IFX (all the versions) IDU 620

10.3 Relation with Other FeaturesThe XPIC feature is related to the 1+1 protection configuration, , and ATPC feature.

Relation with the 1+1 Protection ConfigurationThe two IF boards in an XPIC working group cannot be configured into one 1+1 protectiongroup, but the two IF boards in different XPIC working groups can be configured into one 1+1protection group. Therefore, the four IF boards in two XPIC working groups can form two 1+1protection groups.

Figure 10-5 provides an example of two XPIC groups forming two 1+1 protection groups. Inthis example, the service channels of the IFX boards in slots 5 and 6 form one XPIC group andthe service channels of the IFX boards in slots 7 and 8 form another XPIC group. The servicechannels of the IFX boards in slots 5 and 7 form one 1+1 HSB protection group and the servicechannels of the IFX boards in slots 6 and 8 form another 1+1 HSB protection group. The serviceschannels of the IFX boards in slots 5 and 6 are the main channels of the two 1+1 HSB protectiongroups.

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 theIFX board in slot 7. The fault also causes the loss of the XPIC signals sent by the IFX board inslot 5 to the IFX board in slot 6. As a result, the HSB switching occurs on the IFX board in slot6 and the services are switched to the channels of the IFX board in slot 8. Thus, the services areswitched from one XPIC group to another XPIC group.



10-5

Figure 10-5 Typical XPIC configuration (1+1 protection configuration)

FAN

Slot 20

EXT Slot 7

EXT Slot 5

PXC Slot 3

PXC Slot 1

EXT Slot 8

EXT Slot 6

SD1 Slot 4

SCC Slot 2

IFX

IFX

ODU

ODU

IDU 620


IFX

IFX

Hybridcoupler

ODU

ODU

Hybridcoupler

NOTE

Select balanced hybrid couplers to ensure, to the maximum extent, that the receiver power of the two ODUs thatare in an XPIC group is the same.

Relation with the ATPC FeatureThe transmit power of the two ODUs that are in an XPIC working group should be the same ifpossible. 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 boardsthat are in an XPIC working group.

10.4 Realization PrincipleThe 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.


Feature Description


Issue 02 (2008-06-20)

Figure 10-6 Realization principle of XPIC

Modemhorizontal

Modemvertical

Horizontalpolarization

A/D

A/D

Filter

Verticalpolarization

Crossinterference

Crossinterference Filter

Filter

Filter

Coefficientcontrol

Coefficientcontrol

Decision

Decision

XPIC module of IFX

XPIC module of IFX


1. The transmitter transmits two signals with the same frequency over a horizontal polarizationwave and a vertical polarization wave respectively.

2. Due to XPD of the antenna and channel degradation, cross-polarization interference existsin the signals received by the ODU and also in the IF signals transmitted from the ODU tothe IFX boards.

3. The XPIC module on the IFX board receives the IF signal from the ODU and also the IFsignal from the other IFX board, and processes the IF signals, for example, A/D conversion.

4. The XPIC module on the IFX board controls the coefficient of the feed forward equalizerfilters (FFF) of the two IF signals by using the decision feedback equalizer (DFE). As aresult, after filtering and combination, the interference is cancelled in the two IF signals.

10.5 Planning GuidePlan XPIC parameters according to the situation of microwave links.

Prerequisite

You must have an understanding of the information about microwave links.

Procedure

Plan XPIC parameters.

Follow these four principles when planning XPIC parameters:

l When CCDP is applied to STM-1 microwave links, IFX boards must be installed and theXPIC function must be enabled.

l In the case of the single-NE configuration, an XPIC working group must be configured toensure that the XPIC working group is configured with the same working mode, transmissionfrequency, transmit power, and ATPC attributes. In the case of the dual-NE configuration,ensure that each of the previous parameters is set to the same value for an XPIC workinggroup.



10-7

l When the used ODUs support two T/R spacings, ensure that the two ODUs of an XPICworking group adopt the same T/R spacing.

l In the case of the single-NE configuration, if the 1+1 protection is not required, install IFXboards in slots 5 and 7 (the IFX board in slot 5 processes vertically polarized signals and theIFX board in slot 7 processes horizontally polarized signals) or in slots 6 and 8 (the IFX boardin slot 6 processes vertically polarized signals and the IFX board in slot 8 processeshorizontally polarized signals); if the 1+1 protection is required, install IFX boards in slots5 and 6 (the IFX board in slot 5 processes vertically polarized signals and the IFX board inslot 6 processes horizontally polarized signals) or in slots 7 and 8 (the IFX board in slot 7processes vertically polarized signals and the IFX board in slot 8 processes horizontallypolarized signals). In the case of the dual-NE configuration, install IFX boards in the slotsthat are the closest to each other.

----End

10.6 Creating an XPIC Protection GroupWhen two IFX boards that form an XPIC protection group are installed on an IDU, you cancreate an XPIC protection group to ensure that the XPIC protection group is configured with thesame working mode, transmission frequency, transmit power, and ATPC attributes.

Prerequisitel The IFX boards and the ODUs to which the IFX boards are connected must be created.

l The XPIC Enabled parameter must be set to Enabled (default value) for the IFX boards.


Procedure

Step 1 Select the IFX board from the Object Tree in the NE Explorer. Choose Configuration > LinkConfiguration from the Function Tree.

Step 2 Click the XPIC tab.

Step 3 Click Create.

Step 4 Set the parameters for the XPIC protection group.


Feature Description


Issue 02 (2008-06-20)

Step 5 Click OK.

----End

Parameters


Polarizationdirection-V

IF ports of IFXboards

- l Polarization direction-V andPolarization direction-H indicate the IFports to which polarization direction Vand polarization direction H correspondrespectively.

l It is recommended that you install the twoIFX boards that form an XPIC protectiongroup in the slots that are at the same layeror in the same column. Set the IF port onthe IFX board that has a smaller slotnumber to Polarization direction-V andthe IF port on the other IFX board toPolarization direction-H.

Polarizationdirection-H

Link ID-V 1 to 4094 1 l Link ID-V and Link ID-H indicate thelink IDs to which polarization directionV and polarization direction Hcorrespond respectively.

l A link ID is an identifier of a microwavelink and is used to prevent the microwavelinks between sites from being wronglyconnected.



10-9


Link ID-H l When the link ID received by an NE isdifferent from the link ID set for the NE,the NE reports an MW_LIM alarm andinserts the AIS.

l Set these two parameters according to theplanning information. These twoparameters must be set to differentvalues, but the Link ID-V must be set tothe same value at the two ends of a linkand the Link ID-H must also be set to thesame value at the two ends of a link.

Transmit Power(dBm)

-10.0 to 35.0 -10.0 l The value of this parameter must notexceed the rated power range supportedby the ODU.

l The transmit power of the ODU must beset to the same value at the two ends of amicrowave link.


TransmissionFrequency (MHz)

0 to 4294967.295 0 l The parameter specifies the channelcenter frequency.

l The value of this parameter must not beless than the sum of the lower Txfrequency limit supported by the ODUand a half of the channel spacing, andmust not be greater than the differencebetween the upper Tx frequency limitsupported by the ODU and a half of thechannel spacing.



Feature Description


Issue 02 (2008-06-20)


Transmission Status mute, unmute unmute l When Transmission Status is set tomute, the transmitter of the ODU doesnot work but the ODU can normallyreceive microwave signals.

l When Transmission Status is set tounmute, the ODU normally transmitsand receives microwave signals.

l In normal cases, set this parameter to thedefault value.

ATPC Enabled Enabled, Disabled Disabled l This parameter specifies whether theATPC function is enabled. The ATPCfunction enables the transmit power of atransmitter to automatically trace thechange of the received signal level (RSL)at the receive end within the ATPCcontrol range.

l In the case of areas where fast fading issevere, it is recommended that you setthis parameter to Disabled.

l During commissioning, set thisparameter to Disabled to ensure that thetransmit power is not changed. After thecommissioning, you then re-Set theATPC attributes.

ATPC UpperThreshold (dBm)

-20 to -75 -45 l When the ATPC function is enabled, ifthe RSL at the receive end is higher thanthe preset ATPC upper threshold at thereceive end, the receiver notifies thetransmitter to decrease the transmitpower according to the preset ATPCadjustment step at the transmit end untilthe RSL is lower than the ATPC upperthreshold.

l Generally, ATPC Upper Threshold(dBm) should be 20 dB to 30 dB higherthan ATPC Lower Threshold (dBm),and must not be less than 15 dB. If thedifference between the upper thresholdand the lower threshold is big, the numberof ATPC adjustments is reduced and thesystem load is also reduced. If thedifference between the upper thresholdand the lower threshold is small, thetransmit power is adjusted in a timelymanner and the interference to adjacentsystems is reduced.



10-11


ATPC LowerThreshold (dBm)

-35 to -90 -70 l When the ATPC function is enabled, ifthe RSL at the receive end is lower thanthe preset ATPC lower threshold, thereceiver notifies the transmitter toincrease the transmit power according tothe preset ATPC adjustment step at thetransmit end until the RSL is higher thanthe ATPC lower threshold.

l Generally, set this parameter to a value10 dB or more higher than the receiversensitivity to prevent sudden fast fadingfrom causing that the RSL becomes lowerthan the receiver sensitivity.

ATPC Adjustment(dB)

1 to 5 5 l This parameter specifies the variation inthe transmit power caused by one ATPCadjustment.


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 XPICprotection group. You, however, need to set the T/R spacing used by the ODU in the IF/ODUConfiguration tab if the used ODU supports two T/R spacings.

10.7 Maintenance GuideThis topic describes alarms and performance events relevant to the XPIC feature, and problemsthat occur frequently during the application of the XPIC feature.

10.7.1 Relevant Alarms and EventsWhen XPIC signals are lost, the system reports an alarm.

Relevant Alarmsl XPIC_LOS

The XPIC_LOS alarm indicates that the XPIC compensation signal is lost.

Relevant Abnormal Events

None.


Feature Description


Issue 02 (2008-06-20)

10.7.2 FAQsThis topic lists the problems that occur frequently during the application of the XPIC feature.

Q: What are the common causes of XPIC faults?


l The data is wrongly configured.The two IFX boards that form an XPIC group must be configured with the same workingmode, transmission frequency, and T/R spacing.

l Cables are wrongly connected.The provision of the XPIC feature involves the installation of IF cables, installation of XPICcables, 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 configuredwith 1+1 protection. Divide the cables into two parts according to the polarization directionof signals and then check each part.

l The polarization directions of dual-polarized antennas are not aligned.The XPD can reach the design value of the antennas only when the polarization directionsof dual-polarized antennas are totally aligned.



10-13

11 N+1 Protection

About This Chapter

N+1 protection refers to the protection configuration in which N working channels in amicrowave direction share one protection channel.

11.1 Feature DescriptionThis topic describes the system configuration, protection type, switching condition, andswitching impact of the N+1 protection.

11.2 AvailabilityThe N+1 protection feature requires support of the involved equipment and boards.

11.3 Relation with Other FeaturesThe N+1 protection is related to the 1+1 protection configuration, , and SNCP feature.

11.4 Realization PrincipleThe N+1 protection uses the N+1 protection protocol to realize the switching. The N+1protection protocol is similar to the 1:N linear multiplex section protection protocol.

11.5 Planning GuideWhen the OptiX RTN 600 transmits two or three STM-1 microwave services in the point-to-point mode, you can adopt the N+1 protection configuration.

11.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of the N+1 protection mode. An example is provided as a supplement to the configuration.

11.7 Maintenance GuideThis topic describes how to carry out N+1 protection switching, relevant alarms and events, andproblems that occur frequently during the application of the protection feature.

OptiX RTN 600 Radio Transmission SystemFeature Description 11 N+1 Protection


11-1

11.1 Feature DescriptionThis topic describes the system configuration, protection type, switching condition, andswitching impact of the N+1 protection.

11.1.1 System ConfigurationN+1 protection is available in two configuration modes: 2+1 protection configuration and 3+1protection configuration.

2+1 Protection ConfigurationOne IDU 620 system supports one 2+1 protection group. One 2+1 protection group occupiesthree channels and consists of the following:

l Three IF boards

l Three ODUs

l One dual-polarized antenna (with one hybrid coupler)

NOTE

l The IF board can be the IF1A board, IF1B board, or IFX board. As the XPIC function is not required, it isrecommended that you use the IF1A board or IF1B board.

l The three channels can use the adjacent channel alternate-polarized (ACAP) mode.

l The hybrid coupler can be balanced or unbalanced. Generally, the balanced hybrid coupler is used.

Figure 11-1 provides a typical configuration of one 2+1 protection group. The configuration isas follows:

l The IF1B boards in slots 5 and 7 provide two working channels. The IF1B board in slot 8provides one protection channel.

l The three channels are configured in the ACAP mode. See Figure 11-2.

l The radio receive power of the three channels should be the same if possible to reduceadjacent channel interference. That is, the ODU transmit power set for the two workingchannels should be higher than the ODU transmit power set for the protection channel andthe increment should exactly offset the extra loss caused by the hybrid coupler.

l One SL1 board and one SD1 board access two working services and one extra service.

11 N+1 ProtectionOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

Figure 11-1 Typical configuration of one 2+1 protection group

FAN

Slot 20

EXT Slot 7

EXT Slot 5

PXC Slot 3

PXC Slot 1

EXT Slot 8

SL1 Slot 6

SD1 Slot 4

SCC Slot 2

IF1B

IFIB

ODU

ODU

IDU 620


IF1B

Hybridcoupler ODU

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

V

H

Workingchannel 1

Workingchannel 2

Protectionchannel

3+1 Protection ConfigurationTwo IDU 620 systems support one 3+1 protection group. One 3+1 protection group occupiestwo frequencies and consists of the following:

l Four IF boards (two for each NE)

l Four ODUs (two for each NE)

l Two SD1 boards (one for each NE)

l One dual-polarized antenna (with two balanced hybrid couplers)

NOTE

The IF board can be the IF1A board, IF1B board, or IFX board. As the XPIC function is not required, it isrecommended that you use the IF1A board or IF1B board.

Figure 11-3 provides a typical configuration of one 3+1 protection group. The configuration isas follows:



11-3

l The two IF1B boards of the primary NE provide two working channels. The two IF1Bboards of the secondary NE provide one working channel and one protection channel.

l The four channels are configured in the ACAP mode. See Figure 11-4.l 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 channelsshould be the same.

l The two SD1 boards in slots 6 and 8 of the primary NE access three working services andone extra service. One working service and the extra service are transferred to the secondaryNE through the SD1 board in slot 4.

l The SD1 board in slot 4 of the secondary NE accesses the one working service and theextra service that are transferred from the primary NE.

NOTE

You can use one SL4 board to replace the two SD1 boards in slots 6 and 8 of the primary NE to access theservices, depending on the requirements.

Figure 11-3 Typical configuration of one 3+1 protection group

FAN

Slot 20

EXT Slot 7

EXT Slot 5

PXC Slot 3

PXC Slot 1

SD1 Slot 8

SD1 Slot 6

SD1 Slot 4

SCC Slot 2

IF1B

IF1B

ODU

ODU

Primary NE (IDU 620 )


Hybridcoupler

ODU

ODU

Hybridcoupler

FAN

Slot 20

EXT Slot 7

EXT Slot 5

PXC Slot 3

PXC Slot 1

SD1 Slot 8

SD1 Slot 6

SD1 Slot 4

SCC Slot 2

IF1B

IF1B

Secondary NE (IDU 620 )


Feature Description


Issue 02 (2008-06-20)

Figure 11-4 Typical channel configuration of one 3+1 protection group

V

H

Workingchannel 1

Workingchannel 2

Protectionchannel

Workingchannel 3

Limitations of N+1 ProtectionThe limitations of N+1 protection are as follows:

l N+1 protection supports only the STM-1 radio working mode.

l The IDU must be the IDU 620.

l The ODUs must adopt the separate mounting mode due to the limitations of the dual-polarized antenna.

11.1.2 Protection TypeThe protection type of N+1 protection is similar to the dual-ended revertive switching mode of1: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 directionsare switched to the protection channels.

l When an NE is in the switching state, the NE releases the switching and enables the formerworking channel to return to the working state some time after the former working channelis restored to normal. The period from the time the former working channel is restored tonormal until 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 isrecommended that you set the WTR time to five to twelve minutes.

11.1.3 Switching ConditionN+1 protection can be triggered by local SF conditions, local SD conditions, local externalswitching requests, and byte K sent from the NE on the opposite side. This is similar to linearmultiplex section protection.

Table 11-1 Switching conditions of the N+1 protection


Lockout of protection(external switching)


The lockout of protection blocks normal trafficsignals from entering the protection channel but doesnot block traffic signals from being switched fromthe protection channel to the working channel. Thesignal fail condition in the protection channel isequivalent to the lockout of protection.



11-5



Traffic signals on the working channel are forcedlyswitched to the protection channel.

Signal fail (SF) The SF on the working channel causes traffic signalsto be switched to the protection channel. When thereis 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 isfaulty, the SF switching is triggered.

Signal degrade (SD) The SD on the working channel causes traffic signalsto be switched to the protection channel. When thereis the B2_SD alarm on the working channel, the SDswitching is triggered.




After traffic signals are switched to the protectionchannel due to the SF/SD condition on the workingchannel and the working channel is already restoredto normal for the WTR time, a revertive switchingoccurs. Within the period from the time the formeractive equipment is restored to normal until the timethe revertive switching occurs, the switching is in theWTR state. After the revertive switching, theswitching enters the normal state.

Exercise switching(external switching)

Traffic signals are not actually switched. Theexercise functionality is used only to check whetheran NE can normally carry out the N+1 protectionprotocol.


Feature Description


Issue 02 (2008-06-20)

NOTE

l The SD is an optional switching condition. You can specify whether to use the SD as a switching conditionon the NMS. By default, the SD switching condition is used.

l If two switching conditions exist on a channel at the same time, the switching of higher priority preemptsthe channel.

l External switching commands include the switching clear commands, which are the clear lockout command,clear forced switching command, clear manual switching command, clear exercise switching command,clear WTR state command, and clear all command. The clear WTR state command is used to end the currentWTR state of the NE and to immediately switch services to the working channel. The clear all command isused to clear all switching actions triggered by external switching commands and to clear the WTR state.

l If an NE needs to perform switching according to byte K sent from the NE at the opposite end, the NEdetermines the switching priority according to the bridge request code contained in byte K. For details, see14.1.2 Meaning of Byte K.

11.1.4 Switching ImpactWithin the N+1 protection switching time (shorter than 50 ms), services are interrupted. Extraservices are interrupted within the period from the time normal services are switched to theprotection channel until the time the services are restored to the working channel.

11.2 AvailabilityThe N+1 protection feature requires support of the involved equipment and boards.

Table 11-2 Availability of the N+1 protection feature


N+1 protection IF1A/IF1B (all the versions) IDU 620


11.3 Relation with Other FeaturesThe N+1 protection is related to the 1+1 protection configuration, , and SNCP feature.l The members of an N+1 protection group cannot be configured with 1+1 protection.

l The radio link with N+1 protection configuration can work only as the service sink of anSNCP service pair, and cannot work as the working source or protection source.

11.4 Realization PrincipleThe N+1 protection uses the N+1 protection protocol to realize the switching. The N+1protection protocol is similar to the 1:N linear multiplex section protection protocol.

11.4.1 2+1 Protection ConfigurationIn the case of 2+1 protection configuration, three IF boards form a 2+1 protection group to realizeprotection switching.



11-7

NOTE

The following describes the switching principle of 2+1 protection. The 2+1 protection configuration describedin 11.1.1 System Configuration is provided as an example.

Figure 11-5 Realization principle of 2+1 protection (before the switching)

7-IF1B-1

5-IF1B-1

8-IF1B-1

PXC

6-SL1-1

4-SD1-1

4-SD1-2

17-ODU

15-ODU

18-ODU

Working channel Protection channel

Figure 11-6 Realization principle of 2+1 protection (after the switching)

7-IF1B-1

5-IF1B-1

8-IF1B-1

PXC

6-SL1-1

4-SD1-1

4-SD1-2

17-ODU

15-ODU

18-ODU


In this example, port 1 of the IF1B board in slot 5, port 1 of the IF1B board in slot 7, and port 1of 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 asfollows:

1. Before the switching, the NE sends and receives normal traffic signals on the workingchannel, and sends and receives extra traffic signals on the protection channel.

2. On detecting that the signals on a working channel fail (for example, the IF1B board in slot5 detects that an MW_LOF alarm is generated on port 1), the IF board notifies the SCCboard.

3. The SCC board controls the PXC board to realize the transmission of the working trafficsignals (port 1 of the SD1 board in slot 4) on the protection channel (port 1 of the IF1B


Feature Description


Issue 02 (2008-06-20)

board in slot 8). The SCC board also interacts with the NE on the opposite side throughbyte K to enable the NE on the opposite side to perform synchronous switching.

NOTE

The interaction of byte K between NEs complies with the N+1 protection protocol, which is similar to the MSPprotocol. For details, see Realization Principle of 1:N Linear MSP.

11.4.2 3+1 Protection ConfigurationIn the case of 3+1 protection configuration, the primary NE forms a 3+1 protection group torealize protection switching and the secondary NE forms two STM-1 REGs to realize transparenttransmission of byte K.

NOTE

The following describes the switching principle of 3+1 protection. The 3+1 protection configuration describedin 11.1.1 System Configuration is provided as an example.

Figure 11-7 Realization principle of 3+1 protection (before the switching)

7-IF1B-1

5-IF1B-1

4-SD1-1

PXC

6-SD1-2

6-SD1-1

8-SD1-1

17-ODU

15-ODU


4-SD1-28-SD1-2

7-IF1B-1

5-IF1B-1

PXC

4-SD1-2

4-SD1-1

17-ODU

15-ODU

Primary NE

Secondary NE



11-9

Figure 11-8 Realization principle of 3+1 protection (after the switching)

7-IF1B-1

5-IF1B-1

4-SD1-1

PXC

6-SD1-2

6-SD1-1

8-SD1-1

17-ODU

15-ODU


4-SD1-28-SD1-2

7-IF1B-1

5-IF1B-1

PXC

4-SD1-2

4-SD1-1

17-ODU

15-ODU

Primary NE

Secondary NE

In this example, port 1 of the IF1B board in slot 5 of the primary NE, port 1 of the IF1B boardin slot 7 of the primary NE, and ports 1 and 2 of the SD1 board in slot 4 of the primary NE forma 3+1 protection group. An REG is established between port 1 of the IF1B board in slot 5 of thesecondary NE and port 1 of the SD1 board in slot 4 of the secondary NE. Another REG isestablished between port 1 of the IF1B board in slot 7 of the secondary NE and port 2 of theSD1 board in slot 4 of the secondary NE.

When a working channel fails, the switching principle of the 3+1 protection configuration is asfollows:

1. Before the switching, the primary NE sends and receives normal traffic signals on theworking 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 multiplexsection overheads.

2. On detecting that the signals on a working channel fail (for example, the IF1B board in slot5 detects that an MW_LOF alarm is generated on port 1), an IF board of the secondary NEinserts the MS_AIS alarm and transparently transmits the multiplex section overheads andVC signals to port 1 of the SD1 board in slot 4 of the primary NE through port 1 of the SD1board in slot 4 of the secondary NE.

3. On detecting the MS_AIS alarm, the SD1 board in slot 4 of the primary NE reports thealarm to the SCC board.


Feature Description


Issue 02 (2008-06-20)

4. The SCC board controls the PXC board to realize the transmission of the working trafficsignals (port 1 of the SD1 board in slot 8) on the protection channel (port 2 of the SD1board in slot 4). The SCC board also interacts with the NE on the opposite side throughbyte K to enable the NE on the opposite side to perform synchronous switching. Becausebyte K belongs to the multiplex section overheads, the secondary NE always transparentlytransmits byte K when the primary NE exchanges byte K with the NE on the opposite side.

NOTE

l In this example, the working channels of the secondary NE fail. If the working channels of the primary NEfail, the IF board directly reports the alarm to the SCC board to trigger the protection switching.

l The REG formed by the secondary NE is slightly different from an ordinary REG. The REG formed by thesecondary NE does not insert an AU_AIS alarm but inserts an MS_AIS alarm to trigger N+1 protectionswitching when an MW_LOF alarm or a regenerator section alarm (for example, R_LOS, R_LOC, andR_LOF) is generated.

l The interaction of byte K between NEs complies with the N+1 protection protocol, which is similar to theMSP protocol. For details, see Realization Principle of 1:N Linear MSP.

11.5 Planning GuideWhen the OptiX RTN 600 transmits two or three STM-1 microwave services in the point-to-point 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 in the range from five minutes to twelve minutes. It is

recommended that you set the value to ten minutes.l It is recommended that you use SD as a switching condition.

----End

11.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of the N+1 protection mode. An example is provided as a supplement to the configuration.

11.6.1 Configuration FlowThis topic describes the configuration flow for the N+1 protection mode.



11-11

Figure 11-9 Configuration flow for the N+1 protection mode

Start

Create an N+1protection group

1

Create REGs2

Is the 3+1protection mode

used?

No

End

Yes

Table 11-3 Description of the configuration flow of the N+1 protection mode

Number Description

① l In the case of 3+1 protection, an N+1 protection group needs to be createdonly for the primary NE.

l For the configuration process, see 11.6.2 Creating an N+1 ProtectionGroup.

② l Create REGs between two IF boards of the secondary NE and two ports ofthe SD1 board that is connected to the primary NE.

l For the configuration process, see 11.6.3 Creating REGs.

11.6.2 Creating an N+1 Protection GroupWhen the OptiX RTN 600 transmits two or three STM-1 microwave services in the point-to-point mode, you can adopt the N+1 protection configuration.

Prerequisitel The IF boards and the ODUs to which the IF boards are connected must be created.

l The STM-1 optical/electrical interface boards (only in the case of the primary NE that isto be configured with 3+1 protection) must be created.

l The IF boards must work in the STM-1 mode.



Feature Description


Issue 02 (2008-06-20)

Procedure


Step 2 Click the N+1 Protection tab.

Step 3 Click Create.The system displays the Create a N+1 Protection Group dialog box.

Step 4 Set the attributes of the N+1 protection group.

Step 5 Set the slot mapping relation.1. In Select Mapping direction, select West Working Unit.2. In Select Mapping Mode, select the line port to which a working channel corresponds and

click .3. Repeat Step 5.2 to select the line ports to which other working channels correspond.4. In Select Mapping direction, select West Protection Unit.5. In Select Mapping Mode, select the line port to which the protection channel corresponds

and click .

Step 6 Click OK.

----End



11-13


WTR Time(s) 300 to 720 600 l When the time after the former workingchannel is restored to normal reaches theset wait-to-restore (WTR) time, arevertive switching occurs.


SD enable Enabled, Disabled Enabled l When SD enable is set to Enabled, theB2_SD alarm is considered as aswitching condition.


Slot MappingRelation

- - l In the case of 2+1 protection, map two IFports as West Working Unit and map theremaining IF port as West ProtectionUnit.

l In the case of 3+1 protection, it isrecommended that you map the two IFports and the first line port of the STM-1optical/electrical interface board that isconnected to the secondary NE as WestWorking Unit, and map the other lineport as West Protection Unit.

NOTE

The N+1 protection groups of the equipment at both ends must have the same attributes.

11.6.3 Creating REGsIn the case of 3+1 protection, you need to configure REGs for the secondary NE.

Prerequisitel The IF boards and the ODUs to which the IF boards are connected must be created.

l The STM-1 optical/electrical interface board that is connected to the primary NE must becreated.

l The IF boards must work in the STM-1 mode.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > REGConfiguration from the Function Tree.

Step 2 Click Create.


Feature Description


Issue 02 (2008-06-20)

The system displays the Create REG dialog box.

Step 3 Set the SD Enabled parameter.

Step 4 Set the slot mapping relation.

1. In Slot Mapping Direction, select West Line.

2. In Select Mapping Mode, select the line port to which the west line corresponds and click

.

3. In Slot Mapping Direction, select East Line.

4. In Select Mapping Mode, select the line port to which the east line corresponds and click

.

Step 5 Click OK.

----End

Parameters


SD Enabled Enabled, Disabled Enabled l When this parameter is set to Enabled,the REG inserts an MS-AIS alarm whena B2_SD alarm is generated.



- - It is recommended that you map the IF portas West Line and the port of the STMJ-1optical/electrical interface board as EastLine.



11-15

11.6.4 Configuration ExampleThis topic provides an example to describe how to configure the N+1 protection mode.

PrecautionsNOTE

l For the system configuration of this example, refer to the 3+1 protection configuration example providedin 11.1.1 System Configuration.

l 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 slot7 of the primary NE, and ports 1 and 2 of the SD1 board in slot 4 of the primary NE into a 3+1protection group. For details, see 11.6.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 theSD1 board in slot 4 of the secondary NE, and create another REG between port 1 of the IF1Bboard 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.6.3 Creating REGs.

----End

11.7 Maintenance GuideThis topic describes how to carry out N+1 protection switching, relevant alarms and events, andproblems that occur frequently during the application of the protection feature.

11.7.1 Starting/Stopping the N+1 Protection ProtocolIf you first stop the N+1 protection protocol and then start it, the N+1 protection protocol canbe restored to the initial state.

Prerequisitel The N+1 protection group must be configured.


Precautionsl Stopping the N+1 protection protocol causes failure of N+1 protection.

l When services are switched onto the protection channel, stopping the N+1 protectionprotocol causes the services to switch back to the working channel. At this time, if theworking channel is normal, the services are transiently interrupted; if the working channelis faulty, the services are interrupted until the working channel is restored to normal or theN+1 protection protocol is started.


Feature Description


Issue 02 (2008-06-20)

Procedure



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.7.2 N+1 Protection SwitchingThe N+1 protection switching is an important maintenance operation.

Prerequisitel The N+1 protection group must be configured.


Procedure



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

11.7.3 Relevant Alarms and EventsWhen an N+1 protection switching occurs on IF boards, the system reports corresponding alarmsand abnormal events.

Relevant Alarmsl NP1_SW_INDI

The NP1_SW_INDI alarm indicates the N+1 protection switching.l NP1_SW_FAIL

The NP1_SW_FAIL alarm indicates that the N+1 protection switching fails.l NP1_MANUAL_STOP



11-17

The NP1_MANUAL_STOP alarm indicates that the N+1 protection protocol is manuallystopped.

Relevant Abnormal Eventsl N+1 protection switching

This abnormal event indicates that the N+1 protection switching occurs.

11.7.4 FAQsThis topic lists the problems that occur frequently during the application of N+1 protection.

Q: What switching states does N+1 protection have?

A: N+1 protection has the following switching states:

l Protocol is not startedThe state when the N+1 protection protocol is not started

l Protocol startingThe state when the N+1 protection protocol is starting

l Protocol normalThe normal state after the N+1 protection protocol is started

l LockoutThe state after the protection channel is locked out



l ExerciseThe state after an exercise switching

l Signal failureThe state after an SF switching

l Signal degradeThe state after an SD switching

l WTRThe state that exists from the time the working equipment is restored to normal after anautomatic switching until the time the revertive switching occurs in the revertive mode

Q: Why the forced switching cannot be carried out when the signal on the protectionchannel fails?

A: After the signal on the protection channel fails, the protection channel is locked out. As thelockout of the protection channel has a higher priority than the forced switching, the forcedswitching cannot be carried out.

Q: Why does the creation of an N+1 protection group fail?


Feature Description


Issue 02 (2008-06-20)

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

12 Automatic Transmit Power ControlFunction

About This Chapter

The automatic transmit power control (ATPC) function is an important function of a radiotransmission system. The ATPC function reduces the interference from a transmitter to adjacentsystems and also reduces the residual bit error rate.

12.1 Feature DescriptionThe ATPC function enables the transmit power of a transmitter to automatically trace the changeof the received signal level (RSL) at the receive end within the ATPC control range.

12.2 AvailabilityThe ATPC feature requires support of the involved equipment and boards.

12.3 Relation with Other FeaturesThe transmit power of the two ODUs that are in an XPIC working group should be the same ifpossible. 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 boardsthat are in an XPIC working group.

12.4 Realization PrincipleThe OptiX RTN 600 uses the ATPC overhead in the microwave frame to realize the ATPCfunction.

12.5 Planning GuidePlan ATPC parameters according to the situation of microwave links.

12.6 Configuring the ATPC FunctionTo configure the ATPC function, set the ATPC attributes of the IF board.

12.7 Maintenance GuideThis topic describes alarms and performance events relevant to the ATPC function, and problemsthat occur frequently during the application of the ATPC function.

OptiX RTN 600 Radio Transmission SystemFeature Description 12 Automatic Transmit Power Control Function


12-1

12.1 Feature DescriptionThe ATPC function enables the transmit power of a transmitter to automatically trace the changeof the received signal level (RSL) at the receive end within the ATPC control range.

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 receivernotifies the transmitter to increase the transmit power according to the preset ATPCadjustment step at the transmit end until the RSL is higher than the ATPC lower threshold.

l If the RSL at the receive end is higher than the preset ATPC upper threshold, the receivernotifies the transmitter to decrease the transmit power according to the preset ATPCadjustment 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 Value Range ofthe ATPCAdjustment Step(dB)

ATPC AdjustmentSpeed (dB/s)

Lower Threshold(dBm)

Upper Threshold(dBm)

–6 (SP series ODUseries)Rated minimumtransmit power (HP/SPA/LP ODU series)

Rated maximumtransmit power + 1.5dB (SP ODU series)Rated maximumtransmit power (HP/SPA/LP ODU series)

1 to 5 ≥ 10 (when theadjustment step is setto 1 dB)≥ 20 (when theadjustment step is setto 2 dB)≥ 30 (when theadjustment step is setto a value in the rangefrom 3 dB to 5 dB)

12.2 AvailabilityThe ATPC feature requires support of the involved equipment and boards.

Table 12-2 Availability of the ATPC feature


ATPC – IDU 605

IF1A/IF1B (all the versions) IDU 610/620



12 Automatic Transmit Power Control FunctionOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

12.3 Relation with Other FeaturesThe transmit power of the two ODUs that are in an XPIC working group should be the same ifpossible. 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 boardsthat are in an XPIC working group.

12.4 Realization PrincipleThe OptiX RTN 600 uses the ATPC overhead in the microwave frame to realize the ATPCfunction.

Figure 12-1 ATPC realization principle

Adjust the ODU poweronce according to theATPC adjustment step

Microwave frame (ATPC overheadindicates to adjust the transmit power)

Adjust the ODU poweronce according to theATPC adjustment step

Microwave frame (ATPC overheadindicates to adjust the transmit power)

Microwave frame (ATPC overheadindicates not to adjust the transmit power)

Does not adjust theODU power

……

Transmitter Receiver

RSL within ATPCadjustment range

RSL out of ATPCadjustment range

……

……


1. The receiver detects the RSL.

2. After the ATPC function is enabled, when the RSL is lower than the lower ATPC thresholdor higher than the upper ATPC threshold, the receiver sets the ATPC overhead in themicrowave frame to be sent to the transmitter, to indicate an increase or decrease in thetransmit power.



12-3

NOTE

To prevent continuous adjustment to ODU power at the transmit end from occupying a large number ofresources, the receiver does not set the ATPC overhead in each microwave frame to indicate an increaseor decrease in the transmit power. Instead, the receiver sets the ATPC overhead every several microwaveframes.

3. The transmitter detects the ATPC overhead in the received microwave frame.

4. When the transmitter detects that the ATPC overhead in a microwave frame indicates anincrease or decrease in the transmit power, the transmitter increases or decreases thetransmit power of the ODU according to the preset ATPC adjustment step.

5. When the receiver detects that the RSL is within the ATPC adjustment range, the receiversets the ATPC overhead in the microwave frame again to make the ATPC overhead indicatenot to adjust the transmit power.

6. When the transmitter does not detect the ATPC overhead that indicates an increase ordecrease in the transmit power, the transmitter does not change the transmit power of theODU.

12.5 Planning GuidePlan ATPC parameters according to the situation of microwave links.

Prerequisite

You must have an understanding of the information about microwave links.

Procedure

Plan ATPC parameters.

Follow these five principles when planning ATPC parameters:

l Set ATPC parameters consistent at the two sides of a hop of microwave link.

l It is recommended that you disable the ATPC function for areas where fast fading is severe.

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

l Generally, the ATPC upper threshold should be 20 dB to 30 dB higher than the ATPC lowerthreshold, and must not be less than 15 dB. If the difference between the upper threshold andthe lower threshold is big, the number of ATPC adjustments can be reduced and the systemload also can be reduced. If the difference between the upper threshold and the lowerthreshold is small, the transmit power can be adjusted in a timely manner and the interferenceto adjacent systems can be reduced.

l It is recommended that you set the ATPC adjustment step to 5 dB.

----End

12.6 Configuring the ATPC FunctionTo configure the ATPC function, set the ATPC attributes of the IF board.


Feature Description


Issue 02 (2008-06-20)

Prerequisitel The related IF board must be added.


Precautionsl In the case of the IF boards that are configured with 1+1 protection, set only the ATPC

attributes of the main IF board.

l The following procedure describes the configuration of ATPC parameters in the IF interfaceconfiguration dialog box of the IF board. You can also set ATPC parameters in the followingconfiguration dialog boxes:

– 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 > IFInterface from the Function Tree.

Step 2 Click the ATPC Attributes tab.

Step 3 Set the ATPC attributes.

NOTE

Step 4 Click Apply.

----End

Parameters


ATPC Enable Status Enabled, Disabled Disabled l This parameter specifies whether theATPC function is enabled. The ATPCfunction enables the transmit power of atransmitter to automatically trace thechange of the received signal level (RSL)at the receive end within the ATPCcontrol range.

l In the case of areas where fast fading issevere, it is recommended that you setthis parameter to Disabled.



12-5


ATPC UpperThreshold (dBm)

-20 to -75 -45 l When the ATPC function is enabled, ifthe RSL at the receive end is higher thanthe preset ATPC upper threshold at thereceive end, the receiver notifies thetransmitter to decrease the transmitpower according to the preset ATPCadjustment step at the transmit end untilthe RSL is lower than the ATPC upperthreshold.

l Generally, ATPC Upper Threshold(dBm) should be 20 dB to 30 dB higherthan ATPC Lower Threshold (dBm),and must not be less than 15 dB. If thedifference between the upper thresholdand the lower threshold is big, the numberof ATPC adjustments is reduced and thesystem load is also reduced. If thedifference between the upper thresholdand the lower threshold is small, thetransmit power is adjusted in a timelymanner and the interference to adjacentsystems is reduced.

ATPC LowerThreshold (dBm)

-35 to -90 -70 l When the ATPC function is enabled, ifthe RSL at the receive end is lower thanthe preset ATPC lower threshold, thereceiver notifies the transmitter toincrease the transmit power according tothe preset ATPC adjustment step at thetransmit end until the RSL is higher thanthe ATPC lower threshold.

l Generally, set this parameter to a value10 dB or more higher than the receiversensitivity to prevent sudden fast fadingfrom causing that the RSL becomes lowerthan the receiver sensitivity.

ATPC Adjustment(dB)

1 to 5 5 l This parameter specifies the variation inthe transmit power caused by one ATPCadjustment.


NOTE

l Each of the ATPC parameters must be set to the same value at the two ends of a microwave link.

l During commissioning, set ATPC Enable Status to Disabled to ensure that the transmit power is notchanged. After the commissioning, you then re-set the ATPC attributes.


Feature Description


Issue 02 (2008-06-20)

12.7 Maintenance GuideThis topic describes alarms and performance events relevant to the ATPC function, and problemsthat occur frequently during the application of the ATPC function.

12.7.1 Relevant Alarms and EventsThere is no alarm or event relevant to the ATPC function.

12.7.2 FAQsThis 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 ATPCthreshold range?

A: Possible causes are as follows:

l The ATPC function is in 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 betweenATPC adjustments (the break time is about five minutes). Hence, the RSL may be out ofthe ATPC threshold range during the break time. The RSL falls within the ATPC thresholdrange after the break time.

l The ATPC adjustment speed is lower than the instantaneous fading speed.This ATPC adjustment speed may be lower than the instantaneous speed of certain fadings.In this case, the transmit power adjusted by the ATPC function fails to offset the fading ina timely manner, and hence, the RSL is out of the ATPC threshold range.

l The transmit power reaches the threshold of the ATPC control range, and cannot beincreased or decreased.



12-7

13 Sub-Network Connection Protection

About This Chapter

The sub-network connection protection (SNCP) scheme protects the services that are acrosssubnets. 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 supportsa maximum of 210 SNCP groups.

13.1 Feature DescriptionThis topic describes the protection type, service pair, switching condition, and switching impactof SNCP.

13.2 AvailabilityThe SNCP solution requires support of the involved equipment and boards.

13.3 Relation with Other FeaturesSNCP has different relationships with different protection features.

13.4 Realization PrincipleSNCP is realized based on the dual fed and selective receiving mechanism.

13.5 Planning GuideFor a ring network (except service-distributed STM-4 or higher-rate ring networks) or a ringwith chain network that is comprised of the OptiX RTN 600, it is recommended that you adoptSNCP as the protection scheme. When planning SNCP, first plan the trails of the working SNCand the protection SNC, and then plan the parameters.

13.6 Configuration GuideThis topic describes the configuration tasks related to SNCP services.

13.7 Maintenance GuideThis topic describes how to carry out an SNCP switching, relevant alarms and events, andproblems that occur frequently during the application of the protection feature.

OptiX RTN 600 Radio Transmission SystemFeature Description 13 Sub-Network Connection Protection


13-1

13.1 Feature DescriptionThis topic describes the protection type, service pair, switching condition, and switching impactof SNCP.

13.1.1 Protection TypeSNCP is classified into the revertive mode and the non-revertive mode.

l Revertive mode



When an NE is in the switching state, the NE keeps the state of the former working channelunchanged even though it is restored to normal, unless another switching occurs.

13.1.2 SNCP Service PairAn SNCP service pair is a basic unit of SNCP. It consists of a working source, a protectionsource, and a service sink.

Figure 13-1 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 radiolink, and can be of different line types. The service sink can be of any line or tributary type.

13.1.3 Switching ConditionThe switching priority varies according to the switching condition.

Table 13-1 Switching conditions of SNCP



From topdownwards, thepriority isfrom the


13 Sub-Network Connection ProtectionOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)



highest tothe lowest.



If a switching is in the lockout state, no forcedswitching occurs. Otherwise, the system switchesservices from the working SNC to the protectionSNC or from the protection SNC to the working SNCaccording to the command. The switching thenenters the forced switching state.

Signal failure If a switching is in the lockout or forced switchingstate, or if the signal of the protection SNC fails, noswitching occurs. Otherwise, the system switchesservices from the working SNC to the protectionSNC. The switching then enters the automaticswitching state. For the trigger conditions of theautomatic switching, see Table 13-2 and Table13-3.


If a switching is in the lockout or forced switchingstate, or if the signal of the protection SNC fails, noswitching occurs. Otherwise, the system switchesservices from the working SNC to the protectionSNC or from the protection SNC to the working SNCaccording to the command. The switching thenenters the manual switching state.


When the switching is in the automatic state and theworking SNC is already restored to normal for theWTR time, a revertive switching occurs. Within theperiod from the time the working SNC is restored tonormal until the time the revertive switching occurs,the switching is in the WTR state. After the revertiveswitching, the switching enters the normal state.

Table 13-2 Trigger conditions of the automatic SNCP switching (VC-4 services)


The hardware of the line board is faulty. Default condition

R_LOS Default condition

R_LOF Default condition

R_LOC Default condition



13-3


MS_AIS Default condition

B2_EXC Default condition

AU_LOP Default condition

AU_AIS Default condition

HP_LOM Default condition

MW_LOF Default condition (only if the IF board worksas a line board)

MW_LIM Default condition (only if the IF board worksas a line board)

B3_EXC Optional condition

B3_SD Optional condition

HP_TIM Optional condition

HP_UNEQ Optional condition

NOTE

The optional conditions in the above table can be the trigger condition of the automatic SNCP switching at theVC-4 level only after you set automatic switching conditions on the NMS. For the setting method, see 13.6.2Setting the Automatic Switching Conditions of SNCP Services. By default, the optional conditions do notwork as a switching condition.

Table 13-3 Trigger conditions of the automatic SNCP switching (VC-3/VC-12 services)


The hardware of the line board is faulty. Default condition

R_LOS Default condition

R_LOF Default condition

R_LOC Default condition

MS_AIS Default condition

B2_EXC Default condition

AU_LOP Default condition

AU_AIS Default condition

HP_LOM Default condition

MW_LOF Default condition (only if the IF board worksas a line board)


Feature Description


Issue 02 (2008-06-20)


MW_LIM Default condition (only if the IF board worksas a line board)

TU_AIS Default condition

TU_LOP Default condition

13.1.4 Switching ImpactWithin the SNCP switching time (shorter than 50 ms), services are interrupted.

13.2 AvailabilityThe SNCP solution requires support of the involved equipment and boards.

Table 13-4 Availability of the SNCP solution


SNCP IF1A/IF1B (all the versions) IDU 610/620

SL1/SD1 (all the versions)

SLE/SDE (all the versions)

IFX (all the versions) IDU 620

SL4 (all the versions)

13.3 Relation with Other FeaturesSNCP has different relationships with different protection features.

l The MSP line can work only as the service sink of an SNCP service pair and cannot workas the working source or protection source.

l The radio link with 1+1 protection configuration can work only as the service sink of anSNCP service pair, and cannot work as the working source or protection source.

l The radio link with N+1 protection configuration can work only as the service sink of anSNCP service pair, and cannot work as the working source or protection source.

l The radio link with XPIC configuration can work only as the service sink of an SNCPservice pair, and cannot work as the working source or protection source.

13.4 Realization PrincipleSNCP is realized based on the dual fed and selective receiving mechanism.



13-5

NOTE

The following describes the switching principle of SNCP. The switching triggered by the signal failure of theworking SNC is provided as an example.

Figure 13-2 SNCP realization principle (before the switching)

Working SNC

Protection SNC

Trail source

NE A NE B

Trail sink

Figure 13-3 SNCP realization principle (after the switching)

Working SNC

Protection SNC

Trail source

NE A NE B

Trail sink

When the working SNC fails, the SNCP switching principle is as follows:

1. Before the switching, the trail source of the SNC (NE A) sends normal service signals tothe trail sink (NE B) through both the working SNC and the protection SNC.

2. On detecting that the signal of the working SNC fails, the line board of NE B reports theevent to the SCC board.

3. After confirming that the signal of the working SNC fails and that the signal of theprotection SNC is normal, the SCC board of NE B enables the cross-connect board tocomplete the cross-connection between the protection SNC and the service sink.

13.5 Planning GuideFor a ring network (except service-distributed STM-4 or higher-rate ring networks) or a ringwith chain network that is comprised of the OptiX RTN 600, it is recommended that you adoptSNCP as the protection scheme. When planning SNCP, first plan the trails of the working SNCand the protection SNC, and then plan the parameters.


Feature Description


Issue 02 (2008-06-20)

Procedure

Step 1 Plan the trails of the working SNC and the protection SNC.

Follow these two principles when planning the trails:

l Do not overlap the working SNC and the protection SNC if possible.

l The OptiX RTN 600 does not support the line with the MSP, 1+1 protection configurationor N+1 protection configuration as the working source or protection source of SNCP.

Step 2 Plan the parameters relevant to the protection configuration.

l It is recommended that the working SNC uses the line ports of one line board and theprotection SNC uses those of another line board to prevent the situation in which failure ofa line board causes the protection to fail.


----End

13.6 Configuration GuideThis topic describes the configuration tasks related to SNCP services.

13.6.1 Creating Cross-Connections for SNCP ServicesThe cross-connection of SNCP services is a cross-connection that a working source and aprotection source correspond to a service sink.

Prerequisitel The boards where the source and the sink are must be configured.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-Connection Configuration from the Function Tree.

Step 2 Optional: Click Cross-Connection Configuration to change the VC12 timeslot numberingscheme used by the cross-connection.

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



13-7

NOTE

Step 5 Click OK.

NOTE

l When you create a cross-connection whose source or sink is the timeslots of an IF board, the creation mayfail due to the limited number of licenses.

l By default, each NE has a license for 7xE1. A license document is required if you want to create many cross-connections for the timeslots in IF boards.

l The calculation of the required number of licenses is based on the total number of the service timeslots ofall the IF boards that are involved in cross-connections. In the case of the cross-connections of VC-3 orVC-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 numberof licenses that are used for 21xE1. One VC-3 pass-through service between two IF boards requires thenumber of licenses that are used for 42xE1. The 8xE1 SNCP services from two IF boards to one PO1 boardrequire the number of licenses that are used for 16xE1.

----End


Service Type SNCP SNCP -


Feature Description


Issue 02 (2008-06-20)


Level VC12, VC3, VC4 VC12 l This parameter specifies the level of thecross-connection to be created.

l If the service is an E1 service or a dataservice that is bound with VC-12 paths,set this parameter to VC12.

l If the service is an E3/T3 service or a dataservice that is bound with VC-3 paths, setthis parameter to VC3.

l If all the services in a VC-4 pass throughthe NE, set this parameter to VC4.

Revertive Mode Non-Revertive,Revertive




Direction Unidirectional,Bidirectional

Unidirectional l When this parameter is set toUnidirectional, only the cross-connections in the SNCP receivedirection are created.

l When this parameter is set toBidirectional, both the cross-connections in the SNCP receivedirection and the cross-connections in theSNCP transmit direction are created.

l It is recommended that you set thisparameter to Bidirectional.

Hold-off Time(100ms)

0 to 100 0 l When a line fault occurs, an NE canperform SNCP switching after a delay oftime to prevent the situation where theNE performs SNCP switching and otherprotection switching at the same time.This parameter specifies the duration ofthe delay.

l It is recommended that you use thedefault value because the SNCP cannotco-exist with other protection switchingmodes in the OptiX RTN 600.



13-9





Source Port - - This parameter specifies the port where theservice source exists.

Source VC4 - - This parameter specifies the number of theVC-4 where the service source exists.

Source TimeslotRange(e.g.1,3-6)

- - l This parameter specifies the timeslotrange to which the service sourcecorresponds.

l You can set this parameter to a number orseveral numbers. When you set thisparameter to several numbers, use "," toseparate these discrete values and use "-"to indicate continuous numbers. Forexample, "1, 3-6" indicates numbers 1, 3,4, 5, and 6.

l In the case of an IF board that works inthe PDH mode, the first to nth E1s/E3stransmitted by microwaves correspond tothe first to nth VC-12/VC-3 timeslotsrespectively. Similarly, the first to nthports of an E1 interface board or an E3/T3 interface board correspond to the firstto nth VC-12/VC-3 timeslotsrespectively.

Sink Port - - This parameter specifies the port where theservice sink exists.

Sink VC4 - - This parameter specifies the number of theVC-4 where the service sink exists.


Feature Description


Issue 02 (2008-06-20)


Sink TimeslotRange(e.g.1,3-6)

- - l This parameter specifies the timeslotrange to which the service sinkcorresponds.

l You can set this parameter to a number orseveral numbers. When you set thisparameter to several numbers, use "," toseparate these discrete values and use "-"to indicate continuous numbers. Forexample, "1, 3-6" indicates numbers 1, 3,4, 5, and 6.


PostrequisiteIf Direction is set to Unidirectional, the cross-connection only in the SNCP receive directionis created. Hence, you need to configure a unidirectional cross-connection between the serviceand the working trail, and a unidirectional cross-connection between the service and theprotection trail later.

13.6.2 Setting the Automatic Switching Conditions of SNCPServices

In the case of the SNCP services at the VC-4 level, you can setting the automatic switchingconditions.

Prerequisitel 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 ServiceControl from the Function Tree.

Step 2 Select the SNCP protection group. Double-click Initiation Condition to which the workingservice corresponds.The system displays the Initiation Condition dialog box.



13-11

Step 3 Select SD switching conditions. Then, click OK.

Step 4 Select the SNCP protection group. Double-click Initiation Condition to which the protectionservice 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


HPUNEQ Selected, Notselected

Not selected l When this item is selected, the SNCPservice considers the HP_UNEQ alarm asan SD switching condition.


HPTIM Selected, Notselected

Not selected l When this item is selected, the SNCPservice considers the HP_TIM alarm asan SD switching condition.


B3SD Selected, Notselected

Not selected l When this item is selected, the SNCPservice considers the B3_SD alarm as anSD switching condition.


B3EXC Selected, Notselected

Not selected l When this item is selected, the SNCPservice considers the B3_EXC alarm asan SD switching condition.


NOTE

It is recommended that you set Initiation Condition of the working service to be the same as InitiationCondition of the protection service.


Feature Description


Issue 02 (2008-06-20)

13.6.3 Converting Normal Services to SNCP ServicesAfter converting normal services to SNCP services, you can convert the unidirectional cross-connection of normal services to the unidirectional cross-connection in the receive direction ofSNCP services.

Prerequisitel The unidirectional cross-connection of normal services must be configured and the source

of the cross-connection must be a line board.l The user must have the system level authority.

Procedure


Step 2 In the Cross-Connection Configuration tab, select the cross-connection of normal services andclick To SNCP.The system displays the Convert to SNCP Service dialog box.

Step 3 Set the attributes of the SNCP protection group and the slot mapping relation of the SNCPservice.

Step 4 Click OK.

----End



13-13


Revertive Mode Non-Revertive,Revertive




Hold-off Time(100ms)

0 to 100 0 l When a line fault occurs, an NE canperform SNCP switching after a delay oftime to prevent the situation where theNE performs SNCP switching and otherprotection switching at the same time.This parameter specifies the duration ofthe delay.

l It is recommended that you use thedefault value because the SNCP cannotco-exist with other protection switchingmodes in the OptiX RTN 600.




Source Port - - This parameter specifies the port where theservice source exists.

Source VC4 - - This parameter specifies the number of theVC-4 where the service source exists.


Feature Description


Issue 02 (2008-06-20)


Source TimeslotRange(e.g.1,3-6)

- - l This parameter specifies the timeslotrange to which the service sourcecorresponds.

l You can set this parameter to a number orseveral numbers. When you set thisparameter to several numbers, use "," toseparate these discrete values and use "–"to indicate continuous numbers. Forexample, "1, 3–6" indicates numbers 1, 3,4, 5, and 6.


Sink Port - - This parameter specifies the port where theservice sink exists.

Sink VC4 - - This parameter specifies the number of theVC-4 where the service sink exists.

Sink TimeslotRange(e.g.1,3-6)

- - l This parameter specifies the timeslotrange to which the service sinkcorresponds.

l You can set this parameter to a number orseveral numbers. When you set thisparameter to several numbers, use "," toseparate these discrete values and use "–"to indicate continuous numbers. Forexample, "1, 3–6" indicates numbers 1, 3,4, 5, and 6.


PostrequisiteThe 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



13-15

trail, and a unidirectional cross-connection between the service and the protection trail. Thenormal service can be converted into the SNCP service both in the receive direction and thetransmit direction only after the configuration.

13.6.4 Converting SNCP Services to Normal ServicesAfter converting SNCP services to normal services, you can convert the SNCP cross-connectionin the receive direction to the unidirectional cross-connection of normal services.

Prerequisitel The SNCP cross-connection in the receive direction must be configured.


Procedure


Step 2 In the Auto-Created Cross-Connection pane, select the cross-connection and click ToNormal.

Step 3 Choose Working or Protection from the displayed menu.

l To convert the cross-connection to a cross-connection between the working source and theservice sink, choose Working.

l To convert the cross-connection to a cross-connection between the protection source andthe service sink, choose Protection.

----End

Postrequisite

You need to delete the unidirectional cross-connection between the service and the working trailor the unidirectional cross-connection between the service and the protection trail. The SNCPservice can be converted into the normal service both in the receive direction and the transmitdirection only after the deletion.

13.7 Maintenance GuideThis topic describes how to carry out an SNCP switching, relevant alarms and events, andproblems that occur frequently during the application of the protection feature.

13.7.1 SNCP SwitchingThe SNCP switching is an important maintenance operation.

Prerequisitel The SNCP protection group must be configured.



Feature Description


Issue 02 (2008-06-20)

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP ServiceControl from the Function Tree.

Step 2 Select the SNCP protection group. Right-click on the selected group and select the requiredswitching mode mode.The system then displays a prompt dialog box.

Step 3 Click Yes.

Step 4 Click Query.

----End

13.7.2 Relevant Alarms and EventsWhen an SNCP switching occurs, the system reports corresponding alarms and abnormal events.

Relevant Alarmsl PS

The PS alarm indicates that a protection switching occurs.

NOTE

The PS alarm is reported Only when the SNCP service sink is at the tributary board (PO1/PH1/PD1).

Relevant Abnormal Eventsl SDH SNCP protection switching

This abnormal event indicates that an SNCP switching occurs.

13.7.3 FAQsThis 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 NormalThe state when both the working SNC and the protection SNC are normal

l AutomaticThe state after an automatic switching triggered by the signal failure of the working SNC




l WTR



13-17

The state that exists from the time the working SNC is restored to normal until the time therevertive switching occurs in the revertive mode

Q: What are the differences between a two-fiber bidirectional MSP ring and an SNCPring?

A:

Item Two-Fiber BidirectionalMSP Ring

SNCP Ring

Protected object A line Services between subnets

Protection level Multiplex section level VC-4 level, VC-3 level, orVC-12 level

Protection mechanism Shared protection Dedicated protection

Line rate STM-4 or an STM mode witha higher rate

PDH microwave, STM-1, oran STM mode with a higherrate

Switching mode Ring switching Single-ended switching

Bridging/Switching point The head end/tail endautomatically performsbridging and switchingaccording to the APSprotocol. Generally, the headend/tail end is both thebridging node and switchingnode.

The transmit end ispermanently bridged and thereceive end is automaticallyswitched.

Reliability Relatively low Relatively high

Maximum capacity STM-N x n/2 (n representsthe number of the nodes on aring)

STM-N

Number of the nodes on aring network

16 (at most) No restriction

Application Scenario A ring network whereservices are distributedamong NEs

A ring network whereservices are centralized on acentral NE


Feature Description


Issue 02 (2008-06-20)

14 Linear Multiplex Section Protection

About This Chapter

The linear MSP is applicable to point-to-point physical networks. Linear MSP providesprotection 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 acombination of three linear MSP groups for the optical/electrical line and one STM-4 linearMSP group.

14.1 Feature DescriptionThis topic describes the protection type, meaning of byte K in the switching protocol, switchingcondition, and switching impact of linear MSP.

14.2 AvailabilityThe linear MSP solution requires support of the involved equipment and boards.

14.3 Relation with Other FeaturesLinear MSP has different relationships with different protection features.

14.4 Realization PrincipleThe 1+1 protection and 1:N protection have different switching principles.

14.5 Planning GuideIf the OptiX RTN 600 adopts the chain network that is formed through optical fibers or STM-1ecables, it is recommended that you adopt linear MSP as the protection scheme. When planninglinear MSP, first plan the linear MSP mode, and then plan the parameters.

14.6 Creating Linear MSPTo protect the services carried by the optical fibers or STM-1e cables between two nodes,configure linear MSP.

14.7 Maintenance GuideThis topic describes how to start and stop linear MSP, and how to carry out a linear MSPswitching. It also describes relevant alarms and events, and problems that occur frequently duringthe application of the protection feature.

OptiX RTN 600 Radio Transmission SystemFeature Description 14 Linear Multiplex Section Protection


14-1

14.1 Feature DescriptionThis topic describes the protection type, meaning of byte K in the switching protocol, switchingcondition, and switching impact of linear MSP.

14.1.1 Protection TypeLinear MSP can be classified in terms of the protection mechanism, switching mode, andrevertive mode.

In terms of the protection mechanism, linear MSP is classified into the dedicated protection andthe shared protection.

l Dedicated protectionDedicated protection refers to the case that one working channel exclusively uses oneprotection channel. The dedicated protection channel cannot carry extra services. The 1+1protection is the dedicated protection.

l Shared protectionShared protection refers to the case that one or more working channels share one protectionchannel. The shared protection channel can carry extra services. The 1:N (including the1:1) protection is the shared protection.

In terms of the switching mode, linear MSP is classified into the single-ended switching and thedual-ended switching.

l Single-ended switchingIn the single-ended switching mode, the switching occurs only at one end and the state ofthe other end remains unchanged.

l Dual-ended switchingIn the dual-ended switching mode, the switching occurs at both ends at the same time.

In terms of the revertive mode, linear MSP is classified into the revertive mode and the non-revertive mode.

l Revertive modeWhen an NE is in the switching state, the NE releases the switching and enables the formerworking channel to return to the working state some time after the former working channelis restored to normal. The period from the time the former working channel is restored tonormal until 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 isrecommended that you set the WTR time to five to twelve minutes.

l Non-revertive modeWhen an NE is in the switching state, the NE keeps the state of the former working channelunchanged even though it is restored to normal unless another switching occurs.

Hence, linear MSP is classified into the following eight modes:

l 1+1 dual-ended revertive mode

l 1+1 dual-ended non-revertive mode

l 1+1 single-ended revertive mode

14 Linear Multiplex Section ProtectionOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

l 1+1 single-ended non-revertive mode

l 1:N dual-ended revertive mode

l 1:N dual-ended non-revertive mode

l 1:N single-ended revertive mode

l 1:N single-ended non-revertive mode

The OptiX RTN 600 supports the following five linear MSP modes:

l 1+1 dual-ended revertive mode

l 1+1 dual-ended non-revertive mode

l 1+1 single-ended revertive mode

l 1+1 single-ended non-revertive mode

l 1:N (N≤3) dual-ended revertive mode

The 1:N dual-ended revertive mode is switched according to the MSP protocol of linear MSPdescribed in ITU-T G.841. The 1+1 dual-ended mode uses the protocol that is compatible withthe 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 protocolis much maturer and the restructure protocol is in better compliance with the standards.

14.1.2 Meaning of Byte KThe MSP protocol uses bytes K1 and K2 in the multiplex section overhead to transfer switchingrequests.

Table 14-1 Meaning of byte K (linear MSP)

Byte K Meaning

K1 (bit 1 to bit 4) It carries the bridge request code, whosemeaning is provided in Table 14-2.

K1 (bit 5 to bit 8) It carries the number of the traffic signal towhich the bridge request corresponds. 0represents the null signal, 1–14 representnormal traffic signals, and 15 represents theextra traffic signal (only in the case of 1:N).

K2 (bit 1 to bit 4) It carries the number of the traffic signal thatbridges the local end and the channel. It hasthe same value range as K1 (bit 5 to bit 8).

K2 (bit 5) It carries the protection mode. 1 represents the1:N mode. 0 represents the 1+1 mode.

K2 (bit 6 to bit 8) It carries the status. 000 represents the idlestate, 111 represents the MS-AIS state, and110 represents the MS-RDI state.



14-3

NOTE

l For the 1:N mode, the OptiX RTN 600 supports only the 1:N (N≤3) mode.

l In certain area applications, when no MS-RDI or MS-AIS is generated, K2 (bit 6 to bit 8) is used to indicatethe switching mode (100 indicating the single-ended mode and 101 indicating the dual-ended mode). ITU-T G.841 provides no explicit requirements for the usage. By default, the OptiX RTN 600 does not supportthe function but you can make a modification by setting the function.

Table 14-2 Bridge request code (linear MSP)

Bit 1 Bit 2 Bit 3 Bit 4 Meaning

1 1 1 1 Lockout of protection

1 1 1 0 Forced switching

1 1 0 1 Signal fail high priority

1 1 0 0 Signal fail low priority

1 0 1 1 Signal degrade high priority

1 0 1 0 Signal degrade low priority

1 0 0 1 Unused

1 0 0 0 Manual switching

0 1 1 1 Unused

0 1 1 0 WTR

0 1 0 1 Unused

0 1 0 0 Exercise

0 0 1 1 Unused

0 0 1 0 Reverse request

0 0 0 1 Do not revert

0 0 0 0 No request

NOTE

l Reverse Request assumes the priority of the bridge request to which it is responding.

l 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 third-party equipment, the OptiX RTN 600 canuse 1100 (signal fail low priority) and 1010 (signal degrade low priority) as the SF/SD switching requestafter you make settings on the NMS.

14.1.3 Switching ConditionLinear MSP can be triggered by local SF conditions, local SD conditions, and local externalswitching requests. In the dual-ended mode, the local NE can perform switching according tobyte K from the NE at the opposite end.


Feature Description


Issue 02 (2008-06-20)

Table 14-3 Linear MSP switching conditions







Signal fail (SF) The SF on the working channel causes traffic signalsto be switched to the protection channel. When thereis the R_LOC, R_LOF, R_LOS, MS_AIS, orB2_EXC alarm on the working channel, the SFswitching is triggered.







Traffic signals are not actually switched. Theexercise functionality is used only to check whetheran NE can normally carry out the MSP protocol.



14-5

NOTE




l If an NE needs to perform switching according to byte K from the NE at the opposite end, the NE determinesthe switching priority according to the bridge request code contained in byte K. For the meaning of byte K,see 14.1.2 Meaning of Byte K.

14.1.4 Switching ImpactWithin the linear MSP switching time (shorter than 50 ms), services are interrupted. For the 1:1linear MSP, extra services are interrupted within the period from the time normal services areswitched to the protection channel until the time the services are restored to the working channel.

14.2 AvailabilityThe linear MSP solution requires support of the involved equipment and boards.

Table 14-4 Availability of the linear MSP solution


Linear MSP SL4 (all the versions) IDU 620

SL1/SD1 (all the versions) IDU 610/620

SLE/SDE (all the versions)

14.3 Relation with Other FeaturesLinear MSP has different relationships with different protection features.l The line that is configured with linear MSP can work only as the sink of an SNCP service

pair, and cannot work as the working source or protection source.l The line that is configured with linear MSP cannot be configured to form an MSP ring.

14.4 Realization PrincipleThe 1+1 protection and 1:N protection have different switching principles.

14.4.1 1+1 Linear MSPThe 1+1 linear MSP adopts the dual fed and selective receiving mechanism to realize theswitching.


Feature Description


Issue 02 (2008-06-20)

NOTE

The following describes the switching principle of the 1+1 linear MSP. The switching triggered by the signalfailure on the working channel is provided as an example.

Figure 14-1 Realization principle of 1+1 linear MSP (before the switching)

Working

Protection

Working

Protection

NE B NE A

Normal service

Figure 14-2 Realization principle of 1+1 linear MSP (after the switching, in the single-endedmode)

Working

Protection

Working

Protection

NE B NE A

Normal service

Figure 14-3 Realization principle of 1+1 linear MSP (after the switching, in the dual-endedmode)

Working

Protection

Working

Protection

NE B NE A

Normal service



14-7

When the signal on the working channel fails, the switching principle in the single-ended modeis as follows:

1. Before the switching, the source sends traffic signals to both the working channel and theprotection channel. The sink selects the traffic signals from the working channel.

2. On detecting that the signal on the working channel fails, the line board at the sink in acertain direction (NE A) reports the event to the SCC board.

3. After confirming that the signal on the working channel fails and that the signal on theprotection channel is normal, the SCC board enables the cross-connect board to completethe 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 modeis as follows:

1. Before the switching, the source sends traffic signals to both the working channel and theprotection channel. The sink selects the traffic signals from the working channel.

2. On detecting that the signal on the working channel fails, the sink in a certain direction (NEA) sends byte K to the source (NE B) on the protection channel (the request type is "signalfail").

3. NE B sends byte K to NE A also on the protection channel (the request type is "reverserequest").

4. NE A receives the traffic signals from the protection channel.5. NE B also receives the traffic signals from the protection channel.

14.4.2 1:N Linear MSPThe 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 triggeredby the signal failure on the working channel is provided as an example.

Figure 14-4 Realization principle of 1:1 linear MSP (before the switching)

Working

Protection

NE B NE A

Working

Protection

Normal service Extra service


Feature Description


Issue 02 (2008-06-20)

Figure 14-5 Realization principle of 1:1 linear MSP (after the switching)

Working

Protection

NE B NE A

Working

Protection

Normal service Extra service

When the signal on the working channel fails, the switching principle in the 1:1 mode is asfollows:

1. Before the switching, both the source and the sink send and receive normal traffic signalson the working channel, and send and receive extra traffic signals on the protection channel.

2. On detecting that the signal on the working channel fails, the sink in a certain direction (NEA) sends byte K to the source (NE B) on the protection channel (the request type is "signalfail").

3. NE B performs a bridge of the normal traffic signals onto the protection channel and sendsbyte K to NE A on the protection channel (the request type is "reverse request").

4. NE A receives the normal traffic signals from the protection channel and performs a bridgeof the normal traffic signals onto the protection channel.

5. NE B receives the normal traffic signals from the protection channel.

NOTE

Actually, to speed up the switching, NE B does not perform a service bridge in Step 3 but performs it in Step 5.

14.5 Planning GuideIf the OptiX RTN 600 adopts the chain network that is formed through optical fibers or STM-1ecables, it is recommended that you adopt linear MSP as the protection scheme. When planninglinear 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 dual-ended revertive mode, depending on the requirements.

l In the 1+1 single-ended non-revertive mode, the realization is simple and the switching speedis high. In addition, the equipment at both sides need not be interconnected.

l In the 1:N dual-ended revertive mode, extra services can be transmitted.




14-9

l The MS protocols used at both sides must be consistent. It is recommended that you adoptthe new protocol when both sides use the OptiX equipment.

l It is recommended that the working channel uses the line ports of one line board and theprotection channel uses those of another line board to prevent the situation in which failureof a line board causes the protection to fail.


l It is recommended that you use SD as a switching condition.

----End

14.6 Creating Linear MSPTo protect the services carried by the optical fibers or STM-1e cables between two nodes,configure linear MSP.

Prerequisitel The boards where the working unit and the protection unit are located must be configured.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MSfrom 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 toextra service and protection switching will interrupt the service in the protection timeslot."

Step 4 Set the slot mapping relation.1. In Select Mapping direction, select West Working Unit.2. In Select Mapping Mode, select the line port to which the working channel corresponds

and click .3. In Select Mapping direction, select West Protection Unit.4. In Select Mapping Mode, select the line port to which the protection channel corresponds

and click .


Feature Description


Issue 02 (2008-06-20)

Step 5 Click OK.

----End


Protection Type 1+1 Protection, 1:NProtection

1+1 Protection l In the single-ended mode, if the serviceson the working channels in a certaindirection need to be switched, only theservices on the working channels in thedirection are switched to the protectionchannels.

l In the dual-ended mode, the services onthe working channels in two directionsare switched to the protection channels.

l When Revertive Mode is set toRevertive, the NE that is in the switchingstate releases the switching and enablesthe former working channel to return tothe working state some time after theformer working channel is restored tonormal.

Switching Mode l Single-EndedSwitching, Dual-Ended Switching(1+1 protection)

l Dual-EndedSwitching (1:Nprotection)

l Single-EndedSwitching (1+1protection)

l Dual-EndedSwitching (1:Nprotection)



14-11


Revertive Mode l Non-Revertive,Revertive (1+1protection)

l Revertive (1:Nprotection)

l Non-Revertive (1+1 protection)

l Revertive (1:Nprotection)

l When Revertive Mode is set to Non-Revertive, the NE that is in the switchingstate keeps the state of the formerworking channel unchanged even thoughthe former working channel is restored tonormal unless another switching occurs.

l When extra services need to betransmitted or several working channelsexist, select 1:N protection.

l In the case of other situations, it isrecommended that you select the 1+1single-ended and non-revertive mode.






Protocol Type New Protocol,Restructure Protocol

New Protocol l The new protocol is much maturer thanthe restructure protocol but therestructure protocol is in bettercompliance with the standards than thenew protocol.

l It is recommended that you select the newprotocol. When the OptiX equipment isinterconnected with third-partyequipment, select the restructure protocolif an interconnection problem occurswhen the new protocol is adopted.


Feature Description


Issue 02 (2008-06-20)


SD/SF PRISwitching Tag

High priority, Lowpriority

High priority l When this parameter is set to Highpriority, "1101" and "1011" are used asan SF/SD switching request.

l When this parameter is set to Lowpriority, "1100" and "1010" are used asan SF/SD switching request.


Switching ModeIndication

Not indicated,Indicated

l Not indicated (1+1 protection)

l Indicated (1:Nprotection)

l When this parameter is set to Indicated,the MSP protocol uses K2 (bit 6 to bit 8)to indicate the switching mode (that is,uses code "100" to indicate the single-ended mode and code "101" to indicatethe dual-ended mode).

l When this parameter is set to Notindicated, the MSP protocol does notindicate the switching mode.



- - l In the case of 1+1 protection, only oneline port can be mapped as WestWorking Unit; in the case of 1:Nprotection, a maximum of three line portscan be mapped as West Working Unit.

l Only one line port can be mapped as WestProtection Unit.

l Ensure that the line port that is mapped asWest Protection Unit and the line portthat is mapped as West Working Unitare not on the same board, if possible.

NOTE

Ensure that the MSP groups of the equipment at both ends of the linear multiplex section are set with the sameattributes.

Postrequisitel 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 andthe protection channels.

l In the case of the 1+1 linear MSP, you need to configure unidirectional cross-connectionsbetween the services and the protection channels, in addition to configuring thebidirectional cross-connections between the services and the working channels.



14-13

14.7 Maintenance GuideThis topic describes how to start and stop linear MSP, and how to carry out a linear MSPswitching. It also describes relevant alarms and events, and problems that occur frequently duringthe application of the protection feature.

14.7.1 Starting/Stopping the Linear MSP ProtocolIf you first stop the linear MSP protocol and then start it, the linear MSP status can be restoredto the initial state.

Prerequisitel A linear MSP group must be configured.


Precautionsl Stopping the linear MSP protocol causes failure of linear MSP.

l When services are switched onto the protection channel, stopping the linear MSP protocolcauses the services to switch back to the working channel. At this time, if the workingchannel 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 linearMSP protocol is started.

Procedure


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

14.7.2 Linear MSP SwitchingThe linear MSP switching is an important maintenance operation.

Prerequisitel A linear MSP group must be configured.



Feature Description


Issue 02 (2008-06-20)

Procedure


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

14.7.3 Relevant Alarms and EventsWhen a linear MSP switching occurs, the system reports corresponding alarms and abnormalevents.

Relevant Alarmsl APS_INDI

The APS_INDI alarm indicates that a protection switching occurs.l APS_FAIL

The APS_FAIL alarm indicates that the protection switching fails.l ALM_APS_MANU_STOP

The ALM_APS_MANU_STOP alarm indicates that the MSP protocol is manually stopped.l K1_K2_M

The K1_K2_M alarm indicates that there is a mismatch between byte K1 and byte K2. Ifthe service signal indicated by the sent K1 (bit 5 to bit 8) is not the same as that indicatedby the received K2 (bit 1 to bit 4), the system reports the K1_K2_M alarm.

l K2_MThe K2_M alarm indicates a mismatch of byte K2. When the protection type indicated bythe received K2 (bit 5) does not match that of the NE, the system reports the K2_M alarm.

l LPS_UNI_BI_MThe LPS_UNI_BI_M alarm indicates a mismatch of the single-ended/dual-ended mode oflinear MSP. When the K2 (bit 6 to bit 8) is enabled to indicate the single-ended/dual-endedmode, if the received single-ended/dual-ended mode does not match the mode adopted bythe NE, the system reports the LPS_UNI_BI_M alarm. This alarm applies only to therestructure protocol.

Relevant Abnormal Eventsl Linear MSP protection switching

This abnormal event indicates that a linear MSP protection switching occurs.l No response from the remote end of the linear MSP

This abnormal event indicates that the remote end does not respond to the linear MSPswitching request sent by the local end.



14-15

14.7.4 FAQsThis topic lists the problems that occur frequently during the application of linear MSP.

Q: What switching states does linear MSP have?

A: Linear MSP has the following switching states:

l Protocol is not startedThe state when the linear MSP protocol is not started

l Protocol startingThe state when the linear MSP protocol is starting

l Protocol normalThe normal state after the linear MSP protocol is started

l LockoutThe state after the protection channel is locked out



l ExerciseThe state after an exercise switching

l Signal failureThe state after an SF switching

l Signal degradeThe state after an SD switching

l WTRThe state that exists from the time the working equipment is restored to normal after anautomatic switching until the time the revertive switching occurs in the revertive mode

Q: What should be noted when the OptiX equipment is interconnected to the third-partyequipment with linear MSP applied?

A: Note the following points:

l Select the 1+1 single-ended non-revertive mode if possible. In this case, if aninterconnection problem occurs, generally, it is because the third-party equipment hasspecial requirements for byte K.

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.

l ITU-T G.841 defines two priority levels for the SF and SD on byte K. By default, the OptiXequipment uses the SF and SD of the higher priority. If the third-party equipment uses theSF and SD of the lower priority, make modifications accordingly on the OptiX equipment.

l Check whether the third-party equipment uses the last three bits of byte K2 to indicate thesingle-ended/dual-ended mode. If yes, make modifications accordingly on the OptiXequipment.


Feature Description


Issue 02 (2008-06-20)

Q: Why the forced switching cannot be carried out when the signal on the protectionchannel fails?

A: After the signal on the protection channel fails, the protection channel is locked out. As thelockout of the protection channel has a higher priority than the forced switching, the forcedswitching cannot be carried out.

Q: Why are services interrupted after the 1+1 unidirectional linear MSP switching?

A: During the configuration of the 1+1 linear MSP on the NMS, the unidirectional cross-connection between the service source and the protection channel is not configured.



14-17

15 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-4or higher level formed by fibers, and provides protection at the MS level for services betweenthe nodes of a ring network.

The IDU 620 supports a maximum of one STM-4 two-fiber bidirectional MSP ring.

15.1 Feature DescriptionThis topic describes the protection type, meaning of byte K in the switching protocol, switchingcondition, and switching impact of the two-fiber bidirectional ring MSP.

15.2 AvailabilityThe two-fiber bidirectional ring MSP needs the support of the corresponding equipment andboards.

15.3 Relation with Other FeaturesThe two-fiber bidirectional ring MSP is related to the linear MSP and SNCP.

15.4 Realization PrincipleThe two-fiber bidirectional ring MSP adopts the automatic bridging mechanism betweenworking channels and protection channels to realize the switching.

15.5 Planning GuideIf the OptiX RTN 600 adopts the ring network that is formed by STM-4 fibers and the servicesare discrete services, it is recommended that you adopt the two-fiber bidirectional ring MSP asthe protection scheme.

15.6 Creating a Ring Multiplex SectionIf a ring network formed by STM-4 fibers is used and the services are discrete services, you canconfigure ring MSP.

15.7 Maintenance GuideThis topic describes how to start and stop the two-fiber bidirectional ring MSP, and how to carryout a two-fiber bidirectional ring MSP switching. It also describes relevant alarms and events,and problems that occur frequently during the application of the protection feature.

OptiX RTN 600 Radio Transmission SystemFeature Description 15 Two-Fiber Bidirectional Ring MSP


15-1

15.1 Feature DescriptionThis topic describes the protection type, meaning of byte K in the switching protocol, switchingcondition, and switching impact of the two-fiber bidirectional ring MSP.

15.1.1 Protection TypeThe 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 protectiontype:

l A ring network uses two fibers. One fiber is used to receive signals and the other fiber isused to transmit signals.

l Services are received and transmitted on the same route.

l The normal services between different nodes share the protection channel. The protectionchannel can be used to transfer extra services.

l The two-fiber bidirectional ring MSP adopts the revertive mode. That is, an NE that is inthe switching state releases the switching and enables the former working channel to returnto the working state some time after the former working channel is restored to normal. Theperiod from the time the former working channel is restored to normal until the time theNE releases the switching is called the wait-to-restore (WTR) time. To prevent frequentswitching events due to an unstable working channel, it is recommended that you set theWTR time to five to twelve minutes.

15.1.2 Meaning of Byte KThe two-fiber bidirectional MSP ring is switched according to the MSP protocol described inITU-T G.841. The MSP protocol uses bytes K1 and K2 in the multiplex section overhead totransfer switching requests.

Table 15-1 Meaning of byte K (two-fiber bidirectional ring MSP)

Byte K Meaning

K1 (bit 1 to bit 4) It carries the switching request code, whose meaning isprovided in Table 15-2.

K1 (bit 5 to bit 8) It carries the destination node ID.

K2 (bit 1 to bit 4) It carries the source node ID.

K2 (bit 5) 1 represents the long path and 0 represents the short path.

K2 (bit 6 to bit 8) It carries the status. 000 represents the idle state, 111represents the MS-AIS state, 110 represents the MS-RDIstate, 011 represents that extra traffic exists, 010 representsthe bridging and switching, and 001 represents thebridging.a

15 Two-Fiber Bidirectional Ring MSPOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

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 equipmentreceives the services that should be received from the west (or east) working channels in normal cases from theeast (or west) protection channels.

Table 15-2 Switching request code

Bit 1 Bit 2 Bit 3 Bit 4 Meaning

1 1 0 1 Forced switching_ring (FS_R)

1 0 1 1 Signal fail_ring (SF_R)

1 0 0 0 Signal degrade_ring (SD_R)

0 1 1 0 Manual switching_ring (MS_R)

0 1 0 1 WTR

0 0 1 1 Exercise switching_ring (EXER_R)

0 0 0 1 Reverse request_ring (RR_R)

0 0 0 0 No request

NOTE

l A reverse request inherits the priority of the bridge request to which the reverse request responds.

l The other values of the bridge request code are used in the case of the two-fiber ring MSP, and hence, arenot described here.

15.1.3 Switching ConditionTwo-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 15-3 Switching conditions of the two-fiber bidirectional ring MSP









15-3


Signal fail (SF) The SF on the working channel causes traffic signalsto be switched to the protection channel. When thereis the R_LOC, R_LOF, R_LOS, MS_AIS, orB2_EXC alarm on the working channel, the SFswitching is triggered.







Traffic signals are not actually switched. Theexercise functionality is used only to check if an NEcan normally carry out the MSP protocol.

NOTE




l If an NE needs to perform switching according to byte K sent from another node NE, the NE determinesthe switching priority according to the bridge request code contained in byte K. For the meaning of byte K,see 15.1.2 Meaning of Byte K.


Feature Description


Issue 02 (2008-06-20)

15.1.4 Switching ImpactWithin the MSP switching time (shorter than 50 ms), services are interrupted. Extra services areinterrupted within the period from the time normal services are switched to the protection channeluntil the time the services are restored to the working channel.

15.2 AvailabilityThe two-fiber bidirectional ring MSP needs the support of the corresponding equipment andboards.

Table 15-4 Availability of the two-fiber bidirectional ring MSP


Two-fiber bidirectional ringMSP

SL4 (all the versions) IDU 620

15.3 Relation with Other FeaturesThe two-fiber bidirectional ring MSP is related to the linear MSP and SNCP.l The line of a two-fiber bidirectional MSP ring cannot be configured with linear MSP.

l The line of a two-fiber bidirectional MSP ring can work only as the sink of an SNCP servicepair, and cannot work as the working source or protection source.

15.4 Realization PrincipleThe two-fiber bidirectional ring MSP adopts the automatic bridging mechanism betweenworking channels and protection channels to realize the switching.

NOTE

The following describes the switching principle of the two-fiber bidirectional ring MSP. The protectionswitching triggered by a unidirectional signal failure on a two-fiber bidirectional MSP ring formed by four NEsis provided as an example.



15-5

Figure 15-1 Realization principle of the two-fiber bidirectional ring MSP (before the switching)

STM-4 two-fiberbidirectional MSP ring

NE A

NE B

NE C

NE D

East

West

West

West

East

East

West

East

Service between NE A and NE C

#1 VC-4

Figure 15-2 Realization principle of the two-fiber bidirectional ring MSP (after the switching)

STM-4 two-fiberbidirectional MSP ring

NE A

NE B

NE C

NE D

East West

West

East

East

East

Service from NE A to NE C

#3VC-4

#3 VC-4

#1 VC-4

West

West

When the signal on the working channel fails, the switching principle of the two-fiberbidirectional ring MSP is as follows:

1. When the network is in the normal state, the service between NE A and NE C is transmittedin certain timeslots of the first VC-4 in the line. The service route is shown in Figure15-1.

2. On detecting that the signal on the working channel in the receive direction fails, the westline 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 andthe state being idle) on the long path (NE B -> NE C -> NE D -> NE A).

3. On receiving byte K sent from NE B to NE A, NE C and NE D transparently transmit thereceived byte K.

4. On receiving byte K on the short path, the east line board of NE A sends byte K (the requesttype being RR_R and the state being idle) on the short path (NE A -> NE B) and also sendsbyte 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. On receiving byte K on the long path, the west line board of NE A sends byte K (the requesttype being RR_R and the state being the bridging and switching) on the short path (NE A


Feature Description


Issue 02 (2008-06-20)

-> NE B) and also sends byte K (the request type being SF_R and the state being the bridgingand 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 bereceived 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 normalcases 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 switchingstate.

6. On receiving byte K (the request type being SF_R and the state being the bridging andswitching) sent from NE A to NE B, NE C and NE D enter the pass-through state. WhenNE C and NE D pass through byte K, NE C and NE D also pass through the informationcarried on the protection channels.

7. On receiving byte K (the request type being SF_R and the state being the bridging andswitching) sent from NE A, NE B sends byte K (the request type being SF_R and the statebeing 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 bereceived 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 normalcases 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 theservice to the first VC-4 in the east direction in the normal state, but receives the servicefrom the third VC-4 path in the east direction and transmits the service to the first VC-4path in the east direction in the west switching state.

15.5 Planning GuideIf the OptiX RTN 600 adopts the ring network that is formed by STM-4 fibers and the servicesare discrete services, it is recommended that you adopt the two-fiber bidirectional ring MSP asthe protection scheme.

Procedure

Step 1 Allocate a node ID to each NE.

l The number of NE nodes must not exceed 16. The value range of a node ID is from 0 to 15.

l In the case of a newly built ring network, it is recommended that you set the node ID of thecentral station in the network to 0 and allocate node IDs to the other NEs one by onecounterclockwise, with the node ID of each NE being one more than the node ID of theprevious NE.

l If you add an NE in an existing ring network, it is recommended that you set the node ID ofthe new NE to the number that is one less than the maximum number of the nodes (includingthe new NE) in the ring network.


l The MSP protocols used in a ring network must be consistent. It is recommended that youselect the new protocol.

l Set the WTR time to a value in the range from five minutes to twelve minutes. It isrecommended that you set the value to ten minutes.



15-7

l It is recommended that you use SD as a switching condition.

----End

15.6 Creating a Ring Multiplex SectionIf a ring network formed by STM-4 fibers is used and the services are discrete services, you canconfigure ring MSP.

Prerequisitel The boards where the working unit and the protection unit are located must be configured.


Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ring MS fromthe Function Tree.

Step 2 Click New.The system displays the message "This service will change to extra service and protectionswitching 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 MS protection group.

Step 5 Set the slot mapping relation.1. In Select Mapping Direction, select West Line 1.2. In Select Mapping Mode, select the line port to which the working channel corresponds

and click .3. In Select Mapping Direction, select East Line 1.4. In Select Mapping Mode, select the line port to which the protection channel corresponds

and click .


Feature Description


Issue 02 (2008-06-20)

Step 6 Click OK.

----End


Level STM-4 STM-4 This parameter is prohibited from beingmodified.

Protection Type 2-fiber BidirectionalMultiplex Section

2-fiber BidirectionalMultiplex Section

This parameter is prohibited from beingmodified.

Local Node 0 to 15 0 l This parameter specifies the node IDallocated to the local NE.

l The node ID of each NE must be unique.

West Node 0 to 15 0 This parameter specifies the node ID that isallocated to the NE to which the west lineboard of the local NE is connected.

East Node 0 to 15 0 This parameter specifies the node ID that isallocated to the NE to which the east lineboard of the local NE is connected.



15-9


WTR Time(s) 300 to 720 600 l When the time after the former workingchannel is restored to normal reaches theset value of this parameter, a revertiveswitching occurs.




Protocol Type New Protocol,Restructure Protocol

New Protocol l The new protocol is much maturer thanthe restructure protocol but therestructure protocol is in bettercompliance with the standards than thenew protocol.

l It is recommended that you select the newprotocol. When the OptiX equipment isinterconnected with third-partyequipment, select the restructure protocolif an interconnection problem occurswhen the new protocol is adopted.


- - It is recommended that you map the line portof the SL4 board in slot 6 as West Line 1and map the line port of the SL4 board inslot 8 as East Line 1.

Map as VC4 Selected, Notselected

Not selected l If you select Map as VC4, the VC-4 isconsidered as the unit of the settings inthe slot mapping relation.


NOTE

The protection groups of the NEs that form a ring multiplex section must be set with the same attributes exceptLocal Node, West Node, and East Node.

PostrequisiteIn the case of a two-fiber bidirectional MSP ring, you need to configure bidirectional cross-connections between the services and the timeslots of the working channel (the first half of thetimeslots of the line port) later. If extra services need be transmitted, you need to configurebidirectional cross-connections between the extra services and the timeslots of the protectionchannel (the second half of the timeslots of the line port).


Feature Description


Issue 02 (2008-06-20)

15.7 Maintenance GuideThis topic describes how to start and stop the two-fiber bidirectional ring MSP, and how to carryout a two-fiber bidirectional ring MSP switching. It also describes relevant alarms and events,and problems that occur frequently during the application of the protection feature.

15.7.1 Starting/Stopping the Ring MSP ProtocolIf you first stop the ring MSP protocol and then start it, the ring MSP status can be restored tothe initial state.

Prerequisitel A ring MSP group must be configured.


Precautionsl Stopping the ring MSP protocol causes failure of ring MSP.

l When services are switched onto the protection channel, stopping the ring MSP protocolcauses the services to switch back to the working channel. At this time, if the workingchannel 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 protocolis started.

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ring MS fromthe 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

15.7.2 Ring MSP SwitchingThe ring MSP switching is an important maintenance operation.

Prerequisitel A ring MSP group must be configured.




15-11

ProcedureStep 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

15.7.3 Relevant Alarms and EventsWhen a two-fiber bidirectional ring MSP switching occurs, the system reports correspondingalarms and abnormal events.

Relevant Alarmsl APS_INDI

The APS_INDI alarm indicates that a protection switching occurs.l APS_FAIL

The APS_FAIL alarm indicates that the protection switching fails.l APS_MANU_STOP

The APS_MANU_STOP alarm indicates that the MSP protocol is manually stopped.

Relevant Abnormal Eventsl MSP switching

This abnormal event indicates that a ring MSP switching occurs.l No response from the remote end of the ring MSP

This abnormal event indicates that the remote end does not respond to the ring MSPswitching request sent by the local end.

15.7.4 FAQsThis topic lists the problems that occur frequently during the application of the two-fiberbidirectional 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 theconsistency of service routes, it is required that most of the services are configured to travel inone 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 sendsservices is the primary direction, the line direction is called the east. If the line direction in whichthe 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?


Feature Description


Issue 02 (2008-06-20)

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

l Protocol starting

The state when the MSP protocol is starting

l Idle

The normal state after the MSP protocol is started

l Switching

This refers to the state after a switching event. In the case of east switching, the equipmentreceives the services that should be received from the west working channels in normalcases from the east protection channels, and transmits the services that should be transmittedto the west working channels in normal cases to the east working channels. In the case ofwest switching, the equipment receives the services that should be received from the eastworking channels in normal cases from the west protection channels, and transmits theservices that should be transmitted to the east working channels in normal cases to the westprotection channels.

l Pass-through

In the pass-through state, the cross-connections on the working channels remain unchanged,and the services on the protection channels in the east and west directions are passedthrough.

Q: What are the differences between a two-fiber bidirectional MSP ring and an SNCPring?

A:


SNCP Ring

Protected object A line Services between subnets

Protection level Multiplex section level VC-4 level, VC-3 level, orVC-12 level

Protection mechanism Shared protection Dedicated protection

Line rate STM-4 or an STM mode witha higher rate

PDH microwave, STM-1, oran STM mode with a higherrate

Switching mode Ring switching Single-ended switching

Bridging/Switching point The head end/tail endautomatically performsbridging and switchingaccording to the APSprotocol. Generally, the headend/tail end is both thebridging node and switchingnode.

The transmit end ispermanently bridged and thereceive end is automaticallyswitched.



15-13


SNCP Ring

Reliability Relatively low Relatively high

Maximum capacity STM-N x n/2 (n representsthe number of the nodes on aring)

STM-N

Number of the nodes on aring network

16 (at most) No restriction

Application Scenario A ring network whereservices are distributedamong NEs

A ring network whereservices are centralized on acentral NE

Q: How does one handle a two-fiber bidirectional ring MSP switching failure?


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 networktopology. 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 channelwith reference to the alarm.

3. Check the MSP state of each NE. In the case of normal switching, the head-end/tail-endnode 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.l 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.


Feature Description


Issue 02 (2008-06-20)

16 Features of Ethernet Ports

About This Chapter

To effectively work with the data communication equipment at the client side, the Ethernet portsupports the auto-negotiation function, Jumbo frames, and flow control function.

16.1 Feature DescriptionThis topic describes the auto-negotiation function, Jumbo frames, and flow control function ofthe Ethernet port.

16.2 AvailabilityThe Ethernet port feature requires support of the involved equipment and boards.

16.3 Relation with Other FeaturesThe auto-negotiation function, Jumbo frames, and flow control function do not affect otherfeatures.

16.4 Realization PrincipleThe realization principles of the auto-negotiation function and the flow control function complywith IEEE 802.3.

16.5 Planning GuideBefore you plan Ethernet port features, obtain the information of the client-side equipment.

16.6 Configuration GuideThis topic describes the configuration tasks relevant to the Ethernet port feature.

16.7 Maintenance GuideThis topic describes alarms and events relevant to the Ethernet port feature and problems thatoccur frequently during the application of the feature.

OptiX RTN 600 Radio Transmission SystemFeature Description 16 Features of Ethernet Ports


16-1

16.1 Feature DescriptionThis topic describes the auto-negotiation function, Jumbo frames, and flow control function ofthe Ethernet port.

16.1.1 Auto-Negotiation FunctionThe auto-negotiation function allows the network equipment to send information of its supportedworking mode to the opposite end on the network and to receive the corresponding informationthat the opposite end may transfer.

Auto-Negotiation Function of FE Electrical PortsIn the case of FE electrical ports, there are four common working modes: 10M half-duplex, 10Mfull-duplex, 100M half-duplex, and 100M full-duplex. If the working mode of an Ethernet portdoes not match that of its opposite port, the two ports cannot communicate. With the auto-negotiation function, however, the two ports can communicate with each other. The auto-negotiation function uses fast link pulses and normal link pulses to transfer the negotiationinformation of the working mode to enable the working mode of the local Ethernet port to matchthe working mode of the opposite end.

Table 16-1 lists the auto-negotiation rules of FE electrical ports.

Table 16-1 Auto-negotiation rules of FE electrical ports (when the local port adopts the auto-negotiation mode)

Working Mode of the Opposite Port Auto-Negotiation Result

Auto-negotiation 100M full-duplex

10M half-duplex 10M half-duplex

10M full-duplex 10M half-duplex



NOTE

From Table 16-1, it is evident that when the working mode of the opposite equipment is 10M full-duplex or100M full-duplex, the auto-negotiation result cannot realize the matching between the working modes of bothsides, and hence 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 FE electrical ports on both sides are working in the auto-negotiation mode, theequipment on both sides can negotiate the flow control function through the auto-negotiationfunction.

Auto-Negotiation Function of GE Electrical PortsIn the case of GE electrical ports, there are five working modes: 10M half-duplex, 10M full-duplex, 100M half-duplex, 100M full-duplex, and 1000M full-duplex. The auto-negotiation

16 Features of Ethernet PortsOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

function of GE electrical ports is similar to the auto-negotiation function of FE electrical ports.Table 16-2 lists the auto-negotiation rules of GE electrical ports.

Table 16-2 Auto-negotiation rules of GE electrical ports (when the local port adopts the auto-negotiation mode)

Working Mode of the Opposite Port Auto-Negotiation Result

Auto-negotiation 100M full-duplex







When the GE electrical ports on both sides are working in the auto-negotiation mode, theequipment on both sides can negotiate the flow control function through the auto-negotiationfunction.

Auto-Negotiation Function of GE Optical Ports

GE optical ports support only the 1000M full-duplex working mode. The auto-negotiationfunction 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 opticalport of the equipment on the other side works in the auto-negotiation mode, a link error occurs due to an auto-negotiation failure, and as a result, a LINK_ERR alarm is generated.

16.1.2 Jumbo FramesThe Ethernet board can receive and transmit the Jumbo frame that is not longer than 9600 bytes.

An Ethernet frame requires that the maximum length 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 Jumboframe adopts the structure of an ordinary Ethernet frame but does not have a requirement for themaximum length of the payload. To differentiate a Jumbo frame from an ordinary Ethernetframe, we define the type field of a Jumbo frame as "0x8870".

The differences between the ways in which different Ethernet boards process Jumbo frames areas follows:

l The Ethernet port of an EFT4 board checks whether an Ethernet frame is a Jumbo frameby checking the type field in the Ethernet frame. If the Ethernet frame is a Jumbo frame,there is no restriction on the maximum frame length.



16-3

l The Ethernet port of an EMS6 board does not check whether an Ethernet frame is a Jumboframe. All the frames are restricted by the maximum frame length.

l VCTRUNKs 1–4 of an EFT4 board and VCTRUNKs 5–8 of an EMS6 board check whetheran Ethernet frame is a Jumbo frame. If the Ethernet frame is not a Jumbo frame and theframe has more than 1535 bytes, the board discards the frame. VCTRUNKs 1–4 of anEMS6 board do not check for Jumbo frames. The EMS6 board discards all the frames eachof which has more than 1535 bytes.

NOTE

The maximum frame length (that is, the maximum transport unit (MTU)) is a parameter of Ethernet ports. Inthe case of ordinary Ethernet frames, the Ethernet board discards the frame whose length is more than the valuespecified by this parameter.

The default type field of a Jumbo frame is "0x8870". The EFT4 board does not support themodification of the default value, whereas the EMS6 board supports the modification of thedefault value.

16.1.3 Flow Control FunctionWhen the data processing/transferring capability of the equipment fails to handle the flowreceived at the port, congestion occurs on the line. To reduce the number of discarded packetsdue to buffer overflow, proper flow control measures must be taken.

The half-duplex Ethernet adopts the back-pressure mechanism to control the flow. The full-duplex Ethernet adopts PAUSE frames to control the flow. Currently, as the half-duplex Ethernetis not widely applied, the flow control function realized by the Ethernet board is in the case ofthe full-duplex Ethernet.

The flow control function realized by the Ethernet board is of two types, auto-negotiation flowcontrol and non-auto-negotiation flow control.

Auto-Negotiation Flow Control

When the Ethernet port is working in the auto-negotiation mode, you can adopt the auto-negotiation flow control function. The auto-negotiation flow control modes include thefollowing:

l Asymmetric PAUSE toward the link partner

In the case of congestion, the port can send PAUSE frames but cannot process receivedPAUSE frames.

l Symmetric PAUSE

The port can send and process PAUSE frames.

l Both asymmetric and symmetric PAUSE

The port has the following three capabilities:

– Sends and processes PAUSE frames.

– Sends but does not process PAUSE frames.

– Processes but does not send PAUSE frames.

l Disabled

The port does not send nor process PAUSE frames.


Feature Description


Issue 02 (2008-06-20)

Non-Auto-Negotiation Flow Control

When the Ethernet port is working in a fixed working mode, you can adopt the non-auto-negotiation flow control function. The non-auto-negotiation flow control modes include thefollowing:

l Send only

In the case of congestion, the port can send PAUSE frames but cannot process receivedPAUSE frames.

l Receive only

In the case of congestion, the port can process received PAUSE frames but cannot sendPAUSE frames.

l Send and receive

The port can send PAUSE frames and can also process received PAUSE frames.

l Disabled

The port does not send nor process PAUSE frames.

16.2 AvailabilityThe Ethernet port feature requires support of the involved equipment and boards.

Table 16-3 Availability of the Ethernet port feature


Auto-negotiation EFT4 (all the versions) IDU 610/620

EMS6 (all the versions) IDU 620

Jumbo frame EFT4 (all the versions) IDU 610/620


Flow control function EFT4 (all the versions) IDU 610/620


16.3 Relation with Other FeaturesThe auto-negotiation function, Jumbo frames, and flow control function do not affect otherfeatures.

16.4 Realization PrincipleThe realization principles of the auto-negotiation function and the flow control function complywith IEEE 802.3.



16-5

16.4.1 Auto-Negotiation FunctionThe auto-negotiation function uses fast link pulses and normal link pulses to transfer informationof 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 functionof FE electrical ports is provided as an example.

The fast link pulse (FLP) is called the 10BASE-T link integrity test pulse sequence. Each devicemust be capable of issuing FLP bursts at power up, on command from management, or due touser interaction. The FLP burst consists of a series of link integrity test pulses that form analternating clock/data sequence. Extraction of the data bits from the FLP burst yields a link codeword that identifies the working modes supported by the remote device, as well as certaininformation used for the handshake mechanism of the auto-negotiation function.

To maintain interoperability with existing 10BASE-T devices, the auto-negotiation function alsosupports the reception of 10BASE-T compliant link integrity test pulses. 10BASE-T link pulseactivity is referred to as the normal link pulse (NLP) sequence. A device that fails to respond tothe FLP burst sequence by returning only the NLP sequence is treated as a 10BASE-T compatibledevice.

The first pulse in an FLP burst is defined as a clock pulse. Clock pulses within an FLP burst arespaced at 125 us. Data pulses occur in the middle of two adjacent clock pulses. The positivepulse represents a logic one and the absence of a pulse represents a logic zero. An FLP burstconsists of 17 clock pulses and 16 data pulses (if all data bits are 1). The NLP waveform issimpler than the FLP waveform. The NLP sends a positive pulse every 16 ms when no dataframe needs to be transmitted.

Figure 16-1 Waveform of a single FLP

Clock pulses

First bit on wire

Data

Encoding

1 1 0 1D0

D1

D2

D3

…

…

…

T1

T2

T3

T1: 100 ns T2: 62.5 us T3: 125 us


Feature Description


Issue 02 (2008-06-20)

Figure 16-2 Consecutive FLP bursts and NLPs

FLP bursts

NLPs

T4T5

T4: 2 ms T5: 16 ms

16.4.2 Flow Control FunctionThe 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 receivebuffer 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<N≤65535).

2. On receiving the PAUSE frame, and being capable of processing PAUSE frames, theEthernet 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).

3. If the congestion at the receive port is cleared (the data in the receive buffer is below acertain threshold) but the pause-time does not end, the port sends a PAUSE frame whosepause-time is 0 to notify the opposite end to start sending data.

IEEE 802.3 defines the format of the PAUSE frame as follows:

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

Figure 16-3 Structure of the PAUSE frame

01-80-C2-00-00-01

XX-XX-XX-XX-XX-XX

88-08

00-01

XX-XX

Reserved

Destination address 6 octets

6 octetsSource address

Type/Length 2 octets

2 octets

2 octets

MAC control opcode

MAC control parameter(pause-time)



16-7

16.5 Planning GuideBefore you plan Ethernet port features, obtain the information of the client-side equipment.

Procedure

Step 1 Plan the working mode of the Ethernet port.

Follow these two principles when planning the working mode of the Ethernet port:

l In the case of the EFT4 board, if the port on the opposite side works in the 10M full-duplexor 100M full-duplex mode, set the working mode of the local port to the same working mode;if the port on the opposite side works in the auto-negotiation mode, 10M half-duplex mode,or 100M half-duplex mode, set the working mode of the local port to the auto-negotiationmode.

l In the case of the EMS6 board, set the working mode of the local port to the same workingmode of the port on the opposite side.

Step 2 Plan the parameter MTU.

In the case of the EFT4 board, follow these four principles when planning the MTU of theEthernet port:

l The MTU should be greater than the length of the maximum frame among all L2 data framesto be transmitted.

l The value of the MTU ranges from 1518 to 1535 bytes.

l The default value of the MTU is 1522 bytes, which is the sum of the length of the maximumbasic frame and the length of the VLAN label.

l The MTU is invalid for the Jumbo frame.

In the case of the EMS6 board, follow these four principles when planning the MTU of theEthernet port:

l The MTU should be greater than the length of the maximum frame among all L2 data framesto be transmitted.

l The value of the MTU ranges from 1518 to 1535 bytes.

l The default value of the MTU is 1522 bytes, which is the sum of the length of the maximumbasic frame and the length of the VLAN label.

l The MTU parameter restricts the maximum length of a Jumbo frame.

Step 3 Plan the flow control parameters for the Ethernet port.

Follow these six principles when planning the flow control parameters for the Ethernet port:

l The flow control parameters are valid only for the full-duplex Ethernet.

l The flow control parameters are valid only for the Ethernet transparent transmission service.

l When the Ethernet port works in the auto-negotiation mode, use the auto-negotiation flowcontrol parameter.

l When the Ethernet port works in a fixed working mode, use the non-auto-negotiation flowcontrol parameter.


Feature Description


Issue 02 (2008-06-20)

l The flow control parameters at both sides must match each other. It is prohibited that theflow control function is enabled at one side and disabled at the other side.

l It is recommended that you enable the flow control function for the Ethernet board and forthe opposite equipment on the network with flow bursts.

----End

16.6 Configuration GuideThis topic describes the configuration tasks relevant to the Ethernet port feature.

16.6.1 Configuring the External Port of the Ethernet BoardWhen an NE accesses Ethernet services through an external port (that is, PORT) of an Ethernetboard, the attributes of the external port need to be set. Thus, the Ethernet board works with thedata communication equipment on the client side to access the Ethernet services.

Prerequisitel The Ethernet board must be included in the slot layout.


PrecautionsThe OptiX RTN 600 supports two types of Ethernet boards: EFT4 board and EMS6 board.

l Ethernet ports FE1–FE4 of an EFT4 board correspond to PORT1–PORT4 respectively.The EFT4 board does not support the setting of TAG attributes, network attributes, and thebroadcast packet suppression function.

l Ethernet ports FE1–FE4 of an EMS6 board correspond to PORT1–PORT4 respectively.Ports GE1 and GE2 of an EMS6 board correspond to PORT5 and PORT6 respectively.

NOTE

The following procedures describe how to configure the external port of an EMS6 board. The EFT4 board doesnot support the configuration of the TAG attributes, network attributes, and broadcast packet suppressionfunction.

Procedure

Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet InterfaceManagement > Ethernet Interface from the Function Tree. Select External Port.

Step 2 Set the basic attributes of the port.1. Click the Basic Attributes tab.2. Set the basic attributes of the port.



16-9

3. Click Apply.

Step 3 Set the flow control mode of the port.

1. Click the Flow Control tab.

2. Set the flow control mode of the port.

3. Click Apply.

Step 4 Optional: Set the TAG attributes of the port.

1. Click the TAG Attributes tab.

2. Set the TAG attributes of the port.

3. Click Apply.

Step 5 Optional: Set the network attributes of the port.

1. Click the Network Attributes tab.

2. Set the network attributes of the port.

3. Click Apply.

Step 6 Optional: Set the broadcast packet suppression function of the port.

1. Click the Advanced Attributes tab.

2. Set the broadcast packet suppression function of the port.


Feature Description


Issue 02 (2008-06-20)

3. Click Apply.

----End


Port Enabled Enabled, Disabled Disabled l In the case of the port that accessesservices, set this parameter to Enabled.In the case of other ports, set thisparameter to Disabled.

l If this parameter is set to Enabled for theport that does not access services, anETH_LOS alarm may be generated.

Working Mode l 10M Full-Duplex, 100MFull-Duplex,Auto-Negotiation(EFT4)

l 10M Half-Duplex, 10MFull-Duplex,100M Half-Duplex, 100MFull-Duplex,1000M Full-Duplex, Auto-Negotiation(EMS6)

Auto-Negotiation l The Ethernet ports of different typessupport different working modes.

l When the equipment on the opposite sideworks in the auto-negotiation mode, setthe working mode of the equipment onthe local side to Auto-Negotiation.

l When the equipment on the opposite sideworks in the full-duplex mode, set theworking mode of the equipment on thelocal side to 10M Full-Duplex, 100MFull-Duplex, or 1000M Full-Duplexdepending on the port rate of theequipment on the opposite side.

l When the equipment on the opposite sideworks in the half-duplex mode, set theworking mode of the equipment on thelocal side to 10M Half-Duplex, 100MHalf-Duplex, or Auto-Negotiationdepending on the port rate of theequipment on the opposite side.



16-11


Maximum FrameLength

l 1518–1535(EFT4)

l 1518–9600(EMS6)

1522 l The value of this parameter should begreater than the maximum length of aframe among all the L2 data frames to betransported.

l In the case of the EFT4 board, thisparameter is invalid for Jumbo frames. Inthe case of the EMS6 board, thisparameter has a restriction on Jumboframes.

l If Jumbo frames are not considered andthe accessed services are ordinaryEthernet frames that use VLAN tags ordo not have VLAN tags, it isrecommended that you use the defaultvalue. If the access services includeservices that use double tags such asQinQ services, it is recommended thatyou set this parameter to 1526.

MAC Loopback Non-Loopback,Inloop

Non-Loopback l When this parameter is set to Inloop, theEthernet frame signals that are to be sentto the opposite end are looped back.

l In normal cases, use the default value.

PHY Loopback Non-Loopback,Inloop

Non-Loopback l When this parameter is set to Inloop, theEthernet physical signals that are to besent to the opposite end are looped back.

l In normal cases, use the default value.

Non-AutonegotiationFlow Control Mode

Disabled, EnableSymmetric FlowControl, Send Only,Receive Only

Disabled l This parameter is used when WorkingMode is not set to Auto-Negotiation.

l When this parameter is set to EnableSymmetric Flow Control, the port cansend PAUSE frames and processreceived PAUSE frames.

l When this parameter is set to SendOnly, the port can send PAUSE framesin the case of congestion but cannotprocess received PAUSE frames.

l When this parameter is set to ReceiveOnly, the port can process receivedPAUSE frames but cannot send PAUSEframes in the case of congestion.

l The non-autonegotiation flow controlmode of the equipment on the local sidemust match the non-autonegotiation flowcontrol mode of the equipment on theopposite side.


Feature Description


Issue 02 (2008-06-20)


AutonegotiationFlow Control Mode

Disabled, EnableSymmetric/Dissymmetric FlowControl, EnableSymmetric FlowControl, EnableDissymmetric FlowControl

Disabled l This parameter is used when WorkingMode is set to Auto-Negotiation.

l When this parameter is set to EnableSymmetric Flow Control, the port cansend and process PAUSE frames.

l When this parameter is set to EnableDissymmetric Flow Control, the portcan send PAUSE frames in the case ofcongestion but cannot process receivedPAUSE frames.

l When this parameter is set to EnableSymmetric/Dissymmetric FlowControl, the port can perform as follows:– Sends and processes PAUSE frames.

– Sends but does not process PAUSEframes.

– Processes but does not send PAUSEframes.

l The autonegotiation flow control mode ofthe equipment on the local side mustmatch the autonegotiation flow controlmode of the equipment on the oppositeside.

Ingress Check Enabled, Disabled Enabled l This parameter specifies whether tocheck the incoming packets from the portaccording to the TAG attributes.

l Set this parameter according to actualsituations.

TAG Access, Tag Aware,Hybrid

Tag Aware l When ports are configured with TAGflags, the ports process frames by usingthe methods provided in Table 16-4.

l If all the accessed services are frameswith the VLAN tag (tagged frames), setthis parameter to Tag Aware.

l If all the accessed services are frames thatdo not have the VLAN tag (untaggedframes), set this parameter to Access.

l When the accessed services containtagged frames and untagged frames, setthis parameter to Hybrid.



16-13


Default VLAN ID 1 to 4095 1 l This parameter is valid only when TAGis set to Access or Hybrid.

l For the usage of this parameter, see Table16-4.


VLAN Priority 0 to 7 0 l This parameter is valid only when TAGis set to Access or Hybrid.


l When the VLAN priority is required todivide streams or to be used for otherpurposes, set this parameter according toactual situations. Generally, it isrecommended that you use the defaultvalue.

Port Type UNI, C-Aware, S-Aware

UNI l When this parameter is set to UNI, theport processes data frames according tothe tag attributes.

l When this parameter is set to C-Awareor S-Aware, the port does not processdata frames according to the tag attributesbut processes the data frames accordingto the way of processing QinQ services.

l In the case of QinQ services, set thisparameter to the default value because theNE automatically sets network attributesaccording to the operation type that is setwhen the QinQ services are created.

Enabling BroadcastPacket Suppression

Enabled, Disabled Disabled This parameter specifies whether to restrictthe traffic of broadcast packets according tothe ratio of the broadcast packets to the totalpackets. When a broadcast storm may occurin the equipment on the opposite side, setthis parameter to Enabled.

Broadcast PacketSuppressionThreshold

1 to 10 3 When this parameter is set to N, the portdiscards the received broadcast packetswhen the ratio of the received broadcastpackets to the total packets exceeds Nx10%.The value of this parameter should begreater than the ratio of the broadcastpackets to the total packets when thebroadcast storm does not occur. Generally,set this parameter to 3 or a greater value.


Feature Description


Issue 02 (2008-06-20)

Table 16-4 Methods used by ports to process data frames

Direction Type ofDataFrame

How to Process

Tag aware Access Hybrid

Ingress Taggedframe

The port receives theframe.

The port discards theframe.


Untaggedframe


The port adds the VLANtag to which DefaultVLAN ID and VLANPriority correspond, tothe frame, and receives theframe.


Egress Taggedframe

The port transmits theframe.

The port strips the VLANtag from the frame andthen transmits the frame.

l If the VLAN ID in theframe is DefaultVLAN ID, the portstrips the VLAN tagfrom the frame and thentransmits the frame.

l If the VLAN ID in theframe is not DefaultVLAN ID, the portdirectly transmits theframe.

16.6.2 Modifying the Type Field of Jumbo FramesBy default, the type field of Jumbo frames processed by Ethernet boards is set to "0x8700".



Precautions

The OptiX RTN 600 supports two types of Ethernet boards: EFT4 board and EMS6 board.

l The EFT4 board does not support the modification of the type field of Jumbo frames.

l The EMS6 board supports the modification of the type field of Jumbo frames.

Procedure

Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet InterfaceManagement > Jumbo Frame from the Function Tree.

Step 2 Modify the type field of Jumbo frames.



16-15

Step 3 Click Apply.

----End


Jumbo Frame - 88 70 This parameter specifies the typefield of Jumbo frames. Set thisparameter according to the typefield of the accessed Jumbo frames.

16.7 Maintenance GuideThis topic describes alarms and events relevant to the Ethernet port feature and problems thatoccur frequently during the application of the feature.

16.7.1 Relevant Alarms and EventsWhen a feature of the Ethernet port becomes abnormal, the system reports corresponding alarmsand RMON events.

Relevant Alarmsl ETH_LOS

The ETH_LOS alarm indicates that the network port is disconnected.l LINK_ERR

The LINK_ERR alarm indicates that an error occurs on a data link.l MOD_TYPE_MISMATCH

The MOD_TYPE_MISMATCH alarm indicates that the modules at the ports do not matcheach other.

l PORT_MODULE_OFFLINEThe PORT_MODULE_OFFLINE alarm indicates that the port is not in position.

Relevant RMON EventsFor RMON events, see the 22 Remote Monitoring Feature.

16.7.2 FAQsThis topic lists the problems that occur frequently during the application of the Ethernet portfeature.


Feature Description


Issue 02 (2008-06-20)

Q: If the setting of the opposite equipment is unavailable, how does one find out whetherthe opposite Ethernet port is working in the 100M full-duplex mode or in the auto-negotiation mode at the local station?

A: There are the following methods:

1. Set the working mode of the local Ethernet port to the auto-negotiation mode.2. Query the physical parameters of the local port on the NMS.3. 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 judge that an Ethernet port receives a frame whose length is longer thanthe MTU?


1. Enable the RMON performance monitoring function for the Ethernet port.2. After traffic signals are transmitted for some time, check the value of the ETHOVER

(received over-long packets) in the RMON performance event.3. 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 judge that an Ethernet port starts the flow control function?


1. Enable the RMON performance monitoring function for the Ethernet port.2. 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 theRMON performance event.

3. If the value of the RXPAUSE is not 0, the Ethernet port has received PAUSE frames. Ifthe value of the TXPAUSE is not 0, the Ethernet port has sent PAUSE frames.



16-17

17 Encapsulation and Mapping of EthernetServices

About This Chapter

To transparently transmit Ethernet frames through the optical transmission network and the radiotransmission network, it is necessary to encapsulate the Ethernet frames and map them into VCcontainers at the access point.

17.1 Feature DescriptionThis topic describes the encapsulation and mapping protocols of Ethernet services, and thevirtual concatenation technology and the LCAS technology relevant to the mapping.

17.2 AvailabilityThe Ethernet encapsulation and mapping feature requires support of the involved equipment andboards.

17.3 Relation with Other FeaturesThe Ethernet service encapsulation, virtual concatenation, and LCAS technology do not havean impact on other features.

17.4 Realization PrincipleThis topic describes the realization principles of the encapsulation and mapping protocol of theEthernet service, the relevant virtual concatenation and LCAS technology.

17.5 Planning GuideBefore you plan the Ethernet encapsulation and mapping features, obtain the information of theopposite equipment.

17.6 Configuring the Internal Port of the Ethernet BoardWhen 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 boardworks with the Ethernet board on the opposite side to realize the transmission of the Ethernetservices in the network.

17.7 Maintenance Guide

OptiX RTN 600 Radio Transmission SystemFeature Description 17 Encapsulation and Mapping of Ethernet Services


17-1

This topic describes how to increase/decrease the VCTRUNK bandwidth, alarms and eventsrelevant to the Ethernet service encapsulation and mapping, and problems that occur frequentlyduring the application of the feature.

17 Encapsulation and Mapping of Ethernet ServicesOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

17.1 Feature DescriptionThis topic describes the encapsulation and mapping protocols of Ethernet services, and thevirtual concatenation technology and the LCAS technology relevant to the mapping.

17.1.1 Encapsulation and Mapping ProtocolsThe encapsulation and mapping protocols used by the Ethernet board include the high-level datalink control (HDLC), link access procedure - SDH (LAPS), and generic framing procedure(GFP).

HDLCThe HDLC is a general data link control procedure. When using the HDLC protocol, the systemencapsulates data services into HDLC-like frames as information bits and maps the frames intoSDH VC containers.

LAPSThe LAPS is also a data link control procedure. It is improved on the basis of the HDLC. TheLAPS complies with ITU-T X.86.

GFPThe GFP is currently the most widely applied general encapsulation and mapping protocol. Itprovides a general mechanism to adapt higher-layer client signal flows into the transport networkand can map the variable-length payload into the byte-synchronized transport path. Client signalscan be protocol data units (PDU-oriented, such as IP/PPP and Ethernet), block-code data (block-code oriented, such as FC and ESCON), or ordinary bit streams. The GPF protocol complieswith ITU-T G.7041.

The GFP defines the following two modes to adapt client signals:

l Frame-mapping GFP (GFP-F)The GFP-F is a PDU-oriented processing mode. It encapsulates the entire PDU into theGFP payload area and does not modify the encapsulated data. It determines whether to adda detection area for the payload area, depending on requirements.

l Transparent GFP (GFP-T)The GFP-T is a block-code (8B/10B code block) oriented processing mode. It extracts asingle character from the received data block and maps the character into the fixed-lengthGFP frame.

All Ethernet boards of the OptiX RTN 600 use the GFP-F mode to perform the encapsulationand mapping.

17.1.2 Virtual ConcatenationThe 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, there is a wastage ofa large amount of transmission bandwidth. To solve the problem, use the virtual concatenation



17-3

technology to concatenate many standard VC containers to a large VC container that adapts tothe rate of the Ethernet service.

The concatenation is defined in ITU-T G.707. There are two concatenation methods: contiguousconcatenation and virtual concatenation. Both methods provide concatenated bandwidth of Xtimes Container-N at the path termination.

Contiguous concatenation concatenates the contiguous C-4s in the same STM-N into an entirestructure to be transported. It maintains the contiguous bandwidth throughout the wholetransport. Virtual concatenation concatenates many individual VC containers (VC-12containers, 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 theindividual VCs, and recombines these VCs to a contiguous bandwidth at the end point of thetransmission.

In the case of the virtual concatenation, each VC container may be transported in different pathsand there may be a transport delay difference between VC containers. Hence, there aredifficulties in restoring the client signal. As virtual concatenation requires concatenationfunctionality only at the path termination equipment and it can flexibly allocate bandwidth,however, the widely applied concatenation technology is virtual concatenation.

Virtual concatenation is available in two types, virtual concatenation in a higher order path andvirtual concatenation in a lower order path. A higher order virtual concatenation VC-4-Xvprovides a payload area of X Container-4 (VC-4). The payload is mapped individually into Xindependent VC-4s. Each VC-4 has its own POH. Similarly, a lower order virtual concatenationVC-12-Xv provides a payload area of X Container-12 (VC-12). The payload is mappedindividually into X independent VC-12s. Each VC-12 has its own POH, as does the virtualconcatenation of VC-3s.

Physical channels formed by virtual concatenation are called VCTRUNKs and are also calledinternal ports of the Ethernet board. The Ethernet board does not support VC-4-Xv.

17.1.3 LCASThe link capacity adjustment scheme (LCAS) is applied on the basis of virtual concatenationand can improve the performance of virtual concatenation. The LCAS can dynamically adjustthe number of virtual containers for mapping required services to meet the bandwidthrequirements 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 withoutaffecting the availability of the existing service.

l If there are failed physical channels in virtual concatenation, the LCAS shields thesephysical channels. Other physical channels in virtual concatenation can transfer services.Hence, this prevents a situation where the failure of a single physical channel causesinterruption of services. After the failed physical channels are restored, they can transferservices.

17.2 AvailabilityThe Ethernet encapsulation and mapping feature requires support of the involved equipment andboards.


Feature Description


Issue 02 (2008-06-20)

Table 17-1 Availability of the Ethernet encapsulation and mapping feature


Mapping protocol (GFP,HDLC, and LAPS)

EFT4 (all the versions) IDU 610/620


Virtual concatenation EFT4 (all the versions) IDU 610/620


LCAS EFT4 (all the versions) IDU 610/620


17.3 Relation with Other FeaturesThe Ethernet service encapsulation, virtual concatenation, and LCAS technology do not havean impact on other features.

17.4 Realization PrincipleThis topic describes the realization principles of the encapsulation and mapping protocol of theEthernet service, the relevant virtual concatenation and LCAS technology.

17.4.1 Encapsulation and MappingThe 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 areencapsulated and mapped.



17-5

Structure of the GFP Frame

Figure 17-1 Structure of the GFP frame

Octet transmission order

12345

4-65535

1 2 3 4 5 6 7 8

n


Core header

Payload area

4

a) Frame size and transmission order

Core header

Payload area

16-bit payloadlength indicator

c-HEC(CRC-16)

Payloadheaders

(4-64 bytes)

Clientpayload

informationfield

Optionalpayload FCS

(CRC-32)

b) Field constituting a GFP client frame

A GFP frame consists of a core header and a payload area. The Idle frame does not have thepayload area.

The GFP core header includes the following fields:

l Payload length indicator (PLI)


Feature Description


Issue 02 (2008-06-20)

The PLI field represents the number of octets in the GFP payload area. The minimum valueof the PLI field in a GFP client frame is 4 octets. PLI values 0 to 3 are reserved for GFPcontrol frame usage.

l Core HEC (cHEC)The cHEC field protects the integrity of the contents of the core header by enabling bothsingle-bit error correction and multi-bit error detection.

The GFP payload area includes the payload header, client payload information field, and payloadframe check sequence. The payload header consists of the type, type HEC (tHEC), extensionheader 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 currentlydefined, user data frames (PTI = 000) and client management frames (PTI = 100).

l Payload FCS indicator (PFI)The PFI indicates the presence (PFI = 1) or absence (PFI = 0) of the payload FCS field.

l Extension header identifier (EXI)The EXI indicates the presence or absence of the extension header. When EXI = 0, thereis no extension header. This frame format applies to a logical point-to-point configuration.

l User payload identifier (UPI)The UPI identifies the type of the client frame.

Figure 17-2 GFP type field format


6

5 PTI PFI EXI

UPI

1 2 3 4 5 6 7 8 Octet transmission order7 6 5 4 3 2 1 0 Bit number

Bit number15 14 13 12 11 10 9 8

The tHEC field protects the integrity of the type field by enabling both single-bit error correctionand multi-bit error detection.

The extension header field and eHEC field are used to support special data link headertechnologies and are seldom used in actual situations.

Type of the GFP FrameThere 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 frameis a four-octet GFP control frame consisting of only a GFP core header. The Idle frame is intendedfor the GFP source adaptation process to facilitate the adaptation of the GFP octet stream to anygiven 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 managementframe. GFP client data frames are used to transport data from the client signal. GFP clientmanagement frames are used to transport information associated with the management of theclient signal or GFP connection. The type field of the client data frames uses the followingvalues:



17-7

l PTI = 100

l PFI = Payload specific

l EXI = Payload specific

l UPI = See Table 17-2.

Table 17-2 UPI values of the client management frame

UPI Value Usage

0000 00001111 1111

Reserved

0000 0001 Client signal fail (loss of client signal)

0000 0010 Client signal fail (loss of charactersynchronization)

0000 0011through1111 11110

Reserved for future use

Ethernet Frame EncapsulationThe Ethernet board adopts the GFP-F adaptation mode to encapsulate Ethernet frames into thecorresponding 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 maintainedand bit identification within octets is maintained.

Octets GFP frame

PLIcHECTypetHEC

GFP extension header

GFPpayload

2222

0-60

1 2 3 4 5 6 7 8 Bits1 2 3 4 5 6 7 8 Bits

Octets

Ethernet MAC frame

71662

4

PreambleStart of frame delimiter

Source Address (SA)Destination Address (DA)

Length/TypeMAC client data

PadFrame Check Sequence (FCS)

2. Calculate other fields of the GFP client data frame over the content of the payload.3. Scramble the core header and the payload area to maintain DC balance of the transported

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


Feature Description


Issue 02 (2008-06-20)

The decapsulation process is as follows:

1. Check for a correct cHEC, byte by byte in the payload of the virtual container. Once acorrect cHEC is detected, a GFP frame is found.

2. Check for subsequent GFP frames frame by frame according to the PLI in the GFP frameand discard Idle frames.

3. Descramble the payload area in the found GFP frame and extract the Ethernet MAC octetsfrom the destination address through the frame check sequence, inclusive.

17.4.2 Virtual ConcatenationThe virtual concatenation is realized using byte H4 or K4 as the virtual concatenation-specificmultiframe indicator and sequence indicator.

VC-4-Xv and VC-3-XvThe virtual container that is formed by a VC-4-Xv/VC-3-Xv can be mapped into X individualVC-4/VC-3s which form the VC-4-Xv/VC-3-Xv. Each VC-4/VC-3 has its own POH. The POHhas the same specifications as the ordinary VC-4 POH. The H4 byte in the POH is used for thevirtual 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 sourcecarries 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. TheMFI-2 uses H4, bit 1 to bit 4 in frame 0 (MFI-2 bits 1–4) and 1 (MFI-2 bits 5–8). Hence, theMFI-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 informationinto the frame according to the payload allocation sequence. The sink decides the sequence toextract the payload from the frames that form C-n-Xv according to the SQ. The SQ is transportedin bits 1 to 4 of the H4 bytes, using frame 14 (SQ bits 1-4) and 15 (SQ bits 5-8) of MFI-1.



17-9

Figure 17-3 VC-3-Xv/VC-4-Xv multiframe and sequence indicator

C-3-X/C-4-X

1 X

C-3-Xv/C-4-Xv

PO

HP

OH

Mul

tifra

me

(MF)

SQ = 0MFI-1 = 0MFI-2 = 0SQ = 0MFI-1 = 1MFI-2 = 0

PO

HP

OH


PO

HP

OH


HH

H

SQ = X-1

SQ = X-1

SQ = X-1

= 1= 0

= 0= 0X-1

= 15= 0

= 0= 15

X-1

= 15= 255

= 0= 0

X-1

With the MFI and SQ, the sink can correctly restore the position of each frame in the C-n-Xv toavoid 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-12swhich form the VC-12-Xv. Each VC-12 has its own POH. The POH has the same specificationsas the ordinary VC-12 POH. Bit 2 of the K4 byte in the POH is used for the virtual concatenation-specific frame count and sequence indicator.

Bit 2s of the K4 bytes in every 32 multiframes (one multiframe comprising four VC-12s) areextracted to form a 32-bit character string to express the frame count and sequence indicator.Bits 1–5 of the string express the frame count, whose value range is between 0 and 31. Thestructure formed by 32 multiframes has 128 frames. Hence, the resulting overall multiframe is1096 frames (= 512 ms) long. Bits 6–11 of the string express the sequence indicator. The framecount/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.

17.4.3 LCASThe LCAS realizes the capacity adjustment of the virtual container by exchanging the controlinformation between both the source and the sink side.

Control Information

Synchronization of changes in the capacity of the transmitter (So) and the receiver (Sk) isachieved by a control packet. Each control packet describes the state of the link during the next


Feature Description


Issue 02 (2008-06-20)

control packet. Changes are sent in advance so that the receiver can switch to the newconfiguration as soon as it arrives.

The control packet is transported in byte H4 (higher order path) or bit 2 of byte K4 (lower orderpath).

The control packet includes the following:

l MFI or frame countMFI is used for the VC-4-Xv/VC-3-Xv and the frame count is used for the VC-12-Xv. Bothare used to indicate the position of a multiframe. For the usage, see 17.4.2 VirtualConcatenation.

l SQSQ is used to indicate the position of a frame in the C-n-Xv. For the usage, see 17.4.2Virtual Concatenation.

l GIDThe GID is used for identification of the VCG. The GID bit of all members of the sameVCG has the same value. The VCG refers to a group of co-located member trail terminationfunctions that are connected to the same virtual concatenation link. The members of a VCGare the virtual containers that form the VCG. The VCG is equivalent to the generally spokenVCTRUNK.

l Control field (CTRL)The control field is used to transfer the link information from the source to the sink. It mustprovide the status of the individual member of the link.

Table 17-3 LCAS CTRL words

Command Remarks

FIXED This is an indication that this end uses fixed bandwidth (non-LCASmode).

ADD This member is about to be added to the group.

NORM Normal transmission

EOS End of sequence indication and normal transmission

IDLE This member is not part of the group or about to be removed.

DNU Do not use (the payload). The sink side reported FAIL status.

l CRC

The CRC check is performed on every control packet after it has been received, and thecontents rejected if the test fails.

l Member status field (MST)It reports the member status from the sink to the source. There are two states, OK and FAIL.

l Re-sequence acknowledge (RS-Ack) bitWhen a change of the status of the members in a VCG is detected at the sink side, anotification to the source has to be performed by toggling (that is, change from '0' to '1' orfrom '1' to '0') the RS-Ack bit.



17-11

The forward control packets from the source to the sink include the MFI, SQ, GID, CTRL, andCRC. The backward control packets from the sink to the source include the MST, RS-Ack, andCRC.

Capacity Adjustment Process

Figure 17-4 Capacity adjustment process (addition of a member)

Source (EOS) Source (new) Sink (new)

Ctrl=ADD

Ctrl=EOS

MST=OK

RS-AckCtrl=NORM

Source (EOS)

When a member is added to a VCTRUNK on the NMS, the LCAS capacity adjustment processis as follows:

1. The LCAS source assigns a sequence number (one larger than the currently highestsequence number) to the new member and sends a forward control packet with its CTRLword being ADD to the sink.

2. The LCAS sink performs continuity check for the new member. If the link of the newmember is normal, the sink sends a backward control packet in which MST = OK to thesource.

3. The LCAS source sends a forward control packet with its CTRL code being EOS to thesink for the new member, indicating that the SQ of the new member is the currently highestnumber in the VCG.

4. The LCAS sink sends the RS-Ack to the source to acknowledge the change of the SQ.5. 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 normallytransmitted but is not the one with the highest SQ.

6. Both the source and the sink use the new member to transport the payload.

Figure 17-5 Capacity adjustment process (deletion of a member)

Source(SQ>removedmember's SQ) Source(removed) Sink(removed)

Ctrl=IDLEMST=FAIL

RS-Ack

Ctrl=EOS/NORMRS-Ack

Sink(SQ>removedmember's SQ)

When a member is deleted from a VCTRUNK on the NMS, the LCAS capacity adjustmentprocess is as follows:


Feature Description


Issue 02 (2008-06-20)

1. The LCAS source sends a forward control packet with its CTRL code being IDLE to thesink for the deleted member.

2. The LCAS sink sets the status of the member to FAIL and sends a backward control packetin which MST = FAIL to the source and also sends the RS-Ack to acknowledge the changeof the SQ.

3. The LCAS source reallocates SQs for all the members whose SQ is higher than that of thedeleted member (SQ decremented successively by 1). It also sends a forward control packetwith its CTRL code being EOS or NORM to the sink to indicate the change of the SQ.

4. The LCAS sink sends the RS-Ack to the source to acknowledge the change of the SQ.5. Both the source and the sink do not use the deleted member to transport the payload.

Figure 17-6 Capacity adjustment process (one member link restored after a failure)

Source (link error) Sink

MST=FAILCtrl=DNU

...MST=OK

Ctrl=NORM

When a member link of a VCTRUNK is restored after a failure, the LCAS capacity adjustmentprocess is as follows:

1. On detecting that a member link is faulty, the LCAS sink sends a backward control packetin which MST = FAIL to the source.

2. The LCAS source sends a forward control packet with its CTRL code being DNU to thesink for the member, indicating that the member is temporarily unavailable.

3. If the original status of the member is EOS, the LCAS source sends a forward control packetwith its CTRL word being EOS to the sink for the member whose SQ is one lower thanEOS.

4. Both the source and the sink do not use the faulty link member to transport the payload.5. On detecting that the member link is restored, the LCAS sink sends a backward control

packet in which MST = OK to the source.6. 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.7. 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.8. Both the source and the sink use the restored member to transport the payload.



17-13

NOTE

l The LCAS source can adopt the Huawei mode or the standard mode to send the two control packets MSTand Rs-Ack. In the Huawei mode, the Rs-Ack is sent before the MST. In the standard mode, the MST issent before the Rs-Ack. You can set the mode on the NMS.

l The LCAS sink uses the trail signal fail (TSF) or the loss of multiframe (LOM) as a required condition todetermine whether a link is faulty. It uses the trail signal degraded (TSD) as an optional condition. For theVC-12, the TSD is the BIP_SD. For the VC-3, the TSD is the B3_SD_VC3. You can enable or disable theTSD on the NMS.

l When a member link is faulty, the LCAS performs a protection switching after a delay of time to preventthe situation where an NE simultaneously performs a protection switching like SNCP and deletes themember. You can set the delay time on the NMS.

l A VCG uses a member to transport payload some time after the member link is restored. You can set theWTR time on the NMS.

17.5 Planning GuideBefore you plan the Ethernet encapsulation and mapping features, obtain the information of theopposite equipment.

Procedure

Step 1 Plan the Ethernet encapsulation and mapping protocol.

Follow these two 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 thatyou adopt the GFP protocol.

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

Follow these four principles when planning VCTRUNKs:

l The capacity of VCTRUNKs should be determined by the actual bandwidth of the serviceneeds.

l Bind only the paths in a VC-4 if possible. If the paths of several VC-4s need to be bound,the VC-4s that have the same transmission path take priority.

l As each VC-4 of the Ethernet board can bind only VC-3 or VC-12, give priority to the VC-4swhose paths are already bound with the VC-12 or VC-3.

l As the VC-4-1 of the EFT4 board and EMS6 board can bind only VC-3 paths whereas theVC-4-2 can bind both VC-12 and VC-3 paths, give priority to the paths in the VC-4-1 ifVC-3 paths are to be bound.

Step 3 Plan the LCAS.

Follow these six principles when planning the LCAS:

l The LCAS at both sides must be enabled or disabled.

l If the LCAS is enabled at both sides, the used LCAS parameters at both sides must beconsistent.


Feature Description


Issue 02 (2008-06-20)

l If the opposite equipment is 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 atboth sides.

l It is recommended that you set the delay time to 2000 ms.

l It is recommended that you set the WTR time to 300 seconds.

l It is recommended that you disable the TSD.

----End

17.6 Configuring the Internal Port of the Ethernet BoardWhen 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 boardworks with the Ethernet board on the opposite side to realize the transmission of the Ethernetservices in the network.




l The EFT4 board supports VCTRUNKs 1–4, which are bound with PORTs 1–4 respectively.The EFT4 board does not support the setting of TAG attributes and network attributes.

l The EMS6 board supports VCTRUNKs 1–8. VCTRUNKs 1–8 determine the services tobe transmitted depending on information of the created Ethernet services.

The following procedures describe how to configure the internal port of an EMS6 board. TheEFT4 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 InterfaceManagement > Ethernet Interface from the Function Tree. Choose Internal Port.

Step 2 Set the encapsulation and mapping protocol used by the port.1. Click the Encapsulation/Mapping tab.2. Set Mapping Protocol and the protocol parameters.

3. Click Apply.

Step 3 Set the VC paths to be bound with the port.1. Click the Bound Path tab.



17-15

2. Click Configuration.The system displays the Bound Path Configuration dialog box.

3. In Configurable Ports, select a VCTRUNK as the port to be configured.4. In Available Bound Paths, set Level and Direction of the bound paths.5. Select required items in Available Resources and Available Timeslots and click

.6. Repeat Step 3.5 and bind other VCTRUNKs.7. Click OK.

Step 4 Configure the LCAS function for the port.1. Click the LCAS tab.2. Set the Enabling LCAS parameter and other LCAS parameters.


Feature Description


Issue 02 (2008-06-20)

3. Click Apply.

Step 5 Optional: Set the TAG attributes of the port.1. Click the TAG Attributes tab.2. Set the TAG attributes of the port.

3. Click Apply.

Step 6 Optional: Set the network attributes of the port.1. Click the Network Attributes tab.2. Set the network attributes of the port.

3. Click Apply.

----End



17-17


Mapping Protocol GFP, LAPS, HDLC GFP It is recommended that you use the defaultvalue.

Scramble Unscrambled,Scrambling Mode[X43+1]

Scrambling Mode[X43+1]

l This parameter specifies the scramblingpolynomial used by the mappingprotocol.


Set Inverse Valuefor CRC

Yes, No Yes l This parameter is valid only whenMapping Protocol is set to LAPS orHDLC.

l When this parameter is set to Yes, theFCS is the result after you perform anegation operation for the CRC.

l When this parameter is set to No, the FCSis the CRC.

Check Field Length FCS32, FCS16, No FCS32 l When this parameter is set to FCS32, a32-bit FCS is used.

l When this parameter is set to FCS16, a16-bit FCS is used.

l When the Ethernet board uses the GFPmapping protocol, this parameter can beset to FCS32 or No.

l When the Ethernet board uses the HDLCmapping protocol, this parameter can beset to FCS32 or FCS16.

l When the Ethernet board uses the LPASmapping protocol, this parameter can beset to FCS32.


FCS Calculated BitSequence

Big endian, Littleendian

l Big endian (GFP)

l Little endian(LAPS or HDLC)

l When this parameter is set to Bigendian, the least significant byte of theFCS is placed first and the mostsignificant byte is placed last.

l When this parameter is set to Littleendian, the most significant byte of theFCS is placed first and the leastsignificant byte is placed last.



Feature Description


Issue 02 (2008-06-20)


Extension HeaderOption

No, Yes No l This parameter specifies whether theGFP payload header contains theextension header and eHEC.


Configurable Ports VCTRUNKs VCTRUNK 1 This parameter specifies the VCTRUNKwhose VC paths are to be configured.

Available BoundPaths

- - Follow these principles to plan and set thisparameter:l The capacity of VCTRUNKs should be

determined by the actual bandwidthrequired by services.

l Bind only the paths in a VC-4 for aVCTRUNK if possible. If the paths inseveral VC-4s need to be bound, theVC-4s that have the same transmissionpath take priority.

l Each VC-4 of an Ethernet board can haveonly VC-3 paths or only VC-12 paths.Hence, when a VCTRUNK needs to bebound with VC-3 paths, select VC-3paths first from the VC-4 certain ofwhose VC-3 paths are already bound;when a VCTRUNK needs to be boundwith VC-12 paths, select VC-12 pathsfirst from the VC-4 certain of whoseVC-12 paths are already bound.

l As the VC-4-1s of the EFT4 board andEMS6 board support only VC-3 pathswhereas the VC-4-2s support both VC-12paths and VC-3 paths, give priority to thepaths in the VC-4-1 if a VCTRUNKneeds to be bound with VC-3 paths.

l Generally, bidirectional paths are bound.

Enabling LCAS Enabled, Disabled Disabled l This parameter specifies whether theLCAS function is enabled.

l The LCAS can dynamically adjust thenumber of virtual containers for mappingrequired services to meet the bandwidthrequirements of the application. As aresult, the bandwidth utilization ratio isimproved.



17-19


LCAS Mode Huawei Mode,Standard Mode

Huawei Mode l This parameter specifies the sequence inwhich the LCAS sink sends the MSTcontrol packet and Rs-Ack controlpacket.

l When this parameter is set to HuaweiMode, the LCAS sink first sends the Rs-Ack and then sends the MST.

l When this parameter is set to StandardMode, the LCAS sink first sends theMST and then sends the Rs-Ack.

l If the equipment on the opposite side isthird-party equipment and does notsupport the Huawei mode, it isrecommended that you set this parameterto Standard Mode. Otherwise, set thisparameter to Huawei Mode.

Hold Off Time (ms) 0, any integer that isin the range of 2000to 10000 and has astep of 100

2000 l When a member link is faulty, the LCASperforms switching after a delay of timeto prevent the situation where an NEsimultaneously performs a protectionswitching like SNCP and performs anLCAS switching. This parameterspecifies the duration of the delay.

l If the paths of the VCTRUNK areconfigured with protection, it isrecommended that you set this parameterto 2000 ms. Otherwise, set this parameterto 0.

WTR Time(s) 0 to 720 300 l When the time after a member link isrestored to normal reaches the set valueof this parameter, the VCG uses therestored member link.


TSD Enabled, Disabled Disabled l This parameter specifies whether theTSD is used as a condition for judgingwhether a member link is faulty. In thecase of the VC-12, the TSD refers to theBIP_SD; in the case of the VC-3, the TSDrefers to the B3_SD_VC3.



Feature Description


Issue 02 (2008-06-20)


Ingress Check Enabled, Disabled Enabled l This parameter specifies whether tocheck the incoming packets from the portaccording to the TAG attributes.



Tag Aware l When ports are configured with TAGflags, the ports process frames by usingthe methods provided in Table 17-4.

l If all the accessed services are frameswith the VLAN tag (tagged frames), setthis parameter to Tag Aware.

l If all the accessed services are frames thatdo not have the VLAN tag (untaggedframes), set this parameter to Access.


Default VLAN ID 1 to 4095 1 l This parameter is valid only when TAGis set to Access or Hybrid.



VLAN Priority 0 to 7 0 l This parameter is valid only when TAGis set to Access or Hybrid.


l When the VLAN priority is required todivide streams or to be used for otherpurposes, set this parameter according toactual situations. Generally, it isrecommended that you use the defaultvalue.



17-21


Port Type UNI, C-Aware, S-Aware

UNI l When this parameter is set to UNI, theport processes data frames according tothe tag attributes.

l When this parameter is set to C-Awareor S-Aware, the port does not processdata frames according to the tag attributesbut processes the data frames accordingto the way of processing QinQ services.

l In the case of QinQ services, set thisparameter to the default value because theNE automatically sets network attributesaccording to the operation type that is setwhen the QinQ services are created.

NOTE

l The Mapping Protocol and protocol parameters set for VCTRUNKs at one end of a transmission line mustbe the same as the Mapping Protocol and protocol parameters set for VCTRUNKs at the other end of thetransmission line respectively.

l The Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at one end of a transmission linemust be the same as the Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at the otherend of the transmission line respectively.

l The timeslots to which the paths bound with a VCTRUNK correspond must be the same at both ends of atransmission line.

Table 17-4 Methods used by ports to process data frames


How to Process

Tag Aware Access Hybrid

Ingress Taggedframe




Untaggedframe





Feature Description


Issue 02 (2008-06-20)


How to Process


Egress Taggedframe

The port transmits theframe.

The port strips the VLANtag from the frame andthen transmits the frame.

l If the VLAN ID in theframe is DefaultVLAN ID, the portstrips the VLAN tagfrom the frame and thentransmits the frame.

l If the VLAN ID in theframe is not DefaultVLAN ID, the portdirectly transmits theframe.

17.7 Maintenance GuideThis topic describes how to increase/decrease the VCTRUNK bandwidth, alarms and eventsrelevant to the Ethernet service encapsulation and mapping, and problems that occur frequentlyduring the application of the feature.

17.7.1 Dynamically Increasing/Decreasing the VCTRUNKBandwidth

When the LCAS function is enabled on an NE, you can dynamically increase or decrease theVCTRUNK-bound paths to increase or decrease the bandwidth. The operation does not affectservices.



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. SelectInternal 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. In Configurable Ports, select a VCTRUNK as the configurable port.2. In Available Bound Paths, set Level and Direction of the bound paths.



17-23

3. Select desired items in Available Resources and Available Timeslots and click

.

4. Repeat Step 4.3 and bind other VC paths.

Step 5 Optional: Dynamically decrease the VCTRUNK bandwidth.

1. Do not select the Display in Combination check box.

2. Select the VC paths to be deleted in Selected Bound Paths and click .

3. Repeat Step 5.2 to delete other VC paths.

Step 6 Click OK.

----End

17.7.2 Relevant Alarms and EventsWhen the encapsulation and mapping of the Ethernet service becomes abnormal, the systemreports corresponding alarms and abnormal events.

Relevant Alarmsl ALM_GFP_dCSF

The ALM_GFP_dCSF alarm indicates that the GFP client signal is lost. On detecting theGFP client management frame that indicates the loss of the client signal from the oppositestation, the board reports this alarm.

l ALM_GFP_dLFD


Feature Description


Issue 02 (2008-06-20)

The ALM_GFP_dLFD alarm indicates that the GFP frame is out of synchronization. Ondetecting that the GFP frame is in the out-of-synchronization state, the board reports thisalarm.

l FCS_ERRThe FCS_ERR alarm indicates a check error of the frame check sequence (FCS). If theFCS check on the received HDLC/LAPS/GFP frame encounters an error, the board reportsthis alarm.

l VCAT_LOAThe VCAT_LOA alarm indicates a loss of alignment of the virtual concatenation.

l VCAT_LOM_VC3The VCAT_LOM_VC3 alarm indicates a loss of multiframe of the virtual concatenationat the VC-3 level. On detecting a mismatch between byte H4 and the expected multiframesequence, the board reports this alarm.

l VCAT_LOM_VC12The VCAT_LOM_VC12 alarm indicates a loss of multiframe of the virtual concatenationat the VC-12 level. On detecting a mismatch between byte K4 and the expected multiframesequence, the board reports this alarm.

l VCAT_SQM_VC3The VCAT_SQM_VC3 alarm indicates a mismatch of SQ of the virtual concatenation atthe VC-3 level. On detecting a mismatch between the SQ of the member and the expectedSQ, the board reports this alarm.

l VCAT_SQM_VC12The VCAT_SQM_VC12 alarm indicates a mismatch of SQ of the virtual concatenation atthe VC-12 level. On detecting a mismatch between the SQ of the member and the expectedSQ, the board reports this alarm.

l LCAS_FOPRThe LCAS_FOPR alarm indicates that the protocol in the LCAS receive direction fails. Ifthe receive unit of the LCAS module of the board detects an abnormality that may causethe LCAS protocol to fail to negotiate or negotiate a wrong result, the board reports thisalarm.

l LCAS_FOPTThe LCAS_FOPT alarm indicates that the protocol in the LCAS transmit direction fails. Ifthe transmit unit of the LCAS module of the board detects an abnormality that may causethe LCAS protocol to fail to negotiate or negotiate a wrong result, the board reports thisalarm.

l LCAS_PLCRThe LCAS_PLCR alarm indicates that the bandwidth is partially lost in the LCAS receivedirection. In the receive direction of the VCTRUNK with the LCAS enabled, if the numberof paths that actually carry the payload is smaller than that of the configured paths but isnot 0, the board reports this alarm.

l LCAS_PLCTThe LCAS_PLCT alarm indicates that the bandwidth is partially lost in the LCAS transmitdirection. In the transmit direction of the VCTRUNK with the LCAS enabled, if the numberof paths that actually carry the payload is smaller than that of the configured paths but isnot 0, the board reports this alarm.

l LCAS_TLCR



17-25

The LCAS_TLCR alarm indicates that the bandwidth is totally lost in the LCAS receivedirection. In the receive direction of the VCTRUNK with the LCAS enabled, if the numberof paths that actually carry the payload is 0 but that of the configured paths is not 0, theboard reports this alarm.

l LCAS_TLCTThe LCAS_TLCT alarm indicates that the bandwidth is totally lost in the LCAS transmitdirection. In the transmit direction of the VCTRUNK with the LCAS enabled, if the numberof paths that actually carry the payload is 0 but that of the configured paths is not 0, theboard reports this alarm.

Relevant Abnormal Eventsl LCAS event: Adding a member succeeded

This abnormal event indicates that within the specified time (10 seconds), the memberadded into the VCTRUNK already carries traffic.

l LCAS event: Adding a member timed outThis abnormal event indicates that within the specified time (10 seconds), the memberadded into the VCTRUNK cannot carry traffic.

l LCAS event: Deleting a member succeededThis abnormal event indicates that within the specified time (10 seconds), the memberdeleted from the VCTRUNK does not carry traffic any longer.

l LCAS event: Deleting a member timed out and the member is forcedly deletedThis abnormal event indicates that within the specified time (10 seconds), the LCAS failsto enable the VCTRUNK to delete the member and as a result the local end forcedly deletesthe member.

l LCAS event: Bandwidth restoredThis abnormal event indicates that the member whose link is faulty starts to carry trafficagain.

17.7.3 FAQsThis topic lists the problems that occur frequently during the application of the Ethernetencapsulation and mapping feature.

Q: How does one calculate the theoretical bandwidth of a VCTRUNK for Ethernetservices?

A: Calculation formula: Bandwidth = Number of bound paths of the VCTRUNK x Payload rateof the binding granularity x Encapsulation efficiency of the encapsulation protocol

The payload rate of the VC-12 is 2.176 Mbit/s and that of the VC-3 is 48.384 Mbit/s. The GFPencapsulation efficiency equals the Ethernet frame length divided by the sum of the Ethernetframe length and an overhead of eight bytes. Hence, for the VCTRUNK that binds five VC-12s,when the transported Ethernet frame length is 1500 bytes, the theoretical bandwidth is 10.82Mbit/s; when the transported Ethernet frame length is 64 bytes, the theoretical bandwidth is 9.67Mbit/s.


Feature Description


Issue 02 (2008-06-20)

18 VLAN

About This Chapter

The Ethernet switching processing board supports the virtual local area network (VLAN)function that complies with IEEE 802.1q.

18.1 Feature DescriptionAccording to specific rules, a real network topology can be divided into several logicalsubnetworks, which are referred to as VLANs. The broadcast packets of a VLAN can betransmitted only within the range of this VLAN. That is, one VLAN corresponds to a specificbroadcast domain.

18.2 AvailabilityThe VLAN feature requires support of the involved equipment and boards.

18.3 Relation with Other FeaturesThe port whose VLAN feature is enabled cannot transparently transmit Ethernet services.

18.4 Realization PrincipleRealization of the VLAN function is related to the port attribute and service type.

18.5 Planning GuidePlan related parameters according to the specific application of VLAN.

18.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of theEVPL service that uses the VLAN feature. Two examples are provided as a supplement to theconfiguration.

18.7 Maintenance GuideThis topic describes alarms and performance events relevant to the VLAN feature, and problemsthat occur frequently during the application of the VLAN feature.

OptiX RTN 600 Radio Transmission SystemFeature Description 18 VLAN


18-1

18.1 Feature DescriptionAccording to specific rules, a real network topology can be divided into several logicalsubnetworks, which are referred to as VLANs. The broadcast packets of a VLAN can betransmitted only within the range of this VLAN. That is, one VLAN corresponds to a specificbroadcast domain.

18.1.1 PurposeA VLAN allows users to solve the broadcast flooding problem with a low cost. In addition, aVLAN offers several revolutionary benefits.

Improving Bandwidth UtilizationBecause the broadcast packets are forwarded within the range of a specific VLAN other than inthe entire LAN, a large number of unnecessary broadcast packets will not be generated. Thiseffectively improves the bandwidth utilization. In addition, because a VLAN is actually a smallbroadcast domain, if the routing of a packet is not discovered, the switch transmits this packetonly to other ports that belong to this VLAN other than to all ports of the switch. Hence, thepacket forwarding is restricted to a specific VLAN, which also improves the network utilization.

Isolating Users and Improving Network SecurityThe packets of a VLAN are forwarded within the range of this VLAN, and the packets are notforwarded to the network equipment of other VLAN users. Hence, using VLANs can isolatedifferent users and can realize the privacy of user information.

Realizing Virtual WorkgroupsThe final goal of using VLANs is to establish the virtual workgroup model, that is, to establisha dynamic organization environment. This enables the members of the same VLAN tocommunicate with each other as if they were in the same VLAN, even when they move to otherpositions of the network. The broadcast packets are restricted to this VLAN without affectingthe members of other VLANs. If the network location of one member is changed but the VLANthat the member belongs to is not changed, the configuration of this member does not requirechanging. If the physical location of one member is not changed but the VLAN that the memberbelongs to is changed, the network administrator needs to modify the configuration of thismember.

The virtual workgroup is a long-term goal, which requires support in other aspects.

18.1.2 Frame FormatTo realize the VLAN function, IEEE 802.1q defines the Ethernet frame that contains the VLANinformation, 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.1qheader.

18 VLANOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

Figure 18-1 Tagged frame format

Destinationaddress

Sourceaddress

802.1qheader Length/Type Data FCS

(CRC-32)

4 bytes

VID

12 bits

CFIPCPTPID

1 bit3 bits16 bits

TCI

The 4-byte 802.1q header is divided into two parts: tag protocol identifier (TPID) and tag controlinformation (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 valueis always 0x8100. When the network equipment that cannot identify the tagged framereceives the tagged frame, the equipment discards this frame.

l PCP

The priority code point (PCP) identifies the priority of an Ethernet frame. This field can beused to provide the requirement for the service quality.

l CFI

The CFI is a 1-bit filed, and it is used in certain physical networks that adopt the ringtopology. This field is not processed in the Ethernet.

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

18.1.3 TAG AttributeDepending 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.

Table 18-1 Data frame processing method of the switch port

Direction

Type ofFrame

Processing Method


Ingress Taggedframe

Receives the frame. Discards the frame. Receives the frame.

Untagged frame

Discards the frame. Receives the frameafter the untaggedframe is added withthe port VID (PVID).

Receives the frameafter the untaggedframe is added withthe PVID.



18-3

Direction

Type ofFrame

Processing Method


Egress Taggedframe

Transmits the frame. Transmits the frameafter the PVID of thetagged frame isstripped.

Transmits the frameafter the PVID of thetagged frame isstripped if the VIDequals the PVID.Directly transmitsthe frame if the VIDdoes not equal thePVID.

NOTE

l The untagged frame cannot be transmitted through the port.

l When the Ethernet switching board works in the Ethernet switching state, it can be considered as an Ethernetswitch. In this case, the ports of the Ethernet switching board can be classified into two categories: theexternal port (PORT) and the internal port (VCTRUNK). Each port corresponds to a specific TAG attribute.

l When the Ethernet switching board works in the Ethernet transparent transmission state, it does not checkthe TAG attribute. Hence, the port transparently transmits the tagged frame and untagged frame.

18.1.4 ApplicationA VLAN allows new application scenarios for the Ethernet private line (EPL) service andEthernet private LAN (EPLAN) service.

In the case of the EPL service, after the VLAN is adopted, the Ethernet board can divide theflow by port and VLAN ID other than only by port, which allows the development of the EPLservice to the Ethernet virtual private line (EVPL) service. In the case of the EPLAN service,after the VLAN is adopted, the Ethernet board can create the 802.1q bridge, which allows thedevelopment 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 the802.1q bridge, see 19.1.1 Bridge .

PORT-Shared EVPL ServiceFigure 18-2 shows an example of the PORT-shared EVPL service. The service between theheadquarters 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 whoseVIDs are from 200 to 210. If the Ethernet board at NE1 supports VLAN, use an Ethernet portwhose port attribute is tag aware to access the services from the headquarters. Then, map theservices of different VLANs into different VCTRUNKs. In this way, the services of differentVLANs are isolated during transmission.


Feature Description


Issue 02 (2008-06-20)

Figure 18-2 PORT-shared EVPL service

Headquaters

NE1 NE3

Branch A

VLAN100-110VLAN200-210

PORT1

Branch B

VCTRUNK2

VCTRUNK1

NE2

VLAN100-110

VLAN200-210

VCTRUNK-Shared EVPL ServiceFigure 18-3 shows an example of the VCTRUNK-shared EVPL service. Department A anddepartment B at NE1 need to transmit services to their respective departments at NE2. If theEthernet board supports VLAN, use two Ethernet ports at NE1 whose port attributes are accessand that have different PVIDs to access the services of department A and department B at NE1respectively. Then, map the services into the same VCTRUNK. In this way, the services ofdifferent VLANs are transmitted over the same VCTRUNK. Because the services of the twodepartments can share the bandwidth, the bandwidth utilization is improved.

Figure 18-3 VCTRUNK-shared EVPL service

NE1

VLAN100

VLAN200

PORT1

VCTRUNK1 NE2

PORT1

PORT2 PORT2

VLAN100

VLAN200

A

B

A

B

18.2 AvailabilityThe VLAN feature requires support of the involved equipment and boards.

Table 18-2 Availability of the VLAN feature


VLAN EMS6 (all versions) IDU 620

18.3 Relation with Other FeaturesThe port whose VLAN feature is enabled cannot transparently transmit Ethernet services.

18.4 Realization PrincipleRealization of the VLAN function is related to the port attribute and service type.



18-5

When the VLAN function is enabled, the switch processes a data frame as follows:

1. Processes the data frame that is input into the switch through a port, according to the portattribute of this port. For details, refer to Table 18-1.

2. 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.l 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 19.4.1 Bridge .3. Processes the data frame that is output from this port on the switch, according to the port

attribute of this port. For details, refer to Table 18-1.

18.5 Planning GuidePlan related parameters according to the specific application of VLAN.

PrerequisiteYou must learn about the specific application of VLAN.

PrecautionsNOTE

This topic describes the planning based on the cases in 18.1.4 Application.

Procedure

Step 1 According to the actual requirements, plan the line service type.

When planning the line service type, follow these four principles:

l In the case of the point-to-point service, use the Ethernet transparent transmission service.

l If the service of the same PORT needs to be divided by VLAN and if the service frame isthe tagged frame, use the PORT-shared EVPL service.

l If the services of different PORTs need to share one transmission channel and if the serviceframe is the untagged frame, use the VCTRUNK-shared EVPL service.

l In the case of other requirements that are not contained in the preceding description, use theQinQ service or Layer 2 switching service.

Step 2 Optional: Plan the PORT-shared EVPL service.

When planning the PORT-shared EVPL service, follow these two principles:

l Set TAG of the PORT to Tag Aware.

l 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, follow these three principles:

l Set TAG of the PORT to Access.


Feature Description


Issue 02 (2008-06-20)

l Because the PVIDs of different PORTs should be different, configure the PVIDs of PORTsby user. For example, if the PVIDs of the PORTs used by user A range from 100 to 199, thePVIDs of the PORTs used by user B should range from 200 to 299.

l The services of different PORTs should share one VCTRUNK.

----End

18.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of theEVPL service that uses the VLAN feature. Two examples are provided as a supplement to theconfiguration.

18.6.1 Configuration FlowThis topic describes the configuration flow of the EVPL service that uses the VLAN feature.

Figure 18-4 Configuration flow of the EPL service that uses the VLAN feature (PORT-sharedor VCTRUNK-shared EVPL service)

Start

1

Configure theEthernet internal port

2

End

Create the cross-connection of theEthernet service

4

Create theEthernet line service

3

Configure theEthernet external port



18-7

Table 18-3 Configuration flow of the EVPL service that uses the VLAN feature (PORT-sharedEVPL service)

Number Description

① l Set the TAG attributes of the PORT as follows:– Set TAG to Tag Aware.

– Set Ingress Check to Enabled.

l For the configuration process, see 16.6.1 Configuring the External Portof the Ethernet Board.

② l Configure one VCTRUNK corresponding to each data stream that is fromthe service of the PORT.

l Set the TAG attributes of the VCTRUNK as follows:– Set TAG to Tag aware.


l For the configuration process, see 17.6 Configuring the Internal Port ofthe Ethernet Board.

③ l Configure the EVPL service from the PORT+VLAN to the specifiedVCTRUNK.

l For the configuration process, see 18.6.2 Creating Ethernet LineService.

④ Create the cross-connection from the paths that are bound to the VCTRUNKto the corresponding timeslots on the line.

Table 18-4 Configuration flow of the EVPL service that uses the VLAN feature (VCTRUNK-shared EVPL service)

Number Description

① l Set the TAG attributes of the PORT as follows:– Set TAG to Access.

– Set Default VLAN ID of PORTs to different values.


l For the configuration process, see 16.6.1 Configuring the External Portof the Ethernet Board.

② l Configure a shared VCTRUNK. Set the TAG attributes of the VCTRUNKas follows:

l Set TAG to Tag aware.

l Set Ingress Check to Enabled.

l For the configuration process, see 17.6 Configuring the Internal Port ofthe Ethernet Board.


Feature Description


Issue 02 (2008-06-20)

Number Description

③ l Configure the EVPL service from the PORT to the specified VCTRUNK+VLAN.

l For the configuration process, see 18.6.2 Creating Ethernet LineService.

④ Create the cross-connection from the paths that are bound to the VCTRUNKto the corresponding timeslots on the line.

NOTE

If the QoS of the EVPL service needs to be set, see 20 QoS.

18.6.2 Creating Ethernet Line ServiceTo enable the Ethernet switching board to transmit the line service, perform certain operationsto configure the related information, such as the service source and service sink.

Prerequisitel The Ethernet switching board must be added in the slot layout.


Precautionsl This topic does not describe the method for creating the QinQ service.

l The OptiX RTN 600 supports the Ethernet switching board EMS6. The EFT4 board is anEthernet transparent transmission board, and the PORTs of the EFT4 board correspond toVCTRUNKs respectively. 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 > EthernetService > 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.



18-9

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 consistent withthe result of directly setting the Ethernet service port attributes.

Step 5 Click OK.

----End


Service Type EPL, EVPL (QinQ) EPL When creating the non-QinQ private lineservice, set this parameter to EPL.


Feature Description


Issue 02 (2008-06-20)



Bidirectional l When setting this parameter toUnidirectional, only create the servicefrom the service source to the servicesink. That is, the service source isforwarded only to the sink port.

l When setting this parameter toBidirectional, create the service from theservice source to the service sink and theservice from the service sink to theservice source. That is, when the servicesource is forwarded to the sink port, theservice sink is forwarded to the sourceport.

l Generally, it is recommended that youuse the default value.

Source Port A specific PORT orVCTRUNK

PORT1 l This parameter indicates the port wherethe service source resides.

l When creating the bidirectional Ethernetservice from a PORT to a VCTRUNK,use a specific PORT as the source port.

Source C-VLAN(e.g. 1,3-6)

1–4095 - l You can set this parameter to null, anumber, or several numbers. Whensetting this parameter to several numbers,use "," to separate these discrete valuesand use "–" to indicate continuousnumbers. For example, "1, 3–6" indicatesnumbers 1, 3, 4, 5, and 6.

l The number of VLANs set in thisparameter should be the same as thenumber of VLANs set in Sink C-VLAN(e.g. 1,3-6).

l When you set this parameter to null, allthe services of the source port work as theservice source.

l When you set this parameter to a non-nullvalue, only the services of the source portwhose VLAN IDs are included in the setvalue of this parameter work as theservice source.

Sink Port A specific PORT orVCTRUNK

PORT1 l This parameter indicates the port wherethe service sink resides.

l Do not set the value of this parameter tothe same as the value of Source Port.

l When creating the bidirectional Ethernetservice from a PORT to a VCTRUNK,use a VCTRUNK as the sink port.



18-11


Sink C-VLAN (e.g.1,3-6)

1–4095 - l You can set this parameter to null, anumber, or several numbers. Whensetting this parameter to several numbers,use "," to separate these discrete valuesand use "–" to indicate continuousnumbers. For example, "1, 3–6" indicatesnumbers 1, 3, 4, 5, and 6.

l The number of VLANs set in thisparameter should be the same as thenumber of VLANs set in Source C-VLAN (e.g. 1,3-6).

l When you set this parameter to null, allthe services of the sink port work as theservice sink.

l When you set this parameter to a non-nullvalue, only the services of the sink portwhose VLAN IDs are included in the setvalue of this parameter work as theservice sink.

Port Enabled Enabled, Disabled - When the source port or the sink port is setto a PORT, set Port Enabled to Enabled.


Tag Aware l When the accessed services are all frameswith the VLAN tag (tagged frames), setthis parameter to Tag Aware.

l When all of the accessed services are notframes with the VLAN tag (untaggedframes), set this parameter to Access.


18.6.3 Configuration Example (PORT-Shared EVPL Service)This topic provides an example to describe how to configure the PORT-shared EVPL service

PrecautionsNOTE

l For details about the service configured in this example, refer to the description of the PORT-shared EVPLservice in 18.1.4 Application.

l Because NE2 and NE3 in this example are both configured with the point-to-point EVPL service, this topiconly describes the configuration of NE1.


Feature Description


Issue 02 (2008-06-20)

Procedure

Step 1 Set the port attributes of PORT. See 16.6.1 Configuring the External Port of the EthernetBoard.

Set TAG attributes of PORT1 as follows:

l Set TAG to Tag Aware.


Step 2 Set the port attributes of VCTRUNK1 and VCTRUNK2. See17.6 Configuring the InternalPort of the Ethernet Board.

Set the TAG attributes of VCTRUNK1 and VCTRUNK2 as follows:

l Set TAG to Tag Aware.


Step 3 Configure the EVPL service between PORT1 and VCTRUNK1. See18.6.2 Creating EthernetLine Service.

Set the parameters as follows:

l Set Source Port to PORT1.

l Set Source C-VLAN (e.g.1,3-6) to 100–110.

l Set Sink Port to VCTRUNK1.

l Set Sink C-VLAN (e.g.1,3-6) to 100–110.

Step 4 Configure the EVPL service between PORT1 and VCTRUNK2. See 18.6.2 Creating EthernetLine Service.



l Set Source C-VLAN (e.g.1,3-6) to 200-210.


l 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 correspondingtimeslots on the line.

----End

18.6.4 Configuration Example (VCTRUNK-Shared EVPL Service)This topic provides an example to describe how to configure the VCTRUNK-shared EVPLservice.



18-13

PrecautionsNOTE

l For details about the service configured in this example, refer to the description of the VCTRUNK-sharedEVPL service in18.1.4 Application.

l Because the service configuration of NE1 is the same as the service configuration of NE2 in this example,this topic only describes the configuration of NE1.

Procedure

Step 1 Set the port attributes of PORT1. See 16.6.1 Configuring the External Port of the EthernetBoard.

Set the TAG attributes of PORT1 as follows:

l Set TAG to Access.

l Set Default VLAN ID to 100.


Step 2 Set the port attributes of PORT2. See 16.6.1 Configuring the External Port of the EthernetBoard.

Set the TAG attributes of PORT2 as follows:

l Set TAG to Access.

l Set Default VLAN ID to 200.





l Set Source C-VLAN (e.g.1,3-6) to 100.


l Set Sink C-VLAN (e.g.1,3-6) to 100.




l Set Source C-VLAN (e.g.1,3-6) to 200.


l Set Sink C-VLAN (e.g.1,3-6) to 200.


----End


Feature Description


Issue 02 (2008-06-20)

18.7 Maintenance GuideThis topic describes alarms and performance events relevant to the VLAN feature, and problemsthat occur frequently during the application of the VLAN feature.

18.7.1 Relevant Alarms and EventsThe VLAN feature may cause changes in RMON performance.

Relevant AlarmsNone.

Relevant Abnormal EventsNone.

Relevant RMON Performance EventsSee 22.1.3 List of RMON Alarm Entries and List of RMON Performance Entries.

18.7.2 FAQsThis 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 VLANtag 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 C-VLAN refers to the VLAN on the client side, and the S-VLAN refers to the VLAN at the servicelayer of operators. The VLAN that is commonly used equals the C-VLAN of the QinQ service.



18-15

19 Layer 2 Switching

About This Chapter

To realize the EPLAN service, the Ethernet switching and processing board can create one bridgeor multiple bridges. Each bridge can realize the Layer 2 switching of packets among mountedports and relevant features.

19.1 Feature DescriptionBy using the 802.1d or 802.1q algorithm, the Layer 2 switching can realize the packet switchingamong switch ports based on the MAC address of the packet. Features that are relevant to theLayer 2 switching contain VLAN, STP/RSTP, IGMP Snooping, broadcast packet suppression,and QoS.

19.2 AvailabilityThe Layer 2 switching feature requires support of the involved equipment and boards.

19.3 Relation with Other FeaturesThe Layer 2 switching has different relations with other features.

19.4 Realization PrincipleThe realization principles of bridge, STP/RSTP, and IGMP Snooping comply with the relevantIEEE standards.

19.5 Planning GuidePlan the relevant parameters of the Layer 2 switching service according to the actual situationof microwave links.

19.6 Configuration GuideThis topic describes the configuration tasks relevant to the Layer 2 switching feature.

19.7 Maintenance GuideThis topic describes the maintenance operations, alarms and performance events that are relatedto the Layer 2 switching, and problems that occur frequently during the application of the Layer2 switching.

OptiX RTN 600 Radio Transmission SystemFeature Description 19 Layer 2 Switching


19-1

19.1 Feature DescriptionBy using the 802.1d or 802.1q algorithm, the Layer 2 switching can realize the packet switchingamong switch ports based on the MAC address of the packet. Features that are relevant to theLayer 2 switching contain VLAN, STP/RSTP, IGMP Snooping, broadcast packet suppression,and QoS.

This topic describes the packet forwarding mechanism of the Layer 2 switching, STP/RSTP,IGMP Snooping, and broadcast packet suppression. For details about the VLAN and QoS, see18 VLAN and 20 QoS.

19.1.1 BridgeA bridge refers to a functional unit that realizes the interconnection of two or more LANs.

Bridge Type

The Ethernet switching board can create two types of bridges: 802.1d bridge and 802.1q bridge.

In the case of the 802.1d bridge, the services of different bridges are isolated, but the servicesof different VLANs within the same bridge are not isolated. In the case of the 802.1q bridge,the services of different bridges and the services of different VLANs within the same bridge areboth isolated.

Figure 19-1 802.1d bridge and 802.1q bridge

PORT

PORT

PORT

VLAN1

VLAN2

VLAN3

PORT

PORT

PORT

802.1q bridge

PORT

PORT

PORT

PORT

PORT

PORT

802.1d bridge

PORT

PORT

PORT

PORT

PORT

PORT

VLAN1VLAN2VLAN3

. . .

Table 19-1 Comparison between the 802.1d bridge and the 802.1q bridge

802.1d Bridge 802.1q Bridge

VLAN filter table Not configured. Must be configured.

Ingress filter Does not check the VLANtag.

Checks the VLAN tag. If theVLAN ID does not equal theVLAN ID of the port definedin the VLAN filter table, thepacket is discarded.

MAC address learning mode SVLa IVLb

19 Layer 2 SwitchingOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

802.1d Bridge 802.1q Bridge

Packet forwarding method Obtains the packetforwarding port by queryingthe MAC address table,according to the destinationMAC address of the packet.

Obtains the packetforwarding port by queryingthe MAC address table,according to the destinationMAC address and VLAN IDof the packet.

Range of broadcasting Forwards the broadcastpacket to all the ports withina bridge.

Forwards the broadcastpacket to the ports that arespecified in the VLAN filtertable.

Mounted port attribute Tag aware or access Tag aware, access, or hybrid

NOTE

l a: When the bridge uses the shared VLAN learning (SVL) mode, it creates an entry according to the sourceMAC address and the source port of a packet. This entry is applicable to all VLANs.

l b: When the bridge uses the independent VLAN learning (IVL) mode, it creates an entry according to thesource MAC address, VLAN ID, and source port of a packet. This entry is applicable only to this VLAN.

MAC Address Table

Entries of a MAC address table provide the mapping relations between MAC addresses andports. 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 entryages, and is lost after the Ethernet switching board is reset.

l Static entry

A static entry, which corresponds to a specific MAC address and port, is manually addedby the network administrator into the MAC address table on the NM. A static entry is alsocalled a unicast entry. The static entry does not age, and is not lost after the Ethernetswitching board is reset.

l Blacklist entry

A blacklist entry is used to discard the data frame that contains the specified destinationMAC address, that is, the MAC disabled entry. A blacklist entry is also called a blackholeentry. The blackhole entry is configured by the network administrator. The blackhole entrydoes not age, and is not lost after the Ethernet switching board is reset.

NOTE

l If one routing entry is not updated in a certain period, that is, if no new packet from this MAC address isreceived to enable the re-learning of this MAC address, this routing entry is automatically deleted. Thismechanism is called aging, and this period is called aging time. The aging time of a MAC address table is5 minutes by default. You can set this value on the NM.

l The number of entries in a MAC address table is limited. The MAC address capacity of each bridge in thecase of the Ethernet switching board is 16K.



19-3

Hub/SpokeIn the case of the convergence service, the mutual access between the non-central stations andcentral stations is required but the access between non-central stations is not required. In thiscase, specify a mounted port as a Hub port or a Spoke port.

l Hub portHub ports can mutually access each other. Hub ports and Spoke ports can mutually accesseach other.

l Spoke portSpoke ports cannot mutually access each other. Hub ports and Spoke ports can mutuallyaccess each other.

A mounted port is a Hub port by default.

19.1.2 STP/RSTPWhen the network topology of the Ethernet service forms loops, enable the STP or RSTP.

STPThe spanning tree protocol (STP) is used in the looped network. This protocol realizes the routingredundancy by adopting certain algorithms and releases the looped network into loop-free treenetwork, thus preventing the packets from increasing and cycling in an endless manner in thelooped network.

The STP meets the following requirements:

l Configures any activated topology of any bridge to a single spanning tree, and releases theredundant data loop if there is any between two stations in the network topology.

l Re-configures the spanning tree topology in the case of a bridge fault or an interruptedroute, thus providing a certain protection, and prevents temporary data loops byautomatically containing the bridges and ports of the bridges that are newly added into theLAN.

l Stabilizes the activated topology in a rapid manner.

l The finally activated topology can be predicted and repeated. In addition, the topology canbe selected by managing the parameters of certain algorithms.

l Operations to the end stations are transparent. For example, the end stations are unawareof their attachment to a single LAN or a bridged LAN.

l A small part of the available bandwidth of the link is used to create or maintain the spanningtree, and the bandwidth does not increase with the expanding network size.

The Ethernet switching board supports the STP, which complies with IEEE 802.1d.

RSTPThe 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 theSTP. These two topologies can be identified by the bridge that uses the RSTP for calculatingthe spanning tree.

The Ethernet switching board supports the RSTP, which complies with IEEE 802.1w.


Feature Description


Issue 02 (2008-06-20)

19.1.3 IGMP SnoopingIf the multicast router exists in the network, enable the IGMP Snooping for the bridge to realizethe multicast function with the cooperation of the router.

Multicast Protocol

The multimedia network applications, such as video conference, E-learning, and video ondemand (VOD) service, require that the information is transmitted from one source to multipledestinations, that is, transmitted in one-to-many transmission mode. Because the data traffic ofthe multimedia information is large, simulating the one-to-many transmission through one-to-one mode occupies a large volume of bandwidth. In addition, information flooding is generatedif 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 D-type IP address that is similar to the unicast address to indicate a group. When the packet istransmitted to all the IP hosts in a multicast group, the calling and access mode is similar to thecalling and access mode of the unicast. The hosts in an IP multicast group can join or quit thismulticast group at any time and at any location, with the unlimited number of members. Themulticast router does not store the member relations of all the hosts. The router stores theinformation only about whether any host in the physical subnetwork on the physical interfacebelongs to a specific multicast group. The host stores the information only about the multicastgroups that it joins.

The IP multicast protocol is classified into two categories: communication protocol among themulticast 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 routinginformation. This type of protocol contains the protocol independent multicast-dense mode(PIM-DM), protocol independent multicast-sparse mode (PIM-SM), and distance vectormulticast routing protocol (DVMRP).

l The protocol among the multicast routers, hosts, and Layer 2 switches is used to forwardthe multicast packet according to the multicast routing information. This type of protocolcontains the Internet group management protocol (IGMP), IGMP Snoop, IGMP Proxy, andCisco group management protocol (CGMP). IGMP is a Layer 3 multicast protocol, andIGMP 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 itsadjacent multicast router.

The host notifies the local router of joining a specific multicast group and of accepting theinformation from this multicast group through this protocol. The router periodically querieswhether 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 thuscollects and maintains the member relations of groups that are connected to the router. By usingthis mechanism, the multicast router establishes a table, which contains the ports of the routerand members of each specific group in the subnetworks corresponding to each port. Whenreceiving the packet of a specific group, the router forwards the packet only to these ports thathave the members of this group.



19-5

The router uses the IP multicast address to forward multicast packet. Each multicast groupcorresponds 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 SnoopingWhen the multicast router is connected to the host by using the bridge, the switch broadcasts themulticast packet at Layer 2 if the bridge disables the Layer 2 multicast protocol. See Figure19-2. When the multicast router is connected to the host by using the bridge, if the bridge enablesthe Layer 2 multicast protocol (such as IGMP Snooping), the bridge can establish the mappingrelations between groups members and switch ports and thus can forward the packet only to theports that have group members.

Figure 19-2 Transmission of the multicast packet (with IGMP Snooping disabled)

Internet/Intranet

VOD server

Video stream

Multicastgroup member

Non-multicastgroup member


Video stream

Videostream

Videostream

Videostream

Layer 2 Ethernet switch

Multicast router

Figure 19-3 Transmission of the multicast packet (with IGMP Snooping enabled)

Internet/Intranet

VOD server

Video stream

Multicastgroup member



Video stream

Videostream

Layer 2 Ethernet switch

Multicast router

The IGMP Snooping creates and maintains the mapping relations between group members andswitch ports by sensing the IGMP packet. After the IGMP Snooping is enabled, the bridgeconsiders the port that receives the IGMP request as the router port. When detecting the response


Feature Description


Issue 02 (2008-06-20)

that is transmitted to the router port, the bridge adds the port that receives the response and therouter port into a specific multicast group. When detecting that a certain port in a multicast groupdoes not respond to the IGMP request for consecutive times and that the times exceed thethreshold, the bridge deletes this port from the multicast group.

After the IGMP Snooping is enabled, when receiving the multicast packet, the bridge queriesthe multicast table in which the source port is the router port. If a multicast group that matchesthe multicast address exists in the multicast table, the bridge forwards the packet to this multicastgroup. If no multicast group exists, the bridge discards the multicast packet or broadcasts thepacket depending on the NM setting.

Three versions of IGMP requests are available, and they are, V1, V2, and V3. The Ethernetswitching board can process versions V1 and V2. The Ethernet switching board also supportsthe aging of the router port and multicast table item.

NOTE

l If a router port is not updated in a certain period (that is, no IGMP request from this port is received), all themulticast tables that are related to this router port are deleted. This mechanism is called aging, and this periodis called aging time. The aging time of a router port is 5 minutes by default. You cannot set this value onthe NM.

l Similarly, the multicast table item (that is, multicast group) ages. The aging time is 8 minute by default. Youcan set this value on the NM.

19.2 AvailabilityThe Layer 2 switching feature requires support of the involved equipment and boards.

Table 19-2 Availability of the Layer 2 switching feature


Bridge (802.1q bridge and802.1d bridge)

EMS6 (all versions) IDU 620

STP/RSTP

IGMP Snooping

19.3 Relation with Other FeaturesThe Layer 2 switching has different relations with other features.l The port that is used by the bridge cannot be configured with the line service.

l The STP/RSTP is applicable only to the bridge.

l The IGMP Snooping is applicable only to the bridge.

l The broadcast packet suppression function is applicable only to the PORT on the bridge.

l The port on the bridge supports the QoS function.



19-7

19.4 Realization PrincipleThe realization principles of bridge, STP/RSTP, and IGMP Snooping comply with the relevantIEEE standards.

19.4.1 BridgeA 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 atthe port. If the VLAN ID of this frame does not equal the VLAN ID of the port that isdefined in the VLAN filter table, the bridge discards this frame.

2. If the broadcast packet suppression function of the bridge port is enabled and the traffic ofthe broadcast packet exceeds the pre-set threshold value, the port discards the receivedbroadcast frame.

3. If the IGMP Snooping protocol of the bridge is enabled, the bridge processes the IGMPpacket and multicast packet that are received at the port, according to the principle describedin 19.4.3 IGMP Snooping.

4. If the bridge receives the multicast packet but the IGMP Snooping protocol is disabled, itforwards the multicast packet among all the ports of the bridge or among all the mountedports of the VLAN (excluding the source port).

5. According to the learning mode, the bridge adds or updates the entry corresponding to thesource MAC address of the data frame in the MAC address table, and thus establishes themapping relation between the MAC address and the receive port.

6. The bridge checks the MAC address table according to the destination MAC address of thedata frame.

l If the blacklist entry corresponding to the destination MAC address exists, the bridgediscards this data frame.

l If the dynamic entry or the static entry corresponding to the destination MAC addressexists, the bridge forwards this data frame to the destination port indicated by the entry.

l If no corresponding entry exists, the bridge forwards the packet among all the ports ofthe 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 orSpoke when forwarding the data frame. If the source port is the Hub port, the bridgeforwards 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.

19.4.2 STP/RSTPThe realization of the STP complies with IEEE 802.1d, and the realization of the RSTP complieswith IEEE 802.1w.


Feature Description


Issue 02 (2008-06-20)

Basic Conceptsl Bridge protocol data unit (BPDU)

The STP transmits the BPDU among pieces of equipment to determine the networktopology. The BPDU contains adequate information that is required to implement thecalculation 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 maintainthe 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 thenetwork topology change in the case of topology change.

l Bridge IDThe bridge ID is used to indicate a bridge. The bridge ID is 64-bit long. The most significant16 bits indicate the priority of the bridge, and the least significant 48 bits indicate the MACaddress of a certain bridge port. In the STP, the bridge ID also indicates the priority of thebridge. The smaller the value of the bridge ID, the higher the priority.

l Port IDThe port ID is used to indicate a port on the bridge. The port ID is 16-bit long. The mostsignificant eight bits indicate the priority of the port, and the least significant eight bitsindicate the port number. In the STP, the port ID also indicates the priority of the port. Thesmaller the value of the port ID, the higher the priority.

l Root bridgeIn a network that enables the STP, only one root bridge exists. The root bridge is selectedbased on the running of the STP. The bridge with the smallest bridge ID is selected as theroot bridge. When a network that enables the STP is stabilized, only the root bridgegenerates 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 rootbridge may also change.

l Root portThe root port refers to a port on the bridge that transmits/receives frames to/from the rootbridge. Each non-root bridge has only one root port. The root port is selected based on therunning of the STP. The port of a bridge whose root path cost is the smallest is selected asthe root port. If more than one port whose root path cost is the smallest exist, the port withthe smallest port ID is selected as the root port.

l Designated portThe designated port refers to a port of a LAN that transmits/receives frames to/from theroot bridge. Each LAN has only one designated port. The designated port is selected basedon the running of the STP. The port that is connected to the LAN and whose root path costis the smallest is selected as the designated port. If more than one port whose root path costis the smallest exist and if these ports are on different bridges, the port whose bridge ID isthe smallest is selected as the designated port. If more than one port whose root path costis the smallest exist and if these ports are on the same bridge, the port with the smallest portID is selected as the designated port.

l Path costThe path cost is used to indicate the status of the network that is connected to the port. Thehigher the rate of the port, the smaller the path cost.



19-9

l Root path costThe root path cost refers to the cost of the path from a certain port to the root bridge, thatis, the sum of path cost of all the passed ports from this port to the root bridge.

l Port stateIn 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 theBPDU. When a port is in the blocking state, it does not learn the MAC address and doesnot forward the user packet.

– ListeningIt is a transitional state. A port in the listening state transmits, receives, and processesthe BPDU. When a port is in the listening state, it does not learn the MAC address anddoes not forward the user packet.

– LearningIt is a transitional state. A port in the learning state transmits, receives, and processesthe BPDU. When a port is in the learning state, it learns the MAC address but does notforward the user packet.

– ForwardingA port in the forwarding state transmits, receives, and processes the BPDU. When aport is in the learning state, it learns the MAC address and forwards the user packet.

– DisabledA port in the disabled state does not forward frames, and does not implement thespanning tree algorithm and STP.

l TimerPort timers are classified into the following categories:– Hold timer

The hold timer is used to measure the interval between two CBPDU transmissions. Thetimeout value is the Hold Time of the bridge.

– Message age timerThe message age timer is used to measure the age of the CBPDU packet recorded by aport. When the age of the CBPDU packet stored by the bridge exceeds the Message Ageparameter, the bridge discards the packet. The Message Age parameter determines theinitialization age when the CBPDU packet is stored in the bridge. The Message Ageparameter is 0 when the root bridge generates the packet. Each time the packet isforwarded to a port, a fixed increment value is added to the Message Age parameter.

– Forward delay timerThe forward delay timer is used to measure the holding time of a port in the listeningstate and in the learning state. When the listening state remains for a period that is thesame 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 ForwardDelay 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 CBPDUpacket. The timeout value is the Bridge Hello Time of the bridge.


Feature Description


Issue 02 (2008-06-20)

– Topology change notification timer

The topology change notification timer indicates the duration when the bridgeperiodically transmits the TCN. The timer is used to notify the designated bridge in theLAN that is attached to the root port of the bridge of any detected topology change. Thetimeout 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 TCNafter the topology change is complete and the time period indicated by the topologychange 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 unifiedto the values of these three parameters that are used by the root bridge, by mutually transmitting theCBPDU.

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 thiscase, each port generates the CBPDU, and the CBPDU considers the bridge where the portresides as the root bridge and the root path cost of the CBPDU is 0. Each port transmits theCBPDU periodically, and the period is the Hello Time of the bridge.

2. The bridge compares the information about the CBPDU that is received at the port withthe 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. Thesmaller the root path cost, the better.

(3) If the root path cost values are the same, the bridge compares the designated bridgeIDs. The smaller the designated bridge ID, the better.

(4) If the designated bridge IDs are the same, the bridge compares the designated portIDs. 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 replacesthe information about the CBPDU that is originally stored by the port. If the root bridge IDor the root path cost in the information about the CBPDU that replaces the informationabout the CBPDU originally stored by the port, the bridge needs to process the newinformation as follows:

l The bridge stores the information about the CBPDU (including the root bridge ID, rootpath cost, message age, and corresponding timers).

l The bridge updates the root bridge ID and root path cost (the root path cost of the bridgeequals the sum of the root path cost of the port that stores the packet and the root pathcost of the port that receives the CBPDU).

l The designated port updates the designated root bridge and the root path cost at the sametime (the root path cost of the designated port equals the sum of the root path cost ofthe bridge and the path cost of the port).

l The designated port relays the CBPDU.



19-11

If the information about the CBPDU that is received at the port is worse than the informationabout the CBPDU that is stored by the port, the port transmits the CBPDU that is stored asa response.

4. If the bridge maintains a root bridge ID that is the same as its bridge ID and if the root pathcost is 0, the bridge is a root bridge. The root bridge sets the path cost of each port to 0.

5. If the bridge is a non-root bridge, it considers the port that receives the best CBPDUinformation as the root port.

6. If the bridge is a non-root bridge, it considers any of the following ports as the designatedport:l The bridge ID and port ID of the port are the same as the designated bridge ID and port

ID that are recorded by the port respectively.l The root bridge ID that is recorded by the port is different from the root bridge ID of

the bridge.l The root path cost 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 that is recorded by the port.l The root path cost of the port is the same as the root path cost that is recorded by the

port, but the bridge ID is smaller than the designated bridge ID of the port.l The root path cost of the port is the same as the root path cost that is recorded by the

port, and the bridge ID is the same as the designated bridge ID of the port. The port ID,however, is smaller than the designated ID of the port.

7. When the Forward Delay parameter set for the listening state timer of the port expires, thestates of the root port and the designated port transition to learning. When the learning stateremains for a period that is the same as the value of the Forward Delay parameter, the statesof the root port and the designated port transition to forwarding. The states of these portswhose states are not changed to forwarding transition to blocking.

8. If a trail becomes faulty, the root port on this trail no longer receives new CBPDUs, andtherefore, the original CBPDU is discarded due to timeout. In this case, the calculation ofthe spanning tree is conducted again, and a new trail will be available to replace the faultytrail, thus restoring the connectivity of the network.

Improvement in the RSTPCompared with the STP, the RSTP is improved as follows:

l Classification of port rolesThe port roles in the RSTP are classified into the following categories: root port, designatedport, alternate port, and backup port. The alternate port refers to a port that is in the blockingstate due to the learning of the BPDU transmitted by other bridges. The backup port refersto a port that is in the blocking state due to the learning of the BPDU transmitted by thebridge the port resides.

l Classification of port statesThe blocking, listening, and disabled states are combined into the discarding state in theRSTP.

l Rapid transition of port statesTo support the rapid transition of port states, the RSTP defines the point-to-point attributeof 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


Feature Description


Issue 02 (2008-06-20)

determines the actual point-to-point attribute of the port according to the actual workingmode of the port. If the actual working mode of the port is full-duplex, the actual point-to-point attribute of the port is "true". If the actual working mode of the port is half-duplex, the actual point-to-point attribute of the port is "false". If the point-to-pointattribute of a port is set to shared media, the actual point-to-point attribute of the portis "false". If the point-to-point attribute of a port is set to link connection, the actualpoint-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 setto 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 an designated port, the port can realize the rapid statetransition.

The rapid transition among port states can be classified into the rapid port state transitionof the root port, rapid port state transition of the designated port, and the rapid port statetransition 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 periodthat is less than double times of the Hello Time) transition to the forwarding state withouta delay, and this root port enables the designated port that functions as the root portrecently (that is, in a recent period that is less than Forward Delay) to transition to thediscarding 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 statewithout a delay. The designated port whose actual point-to-point attribute is "true" canrealize the rapid transition among port states through rapid switching between therequest 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 statewithout a delay.

19.4.3 IGMP SnoopingThe IGMP Snooping establishes and creates the mapping relations between the group membersand switch ports by sensing the IGMP packet. This ensures that the multicast packet istransmitted only to the ports that are connected to the multicast users.

Basic Conceptsl Router port

The router port refers to a port that connects to a multicast router.

l Multicast member port

The multicast member port refers to a port that connects to a multicast group member. Themulticast group member refers to a host that joins a multicast group.

l Multicast group

The multicast group records the mapping relations among the router ports, MAC multicastaddresses, and multicast group members. A multicast group is also called a multicast tableitem.



19-13

l Maximum query response time

When transmitting the IGMP specific query packet to the multicast member port, the 802.1qbridge starts the maximum query response timer. If the bridge does not receive the IGMPresponse packet within the maximum query response time, the bridge adds one to the no-response times of the port. When the no-response times of the port exceeds the pre-setthreshold, 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 routerto the multicast group members. The IGMP general query packet is used to query whichmulticast groups have members.

l IGMP specific query packet

The IGMP specific query packet refers to a packet that is transmitted by a multicast routerto the multicast group members. The IGMP specific query packet is used to query whetherspecific multicast groups have members.

l IGMP report packet

The IGMP report packet refers to a report packet that is transmitted by a host to a multicastrouter. The IGMP report packet is used to apply for the joining of a multicast group or torespond 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 bridgeprocesses this packet as follows:

(1) The bridge checks whether the port that receives the packet is already learnt as therouter port.

(2) If this port is already learnt, the bridge re-sets the aging time of the router port. If thisport is not learnt, the bridge records the port as the router port and starts the agingtimer of the port.

(3) If the received packet is the IGMP specific query packet and the port that receives thispacket is already recorded as the router port, the bridge broadcasts this packet in thespecific multicast group and starts the timer for the maximum query response time ifthe multicast group that is specified in this packet exists. Otherwise, the bridgebroadcasts 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 domainof the 802.1q bridge.

(2) If this multicast record is not learnt and if the multicast group does not exist, the bridgecreates the multicast group and establishes the mapping relations among the routerports, MAC multicast addresses, and multicast group members by considering thisport as the multicast member port. If this multicast record is not learnt and this port isnot contained in the multicast member ports of the multicast group, the multicast groupadds this port as the multicast member port. If this multicast record is learnt, the bridgere-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 The bridge queries the multicast table that uses the router port as the source port.


Feature Description


Issue 02 (2008-06-20)

l If a multicast group that matches the multicast address exists in the multicast table, thebridge forwards the packet to this multicast group.

l If no multicast group exists, the bridge discards the multicast packet or broadcasts thepacket in the VLAN range depending on the NM setting.

4. The bridge processes the aging as follows.

l If the aging time of the router port times out, the bridge deletes this router port andrelevant multicast group record.

l If the maximum query response time times out, the bridge adds one to the no-responsetimes of the multicast member.

l If the no-response times of a multicast member exceeds the threshold, the bridge deletesthis multicast member port.

l If a multicast group does not have any multicast member port, the bridge deletes thismulticast group.

The 802.1d bridge processes the IGMP Snooping similarly. The difference is as follows: The802.1d learns the packet by using the SVL mode other than using the IVL mode, and the 802.1dbridge 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 Ethernetswitching 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 themulticast group.

l Supports the specific query packet.

This packet allows broadcasting the IGMP query packet in the specific multicast group.

19.5 Planning GuidePlan the relevant parameters of the Layer 2 switching service according to the actual situationof microwave links.

Prerequisite

You must learn the situation of microwave links.

Procedure

Step 1 Plan the bridge.

Follow these two 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 userare not known and if the user does not require the isolation of the data among VLANs, youcan also use the 802.1d bridge.



19-15

l If the Layer 2 switching services from several branch nodes are converged at a convergencenode, set this convergence node to Hub and set these branch nodes to Spoke. In the case ofthe multipoint-to-multipoint Layer 2 switching service, set each node to Hub.

Step 2 Plan the MAC address table.

Follow these three principles when planning the MAC address table:

l If the node that only receives data frames exists in the network, configure the correspondingVLAN unicast entry.

l If certain nodes are not allowed to transmit data frames, configure the corresponding MACdisabled entries for the bridge that accesses these nodes.

l Set the aging time of the MAC address table to the same value as the aging time of theinterconnected Ethernet equipment. It is recommended that you set the aging time of theMAC address table to 5 minutes (default value).

Step 3 Plan the STP/RSTP.

Follow these four principles when planning the STP/RSTP:

l In the service networking process, it is recommended that you prevent the loop from formingin the case of the Layer 2 service and thus avoid enabling the STP or RSTP.

l 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 Ethernetequipment. It is recommended that you use the RSTP.

l The bridge priority, port priority, and port path cost should be set according to the requirementof the interconnected Ethernet equipment. Unless otherwise specified, use the default values.

l The Max Age, Hello Time, and Forward Delay parameters should be set to the same valuesas these parameters of the interconnected Ethernet equipment. Unless otherwise specified,use the default values.

Step 4 Plan the IGMP Snooping protocol.

Follow these two principles when planning the IGMP Snooping protocol:

l If the IGMP multicast router exists in the interconnected Ethernet network, enable the IGMPSnooping protocol according to the requirement of the router. Otherwise, do not enable theIGMP Snooping protocol.

l Set the processing method for the unknown multicast packet and multicast aging timeaccording to the requirement of the IGMP multicast router. It is recommended that you usethe default values.

----End

19.6 Configuration GuideThis topic describes the configuration tasks relevant to the Layer 2 switching feature.

19.6.1 Creating the Ethernet LAN ServiceTo enable the Ethernet switching board to transmit the LAN service, perform certain operationsto create the bridge and set the attributes of the bridge and to configure the mounted ports of thebridge.


Feature Description


Issue 02 (2008-06-20)

Prerequisitel The Ethernet switching board must be included in the slot layout.


Precautions

The OptiX RTN 600 supports the Ethernet switching board EMS6.

Procedure

Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > EthernetService > 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.



19-17

Step 4 Configure the mounted ports of the bridge.1. Click Configure Mounted Port....

The VB Mount Port Configuration dialog box is displayed.2. Select a port from the ports listed in Available Mounted Ports, and then click

.3. Repeat Step 4.2 to select other mounted ports.


Feature Description


Issue 02 (2008-06-20)

4. Click OK.

Step 5 Optional: If any VCTRUNK is mounted to the VB, configure the VC paths that are bound tothe VCTRUNK.1. Click Configuration.

The Bound Path Configuration dialog box is displayed.2. In Configurable Ports, select a VCTRUNK as the configurable port.3. In Available Bound Paths, set Level and Direction of the bound paths.4. Select required items in Available Resources and Available Timeslots and click

.5. Repeat Step 5.4 to bind other VC paths.



19-19

NOTE

The result of setting the port attributes during the Ethernet line service configuration process is consistentwith the result of directly setting the Ethernet service port attributes.

6. Click OK.

Step 6 Click OK.

----End

Parameters


VB Name - - This parameter is a string that describes thebridge. It is recommended that you set thisstring to a value that contains the specificpurpose of the bridge.

VB Type 802.1q, 802.1d 802.1q l When setting this parameter to 802.1q,create the 802.1q bridge.

l When setting this parameter to 802.1d,create the 802.1d bridge.

l Using the 802.1q bridge is a priority. Ifthe conditions of the VLAN that is usedby the user are not known and if the userdoes not require the isolation of the dataamong VLANs, you can also use the802.1d bridge.


Feature Description


Issue 02 (2008-06-20)


Bridge Switch Mode IVL/Ingress FilterEnable (802.1q),SVL/Ingress FilterDisable (802.1d)

IVL/Ingress FilterEnable (802.1q),SVL/Ingress FilterDisable (802.1d)

l When the bridge uses the SVL mode, allthe VLANs share one MAC addresstable. When the bridge uses the IVLmode, all the VLANs correspond to theirrespective MAC address tables.

l If the ingress filter is enabled, the VLANtag is checked at the ingress port. If theVLAN ID does not equal the VLAN IDof the port defined in the VLAN filteringtable, the packet is discarded. If theingress filter is disabled, the precedingdescribed check is not conducted.

VB Mount Port - - l Only the port that is selected as themounted port of a bridge functions in thepacket forwarding process of the bridge.


Configurable Ports Mount eachVCTRUNK of theport.

- This parameter specifies the VCTRUNKwhose VC paths are to be configured.

Available BoundPaths

- - Follow these five principles to plan and setthis parameter:l The capacity of VCTRUNKs should be

determined by the actual bandwidth ofthe service needs.

l Bind only the paths in a VC-4 if possible.If the paths of several VC-4s need to bebound, the VC-4s that have the sametransmission path take priority.

l Each VC-4 of an Ethernet board can haveonly VC-3 paths or only VC-12 paths.Hence, when a VCTRUNK needs to bebound with VC-3 paths, select VC-3paths first from the VC-4 certain ofwhose VC-3 paths are already bound;when a VCTRUNK needs to be boundwith VC-12 paths, select VC-12 pathsfirst from the VC-4 certain of whoseVC-12 paths are already bound.

l As the VC-4-1s of the EFT4 board andEMS6 board support only VC-3 pathswhereas the VC-4-2s support both VC-12paths and VC-3 paths, give priority to thepaths in the VC-4-1 if a VCTRUNKneeds to be bound with VC-3 paths.

l Generally, bidirectional paths are bound.



19-21

19.6.2 Modifying the Mounted Port of a BridgeThis operation enables the user to modify the mounted port of a bridge, the enabled state of themounted port, and Hub/Spoke attribute of the port.


l The Ethernet LAN service must be created.


PrecautionsThe OptiX RTN 600 supports the Ethernet switching board EMS6.

Procedure


Step 2 Select the bridge that is already created, and click the VB Mount Port tab.

Step 3 Modify the mounted port of this bridge and the related attributes of the mounted port.

----End


Mount Port Unconnected, aspecific PORT, aspecific VCTRUNK

- l Only the port that is selected as themounted port of a bridge functions in thepacket forwarding process of the bridge.


Port Enabled A specific PORT inthe selectedforwarding ports

Enabled Set Port Enabled to Enabled. Otherwise,the port cannot forward the service.

Hub/Spoke Hub, Spoke Hub l The Spoke ports cannot access eachother. The Hub port and the Spoke portcan access each other. The Hub ports canaccess each other.



Feature Description


Issue 02 (2008-06-20)

19.6.3 Creating the VLAN Filter TableIf you create the 802.1q bridge during the process of creating the Ethernet LAN service, createthe VLAN filter table.





Procedure


Step 2 Select the bridge that is already created, and click the VLAN Filtering tab.

Step 3 Create the VLAN filter table.1. Click New.

The Create VLAN dialog box is displayed.2. Set VLAN ID (e.g:1,3-6).3. Select a port from the ports listed in Available forwarding ports, and then click

.4. Repeat Step 3.3 to select other forwarding ports.



19-23

5. Click OK.

----End


VLAN ID (e.g:1,3-6)

1–4095 - l You can set this parameter to a number orseveral numbers. When you set thisparameter to several numbers, use "," toseparate these discrete values and use "–"to indicate continuous numbers. Forexample, "1, 3–6" indicates numbers 1, 3,4, 5, and 6.


Selected forwardingports

This parameterindicates the portsthat are mounted to abridge.

- l The ports that are in selected forwardingports can forward only the packet thatcarries the VLAN ID (e.g:1,3-6) tag.These ports discard the packet that carriesother VLAN tags.

l The broadcast packet that is transmittedby the ports in selected forwardingports is broadcast only to the portsincluded in selected forwarding ports.


Feature Description


Issue 02 (2008-06-20)

19.6.4 Creating the Entry of a MAC Address Table ManuallyThe 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 createdentries of a MAC address table can be classified into two categories: unicast entry (that is, staticentry) and disabled entry (that is, blacklist entry).



l The VLAN filter table must be created (only applicable to the 802.1q bridge).


Precautions


Procedure


Step 2 Optional: Create the unicast entry manually.

1. Select the bridge that is already created, and click the VLAN Unicast tab.

2. Click New.The Create VLAN Unicast dialog box. is displayed.

3. Set the parameters of the unicast entry.

4. Click OK.

Step 3 Optional: Create the disabled entry manually.

1. Select the bridge that is already created, and click the Disable MAC Address tab.

2. Click New.The Disable MAC Address Creation dialog box is displayed.

3. Set the parameters of the disabled entry.



19-25

4. Click OK.

----End


VLAN ID 1–4095 - l In the case of the 802.1d bridge, if it usesthe SVL mode, this parameter is invalid.The set entry applies to all the VLANs.

l In the case of the 802.1q bridge, if it usesthe IVL mode, the set entry applies to theVLAN whose ID equals the set value.


MAC Address - - Set this parameter according to actualsituations.

Physical Port Each port that ismounted to a bridge

- This parameter indicates the Ethernet portcorresponding to a MAC address. Set thisparameter according to actual situations.

19.6.5 Modifying the Aging Time of the MAC Address Table EntryIn the case of the Ethernet switching board, the aging time of a MAC address table entry is 5minutes by default.






Feature Description


Issue 02 (2008-06-20)

Procedure

Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2Switching Management > Aging Time from the Function Tree.

Step 2 Modify the aging time of the MAC address table entry.

1. Double-click MAC Address Aging Time corresponding to this Ethernet switching board.The MAC Address Aging Time dialog box is displayed.

2. Set the duration and unit of the aging time.

3. Click OK.

Step 3 Click Apply.

----End

Parameters


MAC AddressAging Time

1 Min to 120 Day 5 Min l If one entry is not updated in a certainperiod, that is, if no new packet from thisMAC address is received to enable the re-learning of this MAC address, this entryis automatically deleted. This mechanismis called aging, and this period is calledaging time.

l If this parameter is set to a very greatvalue, the bridge stores excessive MACaddress table entries that are outdated,which exhausts the resources of the MACaddress forwarding table.

l If this parameter is set to a very smallvalue, the bridge may delete the MACaddress table entry that is needed, whichreduces the forwarding efficiency.


19.6.6 Configuring the Spanning Tree ProtocolIn the case of the Layer 2 service, if the loop is formed, enable the STP or RSTP for the bridgeand set bridge parameters and port parameters.



19-27




Precautions


Procedure

Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Layer-2Switching Management > Spanning Tree from the Function Tree.

Step 2 Optional: Set the enabled status of the protocol.

1. Click the Protocol Enable tab.

2. Configure parameters of the enabled protocol.

3. Click Apply.

Step 3 Optional: Set bridge parameters.

1. Click the Bridge Parameter tab.

2. Set bridge parameters.

3. Click Apply.

Step 4 Optional: Set port parameters.

1. Click the Port Parameter tab.

2. Set port parameters.

3. Click Apply.

Step 5 Optional: If enabling the RSTP, set the point-to-point attribute of the Ethernet port.

1. Click the Point to Point Attribute tab.

2. Set the point-to-point attribute.


Feature Description


Issue 02 (2008-06-20)

3. Click Apply.

----End


Protocol Enabled Enabled, Disabled Disabled l This parameter determines whether toenable the spanning tree protocol.

l It is recommended that you do not enablethe STP or RSTP in the servicenetworking process, because this canprevent the Layer 2 service from formingthe loop.

l If the loop is already formed in the servicenetworking, you must start the STP orRSTP.

Protocol Type STP, RSTP RSTP l This parameter is valid only whenProtocol Enabled is set to Enabled.

l The protocol type should be set accordingto the requirement of the interconnectedEthernet equipment. Generally, it isrecommended that you use the defaultvalue.

Priority (BridgeParameter)

0–61440 32768 l The most significant 16 bits of the bridgeID indicates the priority of the bridge.

l The smaller the value of this parameter,the higher priority and the higherpossibility that the bridge is selected asthe root bridge.

l If the priorities of all the bridges in theSTP network use the same value, thebridge whose MAC address is thesmallest is selected as the root bridge.

Hello Time (s) 1–10 2 l This parameter indicates the interval oftransmitting the CBPDU packet of thebridge.

l The greater the value of this parameter,the less the network resources that areoccupied by the spanning tree. Thetopology stability, however, decreases.



19-29


Max Age (s) 6–40 20 l This parameter indicates the maximumage of the CBPDU packet that is recordedby the port.

l The greater the value, the longertransmission distance of the CBPDU,which indicates that the network diameteris greater. When the value of thisparameter is greater, it is less possible thatthe bridge detects the link fault in a timelymanner and thus the network adaptationability is reduced.

Forward Delay (s) 4–30 15 l This parameter indicates the holding timeof a port in the listening state and in thelearning state.

l The greater the value, the longer the delaytime of the network state change. Hence,the topology changes slower and therecovery in the case of faults is slower.

TxHoldCout(Times/s)

1–10 6 This parameter indicates the number oftimes that the port transmits the CBPDU inevery second.

Admin EdgeAttribute

Enabled, Disabled Disabled l This parameter is valid only when theRSTP is used.

l This parameter determines whether to setthe port to an edge port. The edge portrefers to the bridge port that is connectedonly to the LAN. The edge port receivesthe BPDU and does not transmit theBPDU.

l This parameter is set to Enabled onlywhen the Ethernet port of the Ethernetboard is directly connected to the datacommunication terminal equipment,such as a computer. In other cases, it isrecommended that you use the defaultvalue.


Feature Description


Issue 02 (2008-06-20)


Auto EdgeDetection

Enabled, Disabled Disabled l This parameter is valid only when AdminEdge Attribute is set to Enabled.

l When this parameter is set to Enabled, ifthe bridge detects that this port isconnected to the port of other bridges, theRSTP considers this port as a non-edgeport.

l If Admin Edge Attribute is set toEnabled, set this parameter to Enabled.In other cases, it is recommended that youuse the default value.

Protocol Enabled Enabled, Disabled Enabled l This parameter determines whether theSTP or RSTP of the port is enabled.

l When this parameter is set to Disabled,the port does not process and transmit theBPDU.


Port Path Cost 1–65535 - l This parameter indicates the status of thenetwork that the port is connected to.

l In the case of the bridges on both ends ofthe path, set this parameter to the samevalue.

Priority (PortParameter)

0–240 128 l The most significant eight bits of the portID indicate the port priority.

l The smaller the value of this parameter,the higher priority.



19-31


Point-to-PointAttribute

Adaptiveconnection, Linkconnection, Sharedmedia

Adaptiveconnection

l This parameter is valid only when theRSTP is used.

l If this parameter is set to Adaptiveconnection, the bridge determines theactual point-to-point attribute of the portaccording to the actual working mode ofthe port. If the actual working mode of theport is full-duplex, the actual point-to-point attribute of the port is "true". If theactual working mode of the port is half-duplex, the actual point-to-point attributeof the port is "false".

l If this parameter is set to Linkconnection, the actual point-to-pointattribute of the port is "true".

l If this parameter is set to Shared media,the actual point-to-point attribute of theport is "false".

l Only the port whose point-to-pointattribute is "true" can transmit the rapidtransition request and response.


NOTE

l In the service networking process, it is recommended that you prevent the loop from forming in the case ofthe Layer 2 service and thus avoid enabling the STP or RSTP.

l Because the STP and STP are complicated, it is recommended that you negotiate with the engineer in chargeof maintaining the opposite Ethernet equipment and set the related parameters as instructed, before enablingthe STP or RSTP.

19.6.7 Configuring the IGMP Snooping ProtocolIf the bridge accesses a LAN where the IGMP multicast server exists, you can enable the IGMPSnooping protocol and configure the method for processing the unknown multicast packet.



l The VLAN filter table must be created (applies only when the 802.1q bridge is used).




Feature Description


Issue 02 (2008-06-20)

Procedure

Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Layer-2Switching 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.

Step 4 Click Apply.

----End

Parameters


Protocol Enable Enabled, Disabled Disabled l This parameter determines whether toenable the IGMP Snooping protocol.

l If the bridge accesses a LAN where theIGMP multicast server exists, you canenable the IGMP Snooping protocolaccording to the requirement.

Discard the Packet Yes, No Yes l This parameter is valid only whenProtocol Enabled is set to Enabled.

l If the 802.1q bridge receives a multicastpacket whose multicast address has nomapping item in the multicast table (inthis case, this multicast packet is anunknown multicast packet), thisparameter indicates the method forprocessing this packet.

l When this parameter is set to Yes, Theunknown multicast packet is discarded.

l When this parameter is set to No, theunknown multicast packet is broadcast inthe VLAN.

l Set this parameter according to therequirement of the IGMP multicastserver.

19.6.8 Modifying the Aging Time of the Multicast Table ItemIn the case of the Ethernet switching board, the aging time of a multicast table item is 8 minutesby default.



19-33



l The IGMP Snooping protocol of the bridge must be enabled.



Procedure

Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2Switching 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.

Step 4 Click Apply.

----End


Multicast AgingTime (Min)

1–120 8 l When a table item is notrefreshed in a certain period (thatis, no IGMP request from thismulticast address is received),this table item is automaticallydeleted. This mechanism iscalled aging, and this period iscalled aging time.

l If this parameter is set to a verygreat value, the bridge storesexcessive multicast table itemsthat are outdated, which exhauststhe resources of the multicasttable.

l If this parameter is set to a verysmall value, the bridge maydelete the multicast table itemthat is needed, which reduces theforwarding efficiency.


Feature Description


Issue 02 (2008-06-20)

19.7 Maintenance GuideThis topic describes the maintenance operations, alarms and performance events that are relatedto the Layer 2 switching, and problems that occur frequently during the application of the Layer2 switching.

19.7.1 Querying the Actual Capacity of the MAC Address Table andthe Dynamic Entry

By querying the actual capacity of the MAC address table and the dynamic entry, you can learnabout the MAC address learning situation of the bridge.





Procedure


Step 2 Query the actual capacity of the MAC address table.1. Select the bridge that is already created, and click the VLAN MAC Address Table

Capacity tab.2. Click Query.3. View the actual capacity of the MAC address table.

Step 3 Query the actual capacity of the MAC address table.1. Select the bridge that is already created, and click the Self-learning MAC Address tab.2. Click First page, Previous, or Next to view the dynamic entry of the MAC address table

by page.

----End

19.7.2 Querying the Running Information About the Spanning TreeProtocol

The running information about the spanning tree protocol includes the bridge runninginformation and port running information.




19-35


l The STP or RSTP of the bridge must be enabled.



Procedure

Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2Switching Management > Spanning Tree from the Function Tree.

Step 2 Query the bridge running information.1. Click the Bridge Running Info tab.2. Click Query.3. View the bridge running information.

Step 3 Query the port running information.1. Click the Port Running Info tab.2. Click Query.3. View the port running information.

----End

19.7.3 Querying the Running Information About the IGMPSnooping Protocol

The running information about the IGMP Snooping protocol includes the current multicast routerport and multicast table item.



l The IGMP Snooping protocol of the bridge must be enabled.



Procedure

Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2Switching Management > IGMP Snooping Protocol from the Function Tree.

Step 2 Query the information about the router port.1. Click the Multicast Router Port Management tab.


Feature Description


Issue 02 (2008-06-20)

2. Click Query.3. View the information about the router port.

Step 3 Query the information about the multicast table item.1. Click the Multicast Table Item tab.2. Click Query.3. View the information about the multicast table item.

----End

19.7.4 Relevant Alarms and EventsThe Layer 2 switching feature may cause changes in RMON performance.



Relevant RMON Performance EventsFor details, see 22.1.3 List of RMON Alarm Entries and List of RMON PerformanceEntries.

19.7.5 FAQsThis topic lists the problems that occur frequently during the application of the Layer 2 switchingfeature.

Q: Why should you prevent the Layer 2 switching service from forming the loop in theservice networking?

A: When the loop is formed in the case of the Layer 2 switching service, you must enable theSTP 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, thiskind of protection can restore the service more quickly than re-stabilizing the networktopology by enabling the STP or RSTP. In this case, the STP or RSTP cannot protect theservice according to the requirement and even increases the service interruption time.

l The spanning tree algorithm is complicated, and thus obtaining the specific service flow isdifficult. In addition, the algorithm occupies a large number of NE resources.



19-37

20 QoS

About This Chapter

In legacy IP networks, all packets are processed according to the first in first out (FIFO) andbest effort strategies. This method cannot meet the requirement of the new service for thebandwidth, delay, and delay jitter. Hence, the QoS technology is developed.

20.1 Feature DescriptionQoS refers to the ability of the communication network to ensure the expected service qualityin the aspects of bandwidth, delay, delay jitter, and packet loss ratio, and thus to ensure that therequest and response from the user or the request and response from the application meet theexpected service class.

20.2 AvailabilityThe QoS feature requires support of the involved equipment and boards.

20.3 Relation with Other FeaturesThe QoS feature does not affect other Ethernet features.

20.4 Realization PrincipleThis topic describes the flow of processing the QoS, and algorithms that are used for the CAR,traffic shaping, and egress queue scheduling.

20.5 Planning GuidePlan related parameters according to the specific application of the QoS feature.

20.6 Configuration GuideThis topic describes the configuration tasks relevant to the QoS feature.

20.7 Maintenance GuideThis topic describes alarms and performance events relevant to the QoS feature, and problemsthat occur frequently during the application of the QoS feature.

OptiX RTN 600 Radio Transmission SystemFeature Description 20 QoS


20-1

20.1 Feature DescriptionQoS refers to the ability of the communication network to ensure the expected service qualityin the aspects of bandwidth, delay, delay jitter, and packet loss ratio, and thus to ensure that therequest and response from the user or the request and response from the application meet theexpected service class.

The Ethernet switching board provides the following QoS functions: flow classification,committed access rate (CAR), class of service (CoS), and traffic shaping. These functionscomply with IEEE 802.1p, RFC 2697, RFC 2698, RFC 2309, RFC 2597, and RFC 2598.

20.1.1 Flow ClassificationFlow refers to a collection of packets with same characteristics. In the case of the Ethernetswitching board, the flow refers to a collection of packets that corresponds to same QoSoperations. Flow classification means, according to certain rules, classifying a packet into severalflow types that different QoS operations are performed on. The flow classification is aprerequisite and basis for the QoS operation.

The flow type is based on the associated Ethernet service type of the flow. The flow types thatare supported by the Ethernet switching board EMS6 are as follows:

l Port flow

The packets from a certain port are classified as a type of flow. The associated Ethernetservice of this flow type is the line service that uses this port as the service source. TheLayer 2 switching service can also be classified as a port flow.

l Port+VLAN flow

The packets that are from a certain port with a specified VLAN ID are classified as a typeof flow. The associated Ethernet service of this flow type is the line service that uses thisport+VLAN as the service source.

l Port+SVLAN flow

The packets that are from a certain port and have a specified SVLAN are classified as atype of flow. The associated Ethernet service of this flow type is the line service that usesthis port+SVLAN as the service source.

l Port+CVLAN+SVLAN flow

The packets that are from a certain port and have a specified CVLAN+SVLAN areclassified as a type of flow. The associated Ethernet service of this flow type is the lineservice that uses this port+CVLAN+SVLAN as the service source.

20.1.2 CARCAR is a type of traffic policing technologies. After the flow classification, the CAR assessesthe rate of the traffic in a certain period (including in the long term and in the short term). TheCAR sets the packet whose rate does not exceed the specified rate to high priority and discardsthe packet whose rate exceeds the specified rate or downgrades this kind of packet, thusrestricting the traffic into the transmission network.

The Ethernet switching board processes the flow whose CAR feature is enabled as follows:

20 QoSOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

l When the rate of packets is not more than the set committed information rate (CIR), thesepackets pass the restriction of the CAR and are forwarded first even in the case of networkcongestion.

l When the rate of packets exceeds the set peak information rate (PIR), the packets whoserate is more than the PIR are directly discarded.

l When the rate of packets is more than the CIR but is not more than the PIR, the packetswhose rate is more than the CIR can pass the restriction of the CAR and are marked yellow,which enables these packets to be discarded first in the case of network congestion.

l When the rate of packets that pass the restriction of the CAR is not more than CIR in acertain period, certain packets can burst and these packets can be forwarded first even inthe case of network congestion. The maximum traffic of burst packets is determined by thecommitted burst size (CBS). The CBS contains two parts: fixed part and variable part. Thefixed part is determined by the CIR and the variable part is set on the NM.

l When the rate of the packets that pass the restriction of the CAR is more than the CIR butis not more than the PIR, certain packets can burst and are marked yellow, which enablesthese packets to be discarded first in the case of network congestion. The maximum trafficof burst packets is determined by the maximum burst size (MBS). The MBS contains twoparts: fixed part and variable part. The fixed part is determined by the PIR and the variablepart is set on the NM.

20.1.3 CoSBy using the CoS, the packets in a flow can be scheduled to different queues of different prioritiesand can be processed according to the priority of each queue. This ensures the packets of differentpriorities can be processed according to different QoS requirements.

Each port on the Ethernet switching board EMS6 supports eight egress queues, and the CoSpriorities of these eight queues are from 0 to 7. If the traffic shaping feature of all the queues isenabled or disabled, the queue whose CoS priority is 7 is a strict priority (SP) queue, and theother queues whose priorities are from 0 to 6 are weighted round robin (WRR) queues. Theweighted 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 thequeue whose traffic shaping feature is enabled according to the set CIR. The remainingbandwidth is allocated to the queues whose traffic shaping is disabled according to the SP+WRRalgorithm.

The CoS of the EMS6 is classified into three categories:

l SimpleIf the CoS type of a flow is set to simple, all the packets in this flow are directly scheduledto a specified egress queue.

l VLAN priorityIf the CoS type of a flow is set to VLAN priority, the packets in this flow are scheduled tospecified egress queues according to the user priorities specified in the VLAN tags of thesepackets.

l DSCPIf the CoS type of a flow is set to DSCP, the packets in this flow are scheduled to specifiedegress queues according to differentiated services code point (DSCP) in the IPv6 tags ofthese packets.

In the case of the simple type, the maximum set number of CoS supported by the EMS6 boardis 8. In the case of the VLAN priority type, the maximum set number of CoS supported by the



20-3

EMS6 board is 6. In the case of the DSCP type, the maximum set number of CoS supported bythe EMS6 board is 6.

20.1.4 Traffic ShapingThe traffic shaping can restrict the traffic and burst of a connection in a network, and thus enablesthe packet to be transmitted at an even rate. The Ethernet switching board shapes the irregulartraffic or the traffic that does not conform to the specified traffic characteristics based on thegeneric traffic shaping (GTS) technology.

In the case of the port queue whose traffic shaping feature is enabled, the Ethernet switchingboard 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 theegress queue.

l When the rate of the packets is more than the set PIR, these packets enter the buffer. Whenthe buffer overflows, the packets are discarded.

l When the rate of the packets is more than the CIR but not more than the PIR, the packetswhose rate is more than the CIR enter the buffer of the CIR. When the buffer overflows,these packets are marked yellow and enter the egress queue. In this case, these packets arediscarded in the case of queue congestion.

l When the rate of the packets that pass the restriction of the traffic shaping in a certain periodis not more than the CIR, certain burst packets enter the egress queue. The maximum trafficof the burst packets is determined by the CBS. The value of the CBS is determined by theCIR, and cannot be set.

l When the rate of the packets that pass the restriction of the traffic shaping in a certain periodis more than the CIR but not more than the PIR, certain burst packets enter the buffer ofthe CIR. The maximum traffic of the burst packets is determined by the MBS. The valueof the MBS is determined by the PIR, and cannot be set.

As is evident from the preceding processing mechanism, the difference of the traffic shapingfrom the CAR is as follows:

l In the processing of the CAR, the packet that does not conform to the traffic characteristicsis downgraded in priority or directly discarded.

l In the processing of the traffic shaping, the packet that does not conform to the trafficcharacteristics is stored in the buffer. The packet is downgraded in priority or directlydiscarded only when the buffer overflows.

20.2 AvailabilityThe QoS feature requires support of the involved equipment and boards.

Table 20-1 Availability of the QoS feature


QoS EMS6 (all the versions) IDU 620


Feature Description


Issue 02 (2008-06-20)

20.3 Relation with Other FeaturesThe QoS feature does not affect other Ethernet features.

20.4 Realization PrincipleThis topic describes the flow of processing the QoS, and algorithms that are used for the CAR,traffic shaping, and egress queue scheduling.

20.4.1 CARThe CAR uses the dual token bucket three color marker algorithm.

Token Bucket AlgorithmFigure 20-1 shows the basic principle of the token bucket algorithm.

Figure 20-1 Basic principle of the token bucket algorithm

Token bucket

Packets that need tobe sent from this port

Packets thatleave this port

Tokens

...

Packets are discarded orprocessed in another way

Classi-fication

Tokens are placedinto the token bucket

at a specified rate

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 bucketexceeds the capacity of the bucket, the number of tokens no longer increases. A token indicatescertain packet traffic. When the packets are transmitted, certain tokens are removed from thebuckets according to the length of the packet. When the number of tokens that are stored in thetoken bucket cannot support the transmitting of the packets, these packets are discarded orprocessed in another way. When the token bucket is filled with tokens, the packets that arerepresented 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 AlgorithmFigure 20-2 shows the basic principle of the dual token bucket three color marker algorithmthat is used by the CAR.



20-5

Figure 20-2 Basic principle of the algorithm that is used by the CAR

Tp Tc

PIR

...

CIR

...

Classi-fication

This algorithm uses two token buckets Tc and Tp, and marks colors for packets according to thesituations 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 a rate of CIR, and the capacity of the Tctoken bucket equals the CBS.

l The packet is placed into the Tp token bucket at a rate of PIR, and the capacity of the Tptoken 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 thecase of network congestion.

l If a packet obtains the Tp token but does not obtain the Tc token, this packet is markedyellow.This kind of packet can pass the restriction of the CAR but is discarded first in the case ofnetwork congestion.

l If a packet does not obtain the Tp token, this packet is marked red.This kind of packet is directly discarded.

20.4.2 Traffic ShapingThe traffic shaping uses the dual token bucket three color marker algorithm that is similar to thealgorithm used by the CAR. The buffer queue, however, is added before the token bucket in thealgorithm used by the traffic shaping.

Figure 20-3 shows the basic principle of the dual token bucket three color marker algorithmthat is used by the traffic shaping.


Feature Description


Issue 02 (2008-06-20)

Figure 20-3 Basic principle of the algorithm that is used by the traffic shaping

Tptoken bucket

Tctoken bucket

PIR

...

CIR...

Tpbuffer queue

Tcbuffer queue

This algorithm uses two token buckets Tc and Tp, and places packets into different queuesaccording 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 a rate of CIR, and the capacity of the Tctoken bucket equals the CBS.

l The packet is placed into the Tp token bucket at a rate of PIR, and the capacity of the Tptoken bucket equals the EBS.

A packet is placed into a queue as follows:

l If a packet obtains the Tc token, this packet is directly placed into the egress queue.

l If a packet obtains the Tp token but does not obtain the Tc token, this packet is placed intothe Tc buffer queue.When the Tc buffer queue overflows, the overflow packet is marked yellow and then entersthe egress queue, which indicates that the packet is discarded first in the case of networkcongestion.

l If a packet does not obtain the Tp token, this packet is placed into the Tp buffer queue.When the Tp buffer queue overflows, the overflow packet is directly discarded.

20.4.3 Egress Queue SchedulingThe EMS6 board uses the SP and WRR algorithms to schedule the egress queue.

Figure 20-4 shows the basic principle of the egress queue algorithm that is used by the EMSboard when the traffic shaping of all the port queues is enabled or disabled.



20-7

Figure 20-4 Basic principle of the egress queue algorithm

Queue 8

Queue 7

Queue 6

Queue 1

...

64

32

1

WeightQueuesPackets that need tobe sent from this port

Packets that leave thisport

Queue where packets are arranged according toemergency level in a descending order from left to right

Strict priority

Classi-fication

Egressscheduling

In this algorithm:

l Queue 8 (whose CoS priority is 7) uses the SP algorithm. When this queue has packets,these packets are forwarded first. When this queue does not have packets, packets in otherqueues are allowed transmitting.

l Queues 7–1 (whose CoS priorities are from 6 to 0) use the WRR algorithm. The WRRallocates the service time segment for each queue according to the weight of each queue,and transmits the packet corresponding to each queue at the specified time segment. If thequeue that corresponds to a time segment does not have packets, this time segment isremoved and the packets in the queue that corresponds to the following time segment. Forexample, if four queues are weighted as follows: 1:2:4:8, the WRR allocates the servicetime segments in the form of cyclic sequence with a period 432443414342434.

If the traffic shaping of certain queues is enabled, the bandwidth is first allocated to the queuewhose traffic shaping is enabled according to the set CIR. The remaining bandwidth is allocatedto the queue whose traffic shaping is disabled according to the preceding algorithm. For example,the traffic shaping of queues 5 and 7 is enabled, the set CIR of both queues is 10 Mbit/s, and thetotal bandwidth at the port is 25 Mbit/s. In this case, the service time segments are allocated toqueues 5 and 7, and the remaining queues according to the weight in the WRR algorithm 10:10:5When 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 of these queues 1:2:4:8:32.

When the egress queues are congested, the packet that is marked yellow in the CAR or in thetraffic shaping is first discarded.

20.5 Planning GuidePlan related parameters according to the specific application of the QoS feature.

Prerequisitel You must know the type and specific situation of the Ethernet service that requires the QoS

application.l You must know the functions of the QoS feature.


Feature Description


Issue 02 (2008-06-20)

Procedure

Step 1 Select the proper QoS function according to the requirement.

Follow these three principles when selecting the QoS function:

l First select the CAR. This can control the service traffic on the ingress side.

l In the case of the important service that requires to improve the traffic fluctuation, select thetraffic shaping function.

l If differentiated services are required for different service types or different user classes,select the CoS function.

Step 2 Optional: Plan the CAR.

Follow these two principles when planning the CAR:

l Bind a CAR to a flow. Do not bind a CAR to multiple flows.

l The sum of CIRs of all the CARs that are associated with a PORT or a VCTRUNK shouldnot exceed the physical bandwidth of this PORT or this VCTRUNK.

Step 3 Optional: Plan the traffic shaping and CoS.

Follow these four principles when planning the traffic shaping and CoS:

l Allocate the service of low delay or the service of low delay commitment (such as thesignaling data, VoIP data, and network management protocol packet) into the queues of strictpriority.

l Allocate the service that does not require low delay or that does not provide low delaycommitment (such as the Internet service) into the WRR queue.

l The sum of CIRs of all the queues that are associated with a PORT or a VCTRUNK shouldnot exceed the physical bandwidth of this PORT or this VCTRUNK.

l Plan the parameters of the traffic shaping according to the traffic characteristics, thuspreventing the buffer from overflowing frequently.

----End

20.6 Configuration GuideThis topic describes the configuration tasks relevant to the QoS feature.

20.6.1 Creating a FlowIn the case of the Ethernet switching board, a flow refers to the collection of packets that thesame QoS operation is performed on. Creating a flow is the prerequisite for performing CARand CoS operations.


l The associated Ethernet service must be created.




20-9


Procedure

Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoSManagement > Flow Management from the Function Tree.

Step 2 Click the Flow Configuration tab.

Step 3 Click New.The New Flow dialog box is displayed.

Step 4 Set the flow parameters.

Step 5 Click OK.

----End


Feature Description


Issue 02 (2008-06-20)


Flow Type Port Flow, Port+VLAN Flow, Port+SVLAN Flow,Port+CVLAN+SVLAN Flow

Port Flow l Port flow: The packets from a certain portare classified as a type of flow. TheEthernet service associated with this flowtype is the line service or Layer 2switching service that uses this port as theservice source.

l Port+VLAN flow: The packets that arefrom a certain port and have a specifiedVLAN ID are classified as a type of flow.The associated Ethernet service of thisflow type is the line service that uses thisport+VLAN as the service source.

l Port+VLAN flow: The packets that arefrom a certain port and have a specifiedSVLAN ID are classified as a type offlow. The associated Ethernet service ofthis flow type is the line service that usesthis port+SVLAN as the service source.

l Port+CVLAN+SVLAN flow: Thepackets that are from a certain port andhave a specified CVLAN+SVLAN areclassified as a type of flow. Theassociated Ethernet service of this flowtype is the line service that uses this port+CVLAN+SVLAN as the service source.

Port A specific PORT orVCTRUNK

PORT1 l When the associated service is the lineservice, set this parameter to the sourceport or sink port of the associatedEthernet service.

l When the associated service is the Layer2 switching service, set this parameter toa mounted port of the bridge.

VLAN ID 1–4095 1 l This parameter is valid only when FlowType is set to Port+VLAN Flow.

l Set this parameter to the source VLAN ofthe associated Ethernet service.

C-VLAN 1–4095 1 l This parameter is valid only when FlowType is set to Port+SVLAN+CVLANFlow.

l Set this parameter to the source C-VLANof the associated Ethernet service.



20-11


S-VLAN 1–4095 1 l This parameter is valid only when FlowType is set to Port+SVLAN Flow or setto Port+SVLAN+CVLAN Flow

l Set this parameter to the source S-VLANof the associated Ethernet service.

PostrequisiteAfter creating a flow, bind it to corresponding CAR or CoS operation as required.

20.6.2 Creating the CARCAR is a type of traffic policing technologies. After the flow classification, the CAR assessesthe rate of the traffic in a certain period (including in the long term and in the short term). TheCAR sets the packet whose rate does not exceed the specified rate to high priority and discardsthe packet whose rate exceeds the specified rate or downgrades this kind of packet, thusrestricting the traffic into the transmission network.




Procedure


Step 2 Click the CAR Configuration tab.

Step 3 Click New.The New Car dialog box is displayed.

Step 4 Set the CAR parameters.


Feature Description


Issue 02 (2008-06-20)

Step 5 Click OK.

----End


CAR ID 1–65535 1 This parameter identifies a CAR operation,and is used to bind a flow to an associatedCAR operation.

Enabled/Disabled Enabled, Disabled Disabled This parameter determines whether toenable the CAR operation performed on theflow bound to the CAR.

CommittedInformation Rate(kbit/s)

An integer rangingfrom 0 to 1048576,with a step of 64

0 l This parameter actually equals the CIR.When the rate of the packets is not morethan the CIR, these packets pass therestriction of the CAR and are forwardedfirst even in the case of networkcongestion.

l The value of this parameter should not bemore than the PIR.



20-13


Committed BurstSize (kbyte)

0–1024 0 This parameter actually equals the CBS.When the rate of the packets that pass therestriction of the CAR is not more than theCIR in a certain period, certain packets canburst and can pass the restriction of theCAR. These packets can be forwarded firsteven in the case of network congestion. Themaximum traffic of the burst packets isdetermined by the CBS. Note that the CBShas an inherent size, and this parameterindicates the increment value only. Theinherent size of the CBS is determined bythe CIR. The greater the CIR, the greater theCBS.

Peak InformationRate (kbit/s)

An integer rangingfrom 0 to 1048576,with a step of 64

0 l This parameter actually equals the PIR.When the rate of the packets is more thanthe PIR, these packets that exceed the raterestriction are directly discarded. Whenthe rate of the packets is more than theCIR but is not more than the PIR, thepackets whose rate is more than the CIRcan pass the restriction of the CAR andare marked yellow, which enables thesepackets to be discarded first in the case ofnetwork congestion.

l The value of this parameter should not bemore than the bandwidth at the port.

Maximum BurstSize (kbyte)

0–1024 0 This parameter actually equals the MBS.When the rate of the packets that pass therestriction of the CAR is more than the CIRbut is not more than the PIR, certain packetscan burst and are marked yellow, whichenables these packets to be discarded first inthe case of network congestion. Themaximum traffic of the burst packets isdetermined by the set MBS. Note that theMBS has an inherent size, and thisparameter indicates the increment valueonly. The inherent size of the MBS isdetermined by the PIR. The greater the PIR,the greater the MBS.

PostrequisiteAfter creating the CAR, bind the flow to the corresponding CAR operation as required.


Feature Description


Issue 02 (2008-06-20)

20.6.3 Creating the CoSBy using the CS, the packets in a flow can be scheduled to different queues of different prioritiesand can be processed according to the priority of each queue. This ensures the packets of differentpriorities can be processed according to different QoS requirements.




Procedure


Step 2 Click the CoS Configuration tab.

Step 3 Click New.The New CoS dialog box is displayed.

Step 4 Set the CoS parameters.



20-15

Step 5 Click OK.

----End


CoS ID 1–65535 1 This parameter identifies a CoS operation,and is used to bind a flow to an associatedCoS operation.


Feature Description


Issue 02 (2008-06-20)


CoS Type simple, VLANpriority, DSCP

simple l If the CoS type of a flow is set to simple,all the packets in this flow are directlyscheduled to a specified egress queue.

l If the CoS type of a flow is set to VLANpriority, the packets in this flow arescheduled to specified egress queuesaccording to the user priorities specifiedin the VLAN tags of these packets.

l If the CoS type of a flow is set to DSCP,the packets in this flow are scheduled tospecified egress queues according todifferentiated services code point(DSCP) in the IPv6 tags of these packets.

CoS Priority 0–7 0 l This parameter determines which queuea packet is schedule to.

l Each port on the EMS6 board supportseight egress queues, and the CoSpriorities of these eight queues are from0 to 7.

l If the traffic shaping feature of all thequeues is enabled or disabled, the queuewhose CoS priority is 7 is an SP queue,and the other queues whose priorities arefrom 0 to 6 are WRR queues. Theweighted proportion of these WRRqueues are 1:2:4:8:16:32:64 (frompriority 0 to priority 6).

l If the traffic shaping feature of certainqueues is enabled, the bandwidth isallocated first to the queue whose trafficshaping feature is enabled according tothe set CIR. The remaining bandwidth isallocated to the queues whose trafficshaping is disabled according to the SP+WRR algorithm.

PostrequisiteAfter creating the CoS, bind the flow to the corresponding CoS operation as required.

20.6.4 Binding the CAR/CoSTo enable the CAR or CoS function, bind the corresponding flow to the created CAR/CoS.




20-17

l The flow and CAR/CoS must be created.


Precautions


Procedure

Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoSManagement > Flow Management.

Step 2 Click the Flow Configuration tab.

Step 3 Bind the CAR/CoS.

Step 4 Click Apply.

----End

Parameters


Bound CAR - - This parameter indicates the CAR IDcorresponding to a CAR operation.Different CAR IDs should be bound todifferent flows, even though the parametersof the CAR operations are the same.

Bound CoS - - This parameter indicates the CoScorresponding to a CoS operation. DifferentCoS IDs should be bound to different flows,even though the parameters of the CoSoperations are the same.

20.6.5 Configuring the Traffic ShapingThe traffic shaping can restrict the traffic and burst of a connection in a network, and thus enablesthe packets to be transmitted at an even rate.




Feature Description


Issue 02 (2008-06-20)


Procedure

Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoSManagement > 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.

Step 4 Click Apply.

----End


Port A specific PORT orVCTRUNK

- This parameter indicates the port whosetraffic is shaped.

Enabled/Disabled Enabled, Disabled Disabled l This parameter determines whether toenable the traffic shaping of an egressqueue.

l If the traffic shaping feature of certainqueues is enabled, the bandwidth isallocated first to the queue whose trafficshaping feature is enabled according tothe set CIR. The remaining bandwidth isallocated to the queues whose trafficshaping is disabled according to the SP+WRR algorithm.

CIR (kbit/s) An integer rangingfrom 0 to 1048574,with a step of 64

0 l This parameter actually equals the CIR.When the rate of the packets is not morethan the CIR, these packets directly enterthe egress queue.

l The value of this parameter should not bemore than the PIR.



20-19


PIR (kbit/s) An integer rangingfrom 0 to 1048574,with a step of 64

0 l This parameter actually equals the PIR.When the rate of the packets is more thanthe PIR, the packets that exceed the raterestriction are directly discarded. Whenthe rate of the packets is more than theCIR but not more than the PIR, thepackets whose rate is more than the CIRenter the buffer of the CIR. When thebuffer overflows, the packets are markedyellow and enter the egress queue, whichenables these packets to be discarded firstin the case of queue congestion.

l The value of this parameter should not bemore than the bandwidth at the port.

20.7 Maintenance GuideThis topic describes alarms and performance events relevant to the QoS feature, and problemsthat occur frequently during the application of the QoS feature.

20.7.1 Relevant Alarms and EventsThe QoS feature may cause changes in RMON performance.

Relevant Alarms

None.

Relevant Abnormal Events

None.

Relevant RMON Performance Events

For details, see 22.1.3 List of RMON Alarm Entries and List of RMON PerformanceEntries.

20.7.2 FAQsThis topic lists the problems that occur frequently during the application of the QoS feature.

Q: Why the Ethernet service is interrupted after the traffic shaping is enabled?

A: Generally, this problem occurs because the CIR and PIR are not configured. The defaultvalues of the CIR and PIR are 0.


Feature Description


Issue 02 (2008-06-20)

21 QinQ

About This Chapter

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.

21.1 Feature DescriptionQinQ is a technology that is used to encapsulate a VLAN tag before the existing VLAN tag ofa data frame. As a result, the data frame has double VLAN tags. In the case of a data frame thathas double tags, the inner VLAN tag is called the C-VLAN, which indicates the customer VLAN,and the outer VLAN tag is called the S-VLAN, which indicates the service VLAN.

21.2 AvailabilityThe QinQ feature requires support of the involved equipment and boards.

21.3 Relation with Other FeaturesThe QinQ feature of the Ethernet switching board supports only private services but does notsupport L2 switching services. QinQ line services support the QoS.

21.4 Realization PrincipleThe attributes of QinQ packets are closely related to the port attributes and service type.

21.5 Planning GuidePlan related parameters according to the specific application of the QinQ feature.

21.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of theQinQ line service. An example is provided as a supplement to the configuration.

21.7 Maintenance GuideThis topic describes alarms and performance events relevant to the QinQ feature, and problemsthat occur frequently during the application of the QinQ feature.

OptiX RTN 600 Radio Transmission SystemFeature Description 21 QinQ


21-1

21.1 Feature DescriptionQinQ is a technology that is used to encapsulate a VLAN tag before the existing VLAN tag ofa data frame. As a result, the data frame has double VLAN tags. In the case of a data frame thathas double tags, the inner VLAN tag is called the C-VLAN, which indicates the customer VLAN,and the outer VLAN tag is called the S-VLAN, which indicates the service VLAN.

21.1.1 FunctionalityThe QinQ technology provides an L2 virtual private network (VPN) solution that is cheaper andsimpler than the multi-protocol label switching (MPLS) technology.

The functions of the QinQ technology are as follows:

l With the application of the QinQ technology, the number of VLAN IDs can reach4096x4096. This effectively solves the problem that the number of VLAN IDs cannot meetthe requirement.

l Customers and operators can plan VLAN resources independently and flexibly, thussimplifying network configuration and maintenance.

l The QinQ technology replaces the MPLS technology to provide a cheaper and simpler L2VPN solution.

l The QinQ technology enables the expansion of Ethernet services from local area networks(LANs) to wide area networks (WANs).

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

Ethernet Frame with Only a C-TAGThe Ethernet frame with only a C-TAG has the same format as the tagged frame defined in IEEE802.1Q. Hence, the tagged frame defined in IEEE 802.1Q is an Ethernet frame that contains aC-VLAN tag. For details on the format of a tagged frame, see Format of the tagged frame.

Figure 21-1 Format of the Ethernet frame with only a C-TAG

Destinationaddress

Sourceaddress C-TAG Length/Type Data FCS

(CRC-32)

4 bytes

VID

12 bits

CFIPCPTPID

1 bit3 bits16 bits

TCI

21 QinQOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

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 addedbefore 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 thevalue of the TPID in the C-TAG is 0x8100.

NOTE

The TPID in the S-TAG supported by the Ethernet switching board has the same value as the TPID in theC-TAG. The TPID value is 0x8100. The TPID value in the S-TAG can be modified. For details, see 21.6.2Modifying 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 21-2 Format of the Ethernet frame with a C-TAG and an S-TAG

Destinationaddress

Sourceaddress S-TAG Length/Type Data FCS

(CRC-32)

4 bytes

VID

12 bits

DEIPCPTPID

1 bit3 bits16 bits

TCI

C-TAG

NOTE

Certain vendors use the Ethernet frames each of which contains a C-TAG and an S-TAG but whose type fieldis 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 C-TAG.

Figure 21-3 Format of the Ethernet frame with only an S-TAG

Destinationaddress

Sourceaddress S-TAG Length/Type Data FCS

(CRC-32)

4 bytes

VID

12 bits

DEIPCPTPID

1 bit3 bits16 bits

TCI



21-3

21.1.3 Network AttributesThe network attribute of each port (PORT or VCTRUNK) can be set to UNI, C-aware, or S-aware depending on how the port processes the C-TAG and S-TAG.

UNI PortA UNI port verifies and processes the outer tag of an Ethernet frame according to the TAGattributes of the port. UNI ports cannot be used in the case of QinQ services.

C-Aware PortA C-aware port is in an equivalent position as a UNI port in a network. A C-aware port considersthat an accessed packet does not contain an S-TAG. C-aware ports can be used in the case ofQinQ services.

NOTE

l C-TAG frames and untagged frames can normally enter and exit C-aware ports.

l When an S-TAG frame enters and exits a C-aware port, the port processes the S-TAG as a C-TAG.

l When a frame that contains an S-TAG and a C-TAG enters and exits a C-aware port, the port processes theS-TAG as a C-TAG and does not process the inner C-TAG.

S-Aware PortAn S-aware port is in an equivalent position as a UNI port in a network. An S-aware portconsiders that an accessed packet contains an S-TAG. S-aware ports can be used in the case ofQinQ services.

NOTE

l S-TAG frames or the frames that contain an S-TAG and a C-TAG can normally enter and exit S-aware ports.

l When a C-TAG frame enters and exits an S-aware port, the port processes the C-TAG frame as an S-TAGframe.

l When an untagged frame enters and exits an S-aware port, the port discards the frame.

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

21.1.4 Application of the QinQ Technology in Line ServicesIntroduction of the QinQ technology provides many new applications for line services.

Line Services Between C-Aware PortsThe line services between C-aware ports have four applications.


Feature Description


Issue 02 (2008-06-20)

Table 21-1 Line services between C-aware ports

Type ofPacket (Typeof SourcePort)

OperationType

Direction Description

C-TAG (C-aware port)

Transparentlytransmit C-VLAN

Unidirectional/Bidirectional

Transparently transmits packetsaccording to the C-VLAN.

Translate C-VLAN


Transmits packets according to theC-VLAN, which is translated.

All types (C-aware port)

Transparentlytransmit C-VLAN


Transparently transmits packets.

Line Services Between a C-Aware Port and an S-Aware PortThe line services between a C-aware port and an S-aware port have three applications.

Table 21-2 Line services between a C-aware port and an S-aware port


OperationType


C-TAG (C-aware port)

Add S-VLAN Unidirectional Transmits packets according to theC-VLAN and adds an S-VLAN tagto each packet.

Bidirectional In the case of the service from a C-aware port to an S-aware port, theport transmits the packets accordingto the C-VLAN and adds an S-VLAN tag to each packet.In the case of the service from an S-aware port to a C-aware port, theport transmits the packets accordingto the C-VLAN and strips the S-VLAN tag from each packet.

All types (C-aware port)

Add S-VLAN Unidirectional Transmits packets and adds an S-VLAN tag to each packet.



21-5


OperationType


Bidirectional In the case of the service from a C-aware port to an S-aware port, theport adds an S-VLAN tag to eachpacket.In the case of the service from an S-aware port to a C-aware port, theport strips the S-VLAN tag fromeach packet.

S-TAG or S-TAG + C-TAG(S-aware port)

Strip S-VLAN Unidirectional Transmits packets according to theS-VLAN and strips the S-VLANtag 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 PortsThe line services between S-aware ports have two applications.

Table 21-3 Line services between S-aware ports


OperationType


S-TAG or S-TAG + C-TAG(S-aware port)

Transparentlytransmit S-VLAN


Transparently transmits packetsaccording to the S-VLAN.

Translate S-VLAN


Transmits packets according to theS-VLAN, which is translated.

21.2 AvailabilityThe QinQ feature requires support of the involved equipment and boards.

Table 21-4 Availability of the QinQ feature


QinQ EMS6 (all the versions) IDU 620


Feature Description


Issue 02 (2008-06-20)

21.3 Relation with Other FeaturesThe QinQ feature of the Ethernet switching board supports only private services but does notsupport L2 switching services. QinQ line services support the QoS.

21.4 Realization PrincipleThe attributes of QinQ packets are closely related to the port attributes and service type.

The following describes how packets are processed in a QinQ network. The QinQ servicesillustrated in Figure 21-4 are provided as an example.

Figure 21-4 Example of QinQ services

Servicenetwork A

C-VLAN1

C-VLAN1Service

network B

NE1

NE2 NE3

NE4

Frame of customer a

Frame of customer b

C-VLAN1S-VLAN2C-VLAN1S-VLAN1



C-VLAN1

C-VLAN1

In the network, the NEs from NE1 to NE4 process the data frames as follows:

1. NE1 adds an S-TAG to each accessed data frame from customer a and customer b andforwards the frames to NE2. In the case of the data frames from customer a, NE1 adds anS-VLAN1 tag to each frame; in the case of the data frames from customer b, NE1 adds anS-VLAN2 tag to each frame.

2. NE2 transparently transmits the data frames of customer a and customer b to NE3 of serviceprovider B according to the S-VLAN tags.

3. 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 containsan S-VLAN3 tag, translates the data frame that contains an S-VLAN2 tag into a data framethat contains an S-VLAN4 tag, and forwards the data frames to NE4.

4. NE4 strips the S-VLAN3 tags and S-VLAN4 tags and forwards the data frames to theEthernet ports of customer a and customer b.

The data frame processing flow from NE4 to NE1 is reverse to the previous flow.

21.5 Planning GuidePlan related parameters according to the specific application of the QinQ feature.



21-7

PrerequisiteYou must have an understanding of the specific application of the QinQ feature.

ProcedureStep 1 Plan the network attributes of the ports according to the actual requirements.

Follow these three 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 betranslated, select the line services between C-aware ports.

l If S-VLAN tags need to be added/stripped, select the line services between a C-aware portand an S-aware port.

l If packets need to be forwarded according to S-VLAN tags or S-VLAN tags need to betranslated, select the line services between S-aware ports.

Step 2 Select a QinQ operation type according to the actual requirements.

Follow these two 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.

l Check whether unidirectional operations or bidirectional operations are required.

Step 3 Allocate S-VLAN tags for customers.

Follow these two principles when planning S-VLAN tags:

l The S-VLAN tag allocated to each customer must be unique.l If a customer requires multiple S-VLAN tags, allocate a section of consecutive S-VLAN tags

to the customer. For example, allocate 100–109 to customer a and 110–119 to customer b.

----End

ExampleThe following describes how to plan QinQ line services. The QinQ services illustrated in Figure21-4 are provided as an example. The ports used in this example are shown in Figure 21-5.

Figure 21-5 Ports used by the QinQ line services

NE1PORT1

PORT2

PORT1

PORT2

VCTRUNK1

VCTRUNK1

VCTRUNK1VCTRUNK2VCTRUNK2

VCTRUNK1

NE2 NE3

NE4

Servicenetwork A

Servicenetwork B


Feature Description


Issue 02 (2008-06-20)

1. Plan the network attributes of the ports.In the case of NE1 and NE4, because NE1 and NE4 need to add/strip S-VLAN tags, planthe network attribute of the related PORTs as C-Aware and the network attribute of therelated VCTRUNKs as S-Aware.In the case of NE2 and NE3, because NE2 and NE3 need to forward packets according toS-VLAN tags, plan the network attribute of the related VCTRUNKs as S-Aware.

2. Plan QinQ operation types.In the case of NE1 and NE4, because NE1 and NE4 can forward all the packets based onports and do not need to recognize the packet type, select the bidirectional "Add S-VLAN"operation.In the case of NE2, because NE2 needs to transparently transmit packets according to S-VLAN tags, select the bidirectional "Transparently transmit S-VLAN" operation.In the case of NE3, because NE3 needs to translate S-VLAN tags according to S-VLANtags and does not translate S-VLAN tags based on ports, select the bidirectional "TranslateS-VLAN" operation.

3. Plan S-VLAN tags.Plan S-VLAN tags on an overall basis. The S-VLAN tags allocated to customer a andcustomer b by service provider A are 100 and 110 respectively, and the S-VLAN tagsallocated to customer a and customer b by service provider B are 200 and 210 respectively.

21.6 Configuration GuideThis topic describes the configuration flow and the corresponding configuration tasks of theQinQ line service. An example is provided as a supplement to the configuration.

21.6.1 Configuration FlowThis topic describes the configuration flow of the QinQ line service.



21-9

Figure 21-6 Configuration flow for the QinQ line service

Start

Configure the external port of theEthernet board

2

Configure the internal port of theEthernet board

3

End

Create cross-connectionsfor Ethernet services

5

Create QinQ line services

4

Is the type field ofQinQ frames processed by the

interconnected equipmentset to "0x8100"?

Modify the type field of QinQ frames

1No

Yes

Table 21-5 Description of the configuration flow of the QinQ line service

Number Description

① For the configuration process, see 21.6.2 Modifying the Type Field of QinQFrames.

② For the configuration process, see 16.6.1 Configuring the External Port ofthe Ethernet Board.

③ For the configuration process, see 17.6 Configuring the Internal Port of theEthernet Board.

④ For the configuration process, see 21.6.3 Creating QinQ Line Services.

⑤ Create the cross-connection from the paths that are bound to the VCTRUNKto the corresponding timeslots on the line.


Feature Description


Issue 02 (2008-06-20)

NOTE

If the QoS of the QinQ line service needs to be set, see 20 QoS.

21.6.2 Modifying the Type Field of QinQ FramesBy default, the type field (that is, the TPID in an S-TAG) of QinQ frames processed by Ethernetswitching boards is set to "0x8100".




Procedure

Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet InterfaceManagement > Advanced Attributes from the Function Tree.

Step 2 Modify the type field of QinQ frames.

Step 3 Click Apply.

----End


QinQ Type Area(Hexadecimal)

- 81 00 This parameter specifies the type field ofQinQ frames. Set this parameter accordingto the type field of the accessed QinQframes.

21.6.3 Creating QinQ Line ServicesTo enable the Ethernet switching board to transmit QinQ line services, perform this task toconfigure the related information such as service source and service sink.





21-11

Precautions


Procedure

Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > EthernetService > 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.

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 consistentwith the result of directly configuring the Ethernet service port attributes.

Step 6 Click OK.

----End


Feature Description


Issue 02 (2008-06-20)


Service Type EPL, EVPL(QinQ) EPL When creating the QinQ line service, set thisparameter to EVPL(QinQ).


Bidirectional l When this parameter is set toUnidirectional, only the service from theservice source to the service sink iscreated.

l When this parameter is set toBidirectional, both the service from theservice source to the service sink and theservice from the service sink to theservice source are created.

l Generally, it is recommended that youuse the default value.

Operation Type Transparentlytransmit C-VLAN,Translate C-VLAN,Add S-VLAN,Transparentlytransmit S-VLAN,Translate S-VLAN,Strip S-VLAN (onlyfor unidirectionalservices)

Add S-VLAN l For the meanings of the values, see 21.1.4Application of the QinQ Technology inLine Services.


Source Port A specific PORT orVCTRUNK

PORT1 l This parameter indicates the port wherethe service source resides.

l When creating the bidirectional Ethernetservice from a PORT to a VCTRUNK, itis recommended that you use a specificPORT as the source port.



21-13


Source C-VLAN(e.g. 1,3-6)

1 to 4095 - l You can set this parameter to null, anumber, or several numbers. When youset this parameter to several numbers, use"," to separate these discrete values anduse "–" to indicate continuous numbers.For example, "1, 3–6" indicates numbers1, 3, 4, 5, and 6.

l The number of C-VLANs set in thisparameter should be the same as thenumber of C-VLANs set in Sink C-VLAN (e.g. 1,3-6).

l When you set this parameter to null, allthe services of the source port work as theservice source.

l When you set this parameter to a non-nullvalue, only the services of the source portwhose C-VLAN IDs are included in theset value range of this parameter work asthe service source.

Source S-VLAN 1 to 4095 - l This parameter must be set to a numericalvalue.

l Only the services of the source portwhose S-VLAN IDs are equal to thevalue of this parameter work as theservice source.

Sink Port A specific PORT orVCTRUNK

PORT1 l This parameter indicates the port wherethe service sink resides.

l Do not set the value of this parameter tothe same as the value of Source Port.

l When creating the bidirectional Ethernetservice from a PORT to a VCTRUNK, itis recommended that you use a specificVCTRUNK as the sink port.


Feature Description


Issue 02 (2008-06-20)


Sink C-VLAN (e.g.1,3-6)

1 to 4095 - l You can set this parameter to null, anumber, or several numbers. When youset this parameter to several numbers, use"," to separate these discrete values anduse "–" to indicate continuous numbers.For example, "1, 3–6" indicates numbers1, 3, 4, 5, and 6.

l The number of VLANs set in thisparameter should be the same as thenumber of VLANs set in Source C-VLAN (e.g. 1,3-6).

l When you set this parameter to null, allthe services of the sink port work as theservice sink.

l When you set this parameter to a non-nullvalue, only the services of the sink portwhose C-VLAN IDs are included in theset value range of this parameter work asthe service sink.

Sink S-VLAN 1 to 4095 - l This parameter must be set to a numericalvalue.

l Only the services of the sink port whoseS-VLAN IDs are equal to the value of thisparameter work as the service sink.

S-VLAN Priority AUTO, Priority0–Priority7

AUTO l This parameter is valid only whenOperation Type is set to Add S-VLAN.

l This parameter specifies the priority ofthe newly added S-VLAN tag.

l When this parameter is set to AUTO, thepriority of the S-VLAN tag is 0.

l When QoS operations do not need to beperformed according to the S-VLANpriority, it is recommended that you usethe default value.

Port Enabled Enabled, Disabled - When the source port or the sink port is setto a PORT, set Port Enabled to Enabled.

21.6.4 Configuration ExampleThis topic provides an example to describe how to configure QinQ line services.



21-15

PrecautionsNOTE

l For details on the services configured in this example, refer to the description of the QinQ line services in21.5 Planning Guide.

Procedure

Step 1 Set the port attributes of the ports of NE1 and NE4. For details, see 16.6.1 Configuring theExternal Port of the Ethernet Board.

Step 2 Set the port attributes of the VCTRUNKs of NE1–NE4. For details, see 17.6 Configuring theInternal Port of the Ethernet Board.

Step 3 Configure a QinQ service from PORT1 to VCTRUNK1 of NE1. For details, see 21.6.3 CreatingQinQ Line Services.


l Set Direction to Bidirectional.

l Set Operation Type to Add S-VLAN.


l Do not set Source C-VLAN (e.g. 1,3-6).


l Do not set Sink C-VLAN (e.g. 1,3-6).

l Set Sink S-VLAN to 100.

Step 4 Configure a QinQ service from PORT2 to VCTRUNK1 of NE1. For details, see 21.6.3 CreatingQinQ Line Services.



l Set Operation Type to Add S-VLAN.


l Do not set Source C-VLAN (e.g. 1,3-6).


l Do not set Sink C-VLAN (e.g. 1,3-6).


Step 5 Configure the QinQ services of NE4. For details, see Step 3–Step 4.

Step 6 Configure the QinQ service to which the traffic stream of customer a at NE2 corresponds. Fordetails, see 21.6.3 Creating QinQ Line Services.



l Set Operation Type to Transparently transmit S-VLAN.



Feature Description


Issue 02 (2008-06-20)

l Set Source S-VLAN to 100.



Step 7 Configure the QinQ service to which the traffic stream of customer b at NE2 corresponds. Fordetails, see 21.6.3 Creating QinQ Line Services.



l Set Operation Type to Transparently transmit S-VLAN.





Step 8 Configure the QinQ service to which the traffic stream of customer a at NE3 corresponds. Fordetails, see 21.6.3 Creating QinQ Line Services.



l Set Operation Type to Translate S-VLAN.

l Set Source Port to VCTRUNK2.




Step 9 Configure the QinQ service to which the traffic stream of customer b at NE3 corresponds. Fordetails, see 21.6.3 Creating QinQ Line Services.



l Set Operation Type to Translate S-VLAN.

l Set Source Port to VCTRUNK2.





----End

21.7 Maintenance GuideThis topic describes alarms and performance events relevant to the QinQ feature, and problemsthat occur frequently during the application of the QinQ feature.



21-17

21.7.1 Relevant Alarms and EventsThe QinQ feature may cause RMON performance changes.



Relevant RMON Performance EventsFor details, see 22.1.3 List of RMON Alarm Entries and List of RMON PerformanceEntries.

21.7.2 FAQsThis 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 vendorsfail?


l The QinQ type field (that is, the TPID in an S-TAG) varies between the equipment ofdifferent vendors. The OptiX equipment uses "0x8100".

l The standards for the QinQ feature are being developed. The principles for adding tags aredifferent between vendors.


Feature Description


Issue 02 (2008-06-20)

22 Remote Monitoring Feature

About This Chapter

The remote monitoring (RMON) feature is used to monitor the data traffic on a network segmentor on an entire network. Currently, the RMON standard is one of the most widely applied networkmanagement standards.

22.1 Feature DescriptionThe RMON feature is based on the management information base (MIB) in the architecture ofthe simple network management protocol (SNMP).

22.2 AvailabilityThe RMON feature requires support of the involved equipment and boards.

22.3 Relation with Other FeaturesThe RMON function is a basic function of the Ethernet board. The RMON function does nothave impact on other Ethernet features, and the other Ethernet features do not also have impacton the RMON function. The other Ethernet features, however, affect the performance datacounted by the RMON function.

22.4 Realization PrincipleThe RMON agent is embedded in an Ethernet board. The Web LCT server or T2000 serverfunctions as the NMS. The NMS exchanges data information with the agent through basic SNMPcommands. Thus, the statistical network data is collected.

22.5 Planning GuidePlan related parameters according to the specific application of the RMON function.

22.6 Configuration GuideThe RMON function need not be configured and can be directly used.

22.7 Maintenance GuideThis topic describes how to use the RMON function and describes the problems that occurfrequently during the application of the RMON function.

OptiX RTN 600 Radio Transmission SystemFeature Description 22 Remote Monitoring Feature


22-1

22.1 Feature DescriptionThe RMON feature is based on the management information base (MIB) in the architecture ofthe simple network management protocol (SNMP).

22.1.1 SNMPCurrently, 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 nodesin the network. This facilitates the network administrator to retrieve information, modifyinformation, locate a fault, diagnose a fault, plan capacity, and generate a report on any node inthe network.

Architecture of the SNMP

The SNMP is divided into the network management station (NMS) and the agent.

l NMS

The NMS is a workstation where the client program is running. When the RMON functionis used, the Web LCT or T2000 server functions as the NMS.

l Agent

The agent is the server software that is running on the network equipment. When the RMONfunction is used, the agent is embedded in the Ethernet board.

The NMS can send the GetRequest, GetNextRequest, or SetRequest packet to the agent. Onreceiving such a request packet, the agent reads or writes the packet according to the type of thepacket, 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 theNMS.

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 inthe equipment. The overall architecture is like a tree. The nodes on the tree indicate the managedobjects. Each node can be uniquely identified by a path starting from the root. The MIB is usedto describe the architecture of the tree and is the collection of the definitions of the standardvariables of the monitored network equipment. The RMON is a common MIB defined accordingto IETF RFC2819.

22.1.2 RMON Management GroupsThe Ethernet board provides the following RMON management groups specified in IETFRFC2819: statistics group, history group, alarm group, and history control group.

22 Remote Monitoring FeatureOptiX RTN 600 Radio Transmission System

Feature Description


Issue 02 (2008-06-20)

Statistics GroupThe statistics group counts the absolute performance values from the time the statistics group iscreated until the current time.

The Ethernet board supports port-based statistics groups. In the case of a board, you can createa statistics group for only one port. The sampling interval of a statistics group can be set. Thevalue range of the sampling interval is from 1 second to 100 seconds. For the performance entriesthat can be added to a statistics group, see 22.1.3 List of RMON Alarm Entries and List ofRMON Performance Entries.

Alarm GroupThe alarm group monitors the specified alarm objects (for example, the performance data ofports). When the value of the monitored data crosses the configured threshold, an alarm eventis generated.

The Ethernet board supports port-based alarm groups. You can create only one alarm group fora board. The number of alarm entries in an alarm group must not exceed ten. You can set thefollowing 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 threshold-crossing, report all), upper threshold, and lower threshold. For the alarm entries that can be addedto an alarm group, see 22.1.3 List of RMON Alarm Entries and List of RMON PerformanceEntries.

History Control GroupThe history control group specifies the methods of monitoring history performance data. TheEthernet board periodically collects the required statistical network information and temporarilystores the information in the board according to the attributes of the history control group. Thehistory control group has the following attributes:

l History table typeYou can set the history table type to 30-second, 30-minute, custom period 1, or customperiod 2. In the case of a custom period, you need to manually set the required samplinginterval.

l Monitored objectThis specifies the port on which performance data is collected. You can set monitoredobjects for each history table type.

l Number of itemsThis specifies the number of history performance data entries that are stored in the Ethernetboard. Because the history performance data is stored in the wrap mode, the stored data isthe latest history performance data. For example, if the number of items is set to 10, theEthernet board stores the latest ten history performance data entries. You can set the numberof items for each history table type. The number of items can be set to 50 at most.

History GroupThe history group specifies the methods of querying history performance data. The Ethernetboard filters the history performance data stored in the board according to the attributes of thehistory group and returns the history performance data that meets the filtering conditions. Thehistory group has the following attributes:



22-3

l History table type

This specifies the sampling period to which the history performance data corresponds. Youcan set the history table type to 30-second, 30-minute, custom period 1, or custom period2.

l Monitored object

This specifies the port to which the history performance data corresponds.

l Performance entry

This specifies the performance entries to which the history performance data corresponds.The list of performance entries is the same as the list of the performance entries that canbe added into a statistics group.

l Query conditions

This specifies the relative time to which the history performance data corresponds. 1represents the oldest item. You can query a maximum of ten entries at a time.

22.1.3 List of RMON Alarm Entries and List of RMON PerformanceEntries

The RMON alarm entries and RMON performance entries supported by the Ethernet serviceprocessing board comply with RFC2819.

Table 22-1 List of RMON alarm entries

Alarm Name Description

DropEvent The total number of events in which packets are dropped crossesa threshold.

UndersizePkts The number of undersized packets crosses a threshold.

OversizePkts The number of oversized packets crosses a threshold.

Fragments The number of fragments crosses a threshold.

Jabbers The number of jabbers crosses a threshold.

FCSErrors The number of the packets with FCS errors crosses a threshold.

Table 22-2 List of RMON performance entries

Category ofPerformanceEntries

Name of a Performance Entry

Basic performance Packets received (64 octets in length) (packets/second)

Packets received (65–127 octets in length) (packets/second)




Feature Description


Issue 02 (2008-06-20)





Drop events (times/second)

Multicast packets received (packets/second)

Broadcast packets received (packets/second)

Undersize packets received (packets/second)

Oversize packets received (packets/second)

Fragments (packets/second)

Jabbers (packets/second)

Octets received (bytes/second)

Packets received (packets/second)

Extendedperformance

Packets transmitted (64 octets in length) (packets/second)

Packets transmitted (65–127 octets in length) (packets/second)





Unicast packets received (packets/second)

Unicast packets transmitted (packets/second)

Multicast packets transmitted (packets/second)

Broadcast packets transmitted (packets/second)

Pause frames received (frames/second)

Pause frames transmitted (frames/second)

FCS errors (frames/second)

Packets received and transmitted (64 octets in length) (packets/second)

Packets received and transmitted (65–127 octets in length) (packets/second)

Packets received and transmitted (128–255 octets in length)(packets/second)



22-5






Good full frame speed received (bytes/second)

Good full frame speed transmitted (bytes/second)

Good full frame octets received (bytes/second)

Good full frame octets transmitted (bytes/second)

Control frames received (frames/second)

Packets transmitted (packets/second)

Octets transmitted (bytes/second)

VCG performance Octets received (bytes/second)

Octets transmitted (bytes/second)

Packets received (packets/second)

Packets transmitted (packets/second)

Good packets received (packets/second)

Good packets transmitted (packets/second)

Full frame speed received (bytes/second)

Full frame speed transmitted (bytes/second)

NOTE

The PORTs of the EMS6 board and EFT4 board support basic performance entries and extended performanceentries. The VCTRUNKs of the EMS6 board support VCG performance entries. The VCTRUNKs of the EFT4board do not support RMON performance entries.

22.2 AvailabilityThe RMON feature requires support of the involved equipment and boards.


Feature Description


Issue 02 (2008-06-20)

Table 22-3 Availability of the RMON feature


RMON EFT4 (all the versions) IDU 610/620


NOTE

The EFT4 board supports the remote monitoring of PORTs only, whereas the EMS6 board supports the remotemonitoring of both PORTs and VCTRUNKs.

22.3 Relation with Other FeaturesThe RMON function is a basic function of the Ethernet board. The RMON function does nothave impact on other Ethernet features, and the other Ethernet features do not also have impacton the RMON function. The other Ethernet features, however, affect the performance datacounted by the RMON function.

22.4 Realization PrincipleThe RMON agent is embedded in an Ethernet board. The Web LCT server or T2000 serverfunctions as the NMS. The NMS exchanges data information with the agent through basic SNMPcommands. Thus, the statistical network data is collected.

Statistics GroupThe processing flow is as follows:

1. A maintenance engineer clicks Resetting begins.2. The NMS sends the corresponding request packet to the RMON agent.3. The RMON agent embedded in the Ethernet board resets the corresponding current

performance counting register and returns the corresponding response packet to the NMSaccording to the information of the statistics group in the request packet.

4. The NMS sends a request packet to the RMON agent every sampling interval. The RMONagent returns the value of the current performance counting register through the responsepacket.

5. The maintenance engineer clicks Stop.6. The NMS stops sending the corresponding request packet to the RMON agent.

NOTE

l If the maintenance engineer clicks Start, the RMON agent does not reset the performance counting register.

l If the maintenance engineer does not select Display Accumulated Value, the NMS obtains the performancevalue of a sampling interval by performing a subtraction operation between the sampled value returned atthe end of the sampling interval and the sampled value returned at the end of the previous sampling interval.

Alarm GroupThe processing flow is as follows:



22-7

1. The maintenance engineer clicks Apply.2. The NMS sends the corresponding request packet to the RMON agent.3. 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.4. When the alarm object crosses the configured threshold in the corresponding direction, the

RMON agent sends the corresponding trap packet to the NMS.5. The NMS generates the corresponding RMON alarm according to the information in the

packet.

History Control GroupThe processing flow is as follows:

1. The maintenance engineer clicks Apply.2. The NMS sends the corresponding request packet to the RMON agent.3. 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 historyperformance register according to the information of the history control group in the requestpacket.

History GroupThe processing flow is as follows:

1. The maintenance engineer clicks Query.2. The NMS sends the corresponding request packet to the RMON agent.3. 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 NMSthrough the response packet according to the information of the history group in the requestpacket.

22.5 Planning GuidePlan related parameters according to the specific application of the RMON function.

Prerequisitel You must have an understanding of the functions of the RMON management groups.

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

Follow these three principles when selecting RMON management groups:

l When you need to monitor the current performance of a port in real time, select the statisticsgroup.

l When you need to monitor certain performance items of a port in a long term, select the alarmgroup.


Feature Description


Issue 02 (2008-06-20)

l When you need to perform a statistical analysis on the performance of a port over a pastperiod of time, select the history group and history control group.

Step 2 Select proper statistical items.

Follow these four principles when selecting statistical items:

l When you need to analyze the exceptions occurred on a port, select the following statisticalitems: fragments, undersize packets received, FCS errors, pause frames received, pauseframes transmitted, and others.

l When you need to analyze the traffic on a port, select the following statistical items: octetsreceived, octets transmitted, and others.

l When you need to analyze the information on packet transmitting and packet receiving on aport, select the following statistical items: packets received, packets transmitted, and others.

l When you need to analyze the types of the transmitted and received packets on a port, selectthe following statistical items: unicast packets received, unicast packets transmitted,multicast packets received, multicast packets transmitted, broadcast packets received,broadcast packets transmitted, and others.

----End

22.6 Configuration GuideThe RMON function need not be configured and can be directly used.

22.7 Maintenance GuideThis topic describes how to use the RMON function and describes the problems that occurfrequently during the application of the RMON function.

22.7.1 Browsing the Performance Data in the Statistics Group of anEthernet Port

After you configure an RMON statistics group for an Ethernet port, you can browse the real-time statistical performance data of the port.




Procedure

Step 1 Select the Ethernet board in the NE Explorer. Choose Performance > RMON Performancefrom the Function Tree.

Step 2 Click the Statistics Group tab.



22-9

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


Sampling Interval 5 seconds to 150seconds

5 This parameter specifies the period ofsampling the performance data.

DisplayAccumulated Value

Selected, Notselected

Not selected This parameter specifies whether thedisplayed performance value is theincrement of the register value comparedwith the register value at the end of theprevious sampling interval or the currentabsolute value of the register.

22.7.2 Configuring an Alarm Group for an Ethernet PortAfter you configure an RMON alarm group for an Ethernet port, you can monitor whether theperformance value of the port crosses the configured thresholds in a long term.



Precautions


Procedure


Step 2 Click the Alarm Group tab.

Step 3 Set the required parameters for the alarm group.

Step 4 Click Apply.

----End


Feature Description


Issue 02 (2008-06-20)

Parameters


Sampling Interval(s)

5 to 150 5 This parameter specifies the period ofsampling the performance data.

Report Mode Report All, Reportin Case of UpperThreshold-Crossing, Report inCase of LowerThreshold-Crossing

Report All This parameter specifies the mode in whichan alarm event is reported when theperformance data crosses a threshold.

Upper Threshold 1 to 4294967295 1 This parameter specifies the upper thresholdfor the performance data.

Lower Threshold 0 to 4294967294 0 This parameter specifies the lower thresholdfor the performance data.

Monitor Status Enabled, Disabled Disabled This parameter specifies whether to monitorthe alarm object.

22.7.3 Configuring a History Control GroupWhen configuring a history control group for an Ethernet port, you configure how the historyperformance data of the port is monitored. The Ethernet board monitors the history performancedata of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50history performance data items.



Precautions


Procedure


Step 2 Click the History Control Group tab.

Step 3 Set the required parameters for the history control group.

Step 4 Click Apply.

----End



22-11


History Table Type 30-Second, 30-Minute, CustomPeriod1, CustomPeriod2

30-Second This parameter specifies the period ofsampling the history performance data.

Sampling Interval(s)

l 300–43200(custom period 1)

l 300–86400(custom period 2)

l 900 (customperiod 1)

l 86400 (customperiod 2)

This parameter is valid only when HistoryTable Type is set to Custom Period1 orCustom Period2. This parameter specifiesthe period of sampling the performancedata.

Number of Items 1 to 50 50 This parameter specifies the number ofperformance data items.

Monitor Status Enabled, Disabled Disabled This parameter specifies whether to monitorthe object.

22.7.4 Browsing the Performance Data in the History Group of anEthernet Port

After you configure an RMON history group for an Ethernet port, you can browse the statisticalhistory performance data of the port.



l The monitored objects and the corresponding history table type must be set in the HistoryControl Group tab.


Procedure


Step 2 Click the History Group tab.

Step 3 Set the required parameters for the history group.


Feature Description


Issue 02 (2008-06-20)

Step 4 Click Query.

----End


History Table Type 30-Second, 30-Minute, CustomPeriod1, CustomPeriod2

30-Second This parameter specifies the period ofsampling the history performance data.

Start Item 1 to 50 1 This parameter specifies the item fromwhich the system queries the historyperformance data. 1 represents the oldestitem.

End Item 1 to 50 1 This parameter specifies the item afterwhich the system stops querying the historyperformance data. The value of thisparameter must not be more than the sum ofStart Item and 9.

22.7.5 FAQsThis 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 thefollowing scenarios:

l Analyzing the exceptions occurred on a portFocus 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 auto-negotiation but the working mode at the other end is set to full-duplex.

– Undersize packets receivedWhen undersize 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



22-13

the Ethernet board is faulty by using another Ethernet port or replacing the Ethernetboard.

– Oversize packets receivedGenerally, the setting of the maximum frame length to a too small value causes theoccurrence of oversize packets.

– FCS errorsWhen the packets with FCS errors occur, first check whether the port modes match eachother, then check the quality of the network cable, and finally check whether thehardware of the Ethernet board is faulty by using another Ethernet port or replacing theEthernet board.

– Pause frames received and pause frames transmittedWhen 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 onports from being controlled.

l Analyzing the information on packet transmitting and packet receiving on each port of aserviceFor example, when two PORTs share one VCTRUNK to provide a line service, you cancount the packets received on the two PORTs and compare the total number of the receivedpackets with the number of the packets transmitted by the VCTRUNK to judge whether apacket loss occurs.

l Analyzing the traffic on a portFor example, in the case of a transparently transmitted service from a PORT to aVCTRUNK, you can count the bytes received and the bytes transmitted on the PORT andcompare the number of the bytes with the bandwidth of the VCTRUNK to judge whetherthe bandwidth bound by the VCTRUNK is appropriate.

l Analyzing the types of packetsFor example, in the case of a PORT mounted by a bridge, you can count the receivedbroadcast packets and the received packets and calculate the ratio of the broadcast packetsto the received packets to judge whether a broadcast storm occurs on the equipment on theopposite side.


Feature Description


Issue 02 (2008-06-20)

A Glossary

F

FD Frequency Diversity. Two or more microwave frequencies with certainfrequency space are used to transmit/receive the same signal andselection is then performed between the two signals to ease the impactof fading.

G

Gateway NE Gateway Network Element. A gateway NE is the NE connected to theNMS through an Ethernet cable or a serial port cable. Non-gateway NEsare connected to the gateway NE through the ECC channel and thuscommunicate with the NMS through the gateway NE. The gateway NEis the necessary route for the NMS to manage the entire network.

I

IDU Indoor Unit. The indoor unit implements accessing, multiplexing/demultiplexing, and IF processing for services.

IF Intermediate Frequency. IF is the transitional frequency between thefrequencies of a modulated signal and an RF signal

L

Line board A board that processes the services carried on line. As the OptiX RTN600 involves SDH fiber line, STM-1 cable line, and microwave line, theline boards include SDH optical interface board, STM-1 electricalinterface board, and IF board.

N

OptiX RTN 600 Radio Transmission SystemFeature Description A Glossary


A-1

NE Network Element. An NE contains both the hardware and the softwarerunning on it. One NE is at least equipped with one SCC board whichmanages and monitors the entire network element. NE software runs onthe SCC board.

NMS A network management system in charge of the network OAM.

Non-primarystation

The RTN 600 microwave station on which the transmitted frequency islower than the received frequency.

Multiplex sectionprotection

The function performed to provide capability for switching a signalbetween and including two MST functions, from a "working" to a"protection" channel.

O

ODU Outdoor Unit. The outdoor unit implements frequency conversion andamplification for RF signals.

P

PDH Plesiosynchronous Digital Hierarchy. A multiplexing scheme of bitstuffing and byte interleaving. It multiplexes the minimum rate 64 kit/sinto the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s and 565 Mbit/s rates.

Primary station The RTN 600 microwave station on which the transmitted frequency ishigher than the received frequency.

S

SD Space Diversity. Two or more antennas separated by a specific distancetransmit/receive the same signal and selection is then performed betweenthe two signals to ease the impact of fading. Currently, only receive SDis used.

SDH Synchronous Digital Hierarchy. A hierarchical set of digital transportstructures, standardized for the transport of suitably adapted payloadsover physical transmission networks.

Service board Line boards and tributary boards excluding IF boards.

Subnet The logical entity in the transmission network and comprises a group ofnetwork management objects. A subnet can contain NEs and othersubnets. A subnet planning can enhance the organization of a networkview.

Subnetworkconnectionprotection

A working subnetwork connection is replaced by a protectionsubnetwork connection if the working subnetwork connection fails, or ifits performance falls below a required level.

T

A GlossaryOptiX RTN 600 Radio Transmission System

Feature Description

A-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

T2000 A subnet management system (SNMS). In the telecommunicationmanagement network architecture, the T2000 is located between the NElevel and network level, which can supports all NE level functions andpart of the network level management functions.

Trail A type of transport entity, mainly engaged in transferring signal from theinput of the trail source to the output of the trail sink, and monitoring theintegrality of the transferred signal.

V

VCTRUNK A virtual concatenation group applied in data service mapping, alsocalled the internal port of a data service processing board.

Virtualconcatenationgroup

A group of co-located member trail termination functions that areconnected to the same virtual concatenation link.

W

Web LCT Web LCT is located in the NE management layer of an opticaltransmission network. It performs management for a single NE.

OptiX RTN 600 Radio Transmission SystemFeature Description A Glossary


A-3

B Acronyms and Abbreviations

A

APS Automatic Protection Switching

ARP Address Resolution Protocol

ATPC Automatic Transmit Power Control

AU Administrative Unit

B

BER Bit Error Rate

BIP Bit-Interleaved Parity

BPDU Bridge Protocol Data Unit

C

CAR Committed Access Rate

CBS Committed Burst Size

CCDP Co-Channel Dual Polarization

CGMP Cisco Group Management Protocol

CIR committed information rate

CLNP connectionless network protocol

CLNS Connectionless Network Service

CoS Class of Service

CPU Central Processing Unit

CRC cyclic redundancy check

CVLAN Customer VLAN

OptiX RTN 600 Radio Transmission SystemFeature Description B Acronyms and Abbreviations


B-1

C-VLAN Customer VLAN

D

DC Direct Current

DCC Data Communications Channel

DCN Data Communication Network

DSCP differentiated services code point

DVMRP Distance Vector Multicast Routing Protocol

E

ECC Embedded Control Channel

EPL Ethernet Private Line

EPLAN Ethernet Private LAN

ES-IS End System to Intermediate System

EVPL Ethernet Virtual Private Line

F

FCS Frame Check Sequence

FD Frequency Diversity

FE Fast Ethernet

FIFO First In First Out

FLP Fast Link Pulse

FTP file transfer protocol

G

GE Gigabit Ethernet

GFP Generic Framing Procedure

GTS Generic Traffic Shaping

GUI Graphical User Interface

H

HDLC High level Data Link Control procedure

B Acronyms and AbbreviationsOptiX RTN 600 Radio Transmission System

Feature Description

B-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

HSB Hot Standby

HSM Hitless Switch Mode

I

ICMP Internet Control Message Protocol

IDU Indoor Unit

IEEE Institute of Electrical and Electronics Engineers

IETF The Internet Engineering Task Force

IF Intermediate Frequency

IGMP Internet Group Management Protocol

IP Internet Protocol

IPv6 Internet Protocol version 6

IS-IS Intermediate System to Intermediate System

ISO International Standard Organization

ITU-T International Telecommunication Union - TelecommunicationStandardization Sector

IVL Independence VLAN learning

L

LAN Local Area Network

LAPD Link Access Procedure on the D channel

LAPS Link Access Procedure-SDH

LCAS Link Capacity Adjustment Scheme

LCT Generation-Local Craft Terminal

LMSP Linear Multiplex Section Protection

M

MAC Medium Access Control

MBS Maximum Burst Size

MDI Medium Dependent Interface

MIB Management Information Base

MPLS multiprotocol label switching

MSP Multiplex Section Protection



B-3

MTU Maximum Transmission Unit

N

NE Network Element

NLP Normal Link Pulse

NMS Network Management System

NNI Network-to-Network Interface or Network Node Interface

NSAP Network Service Access Point

O

ODU Outdoor Unit

OSI Open Systems Interconnection

OSPF Open Shortest Path First

P

PDH Plesiochronous Digital Hierarchy

PIM-DM Protocol Independent Multicast-Dense Mode

PIM-SM Protocol Independent Multicast-Sparse Mode

PPP Point-to-Point Protocol

Q

QinQ 802.1Q in 802.1Q

QoS Quality of Service

R

RF radio frequency

RFC Request For Comment

RIP Routing Information Protocol

RMON Remote Monitoring

RSL Received Signal Level

RSTP Rapid Spanning Tree Protocol

RTN Radio Transmission Node


Feature Description


Issue 02 (2008-06-20)

S

SD Space Diversity

SDH Synchronous Digital Hierarchy

SNC SubNetwork Connection

SNCP Sub-Network Connection Protection

SNMP Simple Network Management Protocol

SNR Signal-to-Noise Ratio

STM Synchronous Transport Module

STM-1 SDH Transport Module -1

STM-1e STM-1 Electrical Interface

STM-1o STM-1 Optical Interface

STM-4 SDH Transport Module -4

STM-N SDH Transport Module -N

STP Spanning Tree Protocol

SVL Shared VLAN Learning

T

TCI Tag Control Information

TCP Transfer Control Protocol

TU Tributary Unit

U

UDP User Datagram Protocol

UNI user-network interface

V

VC Virtual Container

VC12 Virtual Container -12

VC-12 Virtual Container -12





B-5



VCG Virtual Concatenation Group

VLAN Virtual LAN

VoIP Voice over IP

VPN Virtual Private Network

W

WAN Wide Area Network

WRR Weighted Round Robin

WTR Wait to Restore Time

X

XPD Cross-Polarization Discrimination

XPIC Cross-polarization interference cancellation


Feature Description


Issue 02 (2008-06-20)

Index

Symbols/Numerics1+1 FD

alarm, 8-11availability, 8-7configuration, 7-9configuration guide, 8-10configuration, IDU 605, 7-12event, 8-11FAQ, 8-11introduction, 8-2maintenance guide, 8-11planning guide, 8-10protection type, 8-4realization principle, 8-8relation with other features, 8-8switching condition, 8-5switching impact, 8-7switching operation, 7-15system configuration, 8-2

1+1 HSBalarm, 7-15availability, 7-5configuration, 7-9configuration guide, 7-8configuration, IDU 605, 7-12event, 7-15FAQ, 7-15introduction, 7-2maintenance guide, 7-14planning guide, 7-8protection type, 7-3realization principle, 7-6relation with other features, 7-6switching condition, 7-3switching impact, 7-5switching operation, 7-15system configuration, 7-2

1+1 SDalarm, 9-10availability, 9-6configuration, 7-9configuration guide, 9-10configuration, IDU 605, 7-12

event, 9-10FAQs, 9-11introduction, 9-2maintenance guide , 9-10planning guide, 9-9protection type, 9-3realization principle, 9-7relation with other features, 9-7switching impact , 9-6switching operation, 7-15system configuration, 9-2

AATPC

alarm, 12-7availability, 12-2configuration, 12-4event, 12-7FAQ, 12-7introduction, 12-2maintenance guide, 12-7planning guide, 12-4realization principle, 12-3relation with other features, 12-3

auto-negotiationavailability, 16-5introduction, 16-2realization principle, 16-6

Bbridge

availability, 19-7planning guide, 19-15realization principle, 19-8relation with other features, 19-7type, 19-2

CCAR

algorithm, 20-5binding, 20-17configuration, 20-12

OptiX RTN 600 Radio Transmission SystemFeature Description Index


i-1

introduction, 20-2CCDP, 10-2CLNS role, configuring, 4-12communication parameters, modifying, 2-18converting

normal services to SNCP services, 13-13SNCP services to normal services, 13-16

CoSbinding, 20-17configuration, 20-15introduction, 20-3

creating NE by using the T2000manual method, 2-26search method, 2-24

DDCC transparent transmission

Configuring, 2-22DCC transparent transmission solution

alarm, 5-11availability, 5-5configuration example, 5-10configuration flow, 5-8configuration guide, 5-8event, 5-11FAQ, 5-11introduction, 5-3maintenance guide, 5-11planning guide, 5-6realization principle, 5-5relation with other features, 5-5

DCC transparent transmission through the externalclock interface

alarm, 6-8availability, 6-4configuration example, 6-8configuration flow, 6-7configuration guide , 6-7FAQs, 6-9introduction, 6-3maintenance guide, 6-8planning guide, 6-5realization principle, 6-4relation with other features, 6-4

DCC, configuring, 2-19DCN

constitution, 1-2solution, 1-3

EECC route

how to establish, 2-7querying, 2-23

egress queue schedulingalgorithm, 20-7

encapsulation protocol

alarm, 17-24availability, 17-4event, 17-24FAQ, 17-26introduction, 17-3LCAS

alarm, 17-24event, 17-24FAQ, 17-26

planning guide, 17-14realization principle, 17-5virtual concatenation

alarm, 17-24event, 17-24FAQ, 17-26

Ethernet LAN service, configure, 19-16Ethernet line service, configure, 18-9Ethernet port

alarm, 16-16event, 16-16FAQ, 16-17feature description, 16-2planning guide, 16-8

Ethernet portsrelation with other features, 16-5

extended ECCconfiguring, 2-21introduction, 2-4realization principle, 2-10

external port of the Ethernet boardconfiguration, 16-9

external port of the Ethernet board, configuration, 16-9

Fflow

classification, 20-2configuration, 20-9

flow controlavailability, 16-5introduction, 16-4realization principle, 16-7

GGFP

introduction, 17-3realization principle, 17-5

HHub, 19-2Hub/Spoke

configuration, 19-22Hub/Spoke, configure, 19-22HW ECC

alarm, 2-31availability, 2-7

IndexOptiX RTN 600 Radio Transmission System

Feature Description

i-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

configuration example, 2-29configuration flow, 2-14configuration guide, 2-14event, 2-31FAQ, 2-31how to transfer messages, 2-9introduction, 2-2maintenance guide, 2-31planning guide, 2-10protocol stack, 2-2realization principle, 2-7relation with other features, 2-7

IIGMP Snooping

availability, 19-7configure, aging time of the multicast table item,19-33introduction, 19-5planning guide, 19-15principle, 19-13query, running information, 19-36relation with other features, 19-7

internal port of the Ethernet boardconfiguration, 17-15

internal port of the Ethernet board, configuration,17-15IP over DCC

access mode, 3-3alarm, 3-14availability, 3-4configuration example, 3-12configuration flow, 3-9configuration guide, 3-9FAQ, 3-14introduction, 3-2maintenance guide , 3-14planning guide, 3-6protocol stack, 3-2realization principle, 3-5relation with other features, 3-4

IP routeconfiguring, 3-12querying, 3-11

JJumbo frame

availability, 16-5introduction, 16-3modifying the type field, 16-15

LLayer 2 switching

alarm, 19-37availability, 19-7

configuration guide, 19-16event, 19-37FAQs, 19-37maintenance guide, 19-35planning guide, 19-15realization principle, 19-8relation with other features, 19-7

LCASavailability, 17-4introduction, 17-4planning guide, 17-14realization principle, 17-10

linear MSP, 14-1alarm, 14-15availability, 14-6byte K, 14-3configuration, 14-10event, 14-15FAQ, 14-16introduction, 14-2maintenance guide, 14-14planning guide, 14-9protection type, 14-2realization principle, 14-6relation with other features, 14-6starting, 14-14stopping, 14-14switching condition, 14-4switching impact, 14-6switching operation, 14-14

MMAC address table

configure, aging time, 19-26create the entry manually, 19-25introduction, 19-2planning guide, 19-15query, actual capacity, 19-35query, dynamic entry, 19-35

mapping protocolalarm, 17-24availability, 17-4event, 17-24FAQ, 17-26introduction, 17-3planning guide, 17-14realization principle, 17-5

MIB, 22-2Mount port, configure, 19-22MSP ring, two fiber, bidirectional

configuration, 15-8switching operation, 15-11

NN+1 protection

2+1 protection, realization principle, 11-7



i-3

3+1 protection, realization principle, 11-9alarm, 11-17availability, 11-7configuration, 11-12, 11-14configuration example, 11-16configuration flow, 11-11configuration guide, 11-11event, 11-17FAQs, 11-18introduction, 11-2maintenance guide, 11-16planning guide, 11-11protection type, 11-5relation with other features, 11-7switching condition, 11-5switching impact, 11-7switching operation, 11-17system configuration, 11-2

N+1 protection protocolstarting, 11-16stopping, 11-16

NE ID, modifying, 2-16network attributes, 21-4

OOSI over DCC

access mode, 4-4alarm, 4-15availability, 4-5configuration example, 4-13configuration flow, 4-10configuration guide, 4-10event, 4-15FAQ, 4-15introduction, 4-2maintenance guide , 4-15planning guide, 4-7protocol stack, 4-2realization principle, 4-6relation with other features, 4-6

OSI route, querying, 4-13

QQinQ

alarm, 21-18application, 21-4availability, 21-6configuration, 21-11configuration example, 21-15configuration flow, 21-9event, 21-18FAQs, 21-18frame format, 21-2introduction, 21-2maintenance guide, 21-17modifying the type field, 21-11

planning guide, 21-8realization principle, 21-7Relation with Other Features, 21-7

QoSalarm, 20-20availability, 20-4configuration guide, 20-9event, 20-20FAQs, 20-20introduction, 20-2maintenance guide, 20-20planning guide, 20-8realization principle, 20-5relation with other features, 20-5

Rring MSP

starting, 15-11stopping, 15-11switching condition, 15-3switching impact, 15-5

ring MSP, two-fiber, bidirectionalalarm, 15-12availability, 15-5byte K, 15-2event, 15-12FAQs, 15-12introduction, 15-2maintenance guide, 15-11planning guide, 15-7protection type, 15-2realization principle, 15-5relation with other features, 15-5

RMONalarm group, 22-2alarm group, configuration, 22-10availability, 22-6configuration guide, 22-9FAQs, 22-13history control group, 22-2history control group, configuration, 22-11history group, 22-2history group, configuration, 22-12maintenance guide, 22-9planning guide, 22-8realization principle, 22-7relation with other features, 22-7statistics group, 22-2

ROMNstatistics group, configuration, 22-9

RSTPavailability, 19-7configuration, 19-27, 19-32introduction, 19-4planning guide, 19-15query, running information, 19-35realization principle, 19-8

IndexOptiX RTN 600 Radio Transmission System

Feature Description

i-4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-06-20)

relation with other features, 19-7

Sshaping

configuration, 20-18SNCP

alarm, 13-17automatic switching conditions, setting, 13-11availability, 13-5configuration guide, 13-7configuring, 13-7event, 13-17FAQ, 13-17introduction, 13-2maintenance guide , 13-16planning guide, 13-6protection type, 13-2realization principle, 13-5relation with other features, 13-5service pair, 13-2switching condition, 13-2switching impact, 13-5switching operation, 13-16

SNMP, 22-2Spoke, 19-2STP

availability, 19-7configuration, 19-27, 19-32introduction, 19-4planning guide, 19-15query, running information, 19-35realization principle, 19-8relation with other features, 19-7

TTAG attribute, 18-3traffic shaping

algorithm, 20-6introduction, 20-4

VVCTRUNK

decrease bandwidth, 17-23increase bandwidth, 17-23introduction, 17-4

virtual concatenationavailability, 17-4introduction, 17-4, 17-9planning guide, 17-14

VLANalarm, 18-15application, 18-4availability, 18-5configuration example, PORT-shared EVPL ,18-12

configuration example, VCTRUNK-shared EVPL ,18-13configuration flow, 18-7configuration guide, 18-7, 21-9event, 18-15FAQs, 18-15frame format, 18-2functionality, 21-2introduction, 18-2, 19-2maintenance guide, 18-15planning guide, 18-6purpose, 18-2realization principle, 18-6relation with other features, 18-5

VLAN filter table, configure, 19-23

XXPIC, 10-1

alarm, 10-12availability, 10-4configuration, 10-8event, 10-12FAQs, 10-13introduction, 10-2maintenance guide, 10-12overview, 10-2planning guide, 10-7realization principle, 10-6relation with other features, 10-5system configuration, 10-3



i-5

RTN 600-Feature Description(V100R002_02)

Documents

Transcript of RTN 600-Feature Description(V100R002_02)