Ceragon FibeAir IP-20G Technical Description 11.1 ETSI Rev A.01 PDF

Technical Description
FibeAir® IP-20G
April 2020 | ETSI Version

CeraOS Release: 11.1 | Rev A.01
© Copyright 2020 by Ceragon Networks Ltd. All rights reserved.
Technical Description for FibeAir IP-20G, CeraOS 11.1 (ETSI)
Notice
This document contains information that is proprietary to Ceragon Networks Ltd. No part of this publication
may be reproduced, modified, or distributed without prior written authorization of Ceragon Networks Ltd.
This document is provided as is, without warranty of any kind.
Trademarks
Ceragon Networks®, FibeAir® and CeraView® are trademarks of Ceragon Networks Ltd., registered in the
United States and other countries.
Ceragon® is a trademark of Ceragon Networks Ltd., registered in various countries.
CeraMap™, PolyView™, EncryptAir™, ConfigAir™, CeraMon™, EtherAir™, CeraBuild™, CeraWeb™, and
QuickAir™, are trademarks of Ceragon Networks Ltd.
Other names mentioned in this publication are owned by their respective holders.
Statement of Conditions
The information contained in this document is subject to change without notice. Ceragon Networks Ltd. shall
not be liable for errors contained herein or for damage in connection with the furnishing, performance, or
use of this document or equipment supplied with it.
Open Source Statement

The Product may use open source software, among them O/S software released under the GPL or GPL alike
license ("Open Source License"). Inasmuch that such software is being used, it is released under the Open
Source License, accordingly. The complete list of the software being used in this product including their
respective license and the aforementioned public available changes is accessible at:
Network element site: ftp://ne-open-source.license-system.com
NMS site: ftp://nms-open-source.license-system.com/
Information to User
Any changes or modifications of equipment not expressly approved by the manufacturer could void the
user’s authority to operate the equipment and the warranty for such equipment.
Intended Use/Limitation
Fixed point-to-point radio links for private networks.
Authorized to Use
Only entities with individual authorization from the National Regulator to operate the mentioned radio
equipment.
The equipment can be used in the following EU countries:
Austria (AT) - Belgium (BE) - Bulgaria (BG) - Switzerland/Liechtenstein (CH) - Cyprus (CY) - Czech Republic (CZ)
- Germany (DE) – Denmark (DK) - Estonia (EE) - Finland (FI) - France (FR) -Greece (GR) - Hungary (HU) -
Ireland (IE) – Iceland (IS) – Italy (IT) – Lithuania (LT) - Luxembourg (LU) – Latvia (LV) - Malta (MT) -
Netherlands (NL) - Norway (NO) - Portugal (PT) - Romania (RO) - Sweden (SE) - Slovenia (SI) - Slovak Republic
(SK) – United Kingdom (UK) – Spain (SP) – Poland (PL)
Page 2 of 322
Ceragon Proprietary and Confidential

Table of Contents
1. Synonyms and Acronyms ........................................................................................ 16
2. Introduction............................................................................................................ 19
2.1 Product Overview ...................................................................................................................... 20
2.1.1 IP-20G Radio Options ................................................................................................................. 21
2.1.2 FibeAir IP-20G Interoperability with other Ceragon Products ................................................... 22
2.1.3 IP-20G Highlights ........................................................................................................................ 22
2.1.4 IP-20G Protection Options ......................................................................................................... 22
2.2 Reference Configurations .......................................................................................................... 24
2.2.1 Dual Modem Activation ............................................................................................................. 24
2.2.2 IDU Dual-Modem Cascading Link ............................................................................................... 24
2.2.3 Chained Network ....................................................................................................................... 26
2.2.4 Ring with Spur ............................................................................................................................ 27
2.2.5 Aggregation/POP Site................................................................................................................. 27
2.3 FibeAir IP-20 Assured Platform .................................................................................................. 29
2.4 New Features in CeraOS 11.1 .................................................................................................... 30
3. IDU Hardware Description ....................................................................................... 31

3.1 Hardware Architecture .............................................................................................................. 32
3.2 Front Panel Description ............................................................................................................. 34
3.3 Ethernet Traffic Interfaces ......................................................................................................... 35
3.4 Ethernet Management Interfaces .............................................................................................. 36
3.5 E1 Interface (Optional) ............................................................................................................... 36
3.6 Radio Interfaces ......................................................................................................................... 37
3.7 Power Interface.......................................................................................................................... 37
3.8 Synchronization Interface .......................................................................................................... 37
3.9 Terminal Interface...................................................................................................................... 38
3.10 External Alarms .......................................................................................................................... 38
3.11 Storage Memory Card ................................................................................................................ 39
3.12 Hardware Assembly Options...................................................................................................... 40
3.13 FibeAir IP-20G Unit Redundancy ................................................................................................ 42
3.13.1 Ethernet Interface Protection with IP-20G Unit Redundancy.................................................... 42
3.13.2 Supported Radio Configurations with Unit Redundancy ........................................................... 43
3.13.3 E1 Interface Protection with IP-20G Unit Redundancy .............................................................. 45
3.13.4 T3 Synchronization with Unit Redundancy ................................................................................ 46
3.13.5 Management for Unit Redundancy ........................................................................................... 46
3.13.6 Switchover ................................................................................................................................. 47
4. RFU Hardware Description and Branching Options ................................................... 48

4.1 RFU Overview............................................................................................................................. 49
4.2 RFU Selection Guide ................................................................................................................... 50
Page 3 of 322

4.3 RFU-C ......................................................................................................................................... 51

4.3.1 Main Features of RFU-C ............................................................................................................. 51
4.3.2 RFU-C Functional Block Diagram ................................................................................................ 52
4.4 1500HP/RFU-HP ......................................................................................................................... 53
4.4.1 Main Features of 1500HP/RFU-HP ............................................................................................. 53
4.4.2 1500HP/RFU-HP Functional Block Diagram and Concept of Operation .................................... 55
4.4.3 1500HP/RFU-HP Comparison Table ........................................................................................... 57
4.4.4 1500HP/RFU-HP System Configurations .................................................................................... 58
4.4.5 Space Diversity with IF Combining ............................................................................................. 58
4.4.6 Split Mount Configuration and Branching Network .................................................................. 59
4.4.7 1500HP/RFU-HP Models and Part Numbers .............................................................................. 64
4.4.8 OCB Part Numbers ..................................................................................................................... 65
5. Activation Keys ....................................................................................................... 67

5.1 Working with Activation Keys .................................................................................................... 67
5.2 Demo Mode ............................................................................................................................... 67
5.3 Activation Key Reclaim ............................................................................................................... 68
5.4 Activation Key-Enabled Features ............................................................................................... 68
6. Feature Description................................................................................................. 74
6.1 Innovative Techniques to Boost Capacity and Reduce Latency ................................................. 75
6.1.1 Capacity Summary ..................................................................................................................... 76
6.1.2 Header De-Duplication............................................................................................................... 77
6.1.3 Latency ....................................................................................................................................... 80
6.1.4 Frame Cut-Through .................................................................................................................... 81
6.2 Radio Features ........................................................................................................................... 83
6.2.1 Adaptive Coding Modulation (ACM) .......................................................................................... 84
6.2.2 Cross Polarization Interference Canceller (XPIC) ....................................................................... 89
6.2.3 1+1 HSB Radio Protection .......................................................................................................... 92
6.2.4 ATPC ........................................................................................................................................... 94
6.2.5 Multi-Carrier ABC ....................................................................................................................... 95
6.2.6 BBS Space Diversity .................................................................................................................... 98
6.2.7 Radio Signal Quality PMs .........................................................................................................100
6.2.8 Radio Utilization PMs ...............................................................................................................101
6.3 Ethernet Features ....................................................................................................................102
6.3.1 Ethernet Services Overview .....................................................................................................103
6.3.2 IP-20G’s Ethernet Capabilities .................................................................................................119
6.3.3 Supported Standards ...............................................................................................................120
6.3.4 Ethernet Service Model ...........................................................................................................121
6.3.5 Ethernet Interfaces ..................................................................................................................138
6.3.6 Quality of Service (QoS) ...........................................................................................................148
6.3.7 Global Switch Configuration ....................................................................................................177
6.3.8 Automatic State Propagation and Link Loss Forwarding .........................................................178
6.3.9 Network Resiliency ..................................................................................................................180
6.3.10 OAM .........................................................................................................................................186
6.4 Synchronization .......................................................................................................................190
6.4.1 Synchronization Overview .......................................................................................................191
Page 4 of 322

6.4.2 IP-20G Synchronization Solution..............................................................................................193

6.4.3 Native Sync Distribution Mode ................................................................................................194
6.4.4 SyncE PRC Pipe Regenerator Mode .........................................................................................200
6.4.5 IEEE-1588v2 PTP Optimized Transport ....................................................................................201
6.5 TDM Services............................................................................................................................208
6.5.1 Native TDM Trails .....................................................................................................................209
6.5.2 TDM Pseudowire ......................................................................................................................213
6.5.3 TDM Reference Solutions ........................................................................................................218
6.6 Radio Payload Encryption and FIPS ..........................................................................................220
6.6.1 AES-256 Payload Encryption ....................................................................................................220
6.6.2 FIPS 140-2 Compliance .............................................................................................................222
7. FibeAir IP-20G Management.................................................................................. 224

7.1 Management Overview ...........................................................................................................225
7.2 Automatic Network Topology Discovery with LLDP Protocol ..................................................227
7.3 Management Communication Channels and Protocols ..........................................................228
7.4 Web-Based Element Management System (Web EMS) ..........................................................230
7.5 SDN Support .............................................................................................................................232
7.6 Command Line Interface (CLI) ..................................................................................................233
7.7 Configuration Management .....................................................................................................233
7.8 Software Management ............................................................................................................234
7.8.1 Backup Software Version .........................................................................................................234
7.9 CeraPlan Service for Creating Pre-Defined Configuration Files ...............................................235
7.10 IPv6 Support .............................................................................................................................236
7.11 In-Band Management ..............................................................................................................236
7.12 Local Management ..................................................................................................................236
7.13 Alarms ......................................................................................................................................237
7.13.1 Configurable BER Threshold Alarms and Traps ........................................................................237
7.13.2 RSL Threshold Alarm ................................................................................................................237
7.13.3 Editing and Disabling Alarms and Events .................................................................................237
7.13.4 Timeout for Trap Generation ...................................................................................................237
7.14 External Alarms ........................................................................................................................238
7.15 NTP Support .............................................................................................................................238
7.16 UTC Support .............................................................................................................................238
7.17 System Security Features .........................................................................................................239
7.17.1 Ceragon’s Layered Security Concept........................................................................................239
7.17.2 Defenses in Management Communication Channels ..............................................................240
7.17.3 Defenses in User and System Authentication Procedures .......................................................241
7.17.4 Secure Communication Channels ............................................................................................244
7.17.5 Security Log ..............................................................................................................................247
7.17.6 Anti-Theft .................................................................................................................................248
Page 5 of 322

8. Standards and Certifications .................................................................................. 250

8.1 Supported Ethernet Standards ................................................................................................251
8.2 MEF Certifications for Ethernet Services .................................................................................252
8.3 Supported TDM Pseudowire Encapsulations ...........................................................................253
8.4 Standards Compliance .............................................................................................................253
8.5 Network Management, Diagnostics, Status, and Alarms.........................................................254
9. Specifications........................................................................................................ 255
9.1 General Radio Specifications ...................................................................................................256
9.2 Radio Scripts ............................................................................................................................257
9.3 Radio Capacity Specifications ..................................................................................................259
9.3.1 Radio Capacity Specifications (no XPIC) ...................................................................................259
9.3.2 Radio Capacity Specifications with XPIC ..................................................................................266
9.4 Transmit Power Specifications (dBm) ......................................................................................274
9.4.1 Transmit Power with RFU-C (dBm) ..........................................................................................274
9.4.2 Transmit Power with 1500HP/RFU-HP (dBm) ..........................................................................276
9.5 Receiver Threshold (RSL) .........................................................................................................278
9.5.1 Receiver Thresholds with RFU-C ..............................................................................................278
9.5.2 Receiver Thresholds with RFU-HP ............................................................................................281
9.5.3 Receiver Thresholds with 1500HP ...........................................................................................283
9.6 Frequency Bands ......................................................................................................................285
9.6.1 Frequency Bands – RFU-C ........................................................................................................285
9.6.2 Frequency Bands – 1500HP and RFU-HP .................................................................................296
9.7 Mediation Device Losses ..........................................................................................................297
9.7.1 RFU-C Mediation Device Losses ...............................................................................................297
9.7.2 1500HP/RFU-HP Branching Network Losses ............................................................................298
9.8 Ethernet Latency Specifications ...............................................................................................303
9.8.1 Ethernet Latency – 1.75 MHz Channel Bandwidth ..................................................................303
9.8.2 Ethernet Latency – 3.5 MHz Channel Bandwidth ....................................................................303
9.8.3 Ethernet Latency – 7 MHz Channel Bandwidth .......................................................................304
9.8.4 Ethernet Latency – 14 MHz Channel Bandwidth .....................................................................304
9.9 Ethernet Specifications ............................................................................................................307
9.9.1 Ethernet Interface Specifications .............................................................................................307
9.9.2 Carrier Ethernet Functionality .................................................................................................307
9.9.3 Approved GbE SFP Modules ....................................................................................................308
9.10 TDM Specifications ..................................................................................................................309
9.10.1 E1 Cross Connect .....................................................................................................................309
9.10.2 E1 Interface Specifications .......................................................................................................309
9.10.3 Pseudowire Specifications .......................................................................................................309
9.11 Synchronization Specifications ................................................................................................310
Page 6 of 322

9.12 Mechanical Specifications ........................................................................................................311

9.13 Environmental Specifications ...................................................................................................312
9.13.1 Environmental Specifications for IDU ......................................................................................312
9.13.2 Environmental Specifications for RFU ......................................................................................312
9.14 Supported Antenna Types .......................................................................................................313
9.14.1 RFU-C Antenna Connection .....................................................................................................313
9.14.2 1500HP/RFU-HP Antenna Connection .....................................................................................313
9.15 Waveguide Specifications ........................................................................................................314
9.15.1 RFU-C Waveguide Specifications .............................................................................................314
9.15.2 1500HP/RFU-HP Waveguide Specifications .............................................................................314
9.16 Antenna Interface Requirements for RFU-HP/1500HP ............................................................315
9.17 Power Input Specifications ......................................................................................................316
9.18 Power Consumption Specifications .........................................................................................316
10. Annex 1: RFU-HP Transmit Power and RSL at Radio Ports ....................................... 317
10.1 Transmit Power Specifications (dBm) ......................................................................................317
10.2 Receiver Threshold Specifications ...........................................................................................319
10.2.1 Receiver Threshold – RFU-HP ..................................................................................................319
10.2.2 Receiver Threshold – 1500HP ..................................................................................................321
Page 7 of 322

List of Figures
Figure 1: Reference Configuration – Dual Modem Activation ...............................................................24
Figure 2: Reference Configuration – IDU Cascading with Dual Modems ...............................................25
Figure 3: Reference Configuration – Chained Network .........................................................................26
Figure 4: Reference Configuration – Ring with Spur ..............................................................................27
Figure 5: Reference Configuration – Aggregation/POP Site ...................................................................28
Figure 6: IP-20G Block Diagram ..............................................................................................................33
Figure 7: IP-20G Front Panel and Interfaces ..........................................................................................34
Figure 8: Management Interface Pin Connections .................................................................................36
Figure 9: SM Card and Cover ..................................................................................................................39
Figure 10: Unit Redundancy – 2 x 1+0 – Ethernet Line Protection Mode ..............................................43
Figure 11: Unit Redundancy – 2 x 1+0 – Splitter Mode ..........................................................................44
Figure 12: Unit Redundancy – 2 x 2+0 – Ethernet Line Protection Mode ..............................................44
Figure 13: Unit Redundancy – 2 x 2+0 – Splitter Mode ..........................................................................45
Figure 14: E1 Interface Protection with IP-20G Unit Redundancy .........................................................45
Figure 15: IP-20G with Unit Redundancy – Protection and Management Splitter Connection .............46
Figure 16: RFU-C Functional Block Diagram – 1+0 Configuration ..........................................................52
Figure 17: 1500HP 2RX in 1+0 SD Configuration ....................................................................................55
Figure 18: 1500HP 1RX in 1+0 SD Configuration ....................................................................................55
Figure 19: RFU-HP 1RX in 1+0 SD Configuration ....................................................................................56
Figure 20: All-Indoor Vertical Branching ...............................................................................................59
Figure 21: Split-Mount Branching and All-Indoor Compact ..................................................................59
Figure 22: Old OCB .................................................................................................................................60
Figure 23: OCB ........................................................................................................................................60
Figure 24: OCB and DCB Block Diagrams................................................................................................61
Figure 25: Header De-Duplication ..........................................................................................................77
Figure 26: Header De-Duplication Potential Throughput Savings per Layer ..........................................78
Figure 27: Propagation Delay with and without Frame Cut-Through ....................................................81
Figure 28: Frame Cut-Through ...............................................................................................................82
Figure 29: Frame Cut-Through Operation ..............................................................................................82
Figure 30: Adaptive Coding and Modulation with 11 Working Points ...................................................85
Figure 31: ACM with Adaptive Power Contrasted to Other ACM Implementations ..............................88
Figure 32: Dual Polarization ...................................................................................................................89
Figure 33: XPIC Implementation ............................................................................................................90
Figure 34: XPIC – Impact of Misalignments and Channel Degradation ..................................................90
Figure 35: Path Loss on Secondary Path of 1+1 HSB Protection Link .....................................................93
Page 8 of 322

Figure 36: Multi-Carrier ABC Traffic Flow...............................................................................................95

Figure 37: Multi-Carrier ABC Minimum Bandwidth Override ................................................................97
Figure 38: Direct and Reflected Signals ..................................................................................................98
Figure 39: 1+1 BBS Space Diversity Configuration – Receiving Side ......................................................99
Figure 40: Basic Ethernet Service Model ..............................................................................................103
Figure 41: Ethernet Virtual Connection (EVC) ......................................................................................104
Figure 42: Point to Point EVC ...............................................................................................................105
Figure 43: Multipoint to Multipoint EVC ..............................................................................................105
Figure 44: Rooted Multipoint EVC ........................................................................................................105
Figure 45: MEF Ethernet Services Definition Framework ....................................................................107
Figure 46: E-Line Service Type Using Point-to-Point EVC .....................................................................108
Figure 47: EPL Application Example .....................................................................................................109
Figure 48: EPL Application Example .....................................................................................................109
Figure 49: EVPL Application Example ...................................................................................................110
Figure 50: E-LAN Service Type Using Multipoint-to-Multipoint EVC ....................................................110
Figure 51: Adding a Site Using an E-Line service ..................................................................................111
Figure 52: Adding a Site Using an E-LAN service ..................................................................................111
Figure 53: MEF Ethernet Private LAN Example ....................................................................................112
Figure 54: MEF Ethernet Virtual Private LAN Example.........................................................................113
Figure 55: E-Tree Service Type Using Rooted-Multipoint EVC .............................................................113
Figure 56: E-Tree Service Type Using Multiple Roots ...........................................................................114
Figure 57: MEF Ethernet Private Tree Example ...................................................................................115
Figure 58: Ethernet Virtual Private Tree Example ................................................................................116
Figure 59: Mobile Backhaul Reference Model .....................................................................................116
Figure 60: Packet Service Core Building Blocks ....................................................................................117
Figure 61: IP-20G Services Model ........................................................................................................121
Figure 62: IP-20G Services Core ...........................................................................................................122
Figure 63: IP-20G Services Flow ...........................................................................................................123
Figure 64: Point-to-Point Service .........................................................................................................124
Figure 65: Multipoint Service ...............................................................................................................125
Figure 66: Management Service ..........................................................................................................127
Figure 67: Management Service and its Service Points .......................................................................129
Figure 68: SAPs and SNPs .....................................................................................................................130
Figure 69: Pipe Service Points ..............................................................................................................131
Figure 70: SAP, SNP and Pipe Service Points in a Microwave Network ...............................................131
Figure 71: Service Path Relationship on Point-to-Point Service Path ..................................................135
Figure 72: Physical and Logical Interfaces ............................................................................................138
Page 9 of 322

Figure 73: Grouped Interfaces as a Single Logical Interface on Ingress Side .......................................139
Figure 74: Grouped Interfaces as a Single Logical Interface on Egress Side ........................................139
Figure 75: Relationship of Logical Interfaces to the Switching Fabric ..................................................143
Figure 76: QoS Block Diagram ..............................................................................................................148
Figure 77: Standard QoS and H-QoS Comparison ................................................................................150
Figure 78: Hierarchical Classification ...................................................................................................151
Figure 79: Classification Method Priorities ..........................................................................................152
Figure 80: Ingress Policing Model ........................................................................................................157
Figure 81: IP-20G Queue Manager .......................................................................................................160
Figure 82: Synchronized Packet Loss ....................................................................................................161
Figure 83: Random Packet Loss with Increased Capacity Utilization Using WRED ..............................162
Figure 84: WRED Profile Curve .............................................................................................................163
Figure 85: Detailed H-QoS Diagram .....................................................................................................166
Figure 86: Scheduling Mechanism for a Single Service Bundle ............................................................169
Figure 87: G.8032 Ring in Idle (Normal) State ......................................................................................181
Figure 88: G.8032 Ring in Protecting State ..........................................................................................182
Figure 89: Load Balancing Example in G.8032 Ring ..............................................................................182
Figure 90: IP-20G End-to-End Service Management ............................................................................186
Figure 91: SOAM Maintenance Entities (Example) ..............................................................................187
Figure 92: Ethernet Line Interface Loopback – Application Examples .................................................188
Figure 93: Native Sync Distribution Mode ...........................................................................................194
Figure 94: Synchronization Configuration ............................................................................................196
Figure 95: Native Sync Distribution Mode Usage Example ..................................................................198
Figure 96: Native Sync Distribution Mode – Tree Scenario ..................................................................198
Figure 97: Native Sync Distribution Mode – Ring Scenario (Link Failure) ............................................199
Figure 98: Synchronous Ethernet (SyncE) ............................................................................................200
Figure 99: IEEE-1588v2 PTP Optimized Transport – General Architecture ..........................................201
Figure 100: Calculating the Propagation Delay for PTP Packets ..........................................................202
Figure 101: Transparent Clock – General Architecture ........................................................................205
Figure 102: Transparent Clock Delay Compensation ...........................................................................206
Figure 103: Figure 104: Boundary Clock – General Architecture .........................................................207
Figure 105: Hybrid Ethernet and TDM Services ...................................................................................208
Figure 106: Hybrid Ethernet and TDM Services Carried Over Cascading Interfaces ............................208
Figure 107: Hybrid Ethernet and Native TDM Services ........................................................................209
Figure 108: 1:1 TDM Path Protection – Ring Topology ........................................................................211
Figure 109: 1+1 TDM Path Protection – Dual Homing Topology .........................................................211
Figure 110: All-Packet Ethernet and TDM Pseudowire Services ..........................................................213
Page 10 of 322

Figure 111: Native TDM Trail Interoperability with Optical SDH Equipment .......................................218
Figure 112: Native TDM Trail Interoperability with TDM Pseudowire-over-Packet.............................218
Figure 113: TDM Pseudowire Interoperability with Optical SDH Equipment ......................................218
Figure 114: TDM Pseudowire Interoperability with Third-Party Packet Aggregation Equipment .......219
Figure 115: AES-256 Encrypted Link .....................................................................................................220
Figure 116: Integrated IP-20G Management Tools ..............................................................................226
Figure 117: Security Solution Architecture Concept ............................................................................239
Figure 118: RFU-HP Branching System using Adjacent Channel OCBs .................................................299
Figure 119: RFU-HP Branching System using Symmetrical Coupler .....................................................299
Figure 120: Four-Adjacent Channel Configuration using Symmetrical Coupler ...................................300
Page 11 of 322

List of Tables
Table 1: Synonyms and Acronyms ---------------------------------------------------------------------------------------- 16
Table 2: New Features in CeraOS 11.1 ---------------------------------------------------------------------------------- 30
Table 3: IP-20G Interfaces -------------------------------------------------------------------------------------------------- 34
Table 4: Hardware Assemblies --------------------------------------------------------------------------------------------- 40
Table 5: Y-Cable for Electrical Splitter Mode FE Traffic Interface Protection --------------------------------- 42
Table 6: Y-Cable for E1 Protection ---------------------------------------------------------------------------------------- 45
Table 7: Splitter Cable for Protection and Management ----------------------------------------------------------- 46
Table 8: RFU Selection Guide ---------------------------------------------------------------------------------------------- 50
Table 9: 1500HP/RFU-HP Comparison Table -------------------------------------------------------------------------- 57
Table 10: OCB Component Summary ------------------------------------------------------------------------------------ 62
Table 11: RFU Models – 1RX Units---------------------------------------------------------------------------------------- 64
Table 12: RFU Models – 2RX Units---------------------------------------------------------------------------------------- 64
Table 13: OCB Part Numbers ----------------------------------------------------------------------------------------------- 65
Table 14: OCB Part Number Format ------------------------------------------------------------------------------------- 66
Table 15: Activation Key Types -------------------------------------------------------------------------------------------- 68
Table 16: Capacity Activation Key Levels ------------------------------------------------------------------------------- 71
Table 17: CET Node Activation Key Levels ------------------------------------------------------------------------------ 72
Table 54: Edge CET Note Upgrade Activation Keys ------------------------------------------------------------------ 73
Table 18: ACM Working Points (Profiles) ------------------------------------------------------------------------------- 84
Table 19: MEF-Defined Ethernet Service Types --------------------------------------------------------------------- 107
Table 20: Ethernet Services Learning and Forwarding ------------------------------------------------------------ 126
Table 21: Service Point Types per Service Type --------------------------------------------------------------------- 132
Table 22: Service Point Types that can Co-Exist on the Same Interface -------------------------------------- 133
Table 23: Service Point Type-Attached Interface Type Combinations that can Co-Exist on the Same
Interface ----------------------------------------------------------------------------------------------------------------------- 134
Table 24: C-VLAN 802.1 UP and CFI Default Mapping to CoS and Color ------------------------------------- 152
Table 25: S-VLAN 802.1 UP and DEI Default Mapping to CoS and Color ------------------------------------- 153
Table 26: MPLS EXP Default Mapping to CoS and Color ---------------------------------------------------------- 153
Table 27: DSCP Default Mapping to CoS and Color ---------------------------------------------------------------- 154
Table 28: QoS Priority Profile Example -------------------------------------------------------------------------------- 170
Table 29: WFQ Profile Example------------------------------------------------------------------------------------------ 172
Table 30: 802.1q UP Marking Table (C-VLAN) ----------------------------------------------------------------------- 174
Table 31: 802.1ad UP Marking Table (S-VLAN) ---------------------------------------------------------------------- 175
Table 32: Summary and Comparison of Standard QoS and H-QoS -------------------------------------------- 176
Table 33: Native Sync Interface Options ------------------------------------------------------------------------------ 195
Page 12 of 322

Table 34: Boundary Clock Input Options ------------------------------------------------------------------------------ 207

Table 35: Boundary Clock Output Options --------------------------------------------------------------------------- 207
Table 36: IP-20G Model Supporting 1588 Boundary Clock ------------------------------------------------------ 207
Table 37: Dedicated Management Ports ------------------------------------------------------------------------------ 228
Table 38: Supported Ethernet Standards ----------------------------------------------------------------------------- 251
Table 39: Supported MEF Specifications ------------------------------------------------------------------------------ 252
Table 40: MEF Certifications --------------------------------------------------------------------------------------------- 252
Table 41: Supported TDM Pseudowire Encapsulations ----------------------------------------------------------- 253
Table 42: Standards Compliance ---------------------------------------------------------------------------------------- 253
Table 43: Network Management, Diagnostics, Status, and Alarms -------------------------------------------- 254
Table 44: General Radio Specifications -------------------------------------------------------------------------------- 256
Table 45: MRMC Radio Scripts ------------------------------------------------------------------------------------------- 258
Table 46: 1.75 MHz – Script ID 1075 ----------------------------------------------------------------------------------- 259
Table 47: 3.5 MHz – Script ID 1023 ------------------------------------------------------------------------------------- 260
Table 48: 7 MHz – Script ID 1008 --------------------------------------------------------------------------------------- 260
Table 49: 14 MHz – Script ID 1009 -------------------------------------------------------------------------------------- 261
Table 63: Transmit Power with RFU-C (dBm) ------------------------------------------------------------------------ 274
Table 64: Pmin Power with RFU-C -------------------------------------------------------------------------------------- 275
Table 65: Transmit Power with 1500HP/RFU-HP (dBm) ---------------------------------------------------------- 276
Table 66: Transmit Power for RFU-HP 2RX (1500HP) (dBm) ----------------------------------------------------- 277
Table 67: Receiver Thresholds with RFU-C --------------------------------------------------------------------------- 278
Table 68: Receiver Thresholds with RFU-HP ------------------------------------------------------------------------- 281
Table 69: Receiver Thresholds with 1500HP ------------------------------------------------------------------------- 283
Table 70: Frequency Bands – RFU-C------------------------------------------------------------------------------------ 285
Page 13 of 322

Table 71: Frequency Bands – 1500HP and RFU-HP ---------------------------------------------------------------- 296

Table 72: RFU-C Mediation Device Losses ---------------------------------------------------------------------------- 297
Table 73: 1500HP/RFU-HP Branching Network Losses ------------------------------------------------------------ 298
Table 74: Additional Losses ----------------------------------------------------------------------------------------------- 298
Table 75: 1500HP/RFU-HP All-Indoor Branching Loss ------------------------------------------------------------- 301
Table 76: Ethernet Latency – 1.75 MHz Channel Bandwidth ---------------------------------------------------- 303
Table 77: Ethernet Latency – 3.5 MHz Channel Bandwidth ----------------------------------------------------- 303
Table 78: Ethernet Latency – 7 MHz Channel Bandwidth -------------------------------------------------------- 304
Table 79: Ethernet Latency – 14 MHz Channel Bandwidth ------------------------------------------------------ 304
Table 80: 28 MHz Channel Bandwidth -------------------------------------------------------------------------------- 305
Table 83: Ethernet Interface Specifications -------------------------------------------------------------------------- 307
Table 84: Carrier Ethernet Functionality ------------------------------------------------------------------------------ 307
Table 85: Approved GbE SFP Modules -------------------------------------------------------------------------------- 308
Table 86: E1 Cross Connect Specifications --------------------------------------------------------------------------- 309
Table 87: E1 Interface Specifications ---------------------------------------------------------------------------------- 309
Table 88: Pseudowire Specifications ----------------------------------------------------------------------------------- 309
Table 89: Synchronization Specifications ----------------------------------------------------------------------------- 310
Table 90: IDU Mechanical Specifications ----------------------------------------------------------------------------- 311
Table 91: RFU-C Mechanical Specifications -------------------------------------------------------------------------- 311
Table 92: 1500HP/RFUHP Mechanical Specifications ------------------------------------------------------------- 311
Table 93: RFU-C – Waveguide Flanges--------------------------------------------------------------------------------- 314
Table 94: 1500HP/RFU-HP – Waveguide Flanges ------------------------------------------------------------------- 314
Table 95: 1500HP/RFU-HP Antenna Interface Requirements --------------------------------------------------- 315
Table 96: Power Input Specifications ---------------------------------------------------------------------------------- 316
Table 97: Power Consumption Specifications ----------------------------------------------------------------------- 316
Table 98: Transmit Power Specifications for RFU-HP 1RX (dBm) ----------------------------------------------- 317
Table 99: Transmit power specifications for RFU-HP 2RX (1500HP) (dBm) --------------------------------- 318
Table 100: Receiver Threshold – RFU-HP ----------------------------------------------------------------------------- 319
Table 101: Receiver Threshold – 1500HP ----------------------------------------------------------------------------- 321
Page 14 of 322

About This Guide

This document describes the main features, components, and specifications of the FibeAir
IP-20G system. This document applies to CeraOS version 11.1.
What You Should Know

This document describes applicable ETSI standards and specifications. An ANSI version of
this document is also available.
Target Audience
This manual is intended for use by Ceragon customers, potential customers, and business
partners. The purpose of this manual is to provide basic information about the FibeAir IP-
20G for use in system planning, and determining which FibeAir IP-20G configuration is best
suited for a specific network.
Related Documents
• FibeAir IP-20 CeraOS Version 11.1 Release Notes for All-Indoor and Split-Mount
Systems
• FibeAir CeraOS Version 11.1 User Guide for IP-20F, IP-20G, and IP-20GX
• FibeAir IP-20G Installation Guide
• FibeAir IP-20 Series MIB Reference
Page 15 of 322

1. Synonyms and Acronyms

Table 1: Synonyms and Acronyms
Acronym Equivalent Term
ACAP Adjacent Channel Alternate Polarization

ACCP Adjacent Channel Co-Polarization
ACM Adaptive Coding and Modulation
AES Advanced Encryption Standard
AFR Advanced Frequency Reuse
AIS Alarm Indication Signal
AT Anti-Theft
ATPC Automatic Tx Power Control
BBS Baseband Switching
BER Bit Error Ratio
BLSR Bidirectional Line Switch Ring
BMCA Best Master Clock Algorithm
BPDU Bridge Protocol Data Units
BWA Broadband Wireless Access
CBS Committed Burst Size
CCDP Co-Channel Dual Polarization
CE Customer Equipment
CET Carrier-Ethernet Transport
CFM Connectivity Fault Management
CIR Committed Information Rate
CLI Command Line Interface
CoS Class of Service
DA Destination Address
DSCP Differentiated Service Code Point
EBS Excess Burst Size
EIR Excess Information Rate
EPL Ethernet Private Line
ETH-BN Ethernet Bandwidth Notification
EVPL Ethernet Virtual Private Line
EVC Ethernet Virtual Connection
Page 16 of 322

FEC Forward Error Correction

FTP (SFTP) File Transfer Protocol (Secured File Transfer Protocol)
GbE Gigabit Ethernet
HTTP (HTTPS) Hypertext Transfer Protocol (Secured HTTP)
IPsec Internet Security Protocol
LACP Link Aggregation Control Protocol
LAN Local area network
LLF Link Loss Forwarding
LOC Loss of Carrier
LOF Loss of Frame
LoS Line of Sight
LOS Loss of Signal
LTE Long-Term Evolution
MEN Metro Ethernet Network
MIMO Multiple Input Multiple Output
MPLS Multiprotocol Label Switching
MRU Maximum Receive Unit
MSE Mean Square Error
MSP Multiplex Section Protection
MSTP Multiple Spanning Tree Protocol
MTU Maximum Transmit Capability
MultiCore Radio A system optimized for flexible parallel processing of several radio
System signal flows, thus inherently multiplying the capacity and
increasing system gain using existing spectral resources.
NLoS Non-Line-of-Sight
NMS Network Management System
NSMA National Spectrum Management Association
NTP Network Time Protocol
OAM Operation Administration & Maintenance (Protocols)
PDV Packed Delay Variation
PIR Peak Information Rate
PM Performance Monitoring
PN Provider Network (Port)
PTP Precision Timing-Protocol
QoE Quality of-Experience
Page 17 of 322

QoS Quality of Service

RBAC Role-Based Access Control
RDI Reverse Defect Indication
RMON Ethernet Statistics
RSA Rivest–Shamir–Adleman public-key cryptosystem
RSL Received Signal Level
RSTP Rapid Spanning Tree Protocol
SAP Service Access Point
SD Space Diversity
SDN Software-Defined Networking
SFTP Secure FTP
SISO Single-Input Single-Output
SLA Service level agreements
SNMP Simple Network Management Protocol
SNP Service Network Point
SNR Signal-to-Noise Ratio
SNTP Simple Network Time Protocol
SP Service Point
STP Spanning Tree Protocol
SSH Secured Shell (Protocol)
SSM Synchronization Status Messages
SyncE Synchronous Ethernet
TACACS+ Terminal Access Controller Access-Control System Plus
TC Traffic Class
TOS Type of Service
UNI User Network Interface
UTC Coordinated Universal Time
VC Virtual Containers
Web EMS Web-Based Element Management System
WG Wave guide
WFQ Weighted Fair Queue
WRED Weighted Random Early Detection
XPIC Cross Polarization Interference Cancellation
Page 18 of 322

2. Introduction
This chapter provides an overview of the FibeAir IP-20G, Ceragon’s high-
performance edge node product. IP-20G is specially designed for edge/tail sites,
and features a small footprint, high density, and a high degree of availability.
IP-20G is an integral part of the FibeAir family of high-capacity wireless backhaul
products. Together, the FibeAir family of products provides a wide variety of
backhaul solutions that can be used separately or combined to form integrated
backhaul networks or network segments.
This enables operators to utilize a combination of FibeAir IDUs and radio units
(RFUs) to build networks in which the most appropriate FibeAir product can be
utilized for each node in the network to provide the feature support, capacity
support, frequency range, density, and footprint that is optimized to meet the
needs of that particular node. The FibeAir series “pay-as-you-go” activation key
models further enable operators to build for the future by adding capacity and
functionality over time to meet the needs of network growth without the need to
add additional hardware.
This chapter includes:

• Product Overview
• Reference Configurations
• FibeAir IP-20 Assured Platform
• New Features in CeraOS 11.1
Page 19 of 322

2.1 Product Overview

FibeAir IP-20G is a compact wireless backhaul node that is optimized for tail and
edge/chain nodal deployment, with a small footprint, high density, and a high
degree of availability.
IP-20G includes an advanced feature set for Carrier Ethernet Transport, including
a sophisticated Ethernet services engine, cutting-edge header de-duplication
techniques, frame cut-through, and more.
IP-20G can also include the following optional features:
• Multi-carrier package including two radio channels and radio interfaces.
• 16 x E1 interfaces, with advanced support for TDM services.
• Dual-feed power option for power redundancy.
FibeAir IP-20G is built specifically for tail/edge sites deployments. It is based on
the same architecture and technology as FibeAir IP-20N, and supports essentially
the same feature set but in a fixed form-factor and on a scale that is optimized for
tail/edge sites.
The following interfaces are supported:
• 6 x 1 GbE interfaces total
◦ 2 x dual mode GbE electrical or cascading interfaces (RJ-45)
◦ 2 x GbE electrical interfaces (RJ-45)
◦ 2x GbE optical interfaces (SFP)
• Optional: 16 x E1 interfaces
• Single or dual radio interfaces (TNC)
• Single or dual power-feeds (-48v)
• Sync in/out interface
• Management interfaces
◦ Terminal – RS232 (RJ-45)
◦ 2x FE electrical interfaces (RJ-45)
• External alarms interface
FibeAir IP-20G is based on a passive cooling design that does not require fans, for
improved operational efficiency.
IP-20G enables operators to maximize QoE with an improved customer
experience by providing TCP-friendly backhaul. The system provides support for
emerging services, standards, and networking protocols (future proof). It also
enables operators to reduce TCO by supporting rich, revenue-generating services,
simplified management for reduced OPEX, and improved service availability and
time-to-revenue.
Page 20 of 322

IP-20G provides an innovative packet backhaul services aggregation solution that

is designed to meet the challenges faced by operators building next-generation
wireless backhaul networks for delivery of packet-based services. Meeting these
challenges requires the ability to maintain services with strict SLA by enforcing a
services policy that guarantees and monitors service performance. It also requires
the ability to manage the explosion of data by ensuring capacity allocation and
traffic management under wireless link congestion scenarios.
IP-20G maintains high capacity at the aggregation network, with modulation of up
to 2048 QAM. The IP-20G aggregation solution is based upon rich backhaul
services and simplified management that are supported using personalized QoS
(H-QoS), superb service OAM (FM, PMs, service activation), and carrier-grade
service resiliency (G.8032, MSTP).
2.1.1 IP-20G Radio Options

An IP-20G system consists of an IP-20G indoor unit (IDU) and one or two of the
following radio frequency units (RFUs).
2.1.1.1 RFU-C
RFU-C1 is a fully software configurable, state-of-the-art RFU that supports a broad
range of interfaces and capacities from 10 Mbps up to 500 Mbps. RFU-C operates
in the frequency range of 6-42 GHz.
RFU-C supports low to high capacities for traditional voice and Ethernet services,
as well as PDH/SDH or hybrid Ethernet and TDM interfaces. Traffic capacity
throughput and spectral efficiency are optimized with the desired channel
bandwidth. For maximum user choice flexibility, channel bandwidths can be
selected. RFU-C provides a range of modulations from QPSK to 2048 QAM.
When RFU-C operates in co-channel dual polarization (CCDP) mode using XPIC,
two carrier signals can be transmitted over a single channel, using vertical and
horizontal polarization. This enables double capacity in the same spectrum
bandwidth.
For additional information:

• RFU-C
1
All references to RFU-C in this document refer to RFU-Ce.
Page 21 of 322

2.1.1.2 1500HP/RFU-HP
1500HP and RFU-HP are high transmit power RFUs designed for long haul
applications with multiple carrier traffic. Together with their unique branching
design, 1500HP and RFU-HP can chain up to five carriers per single antenna port
and 10 carriers for dual port, making them ideal for Trunk or Multi Carrier
applications. The 1500HP and RFU-HP can be installed in either indoor or outdoor
configurations.
1500HP/RFU-HP provide a range of modulations from QPSK to 2048 QAM.

• 1500HP/RFU-HP
2.1.2 FibeAir IP-20G Interoperability with other Ceragon Products

IP-20G is interoperable over the radio link with IP-20N and IP-20GX.
In addition, 1+0 links are supported between IP-20G and IP-20S units on 28 MHz
channels using non-XPIC scripts without ATPC and without Multi-Carrier ABC.
For specific software version requirements, refer to the Release Notes for the
version you are using.
2.1.3 IP-20G Highlights

The following are some of the highlights of FibeAir IP-20G.
• Optimized tail/edge solution supporting seamless integration of radio (L1) and
end-to-end Carrier Ethernet transport/services (L2) functionality.
• Rich packet processing feature set for support of engineered end-to-end
Carrier Ethernet services with strict SLA.
• Integrated support for multi-operator and converged backhaul business
models, such as wholesale services and RAN-sharing.
• Highest capacity, scalability and spectral efficiency.
• High precision, flexible packet synchronization solution combining SyncE and
IEEE-1588v2.
• Best-in-class integrated TDM migration solution.
• Specifically built to support resilient and adaptive multi-carrier radio links,
scaling to GbE capacity.
• Future-proof with maximal investment protection.
• Supports RFU-C, and RFU-HP for modulations up to 2048 QAM.
2.1.4 IP-20G Protection Options

IP-20G provides 1+1 HSB radio protection. In dual-carrier systems, the user can
configure the two radio interfaces as a protection group, which protects against
hardware failure in the RFU. The CPU monitors the radio interfaces and initiates
switchover upon indication of a hardware or signal failure.
Page 22 of 322

IP-20G also provides unit redundancy. Unit redundancy utilizes two IP-20G units,
with a single antenna, to provide hardware protection for the IP-20G IDU and
RFU, including protection for Ethernet, radio, and TDM interfaces. Unit
redundancy can be used with 2 x 1+0 and 2 x 2+0 radio configurations.
A power redundancy option is also offered by means of a dual-feed power input
hardware assembly option.
Page 23 of 322

2.2 Reference Configurations

This section provides diagrams that illustrate some of the network applications in
which IP-20G units can be used, taking advantage of its dual-modem capability,
optional 16xE1 module, and hybrid Ethernet/TDM cascading services
functionality.
2.2.1 Dual Modem Activation

The following figure shows how a single-carrier IP-20G unit with dual-modem
hardware can be converted via software upgrade to a dual-modem unit. Dual-
modem IP-20G units can be utilized in 1+0 East-West configurations (upper right
in the figure), or in 2+0 XPIC or 1+1 HSB configurations (lower right in the figure).
1+0
1+0
1+0
16xE1s 6xGE/FE
(Optional)
Second Modem
Activation
2+0 XPIC/1+1 HSB
16xE1s 6xGE/FE
(Optional)
16xE1s 6xGE/FE
(Optional)
Figure 1: Reference Configuration – Dual Modem Activation
2.2.2 IDU Dual-Modem Cascading Link

The following figure shows a dual-modem IP-20G in an East-West configuration,
with a cascading link to a pair of IP-20G units, both in East-West configurations
utilizing dual modems. A cascading connection between these two units enables
hybrid Ethernet/TDM traffic to pass among all three units. This connection utilizes
Page 24 of 322

the GbE1 dual mode electrical/cascading port, leaving ten Ethernet ports available
for other traffic.
1+0
1+0
Second Modem
Activation
IP-20G IDU 1+0

16xE1s 6xGE/FE 1+0
Cascading
(Optional)
1+0 1+0
Second Modem
Activation
32xE1s 10xGE/FE
(Optional)
Figure 2: Reference Configuration – IDU Cascading with Dual Modems
Page 25 of 322

2.2.3 Chained Network

The following figure shows a chain consisting of four IP-20G nodes. From the left:
• The first node consists of a single-modem IP-20G unit linked via a 1+0 radio
link to the next node.
• The second node consists of a dual-modem IP-20G unit linked via separate 1+0
radio links to the first and third node.
• The third node consists of two IP-20G units connected by a cascading link via
the GbE1 dual mode electrical/cascading port. The upper unit is a dual-
modem unit connected to the fourth node via a 1+1 or a 2+0 XPIC link. The
lower unit is a single-modem unit connected to the second node via a 1+0
radio link.
• The fourth node consists of a dual-modem IP-20G unit connected to the third
node via a 1+1 or a 2+0 XPIC link.
1+0
1+0
16xE1s 6xGE/FE 1+1/2+0 XPIC
(Optional)
16xE1s 6xGE/FE
(Optional)
32xE1s 10xGE/FE
(Optional)
16xE1s 6xGE/FE
(Optional)
Figure 3: Reference Configuration – Chained Network
Page 26 of 322

2.2.4 Ring with Spur

The following figure shows a ring consisting of three IP-20G nodes connected via
1+0 radio links, with a spur to a fourth IP-20G node. All of the IP-20G units in the
ring utilize dual-modem configurations, except for the node at the bottom in the
figure. The bottom node consists of two IP-20G units. The upper unit is a dual-
modem unit connected to the other units in the ring. The lower unit is a single-
modem unit connected to the unit in the spur node, which is also a single-modem
unit. The upper and lower units are connected by a cascading link via the GbE1
dual mode electrical/cascading port. The network elements in the ring use the
MSTP and G.8032 network resiliency protocols for ring protection.
1+0
Ring
Protection
16xE1s 6xGE/FE
16xE1s 6xGE/FE (Optional)
(Optional)
1+0
1+0
16xE1s 6xGE/FE
(Optional)
1+0
32xE1s 10xGE/FE
(Optional)
Figure 4: Reference Configuration – Ring with Spur
2.2.5 Aggregation/POP Site

The following figure shows an aggregation/POP site consisting of:
• A ring that includes:
◦ A node with a dual-modem IP-20G unit.
◦ A node with two IP-20G units connected to each other by a cascading link
via the GbE1 dual mode electrical/cascading port.
◦ An IP-20N 2RU unit with four radio carriers.
Page 27 of 322

• The ring is connected via 1+0 links between the single IP-20G node, two of the
IP-20N radio carriers, and the upper IP-20G in the two-unit node.
• The two-IP-20G-unit node is connected to a spur via a 1+0 link between the
single-modem lower IP-20G unit in the ring node and a single-modem IP-20G
unit in the spur.
• The IP-20N unit is connected to two spurs via 1+0 links between two of the IP-
20N unit’s radio carriers and single-modem IP-20G units in the spurs.
• The network elements in the ring use the MSTP and G.8032 network resiliency
protocols for ring protection.
1+0
GE/FE
STM-1s
(Optional)
Ring E1s (Optional)

Protection 1+0
16xE1s 6xGE/FE
(Optional)
1+0
1+0
16xE1s 6xGE/FE
(Optional)
1+0
16xE1s 6xGE/FE
(Optional) 32xE1s 10xGE/FE
(Optional)
1+0
16xE1s 6xGE/FE
(Optional)
Figure 5: Reference Configuration – Aggregation/POP Site
Page 28 of 322

2.3 FibeAir IP-20 Assured Platform

Ceragon’s FibeAir® IP-20 Assured platform enhances network reliability and
security, ensuring that mission-critical networks maintain availability, and
protecting the confidentiality and integrity of their users’ data.
The FibeAir IP-20 Assured platform is compliant with FIPS 140-2, including:
• Compliance with FIPS 140-2 specifications for cryptography module.
• FIPS 140-2 Level 2 physical security.
• AES-256 encryption (FIPS 197) over radio links.
The FibeAir IP-20 Assured platform also provides:
• Secured communication and protocols for management interface.
• Centralized user authentication management via RADIUS or TACACS+.
• Advanced identity management and password policy enforcement.
• Security events log.
• Secure product architecture and development.
The following products are included in the FibeAir IP-20 Assured platform:
• FibeAir IP-20G Assured
• FibeAir IP-20GX Assured
• FibeAir IP-20A Assured
• FibeAir IP-20N Assured
• FibeAir IP-20LH Assured
• FibeAir IP-20C Assured
• FibeAir IP-20C-HP Assured
• FibeAir IP-20S Assured
Note: CeraOS 11.1 cannot be used in FibeAir IP-20 Assured platforms.
For FibeAir IP-20 Assured, use CeraOS 10.9.6 or CeraOS 8.3.
Page 29 of 322

2.4 New Features in CeraOS 11.1

The following table lists the features that have been added in CeraOS version
11.1, and indicates where further information can be found on the new features
in this manual and where configuration instructions can be found in the User
Guide.
Table 2: New Features in CeraOS 11.1

Feature Further Information Configuration Instructions in the User’s Guide
ETH-BN Over Groups Ethernet Bandwidth Section 8.3, Configuring Ethernet Bandwidth
Notification (ETH-BN) on Notification (ETH-BN)
page 189
TACACS+ TACACS+ Support on Section 11.7, Configuring TACACS+,
page 243
Importing and Exporting Configuration Management Section 4.8, Backing Up and Restoring
Configuration Files via on page 233 Configurations
HTTP/HTTPS
Exporting Unit Info File via n/a Section 12.7, Uploading Unit Info
HTTP/HTTPS
Page 30 of 322

3. IDU Hardware Description

This chapter describes the FibeAir IP-20G indoor unit and its interfaces, including a
description of the available hardware assembly options.
• Hardware Architecture
• Front Panel Description
• Ethernet Traffic Interfaces
• Ethernet Management Interfaces
• E1 Interface (Optional)
• Radio Interfaces
• Power Interface
• Synchronization Interface
• Terminal Interface
• External Alarms
• Storage Memory Card
• Hardware Assembly Options
• FibeAir IP-20G Unit Redundancy
Page 31 of 322

3.1 Hardware Architecture

FibeAir IP-20G is a compact unit that fits in a single rack unit, with a passive
cooling system that eliminates the need for fans. An IP-20G system consists of an
IP-20G indoor unit (IDU) and one or two radio frequency units (RFUs). A coaxial
cable connects the IDU to each RFU, transmits traffic and management data
between the IDU and the RFU, and provides DC -48V power to the RFU.
An IP-20G IDU contains six Ethernet interfaces, one or two radio interfaces
depending on the hardware configuration, and optionally a 16 x E1 interface.
The IDU includes two FE management interfaces, a DB9 dry contact external
alarms interface, an RJ-45 synchronization interface, and an RJ-45 terminal
console interface for connection to a local craft terminal.
IP-20G receives an external supply of -48V, with a dual-feed option for power
redundancy.
The following hardware assembly options are available for the IP-20G IDU:
• One or two radio interfaces
• One or two power interfaces
• With or without 16 x E1 interfaces
Page 32 of 322

The following figure provides a block diagram of the IP-20G.
Sync
48V
Radio Interface 1
Power
48V Supply Framer Modem IF
RFU
Interface RFU
(Optional Second
Interface)
XPIC
1588 TC/BC
RFU
(Optional) Framer Modem IF
Interface RFU
Sync
Radio Interface 2
Sync
In/Out Sync Unit (Optional)
FE Management
Interfaces
CPU
Terminal
Ethernet
Ethernet Services
TDM Interfaces
GE Traffic
Interfaces
(Optional)
Network
Processor TDM
16 x E1
TDM Pseudowire Services Services Framer LIU
Interface
Processor
GE/Cascading Services
Interfaces
Engine
TDM Cross
Connect
Native TDM
Services
Multi-Carrier
ABC Engine
Figure 6: IP-20G Block Diagram
Page 33 of 322

3.2 Front Panel Description

This section describes the IP-20G’s front panel. The following sections provide
detailed descriptions of the IP-20G interfaces.
Figure 7: IP-20G Front Panel and Interfaces
Table 3: IP-20G Interfaces

Interface For Further Information
16 x E1s (optional) E1 Interface (Optional)

External Alarms (DB9) External Alarms
Sync Interface In/Out (RJ-45) Synchronization Interface
2 x FE Management Interfaces Ethernet Management Interfaces
(RJ-45)
Terminal Interface (RJ-45) Terminal Interface
2 x GbE Dual Mode GbE Electrical Ethernet Traffic Interfaces
or Cascading Interfaces (RJ-45)
2 x GbE Electrical Interfaces (RJ- Ethernet Traffic Interfaces
45)
2 x GbE Optical Interfaces (SFP) Ethernet Traffic Interfaces
Radio Interfaces (TNC) Radio Interfaces
Power Interface -48V Power Interface
Page 34 of 322

3.3 Ethernet Traffic Interfaces

Related Topics:
• Physical Interfaces
• Ethernet Interface Specifications
The front panel of the FibeAir IP-20G contains four electrical and two optical GbE
Ethernet traffic interfaces:
• 2 x GbE dual mode electrical or cascading interfaces (RJ-45) – GbE1/CS1,
GbE2/CS2
• 2 x GbE electrical interfaces (RJ-45) –GbE3, GbE4
• 2 x GbE optical interfaces (SFP) – SFP5, SFP6
GbE1 and GbE2 can be configured as normal GbE traffic interfaces or as cascading
interfaces. When operating in cascading mode, these interfaces can handle hybrid
Ethernet and Native TDM traffic, enabling operators to create links among
multiple IP-20G units in a node for multi-carrier and multi-directional applications.
Page 35 of 322

3.4 Ethernet Management Interfaces

Related Topics:
• Physical Interfaces
• Ethernet Interface Specifications
FibeAir IP-20G contains two FE management interfaces, which connect to a single
RJ-45 physical connector on the front panel (MGMT).
RJ-45 Connector
Management Switch
(female)
TX+ 1
TX- 2
Port 1
RX+ 3
RX- 4
TX+ 5
TX- 6
Port 2
RX+ 7
RX- 8
Figure 8: Management Interface Pin Connections

If the user only needs to use a single management interface, a standard Cat5 RJ-
45 cable (straight or cross) can be connected to the MGMT interface.
To access both management interfaces, a special 2 x FE splitter cable can be
ordered from Ceragon.
2 x FE Splitter Cable Marketing Model

Marketing Model Marketing Description Part Number
SPL-ETH-CBL Ethernet split cable rohs WA-0245-0
3.5 E1 Interface (Optional)

Related Topics:
• E1 Interface Specifications
Optionally, FibeAir IP-20G can be ordered with an MDR69 connector in which 16
E1 interfaces are available (ports 1 through 16).
Page 36 of 322

3.6 Radio Interfaces

FibeAir IP-20G includes one or two radio interfaces, depending on the hardware
assembly option that was selected. Each radio interface uses a TNC connector
type. Each radio interface is connected to an RFU via coaxial cable. This
connection is used for traffic between the RFU and the IDU. It is also used to
provide -48V DC power from the IDU to the RFU, as well as for management and
configuration of the RFU.
The radio interfaces are labeled Radio 1 and, if there is a second radio interface,
Radio 2.
3.7 Power Interface

FibeAir IP-20G receives an external supply of -48V current via one or two power
interfaces (the second power interface is optional for power redundancy). The IP-
20G monitors the power supply for undervoltage and overvoltage and includes
reverse polarity protection, so that if the positive (+) and negative (-) inputs are
mixed up, the system remains shut down.
The allowed power input range for the IP-20G is -40V to -60V. An undervoltage
alarm is triggered if the power goes below a defined threshold, and an
overvoltage alarm is triggered if the power goes above a defined threshold. The
default thresholds are:
• Undervoltage Raise Threshold: 40V
• Undervoltage Clear Threshold: 42V
• Overvoltage Raise Threshold: 60V
• Overvoltage Clear Threshold: 58V
These thresholds are configurable.
For IP-20G units with two power inputs, overvoltage and undervoltage alarms are
raised specifically for the specific power input. A power input that is not in use can
be masked in order to prevent unnecessary alarms.
In addition, IP-20G provides PMs that indicate, per 15-minute and 24-hour
periods:
• The number of seconds the unit was in an undervoltage state during the
measured period.
• The number of seconds the unit was in an overvoltage state during the
measured period.
• The lowest voltage during the measured period.
• The highest voltage during the measured period.
For devices with two power inputs, the PMs are displayed for both inputs.
3.8 Synchronization Interface

FibeAir IP-20G includes an RJ-45 synchronization interface for T3 clock input and
T4 clock output. The interface is labeled SYNC.
Page 37 of 322

3.9 Terminal Interface

FibeAir IP-20G includes an RJ-45 terminal interface (RS-232). A local craft terminal
can be connected to the terminal interface for local CLI management of the unit.
3.10 External Alarms

IP-20G includes a DB9 dry contact external alarms interface. The external alarms
interface supports five input alarms and a single output alarm.
The input alarms are configurable according to:
1 Intermediate
2 Critical
3 Major
4 Minor
5 Warning
The output alarm is configured according to predefined categories.
Page 38 of 322

3.11 Storage Memory Card

Each FibeAir IP-20G unit includes a Storage Memory card (SM card). The SM card
holds the configuration and software for the IDU. The SM card is embedded in the
SM card cover. In the event of IDU replacement, re-using the existing SM card
cover is necessary to ensure that the unit’s software and configuration is
maintained.
An SM card is pre-installed inside each IP-20G unit. It can also be ordered as a
separate item (e.g., as a spare unit).
Figure 9: SM Card and Cover
Page 39 of 322

3.12 Hardware Assembly Options

Table 4: Hardware Assemblies
Part Number Hardware Capabilities
IP-20G-M2-E6-T16-C-2DC+SM • Hardware supports two radio carriers

• 6 Gigabit Ethernet ports: 2 Optical and 4 Electrical
• 16 TDM interfaces
• Synchronization interfaces T4 output
• IEEE-1588 BC support
• Dual DC power input feed
• Two management ports 100Base-TX, which connect to a
single RJ-45 physical connector on the front panel
(MGMT)
IP-20G-M2-E6-T16-2DC+SM • Hardware supports two radio carriers
(MGMT)
IP-20G-M1-E6-T16-2DC+SM • Hardware supports a single radio carrier
• Synchronization interfaces T3 input and T4 output
(MGMT)
IP-20G-M1-E6-2DC+SM • Hardware supports single radio carrier
(MGMT)
Page 40 of 322

Part Number Hardware Capabilities

IP-20G-M2-E6-2DC+SM • Hardware supports dual radio carrier
(MGMT)
Page 41 of 322

3.13 FibeAir IP-20G Unit Redundancy

Note: The G.8032, MSTP, LLDP, and Service OAM (SOAM) protocols
cannot be used with unit redundancy.
Unit redundancy utilizes two IP-20G units, with a single antenna, to provide
hardware protection for the IP-20G IDU and RFU, including protection for
Ethernet, radio, and TDM interfaces. One IP-20G operates in active mode and the
other operates in standby mode. If a protection switchover occurs, the roles are
switched. The standby unit is managed by the active unit. The standby unit’s
transmitter is muted, but the standby unit’s receiver is kept on in order to
monitor the link. However, the received signal is terminated at the switch level.
Note: For FIPS configurations, the external protection link must be
encrypted using IPsec. This encrypts all IP packets that pass
between the management ports of the two IP-20 units. For
instructions, see Encrypting an External Protection Link.
3.13.1 Ethernet Interface Protection with IP-20G Unit Redundancy

There are three modes for Ethernet interface protection with IP-20G unit
redundancy:
• Line Protection Mode – Traffic is routed to the Ethernet interfaces via two
interfaces on an external switch. LACP protocol is used to determine which IP-
20G port is active and which port is standby, and traffic is only forwarded to
the active port. Line Protection mode can be used with optical and electrical
Ethernet interfaces.
Note: The external switch must support LACP. IP-20G supports LACP for
purposes of line protection only.
• Optical Splitter Mode – An optical splitter cable is used to connect both the
active and the standby Ethernet ports. Optical Splitter mode can be used with
optical Ethernet interfaces only.
• Electrical Splitter Mode – A Y-cable is used to connect to both the active and
the standby Ethernet ports. With Electrical Splitter mode, interface protection
is only supported for speeds up to 100 Mbps (Fast Ethernet). Electrical Splitter
Mode can be used with electrical Ethernet interfaces only.
For Splitter Mode, the following Y-cable must be connected to the relevant
interfaces on the active and standby units:
Table 5: Y-Cable for Electrical Splitter Mode FE Traffic Interface Protection

Part Number Marketing Model Description
WA-0244-0 15P-PROT-CBL CABLE,RJ45F TO 2XRJ45, 1.34M,CAT-5E,
Page 42 of 322

3.13.2 Supported Radio Configurations with Unit Redundancy

IP-20G unit redundancy can be used with the following radio configurations:
• 2 x 1+0 – IP-20G unit with a 1+0 configuration protecting another IP-20G
unit with a 1+0 configuration.
• 2 x 2+0 – IP-20G unit with a 2+0 configuration protecting another IP-20G
unit with a 2+0 configuration.
A 2 x 1+0 IP-20G configuration is interoperable with FibeAir IP-20N using a 1+1
HSB configuration. However, a 2 x 2+0 IP-20G configuration is not interoperable
with FibeAir IP-20N using a 2+2 HSB configuration.
Traffic and
LACP PDUs GbE Port f1
(LACP Modem 1
Mode)
GbE Port
(LACP
Mode)
RFU
Coupler
External Active IP-20G Unit RFU
Switch
LACP PDUs GbE Port

only (LACP Modem 1
Mode)
GbE Port
(LACP
Mode)
f1
Standby IP-20G Unit
Figure 10: Unit Redundancy – 2 x 1+0 – Ethernet Line Protection Mode
Page 43 of 322

f1
Gbe
Port
Modem 1
RFU
Optical Splitter
or Y-Cable Coupler
Active IP-20G Unit RFU
GbE Port
Gbe
(LACP
Port Modem 1
Mode)
f1
Standby IP-20G Unit
Figure 11: Unit Redundancy – 2 x 1+0 – Splitter Mode
Traffic and GbE

GbE Port
f1
LACP PDUs Port
(LACP Modem 1
(LACP
Mode)
GbE Port Mode)
(LACP
Mode) f2
Modem 2
RFU RFU
External Active IP-20G Unit OMT
Switch
RFU RFU
LACP PDUs
only GbE
GbE Port
(LACP
GbE Port
Port f1
Mode)
(LACP
(LACP
Mode)
Modem 1
Mode)
f2
Modem 2
Standby IP-20G Unit
Figure 12: Unit Redundancy – 2 x 2+0 – Ethernet Line Protection Mode
Page 44 of 322

f1
Gbe Modem 1
Port
f2
Modem 2
Optical Splitter RFU RFU

or Y-Cable
Active IP-20G Unit OMT
RFU RFU
GbE Port
Gbe f1
(LACP
Port Modem 1
Mode)
f2
Modem 2
Standby IP-20G Unit
Figure 13: Unit Redundancy – 2 x 2+0 – Splitter Mode
3.13.3 E1 Interface Protection with IP-20G Unit Redundancy

E1 traffic is supported with IP-20G unit redundancy. A Y-cable is used to connect
the active and standby E1 ports. The following table shows the Part Number and
Marketing Model of the Y-cable required for E1 protection.
Table 6: Y-Cable for E1 Protection

Marketing Model Description
IP-10 16E1 protection Y-cable, MDR68 CABLE,2xSCSI68 LEFT ANGL SCSI68,0.6M,120

OHM,ADAP
E1 Active IP-20G Unit

Port
E1
Port Y-Cable
Third Party
Equipment E1
Port
Standby IP-20G Unit
Figure 14: E1 Interface Protection with IP-20G Unit Redundancy
Page 45 of 322

3.13.4 T3 Synchronization with Unit Redundancy

T3 synchronization input is supported with IP-20G unit redundancy. A Y cable is
used to connect to the active and standby Sync interfaces.
3.13.5 Management for Unit Redundancy

IP-20G units in a redundancy configuration must have their CPUs interconnected
in order to synchronize their protection status. The same IP address is used for
both IP-20G units, to ensure that management is not lost in the event of
switchover. A special cable is required to enable this connectivity.
Table 7: Splitter Cable for Protection and Management

Part Number Marketing Model Description
WA-0720-0 CBL-IP20-EXT-PROT+MGMT CABLE,RJ45F TO 2XRJ45,1.34M,CAT-5E,WITH MALE TO

MALE CONNECTION
The protection and management splitter cable must be connected to the

management interfaces of the two IP-20G units using the RJ-45 plug-ends. The
third end of the protection splitter cable (RJ-45 socket) is connected to an external
management station.
IP-20G Management
Port (MGMT)
External Management Connection
IP-20G Management
Port (MGMT)
Figure 15: IP-20G with Unit Redundancy – Protection and Management Splitter
Connection
The active and standby units must have the same configuration. The configuration
of the active unit can be manually copied to the standby unit. Upon copying, both
units are automatically reset. Therefore, it is important to ensure that the units
are fully and properly configured when the system is initially brought into service.
Page 46 of 322

3.13.6 Switchover
In the event of switchover, the standby unit becomes the active unit and the
active unit becomes the standby unit. Switchover takes less than 50 msec.
The following events trigger switchover according to their priority, with the
highest priority triggers listed first:
1 Loss of active unit
2 Force switch
3 Lockout
4 Radio Loss of Frame (LOF) on active unit
5 Change request from the remote unit. This takes place in the event of radio
LOF on both units; a change request is sent to the active unit on the other side
of the link.
6 Loss of Carrier (LOC) in any of the Ethernet interfaces or Loss of Signal (LOS) in
any of the TDM interfaces
7 Manual switch
LOC takes place if the Admin status of the interface is Enabled and the
Operational status is Down. If the interface is closed as a result of ASP, the
interface is not considered to be in LOC state, and switchover is not triggered.
Following switchover triggered by LOC, there is an automatic timeout of one
minute before any further switchover can take place due to LOC.
Page 47 of 322

4. RFU Hardware Description and Branching Options

The radio carrier functionality for an IP-20G node is provided by Radio Frequency
Units (RFUs). An IP-20G can support one or two RFUs.
IP-20G works with the following RFUs:
Standard Power
• RFU-C
High Power
• 1500HP
• RFU-HP

• RFU Overview
• RFU Selection Guide
• RFU-C
• 1500HP/RFU-HP
Page 48 of 322

4.1 RFU Overview

FibeAir Radio Frequency Units (RFUs) were designed with sturdiness, power,
simplicity, and compatibility in mind. These advanced systems provide high-power
transmission for short and long distances and can be assembled and installed
quickly and easily. Any of the RFUs described in this chapter can be used in an IP-
20G system.
RFUs deliver high capacity over 1.75-56 MHz channels with configurable
modulation schemes and a range of modulations from QPSK to 2048 QAM.
The RFUs support low to high capacities for traditional voice, mission critical, and
emerging Ethernet services, with any mix of interfaces, pure Ethernet, pure TDM,
or hybrid Ethernet and TDM interfaces (Native2).
High spectral efficiency can be ensured with XPIC, using the same bandwidth for
double the capacity, via a single carrier, with vertical and horizontal polarizations.
The following RFUs can be installed in a split-mount configuration:
• RFU-C (6–42 GHz)
• 1500HP (6–11 GHz)
• RFU-HP (6-8 GHz)
The following RFUs can be installed in an all-indoor configuration:
• 1500HP (6–11 GHz)
• RFU-HP (6-8 GHz)
The IDU and RFU are connected by a coaxial cable RG-223 (100 m/300 ft), Belden
9914/RG-8 (300 m/1000 ft) or equivalent, with an N-type connector (male) on the
RFU and a TNC connector on the IDU.
The antenna connection can be:
• Direct or remote mount using the same antenna type.
• Remote mount: standard flexible waveguide (frequency dependent)2
2
Remote mount configuration is not supported for 42 GHz.
Page 49 of 322

4.2 RFU Selection Guide

The following table can be used to help you select the RFU that is appropriate to
your location.
Table 8: RFU Selection Guide

Character 1500HP/RFU-HP RFU-C
(6 – 11 GHz) (6 – 42 GHz)
Installation Type Split Mount √ √
All-Indoor √ −
Configuration 1+0/2+0/1+1/2+2 √ √
N+1 √ −
N+0 ( N>2) √ −
SD support √ (IFC, BBS) √ (BBS)
Power Saving Mode Adjustable Power √ −

Consumption
Modulation QPSK to 256 QAM √ √
512 to 2048 QAM √ √
Page 50 of 322

4.3 RFU-C
RFU-C is a fully software configurable, state-of-the-art RFU that supports a broad
range of interfaces and capacities from 10 Mbps up to 500 Mbps. RFU-C operates
in the frequency range of 6-42 GHz. RFU-C supports low to high capacities for
traditional voice and Ethernet services, as well as PDH/SDH/SONET or hybrid
Ethernet and TDM interfaces.
With RFU-C, traffic capacity throughput and spectral efficiency are optimized with
the desired channel bandwidth. For maximum user choice flexibility, channel
bandwidths from 1.75-56 MHz can be selected together with a range of
modulations. RFU-C provides a range of modulations from QPSK to 2048 QAM.3
When RFU-C operates in co-channel dual polarization (CCDP) mode using XPIC,
two carrier signals can be transmitted over a single channel, using vertical and
horizontal polarization. This enables double capacity in the same spectrum
bandwidth.
4.3.1 Main Features of RFU-C

• Frequency range – Operates in the frequency range 6 – 42 GHz
• More power in a smaller package - Up to 26 dBm for extended distance,
enhanced availability, use of smaller antennas
• Configurable Channel Bandwidth – 1.75 MHz – 56 MHz4
• Compact, lightweight form factor - Reduces installation and warehousing
costs
• Supported configurations:5
◦ 1+0 – direct and remote mount
◦ 2+2 – remote mount
• Efficient and easy installation - Direct mount installation with different
antenna types
3
For details about supported modulation capabilities beyond 256 QAM using a standard RFU-
C, contact your Ceragon representative.
4
1.75 MHz channels are supported for 6 and 13 GHz.
5
Remote mount configuration is not supported for 42 GHz.
Page 51 of 322

4.3.2 RFU-C Functional Block Diagram

The RFU is responsible for RF signal processing, and includes an RF transmitter
and an RF receiver with all their related functions.
RFU-C is designed to provide a high-capacity RF module, with a variety of low-loss
mediation devices to accommodate different RF configurations.
The following block diagram illustrates the functional modules of an RFU-C in a
1+0 configuration.
350 MHz VCO
IF TX TX
EMM
FSK Chain
Controller and
(N-Type Connector)
Peripherals
IDU Connection
Quadplexer
Connector
Connector
-48V
PSU Section
(BNC Connector)
RSL Indication
IF RX RX
LNA
Chain
140 MHz
VCO
PSC Board (Frequency Independent) TRX Board (Frequency Dependent) Diplexer
RFU-C Chassis (Frequency Independent)
Figure 16: RFU-C Functional Block Diagram – 1+0 Configuration

• Specifications
Page 52 of 322

4.4 1500HP/RFU-HP
1500HP and RFU-HP are high transmit power RFUs designed for long haul
applications with multiple carrier traffic. Together with their unique branching
design, 1500HP/RFU-HP can chain up to five carriers per single antenna port and
10 carriers for dual port, making them ideal for Trunk or Multi Carrier
applications. The 1500HP/RFU-HP can be installed in either indoor or split mount
configurations.
The field-proven 1500HP/RFU-HP was designed to enable high quality wireless
communication in the most cost-effective manner. With tens of thousands of
units deployed worldwide, the 1500HP/RFU-HP serves mobile operators enabling
them to reach over longer distances while enabling the use of smaller antennas.
1500HP and RFU-HP 1RX support Space Diversity via Baseband Switching in the
IDU (BBS). The 1500HP 2RX, supports Space Diversity through IF Combining (IFC).
Both types of Space Diversity are valid solutions to deal with the presence of
multipath.
1500HP/RFU-HP provides a range of modulations from QPSK to 2048 QAM.
4.4.1 Main Features of 1500HP/RFU-HP6

• Frequency range –
◦ 1500HP 2RX: 6-11GHz
◦ 1500HP 1RX: 11GHz
◦ RFU-HP: 6-8GHz
• Frequency source – Synthesizer
• Installation type – Split mount – remote mount, all indoor (No direct mount)
• Diversity – Optional innovative IF Combining Space Diversity for improved
system gain (for 1500HP 2RX), as well as BBS Space Diversity (all models)
• High transmit power – Up to 33dBm in all indoor and split mount installations
• Configurable Modulation – QPSK – 2048 QAM
• Configurable Channel Bandwidth –
◦ 1500HP 2RX (6-11 GHz): 10-30 MHz
◦ 1500HP 2 RX (6 and 11 GHz wide option): 40 MHz
◦ 1500HP 1RX (11 GHz): 10-30 MHz
◦ 1500HP 1RX (11 GHz wide option): 40 MHz
◦ RFU-HP 1RX (6-8GHz): 3.5-56 MHz
• System Configurations – Non-Protected (1+0), Protected (1+1), Space
Diversity, 2+0/2+2 XPIC
6
For guidance on the differences between 1500HP and RFU-HP, refer to RFU Selection Guide
on page 48.
Page 53 of 322

• XPIC and CCDP – Built-in XPIC (Cross Polarization Interference Canceller) and
Co-Channel Dual Polarization (CCDP) feature for double transmission capacity,
and more bandwidth efficiency
• Power Saving Mode option - Enables the microwave system to automatically
detect when link conditions allow it to use less power (for RFU-HP)
• Tx Range (Manual/ATPC) – The dynamic TX range with ATPC is the same as
the manual TX range, and depends on the RFU type, the frequency, and the
ACM profile. The maximum TX power with ATPC is no higher than the
maximum manually configured TX power.
• ATPC (Automatic Tx Power Control)
• RF Channel Selection – Via EMS/NMS
• NEBS – Level 3 NEBS compliance
Page 54 of 322

4.4.2 1500HP/RFU-HP Functional Block Diagram and Concept of Operation

The RFU handles RF signal processing. The RFU encompasses the RF transmitter
and receiver with all their related functions.
The 1500HP/RFU-HP product line was designed to answer the need for a high
power RF module together with IF combining functionality and the ability to
concatenate several carriers with minimal RF branching loss.
This section briefly describes the basic block diagrams for the various types of
RFUs included in the 1500HP/RFU-HP product line.
Antenna
TX Board
OCB main
VCO
TX
350MHz IF TX TX Pre-
PA
chain Amp
Controller and
FSK peripherals DC / CTRL
Quadplexer
C C TCXO
RF LPBK
o o
n n
-48V
PSU
n n
e e RX
c c RX
LNA Extention port
combiner chain RX Main
140MHz t t
o o
r r RX
RX
LNA
chain RX Diversity
10M
diplexer
XLO
XPIC SW
Antenna
VCO
Diversity
IF & controller Board
RX
Chassis
IDU XPIC source
(Ntype conn.) sharing \ RSL ind.
(TNC conn.)
Figure 17: 1500HP 2RX in 1+0 SD Configuration

Antenna
TX Board
OCB main
VCO
TX
350MHz IF TX TX FMM FLM
chain
Controller and
FSK peripherals DC / CTRL
Quadplexer
C C TXCO
RF LPBK
o o
n n
-48V
PSU
n n
e e RX
c c RX
LNA Extention port
chain RX Main
140MHz t t
o o
r r
10M
diplexer
XLO
XPIC SW
VCO
IF & controller Board
RX Board
Chassis
IDU XPIC source
(Ntype conn.) sharing \ RSL ind.
(TNC conn.)
Figure 18: 1500HP 1RX in 1+0 SD Configuration
Page 55 of 322

Antenna
OCB main
VCO
TX
350MHz IF
TX
TX Pre-
RFIC PA
chain Amp
(BMA conn.)
C C
o o
IDU
FSK Controller and

peripherals
n n DC / CTRL
Quadplexer
n n 40M
RF LPBK
e e
c c
sharing \ RSL
-48V
XPIC source
(BMA conn.)
PSU section t t
ind.
o o RX
RX
r r RX
RFIC chain LNA Extention port
140MHz
40M
diplexer
XLO
XPIC SW
VCO
PSC TRX
Chassis
XPIC source
sharing \ RSL ind.
(TNC conn.)
Figure 19: RFU-HP 1RX in 1+0 SD Configuration

Each of these RFU types must be connected to an OCB (Outdoor Circulator Block)
which serves as both a narrow diplexer and a mediation device to facilitate
antenna connection.

• 1500HP/RFU-HP OCBs
Page 56 of 322

4.4.3 1500HP/RFU-HP Comparison Table

The following table summarizes the differences between the 1500HP 2RX and 1RX
and the RFU-HP.
Table 9: 1500HP/RFU-HP Comparison Table

Feature 1500HP 2RX 1500HP 1RX RFU-HP Notes
Frequency Bands 6L,6H,7,8,11GHz 11 GHz 6L,6H,7,8GHz

Support
Channel Spacing Up to 40 MHz Up to 40 MHz Up to 56 MHz
Support
Split-Mount √ √ √ All are compatible
with OCBs from both
generations
All-Indoor √ √ √ All are compatible
with ICBs
Space Diversity BBS and IFC BBS BBS IFC - IF Combining
BBS - Base Band
Switching
Frequency Diversity √ √ √
1+0/2+0/1+1/2+2 √ √ √
N+1 √ √ √
N+0 (N>2) √ √ √
High Power √ √ √
Remote Mount √ √ √
Antenna
Power Saving Mode -- -- √ Power consumption
changes with TX
power
Note that the main differences between the 1500HP 1RX and RFU-HP 1RX are:
• The RFU-HP offers full support for 3.5M-56MHz channels.
• The RFU-HP supports the green-mode feature
Both systems are fully compatible with all OCB and ICB devices.
Page 57 of 322

4.4.4 1500HP/RFU-HP System Configurations
4.4.4.1 Split Mount and All indoor

The 1500HP/RFU-HP radios can be installed either in split mount or in all indoor
configurations.
The following configurations are applicable for Split-Mount or all indoor
installations:
• Unprotected N+0 - 1+0 to 8+0 – Data is transmitted through N channels,
without redundancy (protection)
• Hot Standby - 1+1 HSB, 2+2 HSB – Two RFUs use the same RF channel
connected via an asymmetrical coupler. One channel transmits (Active) and
the other acts as a backup (Standby). A 2+2 HSB configuration uses two RFUs
which are chained using two frequencies and connected via an asymmetrical
coupler to the other pair of RFUs.
• Protected 2+0 with Frequency Diversity – Data is transmitted through two
channels. In case signal degradation occurs in one of the two channels, traffic
is redistributed across the second channel.
If failure occurs in one of the two channels, traffic is distributed across the
remaining channel.
Notes:
• Space Diversity can be used in each of the configurations with RFU-HP 2RX.
• When the 1500HP/RFU-HP is mounted in a Split-Mount configuration, up to five
RFUs can be chained on one pole mount
When the 1500HP/RFU-HP is installed in an All Indoor configuration, there are
several installation options:
• Up to 10 carriers can be placed in an ETSI rack.7
• Compact assembly – up to two radio carriers in horizontal placement (without
a subrack).
Two types of branching options are available for all indoor configurations:
• Using ICBs – Vertical assembly, up to 10 carriers per rack (five carriers per
subrack)
• Using OCBs – Compact horizontal assembly, up to 2 carriers per subrack
4.4.5 Space Diversity with IF Combining

1500HP has two receivers, enabling it to perform Space Diversity via IF Combining.
The RFU receives and processes both signals, and combines them into a single,
optimized signal. The IFC mechanism gains up to 2.5 dB in system gain.
7
A 19” open rack can also be used, holding a single subrack with up to four or five radio
carriers, depending on the configuration.
Page 58 of 322

4.4.6 Split Mount Configuration and Branching Network

For multiple carriers, up to five carriers can be cascaded and circulated together
to the antenna port.
Branching networks are the units which perform this function and route the
signals from the RFUs to the antenna. The branching network can contain multiple
OCBs or ICBs. When using a Split-Mount or All-Indoor compact (horizontal)
configuration, the OCB branching network is used. When using an All-Indoor
vertical configuration, the ICB branching network is used.
The main differences in branching concept between the OCB and the ICB relate to
how the signals are circulated.
• OCB – The Tx and the Rx path circulate together to the main OCB port. When
chaining multiple OCBs, each Tx signal is chained to the OCB Rx signal and so
on (uses S-bend section). For more details, refer to 1500HP/RFU-HP OCBs on
page 60.
• ICB – All the Tx signals are chained together to one Tx port (at the ICC) and all
the Rx signals are chained together to one Rx port (at the ICC). The ICC
circulates all the Tx and the Rx signals to one antenna port.
Figure 20: All-Indoor Figure 21: Split-Mount Branching

Vertical Branching and All-Indoor Compact
Page 59 of 322

4.4.6.1 1500HP/RFU-HP OCBs

The OCB (Outdoor Circulator Block) has the following main purposes:
• Hosts the circulators and the attached filters.
• Routes the RF signal in the correct direction, through the filters and
circulators.
• Enables RFU connection to the Main and Diversity antennas.
1500HP and RFU-HP supports two types of OCBs:
• OCB (Older Type)
• OCB (Current Type)
Figure 22: Old OCB Figure 23: OCB
Note: This document describes the newer type OCB.

The OCB is optimized for configurations that do not use IFC Space Diversity. To
support IFC Space Diversity, a diversity block is added.
The OCB has only one type, and can be connected to an antenna via a flexible
waveguide.
The OCB connection is at the rear of the OCB. It includes proprietary accessories
(different than those used for the older OCB).
Each OCB has three waveguide ports: The In/Out port is located at the rear of the
OCB.
The OCB ports include:
• Tx port
• Rx Port
• Diversity port
Page 60 of 322

If the system is not configured for diversity, all the relevant ports on the OCB must
be terminated using waveguide shorts. Unused Rx ports are terminated with a
waveguide termination.
main
Antenna
OCB OCB
(back side) (back side)
Next Radio
diversity
Antenna
Next Radio
DCB
Front side
P2 P1
OCB-2 OCB-1
Circ. A
Circ. B
P2 P1
Div. Antenna Port Div. Ext. Port
Rear side
Figure 24: OCB and DCB Block Diagrams
Page 61 of 322

OCB components include the following:

RF Filters
RF Filters are used for specific frequency channels and Tx/Rx separation. The
filters are attached to the OCB, and each RFU contains one Rx and one Tx filter. In
an IFC Space Diversity configuration, each RFU contains two Rx filters (which
combine the IF signals) and one Tx filter. The filters can be replaced without
removing the OCB.
DCB (Diversity Circulator Block)
The DCB is an external block which is added for IFC Space Diversity configurations.
The DCB is connected to the diversity port and can chain two OCBs.
Asymmetrical Coupler Kit
The asymmetrical coupler kit is used for 1+1 Hot Standby (HSB) configurations.
Symmetrical Coupler Kit
The symmetrical coupler kit used for adjacent channel configurations for which
the adjacent channel OCBs are not supported.
Note: Asymmetrical and symmetrical couplers are not interchangeable.
Make sure to order the appropriate type of coupler for your
configuration.
U Bend
The U Bend connects the chained DCB (Diversity Circulator Block) in N+1/N+0
configurations.
S Bend
The S Bend connects the chained OCB (Outdoor Circulator Block) in N+1 /N+ 0
configurations.
Pole Mount Kit
The Pole Mount Kit can attach up to five OCBs and the RFUs to the pole. The kit
enables fast and easy pole mount installation.
4.4.6.2 OCB Component Summary
Table 10: OCB Component Summary

Component Marketing Model Marketing Description Picture
Name
DCB DCBf DCB Diversity Block f GHz kit
Asymmetrical OCB-CPLR-f OCB Coupler f GHz

Coupler
Page 62 of 322

Symmetrical OCB-CPLR_SYM-f OCB symmetrical Coupler fGHz

Coupler
U Bend DCB-UBend DCB Ubend connection f GHz
S Bend OCB-SBend OCB SBend connection f GHz
Pole Mount OCB-Pole Mount OCB-Pole Mount
Note: f= 6L, 6H, 7, 8, 11 GHz
4.4.6.3 Upgrade Procedure

The following components need to be added when upgrading from a 1+0 to an
N+1 Split-Mount configuration:
• • OCBs
• • RFUs
• • IDU/IDMs
• • Flexible waveguides
When adding RF channels or carriers, RFUs and OCBs with specific filters need to
be added as well.
The OCBs are chained together using couplers (for the same frequency) or
U bends/S bends (for different frequencies), in accordance with the specific
configuration.
Open ports on the OCBs are terminated with waveguide terminations.
Detailed upgrade procedure documents are available for specific configurations.
Please note that legacy OCBs can be upgraded and cascaded with the new OCB.
Page 63 of 322

4.4.7 1500HP/RFU-HP Models and Part Numbers

The following table lists and describes the available 1500HP/RFU-HP models. All
RFU models are suited to operate in indoor and outdoor environments.
Table 11: RFU Models – 1RX Units

RFU-HP-1R-6L RFU-HP 6LG 1Rx up to 56M SM / All Indoor

RFU-HP-1R-6H RFU-HP 6HG 1Rx up to 56M SM / All Indoor
RFU-HP-1R-7 RFU-HP 7G 1Rx up to 56M SM / All Indoor
RFU-HP-1R-8 RFU-HP 8G 1Rx up to 56M SM / All Indoor
15HPA-1R-RFU-11 1500HP 11G 1RX SM / All Indoor Up to 30 MHz
15HPA-1R-RFU-11w 1500HP 11G 1RX SM / All Indoor 40 MHz
Table 12: RFU Models – 2RX Units

15HPA-2R-RFU-6L 1500HP 6LG 2RX SM / All Indoor Up to 30 MHz

15HPA-2R-RFU-6Lw 1500HP 6LG 2RX SM / All Indoor 40 MHz
15HPA-2R-RFU-6H 1500HP 6HG 2RX SM / All Indoor Up to 30 MHz
15HPA-2R-RFU-6Hw 1500HP 6HG 2RX SM / All Indoor 40 MHz
15HPA-2R-RFU-7 1500HP 7G 2RX SM / All Indoor
15HPA-2R-RFU-8 1500HP 8G 2RX SM / All Indoor
15HPA-2R-RFU-11 1500HP 11G 2RX SM / All Indoor Up to 30 MHz
15HPA-2R-RFU-11w 1500HP 11G 2RX SM / All Indoor 40 MHz
Page 64 of 322

4.4.8 OCB Part Numbers

The following table presents the various RFU options and the configurations in
which they are used. This table is applicable for all OCB configurations (Split
Mount and Compact All Indoor).
Note: For adjacent channel configurations in which adjacent channel
OCBs are not supported, symmetrical couplers can be used to
connect the OCBs.
Table 13: OCB Part Numbers

Band CHBW IFC Adjacent Marketing Model
6, 7 and 8 28/30 No No 15OCBf-xxxy-nn-L/H

GHz MHz
No Yes 15OCBf-xxxy-nnA-L/H
Yes No 15OCBf-SD-xxxy-nn-L/H
Yes Yes 15OCBf-SD-xxxy-nnA-L/H
40 MHz No No 15OCBf-xxxy-40N-nn-L/H
No Yes 15OCBf-xxxy-40N-nnA-L/H
Yes No 15OCBf-SD-xxxy-40N-nn-L/H
Yes Yes 15OCBf-SD-xxxy-40N-nnA-L/H
56 MHz No No 15OCBf-xxxy-56N-nn-L/H
No No 15OCBf-xxxy-56N-n-m-L/H
11 GHz 28/30 No No 15OCBf-xxxy-nn-L/H
MHz
Yes No 15OCBf-SD-xxxy-nn-L/H
40 MHz No No 15OCB11w-xxxy-nn-L/H
Yes No 15OCB11w-SD-xxxy-nn-L/H
Page 65 of 322

4.4.8.1 OCB Part Number Format
Table 14: OCB Part Number Format

Place Holder in Possible Values Description and Remarks
Marketing Model
f 6L,6H,7,8,11
xxx 000-999 [MHz] TRS in MHz
Y A…Z Ceragon TRS block designation
ZZZ Examples: Designation of the channels the OCB is
1W3 – “Wide” filters covering channels covering
1-3
03 – Only channel 03, 28MHz channel
3-5 – 56MHz “Narrow” filters allowing
concatenation using OCBs covering
channels 3 and 4.
03A – For Channel 03, 28 and 40 MHz
adjacent channels
H/L H or L Designating TX High and TX low
Page 66 of 322

5. Activation Keys
This chapter describes IP-20G’s activation key model. IP-20G offers a pay as-you-
grow concept in which future capacity growth and additional functionality can be
enabled with activation keys. Each unit contains a single activation key.
Activation keys are divided into two categories:
• Per Carrier – The activation key is per carrier.
• Per Device – The activation key is per device, regardless of the number of
carriers supported by the device.
A 1+1 HSB configuration requires the same set of per-carrier activation keys for
both the active and the protected carriers.

• Working with Activation Keys
• Demo Mode
• Activation Key Reclaim
• Activation Key-Enabled Features
5.1 Working with Activation Keys

Ceragon provides a web-based system for managing activation keys. This system
enables authorized users to generate activation keys, which are generated per
IDU serial number.
In order to upgrade an activation key, the activation key must be entered into the
IP-20G. The system checks and implements the new activation key, enabling
access to new capacities and/or features.
In the event that the activation-key-enabled capacity and feature set is exceeded,
an Activation Key Violation alarm occurs and the Web EMS displays a yellow
background and an activation key violation warning. After a 48-hour grace period,
all other alarms are hidden until the capacity and features in use are brought
within the activation key’s capacity and feature set.
5.2 Demo Mode

The system can be used in demo mode, which enables all features for 60 days.
Demo mode expires 60 days from the time it was activated, at which time the
most recent valid activation key cipher goes into effect. The 60-day period is only
counted when the system is powered up. Ten days before demo mode expires, an
alarm is raised indicating to the user that demo mode is about to expire.
Note: Demo mode does not include AES radio encryption functionality
unless a valid AES activation key has been applied for at least one
carrier when demo mode is activated.
Page 67 of 322

5.3 Activation Key Reclaim

If a customer needs to deactivate an IP-20 device, whether to return it for repairs
or for any other reason, the customer can reclaim the device’s activation key and
obtain a credit that can be applied to activation keys for other devices.
Where the customer has purchased upgrade activation keys, credit is given for the
full feature or capacity, not for each individual upgrade. For example, if the
customer purchased five capacity activation keys for 300M and later purchased
three upgrade activation keys to 350M, credit is given as if the customer had
purchased three activation keys for 350M and two activation keys for 300M.
Note: Activation Key Reclaim is only available for IP-20 devices running
CeraOS 9.2 or later.
5.4 Activation Key-Enabled Features

The default (base) activation key provides each carrier with a capacity of 10 Mbps.
In addition, the default activation key provides:
• A single management service, with MSTP available for this service.
• A Smart Pipe (L1) service per each GbE port covered by the activation key.
• A single 1 x GbE port for traffic.
• Unlimited Native TDM services (but no TDM pseudowire services)
• Full QoS with basic queue buffer management (fixed queues with 1 Mbit
buffer size limit, tail-drop only).
• LAG
• No synchronization
Note: As described in more detail below, a CET Node activation key
allows all CET service/EVC types including Smart Pipe, Point-to-
Point, and Multipoint, and MSTP for all services, as well as an
additional GbE traffic port for a total of 2 x GbE traffic ports.
As your network expands and additional functionality is desired, activation keys
can be purchased for the features described in the following table.
Table 15: Activation Key Types

Marketing Model Type Description For Addition Information
Refer to Table 16: Capacity Per Carrier Enables you to increase your system’s radio Capacity Summary
Activation Key Levels on capacity in gradual steps by upgrading your
page 71 capacity activation key level. Without a
capacity activation key, each carrier has a
capacity of 10 Mbps. Activation-key-enabled
capacity is available from 50 Mbps to 500
Mbps. Each radio carrier can be activation-
key-enabled for a different capacity.
SL-CHBW-1.75M Per Carrier Enables you to use MRMC script 1075 (1.75 Radio Scripts
MHz). No other capacity activation key is Radio Capacity Specifications
required for carriers using this script.
Page 68 of 322


SL-2nd-Modem-Act. Per Device Enables the use of a second modem on the Hardware Architecture
IP-20G.
SL-NETCONF/YANG Per Device Enables use of NETCONF/YANG protocols, SDN Support
enabling customers to manage, configure,
and monitor network elements within the
paradigm of SDN network architecture using
Ceragon’s SDN Master controller.
SL-LLF Per Device Enables you to use Link Loss Forwarding Automatic State Propagation
(LLF) with Automatic State Propagation and Link Loss Forwarding
(ASP). Without the activation key, only one
LLF ID can be configured. This means that
only one ASP pair can be configured per
radio interface or radio group.
SL-ACM Per Carrier Enables the use of Adaptive Coding and Adaptive Coding Modulation
Modulation (ACM) scripts. (ACM)
SL-MC-ABC Per Carrier Enables Multi-Carrier ABC. Multi-Carrier ABC
SL-Header-DeDuplication Per Carrier Enables the use of Header De-Duplication, Header De-Duplication
which can be configured to operate at L2
through L4.
SL-XPIC Per Carrier Enables the use of Cross Polarization Cross Polarization
Interference Canceller (XPIC). Each carrier in Interference Canceller (XPIC)
the XPIC pair must be activation-key-
enabled.
SL-Encryption-AES256 Per Carrier Enables the use of AES-256 encryption for AES-256 Payload Encryption
full radio payload encryption. Note that:
• If no AES activation key is configured for
the unit and the user attempts to enable
AES on a radio carrier, in addition to an
Activation Key Violation alarm the
feature will remain inactive and no
encryption will be performed.
• After entering an AES activation key, the
user must reset the unit before AES can
be activated. Unit reset is only necessary
for the first AES activation key. If AES
activation keys are acquired later for
additional radio carriers, unit reset is not
necessary.
Page 69 of 322


SL-GE-Port Per Port Enables the use of an Ethernet traffic port in Ethernet Traffic Interfaces
GbE mode (10/100/1000baseT or
1000baseX). An activation key is required for
each additional Ethernet traffic port that is
used on the device, beyond the one GbE
traffic port that is enabled via the default
activation key. An activation key can be
installed multiple times with dynamic
allocation inside the unit to enable multiple
GbE ports.
Note: Two Ethernet ports are enabled in
FE mode (10/100baseT) by default without
requiring any activation key.
Refer to Table 17: CET Node Per Device Enables Carrier Ethernet Transport (CET) • Ethernet Service Mode
Activation Key Levels on and a number of Ethernet services (EVCs), • Quality of Service (QoS)
page 72 depending on the type of CET Node
activation key:
• Edge CET Node – Up to 8 EVCs.
• Aggregation Level 1 CET Node – Up to 64
EVCs.
A CET Node activation key also enables the
following:
• A GbE traffic port in addition to the port
provided by the default activation key,
for a total of 2 GbE traffic ports.
• Network resiliency (MSTP/RSTP) for all
services.
• Full QoS for all services including basic
queue buffer management (fixed
queues buffer size limit, tail-drop only)
and eight queues per port, no H-QoS.
SL-Network-Resiliency Per Device Enables the following protocols for Network Resiliency
improving network resiliency:
• G.8032
• Native TDM services 1:1 path protection
SL-H-QoS Per Device Enables H-QoS.8 This activation key is Quality of Service (QoS)
required to add service-bundles with
dedicated queues to interfaces. Without this
activation key, only the default eight queues
per port are supported.
8
H-QoS support is planned for future release.
Page 70 of 322


SL-Enh-Packet-Buffer Per Device Enables configurable (non-default) queue Quality of Service (QoS)
buffer size limit for Green and Yellow
frames. Also enables WRED. The default
queue buffer size limit is 1Mbits for Green
frames and 0.5 Mbits for Yellow frames.
SL-Sync-Unit Per Device Enables the G.8262 synchronization unit.
This activation key is required in order to
provide end-to-end synchronization
distribution on the physical layer. This
activation key is also required to use
Synchronous Ethernet (SyncE).
SL-IEEE-1588-TC Per Device Enables IEEE-1588 Transparent Clock IEEE-1588v2 PTP Optimized
support. Transport
SL-IEEE-1588-BC Per Device Enables IEEE-1588 Boundary Clock. IEEE-1588v2 PTP Optimized
Transport
SL-Frame-Cut-Through Per Device Enables Frame Cut-Through. Frame Cut-Through
SL-TDM-PW Per Device Enables TDM pseudowire services on units TDM Pseudowire Services
with TDM interfaces. Without this activation
key, only native TDM services are
supported.
SL-Secure-Management Per Device Enables secure management protocols (SSH, Secure Communication
HTTPS, SFTP, SNMPv3, TACACS+, and Channels
RADIUS).
SL-Eth-OAM-FM Per Device Enables Connectivity Fault Management Connectivity Fault
(FM) per Y.1731 (CET mode only). Management (FM)
SL-Eth-OAM-PM Per Device Enables performance monitoring pursuant
to Y.1731 (CET mode only).9
SL-LACP Per Device Enables Link Aggregation Control Protocol Link Aggregation Groups
(LACP). (LAG) and LACP
SL-NE-Anti-theft Per Device Enables Anti-Theft protection. Anti-Theft
Table 16: Capacity Activation Key Levels

SL-Capacity-50M SL - Capacity 50M, per carrier

9
PM support is planned for future release.
Page 71 of 322


SL-Upg-50M-100M SL - Upg 50M - 100M, per carrier
Table 17: CET Node Activation Key Levels

Marketing Model # of Bundled Management # of Pipe # of CET (L2) # of
GbE Ports for Service (L1) Ethernet Native
User Traffic Ethernet Services10 TDM
Services Services
Default (No Activation 1 Yes Unlimited - 256

Key)
SL-Edge-CET-Node 2 Yes Unlimited 8 256
SL-Agg-Lvl-1-CET-Node 2 Yes Unlimited 64 256
10
Including Point-to-Point, Multipoint, and TDM Pseudowire services. An SL-TDM-PW
activation key is also required to enable TDM Pseudowire services.
Page 72 of 322

If a CET activation key is not generated on the IP-20 device upon initial configuration,
the device uses by default a base smart pipe activation key (SL-0311-0). If the
operator later wants to upgrade from the base smart pipe activation key to a CET
activation key, the customer must use a CET upgrade activation key. The following
table lists the CET upgrade activation keys:
Table 18: Edge CET Note Upgrade Activation Keys

Marketing Model Upgrade From Upgrade To
SL-Upg Smart-Pipe/Edge-CET node NG Smart Pipe Activation Key (SL-0311-0) SL-Edge-CET-Node (SL-0312-0)
SL-Upg Edge/Agg-Lvl-1-CET node IP-20-SL-Edge-CET-Node (SL-0312-0) IP-20-SL-Agg-Lvl-1-CET-Node (SL-0313-0)
SL-Upg Agg-Lvl-1/Lvl-2-CET node IP-20-SL-Agg-Lvl-1-CET-Node (SL-0313-0) IP-20-SL-Agg-Lvl-2-CET-Node (SL-0314-0)
Page 73 of 322

6. Feature Description
This chapter describes the main IP-20G features. The feature descriptions are
divided into the categories listed below.

• Innovative Techniques to Boost Capacity and Reduce Latency
• Radio Features
• Ethernet Features
• Synchronization
• TDM Services
• Radio Payload Encryption and FIPS
Page 74 of 322

6.1 Innovative Techniques to Boost Capacity and Reduce Latency

IP-20G utilizes Ceragon’s innovative technology to provide a high-capacity low-
latency solution. IP-20G’s Header De-Duplication option is one of the innovative
techniques that enables IP-20G to boost capacity and provide operators with
efficient spectrum utilization, with no disruption of traffic and no addition of
latency.
IP-20G also utilizes established Ceragon technology to provide low latency
representing a 50% latency reduction for Ethernet services compared to the
industry benchmark for wireless backhaul.
Another of Ceragon’s innovative features is Frame Cut-Through, which provides
unique delay and delay-variation control for delay-sensitive services. Frame Cut-
Through enables high-priority frames to bypass lower priority frames even when
the lower-priority frames have already begun to be transmitted. Once the high-
priority frames are transmitted, transmission of the lower-priority frames is
resumed with no capacity loss and no re-transmission required.
This section includes:

• Capacity Summary
• Header De-Duplication
• Latency
• Frame Cut-Through
Page 75 of 322

6.1.1 Capacity Summary

Each carrier in an IP-20G provides the following capacity:
• Supported Channels – 1.7511/3.5/7/14/28/40/56 MHz channels.
• All licensed bands – L6, U6, 7, 8, 10, 11, 13, 15, 18, 23, 26, 28, 32, 38, 42 GHz
• High scalability – From 10 Mbps to 500 Mbps, using the same hardware,
including the same RFU, and up to 1 Gbps with Header De-Duplication.
• Modulations – QPSK to 2048 QAM

• Radio Capacity Specifications
11
1.75 MHz channels are supported for 6 and 13 GHz.
Page 76 of 322

6.1.2 Header De-Duplication

IP-20G offers the option of Header De-Duplication, enabling operators to
significantly improve Ethernet throughput over the radio link without affecting
user traffic. Header De-Duplication can be configured to operate on various layers
of the protocol stack, saving bandwidth by reducing unnecessary header
overhead. Header De-duplication is also sometimes known as header
compression.
Note: Without Header De-Duplication, IP-20G still removes the IFG and
Preamble fields. This mechanism operates automatically, even if
Header De-Duplication is not selected by the user.
Figure 25: Header De-Duplication

Header De-Duplication identifies traffic flows and replaces the header fields with a
"flow ID". This is done using a sophisticated algorithm that learns unique flows by
looking for repeating frame headers in the traffic stream over the radio link and
compressing them. The principle underlying this feature is that frame headers in
today’s networks use a long protocol stack that contains a significant amount of
redundant information.
Header De-Duplication can be customized for optimal benefit according to
network usage. The user can determine the layer or layers on which Header De-
Duplication operates, with the following options available:
• Layer2 – Header De-Duplication operates on the Ethernet level.
• MPLS – Header De-Duplication operates on the Ethernet and MPLS levels.
• Layer3 – Header De-Duplication operates on the Ethernet and IP levels.
• Layer4 – Header De-Duplication operates on all supported layers up to Layer
4.
• Tunnel – Header De-Duplication operates on Layer 2, Layer 3, and on the
Tunnel layer for packets carrying GTP or GRE frames.
• Tunnel-Layer3 – Header De-Duplication operates on Layer 2, Layer 3, and on
the Tunnel and T-3 layers for packets carrying GTP or GRE frames.
• Tunnel-Layer4 – Header De-Duplication operates on Layer 2, Layer 3, and on
the Tunnel, T-3, and T-4 layers for packets carrying GTP or GRE frames.
Page 77 of 322

Operators must balance the depth of De-Duplication against the number of flows
in order to ensure maximum efficiency. Up to 256 concurrent flows are
supported.
The following graphic illustrates how Header De-Duplication can save up to 148
bytes per frame.
IP-20G
Layer 2 | Untagged/C/S Tag/Double Tag

Up to 22 bytes compressed
Layer 2.5 | MPLS: up to 7 Tunnels (Untagged/C-Tag)

Up to 28 bytes compressed
Layer 3 | IPv4/IPv6
18/40 bytes compressed
Layer 4 | TCP/UDP
Tunneling Layer | GTP (LTE) / GRE

6 bytes compressed
End User Inner Layer 3 | IPv4/IPv6

End User Inner Layer 4 | TCP/UDP

End User
Figure 26: Header De-Duplication Potential Throughput Savings per Layer

Depending on the packet size and network topology, Header De-Duplication can
increase capacity by up to:
• 50% (256 byte packets)
Page 78 of 322

6.1.2.1 Header De-Duplication Counters

In order to help operators optimize Header De-Duplication, IP-20G provides
counters when Header De-Duplication is enabled. These counters include real-
time information, such as the number of currently active flows and the number of
flows by specific flow type. This information can be used by operators to monitor
network usage and capacity, and optimize the Header De-Duplication settings. By
monitoring the effectiveness of the Header De-Duplication settings, the operator
can adjust these settings to ensure that the network achieves the highest possible
effective throughput.
Page 79 of 322

6.1.3 Latency
IP-20G provides best-in-class latency (RFC-2544) for all channels, making it the
obvious choice for LTE (Long-Term Evolution) networks. Refer to Ethernet Latency
Specifications on page 303.
IP-20G’s ability to meet the stringent latency requirements for LTE systems
provides the key to expanded broadband wireless services:
• Longer radio chains
• Larger radio rings
• Shorter recovery times
• More capacity
• Easing of Broadband Wireless Access (BWA) limitations

• Ethernet Latency Specifications
Page 80 of 322

6.1.4 Frame Cut-Through
Related topics:
• Egress Scheduling
Frame Cut-Through is a unique and innovative feature that ensures low latency
for delay-sensitive services, such as CES, VoIP, and control protocols. With Frame
Cut-Through, high-priority frames are pushed ahead of lower priority frames, even
if transmission of the lower priority frames has already begun. Once the high
priority frame has been transmitted, transmission of the lower priority frame is
resumed with no capacity loss and no re-transmission required. This provides
operators with:
• Immunity to head-of-line blocking effects – key for transporting high-priority,
delay-sensitive traffic.
• Reduced delay-variation and maximum-delay over the link:
◦ Reduced end-to-end delay for TDM services.
◦ Improved QoE for VoIP and other streaming applications.
◦ Expedited delivery of critical control frames.
Figure 27: Propagation Delay with and without Frame Cut-Through
Page 81 of 322

6.1.4.1 Frame Cut-Through Basic Operation

Using Frame Cut-Through, frames assigned to high priority queues can pre-empt
frames already in transmission over the radio from other queues. Transmission of
the preempted frames is resumed after the cut-through with no capacity loss or
re-transmission required. This feature provides services that are sensitive to delay
and delay variation, such as VoIP, with true transparency to lower priority
services, by enabling the transmission of a high-priority, low-delay traffic stream.
Frame 4 Frame 4
Frame 1 Frame 2 Frame 3 Frame Cut-Through Frame 5
Start End
Figure 28: Frame Cut-Through

When enabled, Frame Cut-Through applies to all high priority frames, i.e., all
frames that are classified to a CoS queue with 4th (highest) priority.
Figure 29: Frame Cut-Through Operation
Page 82 of 322

6.2 Radio Features

This chapter describes the main IP-20G radio features.
Ceragon was the first to introduce hitless and errorless Adaptive Coding
Modulation (ACM) to provide dynamic adjustment of the radio’s modulation from
QPSK to 256 QAM. ACM shifts modulations instantaneously in response to
changes in fading conditions. IP-20G utilizes Ceragon’s advanced ACM technology,
and extends it to the range of QPSK to 2048 QAM.
IP-20G also supports Cross Polarization Interference Canceller (XPIC). XPIC enables
operators to double their capacity by utilizing dual-polarization radio over a
single-frequency channel, thereby transmitting two separate carrier waves over
the same frequency, but with alternating polarities.

• Adaptive Coding Modulation (ACM)
• Cross Polarization Interference Canceller (XPIC)
• 1+1 HSB Radio Protection
• ATPC
• Multi-Carrier ABC
• BBS Space Diversity
• Radio Signal Quality PMs
• Radio Utilization PMs
Page 83 of 322

6.2.1 Adaptive Coding Modulation (ACM)
This feature requires:

• ACM script
Related topics:
• Cross Polarization Interference Canceller (XPIC)
• Quality of Service (QoS)
FibeAir IP-20G employs full-range dynamic ACM. IP-20G’s ACM mechanism copes
with 90 dB per second fading in order to ensure high transmission quality. IP-
20G’s ACM mechanism is designed to work with IP-20G’s QoS mechanism to
ensure that high priority voice and data frames are never dropped, thus
maintaining even the most stringent service level agreements (SLAs).
The hitless and errorless functionality of IP-20G’s ACM has another major
advantage in that it ensures that TCP/IP sessions do not time-out. Without ACM,
even interruptions as short as 50 milliseconds can lead to timeout of TCP/IP
sessions, which are followed by a drastic throughout decrease while these
sessions recover.
6.2.1.1 11 Working Points

IP-20G implements ACM with 11 available working points, as follows:
Table 19: ACM Working Points (Profiles)

Working Point (Profile) Modulation
Profile 0 QPSK
Profile 1 8 PSK
Profile 2 16 QAM
Profile 3 32 QAM
Profile 4 64 QAM
Profile 5 128 QAM
Profile 6 256 QAM
Profile 7 512 QAM
Profile 8 1024 QAM (Strong FEC)
Profile 9 1024 QAM (Light FEC)
Profile 10 2048 QAM
Page 84 of 322

Figure 30: Adaptive Coding and Modulation with 11 Working Points
6.2.1.2 Hitless and Errorless Step-by Step Adjustments

ACM works as follows. Assuming a system configured for 128 QAM with ~170
Mbps capacity over a 28 MHz channel, when the receive signal Bit Error Ratio
(BER) level reaches a predetermined threshold, the system preemptively switches
to 64 QAM and the throughput is stepped down to ~140 Mbps. This is an
errorless, virtually instantaneous switch. The system continues to operate at 64
QAM until the fading condition either intensifies or disappears. If the fade
intensifies, another switch takes the system down to 32 QAM. If, on the other
hand, the weather condition improves, the modulation is switched back to the
next higher step (e.g., 128 QAM) and so on, step by step. The switching continues
automatically and as quickly as needed, and can reach all the way down to QPSK
during extreme conditions.
6.2.1.3 ACM Radio Scripts

An ACM radio script is constructed of a set of profiles. Each profile is defined by a
modulation order (QAM) and coding rate, and defines the profile’s capacity (bps).
When an ACM script is activated, the system automatically chooses which profile
to use according to the channel fading conditions.
The ACM TX profile can be different from the ACM RX profile.
The ACM TX profile is determined by remote RX MSE performance. The RX end is
the one that initiates an ACM profile upgrade or downgrade. When MSE improves
above a predefined threshold, RX generates a request to the remote TX to
upgrade its profile. If MSE degrades below a predefined threshold, RX generates a
request to the remote TX to downgrade its profile.
ACM profiles are decreased or increased in an errorless operation, without
affecting traffic.
For ACM to be active, the ACM script must be run in Adaptive mode. In this mode,
the ACM engine is running, which means that the radio adapts its profile
according to the channel fading conditions. Adaptive mode requires an ACM
activation key.
Users also have the option of running an ACM script in Fixed mode. In this mode,
ACM is not active. Instead, the user can select the specific profile from all
available profiles in the script. The selected profile is the only profile that will be
Page 85 of 322

valid, and the ACM engine will be forced to be OFF. Fixed mode can be chosen
without an ACM activation key.
In the case of XPIC/ACM scripts, all the required conditions for XPIC apply.
The user can define a minimum and maximum profile. For example, if the user
selects a maximum profile of 5, the system will not climb above profile 5, even if
channel fading conditions allow it.
6.2.1.4 Hysteresis Value

When stepping down to a lower profile, the switch is initiated when the RSL is
approximately 3.5 dB higher than the threshold for the current profile. When
stepping up to a higher profile, the switch is initiated when the RSL is
approximately 5 dB higher than the threshold for the higher profile.
6.2.1.5 ACM Benefits

The advantages of IP-20G’s dynamic ACM include:
• Maximized spectrum usage
• Increased capacity over a given bandwidth
• 11 working points, with~3 db system gain for each point change
• Hitless and errorless modulation/coding changes, based on signal quality
• Adaptive Radio Tx Power per modulation for maximum system gain per working
point
• An integrated QoS mechanism that enables intelligent congestion management to
ensure that high priority traffic is not affected during link fading conditions.
6.2.1.6 ACM and Built-In QoS

IP-20G’s ACM mechanism is designed to work with IP-20G’s QoS mechanism to
ensure that high priority voice and data frames are never dropped, thus
maintaining even the most stringent SLAs. Since QoS provides priority support for
different classes of service, according to a wide range of criteria, users can
configure IP-20G to discard only low priority frames as conditions deteriorate.
If you want to rely on an external switch’s QoS, ACM can work with the switch via
the flow control mechanism supported in the radio.
6.2.1.7 ACM and 1+1 HSB

When ACM is activated together with 1+1 HSB protection, it is essential to feed
the active RFU via the main channel of the coupler (lossless channel), and to feed
the standby RFU via the secondary channel of the coupler (-6db attenuated
channel). This maximizes system gain and optimizes ACM behavior for the
following reasons:
• In the TX direction, the power will experience minimal attenuation.
• In the RX direction, the received signal will be minimally attenuated. Thus, the
receiver will be able to lock on a higher ACM profile (according to what is
dictated by the RF channel conditions).
Page 86 of 322

The following ACM behavior should be expected in a 1+1 configuration:

• In the TX direction, the Active TX will follow the remote Active RX ACM
requests (according to the remote Active Rx MSE performance).
• The Standby TX might have the same profile as the Active TX, or might stay at
the lowest profile (profile-0). That depends on whether the Standby TX was
able to follow the remote RX Active unit’s ACM requests (only the active
remote RX sends ACM request messages).
• In the RX direction, both the active and the standby carriers follow the remote
Active TX profile (which is the only active transmitter).
Page 87 of 322

6.2.1.8 ACM with Adaptive Transmit Power

• ACM script
• When working with RFU-C, requires RFU software version 2.17 or above
• When working with RFU-HP, requires RFU software version 5.14 or above
• When working with 1500HP, requires RFU software version 8.13a2 or above.
When planning ACM-based radio links, the radio planner attempts to apply the
lowest transmit power that will perform satisfactorily at the highest level of
modulation. During fade conditions requiring a modulation drop, most radio
systems cannot increase transmit power to compensate for the signal
degradation, resulting in a deeper reduction in capacity. IP-20G is capable of
adjusting power on the fly, and optimizing the available capacity at every
modulation point.
The following figure contrasts the transmit output power achieved by using ACM
with Adaptive Power to the transmit output power at a fixed power level, over an
18-23 GHz link. This figure shows how without Adaptive Transmit Power,
operators that want to use ACM to benefit from high levels of modulation (e.g.,
2048 QAM) must settle for low system gain, in this case, 16 dB, for all the other
modulations as well. In contrast, with IP-20G’s Adaptive Transmit Power feature,
operators can automatically adjust power levels, achieving the extra system gain
that is required to maintain optimal throughput levels under all conditions.
Figure 31: ACM with Adaptive Power Contrasted to Other ACM Implementations
Page 88 of 322

6.2.2 Cross Polarization Interference Canceller (XPIC)

• IP-20G hardware assembly with two radio interfaces.
• XPIC script
XPIC is one of the best ways to break the barriers of spectral efficiency. Using
dual-polarization radio over a single-frequency channel, a dual polarization radio
transmits two separate carrier waves over the same frequency, but using
alternating polarities. Despite the obvious advantages of dual-polarization, one
must also keep in mind that typical antennas cannot completely isolate the two
polarizations. In addition, propagation effects such as rain can cause polarization
rotation, making cross-polarization interference unavoidable.
Figure 32: Dual Polarization

The relative level of interference is referred to as cross-polarization discrimination
(XPD). While lower spectral efficiency systems (with low SNR requirements such
as QPSK) can easily tolerate such interference, higher modulation schemes cannot
and require XPIC. IP-20G’s XPIC algorithm enables detection of both streams even
under the worst levels of XPD such as 10 dB. IP-20G accomplishes this by
adaptively subtracting from each carrier the interfering cross carrier, at the right
phase and level. For high-modulation schemes such as 1024 QAM, operating at a
frequency of 28 GHz, an improvement factor of more than 20 dB is required so
that cross-interference does not adversely affect performance.
Page 89 of 322

6.2.2.1 XPIC Implementation

IP-20G units with dual radio interfaces can support XPIC in a single unit utilizing
the two carriers.
The XPIC mechanism utilizes the received signals from the V and H modems to
extract the V and H signals and cancel the cross polarization interference due to
physical signal leakage between V and H polarizations.
The following figure is a basic graphic representation of the signals involved in this
process.
V V+h V
Carrier 1 Carrier 1
h
v
Carrier 2 Carrier 2
H H+v H
IP-20G IP-20G
Figure 33: XPIC Implementation

The H+v signal is the combination of the desired signal H (horizontal) and the
interfering signal V (in lower case, to denote that it is the interfering signal). The
same happens with the vertical (V) signal reception= V+h. The XPIC mechanism
uses the received signals from both feeds and, manipulates them to produce the
desired data.
Figure 34: XPIC – Impact of Misalignments and Channel Degradation

IP-20G’s XPIC reaches a BER of 10e-6 at a high level of co-channel interference
(modulation-dependent). For exact figures, contact your Ceragon representative.
Page 90 of 322

6.2.2.2 XPIC Recovery Mechanism

The XPIC mechanism is based on signal cancellation and assumes that both of the
transmitted signals are received (with a degree of polarity separation). If for some
reason, such as hardware failure, one of the carriers stops receiving a signal, the
working carrier may be negatively affected by the received signals, which cannot
be canceled in this condition.
The purpose of the XPIC recovery mechanism is to preserve the working link while
attempting to recover the faulty polarization.
The mechanism works as follows:
• The recovery mechanism is automatically activated when the unit detects that
one carrier is down (RFU power failure, carrier drawer extraction, carrier
reset, etc.). When activated, the system switches to “Single Carrier” state.
• The recovery mechanism causes the remote transmitter of the faulty carrier to
mute, thus eliminating the disturbing signal and preserving the working link.
• As soon as the failed carrier goes back into service, the XPIC recovery
mechanism adds it back and XPIC operation resumes with both carriers.
The XPIC recovery mechanism is enabled by default, and cannot be disabled by
the user.
6.2.2.3 Conditions for XPIC

XPIC is enabled by selecting an XPIC script for each carrier. In order for XPIC to be
operational, all the following conditions must be met:
• Communications with the RFU must be established by both radio interfaces.
• RFU type must be the same for both carriers.
• The frequency of both radios must be equal.
• 1+1 HSB protection must not be enabled.
• The same script must be loaded for both carriers.
• The script must support XPIC
If any of these conditions is not met, an alarm will alert the user. In addition,
events will inform the user which conditions are not met.
Page 91 of 322

6.2.3 1+1 HSB Radio Protection

IP-20G offers radio redundancy via 1+1 HSB protection. 1+1 HSB protection
provides full protection in the event of interface, signal, or RFU failure.
Note: With Multi-Carrier ABC, 1+1 HSB protection can also be used
with BBS Space Diversity. See BBS Space Diversity on page 98.
The interfaces in a protected pair operate in active and standby
mode. If there is a failure in the active radio interface or RFU, the
standby interface and RFU pair switches to active mode.
Each carrier in a protected pair reports its status to the CPU. The CPU is
responsible for determining when a switchover takes place.
In a 1+1 HSB configuration, the RFUs must be the same type and must have the
same configuration.
IP-20G includes a mismatch mechanism that detects if there is a mismatch
between the radio configurations of the local and mate interfaces and RFUs. This
mechanism is activated by the system periodically and independently of other
protection mechanisms, at fixed intervals. It is activated asynchronously for both
the active and the standby carriers. Once the mismatch mechanism detects a
configuration mismatch, it raises a Mate Configuration Mismatch alarm. When the
configuration of the active and standby carriers is changed to be identical, the
mechanism clears the Mate Configuration Mismatch alarm.
In order to align the configuration between the active and standby carriers, the
user must first complete the required configuration of the active radio interface,
and then perform a copy to mate command. This command copies the entire
configuration of the active interface to the standby interface to achieve full
configuration alignment between the active and standby carriers.
This only needs to be performed once, upon initial setup of the protection group.
Once a pair of carriers has been defined as a 1+1 HSB pair, any configuration
performed on the active carrier will be automatically copied to the standby
carrier, in order to maintain the carrier configuration alignment. This makes it
unnecessary to perform a copy-to-mate command when a configuration change is
made.
Note: The TX Level and Mute settings are not copied to the standby
carrier by the copy to mate command. Therefore, the user must
manually set the TX Level and unmute the standby carrier in
order for 1+1 protection to function.
6.2.3.1 Revertive HSB Protection

In an HSB protection scheme, the active and standby radios are usually connected
to the antenna with an asymmetric coupler. This causes a 6dB loss on one of the
radios on each side of the link, which may result (depending on the active/standby
status of each radio) in up to12dB total path loss for the link. This additional path
Page 92 of 322

loss will either reduce link fade margin or increase the power consumption of the
Power Amplifier (PA) in order to compensate for the additional path loss.
Revertive HSB protection ensures that the radios with no loss are active as long as
no failures are present, resulting in the best possible link budget (0 dB loss).
Coupler Coupler
B -6d
-6d B
Primary Radio Primary Radio
Main Path Main Path
Coupling Path
Coupling Path
Secondary Radio Secondary Radio
Figure 35: Path Loss on Secondary Path of 1+1 HSB Protection Link
IP-20G supports revertive HSB protection. In revertive HSB protection mode, user
defines the primary radio on each side of the link. The primary radio should be the
radio on the coupler’s main path and the secondary radio should be the radio on
the coupling path.
The system monitors the availability of the primary path at all times. Whenever
the primary path is operational and available, without any alarms, but the
secondary path is active, a ten-minute timer is activated. If the primary path
remains operational and available for ten minutes, the system initiates a revertive
protection switch. Every revertive protection switch is recorded as an event in the
event log.
Note: Each protection switch causes traffic disruption.
6.2.3.2 Switchover Triggers

The following events trigger switchover for 1+1 HSB protection according to their
priority, with the highest priority triggers listed first.
1 Hardware module missing
2 Lockout
3 Force switch
4 Traffic failures
5 Manual switch
Page 93 of 322

6.2.4 ATPC
ATPC is a closed-loop mechanism by which each carrier changes the TX power
according to the indication received across the link, in order to achieve a desired
RSL on the other side of the link.
ATPC enables the transmitter to operate at less than maximum power for most of
the time. When fading conditions occur, TX power is increased as needed until the
maximum is reached.
The ATPC mechanism has several potential advantages, including less power
consumption and longer amplifier component life, thereby reducing overall
system cost.
ATPC is frequently used as a means to mitigate frequency interference issues with
the environment, thus allowing new radio links to be easily coordinated in
frequency congested areas.
6.2.4.1 ATPC Override Timer

This feature complies with NSMA Recommendation WG 18.91.032. With ATPC
enabled, if the radio automatically increases its TX power up to the configured
maximum it can lead to a period of sustained transmission at maximum power,
resulting in unacceptable interference with other systems.
To minimize interference, IP-20G provides an ATPC override mechanism. When
ATPC override is enabled, a timer begins when ATPC raises the TX power to its
maximum. When the timer expires, the ATPC maximum TX power is overridden by
the user-configured ATPC override TX power level until the user manually cancels
the ATPC override. The unit then returns to normal ATPC operation.
The following parameters can be configured:
• ATPC Override Admin – Determines whether the ATPC override mechanism is
enabled.
• Override TX Level – The TX power, in dBm, used when the unit is in an ATPC
override state.
• Override Timeout – The amount of time, in seconds, the timer counts from
the moment the radio reaches its maximum configured TX power until ATPC
override goes into effect.
When the radio enters ATPC override state, the radio transmits no higher than the
pre-determined ATPC override TX level, and an ATPC override alarm is raised. The
radio remains in ATPC override state until the ATPC override state is manually
cancelled by the user (or the unit is reset).
In a configuration with unit redundancy or radio protection, the ATPC override
state is propagated to the standby unit or radio in the event of switchover.
Note: When canceling an ATPC override state, the user should ensure
that the underlying problem has been corrected. Otherwise,
ATPC may be overridden again.
Page 94 of 322

6.2.5 Multi-Carrier ABC

Multi-Carrier Adaptive Bandwidth Control (Multi-Carrier ABC) is an innovative
technology that creates logical bundles of multiple radio links optimized for
wireless backhaul applications. Multi-Carrier ABC enables separate radio carriers
to be combined into a virtual transport pipe for a high capacity Ethernet link and
individual TDM links. Both the Ethernet link and the TDM links will be available
over radios with individual variable capacity, and handled by a prioritizing scheme.
In Multi-Carrier ABC mode, traffic is divided among the carriers optimally at the
radio frame level without requiring Ethernet link aggregation (LAG). Load
balancing is performed without regard to the number of MAC addresses or the
number of traffic flows. During fading events which cause ACM modulation
changes, each carrier fluctuates independently with hitless switchovers between
modulations, increasing capacity over a given bandwidth and maximizing
spectrum utilization. In such conditions, the TDM links can be preserved by a
sophisticated prioritizing scheme configured by the user. The result is 100%
utilization of radio resources in which traffic load is balanced based on
instantaneous radio capacity per carrier.
The following diagram illustrates the Multi-Carrier ABC traffic flow.
Carrier 1 Carrier 1
Carrier 2 Carrier 2
Traffic Eth
Eth Traffic Splitter
Combiner
Carrier 3 Carrier 3
Carrier 4 Carrier 4
Figure 36: Multi-Carrier ABC Traffic Flow
Page 95 of 322

6.2.5.1 Multi-Carrier Configurations

In ABC Multi-Carrier mode, IP-20G supports the following configurations:
• 2+0 Multi-Carrier ABC
• 1+1 BBS Space Diversity
• 1 X 2+0 Multi-Carrier ABC Frequency Diversity
6.2.5.2 Multi-Carrier ABC Operation

Multi-Carrier ABC divides each radio carrier into blocks of data. The block size, i.e.,
the number of data bytes inside a block, is configured based on the capacity of the
carrier’s ACM profile. The block size may vary from one block to the other,
independently for each radio carrier.
On the receiving side of the link, all blocks are aligned, which means that all
channels must wait for the slowest arriving block. Alignment does not add any
delay to the slowest carrier. The latency of the aggregated data flow is
determined by the slowest arriving carrier.
A low ACM profile means more latency compared to a higher ACM profile. When
all channels run the same radio script, the latency variation for the aggregated
data stream is determined by the latency variation of one radio channel. This
latency variation is slightly more complicated to predict if the various radio
carriers run different radio scripts, since each radio script has a unique delay
distribution. Multi-Carrier ABC can tolerate a large difference in the degree of
delay between the slowest and the fastest arriving carriers.
Graceful Degradation of Service

Multi-Carrier ABC provides for protection and graceful degradation of service in
the event of failure of an RFU or the slave carrier. This ensures that if one link is
lost, not all data is lost. Instead, bandwidth is simply reduced until the link returns
to service.
The system determines which radio carriers contribute to the aggregated link,
based on the received channel qualities. Other criteria, such as ACM profile and
latency, can also be used. Adding or removing a channel is hitless.
When all channels are up and running, Multi-Carrier ABC provides the maximum
available aggregated capacity. Even when one or more carriers are operating at
limited capacity or are totally down, the data path remains error free. In the event
of degradation in a particular carrier, the carrier is removed from the aggregated
link before bit errors arise, so as not to disturb the aggregated data flow.
Page 96 of 322

Multi-Carrier ABC Minimum Bandwidth Override Option

A Multi-Carrier ABC group can be configured to be placed in Down state if the
group’s aggregated capacity falls beneath a user-defined threshold. This option is
used in conjunction with the LAG override option (see Link Aggregation Groups
(LAG) and LACP on page 146) in cases where the operator wants traffic from an
upstream switch connected to another IP-20 unit to be re-routed whenever the
link is providing less than a certain capacity.
External
Switch LAG
Ethernet Link Ethernet Link Multi-Carrier ABC Link
Upstream IP-20 Unit IP-20G
Alternate Link
Figure 37: Multi-Carrier ABC Minimum Bandwidth Override

By default, the Multi-Carrier ABC minimum bandwidth override option is disabled.
When enabled, the Multi-Carrier ABC group is automatically placed in a Down
state in the event that the group’s aggregated capacity falls beneath the user-
configured threshold. The group is returned to an Up state when the capacity
goes above the threshold.
Note: The Multi-Carrier ABC minimum bandwidth override option is
not available with unit redundancy or HSB radio protection.
Multi-Carrier ABC and ACM

Multi-Carrier ABC automatically adapts to capacity changes that result from
changes in the current ACM profile. When an ACM profile change takes place on a
specific carrier, Multi-Carrier ABC responds by changing the block size of that
channel.
6.2.5.3 Frequency Diversity

In Hybrid Multi-Carrier ABC mode, traffic is split over the available carriers
optimally at the radio frame level irrespective of the traffic type. When using 2+0
MC-ABC, the link provides Frequency Diversity protection while having several
advantages over standard 1+1 Frequency Diversity configurations:
• Higher traffic resiliency in a fading environment
With a 1+1 FD link, throughput is limited by the link with the lowest
modulation. With 2+0 MC-ABC, the traffic is aggregated over the two carriers.
• Higher available capacity (combined capacity of the two carriers)
• Additional link resiliency when using Space Diversity (IFC) for each of the
carriers
Page 97 of 322

6.2.6 BBS Space Diversity

In long distance wireless links with relatively low frequency, multipath
phenomena are common. Both direct and reflected signals are received, which
can cause distortion of the signal resulting in signal fade. The impact of this
distortion can vary over time, space, and frequency. This fading phenomenon
depends mainly on the link geometry and is more severe at long distance links and
over flat surfaces or water. It is also affected by air turbulence and water vapor,
and can vary quickly during temperature changes due to rapid changes in the
reflections phase.
Fading can be flat or dispersive. In flat fading, all frequency components of the
signal experience the same magnitude of fading. In dispersive, or frequency
selective fading, different frequency components of the signal experience
decorrelated fading.
Figure 38: Direct and Reflected Signals

Space Diversity is a common way to negate the effects of fading caused by
multipath phenomena. Space Diversity is implemented by placing two separate
antennas at a distance from one another that makes it statistically likely that if
one antenna suffers from fading caused by signal reflection, the other antenna
will continue to receive a viable signal.
BBS Space Diversity requires two antennas and RFUs. The antennas must be
separated by approximately 15 to 20 meters. The same data stream is received by
both antennas, radios, and modems at the receiving end of the link. The Multi-
Carrier ABC mechanism constantly monitors the signal quality of the main and
diversity carrier, and selects the signal with the best quality. Switching between
the main and diversity carriers is hitless.
Page 98 of 322

Radio &
RX
RMC
M
U
ABC
X
RX
SD RX
Figure 39: 1+1 BBS Space Diversity Configuration – Receiving Side

Note: IP-20G also supports Space Diversity by means of IF Combining.
See Space Diversity with IF Combining on page 58.
Page 99 of 322

6.2.7 Radio Signal Quality PMs

IP-20G supports the following radio signal quality PMs. For each of these PM
types, users can display the minimum and maximum values, per radio, for every
15-minute interval. Users can also define thresholds and display the number of
seconds during which the radio was not within the defined threshold.
• RSL (users can define two RSL thresholds)
• TSL
• MSE
• XPI
Users can display BER PMs, including the current BER per radio, and define
thresholds for Excessive BER and Signal Degrade BER. Alarms are issued if these
thresholds are exceeded. See Configurable BER Threshold Alarms and Traps on
page 237. Users can also configure an alarm that is raised if the RSL falls beneath a
user-defined threshold. See RSL Threshold Alarm on page 237.
Page 100 of 322

6.2.8 Radio Utilization PMs

IP-20G supports the following counters, as well as additional PMs based on these
counters:
• Radio Traffic Utilization – Measures the percentage of radio capacity
utilization, and used to generate the following PMs for every 15-minute
interval:
◦ Peak Utilization (%)
◦ Average Utilization (%)
◦ Over-Threshold Utilization (seconds). The utilization threshold can be
defined by the user (0-100%).
• Radio Traffic Throughput – Measures the total effective Layer 2 traffic sent
through the radio (Mbps), and used to generate the following PMs for every
15-minute interval:
◦ Peak Throughput
◦ Average Throughput
◦ Over-Threshold Utilization (seconds). The threshold is defined as 0.
• Radio Traffic Capacity – Measures the total L1 bandwidth (payload plus
overheads) sent through the radio (Mbps), and used to generate the following
PMs for every 15-minute interval:
◦ Peak Capacity
◦ Average Capacity
◦ Over-Threshold Utilization (seconds). The threshold is defined as 0.
• Frame Error Rate – Measures the frame error rate (%), and used to generate
Frame Error Rate PMs for every 15-minute interval.
Page 101 of 322

6.3 Ethernet Features

IP-20G features a service-oriented Ethernet switching fabric. IP-20G contains four
electrical and two optical 1 GbE Ethernet interfaces, for a total of six Ethernet
interfaces available for traffic. IP-20G also includes two FE interfaces for
management.
IP-20G’s service-oriented Ethernet paradigm enables operators to configure VLAN
definition, CoS, security, and network resiliency on a service, service-point, and
interface level.
IP-20G provides personalized and granular QoS that enables operators to
customize traffic management parameters per customer, application, service
type, or in any other way that reflects the operator’s business and network
requirements.

• Ethernet Services Overview
• IP-20G’s Ethernet Capabilities
• Supported Standards
• Ethernet Service Mode
• Ethernet Interfaces
• Quality of Service (QoS)
• Global Switch Configuration
• Automatic State Propagation and Link Loss Forwarding
• Network Resiliency
• OAM
Page 102 of 322

6.3.1 Ethernet Services Overview

The IP-20G services model is premised on supporting the standard MEF services
(MEF 6, 10), and builds upon this support by the use of very high granularity and
flexibility. Operationally, the IP-20G Ethernet services model is designed to offer a
rich feature set combined with simple and user-friendly configuration, enabling
users to plan, activate, and maintain any packet-based network scenario.
This section first describes the basic Ethernet services model as it is defined by the
MEF, then goes on to provide a basic overview of IP-20G’s Ethernet services
implementation.
The following figure illustrates the basic MEF Ethernet services model.
Figure 40: Basic Ethernet Service Model

In this illustration, the Ethernet service is conveyed by the Metro Ethernet
Network (MEN) provider. Customer Equipment (CE) is connected to the network
at the User Network Interface (UNI) using a standard Ethernet interface
(10/100 Mbps, 1 Gbps). The CE may be a router, bridge/switch, or host (end
system). A NI is defined as the demarcation point between the customer
(subscriber) and provider network, with a standard IEEE 802.3 Ethernet PHY and
MAC.
The services are defined from the point of view of the network’s subscribers
(users). Ethernet services can be supported over a variety of transport
technologies and protocols in the MEN, such as SDH/SONET, Ethernet, ATM,
MPLS, and GFP. However, from the user’s perspective, the network connection at
the user side of the UNI is only Ethernet.
Page 103 of 322

6.3.1.1 EVC
Subscriber services extend from UNI to UNI. Connectivity between UNIs is defined
as an Ethernet Virtual Connection (EVC), as shown in the following figure.
Figure 41: Ethernet Virtual Connection (EVC)

An EVC is defined by the MEF as an association of two or more UNIs that limits the
exchange of service frames to UNIs in the Ethernet Virtual Connection. The EVC
perform two main functions:
• Connects two or more customer sites (UNIs), enabling the transfer of Ethernet
frames between them.
• Prevents data transfer involving customer sites that are not part of the same
EVC. This feature enables the EVC to maintain a secure and private data
channel.
A single UNI can support multiple EVCs via the Service Multiplexing attribute. An
ingress service frame that is mapped to the EVC can be delivered to one or more
of the UNIs in the EVC, other than the ingress UNI. It is vital to avoid delivery back
to the ingress UNI, and to avoid delivery to a UNI that does not belong to the EVC.
An EVC is always bi-directional in the sense that ingress service frames can
originate at any UNI in an EVC.
Service frames must be delivered with the same Ethernet MAC address and frame
structure that they had upon ingress to the service. In other words, the frame
must be unchanged from source to destination, in contrast to routing in which
headers are discarded. Based on these characteristics, an EVC can be used to form
a Layer 2 private line or Virtual Private Network (VPN).
One or more VLANs can be mapped (bundled) to a single EVC.
Page 104 of 322

The MEF has defined three types of EVCs:

1 Point to Point EVC – Each EVC contains exactly two UNIs. The following figure
shows two point-to-point EVCs connecting one site to two other sites.
Figure 42: Point to Point EVC

2 Multipoint (Multipoint-to-Multipoint) EVC – Each EVC contains two or more
UNIs. In the figure below, three sites belong to a single Multipoint EVC and
can forward Ethernet frames to each other.
Figure 43: Multipoint to Multipoint EVC

3 Rooted Multipoint EVC (Point-to-Multipoint) – Each EVC contains one or
more UNIs, with one or more UNIs defined as Roots, and the others defined as
Leaves. The Roots can forward frames to the Leaves. Leaves can only forward
frames to the Roots, but not to other Leaves.
Figure 44: Rooted Multipoint EVC
Page 105 of 322

In the IP-20G, an EVC is defined by either a VLAN or by Layer 1 connectivity (Pipe

Mode).
6.3.1.2 Bandwidth Profile

The bandwidth profile (BW profile) is a set of traffic parameters that define the
maximum limits of the customer’s traffic.
At ingress, the bandwidth profile limits the traffic transmitted into the network:
• Each service frame is checked against the profile for compliance with the
profile.
• Bandwidth profiles can be defined separately for each UNI (MEF 10.2).
• Service frames that comply with the bandwidth profile are forwarded.
• Service frames that do not comply with the bandwidth profile are dropped at
the ingress interface.
The MEF has defined the following three bandwidth profile service attributes:
• Ingress BW profile per ingress UNI
• Ingress BW profile per EVC
• Ingress BW profile per CoS identifier
The BW profile service attribute consists of four traffic parameters:
• CIR (Committed Information Rate)
• CBS (Committed Burst Size)
• EIR (Excess Information Rate)
• EBS (Excess Burst Size)
Bandwidth profiles can be applied per UNI, per EVC at the UNI, or per CoS
identifier for a specified EVC at the UNI.
The Color of the service frame is used to determine its bandwidth profile. If the
service frame complies with the CIR and EIR defined in the bandwidth profile, it is
marked Green. In this case, the average and maximum service frame rates are less
than or equal to the CIR and CBS, respectively.
If the service frame does not comply with the CIR defined in the bandwidth
profile, but does comply with the EIR and EBS, it is marked Yellow. In this case, the
average service frame rate is greater than the CIR but less than the EIR, and the
maximum service frame size is less than the EBS.
If the service frame fails to comply with both the CIR and the EIR defined in the
bandwidth profile, it is marked Red and discarded.
In the IP-20G, bandwidth profiles are constructed using a full standardized TrTCM
policer mechanism.
Page 106 of 322

6.3.1.3 Ethernet Services Definitions

The MEF provides a model for defining Ethernet services. The purpose of the MEF
model is to help subscribers better understand the variations among different
types of Ethernet services. IP-20G supports a variety of service types defined by
the MEF. All of these service types share some common attributes, but there are
also differences as explained below.
Ethernet service types are generic constructs used to create a broad range of
services. Each Ethernet service type has a set of Ethernet service attributes that
define the characteristics of the service. These Ethernet service attributes in turn
are associated with a set of parameters that provide various options for the
various service attributes.
Figure 45: MEF Ethernet Services Definition Framework

The MEF defines three generic Ethernet service type constructs, including their
associated service attributes and parameters:
• Ethernet Line (E-Line)
• Ethernet LAN (E-LAN)
• Ethernet Tree (E-Tree)
Multiple Ethernet services are defined for each of the three generic Ethernet
service types. These services are differentiated by the method for service
identification used at the UNIs. Services using All-to-One Bundling UNIs (port-
based) are referred to as “Private” services, while services using Service
Multiplexed (VLAN-based) UNIs are referred to as “Virtual Private” services. This
relationship is shown in the following table.
Table 20: MEF-Defined Ethernet Service Types

Service Type Port Based VLAN-BASED
(All to One Bundling) (EVC identified by VLAN ID)
E-Line (Point-to-Point Ethernet Private Line (EPL) Ethernet Virtual Private Line (EVPL)
EVC)
E-LAN (Multipoint-to- Ethernet Private LAN (EP-LAN) Ethernet Virtual Private LAN (EVP-
Multipoint EVC) LAN)
E-Tree (Rooted Ethernet Private Tree (EP-Tree) Ethernet Virtual Private Tree (EVP-
Multipoint EVC) Tree)
All-to-One Bundling refers to a UNI attribute in which all Customer Edge VLAN IDs
(CE-VLAN IDs) entering the service via the UNI are associated with a single EVC.
Page 107 of 322

Bundling refers to a UNI attribute in which more than one CE-VLAN ID can be
associated with an EVC.
To fully specify an Ethernet service, additional service attributes must be defined
in addition to the UNI and EVC service attributes. These service attributes can be
grouped under the following categories:
• Ethernet physical interfaces
• Traffic parameters
• Performance parameters
• Class of service
• Service frame delivery
• VLAN tag support
• Service multiplexing
• Bundling
• Security filters
E-Line Service
The Ethernet line service (E-Line service) provides a point-to-point Ethernet
Virtual Connection (EVC) between two UNIs. The E-Line service type can be used
to create a broad range of Ethernet point-to-point services and to maintain the
necessary connectivity. In its simplest form, an E-Line service type can provide
symmetrical bandwidth for data sent in either direction with no performance
assurances, e.g., best effort service between two FE UNIs. In more sophisticated
forms, an E-Line service type can provide connectivity between two UNIs with
different line rates and can be defined with performance assurances such as CIR
with an associated CBS, EIR with an associated EBS, delay, delay variation, loss,
and availability for a given Class of Service (CoS) instance. Service multiplexing can
occur at one or both UNIs in the EVC. For example, more than one point-to-point
EVC can be offered on the same physical port at one or both of the UNIs.
Figure 46: E-Line Service Type Using Point-to-Point EVC
Ethernet Private Line Service

An Ethernet Private Line (EPL) service is specified using an E-Line Service type. An
EPL service uses a point-to-point EVC between two UNIs and provides a high
degree of transparency for service frames between the UNIs that it interconnects
such that the service frame’s header and payload are identical at both the source
Page 108 of 322

and destination UNI when the service frame is delivered (L1 service). A dedicated
UNI (physical interface) is used for the service and service multiplexing is not
allowed. All service frames are mapped to a single EVC at the UNI. In cases where
the EVC speed is less than the UNI speed, the CE is expected to shape traffic to the
ingress bandwidth profile of the service to prevent the traffic from being
discarded by the service. The EPL is a port-based service, with a single EVC across
dedicated UNIs providing site-to-site connectivity. EPL is the most popular
Ethernet service type due to its simplicity, and is used in diverse applications such
as replacing a TDM private line.
Figure 47: EPL Application Example
Figure 48: EPL Application Example
Ethernet Virtual Private Line Service

An Ethernet Virtual Private Line (EVPL) is created using an E-Line service type. An
EVPL can be used to create services similar to EPL services. However, several
characteristics differ between EPL and EVPL services.
First, an EVPL provides for service multiplexing at the UNI, which means it enables
multiple EVCs to be delivered to customer premises over a single physical
connection (UNI). In contrast, an EPL only enables a single service to be delivered
over a single physical connection.
Second, the degree of transparency for service frames is lower in an EVPL than in
an EPL.
Since service multiplexing is permitted in EVPL services, some service frames may
be sent to one EVC while others may be sent to other EVCs. EVPL services can be
used to replace Frame Relay and ATM L2 VPN services, in order to deliver higher
bandwidth, end-to-end services.
Page 109 of 322

Figure 49: EVPL Application Example
E-LAN Service
The E-LAN service type is based on Multipoint to Multipoint EVCs, and provides
multipoint connectivity by connecting two or more UNIs. Each site (UNI) is
connected to a multipoint EVC, and customer frames sent from one UNI can be
received at one or more UNIs. If additional sites are added, they can be connected
to the same multipoint EVC, simplifying the service activation process. Logically,
from the point of view of a customer using an E-LAN service, the MEN can be
viewed as a LAN.
Figure 50: E-LAN Service Type Using Multipoint-to-Multipoint EVC

The E-LAN service type can be used to create a broad range of services. In its basic
form, an E-LAN service can provide a best effort service with no performance
assurances between the UNIs. In more sophisticated forms, an E-LAN service type
can be defined with performance assurances such as CIR with an associated CBS,
EIR with an associated EBS, delay, delay variation, loss, and availability for a given
CoS instance.
For an E-LAN service type, service multiplexing may occur at none, one, or more
than one of the UNIs in the EVC. For example, an E-LAN service type (Multipoint-
to-Multipoint EVC) and an E-Line service type (Point-to-Point EVC) can be service
multiplexed at the same UNI. In such a case, the E-LAN service type can be used to
interconnect other customer sites while the E-Line service type is used to connect
to the Internet, with both services offered via service multiplexing at the same
UNI.
Page 110 of 322

E-LAN services can simplify the interconnection among a large number of sites, in
comparison to hub/mesh topologies implemented using point-to-point
networking technologies such as Frame Relay and ATM.
For example, consider a point-to-point network configuration implemented using
E-Line services. If a new site (UNI) is added, it is necessary to add a new, separate
EVC to all of the other sites in order to enable the new UNI to communicate with
the other UNIs, as shown in the following figure.
Figure 51: Adding a Site Using an E-Line service

In contrast, when using an E-LAN service, it is only necessary to add the new UNI
to the multipoint EVC. No additional EVCs are required, since the E-LAN service
uses a multipoint to multipoint EVC that enables the new UNI to communicate
with each of the others UNIs. Only one EVC is required to achieve multi-site
connectivity, as shown in the following figure.
Figure 52: Adding a Site Using an E-LAN service

The E-LAN service type can be used to create a broad range of services, such as
private LAN and virtual private LAN services.
Ethernet Private LAN Service

It is often desirable to interconnect multiple sites using a Local Area Network
(LAN) protocol model and have equivalent performance and access to resources
such as servers and storage. Customers commonly require a highly transparent
service that connects multiple UNIs. The Ethernet Private LAN (EP-LAN) service is
Page 111 of 322

defined with this in mind, using the E-LAN service type. The EP-LAN is a Layer 2
service in which each UNI is dedicated to the EP-LAN service. A typical use case for
EP-LAN services is Transparent LAN.
The following figure shows an example of an EP-LAN service in which the service is
defined to provide Customer Edge VLAN (CE-VLAN) tag preservation and tunneling
for key Layer 2 control protocols. Customers can use this service to configure
VLANs across the sites without the need to coordinate with the service provider.
Each interface is configured for All-to-One Bundling, which enables the EP-LAN
service to support CE-VLAN ID preservation. In addition, EP-LAN supports CE-VLAN
CoS preservation.
Figure 53: MEF Ethernet Private LAN Example
Ethernet Virtual Private LAN Service

Customers often use an E-LAN service type to connect their UNIs in an MEN, while
at the same time accessing other services from one or more of those UNIs. For
example, a customer might want to access a public or private IP service from a
UNI at the customer site that is also used to provide E-LAN service among the
customer’s several metro locations. The Ethernet Virtual Private LAN (EVP-LAN)
service is defined to address this need. EVP-LAN is actually a combination of EVPL
and E-LAN.
Bundling can be used on the UNIs in the Multipoint-to-Multipoint EVC, but is not
mandatory. As such, CE-VLAN tag preservation and tunneling of certain Layer 2
control protocols may or may not be provided. Service multiplexing is allowed on
each UNI. A typical use case would be to provide Internet access a corporate VPN
via one UNI.
Page 112 of 322

The following figure provides an example of an EVP-LAN service.
Figure 54: MEF Ethernet Virtual Private LAN Example
E-Tree Service
The E-Tree service type is an Ethernet service type that is based on Rooted-
Multipoint EVCs. In its basic form, an E-Tree service can provide a single Root for
multiple Leaf UNIs. Each Leaf UNI can exchange data with only the Root UNI. A
service frame sent from one Leaf UNI cannot be delivered to another Leaf UNI.
This service can be particularly useful for Internet access, and video-over-IP
applications such as multicast/broadcast packet video. One or more CoS values
can be associated with an E-Tree service.
Figure 55: E-Tree Service Type Using Rooted-Multipoint EVC

Two or more Root UNIs can be supported in advanced forms of the E-Tree service
type. In this scenario, each Leaf UNI can exchange data only with the Root UNIs.
The Root UNIs can communicate with each other. Redundant access to the Root
can also be provided, effectively allowing for enhanced service reliability and
flexibility.
Page 113 of 322

Figure 56: E-Tree Service Type Using Multiple Roots

Service multiplexing is optional and may occur on any combination of UNIs in the
EVC. For example, an E-Tree service type using a Rooted-Multipoint EVC, and an E-
Line service type using a Point-to-Point EVC, can be service multiplexed on the
same UNI. In this example, the E-Tree service type can be used to support a
specific application at the Subscriber UNI, e.g., ISP access to redundant PoPs
(multiple Roots at ISP PoPs), while the E-Line Service type is used to connect to
another enterprise site with a Point-to-Point EVC.
Ethernet Private Tree Service

The Ethernet Private Tree service (EP-Tree) is designed to supply the flexibility for
configuring multiple sites so that the services are distributed from a centralized
site, or from a few centralized sites. In this setup, the centralized site or sites are
designed as Roots, while the remaining sites are designated as Leaves. CE-VLAN
tags are preserved and key Layer 2 control protocols are tunneled. The advantage
of such a configuration is that the customer can configure VLANs across its sites
without the need to coordinate with the service provider. Each interface is
configured for All-to-One Bundling, which means that EP-Tree services support CE-
VLAN ID preservation. EP-Tree also supports CE-VLAN CoS preservation. EP-Tree
requires dedication of the UNIs to the single EP-Tree service.
Page 114 of 322

The following figure provides an example of an EP-Tree service.
Figure 57: MEF Ethernet Private Tree Example
Ethernet Virtual Private Tree Service

In order to access several applications and services from well-defined access
points (Root), the UNIs are attached to the service in a Rooted Multipoint
connection. Customer UNIs can also support other services, such as EVPL and EVP-
LAN services. An EVP-Tree service is used in such cases. Bundling can be used on
the UNIs in the Rooted Multipoint EVC, but it is not mandatory. As such, CE-VLAN
tag preservation and tunneling of certain Layer 2 Control Protocols may or may
not be provided. EVP-Tree enables each UNI to support multiple services. A good
example would be a customer that has an EVP-LAN service providing data
connectivity among three UNIs, while using an EVP-Tree service to provide video
broadcast from a video hub location. The following figure provides an example of
a Virtual Private Tree service.
Page 115 of 322

Figure 58: Ethernet Virtual Private Tree Example

IP-20G enables network connectivity for Mobile Backhaul cellular infrastructure,
fixed networks, private networks and enterprises.
Mobile Backhaul refers to the network between the Base Station sites and the
Network Controller/Gateway sites for all generations of mobile technologies.
Mobile equipment and networks with ETH service layer functions can support
MEF Carrier Ethernet services using the service attributes defined by the MEF.
Figure 59: Mobile Backhaul Reference Model

The IP-20G services concept is purpose built to support the standard MEF services
for mobile backhaul (MEF 22, mobile backhaul implementation agreement), as an
addition to the baseline definition of MEF Services (MEF 6) using service attributes
(as well as in MEF 10). E-Line, E-LAN and E-Tree services are well defined as the
standard services.
Page 116 of 322

6.3.1.4 IP-20G Universal Packet Backhaul Services Core

IP-20G addresses the customer demand for multiple services of any of the
aforementioned types (EPL, EVPL, EP –LAN, EVP-LAN, EP-Tree, and EVP-Tree)
through its rich service model capabilities and flexible integrated switch
application. Additional Layer 1 point-based services are supported as well, as
explained in more detail below.
Services support in the mobile backhaul environment is provided using the IP-20G
services core, which is structured around the building blocks shown in the figure
below. IP-20G provides rich and secure packet backhaul services over any
transport type with unified, simple, and error-free operation.
Figure 60: Packet Service Core Building Blocks
Any Service
• Ethernet services (EVCs)
◦ E-Line (Point-to-Point)
◦ E-LAN (Multipoint)
◦ E-Tree (Point-to-Multipoint)12
• Port based (Smart Pipe) services
Any Transport
• Native Ethernet (802.1Q/Q-in-Q)
• Any topology and any mix of radio and fiber interfaces
• Seamless interworking with any optical network (NG-SDH, packet optical
transport, IP/MPLS service/VPN routers)
12
E-Tree services are planned for future release.
Page 117 of 322

Virtual Switching/Forwarding Engine

• Clear distinction between user facing service interfaces (UNI) and intra-
network interfaces
• Fully flexible C-VLAN and S-VLAN encapsulation (classification and
preservation)
• Improved security/isolation without limiting C-VLAN reuse by different
customers
• Per-service MAC learning with 128K MAC addresses support
Fully Programmable and Future-Proof

• Network-processor-based services core
• Ready today to support emerging and future standards and networking
protocols
Rich Policies and Tools with Unified and Simplified Management

• Personalized QoS (H-QoS)13
• Superb service OAM (FM, PM)14
• Carrier-grade service resiliency (G.8032)
13
H-QoS support is planned for future release.
14
PM support is planned for future release.
Page 118 of 322

6.3.2 IP-20G’s Ethernet Capabilities

IP-20G is built upon a service-based paradigm that provides rich and secure frame
backhaul services over any type of transport, with unified, simple, and error-free
operation. IP-20G’s services core includes a rich set of tools that includes:
• Service-based Quality of Service (QoS).
• Service OAM, including FM, granular PMs, and service activation.
• Carrier-grade service resiliency using G.8032.
The following are IP-20G’s main Carrier Ethernet transport features. This rich
feature set provides a future-proof architecture to support backhaul evolution for
emerging services.
• Up to 64 services
• Up to 32 service points per service
• All service types:
◦ Point-to-Point (E-Line)
◦ Multipoint (E-LAN)
◦ Point-to-Multipoint (E-Tree) 15
◦ Smart Pipe
◦ Management
• Split horizon between service points16
• 128K MAC learning table, with separate learning per service (including
limiters)
• Flexible transport and encapsulation via 802.1q, 802.1ad (Q-in-Q)
• High precision, flexible frame synchronization solution combining SyncE and
1588v2Hierarchical QoS with up to 2K service level queues, deep buffering,
hierarchical scheduling via WFQ and Strict priority, and shaping at each level
• 1K hierarchical two-rate three-Color policers
◦ Port based – Unicast, Multicast, Broadcast, Ethertype
◦ Service-based
◦ CoS-based
• Up to four link aggregation groups (LAG)
◦ Hashing based on L2, L3, MPLS, and L4
• Enhanced <50msec network level resiliency (G.8032) for ring/mesh support
15
E-Tree service support is planned for future release.
16
Split horizon is planned for future release.
Page 119 of 322

6.3.3 Supported Standards

IP-20G is fully MEF-9 and MEF-14 certified for all Carrier Ethernet services. For a
full list of standards and certifications supported by IP-20G, refer to the following
section:
• Supported Ethernet Standards
Page 120 of 322

6.3.4 Ethernet Service Model

IP-20G’s service-oriented Ethernet paradigm is based on Carrier-Ethernet
Transport (CET), and provides a highly flexible and granular switching fabric for
Ethernet services.
IP-20G’s virtual switching/forwarding engine is based on a clear distinction
between user-facing service interfaces and intra-network service interfaces. User-
facing interfaces (UNIs) are configured as Service Access Points (SAPs), while intra-
network interfaces (E-NNIs or NNIs) are configured as Service Network Points
(SNPs).
P2P
Service
SNP SNP
UNI
P2P
NNI
Service
SAP SAP
Multipoint SNP SNP Multipoint
SN
SA Service Service
SNP SNP
PP SNP SNP
IP-20G
SAP SAP
SNP SNP
Multipoint Multipoint
Service Service
SNP
SNP
SAP
P2P
Service
SNP
SNP
SNP SNP
IP-20G IP-20G
Multipoint
Service
SNP
SNP SAP
IP-20G
Figure 61: IP-20G Services Model

The IP-20G services core provides for fully flexible C-VLAN and S-VLAN
encapsulation, with a full range of classification and preservation options
available. Service security and isolation is provided without limiting the C-VLAN
reuse capabilities of different customers.
Page 121 of 322

Users can define up to 64 services on a single IP-20G. Each service constitutes a

virtual bridge that defines the connectivity and behavior among the network
element interfaces for the specific virtual bridge. In addition to user-defined
services, IP-20G contains a pre-defined management service (Service ID 1025). If
needed, users can activate the management service and use it for in-band
management.
To define a service, the user must configure virtual connections among the
interfaces that belong to the service. This is done by configuring service points
(SPs) on these interfaces.
A service can hold up to 32 service points. A service point is a logical entity
attached to a physical or logical interface. Service points define the movement of
frames through the service. Each service point includes both ingress and egress
attributes.
Note: Management services can hold up to 30 SPs.
The following figure illustrates the IP-20G services model, with traffic entering and
leaving the network element. IP-20G’s switching fabric is designed to provide a
high degree of flexibility in the definition of services and the treatment of data
flows as they pass through the switching fabric.
P2P Service
Port 1 C-ta 30 00 Port 5

4
g=20 C-tag=
SP SP
SAP
SAP
C-
ta
g=
10
Port 6
00
o 20
Multipoint Service 10 00 t
g=
C-ta
Port 7
SP
SAP SP
SAP 2 ,3
tag=
SC-
Port 2 Untag
Port 8
SP
SAP SP
SAP
200
a g=
Port 3 S-t
C-tag=20
SP
SAP SP
SAP
Smart Pipe Service
Port 4 SP SP
SAP Port 9
SAP
Figure 62: IP-20G Services Core
Page 122 of 322

6.3.4.1 Frame Classification to Service Points and Services

Each arriving frame is classified to a specific service point, based on a key that
consists of:
• The Interface ID of the interface through which the frame entered the IP-20G.
• The frame’s C-VLAN and/or S-VLAN tags.
If the classification mechanism finds a match between the key of the arriving
frame and a specific service point, the frame is associated to the specific service to
which the service point belongs. That service point is called the ingress service
point for the frame, and the other service points in the service are optional egress
service points for the frame. The frame is then forwarded from the ingress service
point to an egress service point by means of flooding or dynamic address learning
in the specific service. Services include a MAC entry table of up to 131,072 entries,
with a global aging timer and a maximum learning limiter that are configurable
per-service.
P2P Service
User Port
GE/FE Port SAP

SAP SNP
SAP
P2P Service Network

User Port
Port
GE/FE Port SAP

SAP SNP
SAP Port Ethernet Ethernet
traffic Radio
Multipoint Service
SAP SNP Network

User Port Port
GE/FE Port Port Ethernet Ethernet

traffic Radio
SAP SNP
Figure 63: IP-20G Services Flow
6.3.4.2 Service Types

IP-20G supports the following service types:
• Point-to-Point Service (P2P)
• MultiPoint Service (MP)
• Management Service
• Point-to-Multipoint Service (E-Tree)
Note: E-Tree service support is planned for future release.
Page 123 of 322

Point to Point Service (P2P)

Point-to-point services are used to provide connectivity between two interfaces of
the network element. When traffic ingresses via one side of the service, it is
immediately directed to the other side, according to ingress and egress tunneling
rules. This type of service contains exactly two service points and does not require
MAC address-based learning or forwarding. Since the route is clear, the traffic is
tunneled from one side of the service to the other and vice versa.
The following figure illustrates a P2P service.
P2P Service
Port 1 Port 4
SP SP
SAP
SAP
Port 2 Port 5
P2P Service
SP
SAP SP
SAP
Port 3 Port 6
Figure 64: Point-to-Point Service

P2P services provide the building blocks for network services such as E-Line EVC
(EPL and EVPL EVCs) and port-based services (Smart Pipe).
Multipoint Service (MP)

Multipoint services are used to provide connectivity between two or more service
points. When traffic ingresses via one service point, it is directed to one of the
service points in the service, other than the ingress service point, according to
ingress and egress tunneling rules, and based on the learning and forwarding
mechanism. If the destination MAC address is not known by the learning and
forwarding mechanism, the arriving frame is flooded to all the other service points
in the service except the ingress service point.
Page 124 of 322

The following figure illustrates a Multipoint service.
Multipoint Service
Port 1 SP SP Port 4
SAP SAP
SP
SAP
Port 2 Port 5
SP SP
SAP
SAP
Port 3 Port 6
Figure 65: Multipoint Service

Multipoint services provide the building blocks for network services such as E-LAN
EVCs (EP-LAN and EVP-LAN EVCs), and for E-Line EVCs (EPL and EVPL EVCs) in
which only two service points are active. In such a case, the user can disable MAC
address learning in the service points to conserve system resources.
Learning and Forwarding Mechanism

IP-20G can learn up to 131,072 Ethernet source MAC addresses. IP-20G performs
learning per service in order to enable the use of 1024 virtual bridges in the
network element. If necessary due to security issues or resource limitations, users
can limit the size of the MAC forwarding table. The maximum size of the MAC
forwarding table is configurable per service in granularity of 16 entries.
When a frame arrives via a specific service point, the learning mechanism checks
the MAC forwarding table for the service to which the service point belongs to
determine whether that MAC address is known to the service. If the MAC address
is not found, the learning mechanism adds it to the table under the specific
service.
In parallel with the learning process, the forwarding mechanism searches the
service’s MAC forwarding table for the frame’s destination MAC address. If a
match is found, the frame is forwarded to the service point associated with the
MAC address. If not, the frame is flooded to all service points in the service.
Page 125 of 322

The following table illustrates the operation of the learning and forwarding
mechanism.
Table 21: Ethernet Services Learning and Forwarding

MAC Forwarding Table
Input Key for learning / forwarding Result Entry Type

(search) operation
Service ID MAC address Service Point
13 00:34:67:3a:aa:10 15 dynamic
13 00:0a:25:33:22:12 31 dynamic
28 00:0a:25:11:12:55 31 static
55 00:0a:25:33:22:12 15 dynamic
55 00:c3:20:57:14:89 31 dynamic
55 00:0a:25:11:12:55 31 dynamic
In addition to the dynamic learning mechanism, users can add static MAC
addresses for static routing in each service. These user entries are not considered
when determining the maximum size of the MAC forwarding table.
Users can manually clear all the dynamic entries from the MAC forwarding table.
Users can also delete static entries per service.
The system also provides an automatic flush process. An entry is erased from the
table as a result of:
• The global aging time expires for the entry.
• Loss of carrier occurs on the interface with which the entry is associated.
• Resiliency protocols, such as MSTP or G.8032.
Management Service (MNG)

The management service is a multipoint service that connects the two local
management ports, the network element host CPU, and the traffic ports into a
single service. The service behavior is same as the Multipoint service behavior.
The management service is pre-defined in the system, with Service ID 1025. The
pre-defined management service has a single service point that connects the
service to the network element host CPU and the two local management
interfaces. To configure in-band management over multiple network elements,
the user must connect the management service to the network by adding a
service point on an interface that provides the required network connectivity.
Page 126 of 322

Users can modify the attributes of the management service, but cannot delete it.
The CPU service point is read-only and cannot be modified. The local management
ports are also connected to the service, but their service points are not visible to
users. The first management interface is enabled by default. The second
management interface must be manually enabled by the user. The management
ports can be used to manage the network element or to access a remote network
element. They can also be used to manage third-party devices. Users can enable
or disable these ports.
The following figure illustrates a management service.
Management Service
Port 1
Port 4
SP
SAP SP
SAP
Port 2
Port 5
SP SP
SAP
SAP
Port 3
Port 6
SP SP
SAP
SAP
Local Management 1
Local Management 2
CPU
Figure 66: Management Service

Management services can provide building blocks for network services such as E-
LAN EVCs (EP-LAN and EVP-LAN), as well as E-Line EVCs (EPL and EVPL EVCs) in
which only two service points are active.
Service Attributes
IP-20G services have the following attributes:
• Service ID – A running number from 1 to 1024 that identifies the service. The
user must select the Service ID upon creating the service. The Service ID
cannot be edited after the service has been created. Service ID 1025 is used
for the pre-defined Management service.
• Service Type – Determines the specific functionality that will be provided for
Ethernet traffic using the service. For example, a Point-to-Point service
provides traffic forwarding between two service points, with no need to learn
a service topology based on source and destination MAC addresses. A
Multipoint service enables operators to create an E-LAN service that includes
several service points.
Page 127 of 322

• Service Admin Mode – Defines whether or not the service is functional, i.e.,
able to receive and transmit traffic. When the Service Admin Mode is set to
Operational, the service is fully functional. When the Service Admin Mode is
set to Reserved, the service occupies system resources but is unable to
transmit and receive data.
• EVC-ID – The Ethernet Virtual Connection ID (end-to-end). This parameter
does not affect the network element’s behavior, but is used by the NMS for
topology management.
• EVC Description – The Ethernet Virtual Connection description. This
parameter does not affect the network element’s behavior, but is used by the
NMS for topology management.
• Maximum Dynamic MAC Address Learning per Service – Defines the
maximum number of dynamic Ethernet MAC address that the service can
learn. This parameter is configured with a granularity of 16, and only applies
to dynamic, not static, MAC addresses.
• Static MAC Address Configuration – Users can add static entries to the MAC
forwarding table. The global aging time does not apply to static entries, and
they are not counted with respect to the Maximum Dynamic MAC Address
Learning. It is the responsibility of the user not to use all the 131,072 entries in
the table if the user also wants to utilize dynamic MAC address learning.
• CoS Mode – Defines whether the service inherits ingress classification
decisions made at previous stages or overwrites previous decisions and uses
the default CoS defined for the service. For more details on IP-20G’s
hierarchical classification mechanism, refer to Classification on page 150.
• Default CoS – The default CoS value at the service level. If the CoS Mode is set
to overwrite previous classification decisions, this is the CoS value used for
frames entering the service.
• xSTP Instance (0-46, 4095) – The spanning tree instance ID to which the
service belongs. The service can be a traffic engineering service (instance ID
4095) or can be managed by the xSTP engines of the network element.
Page 128 of 322

6.3.4.3 Service Points

Service points are logical entities attached to the interfaces that make up the
service. Service points define the movement of frames through the service.
Without service points, a service is simply a virtual bridge with no ingress or
egress interfaces.
IP-20G supports several types of service points:
• Management (MNG) Service Point – Only used for management services. The
following figure shows a management service used for in-band management
among four network elements in a ring. In this example, each service contains
three MNG service points, two for East-West management connectivity in the
ring, and one serving as the network gateway.
MNG
MNG MNG
MNG
MNG
MNG MNG
MNG MNG
MNG MNG
MNG
Figure 67: Management Service and its Service Points

• Service Access Point (SAP) Service Point – An SAP is equivalent to a UNI in
MEF terminology and defines the connection of the user network with its
access points. SAPs are used for Point-to-Point and Multipoint traffic services.
Page 129 of 322

• Service Network Point (SNP) Service Point – An SNP is equivalent to an NNI or

E-NNI in MEF terminology and defines the connection between the network
elements in the user network. SNPs are used for Point-to-Point and Multipoint
traffic services.
The following figure shows four network elements in ring. An MP Service with
three service points provides the connectivity over the network. The SNPs
provide the connectivity among the network elements in the user network
while the SAPs provide the access points for the network.
SAP
SNP SNP
SNP
SNP
SAP SAP
SNP SNP
SNP SNP
SAP
Figure 68: SAPs and SNPs

• Pipe Service Point – Used to create traffic connectivity between two points in
a port-based manner (Smart Pipe). In other words, all the traffic from one port
passes to the other port. Pipe service points are used in Point-to-Point
services
The following figure shows a Point-to-Point service with Pipe service points
that create a Smart Pipe between Port 1 of the network element on the left
and Port 2 of the network element on the right.
Page 130 of 322

Pipe Pipe Pipe Pipe
Figure 69: Pipe Service Points

The following figure shows the usage of SAP, SNP and PIPE service points in a
microwave network. The SNPs are used for interconnection between the network
elements while the SAPs provide the access points for the network. A Smart Pipe
is also used, to provide connectivity between elements that require port-based
connectivity.
Fiber Aggregation
Network
SAP
SNP
SNP
SNP
Microwave
SNP Network
SAP
SNP
SNP
NOC SNP
SNP
SNP
SNP
SNP
SAP
PIPE
PIPE
SNP
SAP
SAP
Base Station
Figure 70: SAP, SNP and Pipe Service Points in a Microwave Network
Page 131 of 322

The following table summarizes the service point types available per service type.
Table 22: Service Point Types per Service Type

MNG SAP SNP Pipe
Service Type Management Yes No No No

Point-to-Point No Yes Yes Yes
Multipoint No Yes Yes No
Service Point Classification

As explained above, service points connect the service to the network element
interfaces. It is crucial that the network element have a means to classify
incoming frames to the proper service point. This classification process is
implemented by means of a parsing encapsulation rule for the interface
associated with the service point. This rule is called the Attached Interface Type,
and is based on a three-part key consisting of:
• The Interface ID of the interface through which the frame entered.
• The frame’s C-VLAN and/or S-VLAN tags.
The Attached Interface Type provides a definitive mapping of each arriving frame
to a specific service point in a specific service. Since more than one service point
may be associated with a single interface, frames are assigned to the earliest
defined service point in case of conflict.
SAP Classification
SAPs can be used with the following Attached Interface Types:
• All to one – All C-VLANs and untagged frames that enter the interface are
classified to the same service point.
• Dot1q – A single C-VLAN is classified to the service point.
• QinQ – A single S-VLAN and C-VLAN combination is classified to the service
point.
• Bundle C-Tag– A set of multiple C-VLANs are classified to the service point.
• Bundle S-Tag – A single S-VLAN and a set of multiple C-VLANs are classified to
the service point.
SNP classification
SNPs can be used with the following Attached Interface Types:
• Dot1q – A single C VLAN is classified to the service point.
• S-Tag – A single S- VLAN is classified to the service point.
Page 132 of 322

MNG classification
Management service points can be used with the following Attached Interface
Types:
• Dot1q – A single C-VLAN is classified to the service point.
• S-Tag – A single S-VLAN is classified to the service point.
• QinQ – A single S-VLAN and C-VLAN combination is classified into the service
point.
The following table shows which service point types can co-exist on the same
interface.
Table 23: Service Point Types that can Co-Exist on the Same Interface
MNG SP SAP SP SNP SP Pipe SP
MNG SP Only one MNG SP is Yes Yes Yes
allowed per interface.
SAP SP Yes Yes No No
SNP SP Yes No Yes No
PIPE SP Yes No No Only one Pipe SP is allowed
per interface.
The following table shows in more detail which service point – Attached Interface
Type combinations can co-exist on the same interface.
Page 133 of 322

Table 24: Service Point Type-Attached Interface Type Combinations that can Co-Exist on the Same Interface
SP Type SAP SNP Pipe MNG
SP Type Attached 802.1q Bundle Bundle All to One QinQ 802.1q S-Tag 802.1q S-Tag 802.1q QinQ S-Tag
Interface Type C-Tag S-Tag
SAP 802.1q Yes Yes No No No No No Only for P2P Service No Yes No No
Bundle C-Tag Yes Yes No No No No No Only for P2P Service No Yes No No
Bundle S-Tag No No Yes No Yes No No No No No Yes No
All to One No No No Only 1 All to One No No No No No No No No

SP Per Interface
QinQ No No Yes No Yes No No No No No Yes No
SNP 802.1q No No No No No Yes No Only for P2P Service No Yes No No
S-Tag No No No No No No Yes No Only for P2P No No Yes

Service
Pipe 802.1q Only for Only for P2P No No No Only for No Only one Pipe SP Per No Yes No No
P2P Service Service P2P Service Interface
S-Tag No No No No No No Only for P2P No Only one Pipe SP No No Yes

Service Per Interface
MNG 802.1q Yes Yes No No No Yes No Yes No No No No
QinQ No No Yes No Yes No No No No No No No
S-Tag No No No No No No Yes No Yes No No No
Page 134 of 322

Service Point Attributes

As described above, traffic ingresses and egresses the service via service points.
The service point attributes are divided into two types:
• Ingress Attributes – Define how frames are handled upon ingress, e.g.,
policing and MAC address learning.
• Egress Attributes – Define how frames are handled upon egress, e.g.,
preservation of the ingress CoS value upon egress, VLAN swapping.
The following figure shows the ingress and egress path relationship on a point-to-
point service path. When traffic arrives via port 1, the system handles it using
service point 1 ingress attributes then forwards it to service point 2 and handles it
using the SP2 egress attributes:
SP1 SP2
Ingress Ingress
Port 1 Port 2
Egress Egress
Figure 71: Service Path Relationship on Point-to-Point Service Path

Service points have the following attributes:
General Service Point Attributes

• Service Point ID – Users can define up to 32 service points per service, except
for management services which are limited to 30 service points in addition to
the pre-defined management system service point.
• Service Point Name – A descriptive name, which can be up to 20 characters.
• Service Point Type – The type of service point, as described above.
• S-VLAN Encapsulation – The S-VLAN ID associated with the service point.
• C-VLAN Encapsulation – The C-VLAN ID associated with the service point.
• Attached C VLAN – For service points with an Attached Interface Type of
Bundle C-Tag, this attribute is used to create a list of C-VLANs associated with
the service point.
• Attached S-VLAN – For service points with an Attached Interface Type of
Bundle S-Tag, this attribute is used to create a list of S-VLANs associated with
the service point.
Page 135 of 322

Ingress Service Point Attributes

The ingress attributes are attributes that operate upon frames when they ingress
via the service point.
• Attached Interface Type – The interface type to which the service point is
attached, as described above. Permitted values depend on the service point
type.
• Learning Administration – Enables or disables MAC address learning for traffic
that ingresses via the service point. This option enables users to enable or
disable MAC address learning for specific service points.
• Allow Broadcast – Determines whether to allow frames to ingress the service
via the service point when the frame has a broadcast destination MAC
address.
• Allow Flooding – Determines whether incoming frames with unknown MAC
addresses are forwarded to other service points via flooding.
• CoS Mode – Determines whether the service point preserves the CoS decision
made at the interface level, overwrites the CoS with the default CoS for the
service point.
• Default CoS – The service point CoS. If the CoS Mode is set to overwrite the
CoS decision made at the interface level, this is the CoS value assigned to
frames that ingress the service point.
• Token Bucket Profile – This attribute can be used to attach a rate meter
profile to the service point. Permitted values are 1– 250.
• CoS Token Bucket Profile – This attribute can be used to attach a rate meter
profile to the service point at the CoS level. Users can define a rate meter for
each of the eight CoS values of the service point. Permitted values are 1-250
for CoS 0–7.
• CoS Token Bucket Admin – Enables or disables the rate meter at the service
point CoS level.
Egress Service Point Attributes

The egress attributes are attributes that operate upon frames egressing via the
service point.
• C-VLAN ID Egress Preservation – If enabled, C-VLAN frames egressing the
service point retain the same C-VLAN ID they had when they entered the
service.
• C-VLAN CoS Egress Preservation – If enabled, the C-VLAN CoS value of frames
egressing the service point is the same as the value when the frame entered
the service.
• S-VLAN CoS Egress Preservation – If enabled, the S-VLAN CoS value of frames
egressing the service point is the same as the value when the frame entered
the service.
Page 136 of 322

• Marking – Marking refers to the ability to overwrite the outgoing priority bits
and Color of the outer VLAN of the egress frame, either the C-VLAN or the S-
VLAN. If marking is enabled, the service point overwrites the outgoing priority
bits and Color of the outer VLAN of the egress frame. Marking mode is only
relevant if either the outer frame is S-VLAN and S-VLAN CoS preservation is
disabled, or the outer frame is C-VLAN and C-VLAN CoS preservation is
disabled. When marking is enabled and active, marking is performed
according to global mapping tables that map the 802.1p-UP bits and the DEI or
CFI bit to a defined CoS and Color value.
• Service Bundle ID – This attribute can be used to assign one of the available
service bundles from the H-QoS hierarchy queues to the service point. This
enables users to personalize the QoS egress path. For details, refer to
Standard QoS and Hierarchical QoS (H-QoS)on page 164.
Page 137 of 322

6.3.5 Ethernet Interfaces

The IP-20G switching fabric distinguishes between physical interfaces and logical
interfaces. Physical and logical interfaces serve different purposes in the switching
fabric.
The concept of a physical interface refers to the physical characteristics of the
interface, such as speed, duplex, auto-negotiation, master/slave, and standard
RMON statistics.
A logical interface can consist of a single physical interface or a group of physical
interfaces that share the same function. Examples of the latter are Multi-Carrier
ABC groups, protection groups, and link aggregation (LAG) groups. Switching and
QoS functionality are implemented on the logical interface level.
It is important to understand that the IP-20G switching fabric regards all traffic
interfaces as regular physical interfaces, distinguished only by the media type the
interface uses, e.g., RJ-45, SFP, or Radio.
From the user’s point of view, the creation of the logical interface is simultaneous
with the creation of the physical interface. For example, when the user enables a
radio interface, both the physical and the logical radio interface come into being
at the same time.
Once the interface is created, the user configures both the physical and the logical
interface. In other words, the user configures the same interface on two levels,
the physical level and the logical level.
The following figure shows physical and logical interfaces in a one-to-one
relationship in which each physical interface is connected to a single logical
interface, without grouping.
Physical Interface 1 Logical Interface SP SP Logical Interface Physical Interface 3
Physical Interface 2 Logical Interface SP SP Logical Interface Physical Interface 4

Service
Figure 72: Physical and Logical Interfaces

Note: For simplicity only, this figure represents a uni-directional rather
than a bi-directional traffic flow.
The next figure illustrates the grouping of two or more physical interfaces into a
logical interface, a link aggregation group (LAG) in this example. The two physical
interfaces on the ingress side send traffic into a single logical interface. The user
configures each physical interface separately, and configures the logical interface
as a single logical entity. For example, the user might configure each physical
interface to 100 Mbps, full duplex, with auto-negotiation off. On the group level,
the user might limit the group to a rate of 200 Mbps by configuring the rate meter
on the logical interface level.
Page 138 of 322

When physical interfaces are grouped into a logical interface, IP-20G also shows
standard RMON statistics for the logical interface, i.e., for the group. This
information enables users to determine the cumulative statistics for the group,
rather than having to examine the statistics for each interface individually.
Physical Interface 1 SP Logical Interface Physical Interface 3

SP
ce
terfa
al In
LAG Logic
Physical Interface 2
SP SP Logical Interface Physical Interface 4

Service
Figure 73: Grouped Interfaces as a Single Logical Interface on Ingress Side

The following figure shows the logical interface at the egress side. In this case, the
user can configure the egress traffic characteristics, such as scheduling, for the
group as a whole as part of the logical interface attributes.
Logical Interface SP SP
Physical Interface 1 Lo
gic
al I Physical Interface 3
nte
rfa
ce
LAG
Physical Interface 4
Physical Interface 2 Logical Interface SP SP
Service
Figure 74: Grouped Interfaces as a Single Logical Interface on Egress Side

6.3.5.1 Physical Interfaces

The physical interfaces refer to the real traffic ports (layer 1) that are connected
to the network. The Media Type attribute defines the Layer 1 physical traffic
interface type, which can be:
• Radio interface.
• RJ-45 or SFP for an Ethernet interface.
• TDM for an E1 interface.
Page 139 of 322

Physical Interface Attributes

The following physical interface parameters can be configured by users:
• Admin – Enables or disables the physical interface. This attribute is set via the
Interface Manager section of the Web EMS.
• Auto Negotiation – Enables or disables auto-negotiation on the physical
interface. Auto Negotiation is always off for radio, SFP, and TDM interfaces.
• Speed and Duplex – The physical interface speed and duplex mode. Permitted
values are:
◦ Ethernet RJ-45 interfaces: 10Mbps HD, 10Mbps FD, 100Mbps HD,
100Mbps FD, and 1000Mbps FD.
◦ Ethernet SFP interfaces: Only 1000FD is supported
◦ Radio and TDM interfaces: The parameter is read-only and set by the
system to 1000FD.
• Flow Control – The physical port flow control capability. Permitted values are:
Symmetrical Pause and/or Asymmetrical Pause. This parameter is only
relevant in Full Duplex mode.17
• Media Type – The physical interface Layer 1 media type. This attribute is only
relevant for Ethernet traffic ports (RJ-45 or SFP). Permitted values are Auto
Detect, RJ-45, and SFP. When Auto Detect is selected, the system detects
whether the optical or electrical port is being used. Auto Detect can only be
used when the interface speed is set to 1000 Mbps.
• IFG – The physical port Inter-frame gap. Although users can modify the IFG
field length, it is strongly recommended not to modify the default value of 12
bytes without a thorough understanding of how the modification will impact
traffic. Permitted values are 6 to 15 bytes.
• Preamble – The physical port preamble value. Although users can modify the
preamble field length, it is strongly recommended not to modify the default
values of 8 bytes without a thorough understanding of how the modification
will impact traffic. Permitted values are 6 to 15 bytes.
• Interface description – A text description of the interface, up to 40 characters.
The following read-only physical interface status parameters can be viewed by
users:
• Operational State – The operational state of the physical interface (Up or
Down).
• Actual Speed and Duplex – The actual speed and duplex value for the
Ethernet link as agreed by the two sides of the link after the auto negotiation
process.
• Actual Flow Control State – The actual flow control state values for the
Ethernet link as agreed by the two sides after the auto negotiation process.
17
This functionality is planned for future release.
Page 140 of 322

• Actual Physical Mode (only relevant for RJ-45 interfaces) – The actual physical
mode (master or slave) for the Ethernet link, as agreed by the two sides after
the auto negotiation process.
Ethernet Statistics
The FibeAir IP-20G platform stores and displays statistics in accordance with
RMON and RMON2 standards.
Users can display various peak TX and RX rates (in seconds) and average TX and RX
rates (in seconds), both in bytes and in packets, for each measured time interval.
Users can also display the number of seconds in the interval during which TX and
RX rates exceeded the configured threshold.
The following transmit statistic counters are available:
• Transmitted bytes (not including preamble) in good or bad frames. Low 32
bits.
• Transmitted bytes (not including preamble) in good or bad frames. High 32
bits.
• Transmitted frames (good or bad)
• Multicast frames (good only)
• Broadcast frames (good only)
• Control frames transmitted
• Pause control frame transmitted
• FCS error frames
• Frame length error
• Oversized frames – frames with length > 1518 bytes (1522 bytes for VLAN-
tagged frames) without errors
• Undersized frames (good only)
• Fragments frames (undersized bad)
• Jabber frames – frames with length > 1518 bytes (1522 for VLAN-tagged
frames) with errors
• Frames with length 64 bytes, good or bad
• Frames with length 65-127 bytes, good or bad
• Frames with length 512-1023 bytes, good or bad.
The following receive statistic counters are available:
• Received bytes (not including preamble) in good or bad frames. Low 32 bits.
• Received bytes (not including preamble) in good or bad frames. High 32 bits.
• Received frames (good or bad)
• Multicast frames (good only)
• Broadcast frames (good only)
Page 141 of 322

• Control frames received

• Pause control frame received
• FCS error frames
• Frame length error
• Code error
• Counts oversized frames – frames with length > 1518 bytes (1522 bytes for
VLAN-tagged frames) without errors and frames with length > MAX_LEN
without errors
• Undersized frames (good only)
• Fragments frames (undersized bad)
• Counts jabber frames – frames with length > 1518 bytes (1522 for VLAN-
tagged frames) with errors
• Frames with length 64 bytes, good or bad
• VLAN-tagged frames with length 1519-1522 bytes, good or bad
• Frames with length > MAX_LEN without errors
• Frames with length > MAX_LEN with errors
6.3.5.2 Logical Interfaces

A logical interface consists of one or more physical interfaces that share the same
traffic ingress and egress characteristics. From the user’s point of view, it is more
convenient to define interface behavior for the group as a whole than for each
individual physical interface that makes up the group. Therefore, classification,
QoS, and resiliency attributes are configured and implemented on the logical
interface level, in contrast to attributes such as interface speed and duplex mode,
which are configured on the physical interface level.
It is important to understand that the user relates to logical interfaces in the same
way in both a one-to-one scenario in which a single physical interface corresponds
to a single logical interface, and a grouping scenario such as a Multi-Carrier ABC
group, a link aggregation (LAG) group, or a radio protection group, in which
several physical interfaces correspond to a single logical interface.
The following figure illustrates the relationship of a 1+1 HSB radio protection
group to the switching fabric. From the point of view of the user configuring the
logical interface attributes, the fact that there are two radios is not relevant. The
user configures and manages the logical interface just as if it represented a single
1+0 radio.
Page 142 of 322

SP SP Logical Interface Physical Interface 3
Radio
Interface 1 Physical Interface 1
HSB Radio Protection Group 1 SP SP Logical Interface Physical Interface 4

Service
Radio Physical Interface 2
Interface 2
Figure 75: Relationship of Logical Interfaces to the Switching Fabric
Logical Interface Attributes

The following logical interface attributes can be configured by users:
General Attributes
• Traffic Flow Administration – Enables traffic via the logical interface. This
attribute is useful when the user groups several physical interfaces into a
single logical interface. The user can enable or disable traffic to the group
using this parameter.
Ingress Path Classification at Logical Interface Level

These attributes represent part of the hierarchical classification mechanism, in
which the logical interface is the lowest point in the hierarchy.
• VLAN ID – Users can specify a specific CoS and Color for a specific VLAN ID. In
the case of double-tagged frames, the match must be with the frame’s outer
VLAN. Permitted values are CoS 0 to 7 and Color Green or Yellow per VLAN ID.
This is the highest classification priority on the logical interface level, and
overwrites any other classification criteria at the logical interface level.
• 802.1p Trust Mode – When this attribute is set to Trust mode and the arriving
packet is 802.1Q or 802.1AD, the interface performs QoS and Color
classification according to user-configurable tables for 802.1q UP bit (C-VLAN
frames) or 802.1AD UP bit (S-VLAN frames) to CoS and Color classification.
• MPLS Trust Mode – When this attribute is set to Trust mode and the arriving
packet has MPLS EXP priority bits, the interface performs QoS and Color
classification according to a user-configurable MPLS EXP bit to CoS and Color
classification table. Both 802.1p and DSCP classification have priority over
MPLS Trust Mode, so that if a match is found on either the 802.1p or DSCP
levels, MPLS bits are not considered.
• IP DSCP Trust Mode –When this attribute is set to Trust mode and the arriving
packet has IP priority bits, the interface performs QoS and Color classification
according to a user-configurable DSCP bit to CoS and Color classification table.
802.1p classification has priority over DSCP Trust Mode, so that if a match is
found on the 802.1p level, DSCP bits are not considered.
Page 143 of 322

• Default CoS – The default CoS value for frames passing through the interface.
This value can be overwritten on the service point and service level. The Color
is assumed to be Green.
For more information about classification at the logical interface level, refer to
Logical Interface-Level Classification on page 151.
Ingress Path Rate Meters at Logical Interface Level

• Unicast Traffic Rate Meter Admin – Enables or disables the unicast rate meter
(policer) on the logical interface.
• Unicast Traffic Rate Meter Profile – Associates the rate meter (policer) with a
specific rate meter (policer) profile.
• Multicast Traffic Rate Meter Admin – Enables or disables the multicast rate
meter (policer) on the logical interface.
• Multicast Traffic Rate Meter Profile – Associates the rate meter (policer) with
a specific rate meter (policer) profile.
• Broadcast Traffic Rate Meter Admin – Enables or disables the broadcast rate
• Broadcast Traffic Rate Meter Profile – Associates the rate meter (policer) with
a specific rate meter (policer) profile.
• Ethertype 1 Rate Meter Admin – Enables or disables the Ethertype 1 rate
• Ethertype 1 Rate Meter Profile – Associates the rate meter (policer) with a
• Ethertype 1 Value – The Ethertype value to which the user wants to apply this
rate meter (policer). The field length is 4 nibbles (for example, 0x0806 - ARP).
• Ethertype 2 Value – The Ethertype value to which the user wants to apply the
• Ethertype 3 Value – The Ethertype value to which the user wants to apply the
• Inline Compensation – The logical interface’s ingress compensation value. The
rate meter (policer) attached to the logical interface uses this value to
compensate for Layer 1 non-effective traffic bytes.
Page 144 of 322

Egress Path Shapers at Logical Interface Level

• Logical Port Shaper Profile – Users can assign a single leaky bucket shaper to
each interface. The shaper on the interface level stops traffic from the
interface if a specific user-defined peak information rate (PIR) has been
exceeded.18
• Outline Compensation – The logical interface’s egress compensation value.
Any shaper attached to this interface, in any layer, uses this value to
compensate for Layer 1 non-effective traffic bytes. Permitted values are even
numbers between 0 and 26 bytes. The default value is 0 bytes.
Egress Path Scheduler at Logical Interface Level

• Logical Interface Priority Profile – This attribute is used to attach an egress
scheduling priority profile to the logical interface.
• Logical Port WFQ Profile – This attribute is used to attach an egress
scheduling WFQ profile to the logical interface. The WFQ profile provides a
means of allocating traffic among queues with the same priority.
The following read-only logical interface status parameters can be viewed by
users:
• Traffic Flow Operational Status – Indicates whether or not the logical
interface is currently functional.
Logical Interface Statistics
RMON Statistics at Logical Interface Level

As discussed in Ethernet Statistics on page 141, if the logical interface represents a
group, such as a LAG or a 1+1 HSB pair, the IP-20G platform stores and displays
RMON and RMON2 statistics for the logical interface.
Rate Meter (Policer) Statistics at Logical Interface Level

For the rate meter (policer) at the logical interface level, users can view the
following statistics counters:
• Green Frames
• Green Bytes
• Yellow Frames
• Yellow Bytes
• Red Frames
• Red Bytes
Note: Rate meter (policer) counters are 64 bits wide.
18
This attribute is reserved for future use. The current release supports traffic shaping per
queue and per service bundle, which provides the equivalent of shaping per logical interface.
Page 145 of 322

Link Aggregation Groups (LAG) and LACP

Link aggregation (LAG) enables users to group several physical interfaces into a
single logical interface bound to a single MAC address. This logical interface is
known as a LAG group. Traffic sent to the interfaces in a LAG group is distributed
by means of a load balancing function. IP-20G uses a distribution function of up to
Layer 4 in order to generate the most efficient distribution among the LAG
physical ports, taking into account:
• MAC DA and MAC SA
• IP DA and IP SA
• C-VLAN
• S-VLAN
• Layer 3 Protocol Field
• UDP/TCP Source Port and Destination Port
• MPLS Label
The LAG distribution function is implemented as follows:
• The hashing is done over the packets header, up to L4
• The 4 LSBs of hashing provide 16 possibilities for streams to hit
• Per each result one port out of 16 LAG members is assigned
• The default assignment is cyclic. For example, for 3-port LAG the ports are
assigned as 1-2-3-1-2-3-1-2-3-1-2-3-1-2-3-1
The user must analyze the Tx traffic load over the link members of the LAG and
decide whether the load balancing is appropriate. If it is not, the user should
select a different distribution function from the list of predefined functions and
check the result again.
For LAG groups that consist of exactly two interfaces, users can change the
distribution function by selecting from ten pre-defined LAG distribution schemes.
The feature includes a display of the TX throughput for each interface in the LAG,
to help users identify the best LAG distribution scheme for their specific link.
LAG can be used to provide redundancy for Ethernet (line protection). LAG can
also be used to aggregate several interfaces in order to create a wider (aggregate)
Ethernet link. For example, LAG can be used to create a 4 Gbps channel.
A LAG group can be configured to be automatically closed in the event of LAG
degradation. This option is used if the customer wants traffic from the switch to
be re-routed during such time as the link is providing less than a certain capacity.
When enabled, the LAG is automatically closed in the event that any one or more
ports in the LAG fail. When all ports in the LAG are again operational, the LAG is
automatically re-opened.
Up to four LAG groups can be created.
Link Aggregation Control Protocol (LACP) expands the capabilities of static LAG,
and provides interoperability with third-party equipment that uses LACP. LACP
improves the communication between LAG members. This improves error
detection capabilities in situations such as improper LAG configuration or
Page 146 of 322

improper cabling. It also enables the LAG to detect uni-directional failure and
remove the link from the LAG, preventing packet loss.
IP-20’s LACP implementation does not include write parameters or churn
detection.
Note: LACP can only be used with Ethernet interfaces.
LACP cannot be used with Enhanced LAG Distribution or with the
LAG Group Shutdown in Case of Degradation Event feature.
LAG groups can include interfaces with the following constraints:
• Only physical interfaces (including radio interfaces), not logical interfaces, can
belong to a LAG group.
• Interfaces can only be added to the LAG group if no services or service points
are attached to the interface.
• Any classification rules defined for the interface are overridden by the
classification rules defined for the LAG group.
• When removing an interface from a LAG group, the removed interface is
assigned the default interface values.
IP-20G enables users to select the LAG members without limitations, such as
interface speed and interface type. Proper configuration of a LAG group is the
responsibility of the user.
Page 147 of 322

6.3.6 Quality of Service (QoS)
Related topics:
• Ethernet Service Mode
• In-Band Management
Quality of Service (QoS) deals with the way frames are handled within the
switching fabric. QoS is required in order to deal with many different network
scenarios, such as traffic congestion, packet availability, and delay restrictions.
IP-20G’s personalized QoS enables operators to handle a wide and diverse range
of scenarios. IP-20G’s smart QoS mechanism operates from the frame’s ingress
into the switching fabric until the moment the frame egresses via the destination
port.
QoS capability is very important due to the diverse topologies that exist in today’s
network scenarios. These can include, for example, streams from two different
ports that egress via single port, or a port-to-port connection that holds hundreds
of services. In each topology, a customized approach to handling QoS will provide
the best results.
The figure below shows the basic flow of IP-20G’s QoS mechanism. Traffic
ingresses (left to right) via the Ethernet or radio interfaces, on the “ingress path.”
Based on the services model, the system determines how to route the traffic.
Traffic is then directed to the most appropriate output queue via the “egress
path.”
Egress
Ingress
Marker
Rate Limit (Optional)
GE/Radio Port Classifier
(Policing) Queue Scheduler/
Manager Shaper
Port GE/Radio
(Optional)
Standard QoS/ H-QoS
Egress
Ingress
Marker
Rate Limit (Optional)
Manager Shaper
Port GE/Radio
(Optional)
Standard QoS/ H-QoS
Egress
Ingress CET/Pipe Marker
Rate Limit Services (Optional)
Manager Shaper
Port GE/Radio
(Optional)
Standard QoS/ H-QoS
Figure 76: QoS Block Diagram

The ingress path consists of the following QoS building blocks:
• Ingress Classifier – A hierarchical mechanism that deals with ingress traffic on
three different levels: interface, service point, and service. The classifier
determines the exact traffic stream and associates it with the appropriate
service. It also calculates an ingress frame CoS and Color. CoS and Color
classification can be performed on three levels, according to the user’s
configuration.
Page 148 of 322

• Ingress Rate Metering – A hierarchical mechanism that deals with ingress

traffic on three different levels: interface, service point, and service point CoS.
The rate metering mechanism enables the system to measure the incoming
frame rate on different levels using a TrTCM standard MEF rate meter, and to
determine whether to modify the color calculated during the classification
stage.
The egress path consists of the following QoS building blocks:
• Queue Manager – This is the mechanism responsible for managing the
transmission queues, utilizing smart WRED per queue and per packet color
(Green or Yellow).
• Scheduling and Shaping – A hierarchical mechanism that is responsible for
scheduling the transmission of frames from the transmission queues, based
on priority among queues, Weighted Fair Queuing (WFQ) in bytes per each
transmission queue, and eligibility to transmit based on required shaping on
several different levels (per queue, per service bundle, and per port).
• Marker – This mechanism provides the ability to modify priority bits in frames
based on the calculated CoS and Color.
The following two modes of operation are available on the egress path:
• Standard QoS – This mode provides eight transmission queues per port.
• Hierarchical QoS (H-QoS) – In this mode, users can associate services from the
service model to configurable groups of eight transmission queues (service
bundles), from a total of up to 2K queues. In H-QoS mode, IP-20G performs
QoS in a hierarchical manner in which the egress path is managed on three
levels: ports, service bundles, and specific queues. This enables users to fully
distinguish between streams, therefore providing a true SLA to customers.
Page 149 of 322

The following figure illustrates the difference between how standard QoS and H-
QoS handle traffic:
Standard QoS
V
Service 1 Voice
D
V Data
D Eth. Ethernet
Service 2 S traffic Radio
V
D S
Streaming
Service 3 S
H-QoS
V
Service 1 D Service 1
S
V
D
Ethernet
Service 2 Service 2
S
Radio
V
Service 3 D Service 3
S
Figure 77: Standard QoS and H-QoS Comparison
6.3.6.1 QoS on the Ingress Path
Classification
IP-20G supports a hierarchical classification mechanism. The classification
mechanism examines incoming frames and determines their CoS and Color. The
benefit of hierarchical classification is that it provides the ability to “zoom in” or
“zoom out”, enabling classification at higher or lower levels of the hierarchy. The
nature of each traffic stream defines which level of the hierarchical classifier to
apply, or whether to use several levels of the classification hierarchy in parallel.
The hierarchical classifier consists of the following levels:
• Logical interface-level classification
• Service point-level classification
• Service level classification
Page 150 of 322

The following figure illustrates the hierarchical classification model. In this figure,
traffic enters the system via the port depicted on the left and enters the service
via the SAP depicted on the upper left of the service. The classification can take
place at the logical interface level, the service point level, and/or the service level.
Service point level

• Preserve previous decision
• Default CoS
• Destination MAC Address (MAC DA)
Port Logical Interface
SAP SNP
SNP
SAP
Logical interface level Service level
• VLAN ID • Default CoS
• 802.1p-based CoS • Preserve Service Point Decision
• DSCP-based CoS
• MPLS EXP-based CoS
• Default CoS
SAP SNP
SNP
SAP
Service
Figure 78: Hierarchical Classification
Logical Interface-Level Classification

Logical interface-level classification enables users to configure classification on a
single interface or on a number of interfaces grouped tougher, such as a LAG
group.
The classifier at the logical interface level supports the following classification
methods, listed from highest to lowest priority. A higher level classification
method supersedes a lower level classification method:
◦ VLAN ID
◦ 802.1p bits.
◦ MPLS EXP field.
◦ DSCP bits.
◦ Default CoS
IP-20G performs the classification on each frame ingressing the system via the
logical interface. Classification is performed step by step from the highest priority
to the lowest priority classification method. Once a match is found, the classifier
determines the CoS and Color decision for the frame for the logical interface-level.
For example, if the frame is an untagged IP Ethernet frame, a match will not be
found until the third priority level (DSCP priority bits). The CoS and Color values
defined for the frame’s DSCP priority bits will be applied to the frame.
Users can disable some of these classification methods by configuring them as un-
trusted. For example, if 802.1p classification is configured as un-trusted for a
specific interface, the classification mechanism does not perform classification by
VLAN UP bits. This is useful, for example, if the required classification is based on
DSCP priority bits.
Page 151 of 322

If no match is found at the logical interface level, the default CoS is applied to
incoming frames at this level. In this case, the Color of the frame is assumed to be
Green.
The following figure illustrates the hierarchy of priorities among classification
methods, from highest (on the left) to lowest (on the right) priority.
Highest
Priority
VLAN ID 802.1p MPLS EXP DSCP Default CoS
Lowest
Priority
Figure 79: Classification Method Priorities

Interface-level classification is configured as part of the logical interface
configuration. For details, refer to Ingress Path Classification at Logical Interface
Level on page 143.
The following tables show the default values for logical interface-level
classification. The key values for these tables are the priority bits of the respective
frame encapsulation layers (VLAN, IP, and MPLS), while the key results are the CoS
and Colors calculated for incoming frames. These results are user-configurable,
but it is recommended that only advanced users should modify the default values.
Table 25: C-VLAN 802.1 UP and CFI Default Mapping to CoS and Color
802.1 UP CFI CoS (configurable) Color (configurable)
0 0 0 Green
0 1 0 Yellow
1 0 1 Green
1 1 1 Yellow
2 0 2 Green
2 1 2 Yellow
3 0 3 Green
3 1 3 Yellow
4 0 4 Green
4 1 4 Yellow
5 0 5 Green
5 1 5 Yellow
6 0 6 Green
6 1 6 Yellow
Page 152 of 322

7 0 7 Green
7 1 7 Yellow
Table 26: S-VLAN 802.1 UP and DEI Default Mapping to CoS and Color
802.1 UP DEI CoS (Configurable) Color (Configurable)
0 0 0 Green
0 1 0 Yellow
1 0 1 Green
1 1 1 Yellow
2 0 2 Green
2 1 2 Yellow
3 0 3 Green
3 1 3 Yellow
4 0 4 Green
4 1 4 Yellow
5 0 5 Green
5 1 5 Yellow
6 0 6 Green
6 1 6 Yellow
7 0 7 Green
7 1 7 Yellow
Table 27: MPLS EXP Default Mapping to CoS and Color

MPLS EXP bits CoS (configurable) Color (configurable)
0 0 Yellow
1 1 Green
2 2 Yellow
3 3 Green
4 4 Yellow
5 5 Green
6 6 Green
7 7 Green
Page 153 of 322

Table 28: DSCP Default Mapping to CoS and Color

DSCP DSCP (bin) Description CoS (Configurable) Color (Configurable)
0 000000 BE (CS0) 0 Green

(default)
10 001010 AF11 1 Green
12 001100 AF12 1 Yellow
14 001110 AF13 1 Yellow
18 010010 AF21 2 Green
20 010100 AF22 2 Yellow
22 010110 AF23 2 Yellow
26 011010 AF31 3 Green
28 011100 AF32 3 Yellow
30 011110 AF33 3 Yellow
34 100010 AF41 4 Green
36 100100 AF42 4 Yellow
38 100110 AF43 4 Yellow
46 101110 EF 7 Green
8 001000 CS1 1 Green
16 010000 CS2 2 Green
24 011000 CS3 3 Green
32 100000 CS4 4 Green
40 101000 CS5 5 Green
48 110000 CS6 6 Green
51 110011 DSCP_51 6 Green
52 110100 DSCP_52 6 Green
54 110110 DSCP_54 6 Green
56 111000 CS7 7 Green
Default value is CoS equal best effort and Color equal Green.
Page 154 of 322

Service Point-Level Classification

Classification at the service point level enables users to give special treatment, in
higher resolution, to specific traffic flows using a single interface to which the
service point is attached. The following classification modes are supported at the
service point level. Users can configure these modes by means of the service point
CoS mode.
◦ Preserve previous CoS decision (logical interface level)
◦ Default service point CoS
◦ MAC DA
If the service point CoS mode is configured to preserve previous CoS decision, the
CoS and Color are taken from the classification decision at the logical interface
level. If the service point CoS mode is configured to default service point CoS
mode, the CoS is taken from the service point’s default CoS, and the Color is
Green.
If the service point CoS mode is configured as MAC DA, frames ingressing the
service point are classified according to their Destination MAC Address (MAC DA).
This gives IP-20N the ability to identify and give priority to frames that lack priority
information, such as untagged non-IP frames.
Two common scenarios in which non-IP frames require prioritization are:
• Networks using IS-IS link state protocol
• Business enterprises using untagged traffic
Up to 64 MAC addresses can be defined per device, including four predefined
MAC addresses. Users can assign each of these MAC addresses a CoS value and a
color.
The following MAC addresses are predefined, with a high priority (CoS=7,
Color=Green). Users can edit or delete these MAC addresses:
• 09:00:2B:00:00:04
• 09:00:2B:00:00:05
• 01:80:C2:00:00:14
• 01:80:C2:00:00:15
These are protocol MAC addresses used to transport IS-IS frames as defined in ISO
9542 and ISO/IEC 10589.
When MAC DA is selected, the MAC DA is the first criterion used to classify frames
ingressing the interface on which the service point is defined.
Service-Level Classification
Classification at the service level enables users to provide special treatment to an
entire service. For example, the user might decide that all frames in a
management service should be assigned a specific CoS regardless of the ingress
port. The following classification modes are supported at the service level:
◦ Preserve previous CoS decision (service point level)
◦ Default CoS
Page 155 of 322

If the service CoS mode is configured to preserve previous CoS decision, frames
passing through the service are given the CoS and Color that was assigned at the
service point level. If the service CoS mode is configured to default CoS mode, the
CoS is taken from the service’s default CoS, and the Color is Green.
Rate Meter (Policing)

IP-20G’s TrTCM rate meter mechanism complies with MEF 10.2, and is based on a
dual leaky bucket mechanism. The TrTCM rate meter can change a frame’s CoS
settings based on CIR/EIR+CBS/EBS, which makes the rate meter mechanism a key
tool for implementing bandwidth profiles and enabling operators to meet strict
SLA requirements.
The IP-20G hierarchical rate metering mechanism is part of the QoS performed on
the ingress path, and consists of the following levels:
• Logical interface-level rate meter
• Service point-level rate meter19
• Service point CoS-level rate meter20
MEF 10.2 is the de-facto standard for SLA definitions, and IP-20G’s QoS
implementation provides the granularity necessary to implement service-oriented
solutions.
Hierarchical rate metering enables users to define rate meter policing for
incoming traffic at any resolution point, from the interface level to the service
point level, and even at the level of a specific CoS within a specific service point.
This option enables users to customize a set of eight policers for a variety of traffic
flows within a single service point in a service.
Another important function of rate metering is to protect resources in the
network element from malicious users sending traffic at an unexpectedly high
rate. To prevent this, the rate meter can cut off traffic from a user that passes the
expected ingress rate.
TrTCM rate meters use a leaky bucket mechanism to determine whether frames
are marked Green, Yellow, or Red. Frames within the Committed Information Rate
(CIR) or Committed Burst Size (CBS) are marked Green. Frames within the Excess
Information Rate (EIR) or Excess Burst Size (EBS) are marked Yellow. Frames that
do not fall within the CIR/CBS+EIR/EBS are marked Red and dropped, without
being sent any further.
IP-20G provides up to 1120 user-defined TrTCM rate meters. The rate meters
implement a bandwidth profile, based on CIR/EIR, CBS/EBS, Color Mode (CM), and
Coupling flag (CF). Up to 250 different profiles can be configured.
Ingress rate meters operate at three levels:
• Logical Interface:
19
Service point-level rate metering is planned for future release.
20
Service point and CoS-level rate metering is planned for future release.
Page 156 of 322

◦ Per frame type (unicast, multicast, and broadcast)

◦ Per frame ethertype
• Per Service Point
• Per Service Point CoS
CoS 1
Service Frame
CoS 2 Ethertype
Point Type
CoS 3
Figure 80: Ingress Policing Model

At each level (logical interface, service point, and service point + CoS), users can
attach and activate a rate meter profile. Users must create the profile first, then
attach it to the interface, service point, or service point + CoS.
Global Rate Meter Profiles

Users can define up to 250 rate meter user profiles. The following parameters can
be defined for each profile:
• Committed Information Rate (CIR) – Frames within the defined CIR are
marked Green and passed through the QoS module. Frames that exceed the
CIR rate are marked Yellow. The CIR defines the average rate in bits/s of
Service Frames up to which the network delivers service frames and meets the
performance objectives. Permitted values are 0 to 1 Gbps, with a minimum
granularity of 32Kbps.
• Committed Burst Size (CBS) – Frames within the defined CBS are marked
Green and passed through the QoS module. This limits the maximum number
of bytes available for a burst of service frames in order to ensure that traffic
conforms to the CIR. Permitted values are 0 to 8192 Kbytes, with a minimum
granularity of 2 Kbytes.
• Excess Information Rate (EIR) – Frames within the defined EIR are marked
Yellow and processed according to network availability. Frames beyond the
combined CIR and EIR are marked Red and dropped by the policer. Permitted
values are 0 to 1 Gbps, with a minimum granularity of 32 Kbps.
• Excess Burst Size (EBS) – Frames within the defined EBS are marked Yellow
and processed according to network availability. Frames beyond the combined
CBS and EBS are marked Red and dropped by the policer. Permitted values are
0 to 8192 Kbytes, with a minimum granularity of 2 Kbytes.
Page 157 of 322

• Color Mode – Color mode can be enabled (Color aware) or disabled (Color
blind). In Color aware mode, all frames that ingress with a CFI/DEI field set to
1 (Yellow) are treated as EIR frames, even if credits remain in the CIR bucket.
In Color blind mode, all ingress frames are treated first as Green frames
regardless of CFI/DEI value, then as Yellow frames (when there is no credit in
the Green bucket). A Color-blind policer discards any previous Color decisions.
• Coupling Flag – If the coupling flag between the Green and Yellow buckets is
enabled, then if the Green bucket reaches the maximum CBS value the
remaining credits are sent to the Yellow bucket up to the maximum value of
the Yellow bucket.
The following parameter is neither a profile parameter, nor specifically a rate
meter parameter, but rather, is a logical interface parameter. For more
information about logical interfaces, refer to Logical Interfaces on page 142.
• Line Compensation – A rate meter can measure CIR and EIR at Layer 1 or
Layer 2 rates. Layer 1 capacity is equal to Layer 2 capacity plus 20 additional
bytes for each frame due to the preamble and Inter Frame Gap (IFG). In most
cases, the preamble and IFG equals 20 bytes, but other values are also
possible. Line compensation defines the number of bytes to be added to each
frame for purposes of CIR and EIR calculation. When Line Compensation is 20,
the rate meter operates as Layer 1. When Line Compensation is 0, the rate
meter operates as Layer 2. This parameter is very important to users that
want to distinguish between Layer 1 and Layer 2 traffic. For example, 1 Gbps
of traffic at Layer 1 is equal to ~760 Mbps if the frame size is 64 bytes, but
~986 Mbps if the frame size is 1500 bytes. This demonstrates that counting at
Layer 2 is not always fair in comparison to counting at Layer 1, that is, the
physical level.
Rate Metering (Policing) at the Logical Interface Level

Rate metering at the logical interface level supports the following:
• Unicast rate meter
• Multicast rate meter
• Broadcast rate mete
• User defined Ethertype 1 rate meter
For each rate meter, the following statistics are available:
• Green Frames (64 bits)
• Green Bytes (64 bits)
• Yellow Frames (64 bits)
• Yellow Bytes (64 bits)
• Red Frames (64 bits)
• Red Bytes (64 bits)
Page 158 of 322

Rate Metering (Policing) at the Service Point Level

Users can define a single rate meter on each service point, up to a total number of
1024 rate meters per network element at the service point and CoS per service
point levels.
The following statistics are available for each service point rate meter:
Rate Metering (Policing) at the Service Point + CoS Level

Users can define a single rate meter for each CoS on a specific service point, up to
a total number of 1024 rate meters per network element at the service point and
CoS per service point levels.
The following statistics are available for each service point + CoS rate meter:
6.3.6.2 QoS on the Egress Path
Queue Manager
The queue manager (QM) is responsible for managing the output transmission
queues. IP-20G supports up to 2K service-level transmission queues, with
configurable buffer size. Users can specify the buffer size of each queue
independently. The total amount of memory dedicated to the queue buffers is
2 Gbits.
The following considerations should be taken into account in determining the
proper buffer size:
• Latency considerations – If low latency is required (users would rather drop
frames in the queue than increase latency) small buffer sizes are preferable.
• Throughput immunity to fast bursts – When traffic is characterized by fast
bursts, it is recommended to increase the buffer sizes to prevent packet loss.
Of course, this comes at the cost of a possible increase in latency.
Users can configure burst size as a tradeoff between latency and immunity to
bursts, according the application requirements.
Page 159 of 322

The queues are ordered in groups of eight queues. These eight queues correspond
to CoS values, from 0 to 7; in other words, eight priority queues.
The following figure depicts the queue manager. Physically, the queue manager is
located between the ingress path and the egress path.
Traffic Flow CoS0

CoS1
SP1 CoS2
SP3
CoS3 Service Bundle 1
CoS4 (8 Queues)
Multipoint
Service CoS5
CoS6
SP2 SP7 CoS7
CoS0
CoS1
SP2 SP3
CoS2

Multipoint SP1 SP5 (8 Queues)
CoS4
Service
CoS5
WRED
SP7 SP6 CoS6
CoS7
CoS0
SP1
Drop Ratio CoS1
(%) CoS2
Queue
Multipoint SP3 CoS3 Service Bundle 3
Occupancy (KB)
Service CoS4 (8 Queues)
SP2 CoS5
CoS6
CoS7
Point to Point SP1

SP2
Service
CoS0
CoS1
CoS2

SP1 (8 Queues)
CoS4
CoS5
Multipoint SP3 CoS6
Service CoS7
SP2
Figure 81: IP-20G Queue Manager

In the figure above, traffic is passing from left to right. The traffic passing from the
ingress path is routed to the correct egress destination interfaces via the egress
service points. As part of the assignment of the service points to the interfaces,
users define the group of eight queues through which traffic is to be transmitted
out of the service point. This is part of the service point egress configuration.
After the traffic is tunneled from the ingress service points to the egress service
points, it is aggregated into one of the eight queues associated with the specific
service point. The exact queue is determined by the CoS calculated by the ingress
path. For example, if the calculated CoS is 6, the traffic is sent to queue 6, and so
on.
Before assigning traffic to the appropriate queue, the system makes a
determination whether to forward or drop the traffic using a WRED algorithm
with a predefined green and yellow curve for the desired queue. This operation is
integrated with the queue occupancy level.
The queues share a single memory of 2 Gbits. IP-20G enables users to define a
specific size for each queue which is different from the default size. Moreover,
Page 160 of 322

users can create an over-subscription scenario among the queues for when the
buffer size of the aggregate queues is lower than the total memory allocated to all
the queues. In doing this, the user must understand both the benefits and the
potential hazards, namely, that if a lack of buffer space occurs, the queue
manager will drop incoming frames without applying the usual priority rules
among frames.
The queue size is defined by the WRED profile that is associated with the queue.
For more details, refer to WRED on page 161.
WRED
The Weighted Random Early Detection (WRED) mechanism can increase capacity
utilization of TCP traffic by eliminating the phenomenon of global synchronization.
Global synchronization occurs when TCP flows sharing bottleneck conditions
receive loss indications at around the same time. This can result in periods during
which link bandwidth utilization drops significantly as a consequence of
simultaneous falling to a “slow start” of all the TCP flows. The following figure
demonstrates the behavior of two TCP flows over time without WRED.
Figure 82: Synchronized Packet Loss

WRED eliminates the occurrence of traffic congestion peaks by restraining the
transmission rate of the TCP flows. Each queue occupancy level is monitored by
the WRED mechanism and randomly selected frames are dropped before the
queue becomes overcrowded. Each TCP flow recognizes a frame loss and restrains
its transmission rate (basically by reducing the window size). Since the frames are
dropped randomly, statistically each time another flow has to restrain its
transmission rate as a result of frame loss (before the real congestion occurs). In
this way, the overall aggregated load on the radio link remains stable while the
transmission rate of each individual flow continues to fluctuate similarly. The
following figure demonstrates the transmission rate of two TCP flows and the
aggregated load over time when WRED is enabled.
Page 161 of 322

Figure 83: Random Packet Loss with Increased Capacity Utilization Using WRED
When queue occupancy goes up, this means that the ingress path rate (the TCP
stream that is ingressing the switch) is higher than the egress path rate. This
difference in rates should be fixed in order to reduce packet drops and to reach
the maximal media utilization, since IP-20G will not egress packets to the media at
a rate which is higher than the media is able to transmit.
To deal with this, IP-20G enables users to define up to 30 WRED profiles. Each
profile contains a Green traffic curve and a Yellow traffic curve. These curves
describe the probability of randomly dropping frames as a function of queue
occupancy. In addition, using different curves for Yellow packets and Green
packets enables users to enforce the rule that Yellow packets be dropped before
Green packets when there is congestion.
IP-20G also includes two pre-defined read-only WRED profiles:
• Profile number 31 defines a tail-drop curve and is configured with the
following values:
100% Yellow traffic drop after 64kbytes occupancy.
100% Green traffic drop after 128kbytes occupancy.
Yellow maximum drop is 100%
Green maximum drop is 100%
• Profile number 32 defines a profile in which all will be dropped. It is for
internal use and should not be applied to traffic.
A WRED profile can be assigned to each queue. The WRED profile assigned to the
queue determines whether or not to drop incoming packets according to the
occupancy of the queue. Basically, as queue occupancy grows, the probability of
dropping each incoming frame increases as well. As a consequence, statistically
more TCP flows will be restrained before traffic congestion occurs.
Page 162 of 322

The following figure provides an example of a WRED profile.

Probability to drop [%]
Yellow max Green max

threshold threshold
100
Yellow max
drop ratio
Green max
drop ratio
Queue depth [bytes]
Yellow min Green min
threshold threshold
Figure 84: WRED Profile Curve

Note: The tail-drop profile, Profile 31, is the default profile for each
queue. A tail drop curve is useful for reducing the effective
queue size, such as when low latency must be guaranteed.
Global WRED Profile Configuration

IP-20G supports 30 user-configurable WRED profiles and one pre-defined (default)
profile. The following are the WRED profile attributes:
• Green Minimum Threshold – Permitted values are 0 Kbytes to 8 Mbytes, with
• Green Maximum Threshold – Permitted values are 0 Kbytes to 8 Mbytes, with
• Green-Maximum Drop – Permitted values are 1% to 100%, with 1% drop
granularity.
• Yellow Minimum Threshold – Permitted values are 0 Kbytes to 8 Mbytes, with
• Yellow Maximum Threshold – Permitted values are 0 Kbytes to 8 Mbytes,
with granularity of 8 Kbytes.
• Yellow Maximum Drop – Permitted values are 1% to 100%, with 1% drop
granularity.
Notes: K is equal to 1024.
Users can enter any value within the permitted range. Based on
the value entered by the user, the software automatically rounds
off the setting according to the granularity. If the user enters a
value below the lowest granular value (except 0), the software
adjusts the setting to the minimum.
Page 163 of 322

For each curve, frames are passed on and not dropped up to the minimum Green
and Yellow thresholds. From this point, WRED performs a pseudo-random drop
with a ratio based on the curve up to the maximum Green and Yellow thresholds.
Beyond this point, 100% of frames with the applicable Color are dropped.
The system automatically assigns the default “tail drop” WRED profile (Profile ID
31) to every queue. Users can change the WRED profile per queue based on the
application served by the queue.
Standard QoS and Hierarchical QoS (H-QoS)

In a standard QoS mechanism, egress data is mapped to a single egress interface.
This single interface supports up to eight priority queues, which correspond to the
CoS of the data. Since all traffic for the interface egresses via these queues, there
is no way to distinguish between different services and traffic streams within the
same priority.
The figure below shows three services, each with three distinct types of traffic
streams:
• Voice – high priority
• Data – medium priority
• Streaming – lower priority
While the benefits of QoS on the egress path can be applied to the aggregate
streams, without H-QoS they will not be able to distinguish between the various
services included in these aggregate streams. Moreover, different behavior
among the different traffic streams that constitute the aggregate stream can
cause unpredictable behavior between the streams. For example, in a situation in
which one traffic stream can transmit 50 Mbps in a shaped manner while another
can transmit 50 Mbits in a burst, frames may be dropped in an unexpected way
due to a lack of space in the queue resulting from a long burst.
Hierarchical QoS (H-QoS) solves this problem by enabling users to create a real
egress tunnel for each stream, or for a group of streams that are bundled
together. This enables the system to fully perform H-QoS with a top-down
resolution, and to fully control the required SLA for each stream.
H-QoS Hierarchy
The egress path hierarchy is based on the following levels:
• Queue level
• Service bundle level
• Logical interface level
The queue level represents the physical priority queues. This level holds up to 2K
queues. Each eight queues are bundled and represent eight CoS priority levels.
One or more service points can be attached to a specific bundle, and the traffic
from the service point to one of the eight queues is based on the CoS that was
calculated on the ingress path.
Note: With standard QoS, all services are assigned to a single default
service bundle.
Page 164 of 322

The service bundle level represents the groups of eight priority queues. Every
eight queues are managed as a single service bundle.
The interface level represents the physical port through which traffic from the
specified service point egresses.
The following summarizes the egress path hierarchy:
• Up to 8 physical interfaces
• One service bundle per interface in standard QoS / 256 service bundles in H-
QoS.
• Eight queues per service bundle
H-QoS on the Interface Level

Users can assign a single leaky bucket shaper to each interface. The shaper on the
interface level stops traffic from the interface if a specific user-defined peak
information rate (PIR) has been exceeded.
In addition, users can configure scheduling rules for the priority queues, as
follows:
• Scheduling (serve) priorities among the eight priority queues.
• Weighted Fair Queuing (WFQ) among queues with the same priority.
Note: The system assigns the rules for all service bundles under the
interface.
RMON counters are valid on the interface level.
H-QoS on the Service Bundle Level

Users can assign a dual leaky bucket shaper to each service bundle. On the service
bundle level, the shaper changes the scheduling priority if traffic via the service
bundle is above the user-defined CIR and below the PIR. If traffic is above the PIR,
the scheduler stops transmission for the service bundle.
Service bundle traffic counters are valid on this level.
Note: With standard QoS, users assign the egress traffic to a single
service bundle (Service Bundle ID 1).
H-QoS on the Queue Level

The egress service point points to a specific service bundle. Depending on the user
application, the user can connect either a single service point or multiple service
points to a service bundle. Usually, if multiple service points are connected to a
service bundle, the service points will share the same traffic type and
characteristics. Mapping to the eight priority queues is based on the CoS
calculated on the ingress path, before any marking operation, which only changes
the egress CoS and Color.
Users can assign a single leaky bucket to each queue. The shaper on the queue
level stops traffic from leaving the queue if a specific user-defined PIR has been
exceeded.
Page 165 of 322

Traffic counters are valid on this level.

The following figure provides a detailed depiction of the H-QoS levels.
Priority 4 (Highest)
Priority 3
Priority 2
Priority 1 (Lowest)
Queues (CoS) Service Bundle Port

Service Point
Single
CoS0 Rate
Single
CoS1 Rate
WFQ
Service 1 CoS2
Single
Rate
Single
CoS3 Rate
Dual
CoS4 Single Shaper
Rate
Single
CoS5 Rate
Single
CoS6 Rate WFQ
CoS7 Single
Rate
Single
Shaper
Single
CoS0 Rate
WFQ
Single
CoS1 Rate
Service 2 CoS2
Single
Rate
Single
CoS3 Rate
Dual
Single
CoS4 Rate
Shaper
Single
CoS5 Rate WFQ
Single
CoS6 Rate
CoS7 Single
Rate
Service Point
Figure 85: Detailed H-QoS Diagram
H- QoS Mode
As discussed above, users can select whether to work in Standard QoS mode or H-
QoS mode.
• If the user configured all the egress service points to transmit traffic via a
single service bundle, the operational mode is Standard QoS. In this mode,
only Service Bundle 1 is active and there are eight output transmission
queues.
• If the user configured the egress service points to transmit traffic via multiple
service bundles, the operational mode is H-QoS. H-QoS mode enables users to
fully distinguish among the streams and to achieve SLA per service.
Page 166 of 322

Shaping on the Egress Path

Egress shaping determines the traffic profile for each queue. IP-20G performs
egress shaping on the following three levels:
• Queue level – Single leaky bucket shaping.
• Service Bundle level – Dual leaky bucket shaping
• Interface level – Single leaky bucket shaping
Queue Shapers
Users can configure up to 31 single leaky bucket shaper profiles. The CIR value can
be set to the following values:
• 16,000 – 32,000,000 bps – granularity of 16,000 bps
• 32,000,000 – 131,008,000 bps – granularity of 64,000 bps
Note: Users can enter any value within the permitted range. Based on
Users can attach one of the configured queue shaper profiles to each priority
queue. If no profile is attached to the queue, no egress shaping is performed on
that queue.
Service Bundle Shapers

Users can configure up to 255 dual leaky bucket shaper profiles. The profiles can
be configured as follows:
• Valid CIR values are:
◦ 0 – 32,000,000 bps – granularity of 16,000 bps
◦ 32,000,000 – 1,000,000,000 bps – granularity of 64,000 bps
• Valid PIR values are:
◦ 16,000 – 32,000,000 bps – granularity of 16,000 bps
◦ 32,000,000 – 1,000,000,000 bps – granularity of 64,000 bps
Users can attach one of the configured service bundle shaper profiles to each
service bundle. If no profile is attached to the service bundle, no egress shaping is
performed on that service bundle.
Page 167 of 322

Interface Shapers
Users can configure up to 31 single leaky bucket shaper profiles. The CIR can be
set to the following values:
• 0 – 8,192,000 bps – granularity of 32,000 bps
• 131,072,000 – 999,424,000 bps – granularity of 8,192,000 bps
value below the value (except 0), the software adjusts the setting
to the minimum.
Users can attach one of the configured interface shaper profiles to each interface.
If no profile is attached to the interface, no egress shaping is performed on that
interface.
Line Compensation for Shaping

Users can configure a line compensation value for all the shapers under a specific
logical interface. For more information, refer to Global Rate Meter Profiles on
page 157.
Egress Scheduling
Egress scheduling is responsible for transmission from the priority queues. IP-20G
uses a unique algorithm with a hierarchical scheduling model over the three levels
of the egress path that enables compliance with SLA requirements.
The scheduler scans all the queues over all the service bundles, per interface, and
determines which queue is ready to transmit. If more than one queue is ready to
transmit, the scheduler determines which queue transmits first based on:
• Queue Priority – A queue with higher priority is served before lower-priority
queues.
• Weighted Fair Queuing (WFQ) – If two or more queues have the same priority
and are ready to transmit, the scheduler transmits frames from the queues
based on a WFQ algorithm that determines the ratio of frames per queue
based on a predefined weight assigned to each queue.
The following figure shows the scheduling mechanism for a single service bundle
(equivalent to Standard QoS). When a user assigns traffic to more than a single
service bundle (H-QoS mode), multiple instances of this model (up to 32 per port)
are valid.
Page 168 of 322

Figure 86: Scheduling Mechanism for a Single Service Bundle
Interface Priority
The profile defines the exact order for serving the eight priority queues in a single
service bundle. When the user attaches a profile to an interface, all the service
bundles under the interface inherit the profile.
The priority mechanism distinguishes between two states of the service bundle:
• Green State – Committed state
• Yellow state – Best effort state
Green State refers to any time when the service bundle total rate is below the
user-defined CIR. Yellow State refers to any time when the service bundle total
rate is above the user-defined CIR but below the PIR.
User can define up to four Green priority profiles, from 4 (highest) to 1 (lowest).
An additional four Yellow priority profiles are defined automatically.
Note: When Frame Cut-Through is enabled, frames in queues with 4th
priority pre-empt frames already in transmission over the radio
from other queues. For details, refer to Frame Cut-Through on
page 81.
Page 169 of 322

The following table provides a sample of an interface priority profile. This profile is
also used as the default interface priority profile.
Table 29: QoS Priority Profile Example

Profile ID (1-9)
CoS Green Priority (user Yellow Priority (read Description
defined) only)
0 1 1 Best Effort
1 2 1 Data Service 4
5 3 1 Real Time 2 (Video with large buffer)
6 3 1 Real Time 1 (Video with small buffer)
7 4 4 Management (Sync, PDUs, etc.)
When the service bundle state is Green (committed state), the service bundle
priorities are as defined in the Green Priority column. When the service bundle
state is Yellow (best effort state), the service bundle priorities are system-defined
priorities shown in the Yellow Priority column.
Note: CoS 7 is always marked with the highest priority, no matter what
the service bundle state is, since it is assumed that only high
priority traffic will be tunneled via CoS 7.
The system supports up to nine interface priority profiles. Profiles 1 to 8 are
defined by the user, while profile 9 is the pre-defined read-only default interface
priority profile.
Page 170 of 322

The following interface priority profile parameters can be configured by users:

• Profile ID – Profile ID number. Permitted values are 1 to 8.
• CoS 0 Priority – CoS 0 queue priority, from 4 (highest) to 1 (lowest).
• CoS 0 Description – CoS 0 user description field, up to 20 characters.
Users can attach one of the configured interface priority profiles to each interface.
By default, the interface is assigned Profile ID 9, the pre-defined system profile.
Weighted Fair Queuing (WFQ)

As described above, the scheduler serves the queues based on their priority, but
when two or more queues have data to transmit and their priority is the same,
the scheduler uses Weighted Fair Queuing (WFQ) to determine the priorities
within each priority. WFQ defines the transmission ratio, in bytes, between the
queues. All the service bundles under the interface inherit the WFQ profile
attached to the interface.
The system supports up to six WFQ interface profiles. Profile ID 1 is a pre-defined
read-only profile, and is used as the default profile. Profiles 2 to 6 are user-
defined profiles.
Page 171 of 322

The following table provides an example of a WFQ profile.
Table 30: WFQ Profile Example

Profile ID (1-7)
CoS Queue Weight (Green) Queue Weight (Yellow – not visible to users)
0 20 20
1 20 20
2 20 20
3 20 20
4 20 20
5 20 20
6 20 20
7 20 20
For each CoS, the user can define;

• Profile ID – Profile ID number. Permitted values are 2 to 6.
• Weight – Transmission quota in bytes. Permitted values are 1 to 20.
Users can attach one of the configured interface WFQ profiles to each interface.
By default, the interface is assigned Profile ID 1, the pre-defined system profile.
Egress PMs and Statistics
Queue-Level Statistics
IP-20G supports the following counters per queue at the queue level:
• Transmitted Green Packet (64 bits counter)
• Transmitted Green Bytes (64 bits counter)
• Transmitted Green Bits per Second (32 bits counter)
• Dropped Green Packets (64 bits counter)
• Dropped Green Bytes (64 bits counter)
• Transmitted Yellow Packets (64 bits counter)
• Transmitted Yellow Bytes (64 bits counter)
• Transmitted Yellow Bits per Second (32 bits counter)
• Dropped Yellow Packets (64 bits counter)
• Dropped Yellow Bytes (64 bits counter)
Page 172 of 322

Service Bundle-Level Statistics

IP-20G supports the following counters per service bundle at the service bundle
level:
• Transmitted Green Packets (64 bits counter)
• Transmitted Green Bytes (64 bits counter)
• Transmitted Green Bits per Second (32 bits counter)
• Dropped Green Packets (64 bits counter)
• Dropped Green Bytes (64 bits counter)
• Transmitted Yellow Packets (64 bits counter)
• Transmitted Yellow Bytes (64 bits counter)
• Transmitted Yellow Bits per Second (32 bits counter)
• Dropped Yellow Packets (64 bits counter)
• Dropped Yellow Bytes (64 bits counter)
PMs for Queue Traffic

For each logical interface, users can configure thresholds for Green and Yellow
traffic per queue. Users can then display the following PMs for 15-minute and 24-
hour intervals, per queue and color:
• Maximum bytes passed per second
• Minimum bytes passed per second
• Average bytes passed per second
• Maximum bytes dropped per second
• Minimum bytes dropped per second
• Average bytes dropped per second
• Maximum packets passed per second
• Minimum packets passed per second
• Average packets passed per second
• Maximum packets dropped per second
• Minimum packets dropped per second
• Average packets dropped per second
• Seconds bytes per second were over the configured threshold per interval
Interface-Level Statistics
For information on statistics at the interface level, refer to Ethernet Statistics on
page 141.
Page 173 of 322

Marker
Marking refers to the ability to overwrite the outgoing priority bits and Color of
the outer VLAN of the egress frame. Marking mode is only applied if the outer
frame is S-VLAN and S-VLAN CoS preservation is disabled, or if the outer frame is
C-VLAN and C-VLAN CoS preservation is disabled. If outer VLAN preservation is
enabled for the relevant outer VLAN, the egress CoS and Color are the same as
the CoS and Color of the frame when it ingressed into the switching fabric.
Marking is performed according to a global table that maps CoS and Color values
to the 802.1p-UP bits and the DEI or CFI bits. If Marking is enabled on a service
point, the CoS and Color of frames egressing the service via that service point are
overwritten according to this global mapping table.
If marking and CoS preservation for the relevant outer VLAN are both disabled,
marking is applied according to the Green frame values in the global marking
table.
When marking is performed, the following global tables are used by the marker to
decide which CoS and Color to use as the egress CoS and Color bits.
Table 31: 802.1q UP Marking Table (C-VLAN)

CoS Color 802.1q UP (Configurable) CFI Color (Configurable)
0 Green 0 0
0 Yellow 0 1
1 Green 1 0
1 Yellow 1 1
2 Green 2 0
2 Yellow 2 1
3 Green 3 0
3 Yellow 3 1
4 Green 4 0
4 Yellow 4 1
5 Green 5 0
5 Yellow 5 1
6 Green 6 0
6 Yellow 6 1
7 Green 7 0
7 Yellow 7 1
Page 174 of 322

Table 32: 802.1ad UP Marking Table (S-VLAN)

CoS Color 802.1ad UP (configurable) DEI Color (configurable)
0 Green 0 0
0 Yellow 0 1
1 Green 1 0
1 Yellow 1 1
2 Green 2 0
2 Yellow 2 1
3 Green 3 0
3 Yellow 3 1
4 Green 4 0
4 Yellow 4 1
5 Green 5 0
5 Yellow 5 1
6 Green 6 0
6 Yellow 6 1
7 Green 7 0
7 Yellow 7 1
The keys for these tables are the CoS and Color. The results are the
802.1q/802.1ad UP and CFI/DEI bits, which are user-configurable. It is strongly
recommended that the default values not be changed except by advanced users.
Page 175 of 322

Standard QoS and Hierarchical QoS (H-QoS) Summary

The following table summarizes and compares the capabilities of standard QoS
and H-QoS.
Table 33: Summary and Comparison of Standard QoS and H-QoS

Capability Standard QoS Hierarchical QoS
Number of transmission 8 256

queues per port
Number of service bundles 1 (always service bundle id equal 1) 32
WRED Per queue (two curves – for green Per queue (two curves – for
traffic and for yellow traffic via the green traffic and for yellow
queue) traffic via the queue)
Shaping at queue level Single leaky bucket Single leaky bucket
Shaping at service bundle Dual leaky bucket Dual leaky bucket
level
Shaping at port level Single leaky bucket (this level is not Single leaky bucket
relevant since it is recommended to
use service bundle level with dual
leaky bucket)
Transmission queues Per queue priority (4 priorities). Per queue priority (4 priorities).
priority All service bundles for a specific
port inherit the 8-queues
priority settings.
Weighted fair Queue Queue level (between queues) Queue level (between queues)
(WFQ) Service Bundle level (between
service bundles)
Marker Supported Supported
Statistics Queue level (8 queues) Queue level (256 queues)
Service bundle level (1 service Service bundle level (32 service
bundle) bundles)
Port level Port level
Page 176 of 322

6.3.7 Global Switch Configuration

The following parameters are configured globally for the IP-20G switch:
• S- VLAN Ethertype –Defines the ethertype recognized by the system as the S-
VLAN ethertype. IP-20G supports the following S-VLAN ethertypes:
◦ 0x8100
◦ 0x88A8 (default)
◦ 0x9100
◦ 0x9200
• C-VLAN Ethertype – Defines the ethertype recognized by the system as the C-
VLAN ethertype. IP-20G supports 0x8100 as the C-VLAN ethertype.
• MRU – The maximum segment size defines the maximum receive unit (MRU)
capability and the maximum transmit capability (MTU) of the system. Users
can configure a global MRU for the system. Permitted values are 64 bytes to
9612 bytes.
Page 177 of 322

6.3.8 Automatic State Propagation and Link Loss Forwarding
Related topics:
• Network Resiliency
Automatic State Propagation (ASP) enables propagation of radio failures back to
the Ethernet port. You can also configure ASP to close the Ethernet port based on
a radio failure at the remote carrier. ASP improves the recovery performance of
resiliency protocols.
Note: It is recommended to configure both ends of the link to the same
ASP configuration.
6.3.8.1 Automatic State Propagation Operation

Automatic state propagation is configured as pairs of interfaces. Each interface
pair includes one Monitored Interface and one Controlled Interface. Multiple pairs
can be configured using the same Monitored Interface and multiple Controlled
Interfaces.
The Monitored Interface is a radio interface, a radio protection group, or a Multi-
Carrier ABC group. The Controlled Interface is an Ethernet interface or LAG. An
Ethernet interface can only be assigned to one Monitored interface.
Each Controlled Interface is assigned an LLF ID. If ASP trigger by remote fault is
enabled on the remote side of the link, the ASP state of the Controlled Interface is
propagated to the Controlled Interface with the same LLF ID at the remote side of
the link. This means if ASP is triggered locally, it is propagated to the remote side
of the link, but only to Controlled Interfaces with LLF IDs that match the LLF IDs of
the affected Controlled Interfaces on the local side of the link.
The following events in the Monitored Interface trigger ASP:
• Radio LOF
• Radio Excessive BER
• Remote Radio LOF
• Remote Excessive BER
• Remote LOC
The user can also configure the ASP pair so that Radio LOF, Radio Excessive BER,
or loss of the Ethernet connection at the remote side of the link will also trigger
ASP.
When a triggering event takes place:
• If the Controlled Interface is an electrical GbE port, the port is closed.
• If the Controlled Interface is an optical GbE port, the port is muted.
The Controlled Interface remains closed or muted until all triggering events are cleared.
In addition, when a local triggering event takes place, the ASP mechanism sends
an indication to the remote side of the link. Even when no triggering event has
taken place, the ASP mechanism sends periodic update messages indicating that
no triggering event has taken place.
Page 178 of 322

Users can configure a trigger delay time, so that when a triggering event takes
place, the ASP mechanism does not propagate the event until this delay time has
elapsed.
6.3.8.2 Automatic State Propagation and Protection

When the Controlled Interface is part of a 1+1 protection pair, a port shutdown
message is only sent to the remote side of the link if both of the protected
interfaces are shut down.
Closing an Ethernet port because of ASP does not trigger a protection switch.
Page 179 of 322

6.3.9 Network Resiliency

IP-20G provides carrier-grade service resiliency using the following protocols:
• G.8032 Ethernet Ring Protection Switching (ERPS)
• Multiple Spanning Tree Protocol (MSTP)
These protocols are designed to prevent loops in ring/mesh topologies.
6.3.9.1 G.8032 Ethernet Ring Protection Switching (ERPS)

ERPS, as defined in the G.8032 ITU standard, is currently the most advanced ring
protection protocol, providing convergence times of sub-50ms. ERPS prevents
loops in an Ethernet ring by guaranteeing that at any time, traffic can flow on all
except one link in the ring. This link is called the Ring Protection Link (RPL). Under
normal conditions, the RPL is blocked, i.e., not used for traffic. One designated
Ethernet Ring Node, the RPL Owner Node, is responsible for blocking traffic at one
end of the RPL. When an Ethernet ring failure occurs, the RPL Owner unblocks its
end of the RPL, allowing the RPL to be used for traffic. The other Ethernet Ring
Node adjacent to the RPL, the RPL Neighbor Node, may also participate in
blocking or unblocking its end of the RPL. A number of ERP instances (ERPIs) can
be created on the same ring.
Note: P2P services are not affected by G.8032, and continue to
traverse ports that are blocked by G.8032.
G.8032 ERPS Benefits

ERPS, as the most advanced ring protection protocol, provides the following
benefits:
• Provides sub-50ms convergence times.
• Provides service-based granularity for load balancing, based on the ability to
configure multiple ERPIs on a single physical ring.
• Provides configurable timers to control switching and convergence
parameters per ERPI.
G.8032 ERPS Operation

The ring protection mechanism utilizes an APS protocol to implement the
protection switching actions. Forced and manual protection switches can also be
initiated by the user, provided the user-initiated switch has a higher priority than
any other local or far-end request.
Ring protection switching is based on the detection of defects in the transport
entity of each link in the ring. For purposes of the protection switching process,
each transport entity within the protected domain has a state of either Signal Fail
(SF) or Non-Failed (OK). R-APS control messages are forwarded by each node in
the ring to update the other nodes about the status of the links.
Note: An additional state, Signal Degrade (SD), is planned for future
release. The SD state is similar to SF, but with lower priority.
Page 180 of 322

Users can configure up to 16 ERPIs. Each ERPI is associated with an Ethernet

service defined in the system. This enables operators to define a specific set of
G.8032 characteristics for individual services or groups of services within the same
physical ring. This includes a set of timers that enables operators to optimize
protection switching behavior per ERPI:
• Wait to Restore (WTR) Timer – Defines a minimum time the system waits
after signal failure is recovered before reverting to idle state.
• Guard Time – Prevents unnecessary state changes and loops.
• Hold-off Time – Determines the time period from failure detection to
response.
Each ERPI maintains a state machine that defines the node’s state for purposes of
switching and convergence. The state is determined according to events that
occur in the ring, such as signal failure and forced or manual switch requests, and
their priority. Possible states are:
• Idle
• Protecting
• Forced Switch (FS)
• Manual Switch (MS)
• Pending
As shown in the following figure, in idle (normal) state, R-APS messages pass
through all links in the ring, while the RPL is blocked for traffic. The RPL can be on
either edge of the ring. R-APS messages are sent every five seconds.
RPL
IP-20G
(Blocked)
Ring Node 1
Wireless Ring IP-20G

Ring Node 4
(RPL Owner)
IP-20G
Ring Node 2
IP-20G
Ring Node 3
R-APS Messages
Traffic
Figure 87: G.8032 Ring in Idle (Normal) State

Once a signal failure is detected, the RPL is unblocked for each ERPI. As shown in
the following figure, the ring switches to protecting state. The nodes that detect
the failure send periodic SF messages to alert the other nodes in the link of the
failure and initiate the protecting state.
Page 181 of 322

IP-20G RPL
(Unblocked)
Ring Node 1
Signal
Failure

Ring Node 4
(RPL Owner)
IP-20G
Ring Node 2
IP-20G
Ring Node 3
R-APS Messages
Traffic
Figure 88: G.8032 Ring in Protecting State

The ability to define multiple ERPIs and assign them to different Ethernet services
or groups of services enables operators to perform load balancing by configuring a
different RPL for each ERPI. The following figure illustrates a ring in which four
ERPIs each carry services with 33% capacity in idle state, since each link is
designated the RPL, and is therefore idle, for a different ERPI.
RPL for
IP-20G
ERPI 1
Ring Node 1
RPL for
ERPI 2
Ring Node 4
RPL for
RPL for
ERPI 4
ERPI 3
IP-20G
Ring Node 2
IP-20G
Ring Node 3
ERPI 1 Traffic
ERPI 2 Traffic
ERPI 3 Traffic
ERPI 4 Traffic
Figure 89: Load Balancing Example in G.8032 Ring
G.8032 Interoperability
G.8032 in IP-20G units is interoperable with IP-20N units running G.8032, as well
as third-party bridges running standard implementations of G.8032.
Page 182 of 322

6.3.9.2 Multiple Spanning Tree Protocol (MSTP)

MSTP, as defined in IEEE 802.1q, provides full connectivity for frames assigned to
any given VLAN throughout a bridged LAN consisting of arbitrarily interconnected
bridges.
With MSTP, an independent multiple spanning tree instance (MSTI) is configured
for each group of services, and only one path is made available (unblocked) per
spanning tree instance. This prevents network loops and provides load balancing
capability. It also enables operators to differentiate among Ethernet services by
mapping them to different, specific MSTIs. The maximum number of MSTIs is
configurable, from 2 to 16.
Note: P2P services are not affected by MSTP, and continue to traverse
ports that are blocked by MSTP.
MSTP is an extension of, and is backwards compatible with, Rapid Spanning Tree
Protocol (RSTP).
IP-20G supports MSTP according to the following IEEE standards:
• 802.1q
• 802.1ad amendment (Q-in-Q)
• 802.1ah (TE instance)
MSTP Benefits
MSTP significantly improves network resiliency in the following ways:
• Prevents data loops by configuring the active topology for each MSTI such that
there is never more than a single route between any two points in the
network.
• Provides for fault tolerance by automatically reconfiguring the spanning tree
topology whenever there is a bridge failure or breakdown in a data path.
• Automatically reconfigures the spanning tree to accommodate addition of
bridges and bridge ports to the network, without the formation of transient
data loops.
• Enables frames assigned to different services or service groups to follow
different data routes within administratively established regions of the
network.
• Provides for predictable and reproducible active topology based on
management of the MSTP parameters.
• Operates transparently to the end stations.
• Consumes very little bandwidth to establish and maintain MSTIs, constituting
a small percentage of the total available bandwidth which is independent of
both the total traffic supported by the network and the total number of
bridges or LANs in the network.
• Does not require bridges to be individually configured before being added to
the network.
Page 183 of 322

MSTP Operation
MSTP includes the following elements:
• MST Region – A set of physically connected bridges that can be portioned into
a set of logical topologies.
• Internal Spanning Tree (IST) – Every MST Region runs an IST, which is a special
spanning tree instance that disseminates STP topology information for all
other MSTIs.
• CIST Root – The bridge that has the lowest Bridge ID among all the MST
Regions.
• Common Spanning Tree (CST) – The single spanning tree calculated by STP,
RSTP, and MSTP to connect MST Regions. All bridges and LANs are connected
into a single CST.
• Common Internal Spanning Tree (CIST) – A collection of the ISTs in each MST
Region, and the CST that interconnects the MST regions and individual
spanning trees. MSTP connects all bridges and LANs with a single CIST.
MSTP specifies:
• An MST Configuration Identifier that enables each bridge to advertise its
configuration for allocating frames with given VIDs to any of a number of
MSTIs.
• A priority vector that consists of a bridge identifier and path cost information
for the CIST.
• An MSTI priority vector for any given MSTI within each MST Region.
Each bridge selects a CIST priority vector for each port based on the priority
vectors and MST Configuration Identifiers received from the other bridges and on
an incremental path cost associated with each receiving port. The resulting
priority vectors are such that in a stable network:
• One bridge is selected to be the CIST Root.
• A minimum cost path to the CIST Root is selected for each bridge.
• The CIST Regional Root is identified as the one root per MST Region whose
minimum cost path to the root is not through another bridge using the same
MST Configuration Identifier.
Based on priority vector comparisons and calculations performed by each bridge
for each MSTI, one bridge is independently selected for each MSTI to be the MSTI
Regional Root, and a minimum cost path is defined from each bridge or LAN in
each MST Region to the MSTI Regional Root.
The following events trigger MSTP re-convergence:
• Addition or removal of a bridge or port.
• A change in the operational state of a port or group (LAG or protection).
• A change in the service to instance mapping.
• A change in the maximum number of MSTIs.
• A change in an MSTI bridge priority, port priority, or port cost.
Note: All except the last of these triggers can cause the entire MSTP to
re-converge. The last trigger only affects the modified MSTI.
Page 184 of 322

MSTP Interoperability
MSTP in IP-20G units is interoperable with:
• IP-20N units running MSTP.
• Third-party bridges running MSTP.
• FibeAir IP-10 units running RSTP.
• Third-party bridges running RSTP
Page 185 of 322

6.3.10 OAM
FibeAir IP-20G provides complete Service Operations Administration and
Maintenance (SOAM) functionality at multiple layers, including:
• Fault management status and alarms.
• Maintenance signals, such as AIS, and RDI.
• Maintenance commands, such as loopbacks and Linktrace commands.
• Ethernet Bandwidth Notification (ETH-BN)
IP-20G is fully compliant with 802.1ag, G.8013/Y.1731, MEF-17, MEF-20, MEF-30,
and MEF-31.
TDM services
Carrier Ethernet services (EVCs)
BNC/RNC
Fiber
Aggregation
Network
IP-20G IP-20G IP-20G
Tail site Aggregation site Fiber site
Figure 90: IP-20G End-to-End Service Management
6.3.10.1 Connectivity Fault Management (FM)

The Y.1731 standard and the MEF-30 specifications define SOAM. SOAM is
concerned with detecting, isolating, and reporting connectivity faults spanning
networks comprising multiple LANs, including LANs other than IEEE 802.3 media.
Y.1731 Ethernet FM (Connectivity Fault Management) consists of three protocols
that operate together to aid in fault management:
• Continuity check
• Link trace
• Loopback.
Note: Link trace is planned for future release.
FibeAir IP-20G utilizes these protocols to maintain smooth system operation and
non-stop data flow.
The following are the basic building blocks of FM:
• Maintenance domains, their constituent maintenance points, and the
managed objects required to create and administer them.
Page 186 of 322

Figure 91: SOAM Maintenance Entities (Example)

• Protocols and procedures used by maintenance points to maintain and
diagnose connectivity faults within a maintenance domain.
◦ CCM (Continuity Check Message): CCM can detect Connectivity Faults (loss
of connectivity or failure in the remote MEP).
◦ Loopback: LBM/LBR mechanism is an on-demand mechanism. It is used to
verify connectivity from any MEP to any certain Maintenance Point in the
MA/MEG. A session of loopback messages can include up to 1024
messages with varying intervals ranging from 1 to 60 seconds. Message
size can reach jumbo frame size.
◦ Linktrace: The LTM/LTR mechanism is an on-demand mechanism. It can
detect the route of the data from any MEP to any other MEP in the
MA/MEG. It can be used for the following purposes:
◦ Adjacent relation retrieval – The ETH-LT function can be used to
retrieve the adjacency relationship between an MEP and a remote MEP
or MIP. The result of running ETH-LT function is a sequence of MIPs
from the source MEP until the target MIP or MEP.
◦ Fault localization – The ETH-LT function can be used for fault
localization. When a fault occurs, the sequence of MIPs and/or MEP will
probably be different from the expected sequence. The difference
between the sequences provides information about the fault location.
◦ AIS: AIS (defined in G.8013/Y.1731O) is the Ethernet alarm indication
signal function used to suppress alarms following detection of defect
conditions at the server (sub) layer.
Page 187 of 322

6.3.10.2 Ethernet Line Interface Loopback

FibeAir IP-20G supports loopback testing for its radio and TDM interfaces, which
enables loopback testing of the radio and TDM traffic interfaces as well as the
IDU-RFU connection.
Note: To perform radio loopback, the radio must be set to its maximum
TX power.
In addition, the Ethernet Line Interface Loopback feature provides the ability to
run loopbacks over the link. When Ethernet loopback is enabled on an interface,
the system loops back all packets ingressing the interface. This enables loopbacks
to be performed over the link from other points in the network.
For example, as shown in the figure below, a loopback can be performed from
test equipment over the line to an Ethernet interface. A loopback can also be
performed from the other side of the radio link.
Loopback on
Radio Link
IP-20G IP-20G
Loopback from Test

Equipment to IP-20G
Ethernet Interface
Test
Equipment
Figure 92: Ethernet Line Interface Loopback – Application Examples

Ethernet loopbacks can be performed on any logical interface. This includes
optical and electrical GbE interfaces, radio interfaces, Multi-Carrier ABC groups,
LAGs, and 1+1 HSB groups. Ethernet loopbacks cannot be performed on the
management interfaces.
The following parameters can be configured for an Ethernet loopback:
• The interface can be configured to swap DA and SA MAC addresses during the
loopback. This prevents Ethernet loops from occurring. It is recommended to
enable MAC address swapping if MSTP or LLDP is enabled.
• Ethernet loopback has a configurable duration period of up to 15 minutes, but
can be disabled manually before the duration period ends. Permanent
loopback is not supported.
Ethernet loopbacks can be configured on more than one interface simultaneously.
When an Ethernet loopback is active, network resiliency protocols (G.8032 and
MSTP) will detect interface failure due to the failure to receive BPDUs.
Page 188 of 322

In a system using in-band management, Ethernet loopback activation on the

remote side of the link causes loss of management to the remote unit. The
duration period of the loopback should take this into account.
6.3.10.3 Ethernet Bandwidth Notification (ETH-BN)

Ethernet Bandwidth Notification (ETH-BN) is defined by the Y.1731 OAM standard.
The purpose of ETH-BN is to inform the L2 or L3 customer switch of the capacity
of the radio link in transmit direction. This enables the switch to respond to
fluctuations in the radio link by, for example, reconfiguring the shaper on the
egress port facing the radio link or rerouting traffic to other egress ports.
Once ETH-BN is enabled, the radio unit reports bandwidth information to
upstream third-party switches. The ETH-BN entity creates a logical relationship
between a radio interface, called the Monitored Interface, and an Ethernet
interface, called the Control Interface. When bandwidth degrades from the
nominal value in the Monitored Interface, messages relaying the actual
bandwidth values (BNM frames) are periodically sent over the Control Interface.
Once the bandwidth returns to its nominal level, BNM messages are no longer
sent. Optionally, the device can be configured to send BNM frames even when
bandwidth is at its nominal level.
The same radio interface can be configured as a Monitored Interface for multiple
EBN instances. However, an Ethernet interface can only be configured as a Control
Interface for a single EBN instance.
Note the following limitations:
• ETH-BN cannot be used with HSB protection groups.
• When used with unit redundancy, the reported bandwidth may be inaccurate
when switchover is in effect.
• If CFM MEPs are being used, the MEL for ETH-BN must be set to a value
greater than the MEG level of the MEP. Otherwise, the BNM frames will be
dropped. – this is correct.
• If CFM MEPs are not being used, the MEL for ETH-BN must be set to a value
greater than 0. Otherwise, the BNM frames will be dropped.
Page 189 of 322

6.4 Synchronization
This section describes IP-20G’s flexible synchronization solution that enables
operators to configure a combination of synchronization techniques, based on the
operator’s network and migration strategy, including:
• Native Sync Distribution, for end-to-end distribution using GbE, FE, E1, T3,
and/or T4 sync input and output.
• SyncE PRC Pipe Regenerator mode, providing PRC grade (G.811) performance
for pipe (“regenerator”) applications.
• IEEE-1588v2 PTP Optimized Transport, providing both frequency and phase
synchronization for compliance with rigorous LTE and LTE-A requirements.

• Synchronization Overview
• IP-20G Synchronization Solution
• Native Sync Distribution Mode
• SyncE PRC Pipe Regenerator Mode
• IEEE-1588v2 PTP Optimized Transport
Page 190 of 322

6.4.1 Synchronization Overview

Synchronization is essential to ensuring optimal performance in
telecommunications networks. Proper synchronization prevents packet loss,
dropped frames, and degradation of quality of experience that can adversely
affect end-user services.
Synchronization is particularly critical to mobile networks in order to ensure
successful call-signal handoff and proper transmission between base stations, as
well as for the transport of real-time services. If individual base stations drift
outside specified frequencies, this can cause mobile handoff delays, resulting in
high dropped-call rates, impaired data services, and, ultimately, lost subscribers.
Mobile base stations require a highly accurate timing signal that must be shared
across the entire network. If any base station drifts outside of the specified +/- 50
ppb threshold, mobile handoff performance degrades, resulting in a high
disconnect rate and poor data-service quality.
6.4.1.1 Types of Synchronization in Mobile Networks

Synchronization in a mobile network involves frequency and phase (time)
synchronization.
Frequency synchronization maintains consistency between the frequencies of
clock signals to ensure that all devices operate at the same rate. Information is
coded into discrete pulses through pulse code modulation (PCM) and transmitted
on the data communication network. If the clock frequencies of two digital
switching devices are different, the bits in the buffer of the digital switching
system may be lost or duplicated, resulting in a slip in the bit stream.
Phase synchronization, also known as time synchronization, adjusts the internal
clock of a local device according to received time information. In contrast to
frequency synchronization, time synchronization adjusts the clock at irregular
intervals.
Phase synchronization involves two major functions: time service and time
keeping. Time service adjusts the clock according to the standard time. By
adjusting the clock at irregular intervals, a device synchronizes its phase with the
standard reference time. Time keeping refers to frequency synchronization, and
ensures that the difference between the time on the local device and the
standard reference time is within a reasonable range during the interval of clock
adjustment.
6.4.1.2 Additional Synchronization Requirements of LTE Networks

LTE imposes additional challenges with respect to synchronization.
Synchronization solutions must meet the rigorous LTE timing and delivery
requirements that ensure network quality and availability.
While TDM networks were able to exploit GPS for synchronization purposes, LTE
enables deployment of small cells in locations where access to GPS is not reliable.
Without the GPS signals that are traditionally used to provide accurate frequency
and time-of-day synchronization information, LTE networks must find other
means for synchronization.
Page 191 of 322

There are additional difficulties with ensuring proper synchronization in LTE

networks. For example, the LTE downlink radio interface relies on an OFDMA
transmission technique in the downlink. OFDMA presents tremendous benefits in
terms of high spectral efficiency, support of advanced features such as frequency
selective scheduling, MIMO, immunity to multipath interference, and interference
coordination. However, these advantages require that the orthogonality between
OFDMA subcarriers be strictly preserved. The orthogonality between the
subcarriers prevents overlapping of the subcarriers’ spectra which would result in
interference between subcarriers.
A frequency offset can also lead to dropped calls during handover between base
stations. During the handover procedure, user equipment (UE) must determine
the timing and frequency parameters of the base station in order to be able to
demodulate the downlink signal and also to transmit correctly on the uplink. The
frequency-stability tolerance of the UE oscillator is typically maintained at 0.1
ppm to minimize cost. Its stability is maintained by tracking the base station
carrier frequency, a critical synchronization requirement.
In addition, in LTE-TDD systems, downlink and uplink transmission occur in the
same channel but in different time slots. Both frequency and phase
synchronization are required in LTE-TDD to avoid interference between the uplink
and the downlink transmissions on neighboring base stations.
Page 192 of 322

6.4.2 IP-20G Synchronization Solution

Ceragon’s synchronization solution ensures maximum flexibility by enabling the
operator to select any combination of techniques suitable for the operator’s
network and migration strategy.
• Native Sync Distribution
◦ End-to-End Native Synchronization distribution
◦ GbE/FE/E121/T3 input
◦ GbE/FE/E122/T4 output
◦ Supports any radio link configuration and network topology
◦ Synchronization Status Messages (SSM) to prevent loops and enable use of
most reliable clock source
◦ User-defined clock source priority and quality level
◦ Automated determination of relative clock source quality levels
• SyncE PRC Pipe Regenerator mode23
◦ PRC grade (G.811) performance for pipe (“regenerator”) applications
• IEEE-1588v2 PTP Optimized Transport
◦ Transparent Clock – Resides between master and slave nodes, and
measurers and adjusts for delay variation to guarantee ultra-low PDV.
◦ Boundary Clock – Regenerates frequency and phase synchronization,
providing, increasing the scalability of the synchronization network while
rigorously maintaining timing accuracy.
21
E1 input is planned for future release.
22
E1 output is planned for future release. However, E1 via T4 output from the synchronization
interface is supported.
23
SyncE PRC Pipe Regenerator mode is planned for future release.
Page 193 of 322

6.4.3 Native Sync Distribution Mode

In this mode, synchronization is distributed end-to-end over the radio links in the
network.
No TDM trails or E1 interfaces at the tail sites are required.
Synchronization is typically provided by one or more clock sources (SSU/GPS) at
fiber hub sites.
Eth
E1
Eth IP-20G
E1
IP-20G
Eth
E1
IP-20G
Figure 93: Native Sync Distribution Mode

Native Sync Distribution mode can be used in any link configuration and any
network topology.
Ring topologies present special challenges for network synchronization. Any
system that contains more than one clock source for synchronization, or in which
topology loops may exist, requires an active mechanism to ensure that:
• A single source is used as the clock source throughout the network, preferably
the source with the highest accuracy.
• There are no reference loops. In other words, no element in the network will
use an input frequency from an interface that ultimately derived that
frequency from one of the outputs of that network element.
IP-20G’s Native Sync Distribution mechanism enables users to define a priority
level for each possible clock source. Synchronization Status Messages (SSM) are
sent regularly through each interface involved in frequency distribution, enabling
the network to gather and maintain a synchronization status for each interface
according to the system’s best knowledge about the frequency quality that can be
conveyed by that interface.
Based on these parameters, the network assigns each interface a quality level and
determines which interface to use as the current clock source. The network does
this by evaluating the clock quality of the available source interfaces and selecting,
from those interfaces with the highest quality, the interface with the highest user-
defined priority.
The synchronization is re-evaluated whenever one of the following occurs:
• Any synchronization source is added, edited, or deleted by a user.
• The clock quality status changes for any source interface.
Page 194 of 322

• The synchronization reference is changed for the node.
6.4.3.1 Available Interfaces for Native Sync Distribution

Frequency signals can be taken by the system from a number of different
interfaces (one reference at a time). The reference frequency may also be
conveyed to external equipment through different interfaces.
Table 34: Native Sync Interface Options

Interface Available for Input Available for Output
Ethernet Interfaces Yes Yes

Traffic E1 No No
2MHz via T3 input from Sync Interface, Yes n/a
supporting both 2048 Kbp/s and 2048 KHz
E1 via T3 input from Sync Interface Yes n/a
2MHz via T4 output from Sync interface n/a Yes
E1 via T4 output from Sync Interface n/a Yes
Radio Carrier Yes Yes
It is possible to configure up to 16 synchronization sources in the system. At any

given moment, only one of these sources is active; the clock is taken from the
active source onto all other appropriately configured interfaces
6.4.3.2 Configuring Native Sync Distribution

Frequency is distributed by configuring the following parameters in each node:
• System synchronization sources. These are the interfaces from which the
frequency is taken and distributed to other interfaces. Up to 16 sources can be
configured in each node. A revertive timer can be configured. For each
interface, user must configure:
◦ Its clock quality level. The quality level may be fixed (according to ITU-T
G.781 option I) or automatic. When the quality level is automatic, it is
determined by SSM messages.
◦ Its priority (1-16). No two interfaces may have the same priority.
• For each interface, the source of its outgoing signal clock. This can be:
◦ Local clock: Causes the interface to generate its signal from a local
oscillator, unrelated to the system reference frequency.
◦ Synchronization reference: Causes the interface to generate its signal
from the system reference clock, which is taken from the synchronization
source.
◦ Loop Timing: Causes the interface to generate the signal from its own
input.
Page 195 of 322

• The node’s synchronization mode. This can be:

◦ Automatic: In this mode, the active source is automatically selected based
on the interface with highest available quality. Among interfaces with
identical quality, the interface with the highest priority is used.
◦ Force: The user can force the system to use a certain interface as the
reference clock source.24
By configuring synchronization sources and transporting the reference frequency
to the related interfaces in a network, a frequency “flow” can be achieved, as
shown in the example below, where the reference frequency from a single node is
distributed to a number of base stations.
Sync Source
Radio Link
IP-20G Node
Ethernet Interface Signal Clock = Reference
E1 Interface Sync Source
IP-20G Node
Signal Clock = Reference Signal Clock = Reference
Sync Source Sync Source

Signal Clock = Reference IP-20G IP-20G
BTS Converter Converter
Signal Clock = Reference Signal Clock = Reference Signal Clock = Reference
Sync Source Sync Source Sync Source

Converter Converter Converter
Signal Clock = Reference Signal Clock = Reference Signal Clock = Reference
BTS BTS BTS
Figure 94: Synchronization Configuration

The following restrictions apply for frequency distribution configuration:
• An interface can either be used as a synchronization source or can take its
signal from the system reference, but not both (no loop timing available,
except locally in SDH interfaces).
• The clock taken from a line interface (E1, SDH, Ethernet) cannot be conveyed
to another line interface in the same card.
• The clock taken from a radio channel cannot be conveyed to another radio
channel in the same radio.
If the signal driving the synchronization fails, an alarm will alert the user and the
system will enter holdover mode until another synchronization source signal is
found.
Note: Normally, when an interface is in holdover state, it uses stored
data to determine its outgoing clock. However, customers can
set the unit to apply a default quality of DNU (Do Not Use) to any
interface in holdover state.
24
Force mode is planned for future release.
Page 196 of 322

6.4.3.3 SSM Support and Loop Prevention

In order to provide topological resiliency for synchronization transfer, IP-20G
implements the passing of SSM messages over the radio interfaces. SSM timing in
IP-20G complies with ITU-T G.781.
In addition, the SSM mechanism provides reference source resiliency, since a
network may have more than one source clock.
The following are the principles of operation:
• At all times, each source interface has a “quality status” which is determined
as follows:
◦ If quality is configured as fixed, then the quality status becomes “failure”
upon interface failure (such as LOS, LOC, LOF, etc.).
◦ If quality is automatic, then the quality is determined by the received SSMs
or becomes “failure” upon interface failure (such as LOS, LOC, LOF, etc.).
• Each unit holds a parameter which indicates the quality of its reference clock.
This is the quality of the current synchronization source interface.
• The reference source quality is transmitted through SSM messages to all
relevant radio interfaces.
• Each unit determines the current active clock reference source interface:
◦ The interface with the highest available quality is selected.
◦ From among interfaces with identical quality, the interface with the
highest priority is selected.
• In order to prevent loops, an SSM with quality “Do Not Use” is sent towards
the active source interface
At any given moment, the system enables users to display:
• The current source interface quality.
• The current received SSM status for every source interface.
• The current node reference source quality.
As a reference, the following are the possible quality values (from highest to
lowest):
• AUTOMATIC (available only in interfaces for which SSM support is
implemented)
• G.811
• SSU-A
• SSU-B
• G.813/8262 - default
• DO NOT USE
• Failure (cannot be configured by user)
Page 197 of 322

6.4.3.4 Native Sync Distribution Examples

The figure below provides a Native Sync Distribution mode usage example in
which synchronization is provided to all-frame Node-Bs using SyncE. In this
illustration, an IP-20G at a fiber node is synchronized to:
• SyncE input from an Ethernet uplink
• External synchronization input via an E1 interface
Ethernet
Node-B
Services
Eth.
Sync
IP-20G
Node-B
Eth.
Sync
Sync Input
IP-20G
GPS/SSU
IP-20G
Node-B Eth
(with SyncE)
Native
sync distribution
Eth.
Sync
IP-20G
RNC or
Aggregation
switch/router
IP-20G at fiber node synchronized to:
Distributed clock is provided to Node-B • SyncE input from Ethernet uplink
using SyncE or dedicated Sync interface. • External Sync Input (From GPS, SSU, etc.)
Figure 95: Native Sync Distribution Mode Usage Example

The following figure illustrates Native Sync Distribution in a tree scenario.
IP-20G with SyncE and Native

Sync Distribution support.
IP-20G
Packet Based
Aggregation
Network
MW Radio link

PRC
BNC/RNC
FE/GE interface with SyncE
IP-20G
Tail Site #3 Aggregation Site Fiber Site
Figure 96: Native Sync Distribution Mode – Tree Scenario
Page 198 of 322

The following figure illustrates Native Sync Distribution in a ring scenario, during
normal operation.
PRC
IP-20G
Tail site #1 Packet Based

Aggregation
Network
IP-20G
IP-20G
Tail site #2 Ring site #1
Wireless
Carrier Ethernet Ring BNC/RNC
IP-20G
Fiber site
2
Native
1+0
IP-20G FE/GE interface
with SyncE
Ring site #2
IP-20G
Ring site #3
IP-20G
Tail site #3
Native Sync Distribution Mode – Ring Scenario (Normal Operation)

The following figure illustrates Native Sync Distribution in a ring scenario, where a
link has failed and the Native Sync timing distribution has been restored over an
alternate path by using SSM messages.
IP-20G
Tail site #1 Packet Based

Aggregation
Network
IP-20G
IP-20G
Tail site #2 Ring site #1
Wireless
Carrier Ethernet Ring IP-20G BNC/RNC
Fiber site PRC

Native2
1+0
IP-20G FE/GE interface
with SyncE
Ring site #2
Alternate path using IP-20G
SSM messages
Ring site #3
IP-20G
Tail site #3
Figure 97: Native Sync Distribution Mode – Ring Scenario (Link Failure)
Page 199 of 322

6.4.4 SyncE PRC Pipe Regenerator Mode

Note: SyncE PRC Pipe Regenerator Mode is planned for future release.
Synchronous Ethernet (SyncE) is standardized in ITU-T G.8261 and G.8262, and
refers to a method whereby the frequency is delivered on the physical layer.
SyncE delivers a frequency reference, but not ToD or phase synchronization. It is
used to distribute timing to applications that rely on precise frequency
synchronization, such as wireless backhaul.
SyncE is based on SDH/TDM timing, with similar performance, and does not
change the basic Ethernet standards. The SyncE technique supports synchronized
Ethernet outputs as the timing source to an all-IP BTS/NodeB. This method offers
the same synchronization quality provided over E1 interfaces to legacy
BTS/NodeB. SyncE is not affected by Path Delay Variation (PDV) and Packet Jitter,
which are inherent in Ethernet networks.
The primary disadvantage of SyncE is that it since it is a physical-layer technology,
it cannot be deployed in legacy Ethernet networks without upgrade of all
hardware and interfaces in the network, since synchronous timing circuitry is
necessary at every node.
Figure 98: Synchronous Ethernet (SyncE)

In SyncE PRC pipe regenerator mode, frequency is transported between two GbE
interfaces through the radio link.
PRC pipe regenerator mode makes use of the fact that the system is acting as a
simple link (so no distribution mechanism is necessary) in order to achieve the
following:
• Improved frequency distribution performance, with PRC quality.
• Simplified configuration
Page 200 of 322

In PRC pipe regenerator mode, frequency is taken from the incoming GbE
Ethernet or radio interface signal, and used as a reference for the radio frame. On
the receiver side, the radio frame frequency is used as the reference signal for the
outgoing Ethernet PHY.
Frequency distribution behaves in a different way for optical and electrical GbE
interfaces, because of the way these interfaces are implemented:
• For optical interfaces, separate and independent frequencies are transported
in each direction.
• For electrical interfaces, each PHY must act either as clock master or as clock
slave in its own link. For this reason, frequency can only be distributed in one
direction, determined by the user.
6.4.5 IEEE-1588v2 PTP Optimized Transport

Precision Timing Protocol (PTP) refers to the distribution of frequency and phase
information across a packet-switched network.
IP-20G supports IEEE-1588v2 PTP optimized transport, a message-based protocol
that can be implemented across packet-based networks. IEEE-1588v2 provides
phase synchronization, and is designed to provide higher accuracy and precision,
to the scale of nanoseconds.
IEEE-1588v2 PTP synchronization is based on a master-slave architecture in which
the master and slave exchange PTP packets carrying clock information. The
master is connected to a reference clock, and the slave synchronizes itself to the
master.
Sync GPS/SSU
Input
Packet Switched Network

Master Slave
Figure 99: IEEE-1588v2 PTP Optimized Transport – General Architecture

Accurate synchronization requires a determination of the propagation delay for
PTP packets. Propagation delay is determined by a series of messages between
the master and slave.
Page 201 of 322

Sync GPS/
SSU
Input
Packet Switched Network

Master Slave
t1
Syn c
(t1)
Follow
-up (t t2
1)
t3
reque st (t3)
Delay_
t4
Delay
_resp
o n se
(t4)
Figure 100: Calculating the Propagation Delay for PTP Packets

In this information exchange:
1 The master sends a Sync message to the slave and notes the time (t1) the
message was sent.
2 The slave receives the Sync message and notes the time the message was
received (t2).
3 The master conveys the t1 timestamp to the slave, in one of the following
ways:
One-Step – Embedding the t1 timestamp in the Sync message.
Two-Step – Embedding the t1 timestamp in a Follow-up message.
4 The slave sends a Delay_request message to the master and notes the time
the message was sent (t3).
5 The master receives the Delay_request message and notes the time the
message was received (t4).
6 The master conveys the t4 timestamp to the slave by embedding the t4
timestamp in a Delay_response message.
Based on this message exchange, the protocol calculates both the clock offset
between the master and slave and the propagation delay, based on the following
formulas:
Page 202 of 322

Offset = [(t2 – t1) – (t4 – t3)]/2

Propagation Delay = [(t2 – t1) + (t4 – t3)]/2
The calculation is based on the assumption that packet delay is constant and that
delays are the same in each direction. For information on the factors that may
undermine these assumptions and how IP-20G’s IEEE-1588v2 implementations
mitigate these factors, see Mitigating PDV on page 203.
6.4.5.1 IEEE-1588v2 Characteristics

IEEE-1588v2 provides packet-based synchronization that can transmit both
frequency accuracy and phase information. This is essential for LTE applications,
and adds the ability to transmit phase information to SyncE.
The main IEEE-1588v2 benefits include:
• Nanosecond precession.
• Meets strict LTE-A requirements for rigorous frequency and phase timing.
• Hardware time stamping of PTP packets.
• Standard protocol compatible with third-party equipment.
• Short frame and higher message rates.
• Supports unicast as well as multicast.
• Enables smooth transition from unsupported networks.
• Mitigates PDV issues by using Transparent Clock and Boundary Clock (see
Mitigating PDV on page 203).
• Minimal consumption of bandwidth and processing power.
• Simple configuration.
6.4.5.2 Mitigating PDV

To get the most out of PTP and minimize PDV, IP-20G supports Transparent Clock
and Boundary Clock.
PTP calculates path delay based on the assumption that packet delay is constant
and that delays are the same in each direction. Delay variation invalidates this
assumption. High PDV in wireless transport for synchronization over packet
protocols, such as IEEE-1588, can dramatically affect the quality of the recovered
clock. Slow variations are the most harmful, since in most cases it is more difficult
for the receiver to average out such variations.
PDV can arise from both packet processing delay variation and radio link delay
variation.
Packet processing delay variation can be caused by:
• Queuing Delay – Delay associated with incoming and outgoing packet buffer
queuing.
• Head of Line Blocking – Occurs when a high priority frame, such as a frame
that contains IEEE-1588 information, is forced to wait until a lower-priority
frame that has already started to be transmitted completes its transmission.
Page 203 of 322

• Store and Forward – Used to determine where to send individual packets.

Incoming packets are stored in local memory while the MAC address table is
searched and the packet’s cyclic redundancy field is checked before the packet
is sent out on the appropriate port. This process introduces variations in the
time latency of packet forwarding due to packet size, flow control, MAC
address table searches, and CRC calculations.
Radio link delay variation is caused by the effect of ACM, which enables dynamic
modulation changes to accommodate radio path fading, typically due to weather
changes. Lowering modulation reduces link capacity, causing traffic to accumulate
in the buffers and producing transmission delay.
Note: When bandwidth is reduced due to lowering of the ACM
modulation point, it is essential that high priority traffic carrying
IEEE-1588 packets be given the highest priority using IP-20G’s
enhanced QoS mechanism, so that this traffic will not be subject
to delays or discards.
These factors can combine to produce a minimum and maximum delay, as
follows:
• Minimum frame delay can occur when the link operates at a high modulation
and no other frame has started transmission when the IEEE-1588 frame is
ready for transmission.
• Maximum frame delay can occur when the link is operating at QPSK
modulation and a large (e.g., 1518 bytes) frame has just started transmission
when the IEEE-1588 frame is ready for transmission.
The worst case PDV is defined as the greatest difference between the minimum
and maximum frame delays. The worst case can occur not just in the radio
equipment itself but in every switch across the network.
To ensure minimal packet delay variation (PDV), IP-20G’s synchronization solution
includes 1588v2-compliant Transparent Clock and Boundary Clock synchronization
protocols. The following two sections describe these protocols and how they
counter PDV.
Page 204 of 322

6.4.5.3 Transparent Clock

IP-20G supports end-to-end Transparent Clock, which updates the correction field
for the delay associated with individual packet transfers. End-to-End Transparent
Clock is the most appropriate option for microwave radio links.
A Transparent Clock node resides between a master and a slave node, and
updates the packets passing between the master and slave to compensate for
delay, enabling the terminating clock in the slave node to remove the delay
accrued in the Transparent Clock node. The Transparent Clock node is itself
neither a master nor a slave node, but rather, serves as a bridge between master
and slave nodes.
Entrance Leaving Time
Time (Update Timestamp)
Sync GPS/SSU
Input
Transparent
Clock
Slave
Master
Leaving Time Entrance

(Update Timestamp) Time
Figure 101: Transparent Clock – General Architecture

IP-20G uses 1588v2-compliant Transparent Clock to counter the effects of
asymmetrical delay and delay variation. Transparent Clock measures and adjusts
for delay variation, enabling the IP-20G to guarantee ultra-low PDV.
The Transparent Clock algorithm forwards and adjusts the messages to reflect the
residency time associated with the Sync and Delay_Request messages as they
pass through the device. The delays are inserted in the 64-bit time-interval
correction field.
As shown in the figure below, IP-20G measures and updates PTP messages based
on both the radio link delay, and the packet processing delay that results from the
network processor (switch operation).
Page 205 of 322

Radio Link
Delay = ∆y
Correction Time
∆x + ∆y + ∆z
1588 1588
Master Slave
IP-20G IP-20G
Packet Processing Packet Processing

Delay = ∆z Delay = ∆x
Figure 102: Transparent Clock Delay Compensation
6.4.5.4 Boundary Clock

IEEE-1588v2 Boundary Clock enables the IP-20G to regenerate phase
synchronization via standard Ethernet. Boundary Clock complies with ITU-T
Telecom Profile G.8275.1. This enables IP-20G, with Boundary Clock, to meet the
rigorous synchronization requirements of LTE-Advanced (LTE-A) networks.
The Boundary Clock in IP-20 supports up to four 1588 slave clock devices.
The Boundary Clock terminates the PTP flow it receives on the slave port, recovers
the time and phase, and regenerates the PTP flow on the master ports.
The Boundary Clock node selects the best synchronization source available in the
domain and regenerates PTP towards the slave clocks. This reduces the processing
load from grandmaster clocks and increases the scalability of the synchronization
network, while rigorously maintaining timing accuracy.
Page 206 of 322

1588
Master
Slave 1588
Port Slave
IP-20G IP-20G
Slave Master Master

Port Port Port
Figure 103: Figure 104: Boundary Clock – General Architecture

Boundary Clock uses the Best Master Clock Algorithm (BMCA) to determine which
of the clocks in the network has the highest quality. This clock is designated the
grandmaster, and it synchronizes all other clocks (slave clocks) in the network. If
the grandmaster is removed from the network, or the BMCA determines that
another clock has superior quality, the BMCA defines a new grandmaster and
adjusts all other clocks accordingly. This process is fault tolerant, and no user
input is required.
A node running as master clock can use the following inputs and outputs. A node
can use a combined mode of SyncE for frequency and 1pps for phase. In this case,
SyncE provides an additional reference for the best possible result.
Table 35: Boundary Clock Input Options

Synchronization Input Frequency/Phase
Ethernet packets from PTP 1588 Remote Phase

Master via radio or Ethernet interface
SyncE (including ESMC) via radio or Frequency
Ethernet interface
Table 36: Boundary Clock Output Options

Synchronization Input Frequency/Phase
Ethernet packets towards PTP 1588 Phase

slaves via radio or Ethernet interface
SyncE (including ESMC) via radio or Frequency
Ethernet interface
IP-20G uses multicast Ethernet messages, per IEEE-1588 Annex F.

Boundary Clock is only supported with the IP-20G hardware version listed in Table 37.
Table 37: IP-20G Model Supporting 1588 Boundary Clock

Marketing Model Marketing Description
IP-20G-M2-E6-T16-C-2DC+SM IP-20G-M2-E6-T16-C-2DC, w/ SM-Card
Page 207 of 322

6.5 TDM Services

IP-20G provides integrated support for transportation of TDM (E1) services with
optional integrated E1 interfaces.
Two types of TDM services are supported using the same hardware:
• Native TDM trails
• TDM Pseudowire services (enabling interoperability with third party
packet/PW equipment)
In addition, IP-20G offers hybrid Ethernet and TDM services. Hybrid services can
utilize either Native TDM or pseudowire.
Services engine
TDM cross-connect (VCs)
E1 TDM
Traffic
Hybrid
TDM Radio
PW
Network processor (EVCs)
Packet
Traffic
GE/FE
Figure 105: Hybrid Ethernet and TDM Services

Hybrid Ethernet and TDM services can also be transported via cascading
interfaces. This enables the creation of links among multiple IP-20G and IP-20N
units in a node for multi-carrier and multi-directional applications.
TDM cross-connect
- (VCs)
SAP
Cascading Port TDM
Traffic
Hybrid
Port Radio
Packet
Traffic
Ethernet Services (EVCs)
SNP SNP
SAP
E1 Port SAP
Cascading Port
Port
User Port Ethernet Services (EVCs)

(UNI)
GE/FE Port SAP

SAP SNP
SAP
Figure 106: Hybrid Ethernet and TDM Services Carried Over Cascading Interfaces
Page 208 of 322

6.5.1 Native TDM Trails

IP-20G provides native TDM support, utilizing a cross-connect module to support
up to 256 TDM trails.
IP-20G also supports hybrid Ethernet and native TDM services, utilizing cascading
ports. The following figure shows an example of a hybrid service package that
includes a Point-to-Point and a Multipoint Ethernet service, along with a TDM trail
utilizing virtual connections (VCs) via IP-20G’s cross-connect.
E1 Port SAP
User Port PtP Service

(UNI) TDM
Traffic Hybrid
GE/FE Port SAP SNP Radio
SAP SAP Packet
Traffic
Multipoint Service
User Port SAP SNP Network

(UNI) Port
GE/FE Port Port GE/FE
SAP SNP
Figure 107: Hybrid Ethernet and Native TDM Services
6.5.1.1 Native TDM Trails Provisioning

The IP-20G Web EMS provides a simple and easy-to-use GUI that enables users to
provision end-to-end TDM trails. The Services Provisioning GUI includes the
following trail-creation end points:
• TDM interface
• Radio interface
• Cascading interface
Page 209 of 322

6.5.1.2 TDM Trails and Synchronization
Related topics:
• Synchronization
Synchronization for TDM trails can be provided by any of the following
synchronization methods:
• Loop Timing – Timing is taken from incoming traffic.
• Recovered Clock– Clock information is recovered on the egress path. Extra
information may be located in an RTP header that can be used to correct
frequency offsets. Recovered Clock can provide very accurate synchronization,
but requires low PDV.
• System Reference Clock –Trails are synchronized to the system reference
clock.
6.5.1.3 TDM Path Protection

TDM path protection enables the operator to define two separate network paths
for a single TDM service. Two different kinds of path protection are available, each
suitable for a different network topology:
• 1:1 TDM path protection is suitable for ring networks that consist entirely of
IP-20G and/or IP-20N elements with two end-point interfaces for the TDM
service.
• 1+1 TDM path protection is suitable for dual homing topologies in which the
IP-20G and/or IP-20N elements are set up as a chain connected to the third
party networks at two different sites. The ring is closed on one side by the IP-
20G or IP-20N and on the other by third party equipment supporting standard
SNCP. In this case, there are three end-point interfaces in the IP-20G or IP-20N
section of the network.
Page 210 of 322

Third Party
Equipment
End-Point
Interface
Path 2
IP-20G
Path 1
IP-20G IP-20G
End-Point IP-20G
Interface
Third Party
Equipment
Figure 108: 1:1 TDM Path Protection – Ring Topology
End-Point
Interface
Third Party
SNCP Equipment SNCP
Path 1 Path 2
Third Party
Equipment
Third Party Third Party
Equipment
TDM Network
Network
Interface 1
Network
Interface 2
IP-20G IP-20G
Path 1 Path 2
End-Point IP-20G
Interface
Third Party
Equipment
Figure 109: 1+1 TDM Path Protection – Dual Homing Topology
Page 211 of 322

1:1 TDM Path Protection

1:1 TDM path protection enables the operator to define two separate network
paths for a single TDM service. Each path has the same TDM interface end points,
but traffic flows to the destination via different paths. Bandwidth is utilized only
on the active path, freeing up resources on the standby path.
TDM path protection is implemented by means of configuring active and backup
path at the TDM service end-points.
1:1 TDM path protection can be configured to operate in revertive mode. In
revertive mode, the system monitors the availability of the protected path at all
times. After switchover to the protecting path, once the protected path is
operational and available without any alarms, the system waits the user-
configured Wait to Restore (WTR) time and then, if the protected path remains
operational and available, initiates a revertive protection switch. A single WTR
time is configured for all the TDM trails in the system.
1+1 TDM Path Protection

1+1 TDM path protection is used for dual homing topologies in which the IP-20G
or IP-20N network elements are set up as a chain connected to third party
networks at two different sites, where one end-point is located on an IP-20G or
IP-20N unit and the other end-point is located on third-party equipment
supporting standard SNCP.
As with 1:1 TDM path protection, the operator defines two separate network
paths for a single TDM service. However, unlike 1:1 TDM path protection, traffic
flows through both paths simultaneously, thereby supporting interoperability with
standard SNCP in the third party equipment.
6.5.1.4 TDM Performance Monitoring

The following monitoring features are available for TDM services and interfaces:
PMs are computed at the TDM card and reported at 15-minute intervals, with one
second granularity.
• PMs for the outgoing TDM trail:
◦ Errored seconds
◦ Severely errored seconds
◦ Unavailable seconds
• PMs for incoming native E1 signal:
◦ Errored seconds
Page 212 of 322

6.5.2 TDM Pseudowire

IP-20G’s TDM Pseudowire provides TDM-over-packet capabilities by means of an
optional, integrated E1 interface that processes TDM data, sends the data through
the system in frame format that can be processed by the IP-20G’s Ethernet ports,
and converts the data back to TDM format.
IP-20G also supports all-packet Ethernet and TDM pseudowire services. The
following figure shows an example of an all-packet service package that includes
two Point-to-Point services and one Multipoint Ethernet service, where the first
Point-to-Point service carries E1 pseudowire traffic. This service package can be
carried on any of the IP-20G’s Ethernet ports.

TDM
PtP Service
PW
E1 Port SAP SNP

SAP SAP
User Port PtP Service

(UNI)
S- VLAN =
200 Packet Packet
GE/FE Port SAP SNP Traffic
SAP SAP Radio
Multipoint
Service
User Port SAP SNP Network
(UNI) Port
GE/FE Port Port GE/FE
SAP SNP
Figure 110: All-Packet Ethernet and TDM Pseudowire Services
6.5.2.1 TDM Pseudowire Supported Standards

TDM Pseudowire supports the following standards:
• SAToP – RFC 4553
• CESoP – RFC 508625
TDM Pseudowire is compliant with the following encapsulations:
• Ethernet VLAN (MEF-8)
• IP/UDP (IETF)26
• MPLS (MFA8) 27
25
CESoP mode is planned for future release.
26
IP/UDP (IETF) encapsulation is planned for future release.
27
MPLS (MFA8) encapsulation is planned for future release.
Page 213 of 322

6.5.2.2 TDM Pseudowire Services

A Pseudowire service is a user-defined, bidirectional flow of information between
a TDM signal and a packed flow, which is always transported over Layer 2
Ethernet. Such a service interconnects and makes use of the following elements:
• TDM Signal
◦ The TDM signal may be an entire E1 or a subset of DS0s (or E1 time-
slots).28
• PSN Tunnel
◦ A PSN tunnel is the means by which the frames containing the TDM
information are sent and received through a PSN network. The type of
tunnel to be used should match the relevant transport network.
◦ Three types of PSN tunnels are supported: MEF-8 (Ethernet), UDP/IP, and
MPLS (MFA8).
• For IP tunnels, the pseudowire services make use of the TDM card’s
IP address, which is user-configurable. For MEF-8 tunnels, the addressing is
done through the TDM card’s MAC address, which is fixed, but readable by
users. For a fixed E1 interface, the MAC address is fixed per unit. PSN Tunnel
Group
◦ A PSN tunnel group is a grouping of two TDM tunnels, one of which will
carry the pseudowire service frames at any given time.
◦ A PSN tunnel group is used when path protection is required for a
pseudowire service.
◦ One of the tunnels is designated as “primary.” The primary tunnel carries
the pseudowire frames in the absence of any failures. The other tunnel is
designated as “secondary.” The secondary tunnel is used whenever the
primary path fails.
• Pseudowire Profile
◦ A profile is a set of parameters that determine various operational settings
of a PW service. A single profile can be used for any number of services.
◦ The following is a short explanation of the main parameters:
◦ Payload size – In terms of E1 frames per frame.
◦ Jitter buffer – In milliseconds.
◦ LOPS detection thresholds.
◦ RTP timestamp usage details (for adaptive clock recovery).
◦ Payload suppression and transmission patterns in case of errors.
28
A subset of DS0 is supported in CESoP, which is planned for a future release.
Page 214 of 322

In addition, there are a number of parameters at the PW Card level that must be
configured properly to ensure proper operation:
• Ethernet traffic port settings
◦ Speed
◦ Duplex
◦ Auto-negotiation
◦ Flow control
• TDM card IP address and subnet mask
• Clock distribution
6.5.2.3 Pseudowire Services Provisioning

The IP-20G Web EMS provides a simple and easy-to-use GUI that enables users to
provision end-to-end pseudowire services. The Services Provisioning GUI includes
the following service-creation end points:
• TDM interface
• Radio interface
• Cascading interface
6.5.2.4 TDM Pseudowire and Synchronization
Related topics:
• Synchronization
A key requirement of pseudowire technology is managing the synchronization of
TDM signals. IP-20G’s TDM Pseudowire supports the following synchronization
methods:
• Absolute Reference Clock (Common Clock) – All E1 lines are synchronized to
the system reference clock.
• Adaptive Clock Recovery – Clock information is included in the frames that
contain the TDM data. Extra information may be located in an RTP header that
can be used to correct frequency offsets. The clock information is extracted at
the point where the frames are received and reconverted to TDM. The
extracted clock information is used for the reconversion to TDM. Adaptive
Clock Recovery can provide very accurate synchronization, but requires low
PDV.
• Differential Clock Recovery – A single common clock is given, while each E1
line has its independent clock referenced to this common clock. 29
• Loop Timing – The pseudowire output signal uses the clock of the incoming E1
lines Timing will be independent for each E1 line.
29
Differential Clock Recovery is planned for future release.
Page 215 of 322

6.5.2.5 TDM Pseudowire Path Protection

For TDM pseudowire traffic redundancy, IP-20G offers 1:1 TDM path protection,
which protects the traffic along the path.
Note: Alternatively, protection for the traffic along the path can be
achieved using 1+1HSB protection for the radios.
1:1 TDM Path protection requires the use of SOAM (FM) at both end-point
interfaces. The TDM module sends two data streams to the CPU. Only the data
stream for the active path contains actual traffic. Both data streams contain
continuity messages (CCMs). This enables the TDM module to monitor the status
of both paths without doubling the amount of data being sent over the network.
The TDM module determines when a switchover is necessary based on the
monitored network status.
In order to achieve TDM Pseudowire path protection, different provisioning
should be made for the Ethernet service corresponding to each of the two data
streams. In order to do this, it is recommended to map the corresponding
Ethernet services to MSTP instance number 63, which is meant for Traffic
Engineering (ports are always forwarding) and to map the two different transport
VLANs over two different paths.
1:1 TDM pseudowire path protection uses SOAM to monitor the network paths.
Because SOAM is configured on the TDM module level, the TDM module can
determine the status of the entire network path, up to and including the card’s
TDM interface.
6.5.2.6 TDM Pseudowire Performance Monitoring

The following monitoring features are available for TDM Pseudowire services and
interfaces:
TDM Pseudowire PMs

Standard PM measurements are provided for each configured service:
• Number of frames transmitted
• Number of frames received
• Number of lost frames detected
• Number of frames received out-of-sequence but successfully reordered
• Number of transitions from normal state to LOPS (loss of frame state)
• Number of malformed frames received
• Number of frames dropped because the receive buffer exceeded the
maximum allowed depth (jitter overruns)
• Maximum deviation from the middle of the jitter buffer (maximum jitter
buffer deviation)
• Minimum jitter buffer usage registered during the prior one second (current
minimum jitter buffer count)
• Maximum jitter buffer usage registered during the prior one second (current
maximum jitter buffer count)
Page 216 of 322

TDM Pseudowire Signal PMs30

PMs are computed at the PW module and reported at 15-minute intervals, with
one second granularity.
• PMs for the recovered E1:
◦ Errored seconds
• PMs for the pseudowire Ethernet connection:
◦ Frame Error Ratio (FER) performance
• RFC 5604 PMs:
◦ Lost frames
◦ Reordered frames
◦ Buffer underruns
◦ Misordered frames dropped
◦ Malformed frames
• PMs for incoming native E1 signal:
◦ Errored seconds
30
Support for TDM signal PMs is planned for future release.
Page 217 of 322

6.5.3 TDM Reference Solutions

This section provides several examples of how IP-20G’s end-to-end TDM service
solutions can be used in various migration scenarios.
Native TDM Trail
Native E1 Trail (VC12)
Hybrid Hybrid
Radio Radio
SDH Optical
Aggregation
Network
FibeAir IP-20 FibeAir IP-20 FibeAir IP-20
BNC/RNC
Figure 111: Native TDM Trail Interoperability with Optical SDH Equipment
Aggregation
Native TDM Trail TDM PW
Hybrid Hybrid
Radio Radio
Fiber Packet
Aggregation
Network
FibeAir IP-10/20 FibeAir IP-20 FibeAir IP-20
BNC/RNC
Figure 112: Native TDM Trail Interoperability with TDM Pseudowire-over-Packet

Native E1 Trail (VC12)
TDM Pseudowire
All-Packet All-Packet
Radio Radio
SDH Optical
Aggregation
Network
BNC/RNC
Figure 113: TDM Pseudowire Interoperability with Optical SDH Equipment
Page 218 of 322

TDM Pseudowire
All-Packet All-Packet
Radio Radio
Fiber Packet
Aggregation
Network
BNC/RNC
Figure 114: TDM Pseudowire Interoperability with Third-Party Packet Aggregation

Equipment
Page 219 of 322

6.6 Radio Payload Encryption and FIPS
6.6.1 AES-256 Payload Encryption

IP-20G supports AES-256 payload encryption.
The Advanced Encryption Standard (AES) is defined in Federal Information
Processing Standard Publication 197 (FIPS 197) for symmetric encryption. AES-256
is widely considered to be secure and efficient and is therefore broadly accepted
as the standard for both government and industry applications.
AES-256 Encrypted Link
Encryption Module in IDU
Figure 115: AES-256 Encrypted Link

Note: The AES-256 payload encryption feature is a controlled item
under applicable Export Laws. Please contact your Ceragon
representative to confirm that the encryption feature can be
delivered.
6.6.1.1 AES Benefits

• Provides protection against eavesdropping and man-in-the-middle attacks on
the radio
• Full encryption for all radio traffic
• Wire-speed, lowest latency encryption
• Eliminates the need for external encryption devices:
◦ Cost effective encryption solution
◦ Low Capex and operational costs; fast and simple deployment
Page 220 of 322

6.6.1.2 IP-20G AES Implementation

In IP-20G, AES provides full payload encryption for all L1 radio traffic. It also
encrypts control data passing through the radio link, such as the Link ID, ATPC
data, and SSM messages. AES encryption operates on a point-to-point radio link
level. AES is enabled and configured separately for each radio carrier.
IP-20G uses a dual-key encryption mechanism for AES.
• The user provides a master key. The master key can also be generated by the
system upon user command. The master key is a 32-byte symmetric
encryption key. The same master key must be manually configured on both
ends of the encrypted link.
• The session key is a 32-byte symmetric encryption key used to encrypt the
actual data. Each link uses two session keys, one for each direction. For each
direction, the session key is generated by the transmit side unit and
propagated automatically to the other side of the link via a Key Exchange
Protocol. The Key Exchange Protocol exchanges session keys by encrypting
them with the master key, using the AES-256 encryption algorithm. Session
keys are regenerated at user-configured intervals.
The first KEP exchange that takes place after a new master key is configured
causes traffic to be blocked for up to one minute, until the Crypto Validation State
becomes Valid. Subsequent KEP exchanges that take place when a session key
expires do not affect traffic. KEP exchanges have no effect upon ACM, RSL, and
MSE.
Once AES encryption has been enabled on both sides of the link, the Key Exchange
Protocol periodically verifies that both ends of the link have the same master key.
If a mismatch is detected, an alarm is raised and traffic transmission is stopped for
the mismatched carrier at both sides of the link. The link becomes non-valid and
traffic stops being forwarded.
6.6.1.3 AES Interoperability

IP-20’s AES implementation is interoperable among IP-20 products that support
AES. This means that for all IP-20 products that are otherwise interoperable with
each other, AES can be used in links between two such products.
Page 221 of 322

6.6.2 FIPS 140-2 Compliance

FibeAir IP-20G can be configured to be FIPS 140-2 level-2 compliant, in specific
hardware and software configurations, as described in this section. FIPS is only
available with the FibeAir IP-20 Assured platform.
Note: CeraOS 11.1 cannot be used in FibeAir IP-20 Assured platforms.
For FibeAir IP-20 Assured, use CeraOS 10.9.6 or CeraOS 8.3.
6.6.2.1 FIPS Overview

The objective of FIPS 140-2 is to provide a standard for secured communication
devices, with an emphasis on encryption and cryptographic methods. The FIPS
standards are promulgated by the National Institute of Standards and Technology
(NIST), and provide an extensive set of requirements for both hardware and
software. For a full list of FIPS requirements, refer to the Ceragon IP-20 FIPS 140-2
Security Policy, available upon request.
It is the responsibility of the user to ensure that the above FIPS requirements are
met.
6.6.2.2 Hardware Requirements

For an IP-20G node to be FIPS-compliant, the chassis must be FIPS-compliant. A
FIPS-compliant IP-20G chassis has a unique part number ending in the letters AF,
as shown in the following table:
FIPS-Compliant Marketing Model

IP-20G-M2-E6-T16-C-2DC+SM-AF IP-20G-M2-E6-T16-C-2DC, w/ SM-Card, FIPS
Special labels must be affixed to a FIPS-compliant IP-20G unit. These labels are
tamper-evident and must be applied in such a way that it is not possible to open
the chassis without also removing a label and leaving evidence that the label was
tampered with. These labels must be replaced whenever components are added
to or removed from the unit. Replacement labels can be ordered from Ceragon
Networks, part number BS-0341-2. Tamper-evident labels should be inspected for
integrity at least once every six months.
6.6.2.3 Software Requirements

FIPS compliance requires the user to operate the IP-20G in FIPS mode. FIPS mode
must be enabled by the user. It can be enabled via the Web EMS, the CLI, or
SNMPv3. Enabling FIPS mode requires a system reset.
Page 222 of 322

6.6.2.4 Encrypting an External Protection Link

For unit redundancy configurations, the external protection link must be
encrypted using IPsec. This encrypts all IP packets that pass between the
management ports of the two IP-20 units.
IPsec uses a 32-character pre-shared key. The pre-shared key is a 32-byte
symmetric encryption key. The same pre-shared key must be configured on both
ends of the encrypted link.
IPsec encryption is automatically enabled when FIPS mode is enabled. However, it
is enabled with a default value: protectionpresharedkey0123456789.
If this default value is not changed, the following alarm is triggered:
• 5113 – Protection Pre-Shared-Key has the default value
Page 223 of 322

7. FibeAir IP-20G Management

• Management Overview
• Automatic Network Topology Discovery with LLDP Protocol
• Management Communication Channels and Protocols
• Web-Based Element Management System (Web EMS)
• SDN Support
• Command Line Interface (CLI)
• Configuration Management
• Software Management
• CeraPlan Service for Creating Pre-Defined Configuration Files
• IPv6 Support
• In-Band Management
• Local Management
• Alarms
• External Alarms
• NTP Support
• UTC Support
• System Security Features
Page 224 of 322

7.1 Management Overview

The Ceragon management solution is built on several layers of management:
• EMS – HTTP web-based EMS
• NEL – Network Element-level CLI
• SDN – Software-Defined Networking, including NETCONF/YANG
• NMS and SML –PolyView/NetMaster platform
Every FibeAir IP-10 and IP-20 network element includes an HTTP web-based
element manager that enables the operator to perform element configuration,
performance monitoring, remote diagnostics, alarm reports, and more.
IP-20 devices support SDN, enabling customers to manage, configure, and
monitor network elements within the paradigm of SDN network architecture
using Ceragon’s SDN Master controller.
In addition, Ceragon provides an SNMP v1/v2c/v3 northbound interface on the IP-
20G.
Ceragon offers the NetMaster network management system (NMS), which
provides centralized operation and maintenance capability for the complete range
of network elements in an IP-20G system. IP-20G and other Ceragon network
elements can also be managed via Ceragon’s PolyView NMS. To facilitate
automated network topology discovery via NMS, IP-20G supports the Link Layer
Discovery Protocol (LLDP).
In addition, management, configuration, and maintenance tasks can be
performed directly via the IP-20G Command Line Interface (CLI). The CLI can be
used to perform configuration operations for IP-20G units, as well as to configure
several IP-20G units in a single batch command.
Page 225 of 322

Northbound OSS/NMS
SNMP
NetAct
CLI Interface
NMS
Client NMS
TCP, Secured
SSL Channel Platform
REST
Over
HTTP
Web EMS
SNMP
HTTP/HTTPS HTTP/HTTPS
FTP/SFTP FTP/SFTP
CLI
HTTP
IP-20G
Craft
Figure 116: Integrated IP-20G Management Tools
Page 226 of 322

7.2 Automatic Network Topology Discovery with LLDP Protocol

FibeAir IP-20G supports the Link Layer Discovery Protocol (LLDP), a vendor-neutral
layer 2 protocol that can be used by a station attached to a specific LAN segment
to advertise its identity and capabilities and to receive identity and capacity
information from physically adjacent layer 2 peers. IP-20G’s LLDP implementation
is based on the IEEE 802.1AB – 2009 standard.
LLDP provides automatic network connectivity discovery by means of a port
identity information exchange between each port and its peer. The port
exchanges information with its peer and advertises this information to the NMS
managing the unit. This enables the NMS to quickly identify changes to the
network topology.
Enabling LLDP on IP-20 units enables the NMS to:
• Automatically detect the IP-20 unit neighboring the managed IP-20 unit, and
determine the connectivity state between the two units.
• Automatically detect a third-party switch or router neighboring the managed
IP-20 unit, and determine the connectivity state between the IP-20 unit and
the switch or router.
Page 227 of 322

7.3 Management Communication Channels and Protocols

Related Topics:
• Secure Communication Channels
Network Elements can be accessed locally via serial or Ethernet management
interfaces, or remotely through the standard Ethernet LAN. The application layer
is indifferent to the access channel used.
The NMS can be accessed through its GUI interface application, which may run
locally or in a separate platform; it also has an SNMP-based northbound interface
to communicate with other management systems.
Table 38: Dedicated Management Ports

Port number Protocol Frame structure Details
161 SNMP UDP Sends SNMP Requests to the network elements

162 Configurable SNMP (traps) UDP Sends SNMP traps forwarding (optional)
80 HTTP TCP Manages devices
443 HTTPS TCP Manages devices (optional)
From port 21 (default) to FTP Control TCP Downloads software and configuration files,
any remote port (>1023). Port uploads security and configuration logs, and unit
Initial port (21) is info files.
configurable. (FTP Server responds to client's control port)
(optional)
From Any port (>1023) to FTP Data Port TCP Downloads software and configuration files,
any remote port (>1023) uploads security and configuration logs, and unit
info files.
The FTP server sends ACKs (and data) to client's
data port.
From port 22 (default) to SFTP Control TCP Downloads software and configuration files, and
any remote port (>1023). Port CSR certificates, uploads security and configuration
Initial port (22) is logs, and unit info files.
configurable. (SFTP Server responds to client's control port)
(optional)
From Any port (>1023) to SFTP Data TCP Downloads software and configuration files, and
any remote port (>1023) Port CSR certificates, uploads security and configuration
logs, and unit info files.
The SFTP server sends ACKs (and data) to client's
data port.
23 telnet TCP Remote CLI access (optional)
22 SSH TCP Secure remote CLI access (optional)
All remote system management is carried out through standard IP

communications. Each NE behaves as a host with a single IP address.
Page 228 of 322

The communications protocol used depends on the management channel being

accessed.
As a baseline, these are the protocols in use:
• Standard HTTP for web-based management
• Standard telnet for CLI-based management
Page 229 of 322

7.4 Web-Based Element Management System (Web EMS)

The IP-20G Element Management System (Web EMS) is an HTTP web-based
element manager that enables the operator to perform configuration operations
and obtain statistical and performance information related to the system,
including:
• Configuration Management – Enables you to view and define configuration
data for the IP-20G system.
• Fault Monitoring – Enables you to view active alarms.
• Performance Monitoring – Enables you to view and clear performance
monitoring values and counters.
• Diagnostics and Maintenance – Enables you to define and perform loopback
tests, software updates, and IDU-RFU interface monitoring.
• Security Configuration – Enables you to configure IP-20G security features.
• User Management – Enables you to define users and user profiles.
A Web-Based EMS connection to the IP-20G can be opened using an HTTP
Browser (Explorer or Mozilla Firefox). The Web EMS uses a graphical interface.
Most system configurations and statuses are available via the Web EMS. However,
some advanced configuration options are only available via CLI.
Note: For optimal Web EMS performance, it is recommended to ensure
that the network speed is at least 100 Kbps for most operations,
and at least 5 Mbps for software download operations.
The Web EMS shows the actual unit configuration and provides easy access to any
interface in the IDU. The Web EMS opens to a Unit and Radio Summary page that
displays the key unit, link, and radio parameters on a single page for quick
viewing. This page can be customized to include only specific columns and tables,
enabling the user to hide information that he does not need in order to focus on
the information that is most relevant to his needs in monitoring and managing the
unit.
The Web EMS includes a Quick Platform Setup page designed to simplify initial
configuration and minimize the time it takes to configure a working link.
The Web EMS also includes quick link configuration wizards that guide the user,
step-by-step, through the creation of:
• 1+0 links with Pipe services
• 1+0 repeater links (radio to radio) with Pipe services
• 1+1 HSB links with Pipe services
• 1+1 HSB links with Space Diversity and Pipe services
• 2+0 Multi-Carrier ABC groups
• TDM services
• Pseudowire services
Page 230 of 322

With respect to system security, the Web EMS includes two features to facilitate
monitoring and configuring security-related parameters.
To configure security-related features, the Web EMS gathers several pages under
the Quick Configuration portion of the Web EMS main menu. Users can configure
the following parameters from these pages:
• FIPS Admin
• Import and export security settings
• Session timeout
• Login banner
• AES-256 payload encryption
• HTTP or HTTPS
• Telnet blocking
• SNMP parameters
• Users and user profiles
• Login and password parameters
• RSA public key configuration
• Certificate Signing Request (CSR) file download and install
The Web EMS also includes a Security Summary page that gathers a number of
important security-related parameters in a single page for quick viewing. The
Security Summary page can be displayed from the root of the Web EMS main
menu.
The Security Summary page includes:
• FIPS Admin status
• Session Timeout
• Login Banner
• AES-256 payload encryption status
• HTTP/HTTPS configuration
• Telnet blocking status
• SNMP parameters
• Login and password security parameters
• Users and their parameters
• Public RSA key currently configured on the device
Page 231 of 322

7.5 SDN Support

IP-20 devices support SDN, with NETCONF/YANG capabilities. This enables IP-20
devices to be managed via SDN using Ceragon’s SDN controller, SDN Master.
SDN (Software-Defined Networking) is a comprehensive, software-centric
approach to networking that makes network planning and management more
flexible, efficient, and effective in many ways
IP-20’s SDN implementation is a key part of Ceragon’s vision for evolving wireless
backhaul towards SDN via open architecture based on standard Northbound and
Southbound interfaces. This vision includes innovative SDN solutions for dynamic
network performance and resource optimization, and SDN-based backhaul
network provisioning, monitoring, and self-healing.
SDN provides a full portfolio of network and network element management
capabilities, including
• Topology auto discovery
• Performance monitoring
• Fault Management
• Alarms and events
• Service configuration
IP-20’s SDN implementation includes the following standard interfaces and
protocols:
• NBI:
IETF
ONF TAPI 2.0 or higher
RESTCONF
• SBI:
NETCONF RFC 6241
Support for get/get-config/edit/copy/delete
YANG RFC 6020
Information Model (TR-532 and TR-527)
SDN provides significant benefits to network operators, including:
• Improving time-to-market and increasing network planning flexibility by
enabling easy connection and integration with legacy devices from multiple
vendors.
• High performance and resiliency due to the availability of plug-in applications
and SDN’s intrinsic design for resiliency and availability.
• Lower CAPEX and OPEX resulting from self-defined scripts, quicker
introduction of new services, and fast troubleshooting.
Page 232 of 322

7.6 Command Line Interface (CLI)

A CLI connection to the IP-20G can be opened via terminal (serial COM, speed:
115200, Data: 8 bits, Stop: 1 bit, Flow-Control: None), or via telnet. The Terminal
format should be VT-100 with a screen definition of 80 columns X 24 rows.
Note: Telnet access can be blocked by user configuration.
All parameter configurations can be performed via CLI.
7.7 Configuration Management

The system configuration file consists of a set of all the configurable system
parameters and their current values.
IP-20G configuration files can be imported and exported. This enables you to copy
the system configuration to multiple IP-20G units.
System configuration files consist of a zip file that contains three components:
• A binary configuration file which is used by the system to restore the
configuration.
• A text file which enables users to examine the system configuration in a
readable format. The file includes the value of all system parameters at the
time of creation of the backup file.
• An additional text file which enables users to write CLI scripts in order to make
desired changes in the backed-up configuration. This file is executed by the
system after restoring the configuration.31
The system provides three restore points to manage different configuration files.
Each restore point contains a single configuration file. Files can be added to
restore points by creating backups of the current system state or by importing
them from an external server.
Note: In the Web EMS, these restore points are referred to as “file
numbers.”
For example, a user may want to use one restore point to keep a last good
configuration, another to import changes from an external server, and the third to
store the current configuration.
Any of the restore points can be used to apply a configuration file to the system.
The user can determine whether or not to include security-related settings, such
as users and user profiles, in the exported configuration file. By default, security
settings are included.
Note: The option to enable or disable import and export of security
parameters is planned for future release.
31
The option to edit the backup configuration is planned for future release.
Page 233 of 322

7.8 Software Management

The IP-20G software installation and upgrade process includes the following steps:
• Download – The files required for the installation or upgrade are downloaded
from a remote server.
• Installation – The files are installed in the appropriate modules and
components of the IP-20G.
• Reset – The IP-20G is restarted in order to boot the new software and
firmware versions.
IP-20G software and firmware releases are provided in a single bundle that
includes software and firmware for all components supported by the system,
including RFUs. When the user downloads a software bundle, the system verifies
the validity of the bundle. The system also compares the files in the bundle to the
files currently installed in the IP-20G and its components, so that only files that
differ between the new version bundle and the current version in the system are
actually downloaded. A message is displayed to the user for each file that is
actually downloaded.
Note: When downloading an older version, all files in the bundle may
be downloaded, including files that are already installed.
Software bundles can be downloaded via FTP, SFTP, HTTP, or HTTPS. When
downloading software via HTTP or HTTPS, the IP-20G unit acts as an HTTP server,
and the software can be downloaded directly to the unit. When downloading
software via FTP or SFTP, the IP-20G functions as an FTP or SFTP client, and FTP or
SFTP server software must be installed on the PC or laptop being using to perform
the upgrade.
After the software download is complete, the user initiates the installation. A
timer can be used to perform the installation after a defined time interval. When
an installation timer is used, the system performs an automatic reset after the
installation.
Although RFU software is included in the standard installation bundle, the current
software version is not automatically updated when an installation is performed.
To upgrade the software in an RFU, you must perform the upgrade manually, per
radio carrier. This enables users to manage IDU and RFU software versions
separately.
7.8.1 Backup Software Version

Note: Backup software version support is planned for future release.
IP-20G maintains a backup copy of the software bundle. In the event that the
working software version cannot be found, or the operating system fails to start
properly, the system automatically boots from the backup version, and the
previously active version becomes the backup version.
Users can also update the backup version manually. The Web EMS includes a field
that indicates whether or not the active and backup software versions are
identical.
Page 234 of 322

7.9 CeraPlan Service for Creating Pre-Defined Configuration Files

IP-20 units running CeraOS 9.2 or higher can be configured from the Web EMS in a
single step by applying a pre-defined configuration file. This drastically reduces
the initial installation and setup time in the field.
Using pre-defined configuration files also reduces the risk of configuration errors
and enables operators to invest less time and money training installation
personnel. Installers can focus on hardware configuration, relying on the pre-
defined configuration file to implement the proper software configuration on
each device.
The pre-defined configuration file is generated by Ceragon Professional Services
and provided as a service.
A pre-defined configuration file can be prepared for multiple IP-20 units, with the
relevant configuration details specified and differentiated per-unit. This simplifies
administration, since a single file can be used with multiple devices.
Pre-defined configuration files can include all the parameters necessary to
configure basic links, including:
• ETSI to ANSI conversion
• Activation Key (or Demo mode) configuration
• Radio Parameters
• Interface Groups (LAG, Multi-Carrier ABC)
• Management Service
All configurations that can be implemented via the Web EMS Quick Configuration
wizards can also be configured using pre-defined configuration files.
Pre-defined configuration files can be created by Ceragon Professional Services,
according to customer specifications. For further information on CeraPlan, consult
your Ceragon representative.
Page 235 of 322

7.10 IPv6 Support

FibeAir IP-20G management communications can use both IPv4 and IPv6. The unit
IP address for management can be configured in either or both formats.
Additionally, other management communications can utilize either IPv4 or IPv6.
This includes:
• Software file downloads
• Configuration file import and export
• Trap forwarding
• Unit information file export (used primarily for maintenance and
troubleshooting)
7.11 In-Band Management

FibeAir IP-20G can optionally be managed In-Band, via its radio and Ethernet
interfaces. This method of management eliminates the need for a dedicated
management interface. For more information, refer to Management Service
(MNG) on page 126.
7.12 Local Management

IP-20G provides two FE interfaces for local management. The two management
interfaces give users the ability not only to manage the IP-20G directly via a laptop
or PC, but also to manage other devices via the second management port of the
IP-20G.

• Ethernet Management Interfaces
Page 236 of 322

7.13 Alarms
7.13.1 Configurable BER Threshold Alarms and Traps

Users can configure alarm and trap generation in the event of Excessive BER and
Signal Degrade BER above user-defined thresholds. Users have the option to
configure whether or not excessive BER is propagated as a fault and considered a
system event.
7.13.2 RSL Threshold Alarm

Users can configure an alarm that is raised if the RSL falls beneath a user-defined
threshold. This feature can be enabled or disabled per radio carrier. By default, it
is disabled. The RSL threshold alarm provides a preventative maintenance tool for
monitoring the health of the link and ensuring that problems can be identified and
corrected quickly.
7.13.3 Editing and Disabling Alarms and Events

Users can change the description text (by appending extra text to the existing
description) or the severity of any alarm in the system. Users can also choose to
disable specific alarms and events. Any alarm or event can be disabled, so that no
indication of the alarm or event is displayed, and no traps are sent for the alarm
or event.
This is performed as follows:
• Each alarm and event in the system is identified by a unique name (see
separate list of system alarms and events).
• The user can perform the following operations on any alarm:
◦ View current description and severity
◦ Define the text to be appended to the description and/or severity
◦ Return the alarm to its default values
◦ Disable or re-enable the alarm (or event)
• The user can also return all alarms and events to their default values.
7.13.4 Timeout for Trap Generation

Users can configure a wait time of 0 to 120 seconds after an alarm is cleared in
the system before the alarm is actually reported as being cleared. This prevents
traps flooding the NMS in the event that some external condition causes the
alarm to be raised and cleared continuously.
This means that when the alarm is cleared, the alarm continues to be displayed
and no clear alarm trap is sent until the timeout period is finished.
The timeout for trap generation can be configured via CLI. By default, the timeout
is 10 seconds.
Page 237 of 322

7.14 External Alarms

IP-20G includes a DB9 dry contact external alarms interface. The external alarms
interface supports five input alarms. For each alarm input, the user can configure
the following:
1 Alarm administration (On or Off)
2 Alarm text
3 Alarm severity
Alarm severity can be configured to:
1 Indeterminate
2 Critical
3 Major
4 Minor
5 Warning
7.15 NTP Support

Related topics:
• Synchronization
IP-20G supports Network Time Protocol (NTP). NTP distributes Coordinated
Universal Time (UTC) throughout the system, using a jitter buffer to neutralize the
effects of variable latency.
IP-20G supports NTPv3 and NTPv4. NTPv4 provides interoperability with NTPv3
and with SNTP.
7.16 UTC Support

IP-20G uses the Coordinated Universal Time (UTC) standard for time and date
configuration. UTC is a more updated and accurate method of date coordination
than the earlier date standard, Greenwich Mean Time (GMT).
Every IP-20G unit holds the UTC offset and daylight savings time information for
the location of the unit. Each management unit presenting the information (CLI
and Web EMS) uses its own UTC offset to present the information in the correct
time.
Page 238 of 322

7.17 System Security Features

To guarantee proper performance and availability of a network as well as the data
integrity of the traffic, it is imperative to protect it from all potential threats, both
internal (misuse by operators and administrators) and external (attacks
originating outside the network).
System security is based on making attacks difficult (in the sense that the effort
required to carry them out is not worth the possible gain) by putting technical and
operational barriers in every layer along the way, from the access outside the
network, through the authentication process, up to every data link in the network.
7.17.1 Ceragon’s Layered Security Concept

Each layer protects against one or more threats. However, it is the combination of
them that provides adequate protection to the network. In most cases, no single
layer protection provides a complete solution to threats.
The layered security concept is presented in the following figure. Each layer
presents the security features and the threats addressed by it. Unless stated
otherwise, requirements refer to both network elements and the NMS.
Figure 117: Security Solution Architecture Concept
Page 239 of 322

7.17.2 Defenses in Management Communication Channels

Since network equipment can be managed from any location, it is necessary to
protect the communication channels’ contents end to end.
These defenses are based on existing and proven cryptographic techniques and
libraries, thus providing standard secure means to manage the network, with
minimal impact on usability.
They provide defense at any point (including public networks and radio
aggregation networks) of communications.
While these features are implemented in Ceragon equipment, it is the
responsibility of the operator to have the proper capabilities in any external
devices used to manage the network.
In addition, inside Ceragon networking equipment it is possible to control physical
channels used for management. This can greatly help deal with all sorts of DoS
attacks.
Operators can use secure channels instead or in addition to the existing
management channels:
• SNMPv3 for all SNMP-based protocols for both NEs and NMS
• HTTPS for access to the NE’s web server
• SSH-2 for all CLI access SFTP for all software and configuration download
between NMS and NEs
All protocols run with secure settings using strong encryption techniques.
Unencrypted modes are not allowed, and algorithms used must meet modern and
client standards.
Users are allowed to disable all insecure channels.
In the network elements, the bandwidth of physical channels transporting
management communications is limited to the appropriate magnitude, in
particular, channels carrying management frames to the CPU.
Attack types addressed
• Tempering with management flows
• Management traffic analysis
• Unauthorized software installation
• Attacks on protocols (by providing secrecy and integrity to messages)
• Traffic interfaces eavesdropping (by making it harder to change configuration)
• DoS through flooding
Page 240 of 322

7.17.3 Defenses in User and System Authentication Procedures
7.17.3.1 User Configuration and User Profiles

User configuration is based on the Role-Based Access Control (RBAC) model.
According to the RBAC model, permissions to perform certain operations are
assigned to specific roles. Users are assigned to particular roles, and through
those role assignments acquire the permissions to perform particular system
functions.
In the IP-20G GUI, these roles are called user profiles. Up to 50 user profiles can
be configured. Each profile contains a set of privilege levels per functionality
group, and defines the management protocols (access channels) that can be used
to access the system by users to whom the user profile is assigned.
The system parameters are divided into the following functional groups:
• Security
• Management
• Radio
• TDM
• Ethernet
• Synchronization
A user profile defines the permitted access level per functionality group. For each
functionality group, the access level is defined separately for read and write
operations. The following access levels can be assigned:
• None – No access to this functional group.
• Normal – The user has access to parameters that require basic knowledge
about the functional group.
• Advance – The user has access to parameters that require advanced
knowledge about the functional group, as well as parameters that have a
significant impact on the system as a whole, such as restoring the
configuration to factory default settings.
7.17.3.2 User Identification

IP-20G supports the following user identification features:
• Configurable inactivity time-out for automatically closing unused management
channels
• Optional password strength enforcement. When password strength
enforcement is enabled; passwords must comply with the following rules:
◦ Password must be at least eight characters long.
◦ Password must include at least three of the following categories: lower-
case characters, upper-case characters, digits, and special characters.
◦ When calculating the number of character categories, upper-case letters
used as the first character and digits used as the last character of a
password are not counted.
◦ The password cannot have been used within the user’s previous five passwords.
Page 241 of 322

• Users can be prompted to change passwords after a configurable amount of

time (password aging).
• Users can be blocked for a configurable time period after a configurable
number of unsuccessful login attempts.
• Users can be configured to expire at a certain date
• Mandatory change of password at first time login can be enabled and disabled
upon user configuration. It is enabled by default.
7.17.3.3 Remote Authentication

Note: Remote authorization is planned for future release.
Certificate-based strong standard encryption techniques are used for remote
authentication. Users may choose to use this feature or not for all secure
communication channels.
Since different operators may have different certificate-based authentication
policies (for example, issuing its own certificates vs. using an external CA or
allowing the NMS system to be a CA), NEs and NMS software provide the tools
required for operators to enforce their policy and create certificates according to
their established processes.
Server authentication capabilities are provided.
7.17.3.4 RADIUS Support

The RADIUS protocol provides centralized user management services. IP-20G
supports RADIUS server and provides a RADIUS client for authentication and
authorization.
RADIUS can be enabled or disabled. When RADIUS is enabled, a user attempting
to log into the system from any access channel (CLI, WEB, NMS) is not
authenticated locally. Instead, the user’s credentials are sent to a centralized
standard RADIUS server which indicates to the IP-20G whether the user is known,
and which privilege is to be given to the user. RADIUS uses the same user
attributes and privileges defined for the user locally.
Note: When using RADIUS for user authentication and authorization,
the access channels configured per IP-20 user profile are not
applicable. Instead, the access channels must be configured as
part of the RADIUS server configuration.
RADIUS login works as follows:
• If the RADIUS server is reachable, the system expects authorization to be
received from the server:
◦ The server sends the appropriate user privilege to the IP-20G, or notifies
the IP-20G that the user was rejected.
◦ If rejected, the user will be unable to log in. Otherwise, the user will log in
with the appropriate privilege and will continue to operate normally.
• If the RADIUS server is unavailable, the IP-20G will attempt to authenticate
the user locally, according to the existing list of defined users.
Page 242 of 322

Note: Local login authentication is provided in order to enable users to

manage the system in the event that RADIUS server is
unavailable. This requires previous definition of users in the
system. If the user is only defined in the RADIUS server, the user
will be unable to login locally in case the RADIUS server is
unavailable.
In order to support IP-20G - specific privilege levels, the vendor-specific field is
used. Ceragon’s IANA number for this field is 2281.
The following RADIUS servers are supported:
• FreeRADIUS
• RADIUS on Windows Server (IAS)
◦ Windows Server 2008
7.17.3.5 TACACS+ Support

IP-20G supports TACACS+ for remote access user authentication, authorization,
and accounting. Using TACACS+, the IP-20 device acts as the client, working with a
TACACS+ server to authenticate and authorize users.
The TACACS+ protocol provides centralized user management services. TACACS+
separates the functions of Authentication, Authorization, and Accounting (AAA). It
enables arbitrary length and content authentication exchanges, in order to
support future authentication mechanisms. It is extensible to provide for site
customization and future development features, and uses TCP to ensure reliable
communication.
Note: IP-20 supports session-based TACACS+ authorization, but not
command-based.
When TACACS+ is enabled, a user attempting to log into the system from any
access channel (CLI, WEB, NMS) is not authenticated locally. Instead, the user’s
credentials are sent to a centralized standard TACACS+ server which indicates to
the IP-20 device whether the user is known, and which privilege is to be given to
the user.
When a user successfully logs in or logs out of an IP-20 device via TACACS+, the
device sends an accounting packet to the TACACS+ server packet which contains
the following information:
• User Name
• User IP Address
• Time and Date of Connection
• Connection port on the device
Note: This information is also written to the device’s Security Log.
Page 243 of 322

Ceragon’s TACACS+ solution is compliant with any standard TACACS+ server.

Testing has been performed, and interoperability confirmed, with the following
TACACS+ servers:
• Cisco ISE - Version 2.6.0.156
• Tacacs.net - Version 1.2
• tac_plus version F4.0.4.27a
Up to four TACACS+ servers can be defined to work with an IP-20 device. When a
user attempts to log into the device, the device attempts to contact the first
TACACS+ server to authenticate the user. If no response is received from the
server within the user-defined timeout period, the device tries again to contact
the server up to the user-configured number of retries. Then, if no response is
received from the server, the device attempts to contact the second user-defined
TACACS+ server. If no response is received from any of the servers, the device
performs user authentication locally.
7.17.4 Secure Communication Channels

IP-20G supports a variety of standard encryption protocols and algorithms, as
described in the following sections.
7.17.4.1 SSH (Secured Shell)

SSH protocol can be used as a secured alternative to Telnet. In IP-20G:
• SSHv2 is supported.
• SSH protocol will always be operational. Admin users can choose whether to
disable Telnet protocol, which is enabled by default. Server authentication is
based on IP-20G’s public key.
• RSA and DSA key types are supported.
• MAC (Message Authentication Code): SHA-1-96 (MAC length = 96 bits, key
length = 160 bit). Supported MAC: hmac-md5, hmac-sha1, hmac-ripemd160,
hmac-sha1-96, hmac-md5-96'
• The server authenticates the user based on user name and password. The
number of failed authentication attempts is not limited.
• The server timeout for authentication is 10 minutes. This value cannot be
changed.
Page 244 of 322

7.17.4.2 HTTPS (Hypertext Transfer Protocol Secure)

HTTPS combines the Hypertext Transfer protocol with the SSLv3/TLS (1.0, 1.1, 1.2)
protocol to provide encrypted communication and secure identification of a
network web server. IP-20G enables administrators to configure secure access via
HTTPS protocol.
Users can configure the IP-20 to operate in HTTPS strong mode. In HTTPS strong
mode, SSLv3, TLSv1.0, and TLSv1.1 are disabled completely and only certain
ciphers are supported for TLSv1.2.
When FIPS is enabled, SSLv3, TLSv1.0, and TLSv1.1 are disabled completely and
only certain ciphers are supported in TLSv1.2. This is similar to HTTPS strong
mode, although there are some differences.
Note: HTTPS strong mode cannot be enabled in FIPS mode.
For a list of supported HTTPS ciphers, including an indication of which ciphers are
supported in FIPS mode and HTTPS strong mode, respectively, see Annex A –
Supported Ciphers for Secured Communication Protocols in the Release Notes for
the CeraOS version you are using.
7.17.4.3 SFTP (Secure FTP)

SFTP can be used for the following operations:
• Configuration upload and download,
• Uploading unit information
• Uploading a public key
• Downloading certificate files
• Downloading software
7.17.4.4 Creation of Certificate Signing Request (CSR) File

In order to create a digital certificate for the NE, a Certificate Signing Request
(CSR) file should be created by the NE. The CSR contains information that will be
included in the NE's certificate such as the organization name, common name
(domain name), locality, and country. It also contains the public key that will be
included in the certificate. Certificate authority (CA) will use the CSR to create the
desired certificate for the NE.
While creating the CSR file, the user will be asked to input the following
parameters that should be known to the operator who applies the command:
• Common name – The identify name of the element in the network (e.g., the IP
address). The common name can be a network IP or the FQDN of the element.
• Organization – The legal name of the organization.
• Organizational Unit - The division of the organization handling the certificate.
• City/Locality - The city where the organization is located.
• State/County/Region - The state/region where the organization is located.
• Country - The two-letter ISO code for the country where the organization is location.
• Email address - An email address used to contact the organization.
Page 245 of 322

7.17.4.5 RSA Keys

IP-20 devices support RSA keys for communication using HTTPS and SSH protocol.
The IP-20 device comes with randomly generated private and public RSA keys.
However, customers can replace the private/public key pair with customer-
defined private key. The corresponding RSA public key will be generated based on
this private keys. The file must be in PEM format. Supported RSA private key sizes
are 2048, 4096, and 8192. The customer-defined private key can be downloaded
to the device via HTTPS or SFTP. It is recommended to use HTTPS.
7.17.4.6 SNMP
IP-20G supports SNMP v1, V2c, and v3. The default community string in NMS and
the SNMP agent in the embedded SW are disabled. Users are allowed to set
community strings for access to IDUs.
IP-20G supports the following MIBs:
• RFC-1213 (MIB II)
• RMON MIB
• Ceragon (proprietary) MIB.
Access to all IDUs in a node is provided by making use of the community and
context fields in SNMPv1 and SNMPv2c/SNMPv3, respectively.

• FibeAir IP-20 Series MIB Reference
7.17.4.7 Server Authentication (SSLv3/TLS (1.0, 1.1, 1.2))

• All protocols making use of SSL (such as HTTPS) use SLLv3/TLS (1.0, 1.1, 1.2)
and support X.509 certificates-based server authentication.
• Users with type of “administrator” or above can perform the following server
(IDU) authentication operations for certificates handling:
◦ Generate server key pairs (private + public)
◦ Export public key (as a file to a user-specified address)
◦ Install third-party certificates
◦ The Admin user is responsible for obtaining a valid certificate.
◦ Load a server RSA key pair that was generated externally for use by
protocols making use of SSL.
• Non-SSL protocols using asymmetric encryption, such as SSH and SFTP, can
make use of public-key based authentication.
◦ Users can load trusted public keys for this purpose.
Page 246 of 322

7.17.5 Security Log

The security log is an internal system file which records all changes performed to
any security feature, as well as all security related events.
Note: In order to read the security log, the user must upload the log to
his or her server.
The security log file has the following attributes:
• The file is of a “cyclic” nature (fixed size, newest events overwrite oldest).
• The log can only be read by users with "admin" or above privilege.
• The contents of the log file are cryptographically protected and digitally
signed.
◦ In the event of an attempt to modify the file, an alarm will be raised.
• Users may not overwrite, delete, or modify the log file.
The security log records:
• Changes in security configuration
◦ Carrying out “security configuration copy to mate”
◦ Management channels time-out
◦ Password aging time
◦ Number of unsuccessful login attempts for user suspension
◦ Warning banner change
◦ Adding/deleting of users
◦ Password changed
◦ SNMP enable/disable
◦ SNMP version used (v1/v3) change
◦ SNMPv3 parameters change
◦ Security mode
◦ Authentication algorithm
◦ User
◦ Password
◦ SNMPv1 parameters change
◦ Read community
◦ Write community
◦ Trap community for any manager
◦ HTTP/HTTPS change
◦ FTP/SFTP change
◦ Telnet and web interface enable/disable
◦ FTP enable/disable
◦ Loading certificates
◦ RADIUS server
◦ Radius enable/disable
Page 247 of 322

◦ TACACS+ server
◦ TACACS+ enable/disable
◦ Remote logging enable/disable (for security and configuration logs)
◦ System clock change
◦ NTP enable/disable
• Security events
• Successful and unsuccessful login attempts
• N consecutive unsuccessful login attempts (blocking)
• Configuration change failure due to insufficient permissions
• SNMPv3/PV authentication failures
• User logout
• User account expired
For each recorded event the following information is available:
• User ID
• Communication channel (WEB, terminal, telnet/SSH, SNMP, NMS, etc.)
• IP address, if applicable
• Date and time
7.17.6 Anti-Theft
The purpose of Anti-Theft Protection is to render IP-20 units that are stolen
unusable, thereby eliminating any incentive to steal such units.
Note: AT is not supported on units with Unit Redundancy.
Anti-Theft is configured from the NetMaster NMS, and requires an activation key
on both NetMaster and the IP-20 device.
In Anti-Theft (AT) mode, NetMaster uses HTTPS to periodically authenticate
devices on which Anti-Theft is enabled. A shared code word and Sanction Delay
Counter are configured on NetMaster. NetMaster shares the code word and
Counter with AT-enabled devices.
Each time NetMaster authenticates an AT-enabled device, the Sanction Delay
Counter on the device is reset to its original value. The Sanction Delay Counter
then starts to count down until the next time NetMaster authenticates the device,
at which time the Sanction Counter is again reset to its original value.
If the counter reaches zero, the device enters Sanction Mode. In Sanction Mode,
the device resets every 30 minutes, making normal operation with the device
impossible. The device remains in Sanction Mode until the next time NetMaster
authenticates the device. When NetMaster does authenticate the device,
Sanction Mode ends, and the Sanction Counter is reset to its original value.
Only two steps are necessary to enable AT on an IP-20 device:
• Both NetMaster and the device must be configured to use HTTPS.
• The AT activation key must be configured on the device.
Page 248 of 322

Important Note: The user must configure the device and NetMaster to use HTTPS
before configuring the AT activation key on the device. Once AT
mode has been enabled, it will no longer be possible for the
device to work with HTTP.
The rest of the AT configuration is performed on NetMaster.
It is important to note that once AT has been applied on the device and enabled
by NetMaster, it can never be permanently removed or disabled. It can be
temporarily disabled from NetMaster for seven days. Disabling AT requires a
special Disable AT license for NetMaster.
Also, once AT has been applied on the device and enabled by NetMaster, the
device cannot be downgraded to a CeraOS version lower than 11.0.
Page 249 of 322

8. Standards and Certifications

• Supported Ethernet Standards
• MEF Certifications for Ethernet Services
• Supported TDM Pseudowire Encapsulations
• Standards Compliance
• Network Management, Diagnostics, Status, and Alarms
Page 250 of 322

8.1 Supported Ethernet Standards

Table 39: Supported Ethernet Standards
Standard Description
802.3 10base-T
802.3u 100base-T
802.3ab 1000base-T
802.3z 1000base-X
802.3ac Ethernet VLANs
802.1Q Virtual LAN (VLAN)
802.1p Class of service
802.1ad Provider bridges (QinQ)
802.3ad Link aggregation
Auto MDI/MDIX for 1000baseT
RFC 1349 IPv4 TOS
RFC 2474 IPv4 DSCP
RFC 2460 IPv6 Traffic Classes
Page 251 of 322

8.2 MEF Certifications for Ethernet Services
Table 40: Supported MEF Specifications

Specification Description
MEF-2 Requirements and Framework for Ethernet Service Protection

MEF-6.1 Metro Ethernet Services Definitions Phase 2
MEF-8 Implementation Agreement for the Emulation of PDH Circuits over
Metro Ethernet Networks
MEF-10.3 Ethernet Services Attributes Phase 3
MEF 22.1 Mobile Backhaul Implementation Agreement Phase 2
MEF-30.1 Service OAM Fault Management Implementation Agreement Phase 2
MEF-35 Service OAM Performance Monitoring Implementation Agreement
Table 41: MEF Certifications

Certification Description
CE 2.0 Second generation Carrier Ethernet certification

MEF-18 Abstract Test Suite for Circuit Emulation Services
MEF-9 Abstract Test Suite for Ethernet Services at the UNI. Certified for all
service types (EPL, EVPL & E-LAN).
This is a first generation certification. It is fully covered as part of CE2.0)
MEF-14 Abstract Test Suite for Traffic Management Phase 1. Certified for all
service types (EPL, EVPL & E-LAN).
This is a first generation certification. It is fully covered as part of CE2.0)
Page 252 of 322

8.3 Supported TDM Pseudowire Encapsulations

Table 42: Supported TDM Pseudowire Encapsulations
Certification Description Availability
VLAN (MEF-8) Circuit Emulation Services Available.

over native Ethernet
frames
IP/UDP (IETF) Layer 3 encapsulation over Planned for future release.
Ethernet
MPLS (MFA8) MPLS encapsulation over Planned for future release.
Ethernet
8.4 Standards Compliance

Table 43: Standards Compliance
Specification Standard
Radio EN 302 217-2

EMC EN 301 489-4
EN 301 489-1
FCC 47 CFR, part 15, subpart B
ICES-003
Safety EN 60950-1
IEC 60950-1
UL 60950-1
CSA-C22.2 No.60950-1
EN 60950-22 (RFU only)
UL 60950-22 (RFU only)
CSA C22.2.60950-22 (RFU only)
IEC 60950-22 (RFU only)
Ingress Protection (RFUs) RFU-C: IP66
1500HP/RFU-HP: IP56
Operation – IDU ETSI EN 300 019-1-3 Class 3.2
Operation – RFU ETSI EN 300 019-1-4 Class 4.1
Storage ETSI EN 300 019-1-1 Class 1.2
Transportation ETSI EN 300 019-1-2 Class 2.3
Page 253 of 322

8.5 Network Management, Diagnostics, Status, and Alarms

Table 44: Network Management, Diagnostics, Status, and Alarms
Network Management NetMaster/PolyView

System
NMS Interface protocol SNMPv1/v2c/v3

XML over HTTP/HTTPS toward the NMS
Element Management Web based EMS, CLI
Management Channels & HTTP/HTTPS
Protocols Telnet/SSH-2
FTP/SFTP
Authentication, User access control
Authorization & X-509 Certificate
Accounting
Management Interface Dedicated Ethernet interfaces or in-band in traffic ports
In-Band Management Support dedicated VLAN for management
TMN The NMS functions are in accordance with ITU-T recommendations for
TMN
RSL Indication Power reading (dBm) available at RFU32, and NMS
Performance Monitoring Integral with onboard memory per ITU-T G.826/G.828
32
Note that the voltage measured at the BNC port is not accurate and should be used only as
an aid.
Page 254 of 322

9. Specifications
• General Radio Specifications
• Radio Capacity Specifications
• Transmit Power Specifications (dBm)
• Receiver Threshold (RSL)
• Frequency Bands
• Mediation Device Losses
• Ethernet Specifications
• TDM Specifications
• Synchronization Specifications
• Mechanical Specifications
• Environmental Specifications
• Supported Antenna Types
• Waveguide Specifications
• Antenna Interface Requirements for RFU-HP/1500HP
• Power Input Specifications
• Power Consumption Specifications
Related Topics:
• Standards and Certifications
Note: All specifications are subject to change without prior notification.
Page 255 of 322

9.1 General Radio Specifications

Note: The specifications in this section refer to a FibeAir IP-20G system
using an RFU-C or 1500HP/RFU-HP, except where a specific RFU
is noted.
Table 45: General Radio Specifications

Frequency (GHz) Operating Frequency Range (GHz) Tx/Rx Spacing (MHz)
6L,6H 5.85-6.45, 6.4-7.125 252.04, 240, 266, 300, 340, 160, 170,
500
7,8 7.1-7.9, 7.7-8.5 154, 119, 161, 168, 182, 196, 208, 245,
250, 266, 300,310, 311.312, 500, 530
10 10.0-10.7 91, 168,350, 550
11 10.7-11.7 490, 520, 530
13 12.75-13.3 266
15 14.4-15.35 315, 420, 475, 644, 490, 728
18 17.7-19.7 1010, 1120, 1008, 1560
23 21.2-23.65 1008, 1200, 1232
24UL 24.0-24.25 Customer-defined
26 24.2-26.5 800, 1008
28 27.35-29.5 350, 450, 490, 1008
32 31.8-33.4 812
36 36.0-37.0 700
38 37-40 1000, 1260, 700
42 40.55-43.45 1500
Standards ETSI, ITU-R, CEPT
Frequency Stability +0.001%
Frequency Source Synthesizer
RF Channel Selection Via EMS/NMS
Tx Range (Manual/ATPC) The dynamic TX range with ATPC is the same as the manual
TX range, and depends on the RFU type, the frequency, and
the ACM profile. The maximum TX power with ATPC is no
higher than the maximum manually configured TX power.
Page 256 of 322

9.2 Radio Scripts

Designated ETSI System Class Explanation:
ACCP ACAP CCDP
(Adjacent Channel Co (Adjacent Channel (Co Channel Dual
Polarization) Alternate Polarization) Polarization)
H H
V V
Note that:
XPIC scripts (all scripts with Script ID 12XX) are not supported in
1+1 HSB radio protection mode.
Although in some cases it may be possible to configure higher
profiles, the maximum supported profiles are those listed in the
tables below.
Indications of supported System Classes in the following table
refer to the script characteristics only. Regulatory issues must be
determined under the applicable local standards.
Page 257 of 322

Table 46: MRMC Radio Scripts

Script ID Channel Occupied RFU-C RFU- XPIC Highest Max Max
BW BW System HP/1500HP (CCDP) Spectral Profile Profile
Class System Class Efficiency Class (ACM) (Fixed)
107533 1.75 1.6335 ACCP n/a No 6L 5 (256 4 (128

QAM) QAM)
1023 3.5 3.267 ACCP ACAP No 6L 5 (256 4 (128

QAM) QAM)
1008 7 6.5 ACCP ACAP No 7B 9 8
1009 14 13.3 ACCP ACAP No 7B 9 8
1209 14 13.3 ACCP ACAP Yes 7B 9 8
1004 28 26.5 ACCP ACAP No 8B 10 9
1204 28 26.5 ACCP ACAP Yes 7B 9 8
121434 28 26 - ACCP Yes 7B 9 8
1005 28 28 ACAP ACAP No 8A 10 9
1205 28 28 ACAP ACAP Yes 7A 9 8
121735 40 33.5 - ACCP Yes 7B 9 8
1007 40 37.4 ACCP ACAP No 8B 10 9
1207 40 37.4 ACCP ACAP Yes 7B 9 8
1003 56 53 ACCP ACAP No 8B 10 9
1006 56 55.7 ACAP ACAP No 8A 10 9
1203 56 53 ACCP ACAP Yes 7B 9 8
1206 56 55.7 ACAP ACAP Yes 7A 9 8
33
MRMC script 1075 requires RFU-C and is supported for 6 and 13 GHz.
34
MRMC script 1214 provides smaller bandwidth than MRMC script 1204. Script 1214 can be
used for interoperability with existing equipment in the field. It is an Adjacent Channel script,
for use with RFU-HP and 1500HP only.
35
MRMC script 1217 provides smaller bandwidth than MRMC script 1207. Script 1217 can be
used for interoperability with existing equipment in the field. It is an Adjacent Channel script,
Page 258 of 322

9.3 Radio Capacity Specifications

Each table in this section includes ranges of capacity specifications according to
frame size, with ranges given for no Header De-Duplication, Layer-2 Header De-
Duplication, and LTE-optimized Header De-Duplication.
Each table provides the capacity specifications for a specific MRMC script, as
indicated in the table caption. For additional information about each script, see
Radio Scripts on page 257.
Notes: The figures in this section are indicative only. Exact results will
depend on multiple factors, such as packet size, type of traffic,
headers, etc.
Ethernet capacity depends on average frame size.
For LTE-Optimized Header De-Duplication, the capacity figures
are for LTE packets encapsulated inside GTP tunnels with
IPv4/UDP encapsulation and double VLAN tagging (QinQ).
Capacity for IPv6 encapsulation is higher.
9.3.1 Radio Capacity Specifications (no XPIC)
9.3.1.1 1.75 MHz – Script ID 1075
Table 47: 1.75 MHz – Script ID 1075

Profile Modulation Minimum Max # of Ethernet throughput
required supported
capacity E1s No Header De- L2 Header De- LTE-Optimized
activation key Duplication Duplication Header De-
36 Duplication
0 QPSK – 0 1.5-2 – –
1 16 QAM – 1 4-5 – –
2 32 QAM – 2 5.5-7 – –
3 64 QAM – 2 7-8.5 – –
4 128 QAM – 3 8.5-10.5 – –
5 256 QAM – 3 9.5-12 – –
36
Script 1075 requires a special activation key, SL-CHBW-1.75M, instead of a regular capacity
activation key.
Page 259 of 322

9.3.1.2 3.5 MHz – Script ID 1023
Table 48: 3.5 MHz – Script ID 1023

required supported
capacity E1s No Header De- L2 Header De- LTE-Optimized
activation key Duplication Duplication Header De-
Duplication
0 QPSK − 2 3-4 3-5 4-13

1 16 QAM − 4 8-10 8-12 9-32
2 32 QAM − 5 11-14 11-17 12-43
3 64 QAM 50 6 14-17 14-21 15-54
4 128 QAM 50 8 17-21 17-25 18-65
5 256 QAM 50 9 19-24 20-29 20-74
9.3.1.3 7 MHz – Script ID 1008
Table 49: 7 MHz – Script ID 1008

required supported
capacity E1s No Header De- L2 Header LTE-Optimized
activation key Duplication De- Header De-
Duplication Duplication
0 QPSK − 4 8-10 9-13 9-32

1 8 PSK − 6 13-16 13-19 13-48
2 16 QAM 50 8 18-22 18-27 19-69
3 32 QAM 50 11 24-30 24-36 26-92
4 64 QAM 50 14 30-37 30-44 32-114
5 128 QAM 50 16 36-44 36-53 38-137
6 256 QAM 50 19 42-51 42-61 44-158
7 512 QAM 50 20 45-54 45-66 47-169
8 1024 QAM (Strong FEC) 50 21 48-58 48-71 50-182
9 1024 QAM (Light FEC) 50 23 51-62 51-75 53-194
Page 260 of 322

9.3.1.4 14 MHz – Script ID 1009

required supported
0 QPSK 50 9 19-24 20-29 20-74

1 8 PSK 50 13 29-36 30-43 31-112
2 16 QAM 50 18 40-49 41-60 42-153
3 32 QAM 50 24 53-65 54-79 56-203
4 64 QAM 50 29 66-80 66-97 69-249
5 128 QAM 100 36 79-97 80-117 83-301
6 256 QAM 100 41 90-110 91-134 95-344
7 512 QAM 100 45 100-122 101-147 105-380
8 1024 QAM (Strong FEC) 100 48 106-129 106-156 111-402
9 1024 QAM (Light FEC) 100 50 112-137 113-166 118-426
9.3.1.5 28 MHz – Script ID 1004

required supported
0 QPSK 50 18 40-49 41-59 42-153

1 8 PSK 50 27 60-74 61-89 63-229
2 16 QAM 100 37 82-101 83-122 86-313
3 32 QAM 100 49 108-132 109-160 114-412
4 64 QAM 150 60 134-163 135-197 140-508
5 128 QAM 150 72 161-196 162-237 169-612
6 256 QAM 200 82 183-224 184-270 192-696
7 512 QAM 200 91 202-247 203-298 212-769
8 1024 QAM (Strong FEC) 225 97 215-262 216-317 225-817
9 1024 QAM (Light FEC) 225 103 228-279 230-337 239-868
10 2048 QAM 250 110 245-299 246-361 257-931
Page 261 of 322

9.3.1.6 28 MHz – Script ID 1005

required supported
0 QPSK 50 19 43-52 43-63 45-162

1 8 PSK 50 28 62-76 63-92 65-236
2 16 QAM 100 39 87-107 88-129 92-332
3 32 QAM 100 52 115-140 116-170 121-437
4 64 QAM 150 64 141-173 143-209 149-538
5 128 QAM 150 77 170-208 172-252 179-648
6 256 QAM 200 88 196-239 197-289 206-745
7 512 QAM 200 94 209-255 210-308 219-794
8 1024 QAM (Strong FEC) 225 102 228-278 229-336 239-866
9 1024 QAM (Light FEC) 225 108 241-295 243-356 253-917
10 2048 QAM 250 118 263-321 265-389 276-1000
Page 262 of 322

9.3.1.7 40 MHz – Script ID 1007

required supported
0 QPSK 50 26 58-71 58-85 61-220

1 8 PSK 100 39 86-105 87-127 90-328
2 16 QAM 100 53 117-143 118-173 123-446
3 32 QAM 150 69 154-189 156-228 162-588
4 64 QAM 200 85 190-232 191-280 199-722
5 128 QAM 225 103 229-280 231-339 241-873
6 256 QAM 250 111 247-302 249-365 259-939
7 512 QAM 300 122 270-330 272-399 284-1000
8 1024 QAM (Strong FEC) 300 138 306-375 309-453 322-1000
9 1024 QAM (Light FEC) 300 146 325-398 328-481 342-1000
10 2048 QAM 350 158 352-430 355-520 370-1000
Page 263 of 322

9.3.1.8 56 MHz – Script ID 1003

required supported
0 QPSK 100 37 83-101 83-122 87-314

1 8 PSK 100 55 123-150 124-182 129-468
2 16 QAM 150 75 167-205 169-247 176-637
3 32 QAM 225 99 220-269 222-325 231-838
4 64 QAM 300 122 270-331 273-400 284-1000
5 128 QAM 300 147 327-400 329-483 343-1000
6 256 QAM 400 168 374-457 377-553 393-1000
7 512 QAM 400 183 406-496 409-600 426-1000
8 1024 QAM (Strong FEC) 450 199 441-540 445-652 464-1000
9 1024 QAM (Light FEC) 450 211 469-573 472-693 492-1000
10 2048 QAM 500 229 508-621 512-751 534-1000
Page 264 of 322

9.3.1.9 56 MHz – Script ID 1006

required capacity supported E1s
activation key No Header De- L2 Header LTE-Optimized
Duplication De- Header De-
0 QPSK 100 39 87-106 88-128 91-331

1 8 PSK 150 57 127-155 128-187 133-482
2 16 QAM 200 79 176-215 177-260 185-670
3 32 QAM 225 104 232-283 233-342 243-881
4 64 QAM 300 128 284-348 286-420 299-1000
5 128 QAM 350 155 344-420 346-508 361-1000
6 256 QAM 400 178 397-485 400-586 416-1000
7 512 QAM 450 192 427-521 430-630 448-1000
8 1024 QAM 450 209 464-567 467-685 487-1000
(Strong FEC)
9 1024 QAM 500 222 493-602 497-728 517-1000
(Light FEC)
10 2048 QAM 500 240 534-653 538-789 561-1000
Page 265 of 322

9.3.2 Radio Capacity Specifications with XPIC
9.3.2.1 14 MHz – Script ID 1209

required supported
0 QPSK 50 8 18-23 19-27 19-70

1 8 PSK 50 13 28-34 28-41 29-106
2 16 QAM 50 17 38-47 39-57 40-146
3 32 QAM 50 23 51-62 51-75 53-193
4 64 QAM 50 28 62-76 63-92 66-238
5 128 QAM 100 34 76-92 76-112 79-287
6 256 QAM 100 39 87-106 87-128 91-330
7 512 QAM 100 44 98-120 99-145 103-374
8 1024 QAM (Strong 100 48 106-130 107-157 112-405
FEC)
9 1024 QAM (Light FEC) 100 51 114-139 114-168 119-432
Page 266 of 322

9.3.2.2 28 MHz – Script ID 1204

required supported
0 QPSK 50 18 39-48 40-58 41-149

1 8 PSK 50 26 59-72 59-87 62-223
2 16 QAM 100 36 80-98 81-119 84-305
3 32 QAM 100 48 106-129 106-156 111-402
4 64 QAM 150 59 130-159 131-192 137-495
5 128 QAM 150 71 157-192 158-232 165-598
6 256 QAM 200 81 180-220 181-266 189-684
7 512 QAM 200 90 200-244 201-295 210-761
8 1024 QAM (Strong 225 96 212-260 214-314 223-809
FEC)
9 1024 QAM (Light FEC) 225 101 226-276 227-333 237-858
Page 267 of 322

9.3.2.3 28 MHz – Script ID 1214

required supported
activation Duplication De- Header De-
key Duplication Duplication
0 QPSK 50 17 38-46 38-56 40-145

1 8 PSK 50 26 57-69 57-84 60-216
2 16 QAM 100 35 78-95 78-115 82-296
3 32 QAM 100 46 102-125 103-151 107-389
4 64 QAM 150 57 126-154 127-186 132-479
5 128 QAM 150 68 152-186 153-225 160-579
6 256 QAM 150 78 174-213 175-257 183-663
7 512 QAM 200 87 194-237 195-286 203-737
8 1024 QAM (Strong FEC) 200 93 206-251 207-304 216-783
9 1024 QAM (Light FEC) 225 98 218-267 220-323 229-831
Note: MRMC script 1214 provides smaller bandwidth than MRMC

script 1204. Script 1214 can be used for interoperability with
existing equipment in the field. It is an Adjacent Channel script,
Page 268 of 322

9.3.2.4 28 MHz – Script ID 1205

required supported
0 QPSK 50 19 42-51 42-62 44-159

1 8 PSK 50 28 62-76 63-92 65-237
2 16 QAM 100 38 85-104 86-126 89-324
3 32 QAM 100 50 112-137 113-166 118-426
4 64 QAM 150 62 138-168 139-204 145-524
5 128 QAM 150 75 167-204 168-246 175-634
6 256 QAM 200 86 191-233 192-282 200-725
7 512 QAM 225 95 212-259 213-313 222-806
8 1024 QAM (Strong 225 101 225-275 227-333 236-856
FEC)
9 1024 QAM (Light FEC) 225 107 239-292 241-353 251-909
Page 269 of 322

9.3.2.5 40 MHz – Script ID 1207

required supported
0 QPSK 50 24 56-69 56-83 59-213

1 8 PSK 100 36 84-102 84-124 88-318
2 16 QAM 100 50 114-139 115-168 120-434
3 32 QAM 150 65 150-183 151-222 158-571
4 64 QAM 200 80 184-225 186-272 194-702
5 128 QAM 225 97 223-273 225-330 234-849
6 256 QAM 225 111 240-293 242-355 252-914
7 512 QAM 300 123 277-338 279-409 291-1000
8 1024 QAM (Strong 300 131 301-368 303-445 316-1000
FEC)
9 1024 QAM (Light FEC) 300 139 320-391 322-473 336-1000
Page 270 of 322

9.3.2.6 40 MHz – Script ID 1217

required supported
0 QPSK 50 23 50-62 51-75 53-192

1 8 PSK 100 34 75-92 76-111 79-287
2 16 QAM 100 46 103-126 104-152 108-391
3 32 QAM 150 61 135-166 136-200 142-515
4 64 QAM 150 75 166-203 168-246 175-633
5 128 QAM 200 91 201-246 203-297 211-766
6 256 QAM 225 97 217-265 218-320 228-824
7 512 QAM 250 112 250-305 252-369 262-950
8 1024 QAM (Strong 300 122 272-332 274-402 286-1000
FEC)
9 1024 QAM (Light FEC) 300 130 288-353 291-426 303-1000
Note: MRMC script 1217 provides smaller bandwidth than MRMC

script 1207. Script 1217 can be used for interoperability with
existing equipment in the field. It is an Adjacent Channel script,
Page 271 of 322

9.3.2.7 56 MHz – Script ID 1203

required supported
0 QPSK 100 36 81-99 82-120 85-308

1 8 PSK 100 54 120-147 121-178 126-458
2 16 QAM 150 74 164-200 165-242 172-624
3 32 QAM 225 97 216-264 217-319 227-821
4 64 QAM 250 119 265-324 267-391 278-1000
5 128 QAM 300 144 320-391 323-473 336-1000
6 256 QAM 400 165 366-448 369-541 385-1000
7 512 QAM 400 179 398-486 401-588 418-1000
8 1024 QAM (Strong 450 195 432-529 436-639 454-1000
FEC)
9 1024 QAM (Light FEC) 450 206 459-561 463-678 482-1000
Page 272 of 322

9.3.2.8 56 MHz – Script ID 1206

required supported
0 QPSK 100 38 85-104 86-126 89-324

1 8 PSK 150 57 127-155 128-187 133-482
2 16 QAM 150 78 172-211 174-255 181-656
3 32 QAM 225 102 227-277 229-335 238-863
4 64 QAM 300 125 278-340 281-411 292-1000
5 128 QAM 350 151 337-412 339-498 354-1000
6 256 QAM 400 173 385-471 388-569 404-1000
7 512 QAM 400 188 418-511 421-618 439-1000
8 1024 QAM (Strong 450 205 455-556 458-672 477-1000
FEC)
9 1024 QAM (Light FEC) 500 217 483-590 486-713 507-1000
Page 273 of 322

9.4 Transmit Power Specifications (dBm)

Note: The values listed in this section are typical. Actual values may
differ in either direction by up to 1dB.
9.4.1 Transmit Power with RFU-C (dBm)
Table 64: Transmit Power with RFU-C (dBm)

Modulation 6L-8 10-15 18-23 24GHz 26 28 31 32 36 38 42
GHz GHz GHz UL37 GHz GHz GHz GHz GHz GHz GHz
QPSK 26 24 22 0 21 14 16 18 12 18 12
8 PSK 26 24 22 0 21 14 16 18 12 18 12
16 QAM 25 23 21 0 20 14 15 17 11 17 12
32 QAM 24 22 20 0 19 14 14 16 10 16 12
64 QAM 24 22 20 0 19 14 14 16 10 16 12
128 QAM 24 22 20 0 19 14 14 16 10 16 12
256 QAM 22 20 18 0 17 12 12 14 8 14 11
512 QAM 22 20 18 -1 17 9 12 14 10 14 11
1024 QAM 21 19 17 -3 16 8 11 13 9 13 10
2048 QAM 19 17 15 0 14 6 9 11 7 11 8
37
For 1ft ant or lower.
Customers in countries following EC Directive 2006/771/EC (incl. amendments) must
observe the 100mW EIRP obligation by adjusting transmit power according to antenna gain
and RF line losses.
Page 274 of 322

9.4.1.1 Pmin Power with RFU-C
Table 65: Pmin Power with RFU-C

Frequency Band Pmin Frequency Band Pmin
6 4 24 ETSI -39
7 4 26 -1
8 4 28 -2
10 2 31 5
11 2 32 -5
13 0 36 5
15 -7 38 0
18 -7 42 0
23 -7
Page 275 of 322

9.4.2 Transmit Power with 1500HP/RFU-HP (dBm)

Note: Transmit Power values shown in the tables below are measured
at the Antenna Port of the OCB (Port C’-C) in a 1+0 configuration.
The Transmit Power levels at the Tx Port of the RFU (Port A’) is
1.5 dB higher. For Transmit Power levels as measured at the Tx
Port of the RFU, see Annex 1: RFU-HP Transmit Power and RSL at
Radio Ports on page 317.
The following table provides transmit power specifications for RFU-HP 1RX (dBm).
Table 66: Transmit Power with 1500HP/RFU-HP (dBm)

Modulation 6L&H GHz 7 GHz 8 GHz 11 GHz38
QPSK 33 33 33 30
8 PSK 33 33 33 30
16 QAM 33 33 33 30
32 QAM 33 33 33 29
64 QAM 32 32 32 29
128 QAM 31 31 31 29
256 QAM 30 30 30 27
512 QAM 28 28 28 25
1024 QAM 27 27 27 24
2048 QAM 25 25 25 22
38
1500HP only.
Page 276 of 322

The following table provides transmit power specifications for RFU-HP 2RX
(1500HP) (dBm).
Table 67: Transmit Power for RFU-HP 2RX (1500HP) (dBm)

Modulation 6L&H GHz 7 GHz 8 GHz 11 GHz
QPSK 33 33 33 30
8 PSK 33 33 33 30
16 QAM 33 33 33 30
32 QAM 33 33 33 29
64 QAM 32 32 32 29
128 QAM 32 32 32 29
256 QAM 30 30 30 27
512 QAM 28 28 28 25
1024 QAM 27 27 27 24
2048 QAM 25 25 25 22
• These Transmit Power values are applicable to all RFU-HP and 1500HP
Marketing Models for both Split Mount and All Indoor for RFUs produced on
or after March 16, 2014. These RFUs have Serial Numbers starting with
F114xxxxxx and higher.
• The Transmit Power values for RFUs produced prior to March 16, 2014,
identified by lower Serial Numbers, are set forth in the Technical Descriptions
for FibeAir IP-10 products.
• When using Adjacent Channels (ACCP) configuration with 28/30 and 40 MHz
channel filters, the Transmit Power is 1 dB lower than the values shown in the
tables above. This limitation is not applicable to other channels.
Page 277 of 322

9.5 Receiver Threshold (RSL)

Notes: The RSL values listed in this section refer to fixed profiles. When
ACM is enabled, the RSL levels may be different when the radio
switches to other profiles.
The values listed in this section are typical. Actual values may
9.5.1 Receiver Thresholds with RFU-C
Table 68: Receiver Thresholds with RFU-C

Profile Modulation Channel 6 7-10 11-15 18 23 2439 26 28 31-42
Spacing GHz GHz GHz GHz GHz GHz GHz GHz GHz
0 QPSK 1.75 MHz -100.5 – -100.5 – – – – – –
1 16 QAM -94.0 – -94.0 – – – – – –
2 32 QAM -91.0 – -91.0 – – – – – –
3 64 QAM -87.5 – -87.5 – – – – – –
4 128 QAM -84.0 – -84.0 – – – – – –
5 256 QAM -80.5 – -80.5 – – – – – –
0 QPSK 3.5 MHz -97.5 -97.0 -97.5 -96.5 -96.0 -93.0 -95.0 -93.0 -94.0
1 16 QAM -91.0 -90.5 -91.0 -90.0 -89.5 -86.5 -88.5 -86.5 -87.5
2 32 QAM -88.0 -87.5 -88.0 -87.0 -86.5 -83.5 -85.5 -83.5 -84.5
3 64 QAM -84.5 -84.0 -84.5 -83.5 -83.0 -80.0 -82.0 -80.0 -81.0
4 128 QAM -81.0 -80.5 -81.0 -80.0 -79.5 -76.5 -78.5 -76.5 -77.5
5 256 QAM -77.5 -77.0 -77.5 -76.5 -76.0 -73.0 -75.0 -73.0 -74.0
39
Customers in countries following EC Directive 2006/771/EC (incl. amendments) must observe the
100mW EIRP obligation by adjusting transmit power according to antenna gain and RF line losses.
Page 278 of 322


0 QPSK 7 MHz -95 -94.5 -95 -94 -93.5 -90.5 -92.5 -90.5 -91.5
1 8 PSK -89 -88.5 -89 -88 -87.5 -84.5 -86.5 -84.5 -85.5
2 16 QAM -88.5 -88 -88.5 -87.5 -87 -84 -86.0 -84.0 -85.0
3 32 QAM -85 -84.5 -85 -84 -83.5 -80.5 -82.5 -80.5 -81.5
4 64 QAM -82 -81.5 -82 -81 -80.5 -77.5 -79.5 -77.5 -78.5
5 128 QAM -79 -78.5 -79 -78 -77.5 -74.5 -76.5 -74.5 -75.5
6 256 QAM -75.5 -75 -75.5 -74.5 -74 -71 -73.0 -71.0 -72.0
7 512 QAM -73.5 -73 -73.5 -72.5 -72 -69 -71.0 -69.0 -70.0
8 1024 QAM (Strong FEC) -70 -69.5 -70 -69 -68.5 -65.5 -67.5 -65.5 -66.5
9 1024 QAM (Light FEC) -69.5 -69 -69.5 -68.5 -68 -65 -67.0 -65.0 -66.0
0 QPSK 14 MHz -92.0 -91.5 -92.0 -91.0 -90.5 -87.5 -89.5 -87.5 -88.5
1 8 PSK -86.0 -85.5 -86.0 -85.0 -84.5 -81.5 -83.5 -81.5 -82.5
2 16 QAM -85.0 -84.5 -85.0 -84.0 -83.5 -80.5 -82.5 -80.5 -81.5
3 32 QAM -82.0 -81.5 -82.0 -81.0 -80.5 -77.5 -79.5 -77.5 -78.5
4 64 QAM -79.0 -78.5 -79.0 -78.0 -77.5 -74.5 -76.5 -74.5 -75.5
5 128 QAM -75.5 -75.0 -75.5 -74.5 -74.0 -71.0 -73.0 -71.0 -72.0
6 256 QAM -73.0 -72.5 -73.0 -72.0 -71.5 -68.5 -70.5 -68.5 -69.5
7 512 QAM -70.0 -69.5 -70.0 -69.0 -68.5 -65.5 -67.5 -65.5 -66.5
8 1024 QAM (Strong FEC) -67.0 -66.5 -67.0 -66.0 -65.5 -62.5 -64.5 -62.5 -63.5
9 1024 QAM (Light FEC) -66.5 -66.0 -66.5 -65.5 -65.0 -62.0 -64.0 -62.0 -63.0
0 QPSK 28 MHz -89.0 -88.5 -89.0 -88.0 -87.5 -84.5 -86.5 -84.5 -85.5
1 8 PSK -84.5 -84.0 -84.5 -83.5 -83.0 -80.0 -82.0 -80.0 -81.0
2 16 QAM -82.5 -82.0 -82.5 -81.5 -81.0 -78.0 -80.0 -78.0 -79.0
3 32 QAM -79.0 -78.5 -79.0 -78.0 -77.5 -74.5 -76.5 -74.5 -75.5
4 64 QAM -76.0 -75.5 -76.0 -75.0 -74.5 -71.5 -73.5 -71.5 -72.5
5 128 QAM -72.5 -72.0 -72.5 -71.5 -71.0 -68.0 -70.0 -68.0 -69.0
6 256 QAM -69.5 -69.0 -69.5 -68.5 -68.0 -65.0 -67.0 -65.0 -66.0
7 512 QAM -67.5 -67.0 -67.5 -66.5 -66.0 -63.0 -65.0 -63.0 -64.0
8 1024 QAM (Strong FEC) -64.5 -64.0 -64.5 -63.5 -63.0 -60.0 -62.0 -60.0 -61.0
9 1024 QAM (Light FEC) -63.5 -63.0 -63.5 -62.5 -62.0 -59.0 -61.0 -59.0 -60.0
10 2048 QAM -60 -59.5 -60 -59 -58.5 -55.5 -57.5 -55.5 -56.5
Page 279 of 322


0 QPSK 40 MHz -87.5 -87.0 -87.5 -86.5 -86.0 -80.5 -85.0 -83.0 -84.0
1 8 PSK -82.5 -82.0 -82.5 -81.5 -81.0 -75.5 -80.0 -78.0 -79.0
2 16 QAM -81.0 -80.5 -81.0 -80.0 -79.5 -74.0 -78.5 -76.5 -77.5
3 32 QAM -77.5 -77.0 -77.5 -76.5 -76.0 -70.5 -75.0 -73.0 -74.0
4 64 QAM -74.5 -74.0 -74.5 -73.5 -73.0 -67.5 -72.0 -70.0 -71.0
5 128 QAM -71.5 -71.0 -71.5 -70.5 -70.0 -64.5 -69.0 -67.0 -68.0
6 256 QAM -69.0 -68.5 -69.0 -68.0 -67.5 -62.0 -66.5 -64.5 -65.5
7 512 QAM -66.5 -66.0 -66.5 -65.5 -65.0 -59.5 -64.0 -62.0 -63.0
8 1024 QAM (strong FEC) -63.5 -63.0 -63.5 -62.5 -62.0 -56.5 -61.0 -59.0 -60.0
9 1024 QAM (light FEC) -62.5 -62.0 -62.5 -61.5 -61.0 -55.5 -60.0 -58.0 -59.0
10 2048 QAM -59.0 -58.5 -59.0 -58.0 -57.5 -52.0 -56.5 -54.5 -55.5
0 QPSK 56 MHz -85.5 -85.0 -85.5 -84.5 -84.0 -81.0 -83.0 -81.0 -82.0
1 8 PSK -81.5 -81.0 -81.5 -80.5 -80.0 -77.0 -79.0 -77.0 -78.0
2 16 QAM -79.0 -78.5 -79.0 -78.0 -77.5 -74.5 -76.5 -74.5 -75.5
3 32 QAM -75.5 -75.0 -75.5 -74.5 -74.0 -71.0 -73.0 -71.0 -72.0
4 64 QAM -72.5 -72.0 -72.5 -71.5 -71.0 -68.0 -70.0 -68.0 -69.0
5 128 QAM -69.5 -69.0 -69.5 -68.5 -68.0 -65.0 -67.0 -65.0 -66.0
6 256 QAM -66.5 -66.0 -66.5 -65.5 -65.0 -62.0 -64.0 -62.0 -63.0
7 512 QAM -64.5 -64.0 -64.5 -63.5 -63.0 -60.0 -62.0 -60.0 -61.0
8 1024 QAM (Strong FEC) -61.0 -60.5 -61.0 -60.0 -59.5 -56.5 -58.5 -56.5 -57.5
9 1024 QAM (Light FEC) -60 -59.5 -60 -59 -58.5 -55.5 -57.5 -55.5 -56.5
10 2048 QAM -55.5 -55 -55.5 -54.5 -54 -51 -53 -51 -52
Page 280 of 322

9.5.2 Receiver Thresholds with RFU-HP

RSL values shown in the tables below are measured at the Antenna Port of the
OCB (Port C’-C) in a 1+0 configuration. For RSL values as they may be measured at
the Tx Port (Port A’) and Rx Port (Port A) of the RFU, see Annex 1: RFU-HP
Transmit Power and RSL at Radio Ports on page 317.
Table 69: Receiver Thresholds with RFU-HP

Profile Modulation Channel 6 7 8 11
Spacing GHz GHz GHz GHz
0 QPSK 14 MHz -91.5 -91.0 -91.0 -91.0

1 8 PSK -86.5 -86.0 -86.0 -86.0
2 16 QAM -85.0 -84.5 -84.5 -84.5
3 32 QAM -81.5 -81.0 -81.0 -81.0
4 64 QAM -78.5 -78.0 -78.0 -78.0
5 128 QAM -75.0 -74.5 -74.5 -74.5
6 256 QAM -72.0 -71.5 -71.5 -71.5
7 512 QAM -69.5 -69.0 -69.0 -69.0
8 1024 QAM (strong FEC) -66.5 -66.0 -66.0 -66.0
9 1024 QAM (light FEC) -65.5 -65.0 -65.0 -65.0
0 QPSK 28 MHz -88.5 -88.0 -88.0 -88.0

1 8 PSK -83.5 -83.0 -83.0 -83.0
2 16 QAM -82 -81.5 -81.5 -81.5
3 32 QAM -78.5 -78.0 -78.0 -78.0
4 64 QAM -75.5 -75.0 -75.0 -75.0
5 128 QAM -72.5 -72.0 -72.0 -72.0
6 256 QAM -69.5 -69.0 -69.0 -69.0
7 512 QAM -67 -66.5 -66.5 -66.5
8 1024 QAM (strong FEC) -64 -63.5 -63.5 -63.5
9 1024 QAM (light FEC) -63.5 -63.0 -63.0 -63.0
10 2048 QAM -59.5 -59.0 -59.0 -59.0
Page 281 of 322

0 QPSK 40 MHz -87.0 -86.5 -86.5 -86.5

1 8 PSK -82.0 -81.5 -81.5 -81.5
2 16 QAM -80.5 -80.0 -80.0 -80.0
3 32 QAM -77.0 -76.5 -76.5 -76.5
4 64 QAM -74.0 -73.5 -73.5 -73.5
5 128 QAM -71.0 -70.5 -70.5 -70.5
6 256 QAM -68.5 -68.0 -68.0 -68.0
7 512 QAM -66.0 -65.5 -65.5 -65.5
8 1024 QAM (strong FEC) -63.0 -62.5 -62.5 -62.5
9 1024 QAM (light FEC) -62.0 -61.5 -61.5 -61.5
10 2048 QAM -58.5 -58.0 -58.0 -58.0
0 QPSK 56 MHz -85.5 -85.0 -85.0 n/a

1 8 PSK -80.5 -80.0 -80.0 n/a
2 16 QAM -79.0 -78.5 -78.5 n/a
3 32 QAM -75.5 -75.0 -75.0 n/a
4 64 QAM -72.0 -71.5 -71.5 n/a
5 128 QAM -69.5 -69.0 -69.0 n/a
6 256 QAM -66.5 -66.0 -66.0 n/a
7 512 QAM -64.0 -63.5 -63.5 n/a
8 1024 QAM (strong FEC) -61.0 -60.5 -60.5 n/a
9 1024 QAM (light FEC) -60.0 -59.5 -59.5 n/a
10 2048 QAM -56.5 -56.0 -56.0 n/a
• The Receiver Threshold values shown in the table above are measured at the
Antenna Port of the OCB (Port C’-C) in a 1+0 configuration. The Receiver
Thresholds at the Rx Port of the RFU (Port A) are 1.5 dB lower.
channel filters, the Receiver Threshold is 1 dB higher than the values shown in
the table above. This limitation is not applicable to other channels.
Page 282 of 322

9.5.3 Receiver Thresholds with 1500HP

RSL values shown in the tables below are measured at the Antenna Port of the
OCB (Port C’-C) in a 1+0 configuration. For RSL values as they may be measured at
the Tx Port (Port A’) and Rx Port (Port A) of the RFU, see Annex 1: RFU-HP
Transmit Power and RSL at Radio Ports on page 317.
Table 70: Receiver Thresholds with 1500HP

Profile Modulation Channel Spacing 6 7 8 11
GHz GHz GHz GHz
0 QPSK 14 MHz -91.0 -91.0 -91.0 -91.0

1 8 PSK -86.0 -86.0 -86.0 -86.0
2 16 QAM -84.5 -84.5 -84.5 -84.5
3 32 QAM -81.0 -81.0 -81.0 -81.0
4 64 QAM -78.0 -78.0 -78.0 -78.0
5 128 QAM -74.5 -74.5 -74.5 -74.5
6 256 QAM -71.5 -71.5 -71.5 -71.5
7 512 QAM -69.0 -69.0 -69.0 -69.0
8 1024 QAM (strong FEC) -66.0 -66.0 -66.0 -66.0
9 1024 QAM (light FEC) -65.0 -65.0 -65.0 -65.0
0 QPSK 28 MHz -88.0 -88.0 -88.0 -88.0

1 8 PSK -83.0 -83.0 -83.0 -83.0
2 16 QAM -81.5 -81.5 -81.5 -81.5
3 32 QAM -78.0 -78.0 -78.0 -78.0
4 64 QAM -75.0 -75.0 -75.0 -75.0
5 128 QAM -72.0 -72.0 -72.0 -72.0
6 256 QAM -69.0 -69.0 -69.0 -69.0
7 512 QAM -66.5 -66.5 -66.5 -66.5
8 1024 QAM (strong FEC) -63.5 -63.5 -63.5 -63.5
9 1024 QAM (light FEC) -63.0 -63.0 -63.0 -63.0
10 2048 QAM -59.0 -59.0 -59.0 -59.0
Page 283 of 322

0 QPSK 40 MHz -86.5 -86.5 -86.5 -86.5

1 8 PSK -81.5 -81.5 -81.5 -81.5
2 16 QAM -80.0 -80.0 -80.0 -80.0
3 32 QAM -76.5 -76.5 -76.5 -76.5
4 64 QAM -73.5 -73.5 -73.5 -73.5
5 128 QAM -70.5 -70.5 -70.5 -70.5
6 256 QAM -68.0 -68.0 -68.0 -68.0
7 512 QAM -65.5 -65.5 -65.5 -65.5
8 1024 QAM (strong FEC) -62.5 -62.5 -62.5 -62.5
9 1024 QAM (light FEC) -61.5 -61.5 -61.5 -61.5
10 2048 QAM -58.0 -58.0 -58.0 -58.0
• The Receiver Threshold values shown in the table above are measured at the
Antenna Port of the OCB (Port C’-C) in a 1+0 configuration. The Receiver
Thresholds at the Rx Ports of the RFU (Port A, AD) are 1.5 dB lower.
channel filters, the Receiver Threshold is 1 dB higher than the values shown in
the table above. This limitation is not applicable to other channels.
Page 284 of 322

9.6 Frequency Bands

This section outlines the supported tuning range of each RFU unit.
It should be noted that the RFUs are wide enough to support the entire frequency
band. The frequency restricting element in each system is either the diplexer
(RFU-C) or an OCB (RFU-HP).
9.6.1 Frequency Bands – RFU-C
Table 71: Frequency Bands – RFU-C

Frequency Band TX Range RX Range Tx/Rx Spacing
6L GHz 6332.5-6393 5972-6093 300A

5972-6093 6332.5-6393
6191.5-6306.5 5925.5-6040.5 266A
5925.5-6040.5 6191.5-6306.5
6303.5-6418.5 6037.5-6152.5
6037.5-6152.5 6303.5-6418.5
6245-6290.5 5939.5-6030.5 260A
5939.5-6030.5 6245-6290.5
6365-6410.5 6059.5-6150.5
6059.5-6150.5 6365-6410.5
6226.89-6286.865 5914.875-6034.825 252B
5914.875-6034.825 6226.89-6286.865
6345.49-6405.465 6033.475-6153.425
6033.475-6153.425 6345.49-6405.465
6181.74-6301.69 5929.7-6049.65 252A
5929.7-6049.65 6181.74-6301.69
6241.04-6360.99 5989-6108.95
5989-6108.95 6241.04-6360.99
6300.34-6420.29 6048.3-6168.25
6048.3-6168.25 6300.34-6420.29
6235-6290.5 5939.5-6050.5 240A
5939.5-6050.5 6235-6290.5
6355-6410.5 6059.5-6170.5
6059.5-6170.5 6355-6410.5
Page 285 of 322


6H GHz 6924.5-7075.5 6424.5-6575.5 500
6424.5-6575.5 6924.5-7075.5
7032.5-7091.5 6692.5-6751.5 340C
6692.5-6751.5 7032.5-7091.5
6764.5-6915.5 6424.5-6575.5 340B
6424.5-6575.5 6764.5-6915.5
6924.5-7075.5 6584.5-6735.5
6584.5-6735.5 6924.5-7075.5
6781-6939 6441-6599 340A
6441-6599 6781-6939
6941-7099 6601-6759
6601-6759 6941-7099
6707.5-6772.5 6537.5-6612.5 160A
6537.5-6612.5 6707.5-6772.5
6767.5-6832.5 6607.5-6672.5
6607.5-6672.5 6767.5-6832.5
6827.5-6872.5 6667.5-6712.5
6667.5-6712.5 6827.5-6872.5
7 GHz 7783.5-7898.5 7538.5-7653.5
7538.5-7653.5 7783.5-7898.5
7301.5-7388.5 7105.5-7192.5 196A
7105.5-7192.5 7301.5-7388.5
7357.5-7444.5 7161.5-7248.5
7161.5-7248.5 7357.5-7444.5
7440.5-7499.5 7622.5-7681.5
7678.5-7737.5 7496.5-7555.5
7496.5-7555.5 7678.5-7737.5
7580.5-7639.5 7412.5-7471.5 168C
7412.5-7471.5 7580.5-7639.5
7608.5-7667.5 7440.5-7499.5
7440.5-7499.5 7608.5-7667.5
7664.5-7723.5 7496.5-7555.5
7496.5-7555.5 7664.5-7723.5
Page 286 of 322


7609.5-7668.5 7441.5-7500.5 168B
7441.5-7500.5 7609.5-7668.5
7637.5-7696.5 7469.5-7528.5
7469.5-7528.5 7637.5-7696.5
7693.5-7752.5 7525.5-7584.5
7525.5-7584.5 7693.5-7752.5
7273.5-7332.5 7105.5-7164.5 168A
7105.5-7164.5 7273.5-7332.5
7301.5-7360.5 7133.5-7192.5
7133.5-7192.5 7301.5-7360.5
7357.5-7416.5 7189.5-7248.5
7189.5-7248.5 7357.5-7416.5
7280.5-7339.5 7119.5-7178.5 161P
7119.5-7178.5 7280.5-7339.5
7308.5-7367.5 7147.5-7206.5
7147.5-7206.5 7308.5-7367.5
7336.5-7395.5 7175.5-7234.5
7175.5-7234.5 7336.5-7395.5
7364.5-7423.5 7203.5-7262.5
7203.5-7262.5 7364.5-7423.5
7597.5-7622.5 7436.5-7461.5 161O
7436.5-7461.5 7597.5-7622.5
7681.5-7706.5 7520.5-7545.5
7520.5-7545.5 7681.5-7706.5
7587.5-7646.5 7426.5-7485.5 161M
7426.5-7485.5 7587.5-7646.5
7615.5-7674.5 7454.5-7513.5
7454.5-7513.5 7615.5-7674.5
7643.5-7702.5 7482.5-7541.5 161K
7482.5-7541.5 7643.5-7702.5
7671.5-7730.5 7510.5-7569.5
7510.5-7569.5 7671.5-7730.5
7580.5-7639.5 7419.5-7478.5 161J
Page 287 of 322


7419.5-7478.5 7580.5-7639.5
7608.5-7667.5 7447.5-7506.5
7447.5-7506.5 7608.5-7667.5
7664.5-7723.5 7503.5-7562.5
7503.5-7562.5 7664.5-7723.5
7580.5-7639.5 7419.5-7478.5 161I
7419.5-7478.5 7580.5-7639.5
7608.5-7667.5 7447.5-7506.5
7447.5-7506.5 7608.5-7667.5
7664.5-7723.5 7503.5-7562.5
7503.5-7562.5 7664.5-7723.5
7273.5-7353.5 7112.5-7192.5 161F
7112.5-7192.5 7273.5-7353.5
7322.5-7402.5 7161.5-7241.5
7161.5-7241.5 7322.5-7402.5
7573.5-7653.5 7412.5-7492.5
7412.5-7492.5 7573.5-7653.5
7622.5-7702.5 7461.5-7541.5
7461.5-7541.5 7622.5-7702.5
7709-7768 7548-7607 161D
7548-7607 7709-7768
7737-7796 7576-7635
7576-7635 7737-7796
7765-7824 7604-7663
7604-7663 7765-7824
7793-7852 7632-7691
7632-7691 7793-7852
7584-7643 7423-7482 161C
7423-7482 7584-7643
7612-7671 7451-7510
7451-7510 7612-7671
7640-7699 7479-7538
7479-7538 7640-7699
Page 288 of 322


7668-7727 7507-7566
7507-7566 7668-7727
7409-7468 7248-7307 161B
7248-7307 7409-7468
7437-7496 7276-7335
7276-7335 7437-7496
7465-7524 7304-7363
7304-7363 7465-7524
7493-7552 7332-7391
7332-7391 7493-7552
7284-7343 7123-7182 161A
7123-7182 7284-7343
7312-7371 7151-7210
7151-7210 7312-7371
7340-7399 7179-7238
7179-7238 7340-7399
7368-7427 7207-7266
7207-7266 7368-7427
7280.5-7339.5 7126.5-7185.5 154C
7126.5-7185.5 7280.5-7339.5
7308.5-7367.5 7154.5-7213.5
7154.5-7213.5 7308.5-7367.5
7336.5-7395.5 7182.5-7241.5
7182.5-7241.5 7336.5-7395.5
7364.5-7423.5 7210.5-7269.5
7210.5-7269.5 7364.5-7423.5
7594.5-7653.5 7440.5-7499.5 154B
7440.5-7499.5 7594.5-7653.5
7622.5-7681.5 7468.5-7527.5
7468.5-7527.5 7622.5-7681.5
7678.5-7737.5 7524.5-7583.5
7524.5-7583.5 7678.5-7737.5
7580.5-7639.5 7426.5-7485.5 154A
Page 289 of 322


7426.5-7485.5 7580.5-7639.5
7608.5-7667.5 7454.5-7513.5
7454.5-7513.5 7608.5-7667.5
7636.5-7695.5 7482.5-7541.5
7482.5-7541.5 7636.5-7695.5
7664.5-7723.5 7510.5-7569.5
7510.5-7569.5 7664.5-7723.5
8 GHz 8396.5-8455.5 8277.5-8336.5 119A
8277.5-8336.5 8396.5-8455.5
8438.5 – 8497.5 8319.5 – 8378.5
8319.5 – 8378.5 8438.5 – 8497.5
8274.5-8305.5 7744.5-7775.5 530A
7744.5-7775.5 8274.5-8305.5
8304.5-8395.5 7804.5-7895.5 500A
7804.5-7895.5 8304.5-8395.5
8023-8186.32 7711.68-7875 311C-J
7711.68-7875 8023-8186.32
8028.695-8148.645 7717.375-7837.325 311B
7717.375-7837.325 8028.695-8148.645
8147.295-8267.245 7835.975-7955.925
7835.975-7955.925 8147.295-8267.245
8043.52-8163.47 7732.2-7852.15 311A
7732.2-7852.15 8043.52-8163.47
8162.12-8282.07 7850.8-7970.75
7850.8-7970.75 8162.12-8282.07
8212-8302 7902-7992 310D
7902-7992 8212-8302
8240-8330 7930-8020
7930-8020 8240-8330
8296-8386 7986-8076
7986-8076 8296-8386
8212-8302 7902-7992 310C
7902-7992 8212-8302
Page 290 of 322


8240-8330 7930-8020
7930-8020 8240-8330
8296-8386 7986-8076
7986-8076 8296-8386
8380-8470 8070-8160
8070-8160 8380-8470
8408-8498 8098-8188
8098-8188 8408-8498
8039.5-8150.5 7729.5-7840.5 310A
7729.5-7840.5 8039.5-8150.5
8159.5-8270.5 7849.5-7960.5
7849.5-7960.5 8159.5-8270.5
8024.5-8145.5 7724.5-7845.5 300A
7724.5-7845.5 8024.5-8145.5
8144.5-8265.5 7844.5-7965.5
7844.5-7965.5 8144.5-8265.5
8302.5-8389.5 8036.5-8123.5 266C
8036.5-8123.5 8302.5-8389.5
8190.5-8277.5 7924.5-8011.5 266B
7924.5-8011.5 8190.5-8277.5
8176.5-8291.5 7910.5-8025.5 266A
7910.5-8025.5 8176.5-8291.5
8288.5-8403.5 8022.5-8137.5
8022.5-8137.5 8288.5-8403.5
8226.52-8287.52 7974.5-8035.5 252A
7974.5-8035.5 8226.52-8287.52
8270.5-8349.5 8020.5-8099.5 250A
10 GHz
10501-10563 10333-10395 168A
10333-10395 10501-10563
10529-10591 10361-10423
10361-10423 10529-10591
10585-10647 10417-10479
Page 291 of 322


10417-10479 10585-10647
10501-10647 10151-10297 350A
10151-10297 10501-10647
10498-10652 10148-10302 350B
10148-10302 10498-10652
10561-10707 10011-10157 550A
10011-10157 10561-10707
10701-10847 10151-10297
10151-10297 10701-10847
10590-10622 10499-10531 91A
10499-10531 10590-10622
10618-10649 10527-10558
10527-10558 10618-10649
10646-10677 10555-10586
10555-10586 10646-10677
11 GHz
11425-11725 10915-11207 All
10915-11207 11425-11725
11185-11485 10695-10955
10695-10955 11185-11485
13 GHz
13002-13141 12747-12866 266
12747-12866 13002-13141
13127-13246 12858-12990
12858-12990 13127-13246
12807-12919 13073-13185 266A
13073-13185 12807-12919
12700-12775 12900-13000 200
12900-13000 12700-12775
12750-12825 12950-13050
12950-13050 12750-12825
12800-12870 13000-13100
13000-13100 12800-12870
Page 292 of 322


12850-12925 13050-13150
13050-13150 12850-12925
15 GHz
15110-15348 14620-14858 490
14620-14858 15110-15348
14887-15117 14397-14627
14397-14627 14887-15117
15144-15341 14500-14697 644
14500-14697 15144-15341
14975-15135 14500-14660 475
14500-14660 14975-15135
15135-15295 14660-14820
14660-14820 15135-15295
14921-15145 14501-14725 420
14501-14725 14921-15145
15117-15341 14697-14921
14697-14921 15117-15341
14963-15075 14648-14760 315
14648-14760 14963-15075
15047-15159 14732-14844
14732-14844 15047-15159
15229-15375 14500-14647 728
14500-14647 15229-15375
18 GHz
19160-19700 18126-18690 1010
18126-18690 19160-19700
18710-19220 17700-18200
17700-18200 18710-19220
19260-19700 17700-18140 1560
17700-18140 19260-19700
23 GHz
23000-23600 22000-22600 1008
22000-22600 23000-23600
Page 293 of 322


22400-23000 21200-21800 1232 /1200
21200-21800 22400-23000
23000-23600 21800-22400
21800-22400 23000-23600
40
24UL GHz
24000 - 24250 24000 - 24250 All
26 GHz
25530-26030 24520-25030 1008
24520-25030 25530-26030
25980-26480 24970-25480
24970-25480 25980-26480
25266-25350 24466-24550 800
24466-24550 25266-25350
25050-25250 24250-24450
24250-24450 25050-25250
28 GHz
28150-28350 27700-27900 450
27700-27900 28150-28350
27950-28150 27500-27700
27500-27700 27950-28150
28050-28200 27700-27850 350
27700-27850 28050-28200
27960-28110 27610-27760
27610-27760 27960-28110
28090-28315 27600-27825 490
27600-27825 28090-28315
29004-29453 27996-28445 1008
27996-28445 29004-29453
28556-29005 27548-27997
40
Customers in countries following EC Directive 2006/771/EC (incl. amendments) must
observe the 100mW EIRP obligation by adjusting transmit power according to antenna gain
and RF line losses.
Page 294 of 322


27548-27997 28556-29005
29100-29125 29225-29250 125
29225-29250 29100-29125
31 GHz 31000-31085 31215-31300 175
31215-31300 31000-31085
32 GHz 31815-32207 32627-33019 812
32627-33019 31815-32207
32179-32571 32991-33383
32991-33383 32179-32571
38 GHz
39500-39600 38240-38340 1260
38240-38340 39500-39600
38820-39440 37560-38180
37560-38180 38820-39440
38316-38936 37045-37676
37045-37676 38316-38936
39650-40000 38950-39300 700
38950-39300 39500-40000
39300-39650 38600-38950
38600-38950 39300-39650
37700-38050 37000-37350
37000-37350 37700-38050
38050-38400 37350-37700
37350-37700 38050-38400
42 GHz 40550-41278 42050-42778 1500

42050-42778 40550-41278
41222-41950.5 42722-43450
42722-43450 41222-41950.5
Page 295 of 322

9.6.2 Frequency Bands – 1500HP and RFU-HP

Note: Channel spacing for 1500HP/RFU-HP is determined by the
branching network.
Table 72: Frequency Bands – 1500HP and RFU-HP

RFU Coverage Frequency Range Channel Bandwidth
(GHz)
L6 GHz 5.925 to 6.425 29.65/56 MHz

U6 GHz 6.425 to 7.125 20 MHz to
40/56 /60 MHz
7 GHz 7.425 to 7.900 14 MHz to 28/56 MHz
7.425 to 7.725 28/56 MHz
7.110 to 7.750 28/56 MHz
8 GHz 7.725 to 8.275 29.65 MHz
8.275 to 8.500 14 MHz to 28/56 MHz
7.900 to 8.400 14 MHz to 28/56 MHz
11 GHz 10.700 to 11.700 10 MHz to 40/56
Page 296 of 322

9.7 Mediation Device Losses
9.7.1 RFU-C Mediation Device Losses
Table 73: RFU-C Mediation Device Losses

Configuration Interfaces 5.7-8 11 GHz 13-15 18 23-26 28-38 42 GHz
GHz GHz GHz GHz GHz
Flex WG Remote Added on remote 0.5 0.5 1.2 1.2 1.5 1.8 2.5
Mount mount
antenna configurations
1+0 Direct Mount Integrated antenna 0.2 0.2 0.4 0.5 0.5 0.5 0.5
OMT Direct Mount Integrated antenna 0.3 0.3 0.3 0.3 0.5 0.5 0.5
Splitter Direct Mount Integrated antenna 3.6 3.7 3.7 3.7 3.7 4.0 4.0
Notes: The antenna interface is always the RFU-C interface.

If other antennas are to be used, an adaptor with a 0.1 dB loss
should be considered.
Page 297 of 322

9.7.2 1500HP/RFU-HP Branching Network Losses

When designing a link budget calculation, the branching loss (dB) should be
considered as per specific configuration. This section contains tables that list the
branching loss for the following Split-Mount configurations.
Table 74: 1500HP/RFU-HP Branching Network Losses

Interfaces 1+0 1+1 FD/ 2+1 3+1 4+1 5+1 6+1 7+1 8+1 9+1
2+0 3+0 4+0 5+0 6+0 7+0 8+0 9+0 10+0
CCDP with 0 (1c) 0 (1c) 0.5 0.5 1.0 1.0 1.5 1.5 2 (5c) 2 (6c)
DP Antenna (2c) (2c) (3c) (3c) (4c) (4c)
SP Non-Adjacent 0 (1c) 0.5 (2c) 1.0 1.5 2.0 NA NA NA NA NA

Channels (3c) (4c) (5c)
Notes:
• (c) – Radio Carrier
• CCDP – Co-channel dual polarization
• SP – Single pole antenna
• DP – Dual pole antenna
In addition, the following losses will be added when using these items:
Table 75: Additional Losses

Item Where to Use Loss (dB)
Flex WG All configurations 0.5

15m Coax cable Diversity path 6-8/11 GHz 5/6.5
Symmetrical Coupler Adjacent channel configuration. 3.5
Asymmetrical coupler 1+1 HSB configurations Main: 1.6
Coupled: 6.5
9.7.2.1 Adjacent Channels Implementation (ACCP)

The use of Adjacent Channel can be implemented using two methods:
1 Using Adjacent Channel OCBs (when the specific bands and channels
bandwidth is supported)
2 Using a Symmetrical Coupler.
Note: For a listing of which bands and channels support adjacent
channel OCBs, see OCB Part Numbers on page 65.
Page 298 of 322

Branching System using Adjacent Channel OCBs

When using Adjacent Channel OCBs, the OCBs are assembled using the standard
OCB components.
Branching System
F1 F2 F3 F4 F5
Figure 118: RFU-HP Branching System using Adjacent Channel OCBs
Branching System using Symmetrical Coupler

When using a Symmetrical coupler to support Adjacent Channels, the branching
system is split into two branching sub system, each built to support ACAP
configuration according to the following channels assignment:
Branching System #1
F1 F3 F5
Branching System #2
F2 F4 F6
Figure 119: RFU-HP Branching System using Symmetrical Coupler
Page 299 of 322

The following figure shows how to build a four-Adjacent Channel configuration

using a symmetrical coupler.
Figure 120: Four-Adjacent Channel Configuration using Symmetrical Coupler
Page 300 of 322

9.7.2.2 1500HP/RFU-HP All-Indoor Branching Loss

ICC has a 0 dB loss, since the RFU is calibrated to Pmax, together with the filter
and 1+0 branching loss. The following table presents the branching loss per
configuration and the Elliptical wave guide (WG) losses per meter which will be
add for each installation (dependent on the WG length).
Table 76: 1500HP/RFU-HP All-Indoor Branching Loss

Configuration Interfaces 1+0 1+1 2+1 3+1 4+1
FD 3+0 4+0 5+0
2+0
All-Indoor WG losses per 6L 4

100m
6H 4.5
7/8GHz 6
11GHz 10
Symmetrical Added to adjacent 3

Coupler channel configuration
CCDP with DP Tx and Rx 0.3 0.3 0.7 0.7 1.1

antenna (1c) (1c) (2c) (2c) (3c)
Diversity RX 0.2 0.2 0.6 0.6 1.0

(1c) (1c) (2c) (2c) (3c)
SP Non adjacent Tx and Rx 0.3 0.7 1.1 1.5 1.9

channels (1c) (2c) (3c) (4c) (5c)
Diversity RX 0.2 0.6 1.0 1.4 1.8

(1c) (2c) (3c) (4c) (5c)

antenna Upgrade (1c) (1c) (2c) (2c) (3c)
Ready
Diversity RX 0.2 0.6 1.0 1.0 1.4
(1c) (1c) (2c) (2c) (3c)
All-Indoor WG losses per 6L 4

100m
6H 4.5
7/8GHz 6
11GHz 10
Symmetrical Added to adjacent 3

Coupler channel configuration

antenna (3c) (4c) (4c) (5c) (6c)
Diversity RX 1.4 1.8 1.8 2.2 2.2

(3c) (4c) (4c) (5c) (6c)
SP Non adjacent Tx and Rx NA NA NA NA NA

channels
Diversity RX
Page 301 of 322

Configuration Interfaces 1+0 1+1 2+1 3+1 4+1

FD 3+0 4+0 5+0
2+0

antenna Upgrade (3c) (4c) (4c) (5c) (6c)
Ready
Diversity RX 1.4 1.8 1.8 2.2 2.2
(3c) (4c) (4c) (5c) (6c)
Page 302 of 322

9.8 Ethernet Latency Specifications
9.8.1 Ethernet Latency – 1.75 MHz Channel Bandwidth
Table 77: Ethernet Latency – 1.75 MHz Channel Bandwidth

ACM Modulation Latency (µsec) with GbE Interface
Working
Frame Size 64 128 256 512 1024 1518
Point
0 QPSK 2299 2589 3165 4313 6616 8845

1 16 QAM 1276 1399 1647 2141 3134 4091
2 32 QAM 1137 1223 1406 1772 2505 3213
3 64 QAM 1028 1102 1248 1543 2134 2703
4 128 QAM 964 1027 1149 1396 1892 2368
5 256 QAM 872 928 1036 1256
9.8.2 Ethernet Latency – 3.5 MHz Channel Bandwidth
Table 78: Ethernet Latency – 3.5 MHz Channel Bandwidth

Working
Frame Size 64 128 256 512 1024 1518
Point
0 QPSK 1355 1498 1785 2359 3517 4635

1 16 QAM 743 807 928 1180 1692 2186
2 32 QAM 655 701 794 981 1355 1715
3 64 QAM 600 635 708 862 1162 1452
4 128 QAM 563 593 655 783 1037 1281
5 256 QAM 508 537 592 707 931 1148
Page 303 of 322

9.8.3 Ethernet Latency – 7 MHz Channel Bandwidth
Table 79: Ethernet Latency – 7 MHz Channel Bandwidth

Working
Frame 64 128 256 512 1024 1518
Point
Size:
0 QPSK 924 987 1106 1353 1840 2317

1 8 PSK 678 718 799 969 1298 1623
2 16 QAM 525 549 604 728 962 1194
3 32 QAM 446 470 515 605 787 961
4 64 QAM 399 419 456 531 679 824
5 128 QAM 369 383 416 479 603 725
6 256 QAM 366 380 408 463 573 681
7 512 QAM 371 384 411 462 566 668
8 1024 QAM (Strong FEC) 352 366 390 439 538 633
9 1024 QAM (Light FEC) 349 360 384 430 524 613
Table 80: Ethernet Latency – 14 MHz Channel Bandwidth

Working
Frame 64 128 256 512 1024 1518
Point
Size:
0 QPSK 460 480 534 647 867 1086

1 8 PSK 346 364 402 479 629 778
2 16 QAM 265 278 307 364 477 588
3 32 QAM 233 244 267 312 401 487
4 64 QAM 213 222 241 279 353 426
5 128 QAM 193 202 219 251 315 377
6 256 QAM 177 184 199 228 286 341
7 512 QAM 209 216 230 256 310 361
8 1024 QAM (Strong FEC) 195 202 215 241 292 341
9 1024 QAM (Light FEC) 190 197 210 234 283 330
Page 304 of 322

Table 81: 28 MHz Channel Bandwidth

Working
Frame Size 64 128 256 512 1024 1518
Point
0 QPSK 154 169 198 257 373 484

1 8 PSK 130 141 162 204 286 363
2 16 QAM 109 117 133 166 231 290
3 32 QAM 105 111 125 152 204 252
4 64 QAM 101 107 119 142 187 228
5 128 QAM 95 100 110 131 171 207
6 256 QAM 89 94 103 123 160 193
7 512 QAM 113 117 126 145 179 210
8 1024 QAM (Strong 104 108 117 135 168 198
FEC)
9 1024 QAM (Light 106 110 118 136 168 197
FEC)
10 2048 QAM 99 104 111 127 157 182

Working
Point Frame Size: 64 128 256 512 1024 1518
0 QPSK 194 206 230 278 373 465

1 8 PSK 147 156 173 208 277 342
2 16 QAM 120 126 139 165 216 267
3 32 QAM 108 113 124 144 186 226
4 64 QAM 100 104 113 131 166 201
5 128 QAM 92 96 104 120 151 181
6 256 QAM 95 100 106 120 149 177
7 512 QAM 100 104 111 124 151 178
8 1024 QAM (strong 93 96 102 116 141 166
FEC)
9 1024 QAM (light FEC) 95 97 104 116 141 166
10 2048 QAM 81 85 92 105 131 153
Page 305 of 322


Working
Frame Size: 64 128 256 512 1024 1518
Point
0 QPSK 94 102 119 152 216 275

1 8 PSK 83 89 102 127 174 218
2 16 QAM 72 77 87 108 146 182
3 32 QAM 69 73 82 99 133 162
4 64 QAM 66 69 77 93 123 149
5 128 QAM 65 68 75 90 116 140
6 256 QAM 61 64 71 84 110 132
7 512 QAM 69 72 78 92 116 137
8 1024 QAM (Strong 65 68 74 87 110 131
FEC)
10 2048 62 66 72 83 105 124
Page 306 of 322

9.9 Ethernet Specifications
9.9.1 Ethernet Interface Specifications
Table 84: Ethernet Interface Specifications
Supported Ethernet Interfaces for Traffic 4 x 10/100/1000Base-T (RJ-45) and

2 x 1000base-X (SFP)
Supported Ethernet Interfaces for Management 2 x 10/100 Base-T (RJ-45)
Supported SFP Types See Approved GbE SFP Modules on page 308
9.9.2 Carrier Ethernet Functionality
Table 85: Carrier Ethernet Functionality
Switching capacity 5 Gbps

"Jumbo" Frame Support Up to 9600 Bytes
General Header De-Duplication
Integrated Carrier Ethernet MAC address learning with 128K MAC addresses
Switch 802.1ad provider bridges (QinQ)
802.3ad link aggregation
QoS Advanced CoS classification and remarking
Per interface CoS based packet queuing/buffering (8 queues)
Per queue statistics
Tail-drop and WRED with CIR/EIR support
Flexible scheduling schemes (SP/WFQ/Hierarchical)
Per interface and per queue traffic shaping
Hierarchical-QoS (H-QoS) – Up to 2K service level queues41
2 Gbit packet buffer
Network resiliency MSTP
ERP (G.8032)
Service OAM FM (Y.1731)
PM (Y.1731) 42
Performance Monitoring Per port Ethernet counters (RMON/RMON2)
Radio ACM statistics
Enhanced radio Ethernet statistics (Frame Error Rate, Throughput,
Capacity, Utilization)
41
Planned for future release.
42
PM is planned for future release.
Page 307 of 322

9.9.3 Approved GbE SFP Modules
Table 86: Approved GbE SFP Modules

Part Number Marketing Marketing Item Description
Model Description
AO-0058-0 SFP-GE-ZX SFP optical interface XCVR,SFP,1550nm,2.125G,SM,80km,W.DD

1000Base-ZX M
AO-0068-0 SFP-GE-ELC- SFP ELECT INT XCVR,SFP,COOPER 1000BASE-
RXLE 1000Base-T RX_LOS T,RX_LOS ENABLED
enabled
AO-0193-0 SFP-BX-U- SFP SM Fiber, XCVR,SFP,SINGLE FIBER,1310nm
OPT 1310nm TX, 1490nm TX/1490nm
RX RX,1.25Gb,SM,10km,W.DDM,COMMERCIA
L,SINGLE PACK KIT
AO-0194-0 SFP-BX-D- SFP SM Fiber, XCVR,SFP,SINGLE FIBER,1490nm
OPT 1310nm RX, 1490nm TX/1310nm
TX RX,1.25Gb,SM,10km,W.DDM,COMMERCIA
L,SINGLE PACK KIT
AO-0226-0 SFP-GE- SFP GE CWDM, XCVR,SFP,1510nm,GE,SM,CWDM,120km,W
CWDM- 120Km, 1510nm .DDM,COMMERCIAL TEMP
120km-
1510nm
ER-8003-0 SFP-GE-ELC SFP electrical SFP 1000BASE-T 1.25 GBd Small
interface 1000Base- FormPluggable Low Voltage (3.3 V)
T ElectricalTransceiver over Category 5 Cable
with package
ER-8000-0 SFP-GE-SX SFP optical interface XCVR,SFP,850nm,MM,1.0625 Gbit/s FC/
1000Base-SX 1.25 GBE,PACKED
ER-1002-0 SFP-GE-LX SFP optical interface XCVR,SFP,1310nm,1.25Gb,SM,10km,W.DD
1000Base-LX*ROHS M, SINGLE PACK KIT
Note: Ceragon recommends the use of SFP modules certified by

Ceragon, as listed above.
Page 308 of 322

9.10 TDM Specifications
9.10.1 E1 Cross Connect
Table 87: E1 Cross Connect Specifications
E1 Cross Connect Capacity 256 E1 Trails (VCs)

E1 Trails Protection 1+1 / 1:1
9.10.2 E1 Interface Specifications
Table 88: E1 Interface Specifications
Interface Type E1
Number of Ports 16 x E1s
Connector Type MDR 69-pin
Framing Framed / Unframed
Coding HDB3
Line Impedance 120 ohm/100 ohm balanced. Optional 75 ohm unbalanced supported
using panel with integrated impedance adaption.
Compatible Standards ITU-T G.703, G.736, G.775, G.823, G.824, G.828, ITU-T I.432, ETSI ETS
300 147, ETS 300 417, Bellcore GR-253-core, TR-NWT-000499
9.10.3 Pseudowire Specifications
Table 89: Pseudowire Specifications
Circuit-Emulation Modes RFC 4553 – SAToP

RFC 5086 – CESoP43
Circuit-Emulation Ethernet (MEF-8)
Encapsulations IP/UDP44
MPLS (MFA-8)45
Frame payload size Configurable – 1 E1 frame (256 bytes) to 64 frames (8192 bytes)
De-Jitter buffer size Configurable – 1 ms to 32 ms
43
CESoP mode is planned for future release.
44
IP/MPLS encapsulation is planned for future release.
45
MFA-8 encapsulation is planned for future release.
Page 309 of 322

9.11 Synchronization Specifications

Table 90: Synchronization Specifications
Sync Unit / SyncE ITU-T G.8261
Page 310 of 322

9.12 Mechanical Specifications

Table 91: IDU Mechanical Specifications
IDU Dimensions Height: 44 mm (1RU)

Width: 426 mm
Depth: 180 mm
Weight: 2.5 kg
IDU-RFU Coaxial cable RG-223 (300 ft), Belden 9914/RG-8 (1000 ft) or equivalent, TNC
Connection connectors to the IDU and the RFU.
Table 92: RFU-C Mechanical Specifications
RFU-C Dimensions Height: 200 mm

Width: 200 mm
Depth: 85 mm
Weight: 4kg/9 lbs.
RFU-C Standard 50 mm-120 mm/2”-4.5” (subject to vendor and antenna size)
Mounting OD Pole
Table 93: 1500HP/RFUHP Mechanical Specifications
1500HP/RFU-HP Height: 490 mm

Dimensions Width: 144 mm
Depth: 280 mm
Weight: 7 kg (excluding Branching)
1500HP/RFU-HP Height: 420 mm
OCB Branching Width: 110 mm
(Split Mount and
Depth: 380 mm
Compact All-
Indoor ) Weight: 7 kg
Recommended torque for RFU-OCB connection: 17 Nm
1500HP/RFU-HP 76-114 mm (subject to vendor and antenna size)
Standard
Mounting OD Pole
Page 311 of 322

9.13 Environmental Specifications
9.13.1 Environmental Specifications for IDU

• Temperature:
◦ -5C (23F) to 55C (131F) – Temperature range for continuous operating
temperature with high reliability.
◦ -25C (-13F) to 65C (149F) – Temperature range for exceptional
temperatures, tested successfully, with limited margins.
Note: Cold startup requires at least -5C (23F)
• Humidity: 5%RH to 95%RH
9.13.2 Environmental Specifications for RFU

• Temperature:
◦ -33C (-27F) to +55C (131F) – Temperature range for continuous
operating temperature with high reliability:
◦ -45C (-49F) to +60C (140F) – Temperature range for exceptional
temperatures; tested successfully, with limited margins:
• Humidity: 5%RH to 100%RH
Page 312 of 322

9.14 Supported Antenna Types
9.14.1 RFU-C Antenna Connection

RFU-C uses CommScope, RFS, Xian Putian, and Radio Wave antennas.
RFU-C can be mounted directly for all frequencies (6-42 GHz) using the following
antenna types (for integrated antennas, specific antennas PNs are required):
• CommScope: VHLP series
• Radio Wave
• Xian Putian: WTG series
9.14.2 1500HP/RFU-HP Antenna Connection

All Ceragon approved high performance remote mount antenna types can be used
with the 155HP/RFU-HP (RL>30dB).
Page 313 of 322

9.15 Waveguide Specifications
9.15.1 RFU-C Waveguide Specifications

For remote mount installations, the following flexible waveguide flanges should
be used (millimetric). The same antenna type (integrated) as indicated above can
be used (recommended).
Other antenna types using the flanges listed in the table below may be used.
Table 94: RFU-C – Waveguide Flanges

Frequency (GHz) Waveguide Standard Waveguide Flange Antenna Flange
6 WR137 PDR70 UDR70

7/8 WR112 PBR84 UBR84
10/11 WR90 PBR100 UBR100
13 WR75 PBR120 UBR120
15 WR62 PBR140 UBR140
18-26 WR42 PBR220 UBR220
28-38 WR28 PBR320 UBR320
42 WR22 UG383/U UG383/U
If a different antenna type (CPR flange) is used, a flange adaptor is required.
9.15.2 1500HP/RFU-HP Waveguide Specifications

The radio output port (C – Carrier) is frequency dependent, and is terminated with
the following waveguide flanges:
Table 95: 1500HP/RFU-HP – Waveguide Flanges

Frequency Band (GHz) Waveguide Flanges
6L CPR137
6H CPR137
7 CPR112
8 CPR112
11 CPR90
Page 314 of 322

9.16 Antenna Interface Requirements for RFU-HP/1500HP

The following table summarizes the return loss requirements for the antennas.
The return loss figures listed below are measured at the antenna’s waveguide
interface (C, C’ Points) of the system.
Table 96: 1500HP/RFU-HP Antenna Interface Requirements

Installation Type No of Carriers
1 2 3 4 5 6 7 8 9 10
All Indoor (dB) 26 26 26 26 26 26 26 26 26 26

Split Mount (dB) 17 17 17 17 17 17 17 17 17 17
Page 315 of 322

9.17 Power Input Specifications

Table 97: Power Input Specifications
IDU Standard Input -48 VDC

IDU DC Input range -40 to --60 VDC
RFU-C Operating Range -40.5 to -59 VDC
RFU-HP Operating Range -40.5 to -59 VDC
9.18 Power Consumption Specifications

The following table shows the maximum power consumption for IP-20G IDU and
supported RFUs. The maximum power consumption for the entire system is the
sum of the IDU and the RFUs connecting to it.
Table 98: Power Consumption Specifications

Configuration Power (W) Comments
IDU Eth-only with single modem 23.5W

Addition for second modem 2.9W
Addition for 16 E1s 11W
RFU-C 6-26 GHz 1+0: 22 RFU only.
1+1: 39
28-42 GHz 1+0: 26
1+1: 43
1500HP Max Bias: 85W RFU only
Min Bias: 72W
Mute: 29W
RFU-HP 6-8 GHz Max Bias: 73W RFU only.
Mid Bias: 48W
Min Bias: 34W
Mute: 18W
11 GHz Max Bias: 74W
Min Bias: 64W
Mute: 21W
Page 316 of 322

10. Annex 1: RFU-HP Transmit Power and RSL at Radio

Ports
The Transmit Power and Receive Threshold Levels shown in this Annex refer to
the Transmit Power and Receive Threshold Levels as they may be measured at the
Tx Port (Port A’) and Rx Port (Port A) of the RFU.
For Transmit Power values as measured at the Antenna Port of the OCB (Port C’-
C) in a 1+0 configuration, see Transmit Power with 1500HP/RFU-HP (dBm) on
page 276.
For RSL values as measured at the Antenna Port of the OCB (Port C’-C) in a 1+0
configuration, see Receiver Thresholds with RFU-HP on page 281 and Receiver
Thresholds with 1500HP on page 283.
10.1 Transmit Power Specifications (dBm)

The Transmit Power values shown in the tables below refers to the Transmit
Power levels at the Tx Port of the RFU (Port A’).
The Transmit Power values shown in the Web EMS or NMS refer to the Tx Power
as measured at the Antenna Port (Port C’) of the OCB at a 1+0 configuration and
may be up to 2 dB lower than then the values shown in the following tables.
The following table provides transmit power specifications for RFU-HP 1RX (dBm).
Table 99: Transmit Power Specifications for RFU-HP 1RX (dBm)

Modulation 6L&H GHz 7 GHz 8 GHz 11 GHz46
QPSK 34.5 34.5 34.5 30.5

8 PSK 34.5 34.5 34.5 30.5
16 QAM 34.5 34.5 34.5 30.5
32 QAM 34.5 34.5 34.5 30.5
64 QAM 33.5 33.5 33.5 30.5
128 QAM 32.5 32.5 32.5 29.5
256 QAM 31.5 31.5 31.5 28.5
512 QAM 29.5 29.5 29.5 26.5
1024 QAM 28.5 28.5 28.5 26.5
2048 QAM 26.5 26.5 26.5 24.5
46
1500HP only.
Page 317 of 322

The following table provides transmit power specifications for RFU-HP 2RX
(1500HP) (dBm).
Table 100: Transmit power specifications for RFU-HP 2RX (1500HP) (dBm)
Modulation 6L&H GHz 7 GHz 8 GHz 11 GHz
QPSK 34.5 34.5 34.5 30.5

8 PSK 34.5 34.5 34.5 30.5
16 QAM 34.5 34.5 34.5 30.5
32 QAM 34.5 34.5 34.5 30.5
64 QAM 34.5 34.5 34.5 30.5
128 QAM 33.5 33.5 33.5 29.5
256 QAM 32.5 32.5 32.5 28.5
512 QAM 30.5 30.5 30.5 26.5
1024 QAM 29.5 29.5 29.5 26.5
2048 QAM 27.5 27.5 27.5 24.547
• These Transmit Power values are applicable to all RFU-HP and 1500HP
Marketing Models for both Split Mount and All Indoor for RFUs produced on
or after March 16, 2014. These RFUs have Serial Numbers starting with
F114xxxxxx and higher.
• The Transmit Power values for RFUs produced prior to March 16, 2014,
identified by lower Serial Numbers, are set forth in the Technical Descriptions
for FibeAir IP-10 products.
For System Gain calculations, use the Transmit Power
specifications as listed in Section 9.4 and the branching losses as
listed in 1500HP/RFU-HP Branching Network Losses on page 298.
47
1500HP only.
Page 318 of 322

10.2 Receiver Threshold Specifications

The Receiver Threshold values shown in the tables below refer to the Receiver
Threshold levels at the Rx Port of the RFU (Port A).
For System Gain calculations, please use the Transmit Power
specifications as listed in Section 9.4.2 and the branching losses
as listed in 1500HP/RFU-HP Branching Network Losses on
page 298.
10.2.1 Receiver Threshold – RFU-HP
Table 101: Receiver Threshold – RFU-HP

Profile Modulation Channel Frequency (GHz)
Spacing
6 7 8 11
0 QPSK 14 MHz -93 -92.5 -92.5 -92.5

1 8 PSK -87 -86.5 -86.5 -86.5
2 16 QAM -86 -85.5 -85.5 -85.5
3 32 QAM -83 -82.5 -82.5 -82.5
4 64 QAM -80 -79.5 -79.5 -79.5
5 128 QAM -76.5 -76 -76 -76
6 256 QAM -74 -73.5 -73.5 -73.5
7 512 QAM -71 -70.5 -70.5 -70.5
8 1024 QAM (strong FEC) -68 -67.5 -67.5 -67.5
9 1024 QAM (light FEC) -67.5 -67 -67 -67
0 QPSK 28 MHz -90 -89.5 -89.5 -89.5

1 8 PSK -85.5 -85 -85 -85
2 16 QAM -83.5 -83 -83 -83
3 32 QAM -80 -79.5 -79.5 -79.5
4 64 QAM -77 -76.5 -76.5 -76.5
5 128 QAM -74 -73.5 -73.5 -73.5
6 256 QAM -71 -70.5 -70.5 -70.5
7 512 QAM -68.5 -68 -68 -68
8 1024 QAM (strong FEC) -65.5 -65 -65 -65
9 1024 QAM (light FEC) -64.5 -64 -64 -64
10 2048 QAM -61 -60.5 -60.5 -60.5
Page 319 of 322


Spacing
6 7 8 11
0 QPSK 40 MHz -88.5 -88 -88 -88

1 8 PSK -83.5 -83 -83 -83
2 16 QAM -82 -81.5 -81.5 -81.5
3 32 QAM -78.5 -78 -78 -78
4 64 QAM -75.5 -75 -75 -75
5 128 QAM -72.5 -72 -72 -72
6 256 QAM -69.5 -69 -69 -69
7 512 QAM -66.5 -66 -66 -66
8 1024 QAM (strong FEC) -64 -63.5 -63.5 -63.5
9 1024 QAM (light FEC) -63 -62.5 -62.5 -62.5
10 2048 QAM -60.5 -60 -60 -60
0 QPSK 56 MHz -86.5 -86 -86 -

1 8 PSK -82.5 -82 -82 -
2 16 QAM -80 -79.5 -79.5 -
3 32 QAM -77 -76.5 -76.5 -
4 64 QAM -73.5 -73 -73 -
5 128 QAM -71 -70.5 -70.5 -
6 256 QAM -67.5 -67 -67 -
7 512 QAM -65.5 -65 -65 -
8 1024 QAM (strong FEC) -62 -61.5 -61.5 -
9 1024 QAM (light FEC) -61 -60.5 -60.5 -
10 2048 QAM -56.5 -56 -56 -
Page 320 of 322

10.2.2 Receiver Threshold – 1500HP
Table 102: Receiver Threshold – 1500HP

Spacing
6 7 8 11
0 QPSK 14 MHz -92.5 -92.5 -92.5 -92.5

1 8 PSK -86.5 -86.5 -86.5 -86.5
2 16 QAM -85.5 -85.5 -85.5 -85.5
3 32 QAM -82.5 -82.5 -82.5 -82.5
4 64 QAM -79.5 -79.5 -79.5 -79.5
5 128 QAM -76 -76 -76 -76
6 256 QAM -73.5 -73.5 -73.5 -73.5
7 512 QAM -70.5 -70.5 -70.5 -70.5
8 1024 QAM (strong FEC) -67.5 -67.5 -67.5 -67.5
9 1024 QAM (light FEC) -67 -67 -67 -67
0 QPSK 28 MHz -89.5 -89.5 -89.5 -89.5

1 8 PSK -85 -85 -85 -85
2 16 QAM -83 -83 -83 -83
3 32 QAM -79.5 -79.5 -79.5 -79.5
4 64 QAM -76.5 -76.5 -76.5 -76.5
5 128 QAM -73.5 -73.5 -73.5 -73.5
6 256 QAM -70.5 -70.5 -70.5 -70.5
7 512 QAM -68 -68 -68 -68
8 1024 QAM (strong FEC) -65 -65 -65 -65
9 1024 QAM (light FEC) -64 -64 -64 -64
10 2048 QAM -60.5 -60.5 -60.5 -60.5
Page 321 of 322


Spacing
6 7 8 11
0 QPSK 40 MHz -88 -88 -88 -88

1 8 PSK -83 -83 -83 -83
2 16 QAM -81.5 -81.5 -81.5 -81.5
3 32 QAM -78 -78 -78 -78
4 64 QAM -75 -75 -75 -75
5 128 QAM -72 -72 -72 -72
6 256 QAM -69 -69 -69 -69
7 512 QAM -66 -66 -66 -66
8 1024 QAM (strong FEC) -63.5 -63.5 -63.5 -63.5
9 1024 QAM (light FEC) -62.5 -62.5 -62.5 -62.5
10 2048 QAM -60 -60 -60 -60
Page 322 of 322

Ceragon FibeAir IP-20G Technical Description 11.1 ETSI Rev A.01 PDF

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Ceragon FibeAir IP-20G Technical Description 11.1 ETSI Rev A.01 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ceragon FibeAir IP-20G Technical Description 11.1 ETSI Rev A.01 PDF

Uploaded by

Copyright:

Available Formats

Technical Description

April 2020 | ETSI Version

Open Source Statement

Ceragon Proprietary and Confidential

3. IDU Hardware Description ....................................................................................... 31

4. RFU Hardware Description and Branching Options ................................................... 48

Ceragon Proprietary and Confidential

4.3 RFU-C ......................................................................................................................................... 51

5. Activation Keys ....................................................................................................... 67

Ceragon Proprietary and Confidential

6.4.2 IP-20G Synchronization Solution..............................................................................................193

7. FibeAir IP-20G Management.................................................................................. 224

Ceragon Proprietary and Confidential

8. Standards and Certifications .................................................................................. 250

Ceragon Proprietary and Confidential

9.12 Mechanical Specifications ........................................................................................................311

Ceragon Proprietary and Confidential

Ceragon Proprietary and Confidential

Figure 36: Multi-Carrier ABC Traffic Flow...............................................................................................95

Ceragon Proprietary and Confidential

Ceragon Proprietary and Confidential

Ceragon Proprietary and Confidential

Ceragon Proprietary and Confidential

Table 34: Boundary Clock Input Options ------------------------------------------------------------------------------ 207

Ceragon Proprietary and Confidential

Table 71: Frequency Bands – 1500HP and RFU-HP ---------------------------------------------------------------- 296

Ceragon Proprietary and Confidential

About This Guide

What You Should Know

Ceragon Proprietary and Confidential

1. Synonyms and Acronyms

ACAP Adjacent Channel Alternate Polarization

Ceragon Proprietary and Confidential

FEC Forward Error Correction

Ceragon Proprietary and Confidential

QoS Quality of Service

Ceragon Proprietary and Confidential

This chapter includes:

Ceragon Proprietary and Confidential

2.1 Product Overview

Ceragon Proprietary and Confidential

IP-20G provides an innovative packet backhaul services aggregation solution that

2.1.1 IP-20G Radio Options

For additional information:

Ceragon Proprietary and Confidential

For additional information:

2.1.2 FibeAir IP-20G Interoperability with other Ceragon Products

2.1.3 IP-20G Highlights

2.1.4 IP-20G Protection Options

Ceragon Proprietary and Confidential

Ceragon Proprietary and Confidential

2.2 Reference Configurations

2.2.1 Dual Modem Activation

Figure 1: Reference Configuration – Dual Modem Activation

2.2.2 IDU Dual-Modem Cascading Link

Ceragon Proprietary and Confidential

IP-20G IDU 1+0