02 Idu Product Description

8/10/2019 02 Idu Product Description

1/84

FlexiPacket Hub 800

R2.5

IDU Product Description

A25000-A0800-E018-01-76P1

Issue: 1 Issue date: May 2013

Nokia Siemens Networks is continually str iving to reduce the adverse environmental effects of

its products and services. We would like to encourage you as our customers and users to join

us in working towards a cleaner, safer environment. Please recycle product packaging and

follow the recommendations for power use and proper disposal of our products and their

components.

If you should have questions regarding our Environmental Policy or any of the environmental

services we offer, please contact us at Nokia Siemens Networks for any additional information.


2/84

2 A25000-A0800-E018-01-76P1



The information in this document is subject to change without notice and describes only the

product defined in the introduction of this documentation. This documentation is intended for the

use of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted

in any form or means without the prior written permission of Nokia Siemens Networks. The

documentation has been prepared to be used by professional and properly trained personnel,

and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes

customer comments as part of the process of continuous development and improvement of the

documentation.

The information or statements given in this documentation concerning the suitability, capacity,

or performance of the mentioned hardware or software products are given "as is" and all liability

arising in connection with such hardware or software products shall be defined conclusively and

finally in a separate agreement between Nokia Siemens Networks and the customer. However,

Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions

contained in the document are adequate and free of material errors and omissions. Nokia

Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which

may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO

EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMEN-

TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT,

INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT

LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS

OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR

THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and

other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark

of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.

Copyright Nokia Siemens Networks 2013. All rights reserved.

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources

of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle

this product and only after having carefully read the safety information applicable to this

product.

The safety information is provided in the Safety Information section in the Legal, Safety

and Environmental Information part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur ProduktsicherheitVon diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder

andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch

geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-

anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal,

Safety and Environmental Information dieses Dokuments oder dieses Dokumentations-

satzes.


3/84

A25000-A0800-E018-01-76P1


3


Table of ContentsThis document has 84 pages.

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.2 Structure of this document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3 History of changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.4 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.5 Waste electrical and electronic equipment (WEEE) . . . . . . . . . . . . . . . 11

1.6 RoHS compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.7 CE compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.8 MEF compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.9 FCC compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.10 Gost-R compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.11 NEBS compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.12 VCCI compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.1 FPH800 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.2 Release R2.5 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.4 FlexiPacket microwave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.1 Main features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.2 Carrier Ethernet Transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.1 Ethernet service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.2.1.1 E-Line service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.2.1.2 E-LAN service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.2.1.3 Service VLAN Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.2.2 Quality of Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.2.2.1 Ingress storm control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.2.2.2 Service classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.2.2.3 Bandwidth profiles and traffic policing . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.2.2.4 Congestion avoidance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.2.2.5 Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.2.2.6 Queue shaping and port shaping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2.3 Ethernet OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.2.3.1 Continuity check message (CCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.2.3.2 Ethernet Loopback (ETH-LB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2.3.3 AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2.3.4 RDI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2.3.5 Ethernet loss measurement (ETH-LM) . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2.3.6 Ethernet delay measurement (ETH-DM) . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2.4 LLDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.2.5 Bridging modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.3 Multi Service Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.3.1 TDM over Packet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28


4/84

4 A25000-A0800-E018-01-76P1



3.3.1.1 CESoPSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.3.1.2 SAToP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.3.1.3 EoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.3.2 TDM Cross Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.4 Device Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.4.1 LPG protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.4.2 Dual-IDU protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.5 Link protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.5.1 RSTP/MSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.5.2 LAG protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.5.3 CESoPSN and SAToP linear protection . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.5.4 G.8031 linear protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.5.5 G.8032 ring protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.5.5.1 G.8032 interworking with STP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.5.5.2 G.8032 interworking with LPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.5.6 UNI port shutdown upon service failure . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.5.7 STM-1 Multiplex Section Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.6 Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.6.1 TDM synchronization interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.6.2 ToP IEEE1588v2 slave/ordinary clock . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.6.3 Synchronous Ethernet (synchronous Ethernet) . . . . . . . . . . . . . . . . . . . 46

3.6.4 Clock recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.7 OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.7.1 Performance management for Ethernet services . . . . . . . . . . . . . . . . . . 47

3.7.2 Performance management for CESoP service. . . . . . . . . . . . . . . . . . . . 47

3.7.3 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.7.4 Performance monitoring and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.8 Security management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.8.1 SSH/SFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.8.2 SNMPv2c/SNMPv3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.8.3 User class management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.8.4 Securing management protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.9 Dual-IDU management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4 Mechanical structure and interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.1 FPH800 base system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.1.1 Mainboard interfaces on the faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.1.2 Reset button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4.1.3 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4.1.4 FPR/FPMR power feeding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4.1.5 Internal fan tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.1.6 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.1.7 Handling requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.2 Plug-in cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

4.3 LEDs indication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

4.4 Patch panels interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4.5 Dual-IDU interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.6 Radio/MultiRadio connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62


5/84

A25000-A0800-E018-01-76P1


5


5 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.1 Site configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.1.1 Tail site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.1.2 Chain site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.1.3 Hub site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.1.4 Edge site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.1.5 Ring site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.1.6 Ring root site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.2 Dual-IDU applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

6 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

6.1 Network management using NSN NetAct . . . . . . . . . . . . . . . . . . . . . . . 70

6.2 Network management using NSN NetViewer . . . . . . . . . . . . . . . . . . . . 70

6.3 Network management using FPH800 Web-based LCT. . . . . . . . . . . . . 70

6.4 Accessing IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

6.5 SNMP agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

6.6 SNTP, SFTP, and Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

6.7 USB key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

6.8 License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

7 Technical specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

7.1 Dimensions and weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

7.2 Power requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

7.3 Environmental working temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

7.4 Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

8 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82


6/84

6 A25000-A0800-E018-01-76P1



List of FiguresFigure 1 WEEE label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Figure 2 CE marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Figure 3 MEF certified comliant logo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Figure 4 Front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Figure 5 E-Line illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Figure 6 E-Line service application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Figure 7 E-LAN service illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Figure 8 QoS architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Figure 9 Bandwidth profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Figure 10 N X 64 Kbps grooming to 1 X E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Figure 11 N X 64 Kbps grooming application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Figure 12 EoS application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Figure 13 Mixed protection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 14 FPH800 Dual-IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Figure 15 FPH800 Dual-IDU protection application . . . . . . . . . . . . . . . . . . . . . . . . 34

Figure 16 Dual-IDU protection panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 17 Cable requirement on Protection Panel . . . . . . . . . . . . . . . . . . . . . . . . . 36

Figure 18 Power Injector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Figure 19 Power Injector application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Figure 20 Power Injector cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Figure 21 MSTP illustration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Figure 22 End to end protection path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Figure 23 Ethernet ring protection switching architecture - normal condition . . . . . 43

Figure 24 STM-1 MSP protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Figure 25 IEEE1588 module network application . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Figure 26 FPH800 faceplate and backplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 27 Mechanical structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 28 Power feeding inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Figure 29 Power supply illustration to ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Figure 30 Fan tray view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Figure 31 ODU connection with P + E port and with 2-port Power Injector card . . 62

Figure 32 ODU with power injector connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Figure 33 A complete mobile backhauling solution. . . . . . . . . . . . . . . . . . . . . . . . . 64

Figure 34 Tail site configuration with ODU 1+0 connection . . . . . . . . . . . . . . . . . . 65

Figure 35 Tail site configuration with ODU 1+1 HSBY . . . . . . . . . . . . . . . . . . . . . . 65

Figure 36 Chain site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Figure 37 Hub site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Figure 38 Edge site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Figure 39 Ring site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Figure 40 Ring root site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Figure 41 LPG + YPG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Figure 42 LPG + YPG + YPG (P + E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Figure 43 LPG + YPG + YPG (P + E) + LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69


7/84


8/84

8 A25000-A0800-E018-01-76P1




9/84

A25000-A0800-E018-01-76P1


9

IDU Product Description Preface

1 PrefaceThis document provides the technical description and the technical specifications of the

Nokia Siemens Networks FlexiPacket Hub 800, software release R2.5, an Indoor Unit

(IDU) of Nokia Siemens Networks FlexiPacket Microwave family.

1.1 Intended audience

This document is intended for the radio network planners and the technicians in charge

of operating and maintaining FlexiPacket Hub 800 (FPH800).

1.2 Structure of this document

The document is divided into the following main chapters:

1.3 History of changes

1.4 Symbols and conventions

The following symbols and conventions are used in this document:

Chapter Title Subject

Chapter 1 Preface Provides an introduction and overview

of this Product Description document

Chapter 2 Overview Provides an overview on the Flexi-

Packet Hub 800

Chapter 3 Features Provides the main features introduction

Chapter 4 Mechanical structure and

interfaces

Provides the information regarding the

structure and the external interfaces of

the FlexiPacket Hub 800

Chapter 5 Application Provides the main applications that canbe implemented with the FlexiPacket

Hub 800

Chapter 6 Management Provides the information regarding the

management of the FlexiPacket Hub

800

Chapter 7 Technical specifications Lists the technical data

Chapter 8 Glossary Lists the abbreviations used in this

document

Table 1 Structure of this document

Issue Issue date Remarks

1 May 2013 1st version

Table 2 History of changes


10/84

10 A25000-A0800-E018-01-76P1


IDU Product DescriptionPreface

Representation Meaning

Bold Text in the graphical user interface (window and wizard titles, field

names, buttons, etc.) is represented in boldface.

Example: Click Shutdownand then click OKto turn off the com-

puter.

Italic Field values, file names, file extensions, folder and directory

names are denoted by italic text.

Examples: Enter 192.168.0.1in the IP addressfield. Click OKto

produce a .pdffile.

Courier Command and screen output are denoted by courierfont.

Example: ping -t 192.168.0.1

Place holders for distinct names or values are represented byenclosing them in . If a file name is involved, italic

text will also be used.

Example: The naming convention for the log files is

.txt, where is the name of the NE sending

the messages.

Keyboard button Keyboard keys are represented with a surrounding box.

Example: Press Enter.

[Square brackets] Keyboard shortcuts are represented using square brackets.

Example: Press [CTRL+ALT+DEL] to open the Task Manager.

> The > symbol is used as short form to define a path through indi-

vidual elements of the graphical user interface, e.g., menus and

menus commands.

Example: On the Windows taskbar, select Start> Programs>

TNMS> Clientmenu command to start the TNMS Core/CDM

Client.

t A tip provides additional information related to the topic described.

g A note provides important information on a situation that cancause property damage or data loss.

A note introduced in the text by the keyword NOTICE: describes ahazard that may result in property damage but not in personal

injury.

Table 3 List of conventions used in this document


11/84

A25000-A0800-E018-01-76P1


11


Screenshots of the graphical user interface are examples only to illustrate principles.

This especially applies to a software version number visible in a screenshot.

1.5 Waste electrical and electronic equipment (WEEE)

All waste electrical and electronic products must be disposed of separately from the

municipal waste stream via designated collection facilities appointed by the government

or the local authorities. The WEEE label (see Figure 1) is applied to all such devices.

Figure 1 WEEE label

The correct disposal and separate collection of waste equipment will help prevent poten-

tial negative consequences for the environment and human health. It is a precondition

for reuse and recycling of used electrical and electronic equipment.

For more detailed information about disposal of such equipment, please contact Nokia

Siemens Networks.The above statements are fully valid only for equipment installed in the countries of the

European Union and is covered by the directive 2002/96/EC. Countries outside the

European Union may have other regulations regarding the disposal of electrical and

electronic equipment.

1.6 RoHS compliance

FlexiPacket Hub 800 complies with the European Union RoHS Directive 2002/95/EC on

the restriction of use of certain hazardous substances in electrical and electronic equip-

ment.

w A safety message provides information on a dangerous situationthat could cause bodily injury.

The different hazard levels are introduced in the text by the follow-

ing keywords:

DANGER!- Indicates a hazardous situation which, if not avoided,

will result in death or serious (irreversible) personal injury.

WARNING!- Indicates a hazardous situation which, if not

avoided, could result in death or serious (irreversible) personal

injury.

CAUTION! - Indicates a hazardous situation which, if not avoided,

may result in minor or moderate (reversible) personal injury.

Representation Meaning

Table 3 List of conventions used in this document (Cont.)


12/84

12 A25000-A0800-E018-01-76P1


IDU Product DescriptionPreface

The directive applies to the use of lead, mercury, cadmium, hexavalent chromium, poly-

brominated biphenyls (PBB), and polybrominated diphenylethers (PBDE) in electrical

and electronic equipment put on the market after 1 July 2006.

Materials usage information on Nokia Siemens Networks Electronic InformationProducts imported or sold in the Peoples Republic of China

FlexiPacket Hub 800 complies with the Chinese standard SJ/T 11364-2006 on the

restriction of the use of certain hazardous substances in electrical and electronic equip-

ment. The standard applies to the use of lead, mercury, cadmium, hexavalent chro-

mium, polybrominated biphenyls (PBB), and polybrominated diphenyl ethers (PBDE) in

electrical and electronic equipment put on the market after 1 March 2007.

1.7 CE compliance

FlexiPacket Hub 800 is in compliance with the essential requirements and other relevant

provisions of Directive: EN 301 489-4 V1.4.1:2009, EN 300 386 V1.5.1:2010, EN 301489-1 V1.9.2:2011 and EN 60950-A/A12:2011.

Figure 2 CE marking

1.8 MEF compliance

FlexiPacket Hub 800 operating at the NNI delivers EPL, EVPL and E-LAN service com-

pliant with the Metro Ethernet Forum MEF14 technical specification. Flexipacket Hub

800 operating at the UNI delivers EPL, EVPL and E-LAN service compliant with theMetro Ethernet Forum MEF9 technical specification.

Figure 3 MEF certified comliant logo

1.9 FCC compliance


provisions of Directive: UL 60950-1:2007 and CAN/CSA-C22.2 No.60950-1:2007.

The product is marked with the CE marking


13/84

A25000-A0800-E018-01-76P1


13


1.10 Gost-R compliance


provisions of Directive: Gost R IEC 60950-1-2009, Gost R 51318.22-99 (class B), Gost

R 51318.24-99, Gost R 51317.3.2-2006 (Part 6,7) and Gost R 51317.3.3-2008.

1.11 NEBS compliance


provisions of Directive: GR-1089-Core, Issue 6, May 2011 and GR-63-Core, Issue 2,

March 2006.

1.12 VCCI compliance


provisions of Directive: VCCI Technical Requirement (V-3/2010.04) andCISPR22:2008.


14/84

14 A25000-A0800-E018-01-76P1


IDU Product DescriptionOverview

2 OverviewFlexiPacket Hub 800 (FPH800), is a reliable and flexible indoor unit (IDU) of Nokia

Siemens Networks (NSN) FlexiPacket Microwave family (see FlexiPacket microwave),

which can be used for tail, chain, hub and aggregation site application in the mobile

backhaul solution.

2.1 FPH800 introduction

Figure 4 Front panel

FPH800 (Figure 4) is an indoor unit with 1 U (1 U = 44.45 mm) height.

It is connected to and works together with ODUs to transfer/receive local traffic to/from

remote equipment. ODU can be connected to FPH800 through a single Ethernet cable

using ports with ODU power feeding support (P + E). As an alternative, the ODU can be

powered from an external power through a seperate cable.

Besides the interfaces on the mainboard, FPH800 uses multi-slots structure to support

various plug-in cards with various interfaces. With the help of SFPs, plug-in cards and

patch panels, FPH800 can be connected to various interfaces of local traffic, e.g., FE,

GE, E1/T1/J1, STM-1, STM-4 and FlexBus interface. FB interface for FTFA, FTFB,

FIU19(E), FXC RRI, and IFUE, etc., can be supported.

tThe interfaces on the mainboard are described in Mainboard interfaces on the faceplate.

t The interfaces on the plug-in cards are described in Plug-in cards.

Additionally, as part of the NSN Carrier Ethernet portfolio, it allows a smooth integration

in the network, ensuring end to end Quality of Service (QoS) and easy provisioning.

FPH800 has the peculiarity to be able to work in two different modes, Packet mode and

Hybrid mode, via different software release. Both modes support Ethernet and TDM

traffic but the main difference lies in:

In Packet mode, TDM traffic is transported over packets with circuit emulation; but In Hybrid mode, TDM traffic is kept separated from packet traffic.

2.2 Release R2.5 introduction

FPH800 R2.5 is a Packet mode software release and is the enhanced version for mobile

backhaul application. The new features with respect to EoS on STM-1/4 MSC card make

it more attractive and expand its application scenarios. New protection features includ-

ing Dual-IDU, G.8032 make it more robust and bring higher stability.

FPH800 supports the following ODU configurations:

1 + 0

1 + 1 Hot Standby / Space Diversity


15/84

A25000-A0800-E018-01-76P1


15

IDU Product Description Overview

1 + 1 Frequency Diversity

2 + 0 Frequency Diversity

2 + 0 XPIC

2 + 2

2.3 Licensing

Users who wants to use certain value-added features need to purchase the correspond-

ing license. A license can be purchased by user together with the hardware and the

application software in the initial purchase order, or it can be later purchased and

installed into an already operating device.

FPH800 is delivered to customer with the basic license pre-installed, so essential func-

tions are enabled. If additional features need to be activated, customer can acquire

upgrading license.

t Details on license is described in License. Details on license aquisition steps are described in Operate and Maintainmanual.

2.4 FlexiPacket microwave

NSN FlexiPacket Microwave is a packet microwave system designed to meet the

requirements of evolved transport networks with the target of minimizing the operator

Total Cost of Ownership (TCO). It joins together the benefits of an advanced scalable

microwave radio and of a real carrier grade Ethernet nodal solution.

FlexiPacket Microwave is the means of deploying a cost-effective microwave infrastruc-

ture for 2G, 3G, WiMAX and LTE backhaul, high speed wireless Internet networks, fixedbroadband access backhaul and private wireless networks.

FlexiPacket Microwave is the right solution to design advanced mobile backhaul

networks based on Ethernet transport. The solution is conceived both for pure packet

and TDM + Packet hybrid networks.

FlexiPacket Microwave family includes the following:

FlexiPacket Radio (FPR)

FlexiPacket MultiRadio (FPMR)

FlexiPacket FirstMile 200 (FPFM200)

FlexiPacket FirstMile 200i (FPFM200i)

FlexiPacket Hub 800 (FPH800) FlexiPacket Hub 1200/2200 (FPH1200/2200)

g For the detailed information of FPR, FPMR, FPFM200, FPFM200i, FPH1200/2200,please refer to NSN dedicated customer documentation of the product respectively.


16/84

16 A25000-A0800-E018-01-76P1


IDU Product DescriptionFeatures

3 Features

3.1 Main featuresThe following are the FPH800 main features:

Carrier Ethernet Transport

Ethernet service

Quality of Service

Ethernet OAM

LLDP

Bridging modes

Multi Service Application

TDM over Packet

TDM Cross Connection Device Protection

LPG protection

Dual-IDU protection

Link protection

RSTP/MSTP

LAG protection

CESoPSN and SAToP linear protection

G.8031 linear protection

G.8032 ring protection

UNI port shutdown upon service failure

STM-1 Multiplex Section Protection

Synchronization

TDM synchronization interface

ToP IEEE1588v2 slave/ordinary clock

Synchronous Ethernet (synchronous Ethernet)

Clock recovery

OAM

Performance management for Ethernet services

Performance management for CESoP service

Fault Management

Performance monitoring and statistics

Security management

SSH/SFTP

SNMPv2c/SNMPv3

User class management

Securing management protocols

Dual-IDU management


17/84

A25000-A0800-E018-01-76P1


17

IDU Product Description Features

3.2 Carrier Ethernet Transport

3.2.1 Ethernet service

3.2.1.1 E-Line service

E-Line service is a point-to-point Ethernet service. For E-Line service, traffic from one

configurable port can go to any other configurable port (see Figure 5). Packets received

from ingress port, are parsed and processed (e.g., policing, countering, editing). The

selection of egress port is not based on L2 bridging, but based on service mapping rule

definition (thus, E-Line service does not need to learn MAC address).

Figure 5 E-Line illustration

All the TDM traffic from E1/T1 plug-in card and E1/T1 on the mainboard should be

encapsulated into CESoP packet by TDMoP IWF function, and then transmitted as

Ethernet frame. Figure 6demonstrates the use case of E-Line service.

Figure 6 E-Line service application


18/84


19/84

A25000-A0800-E018-01-76P1


19


Ingress storm control

Service classification

Bandwidth profiles and traffic policing

Congestion avoidance Scheduling

Queue shaping and port shaping

Figure 8 QoS architecture

3.2.2.1 Ingress storm control

In the network, a malfunction by a user e.g., sending unicast with unknown MAC

address, broadcast, or multicast traffic at a very high rate could cause a flooding in the

network. Thus a switch like FPH800 is required to have the capability of preventing

flooding traffic from going to other segments of the network.

In FPH800, broadcast and multicast and unknown unicast packets are monitored at the

ingress. Each type of packets have separate counters. The ingress counter counts the

number of packets which enable multicasting and broadcasting received on each port.

The packets are discarded if the respective count exceeds a programmed threshold in

a given time interval.

3.2.2.2 Service classificationThere are 3 main functions in classification:

Service VLAN ID Determination

Priority determination

Egress port determination

Classification at UNI

At UNI port, ingress frames are mapped into services according to configurable mapping

rule (also known as: configuration rule). Precedence between the classification rules

defined on a port is configurable on per-port basis.


20/84

20 A25000-A0800-E018-01-76P1



In FPH800, the mapping field supported on UNI and NNI ports are different. In addition,

the mapping field used for E-Line service and E-LAN service on UNI port is different

either.

Mapping fields on UNI port for E-Line service: MAC DA (Destination Address)

MAC SA (Source Address)

VLAN priority (C-tag)

VLAN ID (C-tag)

Tagged/Untagged

EtherType

Protocol Type

Source IP address

Destination IP address

L4 source port

L4 destination port

DSCP

g A combination of rules can also be used to define a service, e.g. VLAN ID=100 ANDDSCP = 32.

Mapping fields on UNI port for E-LAN service:

MAC SA

VLAN ID (C-tag)

Source IP address Untagged

remaining: all other traffic not compliant to rules defined for other services

g The mapping rule for E-LAN service on UNI port has the following limitations: MAC SA/Source IP address are per system based.

For a single mapping rule, only one field can be used for classification.

Priority of these fields is fixed as (from highest to lowest): VLAN ID, MAC SA,

Source IP address, untagged traffic.

Classification at NNI

On NNI port, only source port and SVID are used for classification.

At NNI, S-tag of ingress traffic is transmitted transparently.

CoS

After traffic classification on UNI, a Class of Service (CoS) is assigned to the service in

two cases.

Single-CoS

By default, all the traffic of a service has the same CoS. This means that all the traffic

of a service enters the same priority queue.


21/84

A25000-A0800-E018-01-76P1


21


Multi-CoS

When Multi-CoS is enabled for a service, the traffic of the service is mapped to dif-

ferent classes (i.e., priorities) based on CoS mapping rules. Thus the traffic belong-

ing to the same service may enter different priority queues.

Priority determination

At UNI, after classification, a Class of Service (CoS) is assigned to the traffic.Options

are:

All traffic of a service is mapped to the same CoS.

Traffic of a service is assigned to different Classes (Multi CoS). Multi CoS classifi-

cation is based on mapping rules for both untagged traffic and tagged traffic.

Priority (IEEE 802.1p) bits in the Service VLAN are marked accordingly.

3.2.2.3 Bandwidth profiles and traffic policing

Bandwidth profile

Bandwidth profile is one of the attributes of Ethernet service. From customers perspec-

tive, bandwidth profile specifies the average rate of committed and excessive cus-

tomers frames allowed into service providers network on UNI port, according to the

definition of Metro Ethernet Forum (MEF).

A bandwidth profile has four major parameters:

CIR (Committed information rate)

PIR (Peak information rate) CBS (Committed burst size)

PBS (Peak burst size)

The definitions and explanations of these parameters can be found in a whitepaper of

MEF on its web site: http://metroethernetforum.org/PDF_Documents/Bandwidth-

Profiles-for-Ethernet-Services.pdf.

g Note that only color-blind mode is supported.

Note also that MEF uses PIR (Peak information rate) instead of CIR for the same

meaning.

FPH800 supports four types of bandwidth profiles:

Per UNI bandwidth profile

Per service bandwidth profile

Per CoS bandwidth profile

Per mapping rule bandwidth profile

The figure below illustrates the effect of each type of bandwidth profile applied to

Ethernet services.


22/84

22 A25000-A0800-E018-01-76P1



Figure 9 Bandwidth profiles

g A service can be applied with only one type of bandwidth profile. However, a service canhave multiple bandwidth profiles of the same type (either the type of per CoS bandwidth

profile or the type of per mapping rule bandwidth profile). Likewise, when there are

multiple services on a UNI port, each service can have its own bandwidth profile of

single type except the case where per UNI bandwidth profile is applied to the UNI port.

Per UNI bandwidth profile

The ingress bandwidth profile provides a bandwidth profile that applies to all the ingress

traffic on an UNI port, even in case where there are several services on this port. It takes

effect only when none of the other types of bandwidth profile (per-service bandwidth

profile, per-CoS bandwidth profile, and per mapping rule bandwidth profile) is applied to

the services bound to the port. On WebLCT, per UNI bandwidth profile is shown as Port

bandwidth porfile.

Per service bandwidth profile

This type of bandwidth profile is applied to the traffic of an E-Line or E-LAN service on

the UNI port in any case of either Single-CoS or Multi-CoS enabled for the service.

Per CoS bandwidth profile

This type of bandwidth profile can be applied to a service when Multi-CoS is enabled for

the service. Instead of specifying the bandwidth for the whole service, per CoS band-

width profile specifies the bandwidth of each class of the service.

Per mapping rule bandwidth profile

This type of bandwidth profile can be applied to each mapping rule of a service. Refer

to Section 3.2.2.2 Service classificationfor the details on service mapping rules.


23/84


24/84

24 A25000-A0800-E018-01-76P1



If the queue depth is between the two thresholds (minimum and maximum), the con-

gestion is determined to be moderate and the packet will be dropped according to

the drop rate.

If the queue depth is above high threshold (maximum), all the yellow packets are-dropped.

g sRED only works for yellow packets. The green packets will be dropped only when thebuffer becomes full. All the red packets are dropped.

3.2.2.5 Scheduling

The following scheduling methods are supported in FPH800:

Strict Priority (SP)

Weighted Round Robin (WRR)

Weighted Deficit Round Robin (WDRR)

SP+WRR/WDRR

Strict Priority

The strict priority method schedules the access to the egress port across the QoS

queues from highest QoS queue index to the lowest. The purpose is to provide lower

latency service to the higher QoS classes of traffic.

Weighted Round Robin

The WRR scheduler provides a weighted packet round robin scheme across the QoS

queues. The purpose is to provide a weighted access to the egress port bandwidth (ata packet level).

Deficit Weighted Round Robin

An inherent limitation of the WRR mode is that the actual bandwidth allocated to a queue

depends on the frame size, but as frame sizes are not known to the scheduler, it is hard

to control the bandwidth allocated to a queue.

To address this issue, Deficit Weighted Round Robin (DWRR or simply DRR) was

invented. It is a modified version of WRR.

DRR has two parameters, Credit counter (also called deficit counter) and Quantum.

DRR serves the frames at the head of every non-empty queue whose Credit counter isgreater than the frames size. If the Credit counter is lower, then the queue is skipped

and its Credit is increased by a given value called Quantum (so here, the function of

Quantum is somewhat like weight but is in bytes.) This increased value is used to cal-

culate the Credit counter the next time around when the scheduler examines this queue

for serving its head-of-line frame. If the queue is served, then the Credit is decremented

by the size of frame being served.

SP + WRR/WDRR

The combination of SP + WRR/WDRR is supported in FPH800. In this case, strict

priority queues are serviced first in the order of their QoS numbering, the rest QoS

queues are serviced in WRR/WDRR manner.


25/84


26/84

26 A25000-A0800-E018-01-76P1



3.2.3.2 Ethernet Loopback (ETH-LB)

Loopback messages are unicast and multicast frames that a Maintenance End Point

(MEP) transmits. It is used to verify the connectivity of a MEP with a Maintenance Inter-

mediate Points (MIP) or peer MEPs. They are similar in concept to an Internet ControlMessage Protocol (ICMP) Echo (Ping) messages, sending Loopback to successive

MIPs in order to determine the location of a fault. Sending a high volume of Loopback

Messages can test bandwidth, reliability, or jitter of a service, which is similar to flood

ping. A MEP can send a Loopback to any MEP or MIP in the service. Unlike CCMs,

Loopback messages are administratively initiated and stopped.

There are two ETH-LB types:

Unicast ETH-LB

Multicast ETH-LB

3.2.3.3 AISEthernet alarm indication signal function (ETH-AIS) is used to suppress alarms following

detection of defect conditions at the server (sub-) layer. Due to independent restoration

capabilities provided within the spanning tree protocol (STP) environments, ETH-AIS is

not expected to be applied in the STP environments.

3.2.3.4 RDI

Ethernet remote defect indication function (ETH-RDI) can be used by a MEP to commu-

nicate to its peer MEPs that a defect condition has been encountered. ETH-RDI is used

only when ETH-CC transmission is enabled.

3.2.3.5 Ethernet loss measurement (ETH-LM)

OAM functions for performance monitoring allow measurement of different performance

parameters. The performance parameters are defined for point-to-point Ethernet con-

nections. FPH800 covers the following performance:

Frame loss ratio

Frame delay

Ethernet loss measurement is performed in Single-ended ETH-LM. It is used for on-

demand OAM. In this case, a MEP sends frames with loss measurement request infor-

mation to its peer MEP and receives frames with loss measurement reply information

from its peer MEP to carry out loss measurements.

3.2.3.6 Ethernet delay measurement (ETH-DM)

Frame delay can be specified as round-trip delay for a frame. It is defined as the time

elapsed since the start of transmission of the first bit of the frame by a source node until

the reception of the last bit of the loopbacked frame by the same source node. The

loopback is performed at the frame's destination node.

Delay measurement can be used for on-demand OAM to measure frame delay and

frame delay variation. Frame delay and frame delay variation measurements are per-

formed by sending periodic frames with delay measurement information to the peer

MEP and receiving frames with delay measurement information from the peer MEPduring the diagnostic interval. Each MEP may perform frame delay and frame delay vari-


27/84

A25000-A0800-E018-01-76P1


27


ation measurement. When a MEP is enabled to generate frames with delay measure-

ment information, it periodically sends frames with delay measurement information to its

peer MEP. When a MEP is enabled to generate frames with delay measurement infor-

mation, it also expects to receive frames with delay measurement information from its

peer MEP.

Delay measurement can be performed in two ways:

One-way ETH-DM

Each MEP sends a frame with one-way delay measurement information to its peer

MEP to facilitate one-way frame delay and/or one-way frame delay variation mea-

surements at the peer MEP. If the clocks between the two MEPs are synchronized,

one-way frame delay measurement can be carried out. Otherwise, only one-way

frame delay variation measurement can be performed.

Two-way ETH-DM

A MEP sends frames with delay measurement request information to its peer MEP

and receives frames with delay measurement reply information from its peer MEPto carry out two-way frame delay and two-way frame delay variation measurements.

FPH800 supports Two-way ETH-DM, and one-way ETH-DM in the future.

3.2.4 LLDP

LLDP is supported in FPH800 to advertise the system key capabilities on the Ethernet

LAN and also learn the key capabilities of other systems on the same Ethernet LAN.

Information like system name and description, IP management address, etc., can be

sent or received as LLDPDU (LLDP Data Unit) via SNMP MIB for every station to know

their neighbours. LLDP frames are sent at a fixed rate on each port of every station and

no acknowledgement is expected from the receiver. It is so-called one way connection-less data link layer protocol which runs on MAC layer.

LLDP allows the NMS to build the physical topology of the network under its supervi-

sion.The NMS can only get a complete picture of the controlled network when all the

NEs support LLDP.

g For the detailed information of LLDP, please refer to IEEE 802.1 ABTM-2005.

3.2.5 Bridging modes

L2 bridging is compliant with 802.1ad Provider Bridge, forwarding is performed accord-

ing to {S-VID, DA} pair for E-LAN service. {S-VID, DA} pair are automatically learned by

the bridge, protection is based on RSTP or MSTP responding to topology change, or on

a ring topology.

g E-Line service uses point-to-point forwarding not based on L2 bridging, typically {SourcePort, VLAN ID}.

g On UNI port, FPH800 supports xSTP peering on any port when running.In IEEE802.1Q mode, FPH800 supports xSTP peer on any port.

In IEEE802.1ad mode, FPH800 does not need to support peering with customer STP.


28/84

28 A25000-A0800-E018-01-76P1



3.3 Multi Service Application

3.3.1 TDM over Packet

FPH800 supports both E1/T1 CESoPSN and E1 SAToP. The operator can configure

SAToP and CESoPSN services by only on E1/T1/STM-1 interface. At a certain time,

only one mode shall be configured through a certain E1/T1/STM-1 interface. The con-

figuration for the E1/T1/STM-1 is independent.Switch between SAToP and CESoPSN

mode on an E1/T1/STM-1 port can be done from WebLCT and NMS. But after switching,

all the TDM services on the E1/T1/STM-1 port will be removed.

g The two STM-1ports on the mainboard (actually the two SFP ports on the mainboardthat are configured as STM-1) must work in 1 + 1 MSP mode, so they function as one

STM-1 port protected by 1 + 1 MSP. They are not two independent STM-1 ports.

3.3.1.1 CESoPSN

The CES processing in FPH800 complies with the RFC5086 standard. The packet

format is IPv4 PSN with UDP (User Data Protocol) demultiplexing and the basic NxDS0

(Digital Service level 0) service is supported.

Each CES service requires an Ethernet service, either E-Line and E-LAN, as its under-

lying pseudo-wire (PW), which must be established and associated with the TDM port

of the CES service.

CESoPSN configurationIn FPH800, CES function encapsulates a TDM signal stream into packets and the

packets are sent via PSN tunnel (in our case, the tunnel is effectively the Ethernet PW)

towards the far end CES device. The packets are decapsulated back to TDM signal in

the far end CES device. The CES function decapsulates a TDM signal from a packet

stream received within a PSN tunnel and transmits the signal as a TDM link. The CES

function provides the control of PSN tunnel establishment and maintenance. The follow-

ing common configuration has to be applied at the PWE entities:

List of TDM time slots per TDM frame

Number of TDM frames per packet

Clock sources

Following options are supported to retrieve clock of each TDM interface:

Adaptive clock

g It will be supported in future release.

Differential clock

Loopback

Centralized clock (system clock)

Interfaces


29/84

A25000-A0800-E018-01-76P1


29


E1/T1

STM-1 (only used to hand off or receive E1s over STM-1 interface)

N X 64 Kbps grooming

Since R2.0EP2, FPH800 R2.0EP2 supports n X 64 Kbps grooming function.

N X 64 Kbps grooming function encapsulates a configurable number of 64Kbps time

slots from several E1 CESoPSN services into one E1 frame that is then handed off to

an E1 port on the mainboard.

N X 64 Kbps grooming function requires software license and it does not allow the two

SFP ports on the mainboard to be configured as STM-1 ports. In R2.0EP2, n X 64 Kbps

grooming is supported only by the 16 x E1 ports on the mainboard. The 16-port E1/T1

MSC does not support this function.

Figure 10 N X 64 Kbps grooming to 1 X E1

Figure 11 N X 64 Kbps grooming application


30/84

30 A25000-A0800-E018-01-76P1



PDH to SDH alarm translation

Starting from R2.0EP2, FPH800 supports E1 AIS replication to TU-12 AIS. If FPH800 is

set to enable E1-AIS to TU-AIS translation, during the mapping process from E1 to STM-

1, the related TU-AIS is set when E1-AIS is detected.

3.3.1.2 SAToP

In FPH800, SAToP (Structure-Agnostic TDM over Packet) is supported over UDP/IP

according to TDM over Packet (RFC 4553). The packet format is IPv4 PSN with UDP

(User Data Protocol) demultiplexing and the basic NxDS0 (Digital Service level 0)

service is supported.

SAToP and CESoPSN mixed configuration

Each E1 tributary or VC12 of STM-1 can be configured either as SAToP or CESoPSN

independently. The TDM payload field has a fixed amount of bytes that will be the samefor both PW's directions. The TDM payload size can be configured by the operator,

according to RFC4553.

TDM Payload size is from 1 to 800 bytes. Ethernet frame type II is supported. The

Ethernet frame includes VLAN tag according to IEEE802.3.

Clock sources

Following options are supported to retrieve clock of each TDM interface:

Adaptive clock

gIt will be supported in future release.

Differential clock

Lookback

Centralized clock (system clock)

Interfaces

E1

STM-1 (only used to hand off or receive E1s over STM-1 interface)

3.3.1.3 EoS

The following shows the STM-1 and STM-4 multiplexing structure of the STM-1/4 MSC

card.

E1 -> C-12 -> VC-12 -> TU-12 -> TUG-3 -> VC-4 -> AU-4 -> AUG-1 -> STM-1

E1 -> C-12 -> VC-12 -> TU-12 -> TUG-3 -> VC-4 -> AU-4 -> AUG-1 -> AUG-4 ->

STM-4

Ethernet over SDH is implemented in FPH800 on 2-port STM-1/4 MSC card. EoS

provides both high-order and low-order virtual concatenation to improve bandwidth effi-

cency.


31/84

A25000-A0800-E018-01-76P1


31


EoS is not applicable in ring application in FPH800. It means no layer 2 protocols such

as G.8032/xSTP/CCM are supported on EoS port. It is used to handle off Ethernet traffic

to SDH network that support EOS.

Figure 12illustrates supported and not-supported scenarios in FPH800. FPH800 can bemanaged in the same management VLAN by Netviewer via EoS port.

g User cannot configure E1 service over STM-1/4 interface of this card becauseCESoP/SAToP service are not supported by STM-1/4 card.

Figure 12 EoS application

Cross connection

User can only configure the following traffic type.

STM-1 modeUser can use 0 ~ 63 VC-12

STM-4 mode

User can use 0 ~ 63 VC-12 or 1 ~ 4 VC4

User cannot, for example, configure STM-4 interface traffic as one VC-4 plus 12 VC-12.

VCAT

VC concatenation (VCAT) is defined in ITU-T G.707(01/2007) clause 11. For the trans-

port of payloads that do not fit efficiently into the standard set of virtual containers (VC-

12, VC-4), VC concatenation can be used. VC concatenation is defined for:

VC-4to provide transport for payloads that require capacity greater than one container-4.

VC-12

to provide transport for payloads that require capacity greater than one container-

12.

The virtual concatenation engine maps encapsulated Ethernet data streams into SDH,

and reconstructs SDH payloads back into encapsulated Ethernet data streams. High-

order and low-order virtual concatenation is supported with up to 64 ms differential delay

between VCG members.

GFP


32/84

32 A25000-A0800-E018-01-76P1



GFP (generic framing procedure) is defined in ITU-T G.7041. FPH800 support GFP-F

mode of GFP. Generic Framing Procedure - Framed (GFP-F) maps each client frame

into a single GFP frame. It is used where the client signal is framed or packetized by the

client protocol.

The GFP frame is mapped into a container-n (n = 11, 12, 2, 3, 4, 4-Xc, 11-Xv/12-Xv/2-

Xv/3-Xv/4-Xv) with its byte boundaries aligned with the byte boundaries of the container-

n. The container-n is then mapped into the VC-n respectively, together with the associ-

ated POH.

Ethernet interface

It supports standard tagged and untagged MAC frame formats. The standard 802.3

frame size has been extended to include jumbo frames up to 9632 bytes, but in FPH800,

the jumbo frame length is up to 9600. All Ethernet port policies can be applied to this

port.

EoS Ethernet interface is mapped as logic user interface of mainboard switch. All

Ethernet port policy can be applied to this port.

Ethernet interface supports E-Line/E-LAN service type, and can be configured as UNI

and NNI interface.

All Ethernet traffic including in-band management service and IEEE 1588 service are

supported by EoS Ethernet interface, these services are transparent to EoS.

g LPG and LAG are not supported by EoS Ethernet interface. XSTP and LLDP are not supported by EoS interface.

3.3.2 TDM Cross ConnectionFPH800 supports TDM Cross connection (TDM CC). Traffic from TDM interfaces such

as STM-1/4, 16xE1, and FB can be sent to other TDM interfaces.

FPH800 TDM CC function is based on L2 switch, all TDM traffic are encapsulated into

CESoP or SAToP packet with port number, then the packets are sent the destination

port via L2 switch.

These CESoP and SAToP packet for TDM CC only transmit inside FPH800, they can't

be transmitted outside. And these packet are fixed length, and in received part, DCR

mode is used. FPH800 TDM CC function is based on L2 switch, all TDM traffic are

encapsulated into CESoP or SAToP packet with port number, then the packets are sent

the destination port via L2 switch. The cross-connect supports 111 x E1's.

3.4 Device Protection

Both IDU protection and ODU protection are supported in FPH800.

t For details on ODU protection schema, please refer to ODU related manuals.

3.4.1 LPG protection

In order to provide resilience against hardware failures of ODU, FPH800 supports link

protection group (LPG). There are up to 4 electrical Gigabit Ethernet interfaces on themainboard and two 4-port GE RJ-45 cards for connection to the ODUs. Therefore it is


33/84

A25000-A0800-E018-01-76P1


33


possible to install up to 6 pairs of protecting ODUs. Mixed configuration can be sup-

ported, for example (1+1) + 2x(1+0). The protection scheme supports the ODU system

types: 1+1 HSBY, 2+0 XPIC, 2+0 FD, 1+1 FD, 1+1 SD, etc. FPH800 supports ODU

swapping and repairing in LPG without traffic interruption (LPG hitless ODU swap).

In Figure 13, two ODUs are configured as 1+1 protection pair, the other two ODUs are

connected to separate radio links. In the protection scheme can be revertive or non-

revertive based on the configuration.

Figure 13 Mixed protection configuration

The 1+1 FD/SD protection involves a pair of FlexiPacket ODUs, one is active and the

other is standby. Traffic is sent to both ODUs, in case of any ODU failure, the standby

ODU becomes active.

LPG configuration

FPH800 supports 6 LPGs at most with the help of plug-in cards.

FPH800 LPG configuration has the following characteristics:

LPG cannot be empty (with no members) and at most be two member ports.

LPG members can only be physical ports.

LPG can be administratively enabled or disabled.

When a LPG is created, LPG will automatically receive the configurable attributes of

the first added port. The second port will inherit the configurable attributes of the

LPG.

When a port is removed from LPG, its configurable attributes will stay the same.

If any member port is link up status, LPG is link up status.

If all member ports are link down status, LPG is link down status.

Member port link status can be changed by E-CCM and RDI.

Two kinds of CCM are defined in protection scheme:

E-CCM: Continuity check between IDU and ODU.

P-CCM: Continuity check between two protected ODUs.

g CCM time interval: The time interval for generation and detection of E-CCM. It can beconfigured from a minimum of 10 ms to a maximum of 1s. The default value is 100 ms.

Before to set this parameter, refer to the documentation of ODU used in order to verify

the compatibility.
http://x%3Dd%3Do%3Dc/s-000002.pdfhttp://x%3Dd%3Do%3Dc/s-000002.pdfhttp://x%3Dd%3Do%3Dc/s-000002.pdfhttp://x%3Dd%3Do%3Dc/s-000002.pdfhttp://x%3Dd%3Do%3Dc/s-000002.pdfhttp://x%3Dd%3Do%3Dc/s-000002.pdf


34/84

34 A25000-A0800-E018-01-76P1



3.4.2 Dual-IDU protection

Dual-IDU is a device-level protection mechanism aimed for nodal protection. It can work

nicely together with ODU protection mechanisms such as 1 + 1 hot standby and 2 + 0

SD/FD to provide full redundancy of a site.

By R2.5, FPH800 dual-IDU supports tree and chain topology. Other types of topology

with loops will be supported by a future release. It is worth noting that network-wide pro-

tection protocols such as xSTP, G.8031/G.8032 can be applied in the network topology

with loops.

FPH800 dual-IDU requires a shroud to hold the two IDUs together and, more important,

to connect the two IDUs via the backplane on the dual-IDU shroud. Generally, the upper

IDU is assigned as the active one, and the other is the standby, but this is configured.

Figure 14 FPH800 Dual-IDU

There are three protection functions in dual-IDU mode:

YPG (Y-cable Protection Group)

FPH800 Dual-IDU provides protection panel, optical splitter, and dual-IDU power

injector that work for YPG.

LPG (Link Protection Group)

Basically, LPG over dual-IDU works in the same way as LPG over single IDU. Its

only difference is that the two GE ports of LPG are on two different IDUs.

LAG (Link Aggregation Group)

LAG over dual-IDU is the same as LAG over single IDU. Its only difference is that

the two ports in LAG are on tow different IDUs.

For detailed information of application scenarios and site configuration, see Chapter 4

Applications.

Figure 15 FPH800 Dual-IDU protection application

By R2.5, dual-IDU must be in 1 : 1 symmetrical configurations. This means that the two

IDUs must have exactly the same configurations, and the ports in LPG/YPG/LAG must

have the same port number. Any port must be in one of LPG/YPG/LAG and individual

port is not supported and cannot be used for port density expansion.

The supported number of services of dual-IDU is smaller than that of single IDU:

CESoP service: 48


35/84

A25000-A0800-E018-01-76P1


35


Ethernet service: 126

Dual-IDU LAG, Dual-IDU LPG, and dual-IDU YPG protection groups are supported in

FPH800 R2.5 Dual-IDU mode:

Dual-IDU LPG

FPH800 supports dual-IDU link protection group (LPG). LPG is considered as a logical

interface which has 2 Ethernet ports. Such two Ethernet ports are redundant for ODU

protection; these two Ethernet ports must be able to be configured across IDU, the LPG

member For LPG located on Dual IDU, the LPG member port must be any two ports on

different IDU.

When configured as dual-IDU, the two IDUs can be perceived logically as a single

device. The way LPG works over dual-IDU is the same as over single IDU. Please refer

to LPG protectionfor the details of LPG.

Dual-IDU LAG

One LAG group consists of two member ports. The traffic towards LAG group is distrib-uted to different group member via backplane based on Hash algorithm. When one LAG

member port is faulty, all traffic will switch to the other member port. LAG over dual-IDU

works in the same way as over single IDU. For more details on LAG, please refer to LAG

protection.

The LAG group only supports symmetrical location. One load balancing is required to

be supported by Dual IDU. 1+1 protection is not supported. For both active and standby

port in LAG, the QoS parameters (shaping, drop mode, queue depth, etc.) must be

exactly the same.

Dual-IDU YPG

FPH800 dual-IDU shall supports YPG functionality across IDU to protection.

YPG port can be electrical GE, optical GE, E1/T1 ports; PoE YPG is supported via dual-

IDU power injector, which supports up to two P + E YPG ports.

There are two members in each YPG group; only the port on active IDU is up, the other

port on standby IDU is down. The port status of YPG is strictly related with IDU status,

and the port status will change once IDU switch-over occurs.

Dual-IDU Protection Panel

Figure 16 Dual-IDU protection panel

Dual-IDU protection panel functions as a Y-cable hub. It is a completely passive device.

It support up to 8 electrical FE/GE interfaces, 16 E1 interfaces, and two optical interfaces

via the optional optical splitter module.

Due to the effect of changed impedance between the GE interfaces, it is required to plugin/out the cables between IDUs and the protection panel only on the protection panel


36/84

36 A25000-A0800-E018-01-76P1



side, which are connector B and D in the picture below. Otherwise, the Y-cable link

becomes down and will not come back automatically.

Figure 17 Cable requirement on Protection Panel

g Another limitation is the length of the cable between a user device (such as BTS) andthe protection panel, which is 70 m for Cat.6 UTP and 5 m for Cat.5 UTP. So it is highly

recommended to use Cat.6 UTP for this connection.

Dual-IDU Power Injector

This device functions as the Y-cable hub as well as power injector (i.e., P + E), so it is

used to connect with 1 + 0 ODU that needs IDU protection. It supports up to 4 ODUs.

Figure 18 Power Injector

g Dual-IDU Power Injector is an active device but it has a distributed architecture inside toachieve high availability. It is controlled by IDUs, as illustrated below.

Figure 19 Power Injector application


37/84

A25000-A0800-E018-01-76P1


37


To control Power Injector on which port group (A or B) should be open (while the other

group is turned down, i.e., disconnected from slave IDU), IDUs use Dry Contact port as

the control port. In this case, the dry contact function is moved to dual-IDU Power Injec-

tor. If dual-IDU Power Injector is not used, the dry contact port of each IDU supports only

1-in and 1-out (because the other pair of 1-in and 1-out pin is reserved for power injector

control), so overall there are still 2-in and 2-out dry contact alarms by the dual-IDU.

When one Power Injector use not enough (in case there are more than 4 ODUs),

another Power Injector can be cascaded, as shown below.

Figure 20 Power Injector cascading

g For details on Protection Panel and Power Injector, please refer to IDU AccessariesProduct Descriptionmanual.

Dual-IDU fail-over performance

As a device-level protection mechanism, the fail-over time of dual-IDU is typically 3 to 4

seconds when the active IDU fails, which is the same for LPG, YPG and LAG. However,

when the active IDU does not fail, port-level LPG and LAG switch-over may take place

and the switch-over time is much shorter. Below is a summary.

Protection type Switch time because of

link failure

Switch time because of

active IDU failure

LPG < 300 ms @ 10 ms ECCM < 500 ms

LAG < 500 ms 3 ~ 4 seconds

E1-YPG not protected < 1 s

Electrical GE-YPG via Pro-

tection panel

not protected 3 ~ 4 seconds

Optical GE-YPG via Pro-

tection panel


P + E YPG via Power

Injector


Table 4 Switch time table


38/84

38 A25000-A0800-E018-01-76P1



3.5 Link protection

3.5.1 RSTP/MSTP

FPRM800 implements the IEEE 802.1w Rapid Spanning Tree Protocol (RSTP) and the

IEEE 802.1s Multiple STP (MSTP). RSTP provides rapid convergence of the spanning

tree. MSTP, which uses RSTP to provide rapid convergence, enables VLANs to be

grouped into a spanning-tree instance. It provides for multiple forwarding paths for data

traffic, and enables load balancing. It improves the fault tolerance of the network

because a failure in one instance (forwarding path) does not affect the other instances

(forwarding paths). The most common initial deployment of MSTP and RSTP is in the

backbone and distribution layers of network.

The rapid spanning tree protocol (RSTP) provides full and symmetric connectivity in a

bridged LAN. It provides rapid reconfiguration of the spanning tree active topology in

case of physical network changes with reduced port states as forwarding, learning and

discarding only.

The multiple spanning tree protocol (MSTP) allows frames assigned to different VLANs

to follow separate paths. Each path is based on an independent multiple spanning tree

instance within multiple spanning tree regions. MSTP can support 8 MSTP instance.

Figure 21 MSTP illustration

Both RSTP and MSTP improve the operation of the spanning tree while maintaining

backward compatibility with equipment that is based on the (original) 802.1d spanning

tree.

BPDU Processing

At UNI port, there are three ways to process STP/RSTP/MSTP BPDU:

Peering: Processed at the UNI. The subscriber network becomes part of the network

for which a single STP is calculated.

Tunneling: Tunneled by the service. The service is perceived by the subscriber

network as a single segment. In this case, subscriber STP can be created between

its sites.


39/84

A25000-A0800-E018-01-76P1


39


Discarding: Dropped at the UNI. The subscriber should manually ensure that his

network does not contain loops going through the service.

Faster Hello Time

In RSTP/MSTP, standard Hello Time range is 1s~10s. In order to improve the conver-

gence time, FPH800 can set Hello Time between 100ms and 10s. 100ms Hello Time

will significantly reduce the convergence time, compared with 1s Hello Time.

Link OAM for RSTP/MSTP

In the case where FPH800 work together with 3rd party devices that do not support

xSTP, it may take very long (in 10s of seconds) to detect the failures between 3rd party

devices. In order to make RSTP/MSTP detect link fail much faster, FPH800 uses the

Link layer OAM to detect the link fail event. At 3.3 ms CCM, the link fails event will be

detected by FPH800 within 10 ms (3.3 ms x 3). RSTP/MSTP will use the Link layer OAMCFM event to trigger the RSTP/MSTP info aged event. When the OAM Link Layer MEP

is configured on a port and the port enabled RSTP/MSTP, the RSTP/MSTP will monitor

the OAM Connection Fault Event on this port.

g Through various enhancements to RSTP/MSTP, such as 100 ms hello time and LinkOAM, FPH800 has improved the switch-over performance of RSTP/MSTP while main-

taining compatibility with RSTP/MSTP.

g For the detailed information of RSTP/MSTP, please refer to IEEE 802.1d, 802.1w, and802.1 respectively.

3.5.2 LAG protection

Link aggregation grouping allows multiple links to be aggregated together to form a Link

Aggregation Group (LAG). A MAC client treats the LAG as if it is a single logical link. For

bridge functionality, the LAG is considered as a single bridge port. LAG consists of N

parallel full duplex point-to-point links.

LAG provides the following functionality:

Increased bandwidth

The capacity of multiple links is combined into one logical link.

Linearly incremental bandwidth

Increased availability

Load sharing

Automatic configuration

Rapid configuration and reconfiguration

Deterministic behavior

Low risk of duplication or mis-ordering

Support of existing IEEE 802.3 MAC clients

Backwards compatibility with aggregation

Accommodation of differing capabilities constraints

No change to the IEEE 802.3 frame format

Network management support


40/84

40 A25000-A0800-E018-01-76P1



g Only six Ethernet ports on the front panel can be configured for LAG.The member ports of LAG must be either all on the mainboard or on the same interface

card.

The frame distribution has 6 modes (from mode 1 to mode 6). The mode of frame distri-

bution is configurable per LAG. Mode 3 is the default mode.

Table 5displays the hash mode operation:

3.5.3 CESoPSN and SAToP linear protection

CESoPSN/SAToP linear protection is implemented as displayed in Figure 22. There are

two paths on packet network between two end nodes of this kind CES/SAToP protection

E-Line service. The protection uses one path as a working path and the other one as a

protection path. For one protected CESoPSN/SAToP service, once the working path is

broken, CES/SAToP traffic will be switched over to the protection path within 50 ms.

CES linear protection is supported by all the E1 ports and by 2-port FB card as well.

g Each CES service configured with CES linear protection must have its own EthernetPW. One Ethernet PW for multiple CES services is not allowed for CES linear protection.

Figure 22 End to end protection path

The allowed number of CES services terminated by one FPH800 is constrained by the

following two conditions:

1. Unprotected CESoPSN X 2 + Protected CESoPSN X 4


41/84

A25000-A0800-E018-01-76P1


41


g The system resources are split between Ethernet and CES services, and the CESand Ethernet service numbers are not related to each other.

3.5.4 G.8031 linear protectionFPH800 supports linear APS (Automatic Protection Switching) which complies with ITU-

T G.8031/Y.1342. G.8031 linear protection can only apply for point-to-point E-Line

service and requires Ethernet OAM (licensed) as pre-condition because OAM is the

mechanism used by G.8031 to detect failures on working (i.e., primary) path.

The following performance and features are to be considered when applying FPH800

G.8031 linear protection.

Limitation of the number of services

Given the system resources reserved for linear protection, the allowed number of

Ethernet services on one FPH800 is bounded to the following two conditions.

1. Unprotected E-LAN +Uprotected E-Line + Protected E-Line x 2


42/84

42 A25000-A0800-E018-01-76P1



SVLAN for working path and protection path

Two SVLANs are allocated for a G.8031 protected E-Line service, one on the

working path and another on the protection path. Even if there is no service traffic

on one of the paths, APS and CCM messages are still sent over it.

G.8031 and xSTP

G.8031 does not change any topology and thus xSTP active topology information is

not affected by G.8031. Meanwhile, since xSTP cannot apply to E-Line service,

there is no conflict between G.8031 and xSTP.

G.8031 and Ethernet OAM

CCM must run on each protected VLAN path, and CCM Loss/RDI/Link Down is used

to trigger linear protection switch-over. This means that G.8031 requires Ethernet

OAM so both the license for G.8031 and the license for Ethernet OAM have to be

installed.

G.8031 and LPG

An LPG is treated as single logical port by G.8031 linear protection. LPG protection

is perceived as a lower mechanism on port level while G.8031 higher layer, i.e.,

service layer, so practically LPG switch-over is required to be faster than G.8031

linear protection when there is a failure on the common path of LPG and G.8031.

However, the switch-over time of LPG only depends on its Hello time interval whose

vaule is 100 ms. Practically, the switch-over time of LPG is around 300 ms to 400

ms regardless of the number of services on the LPG. The switch-over time of

G.8031 may be faster than LPG if the affected number of services is relatively small.

Therefore, attention must be paid when G.8031 is configured over the path where

there are LPG ports. G.8031 hold-off timer can be configured to a higher value to

ensure that LPG switch-over completes before G.8031 switch-over is triggered. Oth-

erwise, unexpected result may arise.

E.g., there are 100 G.8031 protected E-Line services on an LPG port for 1 + 1 hot-standby ODU and G.8031 hold-off timer is 0 (by default). When LPG switch-over

process comes to an end. G.8031 may have switched some of the 100 services to

the protection path while leaving other services in the LPG port. But at this moment,

CCM LOS is cleared (meaning that CCM resumes) and these services will remain

on the LPG port which is on the working path.

In the case above, if user wants LPG switch-over to be completed before G.8031

switch-over is triggered (so that the service remain on the working path to reduce

network churn), he has to set a large G.8031 hold-off timer, e.g., 400 ms.

3.5.5 G.8032 ring protection

ITU-T G.8032 specifies protection switching mechanisms and protocol for Ethernet layer

network (ETH) Ethernet rings. Ethernet rings can provide wide-area multipoint connec-

tivity more economically due to their reduced number of links. The mechanisms and

protocol defined in G.8032 achieves highly reliable and stable protection; and never

form loops, which would fatally affect network operation and service availability.

In FPH800

Only single logical ring protection will be supported on one physical Ethernet port.

Ladder topology is not supported. This means that a GE port belongs only to one

ring.

Supports at least 4 single ring protection instances.

The ring port's physical media can be Optical GE, Electrical GE or Microwave.


43/84

A25000-A0800-E018-01-76P1


43


The hub site ring node supports single GE or LAG to connect to other networks.

Figure 23shows the ethernet ring protection architecture in normal condition.

Figure 23 Ethernet ring protection switching architecture - normal condition

g G.8032 only support 802.1ad mode.

3.5.5.1 G.8032 interworking with STP

In FPH800, G.8032 and STP can be enabled on one port at the same time. Some

VLANs (e.g., the management VLAN) can use STP to protect the traffic while some

other VLANs (e.g., data traffic VLAN) can use G.8032 to protect the traffic.

3.5.5.2 G.8032 interworking with LPG

FPH800 support G.8032 on LPG ring port.

3.5.6 UNI port shutdown upon service failureThe local UNI which the service has been created on will be shut down when the service

fails or remote UNI port is down. This feature can be applied only when there is only one

E-Line service on the UNI port.

The purpose of this feature is to propagate the network failure as quickly as possible to

the user network so that user network can switch traffic based on its own protection

mechanism.

3.5.7 STM-1 Multiplex Section Protection

MSP is supported to protect STM-1 ports from link failures, e.g., fiber broken.


44/84

44 A25000-A0800-E018-01-76P1



g The two STM-1 ports on the mainboard must work in non-revertive 1 + 1 unidirectionalMSP mode. No other alternative is supported.

The traffic behavior of MSP is source side bridges, sink side selects, see Figure 24:

Figure 24 STM-1 MSP protection

The quality criteria to trigger

Date post:	02-Jun-2018
Category:	Documents
Upload:	iqbal-muhammad
View:	232 times
Download:	0 times