Technical Description

FibeAir® IP-20C

April 2019 | ETSI Version

CeraOS Release: 10.7 | Rev A
© Copyright 2019 by Ceragon Networks Ltd. All rights reserved.
Technical Description for FibeAir IP-20C, CeraOS 10.7 (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 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Table of Contents
1. Synonyms and Acronyms ........................................................................................ 15
2. Introduction............................................................................................................ 18
2.1 Product Overview ...................................................................................................................... 18
2.2 Unique IP-20C Feature Set ......................................................................................................... 19
2.3 System Configurations ............................................................................................................... 20
2.3.1 MultiCore 2+0 Single or Dual Polarization Direct Mount ........................................................... 21
2.3.2 2 x MultiCore 2+0 Single Polarization ........................................................................................ 22
2.3.3 2 x MultiCore 2+0 Dual Polarization .......................................................................................... 23
2.3.4 MultiCore 2+2 HSB Single Polarization ...................................................................................... 24
2.3.5 MultiCore 2+2 HSB Dual Polarization XPIC ................................................................................ 25
2.3.6 1+1 HSB-SD ................................................................................................................................ 26
2.3.7 4x4 LoS MIMO ............................................................................................................................ 27
2.3.8 2x2 LoS MIMO ............................................................................................................................ 28
2.4 FibeAir IP-20C Interoperability with Other Ceragon Products ................................................... 29
2.5 FibeAir IP-20 Assured Platform .................................................................................................. 30
2.6 New Features in CeraOS 10.5.5 and 10.7................................................................................... 31

3. IP-20C Hardware Description ................................................................................... 32

3.1 IP-20C Unit Description .............................................................................................................. 32
3.1.1 Hardware Architecture .............................................................................................................. 33
3.1.2 Interfaces ................................................................................................................................... 34
3.1.3 Channel-Port Mapping to Polarization ...................................................................................... 37
3.1.4 Management Connection for 4x4 MIMO and 1+1/2+2 HSB Configurations ............................. 39
3.2 MultiCore Mediation Devices (MCMD) ...................................................................................... 41
3.3 PoE Injector ................................................................................................................................ 43
3.3.1 PoE Injector Interfaces ............................................................................................................... 43
3.4 Voltage Alarm Thresholds and PMs ........................................................................................... 44
3.5 Offshore and ATEX Compatibility ............................................................................................... 45
3.5.1 Offshore Durability .................................................................................................................... 45
3.5.2 ATEX Zone II Certification........................................................................................................... 45

4. Activation Keys ....................................................................................................... 46

4.1 Working with Activation Keys .................................................................................................... 46
4.2 Demo Mode ............................................................................................................................... 46
4.3 Activation Key Reclaim ............................................................................................................... 47
4.4 Activation Key-Enabled Features ............................................................................................... 47

5. Feature Description................................................................................................. 53
5.1 Unique MultiCore Architecture.................................................................................................. 53
5.1.1 Flexible Operating Modes with MultiCore Architecture ............................................................ 54
5.1.2 TCO Savings as a Result of MultiCore Architecture ................................................................... 57
5.2 Innovative Techniques to Boost Capacity and Reduce Latency ................................................. 59

Page 3 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.1 Capacity Summary ..................................................................................................................... 60

5.2.2 Line of Sight (LoS) MIMO ........................................................................................................... 60
5.2.3 Space Diversity ........................................................................................................................... 69
5.2.4 Advanced Space Diversity (ASD) ................................................................................................ 72
5.2.5 Advanced Frequency Reuse (AFR) ............................................................................................. 74
5.2.6 Header De-Duplication............................................................................................................... 81
5.2.7 Frame Cut-Through .................................................................................................................... 84
5.2.8 Multi-Carrier ABC ....................................................................................................................... 86
5.2.9 Adaptive Coding Modulation (ACM) .......................................................................................... 91
5.2.10 Multiband (Enhanced Multi-Carrier ABC) .................................................................................. 95
5.2.10.1 Multiband Operation ............................................................................................... 95
5.2.10.2 Synchronization with Multiband Operation ............................................................ 97
5.2.10.3 Multiband Management .......................................................................................... 98
5.2.10.4 Limitations and Interoperability of Multiband with other Features ........................ 98
5.2.11 Cross Polarization Interference Canceller (XPIC) ....................................................................... 99
5.2.12 Unit (External) Protection ........................................................................................................102
5.2.13 ATPC .........................................................................................................................................106
5.2.14 Radio Signal Quality PMs .........................................................................................................107
5.2.15 Radio Utilization PMs ...............................................................................................................108
5.3 Ethernet Features ....................................................................................................................109
5.3.1 Ethernet Services Overview .....................................................................................................109
5.3.2 IP-20C’s Ethernet Capabilities ..................................................................................................125
5.3.3 Supported Standards ...............................................................................................................126
5.3.4 Ethernet Service Model ...........................................................................................................126
5.3.5 Ethernet Interfaces ..................................................................................................................142
5.3.6 Quality of Service (QoS) ...........................................................................................................151
5.3.7 Global Switch Configuration ....................................................................................................178
5.3.8 Automatic State Propagation and Link Loss Forwarding .........................................................178
5.3.9 Adaptive Bandwidth Notification (EOAM) ...............................................................................181
5.3.10 Network Resiliency ..................................................................................................................182
5.3.11 OAM .........................................................................................................................................187
5.4 Synchronization .......................................................................................................................192
5.4.1 IP-20C Synchronization Solution ..............................................................................................192
5.4.2 Available Synchronization Interfaces .......................................................................................193
5.4.3 Synchronous Ethernet (SyncE) .................................................................................................193
5.4.4 IEEE-1588v2 PTP Optimized Transport ....................................................................................194
5.4.5 SSM Support and Loop Prevention ..........................................................................................201
5.5 Radio Payload Encryption and FIPS ..........................................................................................202
5.5.1 AES-256 Payload Encryption ....................................................................................................202
5.5.2 FIPS 140-2 Compliance .............................................................................................................203

6. FibeAir IP-20C Management .................................................................................. 205

6.1 Management Overview ...........................................................................................................206
6.2 Automatic Network Topology Discovery with LLDP Protocol ..................................................207
6.3 Management Communication Channels and Protocols ..........................................................208
6.4 Web-Based Element Management System (Web EMS) ..........................................................209
6.5 Command Line Interface (CLI) ..................................................................................................210
6.6 Configuration Management .....................................................................................................210

Page 4 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

6.7 Software Management ............................................................................................................211

6.7.1 Backup Software Version .........................................................................................................211
6.8 CeraPlan Service for Creating Pre-Defined Configuration Files ...............................................212
6.9 IPv6 Support .............................................................................................................................212
6.10 In-Band Management ..............................................................................................................212
6.11 Local Management ..................................................................................................................213
6.12 Alarms ......................................................................................................................................213
6.12.1 Configurable BER Threshold for Alarms and Traps ..................................................................213
6.12.2 RSL Threshold Alarm ................................................................................................................213
6.12.3 Editing and Disabling Alarms and Events .................................................................................213
6.12.4 Timeout for Trap Generation ...................................................................................................213
6.13 NTP Support .............................................................................................................................214
6.14 UTC Support .............................................................................................................................214
6.15 System Security Features .........................................................................................................214
6.15.1 Ceragon’s Layered Security Concept........................................................................................214
6.15.2 Defenses in Management Communication Channels ..............................................................215
6.15.3 Defenses in User and System Authentication Procedures .......................................................216
6.15.4 Secure Communication Channels ............................................................................................218
6.15.5 Security Log ..............................................................................................................................220

7. Standards and Certifications .................................................................................. 223

7.1 Supported Ethernet Standards ................................................................................................223
7.2 MEF Certifications for Ethernet Services .................................................................................224

8. Specifications........................................................................................................ 225
8.1 General Radio Specifications ...................................................................................................226
8.2 Frequency Accuracy .................................................................................................................227
8.3 Radio Scripts ............................................................................................................................227
8.4 Radio Capacity Specifications ..................................................................................................229
8.4.1 3.5 MHz – Script ID 1523 ..........................................................................................................229
8.4.2 7 MHz – Script ID 1508 .............................................................................................................230
8.4.3 14MHz – Script ID 1509............................................................................................................230
8.4.4 28 MHz – Script ID 1504 ...........................................................................................................231
8.4.5 28 MHz – Script ID 1505 ...........................................................................................................231
8.4.6 28 MHz – Script IDs 1901 and 1951 .........................................................................................232
8.4.7 28 MHz – Script ID 1534 ...........................................................................................................232
8.4.8 40 MHz – Script ID 1507 ...........................................................................................................233
8.4.9 40 MHz – Script ID 1527 ...........................................................................................................233
8.4.10 40 MHz – Script ID 1902 ...........................................................................................................234
8.4.11 40 MHz – Script ID 1537 ...........................................................................................................234
8.4.12 56 MHz – Script ID 1502 ...........................................................................................................235
8.4.13 56 MHz – Script ID 1506 ...........................................................................................................235
8.4.14 56 MHz – Script IDs 1903 and 1953 .........................................................................................236
8.4.15 80 MHz – Script ID 1501 ...........................................................................................................236
8.5 Transmit Power Specifications .................................................................................................237
8.5.1 Pmin Power ..............................................................................................................................238

Page 5 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.6 Receiver Threshold Specifications ...........................................................................................239

8.6.1 Overload Thresholds ................................................................................................................246
8.7 Frequency Bands ......................................................................................................................247
8.8 Mediation Device Losses ..........................................................................................................259
8.9 Ethernet Latency Specifications ...............................................................................................260
8.9.1 Latency – 3.5 MHz Channel Bandwidth ...................................................................................260
8.9.2 Latency – 7 MHz Channel Bandwidth ......................................................................................260
8.9.3 Latency – 14 MHz Channel Bandwidth ....................................................................................261
8.9.4 Latency – 28 MHz Channel Bandwidth ....................................................................................261
8.9.5 Latency – 40 MHz Channel Bandwidth ....................................................................................262
8.9.6 Latency – 56 MHz Channel Bandwidth ....................................................................................262
8.9.7 Latency – 80 MHz Channel Bandwidth ....................................................................................263
8.10 Interface Specifications ............................................................................................................264
8.10.1 Ethernet Interface Specifications .............................................................................................264
8.11 Carrier Ethernet Functionality .................................................................................................266
8.12 Synchronization Functionality..................................................................................................267
8.13 Network Management, Diagnostics, Status, and Alarms.........................................................268
8.14 Mechanical Specifications ........................................................................................................268
8.15 Standards Compliance .............................................................................................................269
8.16 Environmental Specifications ...................................................................................................269
8.17 Antenna Specifications ............................................................................................................270
8.18 Power Input Specifications ......................................................................................................270
8.19 Power Consumption Specifications .........................................................................................270
8.20 Power Connection Options ......................................................................................................271
8.21 PoE Injector Specifications .......................................................................................................272
8.21.1 Power Input .............................................................................................................................272
8.21.2 Environmental ..........................................................................................................................272
8.21.3 Standards Compliance .............................................................................................................272
8.21.4 Mechanical ...............................................................................................................................272
8.22 Cable Specifications .................................................................................................................273
8.22.1 Outdoor Ethernet Cable Specifications ....................................................................................273
8.22.2 Outdoor DC Cable Specifications .............................................................................................273
8.22.3 ATEX Glands and Cables ...........................................................................................................274

9. Appendix A – Marketing Model Construction ......................................................... 275

10. Appendix B – ATEX Certification ............................................................................ 277

Page 6 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

List of Figures
Figure 1: MultiCore 2+0 Direct Mount Configuration ............................................................................21
Figure 2: MultiCore 2+0 DP ACAP ..........................................................................................................21
Figure 3: MultiCore 2+0 DP CCDP...........................................................................................................21
Figure 4: MultiCore 2+0 SP .....................................................................................................................21
Figure 5: 2 x MultiCore 2+0 Single Polarization Configuration...............................................................22
Figure 6: 2 x MultiCore 2+0 Dual Polarization Configuration .................................................................23
Figure 7: MultiCore 2+2 HSB Single Polarization Configuration .............................................................24
Figure 8: MultiCore 2+2 HSB Dual Polarization Configuration ...............................................................25
Figure 9: 1+1 HSB-SD Configuration .......................................................................................................26
Figure 10: 4x4 LoS MIMO Direct Mount Configuration ..........................................................................27
Figure 11: 2x2 LoS MIMO Direct Mount Configuration ..........................................................................28
Figure 12: IP-20C Rear View (Left) and Front View (Right) ....................................................................32
Figure 13: Cable Gland Construction ......................................................................................................33
Figure 14: IP-20C Block Diagram ............................................................................................................33
Figure 15: IP-20C Interfaces – Descriptive Labels ..................................................................................34
Figure 16: IP-20C Interfaces – Letter Labels ...........................................................................................35
Figure 17: IP-20C Interfaces – 2E2SX Model ..........................................................................................36
Figure 18: Separation Criteria when Working with Two Diplexer Types................................................39
Figure 19: MIMO/Protection Signaling Cable Pinouts ............................................................................40
Figure 20: 4x4 MIMO Configuration with External Management ..........................................................41
Figure 21: Splitter ...................................................................................................................................42
Figure 22: OMT .......................................................................................................................................42
Figure 23: PoE Injector ...........................................................................................................................43
Figure 24: PoE Injector Ports ..................................................................................................................44
Figure 25: ATEX-Certified Pigtails and Connectors .................................................................................45
Figure 26: IP-20C MultiCore Modem and RFIC Chipsets ........................................................................54
Figure 27: Performance Characteristics of Generic, 1+0 Single-Core Radio ..........................................54
Figure 28: Doubling IP-20C’s Capacity by Activating Second Core .........................................................55
Figure 29: Doubling Link Span While Increasing Capacity by Activating Second Core ...........................56
Figure 30: Utilizing Increased System Gain to Reduce Antenna Size .....................................................56
Figure 31: Quadrupling Capacity by Leveraging LoS MIMO with IP-20C’s MultiCore Architecture .......57
Figure 32: NLoS MIMO (Left) and LoS MIMO (Right) Compared ............................................................61
Figure 33: LoS MIMO – Transmitting and Receiving on a Single Frequency Channel ............................61
Figure 34: General LoS MIMO Antenna Setup .......................................................................................61
Figure 35: 4x4 MIMO: Two MultiCore Units Directly Mounted to the Antenna ....................................63

Page 7 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 36: 4x4 MIMO Configuration – Master and Slave Units ..............................................................63
Figure 37: MIMO Resiliency – Master Unit Half-Capacity Link...............................................................64
Figure 38: MIMO Resiliency – Slave Unit Half-Capacity Link ..................................................................64
Figure 39: LoS MIMO: Criterion for Optimal Antenna Separation .........................................................65
Figure 40: LoS MIMO: Optimal Antenna Separation vs. Link Distance ..................................................66
Figure 41: Continuum of Optimal LoS MIMO Installation Scenarios ......................................................67
Figure 42: Effect of Sub-Optimal Installation on Capacity (Maximum Capacity is at 1024 QAM) .........68
Figure 43: Asymmetrical Antenna Setup ................................................................................................69
Figure 44: 1+0 Space Diversity ...............................................................................................................70
Figure 45: 2+2 Space Diversity ...............................................................................................................70
Figure 46: MultiCore 2+2 Space Diversity ..............................................................................................71
Figure 47: 1+1 HSB with Space Diversity ................................................................................................71
Figure 1: Advanced Space Diversity (ASD)..............................................................................................72
Figure 49: ASD Data Paths ......................................................................................................................73
Figure 48: Deployment Scenario without AFR .......................................................................................75
Figure 49: Deployment Scenario with AFR .............................................................................................75
Figure 50: Network Using Four Narrow Channels ..................................................................................76
Figure 51: Converting to Wider Channels with AFR ...............................................................................77
Figure 52: Network Requiring Densification ..........................................................................................77
Figure 53: Densification Example with AFR ............................................................................................78
Figure 54: AFR 1+0 Deployment .............................................................................................................79
Figure 55: AFR 1+1 .................................................................................................................................79
Figure 56: AFR 2+0 XPIC .........................................................................................................................80
Figure 57: Interference Mitigation in AFR ..............................................................................................81
Figure 58: Header De-Duplication ..........................................................................................................82
Figure 59: Header De-Duplication Potential Throughput Savings per Layer ..........................................83
Figure 60: Propagation Delay with and without Frame Cut-Through ....................................................85
Figure 61: Frame Cut-Through ...............................................................................................................85
Figure 62: Frame Cut-Through ...............................................................................................................86
Figure 63: Multi-Carrier ABC Traffic Flow...............................................................................................87
Figure 64: Multi-Carrier ABC Traffic Distribution ...................................................................................87
Figure 65: Multi-Carrier ABC Load Balancing with Different ACM Points ..............................................88
Figure 66: Multi-Carrier ABC Minimum Bandwidth Override ................................................................89
Figure 67: Adaptive Coding and Modulation with 11 Working Points ...................................................92
Figure 68: IP-20C ACM with Adaptive Power Contrasted to Other ACM Implementations ..................94
Figure 69: Multiband Operation.............................................................................................................96
Figure 70: Multiband Cable for Use with CSFP Port ...............................................................................97
Figure 71: Dual Polarization ...................................................................................................................99

Page 8 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 72: XPIC Implementation ..........................................................................................................100

Figure 73: XPIC – Impact of Misalignments and Channel Degradation ................................................101
Figure 74: 1+1 HSB Protection – Split Protection Mode ......................................................................103
Figure 75: 1+1 HSB Protection – Line Protection Mode .......................................................................103
Figure 76: MultiCore 2+2 HSB Protection – Split Protection Mode .....................................................105
Figure 77: MultiCore 2+2 HSB Protection – Line Protection Mode ......................................................105
Figure 78: Internal and Local Management .........................................................................................106
Figure 79: Basic Ethernet Service Model ..............................................................................................110
Figure 80: Ethernet Virtual Connection (EVC) ......................................................................................111
Figure 81: Point to Point EVC ...............................................................................................................112
Figure 82: Multipoint to Multipoint EVC ..............................................................................................112
Figure 83: Rooted Multipoint EVC ........................................................................................................112
Figure 84: MEF Ethernet Services Definition Framework ....................................................................114
Figure 85: E-Line Service Type Using Point-to-Point EVC .....................................................................115
Figure 86: EPL Application Example .....................................................................................................116
Figure 87: EVPL Application Example ...................................................................................................117
Figure 88: E-LAN Service Type Using Multipoint-to-Multipoint EVC ....................................................117
Figure 89: Adding a Site Using an E-Line service ..................................................................................118
Figure 90: Adding a Site Using an E-LAN service ..................................................................................118
Figure 91: MEF Ethernet Private LAN Example ....................................................................................119
Figure 92: MEF Ethernet Virtual Private LAN Example.........................................................................120
Figure 93: E-Tree Service Type Using Rooted-Multipoint EVC .............................................................120
Figure 94: E-Tree Service Type Using Multiple Roots ...........................................................................121
Figure 95: MEF Ethernet Private Tree Example ...................................................................................122
Figure 96: Ethernet Virtual Private Tree Example ................................................................................123
Figure 97: Mobile Backhaul Reference Model .....................................................................................123
Figure 98: Packet Service Core Building Blocks ....................................................................................124
Figure 99: IP-20C Services Model .........................................................................................................127
Figure 100: IP-20C Services Core ..........................................................................................................128
Figure 101: IP-20C Services Flow ..........................................................................................................129
Figure 102: Point-to-Point Service .......................................................................................................130
Figure 103: Multipoint Service .............................................................................................................130
Figure 104: Management Service ........................................................................................................132
Figure 105: Management Service and its Service Points .....................................................................134
Figure 106: SAPs and SNPs ...................................................................................................................135
Figure 107: Pipe Service Points ............................................................................................................136
Figure 108: SAP, SNP and Pipe Service Points in a Microwave Network .............................................136
Figure 109: Service Path Relationship on Point-to-Point Service Path ................................................140

Page 9 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 110: Physical and Logical Interfaces ..........................................................................................142

Figure 111: Grouped Interfaces as a Single Logical Interface on Ingress Side .....................................143
Figure 112: Grouped Interfaces as a Single Logical Interface on Egress Side ......................................143
Figure 113: Relationship of Logical Interfaces to the Switching Fabric ................................................147
Figure 114: QoS Block Diagram ............................................................................................................152
Figure 115: Standard QoS and H-QoS Comparison ..............................................................................153
Figure 116: Hierarchical Classification .................................................................................................154
Figure 117: Classification Method Priorities ........................................................................................155
Figure 118: Ingress Policing Model ......................................................................................................159
Figure 119: IP-20C Queue Manager .....................................................................................................162
Figure 120: Synchronized Packet Loss ..................................................................................................163
Figure 121: Random Packet Loss with Increased Capacity Utilization Using WRED ............................164
Figure 122: WRED Profile Curve ...........................................................................................................165
Figure 123: Detailed H-QoS Diagram ...................................................................................................168
Figure 124: Scheduling Mechanism for a Single Service Bundle ..........................................................171
Figure 125: Network Topology with IP-20C Units and Third-Party Equipment ....................................181
Figure 126: ABN Entity .........................................................................................................................181
Figure 127: G.8032 Ring in Idle (Normal) State ....................................................................................184
Figure 128: G.8032 Ring in Protecting State ........................................................................................184
Figure 129: Load Balancing Example in G.8032 Ring ............................................................................185
Figure 130: IP-20C End-to-End Service Management ..........................................................................188
Figure 131 SOAM Maintenance Entities (Example) .............................................................................188
Figure 132: Ethernet Line Interface Loopback – Application Examples ...............................................190
Figure 133: IEEE-1588v2 PTP Optimized Transport – General Architecture ........................................194
Figure 134: Calculating the Propagation Delay for PTP Packets ..........................................................195
Figure 135: Transparent Clock – General Architecture ........................................................................198
Figure 136: Transparent Clock Delay Compensation ...........................................................................199
Figure 137: Boundary Clock – General Architecture ............................................................................200
Figure 138 AES-256 Encrypted Link ......................................................................................................202
Figure 139: Integrated IP-20C Management Tools ..............................................................................207
Figure 140: Security Solution Architecture Concept ............................................................................215
Figure 141: ATEX Certification for FibeAir IP-20C – Page 1 (Sample) ...................................................277
Figure 142: ATEX Certification for FibeAir IP-20C – Page 2 (Sample) ...................................................278

Page 10 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

List of Tables
Table 1: IP-20C Feature Set ------------------------------------------------------------------------------------------------- 19
Table 2: New Features in CeraOS 10.5.5 and 10.7 ------------------------------------------------------------------- 31
Table 3: Ethernet Splitter Cable and Gland for Dual Ethernet Port ---------------------------------------------- 37
Table 4: IP-20C Mediation Devices --------------------------------------------------------------------------------------- 41
Table 5: Activation Key Types ---------------------------------------------------------------------------------------------- 47
Table 6: Capacity Activation Keys ----------------------------------------------------------------------------------------- 51
Table 7: Edge CET Node Activation Keys -------------------------------------------------------------------------------- 52
Table 8: Edge CET Note Upgrade Activation Keys -------------------------------------------------------------------- 52
Table 9: TCO Comparison Between Single-Core and MultiCore Systems -------------------------------------- 58
Table 10: ACM Working Points (Profiles) ------------------------------------------------------------------------------- 91
Table 11: Multiband Cable for Use with CSFP Port ------------------------------------------------------------------- 97
Table 12: MEF-Defined Ethernet Service Types --------------------------------------------------------------------- 114
Table 13: Ethernet Services Learning and Forwarding ------------------------------------------------------------ 131
Table 14: Service Point Types per Service Type --------------------------------------------------------------------- 137
Table 15: Service Point Types that can Co-Exist on the Same Interface -------------------------------------- 138
Table 16: Service Point Type-Attached Interface Type Combinations that can Co-Exist on the Same
Interface ----------------------------------------------------------------------------------------------------------------------- 139
Table 17: C-VLAN 802.1 UP and CFI Default Mapping to CoS and Color ------------------------------------- 155
Table 18: S-VLAN 802.1 UP and DEI Default Mapping to CoS and Color ------------------------------------- 156
Table 20: MPLS EXP Default Mapping to CoS and Color ---------------------------------------------------------- 156
Table 19: DSCP Default Mapping to CoS and Color ---------------------------------------------------------------- 156
Table 21: QoS Priority Profile Example -------------------------------------------------------------------------------- 172
Table 22: WFQ Profile Example------------------------------------------------------------------------------------------ 173
Table 23: 802.1q UP Marking Table (C-VLAN) ----------------------------------------------------------------------- 175
Table 24: 802.1ad UP Marking Table (S-VLAN) ---------------------------------------------------------------------- 176
Table 25: Summary and Comparison of Standard QoS and H-QoS -------------------------------------------- 177
Table 26: Synchronization Interface Options ------------------------------------------------------------------------ 193
Table 27: Boundary Clock Input Options ------------------------------------------------------------------------------ 200
Table 28: Boundary Clock Output Options --------------------------------------------------------------------------- 200
Table 29: Dedicated Management Ports------------------------------------------------------------------------------ 208
Table 30: Supported Ethernet Standards ----------------------------------------------------------------------------- 223
Table 31: Supported MEF Specifications ------------------------------------------------------------------------------ 224
Table 32: MEF Certifications --------------------------------------------------------------------------------------------- 224
Table 33: Radio Frequencies --------------------------------------------------------------------------------------------- 226
Table 34: General Radio Specifications -------------------------------------------------------------------------------- 226
Table 35: Radio Scripts ----------------------------------------------------------------------------------------------------- 227

Page 11 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Table 36: Radio Capacity for 3.5 MHz – Script ID 1523 ----------------------------------------------------------- 229
Table 37: Radio Capacity for 7 MHz – Script ID 1508 -------------------------------------------------------------- 230
Table 38: Radio Capacity for 14MHz – Script ID 1509 ------------------------------------------------------------- 230
Table 39: Radio Capacity for 28 MHz – Script ID 1504 ------------------------------------------------------------ 231
Table 40: Radio Capacity for 28 MHz – Script ID 1505 ------------------------------------------------------------ 231
Table 41: Radio Capacity for 28 MHz – Script IDs 1901 and 1953 ---------------------------------------------- 232
Table 42: Radio Capacity for 28 MHz – Script ID 1534 ------------------------------------------------------------ 232
Table 43: Radio Capacity for 40 MHz – Script ID 1507 ------------------------------------------------------------ 233
Table 44: Radio Capacity for 40 MHz – Script ID 1527 ------------------------------------------------------------ 233
Table 45: Radio Capacity for 40 MHz – Script ID 1902 ------------------------------------------------------------ 234
Table 46: Radio Capacity for 40 MHz – Script ID 1537 ------------------------------------------------------------ 234
Table 47: Radio Capacity for 56 MHz – Script ID 1502 ------------------------------------------------------------ 235
Table 48: Radio Capacity for 56 MHz – Script ID 1506 ------------------------------------------------------------ 235
Table 49: Radio Capacity for 56 MHz – Script IDs 1903 and 1953 ---------------------------------------------- 236
Table 50: Radio Capacity for 80 MHz – Script ID 1501 ------------------------------------------------------------ 236
Table 51: IP-20C Standard Power --------------------------------------------------------------------------------------- 237
Table 52: IP-20C High Power --------------------------------------------------------------------------------------------- 237
Table 53: IP-20C Pmin Power -------------------------------------------------------------------------------------------- 238
Table 54: Receiver Threshold -------------------------------------------------------------------------------------------- 239
Table 55: Frequency Bands ----------------------------------------------------------------------------------------------- 247
Table 56: Mediation Device Losses ------------------------------------------------------------------------------------- 259
Table 57: Latency – 3.5 MHz Channel Bandwidth ------------------------------------------------------------------ 260
Table 58: Latency – 7 MHz Channel Bandwidth --------------------------------------------------------------------- 260
Table 59: Latency – 14 MHz Channel Bandwidth ------------------------------------------------------------------- 261
Table 60: Latency – 28 MHz Channel Bandwidth ------------------------------------------------------------------- 261
Table 61: Latency – 40 MHz Channel Bandwidth ------------------------------------------------------------------- 262
Table 62: Latency – 56 MHz Channel Bandwidth ------------------------------------------------------------------- 262
Table 63: Latency – 80 MHz Channel Bandwidth ------------------------------------------------------------------- 263
Table 64: Ethernet Interfaces -------------------------------------------------------------------------------------------- 264
Table 65: SPF Devices ------------------------------------------------------------------------------------------------------ 264
Table 66: Approved SFP+ Modules for MIMO Extension Ports ------------------------------------------------- 265
Table 67: Carrier Ethernet Functionality ------------------------------------------------------------------------------ 266
Table 68: Network Management and Monitoring------------------------------------------------------------------ 268
Table 69: Mechanical Specifications ----------------------------------------------------------------------------------- 268
Table 70: Standards Compliance ---------------------------------------------------------------------------------------- 269
Table 71: Antenna Specifications, Remote Mount ----------------------------------------------------------------- 270
Table 72: Power Input ----------------------------------------------------------------------------------------------------- 270
Table 73: Power Consumption------------------------------------------------------------------------------------------- 270

Page 12 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Table 74: Power Connection Options ---------------------------------------------------------------------------------- 271

Table 75: PoE Injector Power Input ------------------------------------------------------------------------------------ 272
Table 76: PoE Injector Standards Compliance ----------------------------------------------------------------------- 272
Table 77: PoE Injector Standards Compliance ----------------------------------------------------------------------- 272
Table 78: Outdoor Ethernet Cable – Electrical Requirements -------------------------------------------------- 273
Table 79: Outdoor Ethernet Cable – Mechanical/ Environmental Requirements ------------------------- 273
Table 80: Outdoor DC Cable – Electrical Requirements ---------------------------------------------------------- 273
Table 81: Outdoor DC Cable – Mechanical/ Environmental Requirements --------------------------------- 274
Table 82: ATEX Glands and Cables -------------------------------------------------------------------------------------- 274
Table 83: IP-20C- PP-a-fw-xxxY-ccc-h-abc ---------------------------------------------------------------------------- 275
Table 84: IP-20C Marketing Model Example ------------------------------------------------------------------------- 276

Page 13 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

About This Guide

This document describes the main features, components, and specifications of the
FibeAir IP-20C system. This document applies to version 10.7.

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-20C for use in system planning, and determining which
FibeAir IP-20C configuration is best suited for a specific network.

Related Documents
• Release Notes for FibeAir IP-20 All-Outdoor Products, CeraOS 10.7
• User Guide for FibeAir IP-20 All-Outdoor Products, CeraOS 10.7
• FibeAir IP-20C Installation Guide
• FibeAir IP-20 Series MIB Reference

Page 14 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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
ASD Advanced Space Diversity
ATPC Automatic Tx Power Control
BBS Baseband Switching
BER Bit Error Ratio
BLSR Bidirectional Line Switch Ring
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
DDM Digital Diagnostic Monitoring
DSCP Differentiated Service Code Point
EBS Excess Burst Size
EIR Excess Information Rate
EPL Ethernet Private Line
EVPL Ethernet Virtual Private Line
EVC Ethernet Virtual Connection
FEC Forward Error Correction
FTP (SFTP) File Transfer Protocol (Secured File Transfer Protocol)

Page 15 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Acronym Equivalent Term

GbE Gigabit Ethernet

HTTP (HTTPS) Hypertext Transfer Protocol (Secured HTTP)
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
QoS Quality of Service
RBAC Role-Based Access Control

Page 16 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Acronym Equivalent Term

RDI Remote Defect Indication

RMON Ethernet Statistics
RSL Received Signal Level
RSTP Rapid Spanning Tree Protocol
SAP Service Access Point
SD Space Diversity
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
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 17 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2. Introduction
Ceragon’s FibeAir IP-20C represents a new generation of radio technology,
capable of high bit rates and longer reach, and suitable for diverse deployment
scenarios.
IP-20C is the first true MultiCore system in the industry which utilizes parallel
radio signal processing in a compact, all-outdoor device combining radio,
baseband, and Carrier Ethernet functionality to offer a future proof solution for
PtP connectivity applications.
IP-20C supports cutting edge capacity-boosting techniques, such as LoS MIMO,
QPSK to 2048 QAM, and Header De-Duplication, to offer a high capacity solution
for every network topology and every site configuration.

This chapter includes:

• Product Overview
• Unique IP-20C Feature Set
• System Configurations
• FibeAir IP-20 Assured Platform
• FibeAir IP-20C Interoperability with Other Ceragon Products
• New Features in CeraOS 10.5.5 and 10.7

2.1 Product Overview

Ceragon’s FibeAir IP-20C sets a new standard in microwave transmission,
combining MultiCore radio technology, QPSK to 2048 QAM modulation, and line-
of-sight (LoS) 4x4 MIMO in a compact, all-outdoor design.
FibeAir IP-20C breaks capacity barriers, offering a virtual fiber solution in licensed
frequency bands. Its versatility makes it ideal for a wide variety of cost-effective
deployment scenarios including macrocell backhaul, small-cell aggregation, and
emerging fronthaul applications.
IP-20C is easily and quickly deployable compared with fiber, enabling operators to
achieve faster time to new revenue streams, lower total cost of ownership, and
long-term peace of mind.
IP-20C can deliver multi-Gbps capacity on a single frequency channel, setting a
new standard for efficient spectrum use. IP-20C’s unique MultiCore radio
architecture is based on an advanced parallel radio processing engine, built
around Ceragon’s in-house chipsets. The result is superior radio performance with
reduced power consumption and form-factor.
IP-20C is an integral part of the FibeAir family of high-capacity wireless backhaul
products. Together, the FibeAir product series provides a wide variety of backhaul
solutions that can be used separately or combined to form integrated backhaul
networks or network segments.

Page 18 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The FibeAir series “pay-as-you-go” activation key model further enables operators
to build for the future by adding capacity and functionality over time to meet the
needs of network growth without requiring additional hardware.
Additionally, IP-20C’s MultiCore architecture enables operators to start with a
single core with the option of enabling the second core remotely when network
capacity requirements increase.
The 4x4 LoS MIMO feature adds yet another element of scalability, enabling
operators to quadruple capability with the addition of a single IP-20C unit and
antenna at each end of the link while utilizing the same exact frequency channel
with no network replanning.
Along with its other configuration options, IP-20C can be used in Multiband
configurations with FibeAir IP-20E to provide robust links that combine microwave
with E-band transmissions, for capacity of up to 2.5 Gbps. In a Multiband
configuration, the very high availability of microwave effectively provides a
backup for the high-capacity E-Band link, thus enabling operators to benefit
simultaneously from the high capacity of E-Band and the high reliability of
microwave.
The following are some of the highlights of FibeAir IP-20C:
• MultiCore Radio Technology – Parallel radio processing engine that boosts
capacity, distance and availability.
• High Capacity and Spectral Efficiency – 2048 QAM modulation and LoS 4x4
MIMO
• Virtual Fiber in Licensed Frequencies – 1 Gbps radio throughput over a single
28 MHz channel utilizing 4x4 LoS MIMO.
• Simple Operation – Software-defined radio, rapid deployment, and minimal
truck rolls.
• Environment-Friendly – Compact, all-outdoor unit with low power
consumption.

2.2 Unique IP-20C Feature Set

The following table summarizes the basic IP-20C feature set.

Table 1: IP-20C Feature Set

Extended Modulation Range ACM 4-2048 QAM (11 ACM points)

Frequency Bands 5.7-42 GHz
Wide Range of Channels 3.5, 7, 14, 28, 40, 56, 80 MHz
Power over Ethernet (PoE) Proprietary
Small Form Factor (H)230mm x (W)233mm x (D)98mm
Antennas Ceragon proprietary RFU-C interface
Direct and remote mount – standard flange
Durable All-Outdoor System IP66-compliant

Page 19 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2.3 System Configurations

FibeAir IP-20C is designed to support the following site configurations:
• MultiCore 2+0 Single/Dual Polarization
• 2 x 1+0 (East-West)
• 2 x MultiCore 2+0 SP/DP
• MultiCore 2+2 SP/DP HSB
• 1+1 HSB-SD1
• 2x2 LoS MIMO
• 4x4 LoS MIMO
• ASD 2+0 (XPIC)
Note: For information on diplexer type and channel selection, refer
to Channel-Port Mapping to Polarization on page 37

1
28 MHz channels only.

Page 20 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2.3.1 MultiCore 2+0 Single or Dual Polarization Direct Mount

The following figure illustrates a MultiCore 2+0 direct mount configuration. For
single polarization, a splitter is used to combine the two cores. For dual
polarization, an OMT is used to combine the two cores.

Figure 1: MultiCore 2+0 Direct Mount Configuration

Ch1V Ch1V Ch1 Ch2

Ch2H
Ch1H

Figure 2: MultiCore 2+0 DP ACAP Figure 3: MultiCore 2+0 DP Figure 4: MultiCore 2+0 SP
CCDP

Page 21 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2.3.2 2 x MultiCore 2+0 Single Polarization

The following figure illustrates a 2 x MultiCore 2+0 single polarization
configuration. The IP-20C units are directly mounted on the antenna with two
splitter types.

Figure 5: 2 x MultiCore 2+0 Single Polarization Configuration

Ch1 Ch2 Ch3 Ch4

Page 22 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2.3.3 2 x MultiCore 2+0 Dual Polarization

The following figure illustrates a 2 x MultiCore 2+0 dual polarization configuration.
The IP-20C units are combined with a dual splitter, which in turn is attached to the
antenna using an OMT.

Figure 6: 2 x MultiCore 2+0 Dual Polarization Configuration

Ch1 V Ch2 V

Ch1 H Ch2 H

Page 23 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2.3.4 MultiCore 2+2 HSB Single Polarization

The following figure illustrates a MultiCore 2+2 HSB single polarization
configuration. The IP-20C units are combined using a dual coupler and a splitter.

Figure 7: MultiCore 2+2 HSB Single Polarization Configuration

Ch1 Ch2
Ch1 Ch2

Page 24 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2.3.5 MultiCore 2+2 HSB Dual Polarization XPIC

The following figure illustrates a MultiCore 2+2 HSB dual polarization
configuration. The IP-20C units are combined using a dual coupler and an OMT.

Figure 8: MultiCore 2+2 HSB Dual Polarization Configuration

Ch1
Ch1 V V
Ch2
Ch1 H H

Page 25 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2.3.6 1+1 HSB-SD

The following figure illustrates a 1+1 HSB-SD. The IP-20C units are combined using
a dual coupler, with two flexible waveguides, one to the primary antenna and one
to the diversity antenna. On each IP-20C unit, the transmitter connected to the
diversity antenna must be muted. For details, refer to Space Diversity on page 69.

Figure 9: 1+1 HSB-SD Configuration

Ch1
Ch1

Page 26 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2.3.7 4x4 LoS MIMO

The following figure illustrates a 4x4 LoS MIMO direct mount configuration. 4x4
LoS MIMO utilizes two IP-20C units. Each unit uses dual polarization, with all four
radio channels using the same frequency. Each unit is connected to an antenna
using an OMT.
Note: The same configuration can be utilized for 2+2 Space Diversity
(SD). In this case, the transmitters connected to the diversity
antenna should be muted. For details, refer to Space Diversity
on page 69.

Figure 10: 4x4 LoS MIMO Direct Mount Configuration

Ch1 V
Ch1 V
Ch1H
Ch1H

Page 27 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2.3.8 2x2 LoS MIMO

The following figure illustrates a 2x2 LoS MIMO direct mount configuration. 2x2
LoS MIMO utilizes a single IP-20C unit. Each unit radio port is connected to a
different antenna and utilizes the same exact RF channel.
Note: The same configuration can be utilized for 1+0 Space Diversity
(SD). In this case, the transmitter connected to the diversity
antenna should be muted. For details, refer to Space Diversity
on page 69.

Figure 11: 2x2 LoS MIMO Direct Mount Configuration

Ch1 V
Ch1

Page 28 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2.4 FibeAir IP-20C Interoperability with Other Ceragon Products

IP-20C is interoperable across the link with IP-20S in 1+0 configurations over 28
MHz channels.

Page 29 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2.5 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.
• 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-20C Assured
• FibeAir IP-20S Assured
• FibeAir IP-20A Assured
• FibeAir IP-20N Assured
• FibeAir IP-20LH Assured
• FibeAir IP-20G Assured
• FibeAir IP-20GX Assured
Note: CeraOS 10.7 cannot be used in FibeAir IP-20 Assured platforms.
For FibeAir IP-20 Assured, use CeraOS 8.3.

Page 30 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

2.6 New Features in CeraOS 10.5.5 and 10.7

The following table lists the features that have been added in CeraOS versions
10.5.5 and 10.7, 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 10.5.5 and 10.7

Feature Further Information Configuration Instructions in the User’s Added in
Guide Release

Advanced Space Diversity Advanced Space Diversity (ASD) Section 3.10, Configuring Advanced 10.7
(ASD) on page 72 Space Diversity (ASD)
East-West Configuration n/a n/a 10.7
1588 Transparent Clock Multiband (Enhanced Multi- Section 3.4, Configuring Multiband 10.7
with Multiband Carrier ABC) on page 95 (Enhanced Multi-Carrier ABC)
Configurations
Web Support for Queue- Egress PMs and Statistics on Section 7.8, Configuring and Displaying 10.7
Level PMs page 174 Queue-Level PMs
Web EMS Support for Voltage Alarm Thresholds and Section 11.5, Configuring Voltage Alarm 10.7
Voltage PMs PMs on page 44 Thresholds and Displaying Voltage PMs
Web EMS Support for SFP SFP DDM and Inventory Section 4.14.2, Displaying PMs about an 10.7
DDM PMs Monitoring on page 191 SFP Module
Stricter HTTPS Cipher HTTPS (Hypertext Transfer Section 21.6, Configuring HTTPS Cipher 10.7
Hardening Protocol Secure) on page 219 Hardening (CLI)
Login Banner n/a Section 14.5, Defining a Login Banner 10.7
FibeAir IP-20C Four-Port Interfaces on page 34 Section 2.12, Enabling the Interfaces 10.5.5
Hardware Model (2E2SX) (Interface Manager)
SFP DDM and Inventory SFP DDM and Inventory Section 4.14.2, Displaying PMs about an 10.5.5
Monitoring Monitoring on page 191 SFP Module
Configurable Voltage Voltage Alarm Thresholds and Section 11.5, Configuring Voltage Alarm 10.5.5
Alarm Thresholds PMs on page 44 Thresholds and Displaying Voltage PMs

Page 31 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

3. IP-20C Hardware Description

This chapter describes the IP-20C and its components, interfaces, and mediation
devices.

This chapter includes:

• IP-20C Unit Description
• MultiCore Mediation Devices (MCMD)
• PoE Injector
• Voltage Alarm Thresholds and PMs
• Offshore and ATEX Compatibility

3.1 IP-20C Unit Description

FibeAir IP-20C features an all-outdoor MultiCore architecture consisting of a single
unit directly mounted on the antenna.
Note: The equipment is type approved and labeled according to EU
Directive 1999/5/EC (R&TTE).

Note that in IP-20C, Port 2 is the upper port, located closest to

the handle, and Port 1 is the lower port, located closest to the
Ethernet ports.

Figure 12: IP-20C Rear View (Left) and Front View (Right)

Page 32 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 13: Cable Gland Construction

3.1.1 Hardware Architecture

The following diagram presents a detailed block diagram of the IP-20C.

Figure 14: IP-20C Block Diagram

The IP-20C combines full system capabilities with a very compact form-fit. The all
outdoor system architecture is designed around Ceragon’s IP core components,
enabling a true MultiCore design.
For a detailed description of the system interfaces, refer to Interfaces on page 34.

Page 33 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

3.1.2 Interfaces
IP-20C is available in several hardware models:
• IP-20C ESS – Includes one RJ-45 port and two SFP ports for Ethernet traffic.
• IP-20C ESX – Includes one RJ-45 port and one SFP port for Ethernet traffic, and
an SFP+ port for use as an Extension port with MIMO 4x4 and Space Diversity
2+2 configurations.
• IP-20C 2E2SX – Includes two RJ-45 traffic ports in a single gland, as well as two
SFP ports, for a total of up to four available traffic ports. In MIMO 4x4 and
Space Diversity 2+2 configurations, one of the SFP ports (P4) is automatically
configured to operate as an Extension port.
Note: IP-20C 2E2SX requires CeraOS 10.5.5 or higher.
Two labelling formats are available for the IP-20C ESS and ESX hardware models,
as shown in the following figures.

Figure 15: IP-20C Interfaces – Descriptive Labels

Page 34 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 16: IP-20C Interfaces – Letter Labels

• Data Port 1 for GbE traffic:
◦ Electric: 10/100/1000Base-T. Supports PoE.
• Data Port 2 for GbE traffic:
◦ Electric: 1000Base-T
◦ Optical: 1000Base-X
• Data Port 3/EXT
◦ Electric: 1000Base-T
◦ Optical: 1000Base-X)
◦ Optical: Ceragon proprietary interface, if this port serves as an extension
port for data sharing.
Note: For more details, refer to Interface Specifications on page 264.
• Power interface (-48VDC)
• Management Port: 10/100Base-T
• 2 RF Interfaces – Standard interface per frequency band
• RSL interface: BNC connector
• Source sharing: TNC connector
• Grounding screw

Page 35 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The 2E2SX model includes two electrical traffic ports in a single gland, in addition
to two optical ports, for a total of up to four available traffic ports. This model is
interoperable with other IP-20C hardware models, and supports MIMO and all
other advanced IP-20C features.

Figure 17: IP-20C Interfaces – 2E2SX Model

• Data Port 1 for GbE traffic (Eth 1):
◦ 10/100/1000Base-T (RJ-45)
◦ Supports PoE
◦ Requires special splitter cable/adaptor
• Data Port 2 for GbE traffic (Eth 2):
◦ 10/100/1000Base-T (RJ-45)
◦ Requires special splitter cable/adaptor
• Data Port 3 for GbE traffic (Eth 3):
◦ Electrical SFP: 1000Base-T
◦ Optical SFP: 1000Base-X
• Data Port 4/EXT
◦ SFP cage which supports SFP+ standard
◦ 1G for traffic (Eth 4) or proprietary 10G connection when used as
Extension port (automatically configured according to unit configuration)
Note: For more details, refer to Interface Specifications on page 264.
• Power interface (-48VDC)
• Management Port: 10/100Base-T
• 2 RF Interfaces – Standard interface per frequency band
• RSL interface: BNC connector
• Source sharing: TNC connector
• Grounding screw

Page 36 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

A special splitter is used to enable dual connection of the cables to a physical

DisplayPort on the IP-20C 2E2SX. The splitter must be ordered separately, and is
provided with its own gland. The following table gives the marketing model of the
splitter and gland.

Table 3: Ethernet Splitter Cable and Gland for Dual Ethernet Port
Marketing Model Item Description

IP-20_Ethernet_Splitter_cable CABLE,DP TO 2xRJ45F, 1.0M, WITH GLANDS, UV PROTECTED

In most configurations, P4 on the 2E2SX model can be used as a traffic port

(Eth 4). However, in MIMO 4x4 and Space Diversity 2+2 configurations, P4 is used
as an Extension port. When one of these configurations is applied, the system
automatically configures P4 to operate as an Extension port and it is no longer
available for use as a traffic port (Eth 4). In these configurations, P4 must be used
with a special SFP+ module. See Table 66.
Note: The 2E2SX hardware model is available for 7, 15, 18, and 23
GHz frequency bands. For information about availability in
additional frequencies, contact your Ceragon representative.

3.1.3 Channel-Port Mapping to Polarization

Two transceiver chains and two diplexers are embedded in each IP-20C unit. In
most cases, both diplexers are the same exact type. When the diplexers are the
same type, radio ports 1 and 2 cover the exact same frequency range.
In the 5.7-11GHz frequency bands, where channelization and diplexers are
relatively narrow, a single IP-20C unit might have to operate in two channels that
are not covered by the same diplexer.
When this is required, the IP-20C can be ordered with two different diplexer types
to cover two different channel ranges within the same frequency band.
An IP-20C with the same type of diplexer assembled on both transceiver chains
has the following marketing model structure:
• Example: IP-20C-HP-6L-252A-1W4-H-ESX
In this example, 1W4 indicates that both transceivers cover channels 1 through 4.
An IP-20C with two different types of diplexers has the following marketing model
structure:
• Example: IP-20C-HP-6L-252A-1W27W8-H-ESX
In this example, 1W27W8 indicates that channels 1 through 2 are covered by
Port1, while channels 7 through 8 are covered by Port2.

Page 37 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

An IP-20C assembly for this example would look as follows:

Radio Port ID (EMS ID) Channels Coverage

Port 2 Ch 7-8
Port 1 Ch 1-2

Note: The same orientation is maintained for TX-H and TX-L units.
When installing an IP-20C unit with two different diplexers in a Multicore 2+0 DP
Direct Mount configuration, the V and H ports of the OMT are mechanically
connected to Port 2 and 1 respectively.
This means that in the above example, V polarization is covered by channels 7
through 8 (Port 2) and H polarization is covered by channels 1 through 2 (Port 1).

To assign the channels to different polarizations, a different system with a

different marketing model should be ordered.
The following marketing model represents a system in which V polarization is
covered by channels 1 through 2 (Port 2) and H polarization is covered by
channels 7 through 8 (Port 1):

Page 38 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

IP-20C-HP-6L-252A-7W81W2-H-ESX:
Radio Port ID (EMS ID) Channels Coverage

Port 2 Ch 1-2
Port 1 Ch 7-8

Please note that when selecting two operational channels that are not covered by
the same diplexer, certain TX-TX separation and TX-RX separation criteria should
be met.

Figure 18: Separation Criteria when Working with Two Diplexer Types
Because diplexer coverage and channelization plans vary in different parts of the
world for specific applications, please consult with Ceragon pre-sales
representatives for support.

3.1.4 Management Connection for 4x4 MIMO and 1+1/2+2 HSB Configurations
In 4x4 MIMO and all HSB protection configurations, two Y-splitter cables and a
special signaling cable must be used to connect the management ports
(MGT/PROT) of the two IP-20C units and provide management access to each
unit.
When Out-of-Band management is used, a splitter is required to connect the
management ports to local management and to each other.
The MIMO/Protection signaling cables are available pre-assembled from Ceragon
in various lengths, but users can also prepare them in the field.
The following sections explain how to prepare and connect these cables.

Page 39 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

3.1.4.1 Preparing a MIMO/Protection Signaling Cable

The MIMO/Protection signaling cables require the following pinouts.

Figure 19: MIMO/Protection Signaling Cable Pinouts

Note: Other than the pinout connection described above, the cable
should be prepared according to the cable preparation
procedure described in the IP-20C Installation Guide.

3.1.4.2 Connecting the MIMO/Protection Splitters and Protection Signaling Cable

Each splitter has three ports:
• System plug (“Sys”) – The system plug should be connected to the IP-20C’s
management port.
• Management port (“Mng”) – A standard CAT5E cable should be connected to
the splitter’s management port in order to utilize out-of-band (external)
management.
Note: Even for systems that use in-band management, initial
configuration of a 4x4 MIMO and any HSB protection
configuration must be performed manually using out-of-band
management.
• MIMO/Protection signaling port (“MIMO/Prot”) – A Protection signaling cross
cable, as described above, should be connected between this port and the
other “MIMO/Prot” port of the second splitter on the mate IP-20C unit.

Page 40 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following figure demonstrates a 4x4 MIMO configuration in which both

IP-20C units are connected to an external management station and to each
other, using two splitters.

Figure 20: 4x4 MIMO Configuration with External Management

3.2 MultiCore Mediation Devices (MCMD)

The Dual Core Mediation Devices (MCMD) are designed to offer a simple and
compact solution for a direct mount installation of the MultiCore IP-20C on a
standard RFU-C antenna.
IP-20C is equipped with two antenna ports, which mandates the use of unique
mediation devices to facilitate direct mount configurations. The following two
examples show dual core mediation devices that enable the connection of a single
IP-20C unit to an antenna. For the full set of mediation devices, refer to the IP-20C
Installation Guide.

Table 4: IP-20C Mediation Devices

MCMD type Functionality

Splitter Combines the two cores using the same polarization

OMT Combines the two cores on alternate polarizations (H,V)

Page 41 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 21: Splitter

Figure 22: OMT

Note: For a detailed description of these mediation devices and how
they are utilized, refer to the FibeAir IP-20C Installation Guide,
DOC-00036522.

Page 42 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

3.3 PoE Injector

The PoE injector box is designed to offer a single cable solution for connecting
both data and the DC power supply to the IP-20C system.
Note: An AC-power PoE Injector option is also available. Contact your
Ceragon representative for details.
To do so, the PoE injector combines 48VDC input and GbE signals via a standard
CAT5E cable using a proprietary Ceragon design.
The PoE injector can be ordered with a DC feed protection, as well as EMC surge
protection for both indoor and outdoor installation options. It can be mounted on
poles, walls, or inside racks.

Figure 23: PoE Injector

Two models of the PoE Injector are available:
• PoE_Inj_AO_2DC_24V_48V – Includes two DC power ports with power input
ranges of -(18-60)V each.
• PoE_Inj_AO – Includes one DC power port (DC Power Port #1), with a power
input range of -(40-60)V.

3.3.1 PoE Injector Interfaces

• DC Power Port 1 -(18-60)V or ±(40-60)V
• DC Power Port 2 -(18-60)V
• GbE Data Port supporting 10/100/1000Base-T
• Power-Over-Ethernet (PoE) Port
• Grounding screw

Page 43 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 24: PoE Injector Ports

3.4 Voltage Alarm Thresholds and PMs

The allowed power input range for the IP-20C 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: 32V
• Undervoltage Clear Threshold: 34V
• Overvoltage Raise Threshold: 60V
• Overvoltage Clear Threshold: 58V
These thresholds are configurable.
IP-20C also 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.

Page 44 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

3.5 Offshore and ATEX Compatibility

FibeAir IP-20C can be ordered for use in offshore and/or hazardous areas,
including areas requiring ATEX Zone-2 compliance.

3.5.1 Offshore Durability

FibeAir IP-20C can be ordered with an option for offshore durability. With this
option, a special coating is applied to the IP-20C unit that provides the unit with
enhanced durability for harsh, salty offshore environments.
IP-20C offshore units must be ordered with special part numbers. Please contact
your Ceragon representative for details.

3.5.2 ATEX Zone II Certification

FibeAir IP-20C can be ordered with hardware that has been tested and certified
for ATEX Zone II use. ATEX certification indicates that the product meets the strict
criteria and specifications for use in hazardous, explosive environments.
An ATEX Zone II-certified IP-20C includes the unit itself, specially-designed
“pigtails” that serve the function of glands, and special patch cords. Every ATEX-
compliant IP-20C unit is pre-tested and certified for ATEX Zone 2 use.
An ATEX-compliant IP-20C is delivered with the pigtails and patch cords factory-
attached, and with unused ports hermitically sealed, according to the site’s
interface requirements.

Figure 25: ATEX-Certified Pigtails and Connectors

For a list of glands and cables used in ATEX-certified configurations, see ATEX
Glands and Cables on page 274.
For a typical ATEX certification certificate that has been provided for FibeAir IP-
20C units, see Appendix B – ATEX Certification on page 277.

Page 45 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

4. Activation Keys
This chapter describes IP-20C’s activation key model. IP-20C offers a pay as-you-
grow concept in which future capacity growth and additional functionality can be
enabled with activation keys. For purposes of the activation keys, each IP-20C unit
is considered a distinct device. Each device contains a single activation key cipher.
Activation keys are divided into two categories:
• Per Core – The activation key is per IP-20C core, which means that two
activation keys are required for a single IP-20C unit.
• Per Device – The activation key is per device, regardless of the number of
cores supported by the device.

This chapter includes:

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

4.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
device serial number.
In order to upgrade an activation key, the activation key must be entered into the
IP-20C. 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.

4.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. 10 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 46 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

4.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.
• Unlimited Smart Pipe (L1) services.
• A single 1 x GbE port for traffic.
• 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 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 5: Activation Key Types

Marketing Model Type Description For Addition Information

Capacity Per Core Enables you to increase your Capacity Summary

Refer to Table 6: Capacity system’s radio capacity in gradual
Activation Keys on page 51. steps by upgrading your capacity
activation key. Without a capacity
activation key, each core has a
capacity of 10 Mbps. Activation-
key-enabled capacity is available
from 50 Mbps to 650 Mbps. A
separate activation key is required
per core.
IP-20-SL-2nd-Core-Act. Enables use of second core. Unique MultiCore
Architecture

Page 47 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Marketing Model Type Description For Addition Information

IP-20-SL-LLF Per Device Enables you to use Link Loss Automatic State
Forwarding (LLF) with Automatic Propagation and Link Loss
State Propagation (ASP). Without Forwarding
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.
IP-20-SL-ASD Per Core Enables the use of Advanced Advanced Space Diversity
Space Diversity (ASD). A separate (ASD)
activation key is required per core.
This means that for a single link,
with two IP-20C units on one side
of the link and one IP-20C unit on
the other side, a total of six ASD
activation keys are required.
IP-20-SL-ACM Per Core Enables the use of Adaptive Adaptive Coding
Coding and Modulation (ACM) Modulation (ACM)
scripts. A separate activation key is
required per core.
IP-20-SL-Freq-Reuse Per Core Enables the use of Advanced Advanced Frequency Reuse
Frequency Reuse (AFR). For a AFR (AFR)
1+0 configuration, two activation
keys are required for the hub site
(one per carrier) and one
activation key is required for each
tail site.
IP-20-SL-MIMO Per Core Enables the use of MIMO. A Line of Sight (LoS) MIMO
separate activation key is required
for each core in the MIMO
configuration.
IP-20-SL-MC-ABC Per Core Enables Multi-Carrier ABC. A Multi-Carrier ABC
separate activation key is required
per core.
IP-20-SL-Header- Per Core Enables the use of Header De- Header De-Duplication
DeDuplication Duplication, which can be
configured to operate at L2
through L4.
IP-20-SL-XPIC Per Core Enables the use of Cross Cross Polarization
Polarization Interference Canceller Interference Canceller
(XPIC). A separate activation key is (XPIC)
required for each core in the XPIC
pair.

Page 48 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Marketing Model Type Description For Addition Information

IP-20-SL-Encryption-AES256 Per Carrier Enables the use of AES-256 AES-256 Payload Encryption
encryption for 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.
IP-20-SL-GE-Port Per Port Enables the use of an Ethernet Interfaces
port in GbE mode
(10/100/1000baseT or
1000baseX). An activation key is
required for each additional traffic
port that is used on the device,
beyond the one GbE traffic port
that is enabled via the default
activation key. Any of these
activation keys can be installed
multiple times with dynamic
allocation inside the unit.
Note: Two Ethernet ports are
enabled in FE mode
(10/100baseT) by default without
requiring any activation key.

Page 49 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Marketing Model Type Description For Addition Information

Refer to Table 7: Edge CET Per Device Enables Carrier Ethernet Transport • Ethernet Service Model
Node Activation Keys on (CET) and a number of Ethernet • Quality of Service (QoS)
page 52. services (EVCs), depending on the
• Network Resiliency
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.2
IP-20-SL-Network-Resiliency Per Device Enables G.8032 for improving Network Resiliency
network resiliency.3
IP-20-SL-H-QoS Per Device Enables H-QoS. This activation key Quality of Service (QoS)
is required to add service-bundles
with dedicated queues to
interfaces. Without this activation
key, only the default eight queues
per port are supported.
IP-20-SL-Enh-Packet-Buffer Per Device Enables configurable (non-default) Quality of Service (QoS)
queue 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.

2
MSTP is planned for future release.
3
G.8032 is planned for future release.

Page 50 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Marketing Model Type Description For Addition Information

IP-20-SL-Sync-Unit Per Device Enables the G.8262 Synchronization

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).
IP-20-SL-IEEE-1588-TC Per Device Enables IEEE-1588 Transparent IEEE-1588v2 PTP Optimized
Clock. Transport
IP-20-SL-IEEE-1588-BC Per Device Enables IEEE-1588 Boundary IEEE-1588v2 PTP Optimized
Clock.4 Transport
IP-20-SL-Frame-Cut- Per Device Enables Frame Cut-Through. Frame Cut-Through
Through
IP-20-SL-Secure- Per Device Enables secure management Secure Communication
Management protocols (SSH, HTTPS, SFTP, Channels
SNMPv3, and RADIUS).
IP-20-SL-Eth-OAM-FM Per Device Enables Connectivity Fault Connectivity Fault
Management (FM) per Y.1731 Management (FM)
(CET mode only).
IP-20-SL-Eth-OAM-PM Per Device Enables performance monitoring
pursuant to Y.1731 (CET mode
only).5
IP-20-SL-LACP Per Device Enables Link Aggregation Control Link Aggregation Groups
Protocol (LACP). (LAG) and LACP

Table 6: Capacity Activation Keys

Marketing Model Description

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

IP-20-SL-Capacity-100M IP-20 SL - Capacity 100M, per carrier
IP-20-SL-Capacity-150M IP-20 SL - Capacity 150M, per carrier
IP-20-SL-Capacity-200M IP-20 SL - Capacity 200M, per carrier
IP-20-SL-Capacity-225M IP-20 SL - Capacity 225M, per carrier
IP-20-SL-Capacity-250M IP-20 SL - Capacity 250M, per carrier
IP-20-SL-Capacity-300M IP-20 SL - Capacity 300M, per carrier
IP-20-SL-Capacity-350M IP-20 SL - Capacity 350M, per carrier

4
IEEE-1588 Boundary Clock is planned for future release.
5
PM support is planned for future release.

Page 51 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

IP-20-SL-Capacity-400M IP-20 SL - Capacity 400M, per carrier

IP-20-SL-Capacity-450M IP-20 SL - Capacity 450M, per carrier
IP-20-SL-Capacity-500M IP-20 SL - Capacity 500M, per carrier
IP-20-SL-Capacity-650M IP-20 SL - Capacity 650M, per carrier
IP-20-SL-Upg-25M-50M IP-20 SL - Upg 25M - 50M, per carrier
IP-20-SL-Upg-50M-100M IP-20 SL - Upg 50M - 100M, per carrier
IP-20-SL-Upg-100M-150M IP-20 SL - Upg 100M - 150M, per carrier
IP-20-SL-Upg-150M-200M IP-20 SL - Upg 150M - 200M, per carrier
IP-20-SL-Upg-200M-225M IP-20 SL - Upg 200M - 225M, per carrier
IP-20-SL-Upg-225M-250M IP-20 SL - Upg 225M - 250M, per carrier
IP-20-SL-Upg-250M-300M IP-20 SL - Upg 250M - 300M, per carrier
IP-20-SL-Upg-300M-350M IP-20 SL - Upg 300M - 350M, per carrier
IP-20-SL-Upg-350M-400M IP-20 SL - Upg 350M - 400M, per carrier
IP-20-SL-Upg-400M-450M IP-20 SL - Upg 400M - 450M, per carrier
IP-20-SL-Upg-450M-500M IP-20 SL - Upg 450M - 500M, per carrier
IP-20-SL-Upg-500M-650M IP-20 SL - Upg 500M - 650M, per carrier

Table 7: Edge CET Node Activation Keys

Marketing Model # of Bundled GbE Management # of Pipe (L1) # of CET (L2)
Ports for User Traffic Service Ethernet Services Ethernet Services

Default (No Activation Key) 1 Yes Unlimited -

IP-20-SL-Edge-CET-Node 2 Yes Unlimited 8
IP-20-SL-Agg-Lvl-1-CET-Node 2 Yes Unlimited 64

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 8: Edge CET Note Upgrade Activation Keys

Marketing Model Upgrade From Upgrade To

IP-20-SL-Upg-Pipe/Edge-CET NG Smart Pipe Activation Key (SL-0311-0) IP-20-SL-Edge-CET-Node (SL-0312-0)

IP-20-SL-Upg-Edge/Agg-Lvl-1 IP-20-SL-Edge-CET-Node (SL-0312-0) IP-20-SL-Agg-Lvl-1-CET-Node (SL-0313-0)

Page 52 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

This chapter includes:

• Unique MultiCore Architecture
• Innovative Techniques to Boost Capacity and Reduce Latency
• Ethernet Features
• Synchronization
• Radio Payload Encryption and FIPS

5.1 Unique MultiCore Architecture

FibeAir IP-20C is the microwave communications industry’s first MultiCore
microwave radio. MultiCore radio architecture marks the beginning of a new era
in wireless communications, boosting microwave to new levels of capacity
previously reserved to fiber optic cable.
IP-20C’s unique MultiCore radio architecture is based on an advanced parallel
radio processing engine built around Ceragon’s proprietary baseband modem and
RFIC chipsets. This architecture is optimized for parallel processing of multiple
radio signal flows, and enables IP-20C to multiply capacity and increase system
gain in comparison with current technology.
Utilizing common processing resources at the kernel of the radio terminal, the
MultiCore system reduces power consumption and maintains a small form-factor.
This makes IP-20C an advantageous choice for deployment in numerous
heterogeneous network scenarios, such as small cells and fronthaul.

Page 53 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 26: IP-20C MultiCore Modem and RFIC Chipsets

IP-20C’s parallel radio processing engine is what differentiates IP-20C from other
multiple-core solutions, which are really nothing more than multiple radio
systems compacted into a single box. IP-20C’s MultiCore architecture enables IP-
20C to provide significant improvements in capacity and link distance, as well as
low power consumption, smaller antennas, more efficient frequency utilization,
less expensive frequency use, and a small form factor.

5.1.1 Flexible Operating Modes with MultiCore Architecture

IP-20C’s MultiCore architecture is inherently versatile and suitable for many
different network deployment scenarios. IP-20C can operate as a high-capacity,
single-core solution. At any time in the network’s growth cycle, the second core
can be activated remotely for optimized performance.
To illustrate the many advantages of IP-20C’s MultiCore architecture, consider a
generic, 1+0 single-core radio with high performance in terms of capacity, link
distance, and antenna size.

Figure 27: Performance Characteristics of Generic, 1+0 Single-Core Radio

IP-20C can operate in single-core mode, with similar parameters to a standard
radio, but with additional capacity due to its ability to operate at 2048 QAM
modulation.

Page 54 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Activating the second core does not simply double the capacity of the IP-20C, but
rather, provides a package of options for improved performance that can be
utilized in a number of ways, according to the requirements of the specific
deployment scenario.

5.1.1.1 Doubling the Capacity

Turning on the IP-20C’s second core automatically doubles the IP-20C’s capacity.
This doubling of capacity is achieved without affecting system gain or availability,
since it results from the use of an additional core with the same modulation, Tx
power, and Rx sensitivity. The IP-20C also maintains the same small form-factor.
Effectively, activating the second core provides a pure doubling of capacity
without any tradeoffs.

Figure 28: Doubling IP-20C’s Capacity by Activating Second Core

5.1.1.2 Doubling the Link Distance

The increased performance that IP-20C’s MultiCore architecture provides can be
leveraged to increase link distance. IP-20C splits the bitstream between its two
cores using Multi-Carrier Adaptive Bandwidth Control (ABC). This makes it
possible to utilize a lower modulation scheme that significantly increases system
gain for Tx power and Rx sensitivity. This enables IP-20C to support longer signal
spans, enabling operators to as much as double their link spans.
For example, consider an IP-20C in a 1+0 configuration with only one core
activated, transmitting 260 Mbps over a 28 MHz channel with 2048 QAM
modulation. Activating the second core makes it possible to reduce the
modulation to 64 QAM and still add capacity, from 260 Mbps to 280 Mbps,
consisting of 2 x 140 Mbps over the 28 MHz channel. Reducing the modulation
from 2048 QAM to 64 QAM delivers a 4dB improvement in Tx power and a 15dB
improvement in Rx sensitivity, for a total increase of 19dB in system gain. This
improved system gain enables the operator to double the link distance, while
benefiting from a 20 Mbps increase in capacity.

Page 55 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 29: Doubling Link Span While Increasing Capacity by Activating Second Core

For additional information:

• Multi-Carrier ABC

5.1.1.3 Reducing Antenna Size by Half

The increased system gain that IP-20C’s MultiCore architecture makes possible
can be leveraged to scale down antenna size by as much as half. In general, each
doubling of antenna size on one side of the link translates into 6dB in additional
link budget. The 19dB increase in system gain that IP-20C’s MultiCore architecture
can provide can be exploited to halve the antenna size. This uses 12dB of the 19dB
system gain, leaving 7dB to further reduce antenna size on either side of the link.
This enables the operator to realize CAPEX savings from the MultiCore
deployment.

Figure 30: Utilizing Increased System Gain to Reduce Antenna Size

5.1.1.4 Frequency Decongestion and Lower License Fees

Another way in which the increased system gain that IP-20C’s MultiCore
architecture makes possible can be leveraged is by taking advantage of the
increased system gain to shift from congested and expensive frequency bands to
uncongested and less costly higher frequency bands. The loss in link budget
incurred by moving to higher frequencies is absorbed by the increased system
gain provided by IP-20C’s MultiCore architecture. Relatively long-span links, which
previously required operation in lower, more congested, and more expensive
frequencies such as 6, 7, and 8 GHz, can be shifted to higher, less congested, and
less expensive frequency bands such as 11 GHz with the help of IP-20C’s
MultiCore architecture.

Page 56 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.1.1.5 Quadrupling Capacity with IP-20C’s MultiCore Architecture and 4x4 LoS MIMO
Two separate MultiCore IP-20C units can be deployed in a MIMO configuration,
making it possible to operate a very efficient Line-of-Sight (LoS) MIMO link by
leveraging MIMO and XPIC technology together with IP-20C’s MultiCore
architecture. With just two MultiCore IP-20C units, four independent bitstreams
can be transmitted over a single frequency channel, quadrupling capacity and
spectral utilization. IP-20C’s 4x4 LoS MIMO capabilities enable microwave to
achieve gigabits of capacity, more than enough for small-cell and other
heterogeneous network deployments.

Figure 31: Quadrupling Capacity by Leveraging LoS MIMO with IP-20C’s MultiCore
Architecture

For additional information:

• Line of Sight (LoS) MIMO
• Cross Polarization Interference Canceller (XPIC)

5.1.2 TCO Savings as a Result of MultiCore Architecture

The various ways described above in which IP-20C MultiCore architecture can be
leveraged to provide additional capacity, longer link distances, and smaller
antenna side, all carry significant cost savings for operators.
Consider the common and practical scenario of a 1+0 link that must be upgraded
to MultiCore 2+0 in order to accommodate growing demand for capacity. For a
single-core system, the upgrade is a complicated process that requires:
• Purchasing a new radio unit.
• Sending an installation team to the site.
• Dismantling the existing radio unit.
• Replacing the single-mount radio-antenna interface with a coupler (for single
polarization) or OMT (for dual polarization) to accommodate the two units.
• Re-installing the original radio unit along with the new radio unit.
• Connecting both radios to a switch in order to provide Layer 2 link aggregation
(LAG), necessary to achieve a MultiCore 2+0 link.

Page 57 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

These steps incur a high initial cost for re-installing and re-configuring the link, as
well as high site leasing fees due to the additional equipment required, the larger
footprint, and additional ongoing power consumption. The upgrade process
involves hours of link down-time, incurring loss of revenue and impaired customer
Quality of Experience (QoE) throughput the upgrade process. During its lifetime,
the upgraded 2+0 single-core system will consume 100% more power than the
1+0 system and will be virtually twice as likely to require on-site maintenance.
With IP-20C, network operators can initially install the MultiCore IP-20C unit in
single-core mode, with enough network capacity to meet current needs and the
ability to expand capacity on the fly in the future. When an upgrade to MultiCore
2+0 becomes necessary, the operator merely needs to perform the following
steps:
• Purchase an activation key for the second core.
• Remotely upload the activation key and activate the second core.
No site visits are required, and virtually no downtime is incurred, enabling
customers to enjoy continuous, uninterrupted service. No additional switch is
necessary, because IP-20C can use Multi-Carrier ABC internally between the two
cores to utilize the multi-channel capacity, in a much more efficient manner than
with Layer 2 LAG. Network operators benefit from much lower power
consumption than 2+0 systems made up of separate, single-core radio units, and
site leasing fees do not increase since no additional hardware is required.
The following table summarizes the cost benefits of IP-20C’s MultiCore technology
in terms of TCO.

Table 9: TCO Comparison Between Single-Core and MultiCore Systems

Single-Core system MultiCore system

Initial Installation 1+0 link with 1+0 antenna 2+0 installation (remote or direct
mediation device (remote or direct mount). Only one core has an
mount). activation key and is activated.
Upgrade to 2+0 • Obtain new radio equipment • Obtain activation key for second
• Send technical team to both core.
ends of the link (at least two • Activate second core remotely.
site visits). • Remotely define the link as 2+0
• Dismantle existing radio and with L1 Multi-Carrier ABC (more
mediation device. efficient than LAG).
• Install new mediation device
(OMT or splitter).
• Re-install old radio with new
radio.
• Obtain and install Ethernet
switch for 2+0 L2 LAG.
Downtime Hours of downtime for complete Negligible downtime.
reconfiguration of the link.
Negative impact on end-user QoE.
Power consumption 100% more than 1+0 link (even Only 55% more power consumption
more with external switch). than 1+0 configuration (single core).

Page 58 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Site leasing fees Approximately double, since No impact, MultiCore system within
equipment is doubled. same small form factor unit
Warehouse Complicated, with different Simple with single-spare, versatile
management equipment for different radio for many deployment scenarios.
deployment scenarios
(standard/high power, low/high
capacity).

5.2 Innovative Techniques to Boost Capacity and Reduce Latency

IP-20C utilizes Ceragon’s innovative technology to provide a high-capacity low-
latency solution. The total switching capacity of IP-20C is 5 Gbps or 3.125 mpps,
whichever capacity limit is reached first. IP-20C 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.
IP-20C supports Line-of-Sight (LoS) Multiple Input Multiple Output (MIMO), which
is the latest leap in microwave technology, enabling operators to double spectral
efficiency. IP-20C’s MultiCore architecture enables operators to double and
quadruple capacity over a single frequency channel with 2x2 and 4x4 MIMO
configurations.
IP-20C’s Header De-Duplication option enables IP-20C to boost capacity and
provide operators with efficient spectrum utilization, with no disruption of traffic
and no addition of latency.
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.
Ceragon was the first to introduce hitless and errorless Adaptive Coding
Modulation (ACM) to provide dynamic adjustment of the radio’s modulation to
account for up-to-the-minute changes in fading conditions. IP-20C utilizes
Ceragon’s advanced ACM technology, and extends it to the range of QPSK to 2048
QAM.
IP-20C also supports Cross Polarization Interference Canceller (XPIC). XPIC enables
operators to double their capacity with a single IP-20C unit directly mounted to
the antenna. The dual core IP-20C utilizes dual-polarization radio over a single-
frequency channel, thereby transmitting two separate carrier waves over the
same frequency, but with alternating polarities. XPIC can be used in standard
MultiCore 2+0 dual polarization configurations. XPIC is also an essential building
block for 4x4 MIMO, enabling each IP-20C unit to operate with two cores over the
same frequency channel using dual polarization.
IP-20C can be used in MultiCore 1+1 and 2+2 HSB configurations. A 1+1
configuration can easily be scaled up into a 2+2 configuration by activating the
second core on each IP-20C unit.

Page 59 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

This section includes:

• Capacity Summary
• Line of Sight (LoS) MIMO
• Space Diversity
• Advanced Space Diversity (ASD)
• Advanced Frequency Reuse (AFR)
• Header De-Duplication
• Frame Cut-Through
• Multi-Carrier ABC
• Adaptive Coding Modulation (ACM)
• Multiband (Enhanced Multi-Carrier ABC)
• Cross Polarization Interference Canceller (XPIC)
• Unit (External) Protection
• ATPC
• Radio Signal Quality PMs
• Radio Utilization PMs

5.2.1 Capacity Summary

The total switching capacity of IP-20C is 5 Gbps or 3.125 mpps, whichever capacity
limit is reached first.
Each of the two cores in an IP-20C unit can provide the following radio capacity:
• Supported Channels – 3.5/7/14/28/40/56/80 MHz channels
• All licensed bands – U5.7, L6, U6, 7, 8, 10, 11, 13, 15, 18, 23, 26, 28, 32, 38, 42 GHz
• High Modulation – QPSK to 2048 QAM

For additional information:

• Radio Capacity Specifications

5.2.2 Line of Sight (LoS) MIMO

Line-of-Sight (LoS) Multiple Input Multiple Output (MIMO) is the latest leap in
microwave technology, enabling operators to double or quadruple spectral
efficiency.
MIMO originated as a non-line-of-sight (NLoS) technology, exploiting signal multi-
path caused by reflections from various physical obstacles by using multiple
transmitters and receivers to increase spectral efficiency by spatially multiplexing
multiple bitstreams over the same frequency channel.
In LoS microwave, the non-LoS multipath signal is weak and unusable for the
purpose of MIMO. Instead, LoS MIMO achieves spatial multiplexing by creating an
artificial phase de-correlation by deliberate antenna distance at each site in
deterministic constant distance.

Page 60 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 32: NLoS MIMO (Left) and LoS MIMO (Right) Compared
At each site in an LoS MIMO configuration, data to be transmitted over the radio
link is split into two bit streams (2x2 MIMO) or four bit streams (4x4 MIMO).
These bit streams are transmitted via two antennas. In 2x2 MIMO, the antennas
use a single polarization. In 4x4 MIMO, each antenna uses dual polarization. The
phase difference caused by the antenna separation enables the receiver to
distinguish between the streams.

Figure 33: LoS MIMO – Transmitting and Receiving on a Single Frequency Channel
The following figure illustrates a 2x2 MIMO configuration consisting of two
transmitters and two receivers on each side of the link, transmitting via two
antennas on each side of the link. The antenna pairs on either side of the link are
spaced at specific distances from each other based on the calculations described
in Antenna Separation Criteria for LoS MIMO on page 63.

Figure 34: General LoS MIMO Antenna Setup

In this illustration:
• h1 and h2 represent the spatial separation between the antenna pairs at each
side of the link.
• d11, d21, d12, and d22 represent the signal path lengths.

Page 61 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

• D represents the link distance.

Each signal arrives at the other side of the link at a different phase. The phases are
determined by the varying path lengths which, in turn, are configurable by
adjusting the degree of antenna separation.

5.2.2.1 4x4 LoS MIMO

Although the illustration above uses 2x2 MIMO for the sake of simplicity, the
same basic principles apply to 4x4 MIMO.
IP-20C utilizes its MultiCore architecture to achieve 4x4 MIMO with two IP-20C
units supporting four cores at each side of the link. By utilizing dual vertical and
horizontal polarization, the 4x4 MIMO configuration can utilize a single frequency
and just two antennas to achieve the benefits of a 4x4 configuration. This enables
operators to quadruple radio throughput using the same spectrum, with half the
form factor of a conventional system.

Page 62 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 35: 4x4 MIMO: Two MultiCore Units Directly Mounted to the Antenna

5.2.2.2 MIMO Resiliency

In hardware failure scenarios, 4x4 MIMO provides a resiliency mechanism that
enables the link to continue functioning as a 2+0 XPIC link. This enables continued
flow of traffic on the link until full MIMO service can be restored.
Each pair of IP-20C units in a 4x4 MIMO configuration consists of a master and a
slave unit, as shown in the following figure.
V
Master
H V
4x4 MIMO Master

Slave H Link Slave

Figure 36: 4x4 MIMO Configuration – Master and Slave Units

The following scenarios trigger the MIMO resiliency mechanism:
• Cable failure of the Cat5 management cable used for inter-CPU
communication between the two IP-20C units
• Cable failure of the coaxial cable used for clock source sharing between the
two IP-20C units
• Cable failure of the data sharing optical cable between the two IP-20C units
• Master unit hardware fault
• Slave unit hardware fault
• Clock source failure in the master unit

Page 63 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

In the event of a cable failure or total loss of the slave unit, the local and remote
slave units are muted and the master units continue to function as a 2+0 XPIC link,
with half the capacity of the original MIMO link.

V
Master
H
2+0 XPIC Master

Slave
(Muted)
X X Slave
(Muted)

Figure 37: MIMO Resiliency – Master Unit Half-Capacity Link

In the event of a total loss of the master unit or a clock source failure in the
master unit, the local and remote master units are muted and the slave units
continue to function as a 2+0 XPIC link, with half the capacity of the original
MIMO link.

Master
(Muted)
X X Master
(Muted)
V

Slave
H
2+0 XPIC Slave

Figure 38: MIMO Resiliency – Slave Unit Half-Capacity Link

Switchover to half-capacity operation is automatic, and takes approximately 30
seconds.
To restore full MIMO operation, the faulty equipment must be replaced. The
replacement equipment must be pre-configured to the same configuration as the
equipment being replaced. Once the new equipment has been properly installed
and, if necessary, powered up, the system automatically reverts to full 4x4 MIMO
operation, with no user intervention required.

5.2.2.3 Benefits of LoS MIMO

Increased Capacity
2x2 LoS MIMO enables transmission of two independent bitstreams over the
same frequency channel, using the same polarization, doubling the capacity of a
single SISO Link (same capacity as XPIC but using only one polarization).
4X4 LoS MIMO, with dual polarization, enables transmission of four independent
bitstreams over the same frequency channel, quadrupling the capacity of a single
SISO link.

Reduced Spectrum License Fees

Beyond the increase in capacity that MIMO provides, MIMO enables operators to
multiply spectral efficiency, thereby spending up to 50% less on frequency
licensing fees.

Page 64 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Improved System Gain

Combining received signals from both antennas in a MIMO system boosts system
gain by 3dB. This is similar to the improvement that can be achieved by space
diversity systems with IF combining.
Further improvement to system gain can be achieved as a tradeoff for some of
the increased capacity MIMO provides by reducing the modulation scheme,
thereby increasing both Tx power and Rx sensitivity. In this way, system gain can
be increased by up to 20dB. This increase can be used to increase link distances or
reduce antenna size. It can also enable the operator to utilize higher frequencies
for long-distance links.

5.2.2.4 Antenna Separation Criteria for LoS MIMO

The following equation provides the criterion for optimal antenna separation in a
LoS MIMO configuration:

𝐷∙𝑐
ℎ1 ∙ ℎ2 =
2𝑓

Figure 39: LoS MIMO: Criterion for Optimal Antenna Separation

In this equation:
• h1 and h2 denote the respective lengths of antenna separation on both sides
of the link (in meters).
• D denotes the link distance (in meters).
𝑚
• c denotes the speed of light (3 × 108 ).
𝑠𝑒𝑐
• f denotes the link frequency (in Hz).
In a symmetrical topology, that is, a link topology in which the antenna separation
is equal on both sides of the link, the following equation provides the optimal
antenna separation distance:

LoS MIMO: Criterion for Optimal Antenna Separation in Symmetrical Topology

𝐷∙𝑐
ℎ𝑜𝑝𝑡𝑖𝑚𝑎𝑙 = √
2𝑓

Page 65 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following diagram provides a rough idea of the separation required between
antennas for different link spans using different frequencies.

Figure 40: LoS MIMO: Optimal Antenna Separation vs. Link Distance
It is important to note that antenna separation does not have to be symmetrical.
Link topologies will often be constrained by factors that limit antenna separation
on one side of the link, such as tower space and mechanical load. Link planners
can compensate for such constraints by adjusting the antenna separation on the
other side of the link so that the product of the antenna separation length
satisfies the equation for Optimal Antenna Separation. Refer to Figure 39: LoS
MIMO: Criterion for Optimal Antenna Separation on page 65.

Page 66 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.2.5 LoS MIMO Link Robustness

One of the main considerations with LoS MIMO operation is the sensitivity of the
link to the accuracy of the installation: how does inaccurate antenna separation
affect the quality of the MIMO link? The following figure shows antenna
separation sensitivity in IP-20C’s MIMO implementation.

Figure 41: Continuum of Optimal LoS MIMO Installation Scenarios

This figure shows how signal-to-noise ratio (SNR) or equivalently, mean square
error (MSE), is affected by using sub-optimal antenna separation, relative to the
optimal separation, ℎ𝑜𝑝𝑡𝑖𝑚𝑎𝑙 . In the case of optimal installation (point A), a 3dB
MSE improvement is achieved compared to a 1+0 SISO link. It also demonstrates
that the tradeoff between antenna separation on both sides of the link yields a
continuous line of optimal installation scenarios, and that sub-optimal antenna
separation on one side can be offset by the separation on the opposite side.
So, for example, in cases where deviation in antenna separation is 10% on each
side (point B), approximately 1dB in MSE may be lost compared to an optimal
installation, yielding only a 2dB MIMO gain (compared to a 1+0 SISO link).
A second example demonstrates that 20% deviation on each side (point C) will
lead to a similar MSE as in the SISO reference (3dB decline cancelling the 3dB
MIMO gain), but still enjoying most of the capacity gain of MIMO. This shows that
IP-20C’s LoS MIMO implementation is quite immune to sub-optimal antenna
installation, and perfect accuracy does not have to be established during
installation in order to gain the capacity benefit.

Page 67 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following figure further demonstrates how sub-optimal antenna separation

affects capacity relative to an optimal installation.

Figure 42: Effect of Sub-Optimal Installation on Capacity (Maximum Capacity is at

1024 QAM)

5.2.2.6 Antenna Characteristics for LoS MIMO

Although it may be convenient to separate antennas vertically in certain
deployments, such as on masts and poles, MIMO antenna separation does not
need to be vertical. Horizontal or diagonal separation provide the same
performance as vertical separation, as long as the separation distances adhere to
the formula for optimal antenna separation. Both sides of the link must be
consistent in this regard, e.g., both horizontal, both diagonal, or both vertical.
For each signal, both signal paths must be received at the same power level. This
means that if, for any reason, the size of one of the antennas needs to be smaller,
the link budget must be compensated. As shown in the figure below, this can be
achieved in either of the following ways:
• Lowering TX power on the antenna that is paired with the smaller antenna, as
shown in Figure B below.
• Matching the size of both antennas in the pair, as shown in Figure C below.

Page 68 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 43: Asymmetrical Antenna Setup

5.2.3 Space Diversity

FibeAir IP-20C’s MIMO capabilities can also be utilized, with minor adjustments, to
provide Baseband Combining (BBC) Space Diversity (SD). An SD configuration is
based on either a 2x2 MIMO installation (for 1+0 SD) or a 4x4 MIMO installation
(for 2+2 HSB SD, using two IP-20C units), with antenna separation based on SD
requirements.
Alternatively, a 1+1 HSB-SD configuration is available. Instead of using a MIMO
installation, 1+1 HSB-SD uses two IP-20C units combined and connected to the
primary and diversity antennas via a dual coupler and two flexible waveguides.
The link is protected via external protection, so that if a protection switchover
occurs, the standby unit becomes the activate unit, and the link continues to
function with full space diversity.
In all SD modes, the transmitter or transmitters connected to the diversity
antenna is muted to achieve a configuration that consists of a single transmitter
and two receivers.
When IP-20C is configured for SD operation, the signal is combined at the
Baseband level to improve signal quality selective fading.

Page 69 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.3.1 1+0 Space Diversity

A 1+0 Space Diversity configuration utilizes a single IP-20C on each side of the link,
with both radio carriers activated. The second carrier is muted. On the receiving
side, the signals are combined to produce a single, optimized signal.

Carrier 1
1+0 SD Carrier 1

Carrier 2
(Muted)
X Carrier 2

Figure 44: 1+0 Space Diversity

5.2.3.2 2+2 Space Diversity

A 2+2 Space Diversity configuration utilizes two IP-20C units on each side of the
link, with both radio carriers activated in each unit. In each IP-20C unit, both radio
carriers are connected to a single antenna. One GbE port on each IP-20C is
connected to an optical splitter. Traffic must be routed to an optical GbE port on
each IP-20C unit.
Both carriers of the slave unit are muted. On the RX side, each unit receives a dual
polarization signal from the remote master unit, which includes the data streams
from both carriers. The slave unit shares the data stream it receives with the
master unit, and the master unit combines each data stream to produce a single,
optimized signal for each carrier.
V Master
Master
H V
H
2+2 SD Data Sharing
Cable

Slave Slave
X Muted

Figure 45: 2+2 Space Diversity

2+2 Space Diversity provides equipment protection as well as signal protection. If
one unit goes out of service, the other unit takes over and maintains the link until
the failed unit is restored to service and Space Diversity operation resumes.
In effect, a 2+2 HSB configuration is a protected 2+0 Space Diversity configuration.
Each IP-20C monitors both of its cores. If the active IP-20C detects a radio failure
in either of its cores, it initiates a switchover to the standby IP-20C.

Page 70 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Optical
GbE
Port
Modem 1 RF Chain
GbE
Port
Modem 2 RF Chain

Optical
Splitter Active IP-20C Unit

Optical
GbE
Port
Modem 1 RF Chain
GbE
Port

Modem 2 RF Chain

Standby IP-20C Unit

Figure 46: MultiCore 2+2 Space Diversity

5.2.3.3 1+1 HSB with Space Diversity

A 1+1 HSB-SD configuration utilizes two IP-20C units on each side of the link, with
both radio carriers activated. On each unit, the carrier connected to the diversity
antenna is muted. On the receiving side, the signals are combined in the active
unit to produce a single, optimized signal. The link is protected via external
protection, so that if a protection switchover occurs, the standby unit becomes
the activate unit, and the link continues to function with full space diversity.

Carrier 1 (Muted)
Carrier 2 1+1 HSB-SD Carrier 1 (Muted)
Carrier 2

Figure 47: 1+1 HSB with Space Diversity

Page 71 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.4 Advanced Space Diversity (ASD)

Advanced Space Diversity (ASD) provides significant savings by enabling space
diversity with only three IP-20C units and three antennas. This means a 25%
reduction from standard space diversity implementations with corresponding
savings in CAPEX and OPEX due to the reduction in equipment and tower load
made possible by ASD.
ASD provides significant increases in system gain and reduces or eliminates the
effects of fading and multipath.

5.2.4.1 ASD Implementation

ASD is implemented as an asymmetrical link with three antennas and three IP-20C
units, as shown in Figure 48.
• In one direction, two transmitters transmit to one receiver. ASD increases
system gain in this direction by 6 dB.
• In the other direction, transmissions from one transmitter are received by two
receivers. This is a simple case of Space Diversity, and provides a 3 dB increase
in system gain.

Master Master
Network RF Network
Switch Eth Port
Processor
Modem 1
Chain V +6dB V RF Chain Modem 1
Processor Eth Port Switch
OMT f1 f1 OMT
Modem 2 RF Chain H H RF Chain Modem 2
+3dB
Communications

Source Sharing
Data Sharing
Protection

Network
Processor
Modem 1 RF Chain V
OMT f1
Modem 2 RF Chain H

Slave

Figure 48: Advanced Space Diversity (ASD)

The ability to implement space diversity with only three IP-20 units and three
antennas is made possible by the use of standard space diversity in one direction
and a phase-synchronized beam-forming mechanism in the other direction. Each
IP-20C unit is installed in a 2+0 XPIC configuration, with an OMT as the mediation
device and a dual-polarization antenna. Alignment is performed using an XPIC
script. Following alignment, the ASD groups are configured and a special ASD
script (28 MHz or 56 MHz) is applied to each of the three ASD groups.
• MRMC Script 1951 – 28 MHz
• MRMC Script 1953 – 56 MHz
For script details, see Radio Scripts on page 227.
Figure 49 shows the data paths between Site 1, with two IP-20C units and two
antennas, and Site 2, with one IP-20C unit and one antenna.

Page 72 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Site 1 Site 2
+3dB +6dB
f1 f1

f1

Figure 49: ASD Data Paths

The data path from Site 1 to Site 2 includes the same TX signals being sent from
the main and diversity radios at Site 1 (RX diversity). IP-20 uses beam forming
technology to achieve optimal reception by the IP-20C unit at Site 2. This
quadruples the signal’s strength, adding 6dB in system gain and resilience to
selective fading.
The data path from Site 2 to Site 1 is similar to that of a standard space diversity
configuration. The signal transmitted from Site 2 is received by the main and
diversity antennas at Site 1 (RX diversity). These signals are combined using
Baseband Combining (BBC). This adds 3dB in system gain since the signal
practically doubles its level as it is received in a phase-synchronized manner by
two receivers.

5.2.4.2 Benefits of ASD

ASD provides the benefits of space diversity with 25% less equipment. These
benefits include:
• Up to 25% savings in CAPEX and OPEX by reducing equipment and tower load.
• Ability to use ASD in links with tower space limitations. The side of the link
with tighter space restriction can be utilized for the single unit installation,
while the other side contains two IP-20 units and two antennas.
• 6dB increase in system gain from the side of the link with two antennas to the
side of the link with one antenna.
• 3dB increase in system gain from the side of the link with one antenna to the
side of the link with two antennas.
• Mitigation of fading and multipath.
ASD is especially useful for long-haul links, in which mitigating the effects of fading
and multipath are particularly important. But the increased system gain and
mitigation of fading and multipath that ASD provides brings significant value for
all types of links.

Page 73 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.5 Advanced Frequency Reuse (AFR)

To thrive in the increasingly competitive, hyper-connected world, network
operators must offer new revenue-generating services while constantly upgrading
their delivery capabilities. Operators must rapidly expand the capacity of their
networks by densifying their networks, which means effectively adding many new
cell sites.
Because backhaul is a major component of sustainable network infrastructure,
backhaul spectrum management is a crucial ingredient for success. A lack of
available backhaul frequencies can restrict new cell-site deployment or
dramatically increase the deployment cost due to use of alternative technologies.
Advanced Frequency Reuse (AFR), based on Ceragon’s unique Multicore
technology, breaks through deployment restrictions to give operators the
freedom to deploy cell sites wherever and whenever they are needed. AFR
enables reuse of frequencies and establishment of wider channels in much denser
deployment scenarios than possible through conventional link-spacing
parameters.

5.2.5.1 AFR Overview

AFR enables operators to reduce the angular separation requirement between
links at the same frequency channel and the same polarization from the currently
required 90-120° range to angular separation as low as 10-40°. This enables
operators to deploy an additional adjacent link at the same frequency spot,
thereby simplifying network deployment.
AFR can also be used to boost the capacity of existing links operating in adjacent
channels by enabling wider channels in AFR mode.
By enabling operators to reuse the same frequency spots with nominal
interference at angles that are significantly narrower than would otherwise be
possible, AFR provides real value in congested network scenarios in which
spectrum can be a significant expense and a bottleneck.
AFR works in conjunction with ACM to enable links to achieve high modulations
and high capacities despite the presence of adjacent links transmitting at the
same frequency. By mitigating the effects of side lobe interference (SLI), AFR can
reduce adjacent link interference to levels that enable links that would otherwise
be limited to QPSK modulation to transmit at modulations of up to 2048 QAM.
This enables deployment of links that would otherwise be impractical to deploy
due to high interference.

Page 74 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

F1

F2

F1 F2 F3 F4 F3
< 15O

F4

Figure 50: Deployment Scenario without AFR

F1

F1

F1 F2 F2
15O

F2

Figure 51: Deployment Scenario with AFR

AFR can also help operators increase the capacity of existing networks by
increasing the channel allocation of adjacent links so that a single, wider channel
can be used side-by-side in place of two separate, narrow channels.
Deployment of wider frequency channels is increasingly being required by
operators in order to achieve better utilization of allocated frequency blocks. With
wider channels, fewer guard bands are required, enabling more spectrum to be
used for actual signal. However, spectrum for these wider bands is not always
available, and when it is available, it can be expensive and time-consuming to
obtain.

Page 75 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following figure depicts a deployment scenario in which Link 1 uses channel 1
(f1), Link 2 uses channel 2 (f2), Link 3 uses channel 3 (f3), and Link 4 uses channel
4 (f4).

F1

F2

F1 F2 F3 F4 F3

F4

Figure 52: Network Using Four Narrow Channels

The following figure depicts the same network following AFR implementation. AFR
has enabled the operator to reconfigure the network so that Link 1 and Link 2
share a wider channel (f1¹) consisting of channel 1 and channel 2, and Link 3 and
Link 4 share a wider channel (f2¹) consisting of channel 3 and channel 4. By
enabling each pair of links to share spectral resources that were previously
separate, AFR enables the operator to double the capacity of the network
deployment.

Page 76 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

F1'

F1'
F1' F2'

F1 F2 F3 F4 F2'

F2'

Figure 53: Converting to Wider Channels with AFR

In some cases, an operator may need to densify a network by placing an
additional site between two existing sites, each transmitting at a different
frequency spot. In the example shown in the following figure, topological or other
factors may prevent the operator from simply increasing the coverage area
and/or the capacity of the existing inks, and spectrum for a third frequency spot
for an additional link might not be available.

F1

No network
Topological coverage
Barriers

F2

Figure 54: Network Requiring Densification

In the scenario depicted in the following figure, AFR enables the operator to reuse
one of the existing frequency spots, despite the narrow angular separation
between the links.

Page 77 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

F1

F1

F2

Figure 55: Densification Example with AFR

5.2.5.2 AFR Configurations

AFR can be used in the following configurations:
• AFR 1+0
• AFR 1+1
• AFR 2+0 (XPIC)
Note: AFR 1+1 and AFR 2+0 (XPIC) are planned for future release.

AFR 1+0
In an AFR 1+0 configuration, a Multicore FibeAir IP-20C unit is deployed at the hub
site and two FibeAir IP-20C or IP-20S units are deployed in two tail sites. Each
carrier at the hub site is known as an “aggregator.”
The hub site utilizes a single FibeAir IP-20C unit with two radio carriers. Each
carrier is in a link, via its own directional antenna, with a tail site that consists of a
FibeAir IP-20C or IP-20S unit.
Note: The links should be located so as to ensure that the two radio
path do not cross.

Page 78 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

F1
Tail Site 1
IP-20C or IP-20S
F1
One frequency
spot Low angular F1
separation

Tail Site 2
IP-20C or IP-20S

Hub Site
Multicore IP-20C

Figure 56: AFR 1+0 Deployment

AFR 1+1
AFR 1+1 uses two Multicore FibeAir IP-20C units at the hub site and two FibeAir
IP-20C or IP-20S units at each tail site. At each hub site, one IP-20 unit protects the
other unit, so that if a problem takes place on any IP-20 radio carrier, the other IP-
20 unit takes over in active mode and the original active IP-20 unit switches to
standby mode.

Backup IP-20C or
IP-20S Unit
Tail Site 1

F1

Active IP-20C or
IP-20S Unit Backup IP-20C or
IP-20S Unit
Backup
IP-20C Unit

F1
Tail Site 2
Active IP-20C or
IP-20S Unit
Hub Site Active
IP-20C Unit

Figure 57: AFR 1+1

AFR 2+0 XPIC

AFR 2+0 XPIC combines the benefits of both XPIC and AFR to enable high-density
links while minimizing the required number of frequency spots.
AFR 2+0 XPIC uses two FibeAir IP-20C units at the hub site and one FibeAir IP-20C
unit at each tail site. For each unit at the hub site, both carriers form an XPIC link
with one of the tail sites, using a dual-polarization antenna. The two units at the

Page 79 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

hub site are connected via a source sharing cable, a 10GB optic cable, and a
management cable, enabling the units to calculate the interference cancellation
necessary for both XPIC and AFR, as well as enabling common management of the
entire hub site.

Tail Site 1

F1
cal IP-20C or IP-20S
V erti
F1 -
on tal
H oriz
F1 -
IP-20C IP-20C or IP-20S

F1
ical
F1 - Vert
Tail Site 2
zontal
F1 - Hori
Hub Site

IP-20C

Figure 58: AFR 2+0 XPIC

5.2.5.3 AFR Mode of Operation

Without AFR, links using the same frequency must generally be angularly
separated by at least 90-120° in order to reduce the interference between the
links. AFR enables the placement of links using the same frequency at much
smaller angular separation by adjusting for the effect of the interference in such a
way as to compensate for the reciprocal interference at the tail site antennas.
AFR implements interference cancelation techniques at the hub site. There are
separate interference cancellation methods for the Tx path and the Rx path. At
the Tx path, the two cores work together to cancel the interferences for each of
the tail sites. On the Rx path of the hub site, the interference compensation is
implemented by interference cancellation, similar to the XPIC mechanism, in each
of the cores.
The AFR interference cancellation is done entirely in at the hub site. Therefore,
there is no need for any connection between the tail sites in order to enable the
operation of these links with AFR.

Page 80 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Tail Site 1

F1
IP-20C or IP-20S
A
Link
er
rfer
Inte
Multicore IP-20C IP-20C or IP-20S
Interferer
F1
Link B

Hub Site Tail Site 2

Figure 59: Interference Mitigation in AFR

5.2.5.4 AFR Calculation Application

Ceragon has developed the AFR Calculation application to help network planners
maximize the value AFR can provide to Ceragon customers. This application helps
the network planner identify links that can be deployed using AFR.
The AFR Calculation application is a standalone application that runs on the user’s
PC or laptop. It is completely independent from CeraOS and the IP-20 device.
A detailed explanation of network planning using AFR, including step-by-step
instructions for using the AFR Calculation application, is provided in a separate
document, the Advanced Frequency Reuse (AFR) Link Planning Guide.

5.2.6 Header De-Duplication

IP-20C offers the option of Header De-Duplication, enabling operators to
significantly improve Ethernet throughout 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-20C still removes the IFG
and Preamble fields. This mechanism operates automatically
even if Header De-Duplication is not selected by the user.

Page 81 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 60: 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.
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.

Page 82 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following graphic illustrates how Header De-Duplication can save up to 148
bytes per frame.

IP-20C

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
4/6 bytes compressed

Tunneling Layer | GTP (LTE) / GRE

6 bytes compressed

End User Inner Layer 3 | IPv4/IPv6

18/40 bytes compressed

End User Inner Layer 4 | TCP/UDP

4/6 bytes compressed

End User

Figure 61: 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)
• 25% (512 byte packets)
• 8% (1518 byte packets)

Page 83 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.6.1 Header De-Duplication Counters

In order to help operators optimize Header De-Duplication, IP-20C 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 de-duplication settings, the operator can
adjust these settings to ensure that the network achieves the highest possible
effective throughput.

5.2.7 Frame Cut-Through

Related topics:
• Ethernet Latency Specifications
• 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:
◦ Improved QoE for VoIP and other streaming applications.
◦ Expedited delivery of critical control frames.

Page 84 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 62: Propagation Delay with and without Frame Cut-Through

5.2.7.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 pre-empted 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 63: 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.

Page 85 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 64: Frame Cut-Through

5.2.8 Multi-Carrier ABC

Multi-Carrier Adaptive Bandwidth Control (ABC) is an innovative technology that
creates logical bundles of multiple radio links and optimizes them for wireless
backhaul applications. Multi-Carrier ABC enables separate radio carriers to be
shared by a single Ethernet port. This provides an Ethernet link over the radio with
double capacity, while still behaving as a single Ethernet interface.
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. 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.

Page 86 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Modem Modem
(Carrier 1) (Carrier 1)

Eth Traffic Eth

Traffic Splitter
Combiner

Modem Modem
(Carrier 2) (Carrier 2)

Figure 65: Multi-Carrier ABC Traffic Flow

5.2.8.1 Multi-Carrier ABC Operation

Multi-Carrier ABC is designed to achieve 100% utilization of available radio
resources by optimizing the way traffic is distributed between the multiple
wireless links. Traffic is forwarded over available radio carriers in a byte-by-byte
manner, as shown in the figure below. This enhances load balancing.

Figure 66: Multi-Carrier ABC Traffic Distribution

Traffic distribution is proportional to the available bandwidth in every link:
• If both links have the same capacity, half the data is sent through each link.
• In ACM conditions, the links could be in different modulations; in this case,
data is distributed proportionally in order to maximize the available
bandwidth.
The granular, byte-by-byte distribution of traffic between radio links enables IP-
20C’s Multi-Carrier ABC implementation to maintain optimal load balancing that
accounts for the condition of each radio link at any given moment. This means
that if a link shifts to a lower ACM modulation point, the Multi-Carrier ABC load
balancing mechanism is notified immediately and adjusts the traffic distribution
by sending less traffic over the link with the lower modulation and more traffic to
links operating at a higher modulation. If there is a failure in one or more of the
links, the load balancing mechanism implements graceful degradation by directing
traffic to the operational links.

Page 87 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 67: Multi-Carrier ABC Load Balancing with Different ACM Points

5.2.8.2 Graceful Degradation of Service

Multi-Carrier ABC provides for protection and graceful degradation of service in
the event that one of the links fails. This ensures that if one link is lost, not all data
is lost. Instead, bandwidth is simply reduced until the link returns to service.
Graceful degradation in Multi-Carrier ABC is achieved by blocking one of the radio
links from Multi-Carrier ABC data. When a link is blocked, the transmitter does not
distribute data to this link and the receiver ignores it when combining.
The blocking is implemented independently in each direction, but TX and RX
always block a link in a coordinated manner.
The following are the criteria for blocking a link:
• Radio LOF
• Link ID mismatch
• Radio Excessive BER – user configurable
• Radio Signal degrade – user configurable
• User command – used to debug a link
When a radio link is blocked, an alarm is displayed to users.

5.2.8.3 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) on page 150) 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.

Page 88 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

External
Switch LAG

Ethernet Link Ethernet Link Multi-Carrier ABC Link

Upstream IP-20 Unit

Alternate Link

Figure 68: 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.

5.2.8.4 Multi-Carrier ABC and ACM

Each carrier can change its ACM profile, with a maximum of 30 msec between
each switch in modulation. There is no limitation upon the profile difference
between carriers, so that one carrier can be operating at the lowest possible
profile (QPSK) while the other is operating at the highest possible profile (2048
QAM).
Users can configure an ACM drop threshold and an ACM up threshold for the
Multi-Carrier group. If the ACM profile falls to the configured drop threshold or
below for a carrier in the group, that carrier is treated as if it is in a failure state,
and traffic is re-routed to the other carriers. When the ACM profile rises to the
configured up threshold, the failure state is removed, and traffic is again routed to
the affected carrier. By default, this mechanism is disabled. When enabled, the
default value for the ACM drop threshold is QPSK and the default value for the
ACM up threshold is 8 QAM.

5.2.8.5 Configuring Multi-Carrier ABC

In order to use Multi-Carrier ABC, both carriers in the IP-20C must be operational.
The user must first create a Multi-Carrier ABC group, and then enable the group.
To delete the Multi-Carrier ABC group, the user must first disable the group, and
then delete it.
In order for Multi-Carrier ABC to work properly, the radio links should use the
same radio script, ACM mode, and maximum ACM profile. Note that in the case of
ACM, the links can operate at different modulation profiles at the same time, but
the same base script must still be configured in both links. Users can perform a
copy-to-mate operation to ensure that both carriers have an identical
configuration.

Page 89 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

In addition to the configurable ACM profile down and up thresholds described in

Multi-Carrier ABC and ACM on page 89, users can configure the system to stop
distributing traffic to an individual carrier in any one or more of the following
circumstances:6
• Excessive BER condition
• Signal Degrade condition
Users can manually block and unblock traffic from a single carrier.

6
This feature is planned for future release.

Page 90 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.9 Adaptive Coding Modulation (ACM)

Related topics:
• Cross Polarization Interference Canceller (XPIC)
• Quality of Service (QoS)
FibeAir IP-20C employs full-range dynamic ACM. IP-20C’s ACM mechanism copes
with 100 dB per second fading in order to ensure high transmission quality. IP-
20C’s ACM mechanism is designed to work with IP-20C’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-20C’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.

5.2.9.1 Eleven Working Points

IP-20C implements ACM with 11 available working points, as shown in the
following table:

Table 10: 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 91 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 69: Adaptive Coding and Modulation with 11 Working Points

5.2.9.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.
In IP-20C units that are utilizing two cores, ACM profile switches are performed
independently for each core.

5.2.9.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.
ACM scripts can be activated in one of two modes:
• Fixed Mode. In this mode, the user can select the specific profile from all
available profiles in the script. The selected profile is the only profile that will
be valid, and the ACM engine will be forced to be OFF. This mode can be
chosen without an ACM activation key.
• 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.

Page 92 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 9, the system will not climb above the profile 9, even
if channel fading conditions allow it.

5.2.9.4 ACM Benefits

The advantages of IP-20C’s dynamic ACM include:
• Maximized spectrum usage
• Increased capacity over a given bandwidth
• 11 modulation/coding work points (~3 db system gain for each point change)
• Hitless and errorless modulation/coding changes, based on signal quality
• An integrated QoS mechanism that enables intelligent congestion
management to ensure that high priority traffic is not affected during link
fading

5.2.9.5 ACM and Built-In QoS

IP-20C’s ACM mechanism is designed to work with IP-20C’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, you can
configure IP-20C 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.

5.2.9.6 ACM in MultiCore HSB Configurations

When ACM is activated in a protection scheme such as MultiCore 1+1 HSB, the
following ACM behavior should be expected:
• 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 units follow the remote
Active TX profile (which is the only active transmitter).

Page 93 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.9.7 ACM with Adaptive Transmit Power

This feature requires:

• ACM script
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-20C 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-20C’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 70: IP-20C ACM with Adaptive Power Contrasted to Other ACM Implementations

Page 94 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.10 Multiband (Enhanced Multi-Carrier ABC)

This feature requires:

• IP-20C ESS hardware version (two SFP ports) is required in order to configure
synchronization and/or in-band management for the IP-20C
• IP-20E ESP hardware version
IP-20C can be used in Multiband configurations with FibeAir IP-20E.
Multiband bundles E-Band and microwave radios in a single group that is shared
with an Ethernet interface. This provides an Ethernet link over the radio with
capacity of up to 2.5 Gbps. A Multiband link is highly resilient because the
microwave link acts, in effect, as a backup for the E-Band link.
In normal circumstances, both links transmit simultaneously, dividing the traffic
between them. The maximum capacity of the IP-20C is 1 Gbps, with the IP-20E
handling the rest of the link’s capacity.
In the event of radio failure in one device, the other device continues to operate
to the extent of its available capacity. Thus, operators benefit from both the high
capacity of E-Band and the high reliability of microwave.

5.2.10.1 Multiband Operation

Multiband uses a master/slave architecture in which the IP-20E serves as master
and the IP-20C serves as slave. All traffic enters the node via the 10G port on the
IP-20E (Eth1). Traffic is passed to a Multiband group that includes Eth2 and the
radio carrier. The Multiband group mechanism divides the traffic, sending a
portion of the traffic via Eth2 to the IP-20C. The rest of the traffic is transmitted
via the IP-20E radio carrier.
The IP-20C acts as a pipe. Traffic is passed from Eth2 to either a single radio carrier
or 2+0 Multi-Carrier ABC group, and transmitted. To ensure a smooth traffic flow,
the following must be configured on the IP-20C:
• Automatic State Propagation, with ASP trigger by remote fault enabled.
• Bandwidth Notification.

Page 95 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 71 illustrates Multiband operation. Figure 71 illustrates a configuration that

includes synchronization and management of the IP-20C via the IP-20E. Both of
these items are optional, and requires an optical cable between Eth3 on the IP-
20E and Eth3 on the IP-20C, as described in the following sections.

Management (Optional) and/or

Management
MGMT
Synchronization (Optional)

Eth1
(10GE)

External Multiband
GbE Port
Eth2 Carrier
Switch Group

Eth3

Traffic

Master - IP-20E

Eth1

Carrier 1
Management Eth2
Pipe Carrier 2
(Optional) and/or
Synchronization
(Optional) Multi-Carrier
Eth 3
ABC Group

Slave - IP-20C

Figure 71: Multiband Operation

Page 96 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.10.2 Synchronization with Multiband Operation

SyncE and 1588 Transparent Clock can be used in Multiband nodes. In Multiband
nodes that consist of an IP-20E and an IP-20C, SyncE and 1588 Transparent Clock
can be configured for both the IP-20E and the IP-20C. SyncE and 1588 Transparent
Clock for the IP-20C require an ESS hardware version for the IP-20C (two SFP
ports).
In CeraOS 10.7, synchronization for the IP-20C requires an optical cable between
port Eth3 on the IP-20E and Eth3 on the IP-20C. In this configuration, Port 2 on the
IP-20E must be used as a CSFP port. Eth2 and Eth3 on the IP-20C must use BiDi
SFP modules.
Eth2 is used to transmit traffic to the IP-20C and Eth 3 used to transmit
synchronization to the IP-20C.

Eth2 Eth2
Port 2
(CSFP)
Eth3 Eth3

IP-20E IP-20C

Figure 72: Multiband Cable for Use with CSFP Port

Table 11: Multiband Cable for Use with CSFP Port

Cable Marketing Model Cable Description

IP-20_FO_SM_LC2SNG2LC_ARM_5m CABLE,FO,DUAL LC TO LC/LC SPLIT,5.3M,SM,3xM28

GLAND,OUTDOOR

Page 97 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.10.3 Multiband Management

The IP-20E unit in a Multiband configuration can be managed normally, as in any
other configuration.
The IP-20C unit can managed directly via its Management port, or via the IP-20E.
To manage the IP-20C via the IP-20E, an optical cable must be connected between
port Eth3 on the IP-20E and Eth3 on the IP-20C. In this configuration, Port 2 on the
IP-20E must be used as a CSFP port. A management service must be defined
between the management port of the IP-20E and Eth3 on the IP-20E. This
transmits management to Eth3 on the IP-20C.
The IP-20C unit can managed directly via its Management port, or via the IP-20E.
In-band management via the IP-20E requires an ESS hardware version for IP-20C
(two SFP ports). To manage the IP-20C via the IP-20E, an optical cable must be
connected between port Eth3 on the IP-20E and Eth3 on the IP-20C. In this
configuration, Port 2 on the IP-20E must be used as a CSFP port. To enable the
connection to both Eth2 and Eth3 on the IP-20C, use the same cable described in
Synchronization with Multiband Operation.
Note: To avoid loops, in-band management must not be configured
on the IP-20C radio.

5.2.10.4 Limitations and Interoperability of Multiband with other Features

• Multiband is fully compatible with ACM.
• The maximum capacity of a Multiband node is 2.5 Gbps.
• LLDP is not supported between Eth2 of the IP-20E and Eth2 of the IP-20C in
Multiband configurations.

Page 98 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.11 Cross Polarization Interference Canceller (XPIC)

This feature requires:

• MultiCore 2+0, 2+2, or 4x4 (MIMO) configuration
• Multi-Carrier ABC for each XPIC pair
• 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 single dual core IP-20C
unit 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 73: 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-20C’s XPIC algorithm enables detection of both streams even
under the worst levels of XPD such as 10 dB. IP-20C accomplishes this by
adaptively subtracting from each carrier the interfering cross carrier, at the right
phase and level. For high-modulation schemes such as 2048 QAM, operating at a
frequency of 28 GHz, an improvement factor of more than 23 dB is required so
that cross-interference does not adversely affect performance. In this scenario, IP-
20C’s XPIC implementation provides an improvement factor of approximately 26
db.
In addition, XPIC includes an automatic recovery mechanism that ensures that if
one carrier fails, or a false signal is received, the mate carrier will not be affected.
This mechanism also ensures that when the failure is cleared, both carriers will be
operational.7

7
The XPIC recovery mechanism is planned for future release.

Page 99 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.2.11.1 XPIC Benefits

The advantages of FibeAir IP-20C’s XPIC option include BER of 10e-6 at a co-
channel sensitivity of 10 dB.
IP-20C’s dual core architecture provides the additional benefit of enabling a
direct-mount XPIC configuration with a single IP-20C unit. Operators can double
their capacity over a single frequency channel by using IP-20C with XPIC, with
each core operating at a different polarization.

5.2.11.2 XPIC Implementation

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
h
v
H H+v H
Dual feed antenna
IP-20C (V and H feeds)
IP-20C

Figure 74: XPIC Implementation

Note: For the sake of simplicity, a dual feed V and H antenna is
depicted. IP-20C can be directly mounted using a mediation
device in this configuration.
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.

Page 100 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 75: XPIC – Impact of Misalignments and Channel Degradation

IP-20C’s XPIC reaches a BER of 10e-6 at a co-channel sensitivity of 10 dB. The
improvement factor in an XPIC system is defined as the SNR@threshold of 10e-6,
with or without the XPIC mechanism.

5.2.11.3 Conditions for XPIC

All IP-20C radio scripts support XPIC. The user must enable XPIC, after loading the
script.
In order for XPIC to be operational, all the following conditions must be met:
• The frequency of both carriers should be equal.
• The same script must be loaded in both carriers.
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.

5.2.11.4 XPIC Recovery Mechanism

Note: The XPIC recovery mechanism is planned for future release.
The purpose of the XPIC recovery mechanism is to salvage half of the capacity of
the link during a single equipment failure.
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, due to a
hardware failure, one of the four carriers malfunctions, the interference from its
counterpart will severely degrade the link at the other polarization. In this
situation, the XRSM will intervene to shut down the interfering transmitter.
Note: The XPIC recovery mechanism does not apply to link
degradation, as opposed to hardware failure. For example, link
degradation caused by fading or multipath interference does
not initiate the XPIC recovery mechanism.
The mechanism works as follows:
• The indication that the recovery mechanism should be activated is a loss of
modem preamble lock, which takes place at SNR~10dB. This indication
differentiates between hardware failure and link degradation.

Page 101 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

• The first action taken by the recovery mechanism is to cause the remote
transmitter of the faulty carrier to mute, thus eliminating the disturbing signal
and saving the working link.
• Following this, the mechanism attempts at intervals to recover the failed link.
In order to do so, it takes the following actions:
◦ The remote transmitter is un-muted for a brief period.
◦ The recovery mechanism probes the link to find out if it has recovered. If
not, it again mutes the remote transmitter.
◦ This action is repeated in exponentially larger intervals. This is meant to
quickly bring up both channels in case of a brief channel fade, without
seriously affecting the working link if the problem has been caused by a
hardware failure.
◦ The number of recovery attempts is user-configurable, with a default value
of 8. If the system does not recovery the faulty link after the defined
number of attempts, the remote transmitter is set to a permanent mute,
the recovery process is discontinued, and user maintenance must be
performed.
Note: Every such recovery attempt will cause a brief traffic hit in the
working link.
All the time intervals mentioned above (recovery attempt time, initial time
between attempts, multiplication factor for attempt time, number of retries) can
be configured by the user, but it is recommended to use the default values.
The XPIC recovery mechanism is enabled by default, but can be disabled by the
user.

5.2.12 Unit (External) Protection

IP-20C offers MultiCore 1+1 and 2+2 HSB protection configurations. 1+1 HSB can
also be implemented with Space Diversity. See 1+1 HSB with Space Diversity on
page 71.
1+1 HSB protection utilizes two IP-20C units operating in single core mode, with a
single antenna. 1+1 HSB-SD utilizes IP-20C units operating in MultiCore mode,
with two antennas. Both configurations provide hardware redundancy for
Ethernet traffic. One IP-20C operates in active mode and the other operates in
standby mode. If a protection switchover occurs, the roles are switched. The
active unit goes into standby mode and the standby unit goes into active mode.
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.
In Split Protection mode, an optical splitter is used to route traffic to an optical
GbE port on each IP-20C unit. Both ports on each IP-20C unit belong to a LAG,
with 100% distribution to the port connected to the optical splitter on each IP-20C
unit. Split Protection mode is only available for optical GbE ports on the IP-20C.

Page 102 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Optical
GbE
Port f1
Modem 1 RF Chain
GbE
Port

Optical Coupler
Splitter Active IP-20C Unit

Optical
GbE
Port
Modem 1 RF Chain
GbE
Port f1

Standby IP-20C Unit

Figure 76: 1+1 HSB Protection – Split Protection Mode

Alternatively, traffic can be routed to the IP-20C units via an external switch. This
is called Line Protection mode.
Line Protection mode can be used for electrical as well as optical GbE ports. Traffic
is routed from two GbE ports on an external switch to a GbE port on the active
and a GbE port on the standby IP-20C unit. LACP protocol is used to determine
which IP-20C port is active and which port is standby, and traffic is only forwarded
to the active port.
Note: The external switch must support LACP. IP-20C supports LACP
for purposes of line protection only.

Traffic and
LACP PDUs GbE Port f1
(LACP Modem 1 RF Chain
Mode)
GbE Port
(LACP
Mode)

Coupler
External Active IP-20C Unit
Switch

LACP PDUs GbE Port

only (LACP Modem 1 RF Chain
Mode)
GbE Port
(LACP
Mode)
f1

Standby IP-20C Unit

Figure 77: 1+1 HSB Protection – Line Protection Mode

In a 1+1 HSB configuration, each IP-20C monitors its own radio. If the active IP-
20C detects a radio failure, it initiates a switchover to the standby IP-20C.

Page 103 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

MultiCore 2+2 HSB protection utilizes two IP-20C units operating in dual core
mode, with a single antenna, to provide hardware redundancy for Ethernet traffic
in a dual core configuration. In effect, a MultiCore 2+2 HSB configuration is a
protected MultiCore 2+0 configuration.
In a MultiCore 2+2 HSB configuration, each IP-20C monitors both of its cores. If
the active IP-20C detects a radio failure in either of its cores, it initiates a
switchover to the standby IP-20C.

Page 104 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Optical
GbE
Port f1
Modem 1 RF Chain
GbE
Port
f2
Modem 2 RF Chain

Optical Coupler
Splitter Active IP-20C Unit

Optical
GbE
Port f1
Modem 1 RF Chain
GbE
Port f2
Modem 2 RF Chain

Standby IP-20C Unit

Figure 78: MultiCore 2+2 HSB Protection – Split Protection Mode

Traffic and GbE

GbE Port
f1
LACP PDUs Port
(LACP Modem 1 RF Chain
(LACP
Mode)
GbE Port Mode)
(LACP
Mode) f2
Modem 2 RF Chain

Coupler
External Active IP-20C Unit
Switch

f1
LACP PDUs Modem 1 RF Chain
GbE Port only GbE
GbE Port
(LACP Port
Mode)
(LACP
(LACP
Mode)
Mode)
f2
Modem 2 RF Chain

Standby IP-20C Unit

Figure 79: MultiCore 2+2 HSB Protection – Line Protection Mode

5.2.12.1 Management for External Protection

In an external protection configuration, the standby unit is managed via the active
unit. A protection cable connects the two IP-20C units via their management
ports. This cable is used for internal management. By placing an Ethernet splitter
on the protection port, the user can add another cable for local management (for
a detailed description, refer to Management Connection for 4x4 MIMO and
1+1/2+2 HSB Configurations on page 39). A single IP address is used for both IP-
20C units, to ensure that management is not lost in the event of switchover.
Note: If in-band management is used, no splitter is necessary.

Page 105 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Port 1

Port 2
Ethernet Splitter
MGT Protection
Local
Management Active IP-20C Unit

Protection
Port 1
Management Cable

Port 2

MGT Protection
Local
Management Ethernet Splitter
Standby IP-20C Unit

Figure 80: Internal and Local Management

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.
Note: Dynamic and hitless copy-to-mate functionality is planned for
future release.

5.2.12.2 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 for HSB protection according to their
priority, with the highest priority triggers listed first:
1 Loss of active unit
2 Lockout
3 Radio/Ethernet interface failure
4 Manual switch

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

Page 106 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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.

5.2.13.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-20C 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 protection, the ATPC override state is propagated to
the standby unit 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.

5.2.14 Radio Signal Quality PMs

IP-20C 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

Page 107 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 for Alarms and Traps on
page 213. Users can also configure an alarm that is raised if the RSL falls beneath a
user-defined threshold. See RSL Threshold Alarm on page 213.

5.2.15 Radio Utilization PMs

IP-20C 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 108 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.3 Ethernet Features

IP-20C features a service-oriented Ethernet switching fabric that provides a total
switching capacity of up to 5 Gbps or 3.125 mpps. IP-20C has an electrical GbE
interface that supports PoE, and two SFP interfaces, as well as an FE interface for
management. The second SFP interface can also be used for data sharing.
IP-20C’s service-oriented Ethernet paradigm enables operators to configure VLAN
definition, CoS, and security on a service, service-point, and interface level.
IP-20C 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.

This section includes:

• Ethernet Services Overview
• IP-20C’s Ethernet Capabilities
• Supported Standards
• Ethernet Service Model
• Ethernet Interfaces
• Quality of Service (QoS)
• Global Switch Configuration
• Automatic State Propagation and Link Loss Forwarding
• Adaptive Bandwidth Notification (EOAM)
• Network Resiliency
• OAM

5.3.1 Ethernet Services Overview

The IP-20C 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-20C 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-20C’s Ethernet services
implementation.

Page 109 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following figure illustrates the basic MEF Ethernet services model.

Figure 81: 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 110 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.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 82: 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 111 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 83: 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 84: 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 85: Rooted Multipoint EVC

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

Page 112 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.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-20C, bandwidth profiles are constructed using a full standardized TrTCM
policer mechanism.

5.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-20C 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.

Page 113 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 86: 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 12: 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
EVC) (EVPL)
E-LAN (Multipoint-to- Ethernet Private LAN (EP- Ethernet Virtual Private LAN
Multipoint EVC) LAN) (EVP-LAN)
E-Tree (Rooted Ethernet Private Tree (EP- Ethernet Virtual Private Tree
Multipoint EVC) Tree) (EVP-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.
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. Theses service attributes can be
grouped under the following categories:
• Ethernet physical interfaces
• Traffic parameters
• Performance parameters

Page 114 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

• 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 87: 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
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.

Page 115 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 88: 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 116 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 89: 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 90: 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 117 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 91: 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 92: 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
defined with this in mind, using the E-LAN service type. The EP-LAN is a Layer 2

Page 118 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 93: 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 119 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following figure provides an example of an EVP-LAN service.

Figure 94: 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 95: 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 120 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 96: 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.
The following figure provides an example of an EP-Tree service.

Page 121 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 97: 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 122 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 98: Ethernet Virtual Private Tree Example

IP-20C 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 99: Mobile Backhaul Reference Model

The IP-20C 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 123 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.3.1.4 IP-20C Universal Packet Backhaul Services Core

IP-20C 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-20C
services core, which is structured around the building blocks shown in the figure
below. IP-20C provides rich and secure packet backhaul services over any
transport type with unified, simple, and error-free operation.

Figure 100: Packet Service Core Building Blocks

Any Service
• Ethernet services (EVCs)
◦ E-Line (Point-to-Point)
◦ E-LAN (Multipoint)
◦ E-Tree (Point-to-Multipoint)8
• 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)

8
E-Tree services are planned for future release.

Page 124 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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)9
• Superb service OAM (FM, PM)10
• Carrier-grade service resiliency (G.8032)11

5.3.2 IP-20C’s Ethernet Capabilities

IP-20C 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-20C’s services core includes a rich set of tools that includes:
• Service-based Quality of Service (QoS).
• Service OAM, including granular PMs, and service activation.
• Carrier-grade service resiliency using G.803212
The following are IP-20C’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:13
◦ Multipoint (E-LAN)
◦ Point-to-Point (E-Line)
◦ Point-to-Multipoint (E-Tree)
◦ Smart Pipe

9
H-QoS support is planned for future release.
10
PM support is planned for future release.
11
G.8032 support is planned for future release.
12
G.8032 support is planned for future release.
13
Point-to-Multipoint service support is planned for future release.

Page 125 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

◦ Management
• 128K MAC learning table, with separate learning per service (including
limiters)
• Flexible transport and encapsulation via 802.1q and 802.1ad (Q-in-Q), with tag
manipulation possible at ingress and egress
• High precision, flexible frame synchronization solution combining SyncE and
1588v2
• Hierarchical QoS with 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

5.3.3 Supported Standards

IP-20C is fully MEF-9 and MEF-14 certified for all Carrier Ethernet services. For a
full list of standards and certifications supported by IP-20C, refer to the following
sections:
• Supported Ethernet Standards
• MEF Certifications for Ethernet Services

5.3.4 Ethernet Service Model

IP-20C’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-20C’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).

Page 126 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

P2P
Service

SNP SNP

UNI

P2P
NNI
Service
SAP SAP
Multipoint SNP SNP Multipoint
SN
SA Service Service
SNP SNP
PP SNP SNP

IP-20C
SAP SAP

SNP SNP

Multipoint Multipoint
Service Service
SNP
SNP

SAP
P2P
Service
SNP
SNP

SNP SNP
IP-20C IP-20C

Multipoint
Service
SNP

SNP SAP

IP-20C

Figure 101: IP-20C Services Model

The IP-20C 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.
Users can define up to 64 services on a single IP-20C. 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-20C contains a pre-defined management service (Service ID 257). 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.

Page 127 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Note: Management services can hold up to 30 SPs.

The following figure illustrates the IP-20C services model, with traffic entering and
leaving the network element. IP-20C’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 102: IP-20C Services Core

5.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-20C.
• 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.

Page 128 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 103: IP-20C Services Flow

5.3.4.2 Service Types

IP-20C supports the following service types:
• Point-to-Point Service (P2P)
• MultiPoint Service (MP)
• Management Service
• Point-to-Multipoint Service (E-Tree)
Note: Support for E-Tree services is planned for future release.

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.

Page 129 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following figure illustrates a P2P service.

P2P Service

Port 1 Port 4
SP SP
SAP
SAP

Port 2
P2P Service

SP
SAP SP
SAP
Port 3 Port 5

Figure 104: 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.
The following figure illustrates a Multipoint service.

Multipoint Service
Port 1 SP SP Port 4
SAP SAP

SP
SAP
Port 2

SP SP
SAP
SAP

Port 3 Port 5

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

Page 130 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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-20C can learn up to 131,072 Ethernet source MAC addresses. IP-20C performs
learning per service in order to enable the use of 64 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.
The following table illustrates the operation of the learning and forwarding
mechanism.

Table 13: 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.

Page 131 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Management Service (MNG)

The management service connects the local management port, the network
element host CPU, and the traffic ports into a single service. The management
service is pre-defined in the system, with Service ID 257. The pre-defined
management service has a single service point that connects the service to the
network element host CPU and the management port. 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.
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
port is also connected to the service, but its service point is not visible to users.
The management port is enabled by default and cannot be disabled.
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
SP SP
SAP
SAP
Local Management

CPU

Figure 106: 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-20C services have the following attributes:
• Service ID – A unique ID 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 257 is reserved for the pre-defined
Management service.

Page 132 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

• 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.
• 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-20C’s
hierarchical classification mechanism, refer to Classification on page 153.
• 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.

5.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-20C 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.

Page 133 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

MNG

MNG MNG

MNG
MNG

MNG MNG

MNG MNG

MNG MNG

MNG

Figure 107: 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.
• 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.

Page 134 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

Page 135 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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.

Pipe Pipe Pipe Pipe

Figure 109: 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
PIPE
SNP

SAP

PIPE

SNP

SAP
SAP

Base Station

Figure 110: SAP, SNP and Pipe Service Points in a Microwave Network

Page 136 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following table summarizes the service point (SP) types available per service
type.

Table 14: Service Point Types per Service Type

Service point 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 137 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

PIPE classification
Pipe service points can be used with the following Attached Interface Types:
• Dot1q – All C-VLANs and untagged frames that enter the interface are
classified to the same service point.
• S-Tag – All S-VLANs and untagged frames that enter the interface are
classified to the same service point.

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 15: 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 138 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Table 16: Service Point Type-Attached Interface Type Combinations that can Co-Exist on the Same Interface
SP Type Attached SAP Bundle Bundle All to One QinQ SNP 802.1q S-Tag Pipe S-Tag MNG QinQ S-Tag
Interface Type 802.1q C-Tag S-Tag 802.1q 802.1q

SAP 802.1q Yes Yes No No No No No Only for P2P No Yes No No

Service
Bundle C-Tag Yes Yes No No No No No Only for P2P No Yes No No
Service
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 No No No No No No No No
One 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 No Yes No No
Service
S-Tag No No No No No No Yes No Only for P2P No No Yes
Service
Pipe 802.1q Only for Only for No No No Only for No Only one Pipe SP No Yes No No
P2P Service P2P P2P Service Per Interface
Service
S-Tag No No No No No No Only for No Only one Pipe No No Yes
P2P Service SP 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 139 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

Ingress Service Point Attributes

The ingress attributes are attributes that operate upon frames when they ingress
via the service point.

Page 140 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

Page 141 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

5.3.5 Ethernet Interfaces

The IP-20C 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 protection
groups and link aggregation groups. Switching and QoS functionality are
implemented on the logical interface level.
It is important to understand that the IP-20C 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 112: Physical and Logical Interfaces

Note: For simplicity only, this figure represents a uni-directional
rather than a bi-directional traffic flow.

Page 142 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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.
When physical interfaces are grouped into a logical interface, IP-20C 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 113: Grouped Interfaces as a Single Logical Interface on Ingress Side

Note: For simplicity only, this figure represents a uni-directional
rather than a bi-directional traffic flow.
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 114: Grouped Interfaces as a Single Logical Interface on Egress Side

Note: For simplicity only, this figure represents a uni-directional
rather than a bi-directional traffic flow.

Page 143 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.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 Ethernet interface.

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 and SFP 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 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.14
• 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.

14
This functionality is planned for future release.

Page 144 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

• 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-20C 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 128-255 bytes, good or bad
• Frames with length 256-511 bytes, good or bad
• Frames with length 512-1023 bytes, good or bad.
• Frames with length 1024-1518 bytes, good or bad
• Frames with length 1519-1522 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)
• Control frames received

Page 145 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

• 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
• Frames with length 65-127 bytes, good or bad
• Frames with length 128-255 bytes, good or bad
• Frames with length 256-511 bytes, good or bad
• Frames with length 512-1023 bytes, good or bad
• Frames with length 1024-1518 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

5.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 link aggregation
group or a radio protection group, in which several physical interfaces correspond
to a single logical interface.

Page 146 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following figure illustrates the relationship of a LAG group to the switching
fabric. From the point of view of the user configuring the logical interface
attributes, the fact that there are two Ethernet interfaces is not relevant. The user
configures and manages the logical interface just as if it represented a single
Ethernet interface.

SP SP Logical Interface Physical Interface 3

Ethernet
Interface 1 Physical Interface 1

LAG LAG 1 SP SP Logical Interface Physical Interface 4

Service
Ethernet Physical Interface 2
Interface 2

Figure 115: 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.

Page 147 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

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
meter (policer) on the logical interface.
• 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
meter (policer) on the logical interface.
• Ethertype 1 Rate Meter Profile – Associates the rate meter (policer) with a
specific rate meter (policer) profile.
• 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 Rate Meter Admin – Enables or disables the Ethertype 2 rate
meter (policer) on the logical interface.
• Ethertype 2 Rate Meter Profile – Associates the rate meter (policer) with a
specific rate meter (policer) profile.
• Ethertype 2 Value – The Ethertype value to which the user wants to apply the
rate meter (policer). The field length is 4 nibbles (for example, 0x0806 - ARP).
• Ethertype 3 Rate Meter Admin – Enables or disables the Ethertype 3 rate
meter (policer) on the logical interface.
• Ethertype 3 Rate Meter Profile – Associates the rate meter (policer) with a
specific rate meter (policer) profile.
• Ethertype 3 Value – The Ethertype value to which the user wants to apply the
rate meter (policer). The field length is 4 nibbles (for example, 0x0806 - ARP).
• 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 148 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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.15
• 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 145, if the logical interface represents a
group, such as a LAG or a 1+1 HSB pair, the IP-20C 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.

15
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 149 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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-20C 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
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 interfaces, both on the same
IP-20C unit (line protection) and on separate units (line protection and equipment
protection). LAGs can also be used to provide redundancy for radio links.
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 3 Gbps
channel by grouping the three Ethernet interfaces to a single LAG.
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
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.

Page 150 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

5.3.6 Quality of Service (QoS)

Related topics:
• Ethernet Service Model
• 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-20C’s personalized QoS enables operators to handle a wide and diverse range
of scenarios. IP-20C’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-20C’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.”

Page 151 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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)
GE/Radio Port Classifier
(Policing) Queue Scheduler/
Manager Shaper
Port GE/Radio
(Optional)
Standard QoS/ H-QoS

Egress
Ingress CET/Pipe Marker
Rate Limit Services (Optional)
GE/Radio Port Classifier
(Policing) Queue Scheduler/
Manager Shaper
Port GE/Radio
(Optional)
Standard QoS/ H-QoS

Figure 116: 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.
• 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 2K queues. In H-QoS mode, IP-20C 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 152 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 117: Standard QoS and H-QoS Comparison

5.3.6.1 QoS on the Ingress Path

Classification
IP-20C 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 153 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

Port Logical Interface

SAP 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 118: 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-20C 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.
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.

Page 154 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 119: 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 147.
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 17: 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
7 0 7 Green
7 1 7 Yellow

Page 155 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Table 18: 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 19: 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

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

Page 156 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

DSCP DSCP (bin) Description CoS (Configurable) Color (Configurable)

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.

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

Page 157 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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
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-20C’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-20C 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 meter16
• Service point CoS-level rate meter17
MEF 10.2 is the de-facto standard for SLA definitions, and IP-20C’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.

16
Service point-level rate metering is planned for future release.
17
Service point and CoS-level rate metering is planned for future release.

Page 158 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

IP-20C provides up to 1024 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:
◦ 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 120: 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 8192kbytes, 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.

Page 159 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

• 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 8192kbytes, with a minimum granularity of 2 Kbytes.
• 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 146.
• 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
• User defined Ethertype 2 rate meter
• User defined Ethertype 3 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 160 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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:
• Green Frames (64 bits)
• Green Bytes (64 bits)
• Yellow Frames (64 bits)
• Yellow Bytes (64 bits)
• Red Frames (64 bits)
• Red Bytes (64 bits)

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:
• Green Frames (64 bits)
• Green Bytes (64 bits)
• Yellow Frames (64 bits)
• Yellow Bytes (64 bits)
• Red Frames (64 bits)
• Red Bytes (64 bits)

5.3.6.2 QoS on the Egress Path

Queue Manager
The queue manager (QM) is responsible for managing the output transmission
queues. IP-20C 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 Gigabits.
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.
The 2K 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.

Page 161 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following figure depicts the queue manager. Physically, the queue manager is
located between the ingress path and the egress path.

Figure 121: IP-20C 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.

Page 162 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The 2K queues share a single memory of 2 Gbits. IP-20C enables users to define a
specific size for each queue which is different from the default size. Moreover,
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 163.

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 122: 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 163 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 123: 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-20C 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-20C 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-20C 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 164 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 124: 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-20C 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
granularity of 8 Kbytes.
• Green Maximum Threshold – Permitted values are 0 Kbytes to 8 Mbytes, with
granularity of 8 Kbytes.
• 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 granularity of 8 Kbytes.
• 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 165 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 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 166 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 5 physical interfaces
• One service bundle per interface in standard QoS / 32 service bundles per
interface 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.
Traffic counters are valid on this level.

Page 167 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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 125: 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 168 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Shaping on the Egress Path

Egress shaping determines the traffic profile for each queue. IP-20C 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 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.
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
Note: 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.
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 169 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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
• 8,192,000 – 32,768,000 bps – granularity of 128,000 bps
• 32,768,000 – 131,072,000 bps – granularity of 512,000 bps
• 131,072,000 – 999,424,000 bps – granularity of 8,192,000 bps
Note: 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 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 159.

Egress Scheduling
Egress scheduling is responsible for transmission from the priority queues. IP-20C
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.

Page 170 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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.

Figure 126: 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.

Page 171 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following table provides a sample of an interface priority profile. This profile is
also used as the default interface priority profile.

Table 21: QoS Priority Profile Example

Profile ID (1-9)
CoS Green Priority Yellow Priority Description
(user defined) (read only)

0 1 1 Best Effort
1 2 1 Data Service 4
2 2 1 Data Service 3
3 2 1 Data Service 2
4 2 1 Data Service 1
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.
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.
• CoS 1 Priority – CoS 1 queue priority, from 4 (highest) to 1 (lowest).
• CoS 1 Description – CoS 1 user description field, up to 20 characters.
• CoS 2 Priority – CoS 2 queue priority, from 4 (highest) to 1 (lowest).
• CoS 2 Description – CoS 2 user description field, up to 20 characters.
• CoS 3 Priority – CoS 3 queue priority, from 4 (highest) to 1 (lowest).
• CoS 3 Description – CoS 3 user description field, up to 20 characters.
• CoS 4 Priority – CoS 4 queue priority, from 4 (highest) to 1 (lowest).
• CoS 4 Description – CoS 4 user description field, up to 20 characters.
• CoS 5 Priority – CoS 5 queue priority, from 4 (highest) to 1 (lowest).
• CoS 5 Description – CoS 5 user description field, up to 20 characters.
• CoS 6 Priority – CoS 6 queue priority, from 4 (highest) to 1 (lowest).
• CoS 6 Description – CoS 6 user description field, up to 20 characters.

Page 172 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

• CoS 7 Priority – CoS 7 queue priority, from 4 (highest) to 1 (lowest).

• CoS 7 Description – CoS 7 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.
The following table provides an example of a WFQ profile.

Table 22: 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.

Page 173 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Egress PMs and Statistics

Queue-Level Statistics
IP-20C 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)

Service Bundle-Level Statistics

IP-20C 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)

Page 174 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

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 23: 802.1q UP Marking Table (C-VLAN)

CoS Color 802.1q UP (Configurable) CFI Color (Configurable)

0 Green 0 0
0 Yellow 0 1

Page 175 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

CoS Color 802.1q UP (Configurable) CFI Color (Configurable)

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

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

Page 176 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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.

Standard QoS and Hierarchical QoS (H-QoS) Summary

The following table summarizes and compares the capabilities of standard QoS
and H-QoS.

Table 25: 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 32
1)
WRED Per queue (two curves – for Per queue (two curves – for green
green traffic and for yellow traffic traffic and for yellow traffic via the
via the queue) 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 Single leaky bucket
not 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). All
priority service bundles for a specific port
inherit the 8-queues priority
settings.
Weighted fair Queue (WFQ) Queue level (between queues) Queue level (between queues)
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 177 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.3.7 Global Switch Configuration

The following parameters are configured globally for the IP-20C switch:
• S- VLAN Ethertype –Defines the ethertype recognized by the system as the S-
VLAN ethertype. IP-20C 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-20C 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.

5.3.8 Automatic State Propagation and Link Loss Forwarding

Related topics:
• Network Resiliency
• Unit (External) Protection
• Link Aggregation Groups (LAG)
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.

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

Page 178 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

5.3.8.2 Automatic State Propagation and Protection

When the Controlled Interface is part of a 1+1 HSB protection configuration, a
port shutdown message is only sent to the remote side of the link if both of the
protected interfaces are shut down.
In a 1+1 HSB configuration using Multi-Unit LAG mode, in which two Ethernet
interfaces on each unit belong to a static LAG, an ASP triggering event only shuts
down the external user port.
When the Monitored interface is part of a 1+1 HSB configuration, ASP is only
triggered if both interfaces fail.
Closing an Ethernet port because of ASP does not trigger a protection switch.

Page 179 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.3.8.3 Preventing Loss of In-Band Management

If the link uses in-band management, shutting down the Ethernet port can cause
loss of management access to the unit. To prevent this, users can configure ASP to
operate in ASP Management Safe mode. In ASP Management Safe mode, the ASP
mechanism does not physically shut down the Controlled Interface when ASP is
triggered. Instead, the ASP mechanism sends a failure indication message. This
message is used to propagate the failure indication to external equipment.
ASP Management Safe mode is particularly useful when the IP-20C unit is an
element in the following network topologies:
• Ring or mesh network topology.
• An IP-20N connected to an IP-20C unit being utilized as a pipe via an Ethernet
interface (back-to-back on the same site).18
• Payload traffic is spanned by G.8032 in the network.
• In-band management is spanned by MSTP in the network.
• An IP-20C unit being utilized as a pipe is running one MSTP instance for
spanning in-band management.19

18
ASP interoperability among IP-20 units requires that all units be running software version 7.7
or higher.
19
G.8032 and MSTP are planned for future release.

Page 180 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.3.9 Adaptive Bandwidth Notification (EOAM)

Adaptive Bandwidth Notification (ABN, also known as EOAM) enables third party
applications to learn about bandwidth changes in a radio link when ACM is active.
Once ABN is enabled, the radio unit reports bandwidth information to third-party
switches.
Radio
Third Party Ethernet Ethernet Third Party
Equipment Equipment
IP-20C IP-20C

Ethernet Ethernet

IP-20C IP-20C

Radio Radio

IP-20C IP-20C

Ethernet Ethernet

Radio

Third Party Ethernet Ethernet Third Party

Equipment Equipment
IP-20C IP-20C

Figure 127: Network Topology with IP-20C Units and Third-Party Equipment
The ABN entity creates a logical relationship between a radio interface or a logical
group of radio interfaces, called the Monitored Interface, and an Ethernet
interface or a logical group of Ethernet interfaces, called the Control Interface.
When bandwidth degrades from the nominal bandwidth value in the Monitored
Interface, messages relaying the actual bandwidth values are periodically sent
over the Control Interface. A termination message is sent once the bandwidth
returns to its nominal level.

Control Monitored
Interface Interface

Third Party Third Party

Equipment Ethernet Equipment
IP-20C Radio IP-20C Ethernet
LAG Multi-Carrier ABC
Radio Protection Group

Figure 128: ABN Entity

The nominal bandwidth is calculated by the system based on the maximum
bandwidth profile. If the Monitored Interface is a Multi-Carrier ABC group, the
nominal bandwidth is based on the sum of the group members. If the Monitored
Interface is a protection group, the nominal bandwidth relates to the active
interface.

Page 181 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The ABN entity measures the bandwidth in samples once a change in profile takes
place. A weighted average is calculated based on the samples at regular, user-
defined intervals to determine whether a bandwidth degradation event has
occurred. Bandwidth degradation is reported only if the measured bandwidth
remains below the nominal bandwidth at the end of a user-defined holdoff
period. This prevents the IP-20C from reporting bandwidth degradation due to
short fading events.

5.3.10 Network Resiliency

IP-20C 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.
Note: G.8032 and MSTP are planned for future release.

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

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

Page 182 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

Page 183 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

RPL
IP-20C
(Blocked)
Ring Node 1

Wireless Ring IP-20C

Ring Node 4
(RPL Owner)

IP-20C
Ring Node 2

IP-20C

Ring Node 3
R-APS Messages

Traffic

Figure 129: 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.

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

Wireless Ring IP-20C

Ring Node 4
(RPL Owner)

IP-20C
Ring Node 2

IP-20C

Ring Node 3
R-APS Messages

Traffic

Figure 130: 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.

Page 184 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

IP-20C
RPL for
ERPI 1
Ring Node 1
RPL for
ERPI 2
Wireless Ring IP-20C

Ring Node 4
RPL for
RPL for
ERPI 4
ERPI 3
IP-20C
Ring Node 2

IP-20C

Ring Node 3
ERPI 1 Traffic

ERPI 2 Traffic

ERPI 3 Traffic

ERPI 4 Traffic

Figure 131: Load Balancing Example in G.8032 Ring

5.3.10.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.
MSTP is an extension of, and is backwards compatible with, Rapid Spanning Tree
Protocol (RSTP).
IP-20C 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.

Page 185 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

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.

Page 186 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

MSTP Interoperability
MSTP in IP-20C units is interoperable with:
• FibeAir IP-10 units running RSTP.
• Third-party bridges running MSTP.
• Third-party bridges running RSTP

5.3.11 OAM
FibeAir IP-20C 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.
IP-20C is fully compliant with G.8013/Y.1731, MEF-17, MEF-20, MEF-30, and
MEF-31.

Page 187 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Carrier Ethernet services (EVCs)

BNC/RNC

Fiber
Aggregation
Network

IP-20C
IP-20C IP-20C

Tail site Aggregation site Fiber site

Figure 132: IP-20C End-to-End Service Management

5.3.11.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-20C 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.

Figure 133 SOAM Maintenance Entities (Example)

• Protocols and procedures used by maintenance points to maintain and
diagnose connectivity faults within a maintenance domain.

Page 188 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

5.3.11.2 Ethernet Line Interface Loopback

FibeAir IP-20C supports loopback testing for its radio interfaces. 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.

Page 189 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Loopback on
Radio Link

IP-20C IP-20C

Loopback from Test

Equipment to IP-20C
Ethernet Interface

Test
Equipment

Figure 134: Ethernet Line Interface Loopback – Application Examples

Ethernet loopbacks can be performed on any logical interface. This includes GbE
interfaces, radio interfaces, and LAGS. Ethernet loopbacks cannot be performed
on the management interface.
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.20
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.

20
G.8032 and MSTP are planned for future release.

Page 190 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.3.11.3 SFP DDM and Inventory Monitoring

FibeAir IP-20C supports static and dynamic monitoring for all SFP modules used in
Ethernet and MIMO ports. Dynamic monitoring PMs are also available.
DDM (Digital Diagnostic Monitoring) enables users to display dynamic information
about the SFP state, including:
• RX Power (in dBm)
• TX Power (in dBm)
• Bias current (mA)
• Temperature (both Celsius and Fahrenheit)
Inventory monitoring enables users to display the following information about
each SFP module installed in the IP-20 unit:
• Connector Type
• Transceiver Type (e.g., 10G BASE-LR)
• Vendor Name
• Vendor Part Number
• Vendor Serial Number
• Vendor Revision
• Wavelength
• Maximum length of link per fiber optic cable type
DDM PMs can be displayed for 15-minute and 24-hour intervals. For each interval,
the following PMs are displayed:
• Minimum RX power during the interval (dBm)
• Average RX power during the interval (dBm)
• Maximum RX power during the interval (dBm)
• Minimum TX power during the interval (dBm)
• Average TX power during the interval (dBm)
• Maximum TX power during the interval (dBm)
Note: DDM parameters are not relevant for electrical SFPs.
Thresholds for these alarms are programmed into the SFP modules by the
manufacturer.

Page 191 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.4 Synchronization
This section describes IP-20C’s flexible synchronization solution that enables
operators to configure a combination of synchronization techniques, based on the
operator’s network and migration strategy, including:
• PTP optimized transport, supporting IEEE 1588 and NTP, with guaranteed
ultra-low PDV and support for ACM and narrow channels.
• Native Sync Distribution, for end-to-end distribution using GbE.
• SyncE PRC Pipe Regenerator mode, providing PRC grade (G.811) performance
for pipe (“regenerator”) applications.

This section includes:

• IP-20C Synchronization Solution
• Available Synchronization Interfaces
• Synchronous Ethernet (SyncE)
• IEEE-1588v2 PTP Optimized Transport
• SSM Support and Loop Prevention

Related topics:
• NTP Support

5.4.1 IP-20C 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
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 mode
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

21
Boundary Clock is planned for future release.

Page 192 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.4.2 Available Synchronization Interfaces

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 26: Synchronization Interface Options

Available interfaces as frequency Available interfaces as frequency
input (reference sync source) output

• Radio carrier • Radio carrier

• GbE Ethernet interfaces • GbE Ethernet interfaces
It is possible to configure up to eight 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

5.4.3 Synchronous Ethernet (SyncE)

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.

5.4.3.1 SyncE PRC Pipe Regenerator Mode

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
In PRC pipe regenerator mode, frequency is taken from the incoming GbE
Ethernet 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.

Page 193 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.4.4 IEEE-1588v2 PTP Optimized Transport

Precision Timing Protocol (PTP) refers to the distribution of frequency and phase
information across a packet-switched network.
IP-20C supports 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 135: 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 194 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Sync GPS/
SSU
Input

Packet Switched Network

Master Slave

t1

Syn c
(t1)

Follow
-up (t1 t2
)

t3
3)
req uest (t
Delay_
t4

Delay
_resp
o n se
(t4)

Figure 136: 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:
Offset = [(t2 – t1) – (t4 – t3)]/2
Propagation Delay = [(t2 – t1) + (t4 – t3)]/2

Page 195 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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-20C’s IEEE-1588v2 implementations
mitigate these factors, see Mitigating PDV on page 196.

5.4.4.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 196).
• Minimal consumption of bandwidth and processing power.
• Simple configuration.

5.4.4.2 Mitigating PDV

To get the most out of PTP and minimize PDV, IP-20C supports Transparent Clock
and Boundary Clock22.
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.

22
Boundary Clock is planned for future release.

Page 196 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

• 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-20C’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-20C’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 197 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.4.4.3 Transparent Clock

IP-20C 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 (Update

Time Timestamp)
Sync GPS/SSU
Input

Transparent
Clock

Master Slave

Leaving Time (Update Entrance

Timestamp) Time

Figure 137: Transparent Clock – General Architecture

IP-20C 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-20C 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 following figure, IP-20C 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 198 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Radio Link
Delay = ∆y

Correction Time
∆x + ∆y + ∆z
1588 1588
Master Slave

Packet Processing Packet Processing

Delay = ∆z Delay = ∆x

Figure 138: Transparent Clock Delay Compensation

5.4.4.4 Boundary Clock

Note: Boundary Clock is planned for future release.
IEEE-1588v2 Boundary Clock enables the IP-20C to regenerate phase
synchronization via standard Ethernet. Boundary Clock complies with ITU-T
Telecom Profile G.8275.1. This enables IP-20C, with Boundary Clock, to meet the
rigorous synchronization requirements of LTE-Advanced (LTE-A) networks.
In Boundary Clock, a single node can include up to four ports; master ports for
time stamp distribution and one slave port that is locked onto a grandmaster.
The Boundary Clock node terminates the PTP flow on the slave port, recovers the
clock and timestamp, 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 199 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

1588
Master
Slave 1588
IP-20C IP-20C Port Slave

Slave Master Master

Port Port Port

Figure 139: 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.

Table 27: Boundary Clock Input Options

Synchronization Input Frequency/Phase

Ethernet packets from PTP 1588 Remote Master via Phase

radio or Ethernet interface
SyncE (including ESMC) via radio or Ethernet Frequency
interface

Table 28: Boundary Clock Output Options

Synchronization Input Frequency/Phase

Ethernet packets towards PTP 1588 slaves via radio Phase

or Ethernet interface
SyncE (including ESMC) via radio or Ethernet Frequency
interface

IP-20C uses multicast Ethernet messages, per IEEE-1588 Annex F.

Page 200 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.4.5 SSM Support and Loop Prevention

In order to provide topological resiliency for synchronization transfer, IP-20C
implements the passing of SSM messages over the radio interfaces. SSM timing in
IP-20C 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 201 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

5.5 Radio Payload Encryption and FIPS

5.5.1 AES-256 Payload Encryption
IP-20C 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.
Encryption Module in IP-20C Unit

AES-256 Encrypted Link

IP-20C IP-20C

Figure 140 AES-256 Encrypted Link

Notes: 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.
AES encryption is not supported with MIMO or Space Diversity
links.

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

5.5.1.2 IP-20C AES Implementation

In IP-20C, AES provides full payload encryption for all L1 radio traffic. AES
encryption operates on a point-to-point radio link level. 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-20C 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.

Page 202 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

• 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.
AES key generation is completely hitless, and has no effect on ACM operation.
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.

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

5.5.2 FIPS 140-2 Compliance

FibeAir IP-20C 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 10.7 does not support the FibeAir IP-20 Assured
platform. The latest release to support FibeAir IP-20 Assured,
including FIPS, is CeraOS 8.3. CeraOS 10.7 does support AES-
256 Radio Payload Encryption.

5.5.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 customer to ensure that the above FIPS requirements
are met.

5.5.2.2 Hardware Requirements

For an IP-20C node to be FIPS-compliant, the unit must be FIPS-compliant
hardware. A FIPS-compliant IP-20C unit has a unique part number ending in the
letters AF, in the following format: IP-20C-***-AF

Page 203 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Special labels must be affixed to a FIPS-compliant IP-20C unit. These labels are
tamper-evident and must be applied in such a way that it is not possible to open
or tamper with the unit. Replacement labels can be ordered from Ceragon
Networks, part number BS-0341-0. Tamper-evident labels should be inspected for
integrity at least once every six months. For further details, refer to the FibeAir IP-
20C Installation Guide.

5.5.2.3 Software Requirements

FIPS compliance requires the user to operate the IP-20C 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 204 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

6. FibeAir IP-20C Management

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

Page 205 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

6.1 Management Overview

The Ceragon management solution is built on several layers of management:
• NEL – Network Element-level CLI
• EMS – HTTP web-based EMS
• NMS and SML –Ceragon NMS 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.
In addition, Ceragon provides an SNMP v1/v2c/v3 northbound interface on the IP-
20C.
Ceragon offers an NMS solution for providing centralized operation and
maintenance capability for the complete range of network elements in an IP-20C
system.
In addition, management, configuration, and maintenance tasks can be
performed directly via the IP-20C Command Line Interface (CLI). The CLI can be
used to perform configuration operations for IP-20C units, as well as to configure
several IP-20C units in a single batch command.

Page 206 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Northbound OSS/NMS
SNMP
NetAct
CLI Interface

NMS
Client NMS
TCP, Secured
SSL Channel Platform
REST
Over
HTTP
Web EMS SNMP
HTTP/HTTPS
FTP/SFTP
HTTP/HTTPS
FTP/SFTP

CLI

HTTP

Craft IP-20C
Figure 141: Integrated IP-20C Management Tools

6.2 Automatic Network Topology Discovery with LLDP Protocol

FibeAir IP-20C 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-20C’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 207 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

6.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 29: Dedicated Management Ports

Port number Protocol Frame Details
structure

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 FTP Control TCP Downloads software and configuration files,
(default) to any Port uploads security and configuration logs, and unit
remote port info files.
(>1023). (FTP Server responds to client's control port)
Initial port (21) is (optional)
configurable.
From Any port FTP Data Port TCP Downloads software and configuration files,
(>1023) to any uploads security and configuration logs, and unit
remote port info files.
(>1023) The FTP server sends ACKs (and data) to client's
data port.
From port 22 SFTP Control TCP Downloads software and configuration files, and
(default) to any Port CSR certificates, uploads security and
remote port configuration logs, and unit info files.
(>1023). (SFTP Server responds to client's control port)
Initial port (22) is (optional)
configurable.
From Any port SFTP Data TCP Downloads software and configuration files, and
(>1023) to any Port CSR certificates, uploads security and
remote port configuration logs, and unit info files.
(>1023) 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)

Page 208 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

All remote system management is carried out through standard IP

communications. Each NE behaves as a host with a single IP address.
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

6.4 Web-Based Element Management System (Web EMS)

The CeraWeb 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-20C 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, and software updates.
• Security Configuration – Enables you to configure IP-20C security features.
• User Management – Enables you to define users and user profiles.
A Web-Based EMS connection to the IP-20C 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 on the unit. 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
• 2+0 Multi-Carrier ABC group

Page 209 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

6.5 Command Line Interface (CLI)

A CLI connection to the IP-20C can be opened via telnet. All parameter
configurations can be performed via CLI.
Note: Telnet access can be blocked by user configuration.

6.6 Configuration Management

The system configuration file consists of a set of all the configurable system
parameters and their current values.
IP-20C configuration files can be imported and exported. This enables you to copy
the system configuration to multiple IP-20C 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.23
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.

23
The option to edit the backup configuration is planned for future release.

Page 210 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

6.7 Software Management

The IP-20C 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-20C.
• Reset – The IP-20C is restarted in order to boot the new software and
firmware versions.
IP-20C software and firmware releases are provided in a single bundle that
includes software and firmware for all components supported by the system.
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-20C 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-20C 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-20C 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. The
system performs an automatic reset after the installation.

6.7.1 Backup Software Version

Note: Backup software version support is planned for future release.
IP-20C 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 211 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

6.8 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:
• Activation Key (or Demo mode) configuration
• Radio Parameters
• Interface Groups (LAG, Multi-Carrier ABC, XPIC, MIMO)
• 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.

6.9 IPv6 Support

FibeAir IP-20C 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)

6.10 In-Band Management

FibeAir IP-20C 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 132.

Page 212 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

6.11 Local Management

IP-20C includes an FE port for local management. This port (MGT) is enabled by
default, and cannot be disabled.

6.12 Alarms
6.12.1 Configurable BER Threshold for 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.

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

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

6.12.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 213 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

6.13 NTP Support

Related topics:
• Synchronization
IP-20C 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-20C supports NTPv3 and NTPv4. NTPv4 provides interoperability with NTPv3
and with SNTP.

6.14 UTC Support

IP-20C 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-20C 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.

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

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

Page 214 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 142: Security Solution Architecture Concept

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

Page 215 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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

6.15.3 Defenses in User and System Authentication Procedures

6.15.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-20C 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
• 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.

Page 216 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

6.15.3.2 User Identification

IP-20C 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.
• 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.

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

6.15.3.4 RADIUS Support

The RADIUS protocol provides centralized user management services. IP-20C
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-20C 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.

Page 217 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

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-20C, or notifies
the IP-20C 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-20C will attempt to authenticate the
user locally, according to the existing list of defined users.
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-20C - 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

6.15.4 Secure Communication Channels

IP-20C supports a variety of standard encryption protocols and algorithms, as
described in the following sections.

6.15.4.1 SSH (Secured Shell)

SSH protocol can be used as a secured alternative to Telnet. In IP-20C:
• 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-20C’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 218 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

6.15.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-20C 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.
For a list of supported HTTPS ciphers, including an indication of which ciphers are
supported in HTTPS strong mode, see Annex B – Supported Ciphers for Secured
Communication Protocols in the Release Notes for the CeraOS version you are
using.

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

6.15.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 219 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

6.15.4.5 SNMP
IP-20C 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 network elements.
IP-20C supports the following MIBs:
• RFC-1213 (MIB II)
• RMON MIB
• Ceragon (proprietary) MIB.
Access to all network elements in a node is provided by making use of the
community and context fields in SNMPv1 and SNMPv2c/SNMPv3, respectively.

For additional information:

• FibeAir IP-20C MIB Reference, DOC- 00036524.

6.15.4.6 Server Authentication (SSLv3/TLS (1.0, 1.1, 1.1))

• 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
(network element) 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.

6.15.4.7 Encryption
Note: Support for encryption is planned for future release.
• Encryption algorithms for secure management protocols include:
◦ Symmetric key algorithms: 128-bit AES
◦ Asymmetric key algorithms: 1024-bit RSA

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

Page 220 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

• 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
◦ 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

Page 221 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

• 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

Page 222 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

7. Standards and Certifications

This chapter includes:
• Supported Ethernet Standards
• MEF Certifications for Ethernet Services

7.1 Supported Ethernet Standards

Table 30: 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 223 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

7.2 MEF Certifications for Ethernet Services

Table 31: 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 32: 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 224 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8. Specifications
This chapter includes:
• General Radio Specifications
• Frequency Accuracy
• Radio Scripts
• Radio Capacity Specifications
• Transmit Power Specifications
• Receiver Threshold Specifications
• Frequency Bands
• Mediation Device Losses
• Ethernet Latency Specifications
• Interface Specifications
• Carrier Ethernet Functionality
• Synchronization Functionality
• Network Management, Diagnostics, Status, and Alarms
• Mechanical Specifications
• Standards Compliance
• Environmental Specifications
• Antenna Specifications
• Power Input Specifications
• Power Consumption Specifications
• Power Connection Options
• PoE Injector Specifications
• Cable Specifications

Related Topics:
• Standards and Certifications
Note: All specifications are subject to change without prior
notification.

Page 225 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.1 General Radio Specifications

Table 33: Radio Frequencies
Frequency (GHz) Operating Tx/Rx Spacing (MHz)
Frequency Range
(GHz)
U5.7 5.725-5.875 65, 75
6L,6H 5.85-6.45, 6.4-7.1 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.32, 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
38 37-40 1000, 1260, 700
42 40.55-43.45 1500

Table 34: General Radio Specifications

Standards ETSI, ITU-R, CEPT

Frequency Source Synthesizer

System Configurations MultiCore 2+0 Single/Dual Polarization, MultiCore 2+2 SP/DP

HSB, 2 x MultiCore 2+0 SP/DP
LoS 4x4 MIMO, LoS 2x2 MIMO

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 frequency and the ACM profile. The
maximum TX power with ATPC is no higher than the maximum
manually configured TX power.

Page 226 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.2 Frequency Accuracy

IP-20C provides frequency accuracy of ±4 ppm24.

8.3 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

The following table lists supported system MRMC (Multi-Rate-Multi-Constellation)

configurations (determined by modem configuration scripts).
Although in some cases it may be possible to configure higher profiles, the
maximum supported profiles are those listed in the table below.
Note: 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.

Table 35: Radio Scripts

Script Channel Occupied System XPIC MIMO Highest Spectral Max Profile Max Profile
ID BW BW Class (CCDP) ASD Efficiency Class (ACM) (Fixed)
AFR

1523 3.5 3.267 ACCP No No 6L 5 (256 4 (128

QAM) QAM)
1508 7 6.5 ACCP Yes No 7B 9 8
1509 14 13.3 ACCP Yes No 7B 9 8
1504 28 26.5 ACCP Yes No 8B 10 9
1505 28 28 ACAP Yes No 8A 10 9
1801 28 26.91 ACCP No AFR 7B 10 9
1901 28 26 ACCP Yes25 MIMO 7B 926 826
1534 28 26 ACCP Yes No No 8B 10

24
Over temperature.
25
Only with 4x4 MIMO.
26
When used in Space Diversity configurations, the maximum profile is 10 (2048 QAM) for
ACM mode and 9 (1024 QAM) for Fixed mode. When used in MIMO configurations with 13,
15, and 18 GHz frequencies, the maximum profile is 10 (2048 QAM) for ACM mode and 9
(1024 QAM) for Fixed mode. For other frequencies, the maximum profile is 9 (1024 QAM) for
ACM mode and 7 (516 QAM) for Fixed mode. Profile 10 (2048 QAM) is guaranteed only
when working with optimal antenna distance.

Page 227 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Script Channel Occupied System XPIC MIMO Highest Spectral Max Profile Max Profile
ID BW BW Class (CCDP) ASD Efficiency Class (ACM) (Fixed)
AFR

1951 28 26 ACCP Yes ASD 7B 9 8

1507 40 37.4 ACCP Yes No 8B 10 9
152727 40 35.7 ACCP Yes No 8B 10 9
1902 40 37.6 ACCP Yes25 MIMO 7B 928 828
1537 40 33.5 ACCP Yes No No 8B 10
1502 56 53 ACCP Yes No 8B 10 9
1503 56 53 ACCP No No 8B 10 9
1506 56 55.7 ACAP Yes No 8A 10 9
1903 56 53 ACCP Yes25 MIMO 7B 928 828
1953 56 53 ACCP Yes ASD 7B 9 8
1501 80 74 ACCP Yes No 6B 8 7

Important note: MRMC radio scripts for MIMO can only be used in MIMO and
Space Diversity links. These scripts can be used in the following
configurations: 2x2 MIMO, 4x4 MIMO, 1+0 SD, and 2+2 SD.

27
Script 1527 is specially designed to meet Japanese specifications.
28
When used in Space Diversity configurations, the maximum profile is 10 (2048 QAM) for
ACM mode and 9 (1024 QAM) for Fixed mode.

Page 228 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.4 Radio Capacity Specifications

Each table in this section includes ranges of capacity specifications per carrier
according to frame size, with ranges given for no Header De-Duplication, Layer-2
Header De-Duplication, and LTE-optimized Header De-Duplication (per core).
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 227.
Notes: Ethernet capacity depends on average frame size.
The capacity figures for LTE packets encapsulated inside GTP
tunnels with IPv4/UDP encapsulation and double VLAN tagging
(QinQ). Capacity for IPv6 encapsulation is higher.
ACAP and ACCP represent compliance with different ETSI mask
requirements. ACCP represents compliance with more
stringent interference requirements.

8.4.1 3.5 MHz – Script ID 1523

Table 36: Radio Capacity for 3.5 MHz – Script ID 1523
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation key Compression Compression De-Duplication

0 QPSK 10 3-4 3-5 4-13

1 16 QAM 10 8-10 8-12 9-32
2 32 QAM 10 11-14 11-17 12-43
3 64 QAM 50 14-17 14-21 15-54
4 128 QAM 50 17-21 17-25 18-65
5 256 QAM 50 19-24 20-29 20-74

Page 229 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.4.2 7 MHz – Script ID 1508

Table 37: Radio Capacity for 7 MHz – Script ID 1508
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation key Compression Compression De-Duplication

0 QPSK 10 8-10 9-13 9-32

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

8.4.3 14MHz – Script ID 1509

Table 38: Radio Capacity for 14MHz – Script ID 1509
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation key Compression Compression De-Duplication

0 QPSK 50 19-24 20-29 20-74

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

Page 230 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.4.4 28 MHz – Script ID 1504

Table 39: Radio Capacity for 28 MHz – Script ID 1504
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation key Compression Compression De-Duplication

0 QPSK 50 40-49 41-59 42-153

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

8.4.5 28 MHz – Script ID 1505

Table 40: Radio Capacity for 28 MHz – Script ID 1505
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation key Compression Compression De-Duplication

0 QPSK 50 43-52 43-63 45-162

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

Page 231 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.4.6 28 MHz – Script IDs 1901 and 1951

Table 41: Radio Capacity for 28 MHz – Script IDs 1901 and 1953
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation key Compression Compression De-Duplication

0 QPSK 50 38-47 38-56 40-145

1 8 PSK 50 57-70 58-85 60-218
2 16 QAM 100 79-96 79-116 83-299
3 32 QAM 100 106-129 107-156 111-403
4 64 QAM 150 129-158 130-191 135-491
5 128 QAM 150 158-193 159-233 166-600
6 256 QAM 200 180-220 182-266 189-686
7 512 QAM 200 187-229 189-277 197-714
8 1024 QAM (Strong FEC) 200 206-251 207-304 216-783
9 1024 QAM (Light FEC) 225 225-275 226-332 236-855
10 2048 QAM 250 242-296 244-358 254-921

8.4.7 28 MHz – Script ID 1534

Table 42: Radio Capacity for 28 MHz – Script ID 1534
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation key Compression Compression De-Duplication

0 QPSK 50 39-48 39-58 41-148

1 8 PSK 50 58-71 59-86 61-222
2 16 QAM 100 80-97 80-118 84-303
3 32 QAM 100 105-128 106-155 110-399
4 64 QAM 150 129-158 130-191 136-491
5 128 QAM 150 156-190 157-230 163-592
6 256 QAM 200 177-217 179-262 186-674
7 512 QAM 200 196-239 197-289 205-744
8 1024 QAM (Strong FEC) 200 208-254 210-307 218-791
9 1024 QAM (Light FEC) 225 221-270 222-326 232-840
10 2048 QAM 225 237-289 239-350 249-901

Page 232 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.4.8 40 MHz – Script ID 1507

Table 43: Radio Capacity for 40 MHz – Script ID 1507
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation key Compression Compression De-Duplication

0 QPSK 50 58-71 58-85 61-220

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

8.4.9 40 MHz – Script ID 1527

Table 44: Radio Capacity for 40 MHz – Script ID 1527
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation key Compression Compression De-Duplication

0 QPSK 50 55-68 56-82 58-210

1 8 PSK 100 82-101 83-122 87-314
2 16 QAM 100 112-137 113-166 118-427
3 32 QAM 150 148-181 149-219 155-563
4 64 QAM 200 182-222 183-269 191-692
5 128 QAM 225 220-269 221-325 231-836
6 256 QAM 225 237-289 238-350 249-901
7 512 QAM 250 259-317 261-383 272-986
8 1024 QAM (Strong FEC) 300 294-359 296-434 308-1000
9 1024 QAM (Light FEC) 300 312-381 314-461 327-1000
10 2048 QAM 350 337-412 340-498 354-1000

Page 233 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.4.10 40 MHz – Script ID 1902

Table 45: Radio Capacity for 40 MHz – Script ID 1902
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation Compression Compression De-Duplication
key

0 QPSK 50 54-66 54-80 57-206

1 8 PSK 100 83-101 83-122 87-315
2 16 QAM 100 117-144 118-174 123-447
3 32 QAM 150 156-191 157-231 164-595
4 64 QAM 200 185-226 186-273 194-704
5 128 QAM 225 218-267 220-323 229-831
6 256 QAM 250 247-302 249-365 259-939
7 512 QAM 300 271-331 273-400 284-1000
8 1024 QAM (Strong FEC) 300 306-374 308-452 321-1000
9 1024 QAM (Light FEC) 300 318-388 320-469 334-1000
10 2048 QAM 350 344-421 347-509 362-1000

8.4.11 40 MHz – Script ID 1537

Table 46: Radio Capacity for 40 MHz – Script ID 1537
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation Compression Compression De-Duplication
key

0 QPSK 50 50-62 51-75 53-192

1 8 PSK 100 75-92 76-111 79-287
2 16 QAM 100 103-126 104-152 108-391
3 32 QAM 150 135-166 136-200 142-515
4 64 QAM 150 166-203 168-246 175-633
5 128 QAM 200 201-246 203-297 211-766
6 256 QAM 225 217-265 218-320 228-824
7 512 QAM 250 250-305 252-369 262-950
8 1024 QAM (Strong FEC) 300 272-332 274-402 286-1000
9 1024 QAM (Light FEC) 300 288-353 291-426 303-1000
10 2048 QAM 300 313-382 315-462 328-1000

Page 234 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.4.12 56 MHz – Script ID 1502

Table 47: Radio Capacity for 56 MHz – Script ID 1502
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation Compression Compression De-Duplication
key

0 QPSK 100 83-101 83-122 87-314

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

8.4.13 56 MHz – Script ID 1506

Table 48: Radio Capacity for 56 MHz – Script ID 1506
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation key Compression Compression De-Duplication

0 QPSK 100 87-106 88-128 91-331

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

Page 235 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.4.14 56 MHz – Script IDs 1903 and 1953

Table 49: Radio Capacity for 56 MHz – Script IDs 1903 and 1953
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation key Compression Compression De-Duplication

0 QPSK 100 77-94 78-114 81-293

1 8 PSK 100 121-148 122-179 128-462
2 16 QAM 150 169-206 170-249 177-642
3 32 QAM 225 223-273 225-330 234-849
4 64 QAM 250 262-321 265-388 276-999
5 128 QAM 300 313-382 315-462 328-1000
6 256 QAM 350 358-437 360-528 376-1000
7 512 QAM 400 400-489 403-591 420-1000
8 1024 QAM (Strong FEC) 450 425-519 428-628 446-1000
9 1024 QAM (Light FEC) 450 451-551 454-666 473-1000
10 2048 QAM 500 498-609 502-737 523-1000

8.4.15 80 MHz – Script ID 1501

Table 50: Radio Capacity for 80 MHz – Script ID 1501
Profile Modulation Minimum Ethernet throughput
required
capacity No L2 Header
activation key Compression Compression De-Duplication

0 QPSK 100 114-140 115-169 120-435

1 8 PSK 150 162-198 164-240 170-618
2 16 QAM 225 231-283 233-342 243-880
3 32 QAM 300 304-371 306-449 319-1000
4 64 QAM 400 371-454 374-549 390-1000
5 128 QAM 450 439-536 442-649 461-1000
6 256 QAM 500 505-618 509-747 531-1000
7 512 QAM 500 555-679 560-821 583-1000
8 1024 QAM 650 604-738 609-892 634-1000

Page 236 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.5 Transmit Power Specifications

Note: Nominal TX power is subject to change until the relevant frequency
band is formally released. See the frequency rollout plan.
The values listed in this section are typical. Actual values may
differ in either direction by up to 1dB.

Table 51: IP-20C Standard Power

Modulation 5.7 - 6 7 8 10-11 13-15 18 23 24 26 28, 32, 42
GHz GHz GHz GHz GHz GHz GHz GHz UL29 GHz 38 GHz GHz

QPSK 25 25 25 23 24 22 20 -17 21 18 15
8 PSK 25 25 25 23 24 22 20 -18 21 18 15
16 QAM 25 24 24 23 23 21 20 -19 20 17 14
32 QAM 24 23 23 22 22 20 20 -19 19 16 13
64 QAM 24 23 23 22 22 20 20 -19 19 16 13
128 QAM 24 23 23 22 22 20 20 -19 19 16 13
256 QAM 24 23 21 22 20 20 18 -19 17 14 11
512 QAM 22 21 21 21 20 18 18 -21 17 14 11
1024 QAM 22 21 21 20 20 18 17 -21 16 13 10
2048 QAM 20 19 19 18 18 16 16 -23 15 12 9

Table 52: IP-20C High Power

Modulation 5.7 - 6 GHz 7 GHz 8 GHz 10-11 GHz

QPSK 28 28 28 26
8 PSK 28 28 28 26
16 QAM 28 27 27 26
32 QAM 27 26 26 25
64 QAM 27 26 26 25
128 QAM 27 26 26 25
256 QAM 27 26 24 25
512 QAM 25 24 24 24
1024 QAM 25 24 24 23
2048 QAM 23 22 22 21

29
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 237 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.5.1 Pmin Power

Table 53: IP-20C Pmin Power
Frequency Band Pmin

6-15 GHz 2
18-24 GHz -1
24 GHz ETSI -39
26-42 GHz -1

Page 238 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.6 Receiver Threshold Specifications

Note: The values listed in this section are typical. Tolerance range is -1dB/+ 2dB.

Table 54: Receiver Threshold

Profile Modulation Channel Frequency (GHz)
Spacing 5.7- 6 7 8 10 11 13 15 18 23 2430 26 28-31 32 38 42

0 QPSK 3.5 MHz -96.5 -96.0 -96.0 -95.5 -96.5 -95.5 -94.5 -96.0 -95.0 -94.5 -94.5 -94.5 -94.0 -94.0 -93.5
1 16 QAM -90.0 -89.0 -89.0 -89.0 -89.5 -88.5 -88.0 -89.0 -88.0 -87.5 -88.0 -87.5 -87.5 -87.0 -86.5
2 32 QAM -86.5 -85.5 -85.5 -85.5 -86.0 -85.0 -84.5 -85.5 -84.5 -84.0 -84.5 -84.0 -84.0 -83.5 -83.0
3 64 QAM -83.0 -82.5 -82.5 -82.0 -83.0 -82.0 -81.0 -82.5 -81.5 -81.0 -81.0 -81.0 -80.5 -80.5 -80.0
4 128 QAM -79.5 -79.0 -79.0 -78.5 -79.5 -78.5 -77.5 -79.0 -78.0 -77.5 -77.5 -77.5 -77.0 -77.0 -76.5
5 256 QAM -76.5 -75.5 -75.5 -75.5 -76.5 -75.0 -74.5 -75.5 -75.0 -74.5 -74.5 -74.0 -74.0 -73.5 -73.0

30
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 239 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Profile Modulation Channel Frequency (GHz)

Spacing 5.7- 6 7 8 10 11 13 15 18 23 2430 26 28-31 32 38 42

0 QPSK 7 MHz -93.5 -93.0 -93.0 -92.5 -93.5 -92.5 -91.5 -93.0 -92.0 -91.5 -91.5 -91.5 -91.0 -91.0 -90.5
1 8 PSK -87.5 -87.0 -87.0 -86.5 -87.5 -86.5 -85.5 -87.0 -86.0 -85.5 -85.5 -85.5 -85.0 -85.0 -84.5
2 16 QAM -87.0 -86.5 -86.5 -86.0 -87.0 -86.0 -85.0 -86.5 -85.5 -85.0 -85.0 -85.0 -84.5 -84.5 -84.0
3 32 QAM -83.5 -83.0 -83.0 -82.5 -83.5 -82.5 -81.5 -83.0 -82.0 -81.5 -81.5 -81.5 -81.0 -81.0 -80.5
4 64 QAM -80.5 -80.0 -80.0 -79.5 -80.5 -79.5 -78.5 -80.0 -79.0 -78.5 -78.5 -78.5 -78.0 -78.0 -77.5
5 128 QAM -77.5 -76.5 -76.5 -76.5 -77.5 -76.0 -75.5 -76.5 -76.0 -75.5 -75.5 -75.0 -75.0 -74.5 -74.0
6 256 QAM -74.0 -73.5 -73.5 -73.0 -74.0 -73.0 -72.0 -73.5 -72.5 -72.0 -72.0 -72.0 -71.5 -71.5 -71.0
7 512 QAM -72.0 -71.5 -71.5 -71.0 -72.0 -71.0 -70.0 -71.5 -70.5 -70.0 -70.0 -70.0 -69.5 -69.5 -69.0
8 1024 QAM (strong FEC) -68.5 -68.0 -68.0 -67.5 -68.5 -67.5 -66.5 -68.0 -67.0 -66.5 -66.5 -66.5 -66.0 -66.0 -65.5
9 1024 QAM (light FEC) -68.0 -67.0 -67.0 -67.0 -67.5 -66.5 -66.0 -67.0 -66.0 -65.5 -66.0 -65.5 -65.5 -65.0 -64.5
0 QPSK 14 MHz -90.5 -90.0 -90.0 -89.5 -90.5 -89.5 -88.5 -90.0 -89.0 -88.5 -88.5 -88.5 -88.0 -88.0 -87.5
1 8 PSK -84.5 -84.0 -84.0 -83.5 -85.5 -83.5 -82.5 -84.0 -83.0 -82.5 -82.5 -82.5 -82.0 -82.0 -81.5
2 16 QAM -83.5 -83.0 -83.0 -82.5 -83.5 -82.5 -81.5 -83.0 -82.0 -81.5 -81.5 -81.5 -81.0 -81.0 -80.5
3 32 QAM -80.5 -79.5 -79.5 -79.5 -80.5 -79.0 -78.5 -79.5 -79.0 -78.5 -78.5 -78.0 -78.0 -77.5 -77.0
4 64 QAM -77.5 -76.5 -76.5 -76.5 -77.0 -76.0 -75.5 -76.5 -76.0 -75.5 -75.5 -75.0 -75.0 -74.5 -74.0
5 128 QAM -74.0 -73.5 -73.5 -73.0 -74.0 -73.0 -72.0 -73.5 -72.5 -72.0 -72.0 -72.0 -71.5 -71.5 -71.0
6 256 QAM -71.5 -70.5 -70.5 -70.5 -71.0 -70.0 -69.5 -70.5 -69.5 -69.0 -69.5 -69.0 -69.0 -68.5 -68.0
7 512 QAM -68.5 -68.0 -68.0 -67.5 -68.5 -67.5 -66.5 -68.0 -67.0 -66.5 -66.5 -66.5 -66.0 -66.0 -65.5
8 1024 QAM (strong FEC) -65.5 -65.0 -65.0 -64.5 -65.5 -64.5 -63.5 -65.0 -64.0 -63.5 -63.5 -63.5 -63.0 -63.0 -62.5
9 1024 QAM (light FEC) -65.0 -64.0 -64.0 -64.0 -64.5 -63.5 -63.0 -64.0 -63.5 -63.0 -63.0 -62.5 -62.5 -62.0 -61.5

Page 240 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Profile Modulation Channel Frequency (GHz)

Spacing 5.7- 6 7 8 10 11 13 15 18 23 2430 26 28-31 32 38 42

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

Page 241 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Profile Modulation Channel Frequency (GHz)

Spacing 5.7- 6 7 8 10 11 13 15 18 23 2430 26 28-31 32 38 42

0 QPSK 28 MHz -87.5 -87.0 -87.0 -86.5 -87.5 -86.0 -85.5 -87.0 -86.0 -85.5 -85.5 -85.5 -85.0 -84.5 -84.5
ACAP
1 8 PSK -82.5 -81.5 -81.5 -81.5 -82.5 -81.0 -80.5 -81.5 -81.0 -80.5 -80.5 -80.0 -80.0 -79.5 -79.0
2 16 QAM -81.0 -80.0 -80.0 -80.0 -80.5 -79.5 -79.0 -80.0 -79.0 -78.5 -79.0 -78.5 -78.5 -78.0 -77.5
3 32 QAM -77.0 -76.5 -76.5 -76.0 -77.0 -76.0 -75.0 -76.5 -75.5 -75.0 -75.0 -75.0 -74.5 -74.5 -74.0
4 64 QAM -74.5 -73.5 -73.5 -73.5 -74.0 -73.0 -72.5 -73.5 -72.5 -72.0 -72.5 -72.0 -72.0 -71.5 -71.0
5 128 QAM -71.0 -70.5 -70.5 -70.0 -71.0 -70.0 -69.0 -70.5 -69.5 -69.0 -69.0 -69.0 -68.5 -68.5 -68.0
6 256 QAM -68.0 -67.5 -67.5 -67.0 -68.0 -67.0 -66.0 -67.5 -66.5 -66.0 -66.0 -66.0 -65.5 -65.5 -65.0
7 512 QAM -66.0 -65.5 -65.5 -65.0 -66.0 -64.5 -64.0 -65.5 -64.5 -64.0 -64.0 -64.0 -63.5 -63.0 -63.0
8 1024 QAM (strong FEC) -63.0 -62.0 -62.0 -62.0 -62.5 -61.5 -61.0 -62.0 -61.0 -60.5 -61.0 -60.5 -60.5 -60.0 -59.5
9 1024 QAM (light FEC) -62.0 -61.0 -61.0 -61.0 -62.0 -60.5 -60.0 -61.0 -60.5 -60.0 -60.0 -59.5 -59.5 -59.0 -58.5
10 2048 QAM -58.0 -57.5 -57.5 -57.0 -58.0 -56.5 -56.0 -57.5 -56.5 -56.0 -56.0 -56.0 -55.5 -55.0 -55.0

Page 242 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Profile Modulation Channel Frequency (GHz)

Spacing 5.7- 6 7 8 10 11 13 15 18 23 2430 26 28-31 32 38 42

0 QPSK 40 MHz -86.0 -85.5 -85.5 -85.0 -86.0 -85.0 -84.0 -85.5 -84.5 -84.0 -84.0 -84.0 -83.5 -83.5 -83.0
1 8 PSK -81.0 -80.5 -80.5 -80.0 -81.0 -79.5 -79.0 -80.5 -79.5 -79.0 -79.0 -79.0 -78.5 -78.0 -78.0
2 16 QAM -79.5 -79.0 -79.0 -78.5 -79.5 -78.0 -77.5 -79.0 -78.0 -77.5 -77.5 -77.5 -77.0 -76.5 -76.5
3 32 QAM -76.0 -75.0 -75.0 -75.0 -75.5 -74.5 -74.0 -75.0 -74.0 -73.5 -74.0 -73.5 -73.5 -73.0 -72.5
4 64 QAM -73.0 -72.0 -72.0 -72.0 -73.0 -71.5 -71.0 -72.0 -71.5 -71.0 -71.0 -70.5 -70.5 -70.0 -69.5
5 128 QAM -70.0 -69.0 -69.0 -69.0 -70.0 -68.5 -68.0 -69.0 -68.5 -68.0 -68.0 -67.5 -67.5 -67.0 -66.5
6 256 QAM -67.0 -66.0 -66.0 -66.0 -66.5 -65.5 -65.0 -66.0 -65.0 -64.5 -65.0 -64.5 -64.5 -64.0 -63.5
7 512 QAM -64.0 -63.5 -63.5 -63.0 -64.0 -62.5 -62.0 -63.5 -62.5 -62.0 -62.0 -62.0 -61.5 -61.0 -61.0
8 1024 QAM (strong FEC) -61.5 -61.0 -61.0 -60.5 -61.5 -60.0 -59.5 -61.0 -60.0 -59.5 -59.5 -59.5 -59.0 -58.5 -58.5
9 1024 QAM (light FEC) -60.5 -60.0 -60.0 -59.5 -60.5 -59.5 -58.5 -60.0 -59.0 -58.5 -58.5 -58.5 -58.0 -58.0 -57.5
10 2048 QAM -58.0 -57.0 -57.0 -57.0 -58.0 -56.5 -56.0 -57.0 -56.5 -56.0 -56.0 -55.5 -55.5 -55.0 -54.5

Page 243 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Profile Modulation Channel Frequency (GHz)

Spacing 5.7- 6 7 8 10 11 13 15 18 23 2430 26 28-31 32 38 42

0 QPSK 56 MHz -84.0 -83.5 -83.5 -83.0 -84.0 -83.0 -82.0 -83.5 -82.5 -82.0 -82.0 -82.0 -81.5 -81.5 -81.0
ACCP
1 8 PSK -80.0 -79.5 -79.5 -79.0 -80.0 -79.0 -78.0 -79.5 -78.5 -78.0 -78.0 -78.0 -77.5 -77.5 -77.0
2 16 QAM -77.5 -77.0 -77.0 -76.5 -77.5 -76.5 -75.5 -77.0 -76.0 -75.5 -75.5 -75.5 -75.0 -75.0 -74.5
3 32 QAM -74.5 -73.5 -73.5 -73.5 -74.0 -73.0 -72.5 -73.5 -72.5 -72.0 -72.5 -72.0 -72.0 -71.5 -71.0
4 64 QAM -71.0 -70.5 -70.5 -70.0 -71.0 -70.0 -69.0 -70.5 -69.5 -69.0 -69.0 -69.0 -68.5 -68.5 -68.0
5 128 QAM -68.5 -67.5 -67.5 -67.5 -68.0 -67.0 -66.5 -67.5 -66.5 -66.0 -66.5 -66.0 -66.0 -65.5 -65.0
6 256 QAM -65.0 -64.5 -64.5 -64.0 -65.0 -64.0 -63.0 -64.5 -63.5 -63.0 -63.0 -63.0 -62.5 -62.5 -62.0
7 512 QAM -63.0 -62.5 -62.5 -62.0 -63.0 -61.5 -61.0 -62.5 -61.5 -61.0 -61.0 -61.0 -60.5 -60.0 -60.0
8 1024 QAM (strong FEC) -59.5 -59.0 -59.0 -58.5 -59.5 -58.5 -57.5 -59.0 -58.0 -57.5 -57.5 -57.5 -57.0 -57.0 -56.5
9 1024 QAM (light FEC) -58.5 -58.0 -58.0 -57.5 -58.5 -57.5 -56.5 -58.0 -57.0 -56.5 -56.5 -56.5 -56.0 -56.0 -55.5
10 2048 QAM -54.0 -53.5 -53.5 -53.0 -54.0 -53.0 -52.0 -53.5 -52.5 -52.0 -52.0 -52.0 -51.5 -51.5 -51.0

Page 244 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Profile Modulation Channel Frequency (GHz)

Spacing 5.7- 6 7 8 10 11 13 15 18 23 2430 26 28-31 32 38 42

0 QPSK 56 MHz -84.5 -84.0 -84.0 -83.5 -84.5 -83.0 -82.5 -84.0 -83.0 -82.5 -82.5 -82.5 -82.0 -81.5 -81.5
ACAP
1 8 PSK -80.0 -79.0 -79.0 -79.0 -79.5 -78.5 -78.0 -79.0 -78.0 -77.5 -78.0 -77.5 -77.5 -77.0 -76.5
2 16 QAM -77.5 -77.0 -77.0 -76.5 -77.5 -76.0 -75.5 -77.0 -76.0 -75.5 -75.5 -75.5 -75.0 -74.5 -74.5
3 32 QAM -74.0 -73.0 -73.0 -73.0 -73.5 -72.5 -72.0 -73.0 -72.0 -71.5 -72.0 -71.5 -71.5 -71.0 -70.5
4 64 QAM -70.5 -70.0 -70.0 -69.5 -70.5 -69.5 -68.5 -70.0 -69.0 -68.5 -68.5 -68.5 -68.0 -68.0 -67.5
5 128 QAM -68.0 -67.0 -67.0 -67.0 -67.5 -66.5 -66.0 -67.0 -66.0 -65.5 -66.0 -65.5 -65.5 -65.0 -64.5
6 256 QAM -64.5 -64.0 -64.0 -63.5 -64.5 -63.5 -62.5 -64.0 -63.0 -62.5 -62.5 -62.5 -62.0 -62.0 -61.5
7 512 QAM -62.5 -62.0 -62.0 -61.5 -62.5 -61.5 -60.5 -62.0 -61.0 -60.5 -60.5 -60.5 -60.0 -60.0 -59.5
8 1024 QAM (strong FEC) -59.0 -58.5 -58.5 -58.0 -59.0 -58.0 -57.0 -58.5 -57.5 -57.0 -57.0 -57.0 -56.5 -56.5 -56.0
9 1024 QAM (light FEC) -58.0 -57.5 -57.5 -57.0 -58.0 -57.0 -56.0 -57.5 -56.5 -56.0 -56.0 -56.0 -55.5 -55.5 -55.0
10 2048 QAM -55.5 -54.5 -54.5 -54.5 -55.0 -54.0 -53.5 -54.5 -53.5 -53.0 -53.5 -53.0 -53.0 -52.5 -52.0

Page 245 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Profile Modulation Channel Frequency (GHz)

Spacing 5.7- 6 7 8 10 11 13 15 18 23 2431 26 28-31 32 38 42

0 QPSK 80 MHz -82.5 -82.0 -82.0 -81.5 -82.5 -81.5 -80.5 -82.0 -81.0 -80.5 -80.5 -80.5 -80.0 -80.0 -79.5
ACCP
1 8 PSK -78.5 -78.0 -78.0 -77.5 -78.5 -77.5 -76.5 -78.0 -77.0 -76.5 -76.5 -76.5 -76.0 -76.0 -75.5
2 16 QAM -76.0 -75.5 -75.5 -75.0 -76.0 -75.0 -74.0 -75.5 -74.5 -74.0 -74.0 -74.0 -73.5 -73.5 -73.0
3 32 QAM -73.0 -72.0 -72.0 -72.0 -72.5 -71.5 -71.0 -72.0 -71.0 -70.5 -71.0 -70.5 -70.5 -70.0 -69.5
4 64 QAM -69.5 -69.0 -69.0 -68.5 -69.5 -68.5 -67.5 -69.0 -68.0 -67.5 -67.5 -67.5 -67.0 -67.0 -66.5
5 128 QAM -67.0 -66.0 -66.0 -66.0 -66.5 -65.5 -65.0 -66.0 -65.0 -64.5 -65.0 -64.5 -64.5 -64.0 -63.5
6 256 QAM -63.5 -63.0 -63.0 -62.5 -63.5 -62.5 -61.5 -63.0 -62.0 -61.5 -61.5 -61.5 -61.0 -61.0 -60.5
7 512 QAM -61.5 -61.0 -61.0 -60.5 -61.5 -60.0 -59.5 -61.0 -60.0 -59.5 -59.5 -59.5 -59.0 -58.5 -58.5
8 1024 QAM (strong FEC) -58.0 -57.5 -57.5 -57.0 -58.0 -57.0 -56.0 -57.5 -56.5 -56.0 -56.0 -56.0 -55.5 -55.5 -55.0
9 1024 QAM (light FEC) -57.0 -56.5 -56.5 -56.0 -57.0 -56.0 -55.0 -56.5 -55.5 -55.0 -55.0 -55.0 -54.5 -54.5 -54.0

8.6.1 Overload Thresholds

• For modulations up to and including 1024 QAM (strong FEC): -20dBm
• For modulations of 1024 (light FEC) and 2048 QAM: -25dBm

31
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 246 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.7 Frequency Bands

Table 55: Frequency Bands
Frequency Band TX Range RX Range Tx/Rx Spacing

U5.7 GHz 5725-5785 5790-5850 65

5725-5765 5810-5850 85
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
6179.415-6304.015 5927.375-6051.975 252A
5927.375-6051.975 6179.415-6304.015
6238.715-6363.315 5986.675-6111.275
5986.675-6111.275 6238.715-6363.315
6298.015-6422.615 6045.975-6170.575
6045.975-6170.575 6298.015-6422.615
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 247 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Frequency Band TX Range RX Range Tx/Rx Spacing

6H GHz 6920-7080 6420-6580 500A

6420-6580 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

Page 248 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Frequency Band TX Range RX Range Tx/Rx Spacing

7 GHz 7783.5-7898.5 7538.5-7653.5 245A

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 182A
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
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

Page 249 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Frequency Band TX Range RX Range Tx/Rx Spacing

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

Page 250 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Frequency Band TX Range RX Range Tx/Rx Spacing

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

Page 251 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Frequency Band TX Range RX Range Tx/Rx Spacing

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

Frequency Band TX Range RX Range Tx/Rx Spacing

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

Page 252 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Frequency Band TX Range RX Range Tx/Rx Spacing

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

Page 253 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Frequency Band TX Range RX Range Tx/Rx Spacing

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
8016.5-8156.5 7733-7873 283A
7733-7873 8016.5-8156.5
8128.5-8268.5 7845-7985
7845-7985 8128.5-8268.5

Frequency Band TX Range RX Range Tx/Rx Spacing

10 GHz 10501-10563 10333-10395 168A

10333-10395 10501-10563
10529-10591 10361-10423
10361-10423 10529-10591
10585-10647 10417-10479
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

Page 254 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Frequency Band TX Range RX Range Tx/Rx Spacing

10499-10531 10590-10622
10618-10649 10527-10558
10527-10558 10618-10649
10646-10677 10555-10586
10555-10586 10646-10677

Frequency Band TX Range RX Range Tx/Rx Spacing

11 GHz 11425-11725 10915-11207 All

10915-11207 11425-11725
11185-11485 10695-10955
10695-10955 11185-11485

Frequency Band TX Range RX Range Tx/Rx Spacing

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
12850-12925 13050-13150
13050-13150 12850-12925

Frequency Band TX Range RX Range Tx/Rx Spacing

15 GHz 15110-15348 14620-14858 490
14620-14858 15110-15348
14887-15117 14397-14627

Page 255 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Frequency Band TX Range RX Range Tx/Rx Spacing

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

Frequency Band TX Range RX Range Tx/Rx Spacing

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

Frequency Band TX Range RX Range Tx/Rx Spacing

23 GHz 23000-23600 22000-22600 1008
22000-22600 23000-23600
22400-23000 21200-21800 1232 /1200
21200-21800 22400-23000
23000-23600 21800-22400
21800-22400 23000-23600

Page 256 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Frequency Band TX Range RX Range Tx/Rx Spacing

32
24UL GHz 24000 - 24250 24000 - 24250 All

Frequency Band TX Range RX Range Tx/Rx Spacing

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

Frequency Band TX Range RX Range Tx/Rx Spacing

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
27548-27997 28556-29005
29100-29125 29225-29250 125

32
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 257 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Frequency Band TX Range RX Range Tx/Rx Spacing

29225-29250 29100-29125

Frequency Band TX Range RX Range Tx/Rx Spacing

31 GHz 31000-31085 31215-31300 175

31215-31300 31000-31085

Frequency Band TX Range RX Range Tx/Rx Spacing

32 GHz 31815-32207 32627-33019 812

32627-33019 31815-32207
32179-32571 32991-33383
32991-33383 32179-32571

Frequency Band TX Range RX Range Tx/Rx Spacing

38 GHz 38820-39440 37560-38180 1260

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

Frequency Band TX Range RX Range Tx/Rx Spacing

42 GHz 40550-41278 42050-42778 1500

42050-42778 40550-41278
41222-41950.5 42722-43450
42722-43450 41222-41950.5

Page 258 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.8 Mediation Device Losses

Table 56: Mediation Device Losses
Mediation Devices Signal Path / Remarks Maximum Insertion Loss [dB]
5.7-8 GHz 11 GHz 13-15 GHz 18 GHz 23-26 GHz 28-38 GHz 42 GHz

Size varies per

Flex WG 0.5 0.5 1.2 1.2 1.5 1.8 2.5
frequency.
OMT Radio to antenna
0.3 0.3 0.3 0.3 0.5 0.5 0.5
ports (V or H)
Splitter Radio to antenna port 3.6 3.7 3.7 3.7 3.7 4.0 4.0
Dual Coupler Main Paths 1.6 1.6 1.6 1.8 1.8 2.0 2.0
Secondary Paths 6±0.7 6±0.7 6±0.7 6±0.8 6±0.8 6±1.0 6±1.0
Dual Splitter Radio to antenna port 3.6 3.7 3.7 3.7 3.7 4.0 4.0
Dual Circulator High Ch radio to
0.2 0.2 0.2 0.5 0.5 0.5 0.5
antenna port
Low Ch radio to
0.2 0.2 0.2 0.5 0.5 0.5 0.5
antenna port

Notes: The antenna interface is always the IP-20C interface.

If other antennas are to be used, an adaptor with a 0.1 dB loss
should be considered.
The numbers above represent the maximum loss per
component.
The following diagram explains the circulators insertion loss:

Page 259 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.9 Ethernet Latency Specifications

8.9.1 Latency – 3.5 MHz Channel Bandwidth
Table 57: Latency – 3.5 MHz Channel Bandwidth
ACM Working Modulation Frame Size Latency (µsec) with GbE Interface
Point 64 128 256 512 1024 1518

0 QPSK 1659 1734 1883 2180 2774 3348

1 16 QAM 903 936 1001 1130 1389 1639
2 32 QAM 783 808 856 952 1146 1333
3 64 QAM 704 724 763 842 999 1149
4 128 QAM 650 668 701 767 901 1027
5 256 QAM 587 603 632 692 811 923

8.9.2 Latency – 7 MHz Channel Bandwidth

Table 58: Latency – 7 MHz Channel Bandwidth
ACM Working Modulation Frame Latency (µsec) with GbE Interface
Point Size 64 128 256 512 1024 1518

0 QPSK 701 763 882 1129 1621 2094

1 8 PSK 516 558 643 810 1144 1466
2 16 QAM 403 432 494 612 852 1081
3 32 QAM 357 381 427 518 702 878
4 64 QAM 326 345 383 459 610 753
5 128 QAM 307 321 353 417 545 666
6 256 QAM 309 324 352 409 522 628
7 512 QAM 346 358 385 437 544 644
8 1024 QAM (strong FEC) 327 340 365 415 516 610
9 1024 QAM (light FEC) 302 314 338 385 481 569

Page 260 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.9.3 Latency – 14 MHz Channel Bandwidth

Table 59: Latency – 14 MHz Channel Bandwidth
ACM Working Modulation Frame Latency (µsec) with GbE Interface
Point Size 64 128 256 512 1024 1518

0 QPSK 276 304 360 473 698 913

1 8 PSK 222 242 281 358 512 659
2 16 QAM 178 193 222 280 398 506
3 32 QAM 166 178 201 247 339 424
4 64 QAM 159 168 187 226 303 374
5 128 QAM 191 199 216 248 315 375
6 256 QAM 136 142 158 187 248 302
7 512 QAM 172 179 193 221 277 327
8 1024 QAM (strong FEC) 161 168 182 209 263 310
9 1024 QAM (light FEC) 158 164 177 202 254 299

8.9.4 Latency – 28 MHz Channel Bandwidth

Table 60: Latency – 28 MHz Channel Bandwidth
ACM Working Modulation Frame Latency (µsec) with GbE Interface
Point Size 64 128 256 512 1024 1518

0 QPSK 144 156 183 236 343 446

1 8 PSK 113 122 142 179 256 330
2 16 QAM 98 105 120 148 206 261
3 32 QAM 94 100 112 135 181 225
4 64 QAM 90 95 106 125 165 203
5 128 QAM 84 89 98 115 149 183
6 256 QAM 92 95 104 119 151 181
7 512 QAM 99 103 111 125 155 184
8 1024 QAM (strong FEC) 92 95 103 117 145 173
9 1024 QAM (light FEC) 93 96 104 117 145 171
10 2048 QAM 88 91 99 111 137 162

Page 261 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.9.5 Latency – 40 MHz Channel Bandwidth

Table 61: Latency – 40 MHz Channel Bandwidth
ACM Working Modulation Frame Latency (µsec) with GbE Interface
Point Size 64 128 256 512 1024 1518

0 QPSK 113 123 144 185 266 346

1 8 PSK 96 103 118 147 205 262
2 16 QAM 81 86 98 120 166 210
3 32 QAM 78 83 92 111 148 184
4 64 QAM 75 79 87 103 135 166
5 128 QAM 71 74 82 96 124 151
6 256 QAM 60 63 71 84 111 137
7 512 QAM 72 75 82 95 120 145
8 1024 QAM (strong FEC) 73 76 82 94 117 141
9 1024 QAM (light FEC) 75 78 84 95 118 140
10 2048 QAM 70 72 78 89 111 132

8.9.6 Latency – 56 MHz Channel Bandwidth

Table 62: Latency – 56 MHz Channel Bandwidth
ACM Working Modulation Frame Latency (µsec) with GbE Interface
Point Size 64 128 256 512 1024 1518

0 QPSK 85 92 107 138 199 255

1 8 PSK 95 100 112 135 180 222
2 16 QAM 62 67 76 95 132 164
3 32 QAM 59 63 71 87 118 145
4 64 QAM 57 60 67 81 109 133
5 128 QAM 55 58 64 77 103 124
6 256 QAM 55 58 64 76 100 120
7 512 QAM 58 61 67 78 102 121
8 1024 QAM (strong FEC) 55 58 64 75 97 116
9 1024 QAM (light FEC) 56 58 64 75 97 115
10 2048 QAM 53 55 61 72 93 110

Page 262 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.9.7 Latency – 80 MHz Channel Bandwidth

Table 63: Latency – 80 MHz Channel Bandwidth
ACM Working Modulation Frame Latency (µsec) with GbE Interface
Point Size 64 128 256 512 1024 1518

0 QPSK 72 78 90 114 163 211

1 8 PSK 58 63 73 91 130 168
2 16 QAM 53 57 65 79 111 141
3 32 QAM 50 54 61 73 101 127
4 64 QAM 48 52 57 69 94 118
5 128 QAM 46 50 55 66 89 111
6 256 QAM 53 56 61 71 93 114
7 512 QAM 50 53 58 67 88 109
8 1024 QAM 47 51 55 65 85 105

Page 263 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.10 Interface Specifications

8.10.1 Ethernet Interface Specifications
Table 64: Ethernet Interfaces

Supported Ethernet Interfaces 1 x 10/100/1000Base-T (RJ-45)

for Traffic 2x1000base-X (Optical SFP) or 1000Base-T (Electrical SFP)
Supported Ethernet Interfaces 10/100 Base-T (RJ-45)
for Management
Recommended SFP Types Optical 1000Base-LX (1310 nm) or SX (850 nm)
Note: SFP devices must be of industrial grade (-40°C to +85°C)

The following table lists Ceragon-approved SFP devices:

Table 65: SPF Devices

Ceragon Marketing Model Part Number Item Description

SFP-GE-LX-EXT-TEMP AO-0097-0 XCVR,SFP,1310nm,1.25Gb, SM,10km,W.DDM,INDUSTRIAL

SFP-GE-SX-EXT-TEMP AO-0098-0 XCVR,SFP,850nm,MM,1.0625 FC/ 1.25 GBE, INDUSTRIAL
SFP-GE-COPER-EXT-TMP- AO-0228-0 XCVR,SFP,COOPER 1000BASE-T,RX_LOS DISABLE,INDUSTR
LOS-DIS
SFP-BX-D-OPT-EXT-TEMP AO-0269-0 XCVR,SFP,SINGLE FIBER,1310nm RX/1490nm
TX,1.25Gb,SM,10km,W.DDM,INDUSTRIAL,SINGLE PACK KIT
SFP-BX-U-OPT-EXT-TEMP AO-0268-0 XCVR,SFP,SINGLE FIBER,1310nm TX/1490nm
RX,1.25Gb,SM,10km,W.DDM,INDUSTRIAL,SINGLE PACK KIT
SFP-XD-D-OPT-EXT-TEMP AO-0271-0 XCVR,SFP,SINGLE FIBER,1310nm RX/1490nm
TX,1.25Gb,SM,40km,W.DDM,INDUSTRIAL,SINGLE PACK KIT
SFP-XD-U-OPT-EXT-TEMP AO-0270-0 XCVR,SFP,SINGLE FIBER,1310nm TX/1490nm
RX,1.25Gb,SM,40km,W.DDM,INDUSTRIAL,SINGLE PACK KIT
SFP-XD15-D-OPT-EXT- AO-0279-0 XCVR,SFP,SINGLE FIBER,1310nm RX/1550nm
TEMP TX,1.25Gb,SM,40km,W.DDM,INDUSTRIAL,SINGLE PACK KIT
SFP-XD15-U-OPT-EXT- AO-0278-0 XCVR,SFP,SINGLE FIBER,1310nm TX/1550nm
TEMP RX,1.25Gb,SM,40km,W.DDM,INDUSTRIAL,SINGLE PACK KIT

Page 264 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following table lists recommended SFP+ modules that can be used with the MIMO
Extension port, including P4 on an IP-20C 2E2SX when used with MIMO 4x4 and Space
Diversity 2+2 configurations.

Table 66: Approved SFP+ Modules for MIMO Extension Ports

Ceragon Marketing Model Item Description

MIMO_SFP_10G XCVR,SFP+,850nm,MM,10 Gbit/s, INDUSTRIAL GRADE

Page 265 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.11 Carrier Ethernet Functionality

Table 67: Carrier Ethernet Functionality

Latency over the radio link < 0.15 ms @ 400 Mbps

"Jumbo" Frame Support Up to 9600 Bytes
General Enhanced link state propagation
Header De-Duplication
Integrated Carrier Ethernet Switching capacity: 5Gbps / 3.12Mpps
Switch Maximum number of Ethernet services: 64 plus one pre-defined
management service
MAC address learning with 128K MAC addresses
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) – 2K service level queues
2 Gbit packet buffer
Network resiliency MSTP
ERP (G.8032)
Service OAM FM (Y.1731)
PM (Y.1731)33
Performance Monitoring Per port Ethernet counters (RMON/RMON2)
Radio ACM statistics
Enhanced radio Ethernet statistics (Frame Error Rate, Throughput,
Capacity, Utilization)

33
PM is planned for future release.

Page 266 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Supported Ethernet/IP 802.3 – 10base-T

Standards 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

8.12 Synchronization Functionality

• SyncE
◦ SyncE input and output (G.8262)
• IEEE 1588v2 (Precision Time Protocol)
◦ Transparent Clock

Page 267 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.13 Network Management, Diagnostics, Status, and Alarms

Table 68: Network Management and Monitoring

Network Management System Ceragon NMS

NMS Interface protocol SNMPv1/v2c/v3
XML over HTTP/HTTPS toward NMS
Element Management Web based EMS, CLI
Management Channels & HTTP/HTTPS
Protocols Telnet/SSH-2
FTP/SFTP
Authentication, Authorization User access control
& Accounting X-509 Certificate
Management Interface Dedicated Ethernet interfaces or in-band in traffic ports
In-Band Management Support dedicated VLAN for management
TMN Ceragon NMS functions are in accordance with ITU-T
recommendations for TMN
RSL Indication Accurate power reading (dBm) available at IP-20C34, and NMS
Performance Monitoring Integral with onboard memory per ITU-T G.826/G.828

8.14 Mechanical Specifications

Table 69: Mechanical Specifications

Module Dimensions (H)230mm x (W)233mm x (D)98mm

Module Weight 6.5 kg
Pole Diameter Range (for Remote Mount Installation) 8.89 cm – 11.43 cm

34
The voltage at the BNC port is 1.XX where XX is the RSL level. For example: 1.59V means an
RSL of -59 dBm. Note that the voltage measured at the BNC port is not accurate and should
be used only as an aid).

Page 268 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.15 Standards Compliance

Table 70: Standards Compliance
Specification Standard

Radio EN 302 217-2-2

EMC EN 301 489-1, EN 301 489-4, Class B (Europe)
FCC 47 CFR, part 15, class B (US)
ICES-003, Class B (Canada)
TEC/EMI/TEL-001/01, Class B (India)
Surge EN61000-4-5, Class 4 (for PWR and ETH1/PoE ports)
Safety EN 60950-1
IEC 60950-1
UL 60950-1
CSA-C22.2 No.60950-1
EN 60950-22
UL 60950-22
CSA C22.2.60950-22

8.16 Environmental Specifications

• Operating: ETSI EN 300 019-1-4 Class 4.1
◦ Temperature range for continuous operating temperature with high
reliability:
-33C to +55C
◦ Temperature range for exceptional temperatures; tested successfully, with
limited margins:
-45C to +60C
◦ Humidity: 5%RH to 100%RH
IEC529 IP66
• Storage: ETSI EN 300 019-1-1 Class 1.2
• Transportation: ETSI EN 300 019-1-2 Class 2.3

Page 269 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.17 Antenna Specifications

• Direct Mount:
CommScope (VHLP), RFS, Xian Putian (WTG), and Radio Wave
• Remote Mount:

Table 71: Antenna Specifications, Remote Mount

Frequency (GHz) Waveguide Standard Waveguide Flange Antenna Flange

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

Please contact your Ceragon representative for details.

8.18 Power Input Specifications

Table 72: Power Input

Standard Input -48 VDC

DC Input range -40 to -60 VDC

8.19 Power Consumption Specifications

Table 73: Power Consumption

Maximum Power 5.7-6 7-8 GHz 11 GHz 13-15 18-24 26-42

Consumption GHz GHz GHz GHz

2+0 Operation 65W 75W 65W 55W 48W 55W

1+0 Operation (one of the 40W 50W 53W 41W 39W 41W
carriers is muted)
Both carriers are muted 15W 25W 41W 27W 30W 27W

Note: Typical values are 5% less than the values listed above.

Page 270 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.20 Power Connection Options

Table 74: Power Connection Options
Power Source and Range Data Connection Connection Length DC Cable Type /
Type Gage

Ext DC ≤ 100m 18AWG

-(40.5 ÷ 60)VDC Optical
100m ÷ 300m 12AWG

Electrical ≤ 100m 18AWG

PoE_Inj_AO Electrical ≤ 100m (13 GHz and above) CAT5e (24AWG)
(All outdoor PoE Injector, ≤ 75m (5.7-11 GHz)
-40 ÷ 60VDC)
PoE_Inj_AO_2DC_24V_48V Electrical ≤ 100m CAT5e (24AWG)
(All outdoor PoE Injector,
-(18 ÷ 60)VDC35,
DC input redundancy)

35
Optional.

Page 271 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.21 PoE Injector Specifications

8.21.1 Power Input
Table 75: PoE Injector Power Input

Standard Input -48

DC Input range -(18/40.5 to 60) VDC

8.21.2 Environmental
• Operating: ETSI EN 300 019-1-4 Class 4.1
◦ Temperature range for continuous operating temperature with high
reliability: -33C to +55C
◦ Temperature range for exceptional temperatures; tested successfully, with
limited margins: -45C to +60C
◦ Humidity: 5%RH to 100%RH
IEC529 IP66
• Storage: ETSI EN 300 019-1-1 Class 1.2
• Transportation: ETSI EN 300 019-1-2 Class 2.3

8.21.3 Standards Compliance

Table 76: PoE Injector Standards Compliance
Specification Standard

EMC EN 301 489-1, EN 301 489-4, Class A (Europe)

FCC 47 CFR, part 15, class B (US)
ICES-003, Class B (Canada)
TEC/EMI/TEL-001/01, Class A (India)
Safety EN 60950-1
IEC 60950-1
UL 60950-1
CSA-C22.2 No.60950-1
EN 60950-22
UL 60950-22
CSA C22.2.60950-22

8.21.4 Mechanical
Table 77: PoE Injector Standards Compliance

Module Dimensions (H)134mm x (W)190mm x (D)62mm

Module Weight 1kg

Page 272 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

8.22 Cable Specifications

8.22.1 Outdoor Ethernet Cable Specifications
Table 78: Outdoor Ethernet Cable – Electrical Requirements

Cable type CAT-5e SFUTP, 4 pairs, according to ANSI/TIA/EIA-568-B-2

Wire gage 24 AWG
Stranding Solid
Voltage rating 70V
Shielding Braid + Foil
Pinout

Table 79: Outdoor Ethernet Cable – Mechanical/ Environmental Requirements

Jacket PVC, double, UV resistant

Outer diameter 7-10 mm
Operating and Storage -40°C - 85°C
temperature range
Flammability rating According to UL-1581 VW1, IEC 60332-1
RoHS According to Directive/2002/95/EC

8.22.2 Outdoor DC Cable Specifications

Table 80: Outdoor DC Cable – Electrical Requirements

Cable type 2 tinned copper wires

Wire gage 18 AWG (for <100m installations)
12 AWG (for >100m installations)
Stranding stranded
Voltage rating 600V

Page 273 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Spark test 4KV

Dielectric strength 2KV AC min

Table 81: Outdoor DC Cable – Mechanical/ Environmental Requirements

Jacket PVC, double, UV resistant

Outer diameter 7-10 mm
Operating & Storage temperature range -40°C - 85°C
Flammability rating According to UL-1581 VW1, IEC 60332-1
RoHS According to Directive/2002/95/EC

8.22.3 ATEX Glands and Cables

Table 82: ATEX Glands and Cables
Marketing Model Marketing Description Item Description

IP-20_ATEX_FO_MM_AR_1m IP-20_ATEX_FO_MM_1m-ARMORED Pigtail 1m for SFP Cable Armored

IP-20_ATEX_FO_MM_1m IP-20_ATEX_FO_MM_1m Pigtail 1m for SFP Cable
IP-20_ATEX_DC_16AWG_AR_1m IP-20_ATEX_DC_16AWG_1m-ARMORED Pigtail 1m for DC Cable Armored
IP-20_ATEX_DC_16AWG_1m IP-20_ATEX_DC_16AWG_1m Pigtail 1m for DC Cable
IP-20_ATEX_RJ45_CAT5_AR_1m IP-20_ATEX_RJ45_CAT5_1m-ARMORED Pigtail 1m for Cat5E Cable Armored
IP-20_ATEX_RJ45_CAT5_1m IP-20_ATEX_RJ45_CAT5_1m Pigtail 1m for Cat5E Cable
IP-20_ATEX_FO_MM_AR_0.2m IP-20_ATEX_FO_MM_0.2m-ARMORED Pigtail 0.2m for SFP Cable Armored
IP-20_ATEX_FO_MM_0.2m IP-20_ATEX_FO_MM_0.2m Pigtail 0.2m for SFP Cable
IP-20_ATEX_DC_16AWG_AR_0.2m IP-20_ATEX_DC_16AWG_0.2m- Pigtail 0.2m for DC Cable Armored
ARMORED
IP-20_ATEX_DC_16AWG_0.2m IP-20_ATEX_DC_16AWG_0.2m Pigtail 0.2m for DC Cable
IP-20_ATEX_RJ45_CAT5_AR_0.2m IP-20_ATEX_RJ45_CAT5_0.2m-ARMORED Pigtail 0.2m for Cat5E Cable Armored
IP-20_ATEX_RJ45_CAT5_0.2m IP-20_ATEX_RJ45_CAT5_0.2m Pigtail 0.2m for Cat5E Cable
IP-20C_ATEX_ZONE2 IP-20C ATEX Zone 2 IP-20C ATEX Zone 2

Page 274 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

9. Appendix A – Marketing Model Construction

This appendix explains how to read marketing models for the IP-20C. Constructing
a marketing model for the purpose of equipment order should always be done
using a configurator.
Note: Not all fields are always necessary to define a valid marketing
model. If a specific field is not applicable, it should be omitted.

Table 83: IP-20C- PP-a-fw-xxxY-ccc-h-abc

Placeholder in Description Possible Values
Marketing Model

PP Power version Blank for standard power

HP – High Power
a Regional standard E-ETSI
F-FCC
Applicable only for 13GHz and up
f Frequency band U5.7,6L,6H,7,8,10,11,13,15,18,23,24,26,28,32,38,42
w When followed by w, indicates support for channels up to
80MHz as defined by FCC standards (11,18 GHz). For
example: 11w.
xxxY TX-RX separation and block xxx - TRS 3 figures in [MHz].
indication(Ceragon internal) Y - Letter to indicate frequency block.
Example: 266A
The frequency block is a Ceragon internal parameter which
defines different channelization using the same TRS and
frequency band.
ccc Channel indication or {Start ch}W{End ch}
LOW/HIGH or blank Example: 10W15
h TX low / TX high indication L – TX Low
H – TX high
abc Ethernet Ports Options. Port structure:
a- Port1, b-Port2, c-Port3 E - Electrical, S - SFP, X – Data sharing port for MIMO
application. X in this location denotes MIMO HW ready.
Alternatively, 2E2SX is used for a model with two electrical
ports, one SFP port, and one dual-use SFP or MIMO port.

Page 275 of 278

Ceragon Proprietary and Confidential

 Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

The following are some examples of specific IP-20C marketing models based on the syntax specified above.

Table 84: IP-20C Marketing Model Example

Marketing Model Example Explanation

IP-20C-E-15-315-4W7-H- ESX IP-20C Dual Core, ETSI standard, 15GHz, TRS=315MHz, two identical
diplexers covering channels 4 to 7, TX high,
Ports: Electrical, SFP, Extension, MIMO HW ready
IP-20C-HP-11w-500-4W9-H-ESX IP-20C, Dual Core, High Power, 11GHz, 80MHz channels support, 500MHz
TRS, two identical diplexers covering channels 4-9 TX high,
Ports: Electrical, SFP, Extension, MIMO HW ready
IP-20C-E-15-420-1W8-H-2E2SX IP-20C Dual Core, ETSI standard, 15GHz, 420MHz TRS, two identical
diplexers covering channels 1 to 8 TX high, Ports: Two Electrical, One SFP,
Extension, MIMO HW ready

Page 276 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

10. Appendix B – ATEX Certification

This appendix provides a sample ATEX certification certificates for IP-20C.

Figure 143: ATEX Certification for FibeAir IP-20C – Page 1 (Sample)

Page 277 of 278

Ceragon Proprietary and Confidential

Technical Description for FibeAir IP-20C, CeraOS 10.7 (ETSI)

Figure 144: ATEX Certification for FibeAir IP-20C – Page 2 (Sample)

Page 278 of 278

Ceragon Proprietary and Confidential