Ceragon IP20

ETSI Version
FibeAir IP-20C
Technical Description
March 2014
Release: 7.5
Document Revision A.06
Copyright © 2014 by Ceragon Networks Ltd. All rights reserved.

FibeAir IP-20C Technical Description
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 incidental or consequential
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 ("GPL License"). Inasmuch that such software is being used, it is released under
the GPL License, accordingly. Some software might have changed. The complete list of the
software being used in this product including their respective license and the aforementioned
public available changes is accessible on http://www.gnu.org/licenses/.
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.
Ceragon Proprietary and Confidential Page 2 of 227

Table of Contents
1. Synonyms and Acronyms .............................................................................. 13
2. Introduction .................................................................................................... 16
2.1 Product Overview ......................................................................................................... 17
2.2 Unique IP-20C Feature Set .......................................................................................... 18
2.3 System Configurations ................................................................................................. 19
2.3.1 MultiCore 2+0 Single or Dual Polarization Direct Mount ............................................. 19
2.3.2 2 x MultiCore 2+0 Single Polarization .......................................................................... 20
2.3.3 2 x MultiCore 2+0 Dual Polarization ............................................................................ 21
2.3.4 MultiCore 2+2 HSB Single Polarization ....................................................................... 22
2.3.5 MultiCore 2+2 HSB Dual Polarization XPIC ................................................................ 23
2.3.6 4x4 LoS MIMO ............................................................................................................. 24
2.3.7 2x2 LoS MIMO ............................................................................................................. 25
3. IP-20C Hardware Description......................................................................... 26

3.1 IP-20C Unit Description................................................................................................ 27
3.1.1 Hardware Architecture ................................................................................................. 28
3.1.2 Interfaces ..................................................................................................................... 29
3.1.3 Channel-Port Mapping to Polarization ......................................................................... 30
3.1.4 Management Connection for MIMO and Protection Configurations ............................ 33
3.2 MultiCore Mediation Devices (MCMD) ......................................................................... 35
3.3 PoE Injector .................................................................................................................. 36
3.3.1 PoE Injector Interfaces ................................................................................................. 36
4. Licensing......................................................................................................... 37
4.1 Working with License Keys .......................................................................................... 38
4.2 Demo License .............................................................................................................. 38
4.3 Licensed Features ........................................................................................................ 38
5. Feature Description ........................................................................................ 41

5.1 Unique MultiCore Architecture ..................................................................................... 42
5.1.1 Radio Script Configuration for Multiple Cores .............................................................. 43
5.1.2 Flexible Operating Modes with MultiCore Architecture ................................................ 43
5.1.3 TCO Savings as a Result of MultiCore Architecture .................................................... 46
5.2 Innovative Techniques to Boost Capacity and Reduce Latency ................................. 48
5.2.1 Capacity Summary ....................................................................................................... 50
5.2.2 Line of Sight (LoS) MIMO............................................................................................. 51
5.2.3 Header De-Duplication ................................................................................................. 59
5.2.4 Frame Cut-Through Support ........................................................................................ 62
5.2.5 Multi-Carrier ABC ......................................................................................................... 63
5.2.6 Adaptive Coding Modulation (ACM) ............................................................................. 67
5.2.7 Cross Polarization Interference Canceller (XPIC) ....................................................... 70
5.2.8 External Protection ....................................................................................................... 74
5.2.9 ATPC ............................................................................................................................ 79
5.3 Ethernet Features ........................................................................................................ 80

5.3.1 Ethernet Services Overview ......................................................................................... 81

5.3.2 IP-20C’s Ethernet Capabilities ..................................................................................... 96
5.3.3 Supported Standards ................................................................................................... 97
5.3.4 Ethernet Service Model ................................................................................................ 98
5.3.5 Ethernet Interfaces ..................................................................................................... 115
5.3.6 Quality of Service (QoS) ............................................................................................ 124
5.3.7 Global Switch Configuration ....................................................................................... 152
5.3.8 Network Resiliency..................................................................................................... 153
5.3.9 OAM ........................................................................................................................... 159
5.4 Synchronization .......................................................................................................... 162
5.4.1 IP-20C Synchronization Solution ............................................................................... 162
5.4.2 Available Synchronization Interfaces ......................................................................... 163
5.4.3 Synchronous Ethernet (SyncE) .................................................................................. 164
5.4.4 IEEE-1588 Transparent Clock ................................................................................... 164
5.4.5 SSM Support and Loop Prevention ........................................................................... 166
6. FibeAir IP-20C Management ........................................................................ 168

6.1 Management Overview .............................................................................................. 169
6.2 Management Communication Channels and Protocols ............................................. 170
6.3 Web-Based Element Management System (Web EMS) ........................................... 172
6.4 Command Line Interface (CLI) ................................................................................... 173
6.5 Configuration Management ........................................................................................ 173
6.6 Software Management ............................................................................................... 174
6.6.1 Backup Software Version ........................................................................................... 174
6.7 In-Band Management................................................................................................. 175
6.8 Local Management..................................................................................................... 175
6.9 Alarms ........................................................................................................................ 176
6.9.1 Configurable RSL Threshold for Alarms and Traps ................................................... 176
6.9.2 Alarms Editing ............................................................................................................ 176
6.10 NTP Support .............................................................................................................. 176
6.11 UTC Support .............................................................................................................. 176
6.12 System Security Features .......................................................................................... 177
6.12.1 Ceragon’s Layered Security Concept ........................................................................ 177
6.12.2 Defenses in Management Communication Channels ................................................ 178
6.12.3 Defenses in User and System Authentication Procedures ........................................ 179
6.12.4 Secure Communication Channels ............................................................................. 181
6.12.5 Security Log ............................................................................................................... 184
7. Standards and Certifications ....................................................................... 186

7.1 Supported Ethernet Standards .................................................................................. 187
7.2 MEF Certifications for Ethernet Services ................................................................... 187
8. Specifications ............................................................................................... 188

8.1 General Radio Specifications ..................................................................................... 189
8.1.1 6-15 GHz .................................................................................................................... 189
8.1.2 18-42 GHz .................................................................................................................. 189

8.2 Frequency Accuracy .................................................................................................. 189

8.3 Radio Capacity Specifications ................................................................................... 190
8.3.1 28 MHz Channel Bandwidth (ACCP) ......................................................................... 190
8.3.2 28 MHz Channel Bandwidth (ACAP) ......................................................................... 191
8.3.5 56 MHz Channel Bandwidth (ACAP) ......................................................................... 192
8.3.6 80 MHz Channel Bandwidth ...................................................................................... 193
8.4 Transmit Power Specifications ................................................................................... 194
8.5 Receiver Threshold Specifications ............................................................................. 196
8.5.1 Overload Thresholds .................................................................................................. 201
8.6 Frequency Bands ....................................................................................................... 202
8.7 Mediation Device Losses ........................................................................................... 213
8.8 Ethernet Latency Specifications ................................................................................. 214
8.8.1 Latency – 28 MHz Channel Bandwidth ...................................................................... 214
8.9 Interface Specifications .............................................................................................. 216
8.9.1 Ethernet Interface Specifications ............................................................................... 216
8.10 Carrier Ethernet Functionality .................................................................................... 217
8.11 Synchronization Functionality .................................................................................... 218
8.12 Network Management, Diagnostics, Status, and Alarms ........................................... 218
8.13 Mechanical Specifications .......................................................................................... 218
8.14 Standards Compliance ............................................................................................... 219
8.15 Environmental Specifications ..................................................................................... 220
8.16 Antenna Specifications............................................................................................... 221
8.17 Power Input Specifications ......................................................................................... 221
8.18 Power Consumption Specifications ........................................................................... 221
8.19 Power Connection Options ........................................................................................ 222
8.20 PoE Injector Specifications ........................................................................................ 223
8.20.1 Power Input ................................................................................................................ 223
8.20.2 Environmental ............................................................................................................ 223
8.20.3 Standards Compliance ............................................................................................... 223
8.20.4 Mechanical ................................................................................................................. 224
8.21 Cable Specifications ................................................................................................... 225
8.21.1 Outdoor Ethernet Cable Specifications ...................................................................... 225
8.21.2 Outdoor DC Cable Specifications .............................................................................. 226
9. Appendix A – Marketing Model Construction ............................................. 227

List of Figures
MultiCore 2+0 Direct Mount Configuration......................................................... 19
MultiCore 2+0 DP ACAP ...................................................................................... 19
MultiCore 2+0 DP CCDP ...................................................................................... 19
MultiCore 2+0 SP.................................................................................................. 19
2 x MultiCore 2+0 Single Polarization Configuration ......................................... 20
2 x MultiCore 2+0 Dual Polarization Configuration ............................................ 21
MultiCore 2+2 HSB Single Polarization Configuration ...................................... 22
MultiCore 2+2 HSB Dual Polarization Configuration ......................................... 23
4x4 LoS MIMO Direct Mount Configuration ........................................................ 24
4x4 LoS MIMO ...................................................................................................... 24
2x2 LoS MIMO Direct Mount Configuration ........................................................ 25

4x4 LoS MIMO ...................................................................................................... 25
IP-20C Rear View (Left) and Front View (Right) ................................................. 27
Cable Gland Construction ................................................................................... 27

IP-20C Block Diagram .......................................................................................... 28
IP-20C Interfaces .................................................................................................. 29
Separation Criteria when Working with Two Diplexer Types ............................ 32

MIMO/Protection Signaling Cable Pinouts ......................................................... 33
4x4 MIMO Configuration with External Management ........................................ 34
Splitter .................................................................................................................. 35
OMT....................................................................................................................... 35
PoE Injector .......................................................................................................... 36
PoE Injector Ports ................................................................................................ 36
IP-20C MultiCore Modem and RFIC Chipsets..................................................... 42
Performance Characteristics of Generic, 1+0 Single-Core Radio..................... 43
Doubling IP-20C’s Capacity by Activating Second Core ................................... 44

Doubling Link Span While Increasing Capacity by Activating Second Core ... 44
Utilizing Increased System Gain to Reduce Antenna Size ................................ 45
Quadrupling Capacity by Leveraging LoS MIMO with IP-20C’s MultiCore

Architecture .................................................................................................... 46

NLoS MIMO (Left) and LoS MIMO (Right) Compared ......................................... 51

LoS MIMO – Transmitting and Receiving on a Single Frequency Channel...... 51
General LoS MIMO Antenna Setup ..................................................................... 52
4x4 MIMO: Two MultiCore Units Directly Mounted to the Antenna .................. 53
LoS MIMO: Criterion for Optimal Antenna Separation ...................................... 54
LoS MIMO: Criterion for Optimal Antenna Separation in Symmetrical Topology
......................................................................................................................... 54
LoS MIMO: Optimal Antenna Separation vs. Link Distance .............................. 55
Continuum of Optimal LoS MIMO Installation Scenarios .................................. 56
Effect of Sub-Optimal Installation on Capacity (Maximum Capacity is at
1024 QAM) ....................................................................................................... 57
Asymmetrical Antenna Setup ............................................................................. 58
Header De-Duplication Operation on Frame Structure ..................................... 61
Frame Cut-Through.............................................................................................. 62
Multi-Carrier ABC Traffic Flow ............................................................................ 63

Multi-Carrier ABC Traffic Distribution ................................................................ 64
Multi-Carrier ABC Load Balancing with Different ACM Points ......................... 64
Adaptive Coding and Modulation with 11 Working Points ................................ 68

Dual Polarization .................................................................................................. 70
XPIC Implementation ........................................................................................... 71
XPIC – Impact of Misalignments and Channel Degradation ............................. 71
1+1 HSB Protection – Line Protection Mode ...................................................... 74
1+1 HSB Protection – Split Protection Mode ..................................................... 75
MultiCore 2+2 HSB Protection – Line Protection Mode..................................... 76
Multiple Traffic Interfaces with Optical Splitters ................................................ 76
Internal and Local Management .......................................................................... 77
Basic Ethernet Service Model ............................................................................. 81
Ethernet Virtual Connection (EVC) ..................................................................... 82
Point to Point EVC ............................................................................................... 83
Multipoint to Multipoint EVC ............................................................................... 83

Rooted Multipoint EVC ........................................................................................ 83
MEF Ethernet Services Definition Framework ................................................... 85

E-Line Service Type Using Point-to-Point EVC .................................................. 86

EPL Application Example .................................................................................... 87
EVPL Application Example.................................................................................. 87
E-LAN Service Type Using Multipoint-to-Multipoint EVC.................................. 88

Adding a Site Using an E-Line service ............................................................... 89
Adding a Site Using an E-LAN service ............................................................... 89
MEF Ethernet Private LAN Example ................................................................... 90

MEF Ethernet Virtual Private LAN Example ....................................................... 91
E-Tree Service Type Using Rooted-Multipoint EVC ........................................... 91
E-Tree Service Type Using Multiple Roots ......................................................... 92

MEF Ethernet Private Tree Example ................................................................... 92
Ethernet Virtual Private Tree Example................................................................ 93
Mobile Backhaul Reference Model ..................................................................... 94

Packet Service Core Building Blocks ................................................................. 94
IP-20C Services Model ......................................................................................... 98
IP-20C Services Core ........................................................................................... 99

IP-20C Services Flow ......................................................................................... 100
Point-to-Point Service........................................................................................ 101
Multipoint Service .............................................................................................. 102
Management Service ......................................................................................... 104
Management Service and its Service Points .................................................... 106
SAPs and SNPs .................................................................................................. 107
Pipe Service Points ............................................................................................ 108
SAP, SNP and Pipe Service Points in a Microwave Network .......................... 108
Service Path Relationship on Point-to-Point Service Path ............................. 112
Physical and Logical Interfaces ........................................................................ 115
Grouped Interfaces as a Single Logical Interface on Ingress Side ................ 116
Grouped Interfaces as a Single Logical Interface on Egress Side ................. 116

Relationship of Logical Interfaces to the Switching Fabric ............................ 119
QoS Block Diagram............................................................................................ 124
Standard QoS and H-QoS Comparison ............................................................ 126

Hierarchical Classification ................................................................................ 127

Classification Method Priorities ........................................................................ 128
Ingress Policing Model ...................................................................................... 132
IP-20C Queue Manager ...................................................................................... 135

Synchronized Packet Loss ................................................................................ 136
Random Packet Loss with Increased Capacity Utilization Using WRED ....... 137
WRED Profile Curve ........................................................................................... 138

Detailed H-QoS Diagram .................................................................................... 141
Scheduling Mechanism for a Single Service Bundle ....................................... 144
G.8032 Ring in Idle (Normal) State .................................................................... 154

G.8032 Ring in Protecting State ........................................................................ 155
Load Balancing Example in G.8032 Ring ......................................................... 155
IP-20C End-to-End Service Management ......................................................... 159

SOAM Maintenance Entities (Example) ............................................................ 160
EFM Maintenance Entities (Example) ............................................................... 161
Transparent Clock Delay Compensation.......................................................... 166

Integrated IP-20C Management Tools............................................................... 169
Security Solution Architecture Concept........................................................... 177

List of Tables
IP-20C Feature Set ............................................................................................... 18
IP-20C Mediation Devices .................................................................................... 35
License Types ...................................................................................................... 38
Capacity Licenses ................................................................................................ 40
Edge CET Node Licenses .................................................................................... 40
TCO Comparison Between Single-Core and MultiCore Systems ..................... 47
Header De-Duplication......................................................................................... 59
ACM Working Points (Profiles) ........................................................................... 67

HSB Protection Switchover Triggers .................................................................. 78
MEF-Defined Ethernet Service Types ................................................................. 85
Ethernet Services Learning and Forwarding ................................................... 103

Service Point Types per Service Type .............................................................. 109
Service Point Types that can Co-Exist on the Same Interface........................ 110
Service Point Type-Attached Interface Type Combinations that can Co-Exist on

the Same Interface........................................................................................ 111
C-VLAN 802.1 UP and CFI Default Mapping to CoS and Color ....................... 128
S-VLAN 802.1 UP and DEI Default Mapping to CoS and Color ....................... 129
DSCP Default Mapping to CoS and Color ........................................................ 129
MPLS EXP Default Mapping to CoS and Color ................................................ 130
QoS Priority Profile Example ............................................................................ 145
WFQ Profile Example ......................................................................................... 147
802.1q UP Marking Table (C-VLAN) .................................................................. 149
802.1ad UP Marking Table (S-VLAN) ................................................................ 150
Summary and Comparison of Standard QoS and H-QoS................................ 151
Synchronization Interface Options ................................................................... 163
Dedicated Management Ports ........................................................................... 170
NMS Server Receiving Data Ports .................................................................... 171

Web Sending Data Ports ................................................................................... 171
Web Receiving Data Ports ................................................................................. 171

Additional Management Ports for IP-20C ......................................................... 171

Supported Ethernet Standards ......................................................................... 187
IP-20C Standard Power...................................................................................... 194
IP-20C High Power ............................................................................................. 195

IP-20C Marketing Model Example ..................................................................... 227

About This Guide

This document describes the main features, components, and specifications of
the FibeAir IP-20C system. This document applies to version 7.5.
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
 FibeAir IP-20C User Guide, DOC-00036523
 FibeAir IP-20C Installation Guide, DOC-00036522
 FibeAir IP-20C MIB Reference, DOC-00036524

1. Synonyms and Acronyms
ACAP Adjacent Channel Alternate Polarization

ACCP Adjacent Channel Co-Polarization
ACM Adaptive Coding and Modulation
AES Advanced Encryption Standard
AIS Alarm Indication Signal
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
DSCP Differentiated Service Code Point
EBS Excess Burst Size
EFM Ethernet in the First Mile
EIR Excess Information Rate
EPL Ethernet Private Line
EVPL Ethernet Virtual Private Line
EVC Ethernet Virtual Connection
FTP (SFTP) File Transfer Protocol (Secured File Transfer Protocol)
GbE Gigabit Ethernet
GMT Greenwich Mean Time
HTTP (HTTPS) Hypertext Transfer Protocol (Secured HTTP)
LAN Local area network

LMS License Management System

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 signal
System flows, thus inherently multiplying the capacity and increasing system gain
using existing spectral resources.
NLoS Non-Line-of-Sight
NMS Network Management System
NTP Network Time Protocol
OAM Operation Administration & Maintenance (Protocols)
PBB-TE Provider Backbone Bridge Traffic Engineering
PBS Peak Burst Rate
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
RDI Reverse 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

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

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.
The FibeAir series pay-as-you-go licensing 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.
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 28MHz 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.
IP-20C Feature Set
Extended Modulation Range ACM 4-2048 QAM (11 ACM points)

Frequency Bands 6-42 GHz
Wide Range of Channels 28, 40, 56, 112 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

2.3 System Configurations

FibeAir IP-20C is designed to support the following site configurations:
 MultiCore 2+0 Single/Dual Polarization
 2 x MultiCore 2+0 SP/DP
 MultiCore 2+2 SP/DP HSB
 2x2 LoS MIMO
 4x4 LoS MIMO
Note: For information on diplexer type and channel selection,
refer to Channel-Port Mapping to Polarization on page 30.
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.
MultiCore 2+0 Direct Mount Configuration
MultiCore 2+0 DP ACAP MultiCore 2+0 DP CCDP MultiCore 2+0 SP
Ch1V Ch1V Ch1 Ch2

Ch2H Ch1H

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 connected to the antenna using an RFU-C
splitter, with dual-core splitters on each side connecting the RFU-C splitter to
the IP-20C units.
2 x MultiCore 2+0 Single Polarization Configuration
Ch1 Ch2 Ch3 Ch4

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.
2 x MultiCore 2+0 Dual Polarization Configuration
Ch1 V Ch2 V
Ch1 H Ch2 H

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.
MultiCore 2+2 HSB Single Polarization Configuration
Ch1 Ch2
Ch1 Ch2

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.
MultiCore 2+2 HSB Dual Polarization Configuration
V V
Ch1
Ch1
H H
Ch2
Ch1

2.3.6 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+0 Space
Diversity (SD). In this case, the transmitters connected to
the diversity antenna should be muted. For details, refer to
Utilizing MIMO Configuration for Space Diversity on page 58.
4x4 LoS MIMO Direct Mount Configuration
4x4 LoS MIMO
Ch1 V
Ch1 V
Ch1H
Ch1H

2.3.7 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
Utilizing MIMO Configuration for Space Diversity on page 58.
2x2 LoS MIMO Direct Mount Configuration
4x4 LoS MIMO
Ch1 V
Ch1

3. IP-20C Hardware Description

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

 IP-20C Unit Description
 MultiCore Mediation Devices (MCMD)
 PoE Injector

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).
IP-20C Rear View (Left) and Front View (Right)
Cable Gland Construction

3.1.1 Hardware Architecture

The following diagram presents a detailed block diagram of the IP-20C.
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 29.

3.1.2 Interfaces
IP-20C Interfaces
 Data Port 1 for GbE traffic:

Electric: 10/100/1000Base-T. Supports PoE.
Optical: 1000Base-X (optional)
 Data Port 2 for GbE traffic:
Electric10/100/1000Base-T
 Data Port 3/EXT
Electric: 10/100/1000Base-T
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 216.
 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

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 6-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.
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):
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.

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 MIMO and Protection

Configurations
In MIMO and all HSB protection configurations, a special signaling cable must
be used to connect the management ports (MGT/PROT) of the two IP-20C
units.
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.
3.1.4.1 Preparing a MIMO/Protection Signaling Cable

The MIMO/Protection signaling cables require the following pinouts.
MIMO/Protection Signaling Cable Pinouts
RJ-45 connector RJ-45 connector

(male) (male)
4฀ 7
Port1: TX+ 1 W/G G/W 1 Port1: TX+
5฀ 8
Port1: TX- 2 G G 2 Port1: TX-
Port1: RX+ 3 W/O O/W 3 Port1: RX+
Port2: TX+ 4 Bl Bl 4 Port2: TX+
Port2: TX- 5 W/Bl Bl/W 5 Port2: TX-

Port1: RX- 6 O O 6 Port1: RX-
Port2: RX+ 7 W/Br Br/W 7 Port2: RX+
Port2: RX- 8 Br CAT5E cable Br 8 Port2: RX-
Color Abbreviations
W – White
G – Green
O – Orange
Bl – Blue
Br - Brown
3.1.4.2 Connecting a MIMO/Protection Signaling Cable

This option should be used when you plan to manage the system using
in-band management.
The MIMO/Protection signaling cable should be connected between the
management ports of two IP-20C units operating in either MIMO or HSB
protection mode. The physical cable connection is the same as connecting a
CAT5E cable to a system data or management port.
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.3 Connecting a MIMO/Protection Splitter

This option should be used when you plan to manage the system using out-of-
band (external) management rather than in-band management.
The 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.
 MIMO/Protection signaling port MIMO/Prot – A standard CAT5E cable
or a MIMO/Protection signaling cable should be connected between this
port and the other MIMO/Prot port of the second splitter on the mate )P-
20C unit.
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.
4x4 MIMO Configuration with External Management
Sys
Splitter
MIMO
Mng
/Prot
External
management
MIMO/Prot. Signaling cable
Standard Eth cable
Sys
OR
Splitter
MIMO
Mng
/Prot
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.
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)
Splitter
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.

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.
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 and with +24VDC
support, as well as EMC surge protection for both indoor and outdoor
installation options. It can be mounted on poles, walls, or inside racks.
PoE Injector
3.3.1 PoE Injector Interfaces

 DC Power Port 1 –40V to -60V
Note: A PoE supporting two redundant DC feeds each supporting
±(18-60)V is also available.
 GbE Data Port supporting 10/100/1000Base-T
 Power-Over-Ethernet (PoE) Port
 Grounding screw
PoE Injector Ports

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

 Working with License Keys
 Demo License
 Licensed Features

4.1 Working with License Keys

Ceragon provides a web-based License Management System (LMS). The LMS
enables authorized users to generate license keys, which are generated per
device serial number.
In order to upgrade a license, the license-key must be entered into the IP-20C.
The system checks and implements the new license key, enabling access to
new capacities and/or features.
In the event that the licensed capacity and feature set is exceeded a License
Violation alarm occurs. After a 48-hour grace period, all other alarms are
hidden until the capacity and features in use are brought within the licensed
capacity and feature set.
4.2 Demo License

A demo license is available that enables all features for 60 days. The demo
license expires 60 days from the time it was activated, and the most recent
valid license goes into effect. The 60-day period is only counted when the
system is powered up. 10 days before the demo license expires, an alarm is
raised indicating to the user that the demo license is about to expire.
4.3 Licensed Features

As your network expands and additional functionality is desired, license keys
can be purchased for the features described in the following table.
License Types
Marketing Model License Application Description For Addition

(Per Core / Per Device) Information
Capacity Licenses Per Core Enables you to increase your system’s radio Capacity Summary
Refer to Capacity capacity in gradual steps by upgrading your
Licenses on page 40. capacity license. Without a capacity license, each
core has a capacity of 10 Mbps. Licensed capacity
is available from 50 Mbps to 500 Mbps. A separate
license is required per core.
IP-20-SL-2nd-Core- Enables use of second core. Unique MultiCore
Act. Architecture
IP-20 SL - ACM Per Core Enables the use of Adaptive Coding and Adaptive Coding
Modulation (ACM) scripts. A separate license is Modulation (ACM)
required per core.
IP-20 SL - MIMO Per Core Enables the use of MIMO. A separate license is Line of Sight (LoS)
required for each core in the MIMO configuration. MIMO
IP-20 SL - MC-ABC Per Core Enables Multi-Carrier ABC. A separate license is Multi-Carrier ABC
required per core.
IP-20-SL-Header- Per Core Enables the use of Header De-Duplication, which Header De-Duplication
DeDuplication can be configured to operate at L2 through L4.

Marketing Model License Application Description For Addition

(Per Core / Per Device) Information
IP-20 SL - XPIC Per Core Enables the use of Cross Polarization Interference Cross Polarization
Canceller (XPIC). A separate license is required for Interference Canceller
each core in the XPIC pair. (XPIC)
IP-20 SL - GE port Per Device Enables the use of an Ethernet port for traffic. A Interfaces
license is required for each traffic port that is used
on the device. Any of these licenses can be
installed multiple times with dynamic allocation
inside the unit.
Refer to Edge CET Per Device Enables Carrier Ethernet Transport (CET) and a  Ethernet Service
Node Licenses on number of Ethernet services (EVCs), depending on Model
page 40. the type of CET Node license: 
 Edge CET Node – Up to 8 EVCs.
Quality of Service
(QoS)
 Aggregation Level 1 CET Node – Up to 64
EVCs.
A CET Node license also enables the following:
 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.
IP-20-SL-Network- Network Resiliency Enables G.8032 for improving network resiliency. Network Resiliency
Resiliency
IP-20 SL - H-QoS Per Device Enables H-QoS. This license is required to add Quality of Service (QoS)
service-bundles with dedicated queues to
interfaces. Without this license, only the default
eight queues per port are supported.
IP-20 SL - Enh. Per Device Enables configurable (non-default) queue buffer Quality of Service (QoS)
Packet 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.
IP-20 SL - Sync. Unit Per Device Enables the G.8262 synchronization unit. This Synchronization
license is required in order to provide end-to-end
synchronization distribution on the physical layer.
This license is also required to use Synchronous
Ethernet (SyncE).
IP-20 SL - Frame Per Device Enables Frame Cut-Through. Frame Cut-Through
Cut-Through Support
IP-20 SL - Secure Per Device Enables secure management protocols (SSH, Secure Communication
Management HTTPS, SFTP, SNMPv3, and RADIUS) Channels

Capacity Licenses
Marketing Model Description

IP-20-SL-Capacity-50M IP-20 SL - Capacity 50M, 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
Edge CET Node Licenses
Marketing Model Description

IP-20 SL - Edge-CET-Node Enables CET with up to 8 services/EVCs.
IP-20 SL - Agg-Lvl-1-CET-Node Enables CET with up to 64 services/EVCs.
IP-20 SL - Upg Edge/Agg-Lvl-1 Upgrades from "Edge-CET-Node" to "Agg-Lvl-1-CET-Node".

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

 Unique MultiCore Architecture
 Innovative Techniques to Boost Capacity and Reduce Latency
 Ethernet Features
 Synchronization

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.
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 Radio Script Configuration for Multiple Cores

When operating with two cores in a single IP-20C unit, users can configure
different scripts independently for each core. Configuring a script in one core
has no impact on the other core s traffic. When the core is reset following
configuration of a script in that core, only that core is reset following the
script s configuration. No general reset is performed.
During script configuration, the core being configured is set to mute. The mute
is released once the script configuration is completed.
5.1.2 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.
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.
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.2.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.

Doubling IP-20C’s Capacity by Activating Second Core
5.1.2.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.
Doubling Link Span While Increasing Capacity by Activating Second Core
For additional information:

 Multi-Carrier ABC

5.1.2.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.
Utilizing Increased System Gain to Reduce Antenna Size
5.1.2.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.
5.1.2.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.

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

 Line of Sight (LoS) MIMO
 Cross Polarization Interference Canceller (XPIC)
5.1.3 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.
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 a license for the second core.
 Remotely upload the license 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.
TCO Comparison Between Single-Core and MultiCore Systems
Single-Core system MultiCore system

Initial Installation 1+0 link with 1+0 antenna mediation 2+0 installation (remote or direct mount).
device (remote or direct mount). Only one core is licensed and activated.
Upgrade to 2+0  Obtain new radio equipment  Obtain license for second core.
 Send technical team to both ends  Activate second core remotely.
of the link (at least two site visits). 

Remotely define the link as 2+0 with L1
Dismantle existing radio and Multi-Carrier ABC (more efficient than
mediation device. 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 more Only 55% more power consumption than 1+0
with external switch). configuration (single core).
Site leasing fees Approximately double, since equipment No impact, MultiCore system within same
is doubled. small form factor unit
Warehouse Complicated, with different equipment Simple with single-spare, versatile radio for
management for different deployment scenarios many 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 (eader 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.

This section includes:

 Capacity Summary
 Line of Sight (LoS) MIMO
 Header De-Duplication
 Frame Cut-Through Support
 Multi-Carrier ABC
 Adaptive Coding Modulation (ACM)
 External Protection
 ATPC

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:
 Radio capacity – Up to 250/340/500/1000 Mbps throughput over
28/40/56/112 MHz channels
 All licensed bands – L6, U6, 7, 8, 10, 11, 13, 15, 18, 23, 26, 28, 32, 38, 42
GHz
 High Modulation – QPSK to 2048 QAM

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

4x4 MIMO: Two MultiCore Units Directly Mounted to the Antenna
5.2.2.2 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.
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.3 Antenna Separation Criteria for LoS MIMO

The following equation provides the criterion for optimal antenna separation
in a LoS MIMO configuration:
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 ( ).
 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

The following diagram provides a rough idea of the separation required

between antennas for different link spans using different frequencies.
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 LoS MIMO: Criterion for Optimal Antenna
Separation on page 54.

5.2.2.4 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 M)MO implementation.
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 M)MO 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.
The following figure further demonstrates how sub-optimal antenna
separation affects capacity relative to an optimal installation.

Effect of Sub-Optimal Installation on Capacity (Maximum Capacity is at 1024 QAM)
5.2.2.5 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.

Asymmetrical Antenna Setup
5.2.2.6 Utilizing MIMO Configuration for Space Diversity

FibeAir IP- C s M)MO capabilities can also be utilized, with minor
adjustments, to provide Baseband (BBS) 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+0 SD, using two IP-20C units), with antenna
separation based on SD requirements.
In both SD modes, the transmitter connected to the diversity antenna should
be manually 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.

5.2.3 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. Users can configure the depth of Header De-Duplication,
up to Layer 4.
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 enabled.
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.
In Header De-Duplication mode, the user can determine the depth to which
the de-duplication mechanism operates, from Layer 2 to Layer 4. 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.
Up to 68 bytes of the L2-4 header can be compressed. In addition Layer 1
header suppression is also performed, replacing the IFG and Preamble fields
(20 bytes) with a GFP header.
Header De-Duplication can be used to compress the following types of header
stacks:
 Ethernet MAC untagged
IPv4
 TCP
 UDP
IPv6
 TCP
 UDP

MPLS
 Ethernet MAC + VALN
IPv4
 TCP
 UDP
IPv6
 TCP
 UDP
MPLS
 Ethernet MAC with QinQ
IPv4
 TCP
 UDP
IPv6
 TCP
 UDP
MPLS
 PBB-TE
The following is a summary of the header elements at each network layer:
 L2:
Ethertype (2 bytes)
MAC SA (6 bytes)
MAC DA (6 bytes)
Outer VLAN header (4 bytes)
Inner VLAN header (4 bytes)
MPLS header (4 bytes)
B-MAC header (22 bytes)
 L3:
IPv4 header (24 bytes)
IPv6 header (40 bytes)
 L4:
UDP header (8 bytes)
TCP header (28 bytes)

The following figure provides a detailed diagram of how the frame structure is
affected by Header De-Duplication.
Header De-Duplication Operation on Frame Structure
IP-20C s Header De-Duplication can improve effective throughput by up to

300% or more without affecting user traffic.
Note: In a worst-case scenario, Header De-Duplication may add up
to 200ns latency.
5.2.3.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.4 Frame Cut-Through Support
Related topics:
 Ethernet Latency Specifications
Note: Frame Cut-Through is planned for future release.
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 and Pseudowires, with true
transparency to lower priority services.
Frame Cut-Through

5.2.5 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.
Multi-Carrier ABC Traffic Flow
Modem Modem
(Carrier 1) (Carrier 1)
Eth Traffic Eth

Traffic Splitter
Combiner
Modem Modem
(Carrier 2) (Carrier 2)

5.2.5.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.
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.
Multi-Carrier ABC Load Balancing with Different ACM Points

5.2.5.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
 Minimum ACM point – user configurable (including none)
 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.5.3 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.5.4 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, minimum ACM profile, 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.

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

in Multi-Carrier ABC and ACM on page 65, users can configure the system to
stop distributing traffic to an individual carrier in any one or more of the
following circumstances:1
 Excessive BER condition
 Signal Degrade condition
Users can manually block and unblock traffic from a single carrier.
5.2.5.5 Interoperability with Other FibeAir Units

An IP-20C using Multi-Carrier ABC can operate with an IP-20N Multi-Carrier
ABC group on the other side of the link, provided that the carriers in the IP-
20N s Multi-Carrier ABC group are using an RMC-B.
1
This feature is planned for future release.

5.2.6 Adaptive Coding Modulation (ACM)
Related topics:
 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.6.1 Eleven Working Points

IP-20C implements ACM with 11 available working points, as shown in the
following table:
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

Adaptive Coding and Modulation with 11 Working Points
5.2.6.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.6.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 license.

 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 license.
In the case of XPIC/ACM scripts, all the required conditions for XPIC apply.
The user can define a 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.6.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.6.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.
)f 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.6.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).

5.2.7 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.
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 XP)C 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 XP)C
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.2
2
The XPIC recovery mechanism is planned for future release.

5.2.7.1 XPIC Benefits

The advantages of FibeAir IP-20C s XP)C 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.7.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.
XPIC Implementation
V V+h V
h
v
H H+v H
IP-20C Dual feed antenna
(V and H feeds)
IP-20C
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.
XPIC – Impact of Misalignments and Channel Degradation

IP-20C s XP)C reaches a BER of e-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.7.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.7.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.
 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.8 External Protection

IP-20C offers MultiCore 1+1 and 2+2 HSB protection configurations.
1+1 HSB protection utilizes two IP-20C units operating in single core mode,
with a single antenna, to 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 mutes its
transmitter, 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.
Port 1 on each IP-20C is connected to an external switch or an optical splitter.
Both ports on each IP-20C unit belong to a LAG, with 100% distribution to
port 1 of the respective IP-20C unit.
If traffic is routed to the IP-20C units via an external switch, the switch is
configured as a static LAG. This is called Line Protection mode. In Line
Protection mode, Port 2 on each IP-20C is connected to Port 2 of the other IP-
20C. The traffic to the standby unit is forwarded to the active unit via Port 2 of
each unit. This enables the active unit to monitor traffic to the standby unit.
1+1 HSB Protection – Line Protection Mode
Port 1
f1
Modem 1 RF Chain
Port 2
Modem 2
Protection
Forwarding
External Coupler
Switch Active IP-20C Unit
(LAG)
Port 1
Modem 1 RF Chain
Port 2 f1
Modem 2
Standby IP-20C Unit
Alternatively, an optical splitter can be used to route traffic to the interfaces

on each IP-20C unit. This is called Split Protection mode. No protection
forwarding cable is required in Split Protection mode.

1+1 HSB Protection – Split Protection Mode
Port 1
f1
Modem 1 RF Chain
Port 2
Modem 2
Optical Coupler
Splitter Active IP-20C Unit
Port 1
Modem 1 RF Chain
Port 2 f1
Modem 2
Standby IP-20C Unit
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.
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. Each IP-20C unit
uses Multi-Carrier ABC to distribute traffic between the two cores. The cores
can use separate frequencies, or a single frequency with dual polarization
(XPIC).
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.

MultiCore 2+2 HSB Protection – Line Protection Mode
Port 1
f1
Modem 1 RF Chain
Port 2
f2
Modem 2 RF Chain
Protection
External Forwarding Coupler
Switch Active IP-20C Unit
(LAG)
Port 1
f1
Modem 1 RF Chain
Port 2
f2
Modem 2 RF Chain
Standby IP-20C Unit
If more than one traffic interface per IP-20C unit is required, an optical splitter
should be used (Split Protection Mode). This eliminates the need for
protection forwarding between the units, freeing the second Ethernet
interfaces on each unit for traffic.
Multiple Traffic Interfaces with Optical Splitters
Port 1
f1
Modem 1 RF Chain
Port 2
f2
Modem 2 RF Chain
Coupler
Optical
Splitter Active IP-20C Unit
Optical
Port 1
Splitter f1
Modem 1 RF Chain
Port 2
f2
Modem 2 RF Chain
Standby IP-20C 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 MIMO and
Protection Configurations on page 33). 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.

Internal and Local Management
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

5.2.8.1 Switchover Triggers

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 table lists the switchover triggers for HSB protection according
to their priority, with the highest priority triggers listed first.
HSB Protection Switchover Triggers
Priority Fault Notes

0 No mate Caused by the absence of a mate unit or
communication cable.
1 Lockout Protection is locked by the user, and switching will
not take place under any circumstances. A lockout
does not persist after a hardware reset.
2 Force Switch A forced switchover is initiated by the user. This
overrides all other triggers except Lockout and No
Mate. A Forced Switch does not persist after a
hardware reset.
3 LOF/LOP Caused by radio loss of frame (LOF) or loss of
preamble (LOP).
4 Hardware Failure/Ethernet LOC/Remote Caused by hardware failure or Ethernet loss of
Ethernet Fault carrier (LOC) in the local, active unit, or an Ethernet
fault in the remote unit.
5 Change Remote due to "Radio LOF" Caused by radio loss of frame (LOF) in the remote,
active radio.
6 Local Radio Excessive BER Caused by an excessive BER level in the local,
active radio. The user can configure whether or not
excessive BER triggers switchover. Irrelevant in
ACM adaptive mode
7 Change Remote due to Radio Caused by an excessive BER level in the remote,
Excessive BER active radio. Irrelevant in ACM adaptive mode
8 Signal Degrade Caused by a signal degrade condition in the local,
active radio.
9 Change Remote due to Signal Degrade Caused by a signal degrade condition in the
remote, active radio.
10 Manual Switch The user initiates switchover. This type of
switchover has lower priority than the other user-
initiated switchovers (Lockout and Force Switch),
and is overridden by the switchover triggers listed
above.
11 Reserved
12 Clear (no request)

5.2.9 ATPC
ATPC is a closed-loop mechanism by which each carrier changes the
transmitted signal 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, transmit power is increased
as needed until the maximum is reached.
The ATPC mechanism has several potential advantages, including less
transmitter power consumption and longer amplifier component life, thereby
reducing overall system cost.
ATPC is frequently used as a means to mitigate frequency interference issues
with the environment, thus allowing new radio links to be easily coordinated
in frequency congested areas.
The Power Consumption Saving mode enables the system to adjust the power
automatically to reduce the power used, when possible.
5.2.9.1 ATPC Override Timer

Note: ATPC Override Timer is planned for future release.
Without ATPC, if loss of frame occurs the system automatically increases its
transmit power to the configured maximum. This may cause a higher level of
interference with other systems until the failure is corrected.
In order to minimize this interference, some regulators require a timer
mechanism which will be manually overridden when the failure is fixed. The
underlying principle is that the system should start a timer from the moment
maximum power has been reached. If the timer expires, ATPC is overridden
and the system transmits at a pre-determined power level until the user
manually re-establishes ATPC and the system works normally again.
The user can configure the following parameters:
 Override timeout (0 to disable the feature): The amount of time the timer
counts from the moment the system transmits at the maximum configured
power.
 Override transmission power: The power that will be transmitted if
ATPC is overridden because of timeout.
The user can also display the current countdown value.
When the system enters into the override state, ATPC is automatically
disabled and the system transmits at the pre-determined override power. An
alarm is raised in this situation.
The only way to go back to normal operation is to manually cancel the
override. When doing so, users should be sure that the problem has been
corrected; otherwise, ATPC may be overridden again.

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 and translation, 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.

 Ethernet Services Overview
 IP-20C s Ethernet Capabilities
 Supported Standards
 Ethernet Service Model
 Ethernet Interfaces
 Quality of Service (QoS)
 Global Switch Configuration
 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.
The following figure illustrates the basic MEF Ethernet services model.
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.

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

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.
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.
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.
Rooted Multipoint EVC
In the IP-20C, an EVC is defined by either a VLAN or by Layer 1 connectivity

(Pipe Mode).

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.
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.
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.
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 EVC) Ethernet Private Line (EPL) Ethernet Virtual Private Line (EVPL)
E-LAN (Multipoint-to- Ethernet Private LAN (EP-LAN) Ethernet Virtual Private LAN (EVP-
Multipoint EVC) LAN)
E-Tree (Rooted Multipoint Ethernet Private Tree (EP-Tree) Ethernet Virtual Private Tree (EVP-
EVC) Tree)
All-to-One Bundling refers to a UNI attribute in which all Customer Edge VLAN
IDs (CE-VLAN IDs) entering the service via the UNI are associated with a
single EVC. 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
 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.
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.
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.
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.
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.
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.
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.
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 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.
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.

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

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

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

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.
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.
Packet Service Core Building Blocks

Any Service
 Ethernet services (EVCs)
E-Line (Point-to-Point)
E-LAN (Multipoint)
E-Tree (Point-to-Multipoint)3
 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)
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/preservation/ translation)
 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)4
 Superb service OAM (CFM, EFM, PM)5
 Carrier-grade service resiliency (G.8032)6
3
E-Tree services are planned for future release.
4
H-QoS support is planned for future release.
5
CFM and EFM support is planned for future release.
6
G.8032 support is planned for future release.

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.80327
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:8
Multipoint (E-LAN)
Point-to-Point (E-Line)
Point-to-Multipoint (E-Tree)
Smart Pipe
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
7
G.8032 support is planned for future release.
8
Point-to-Multipoint service support is planned for future release.

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).
IP-20C Services Model
P2P
Service
SNP SNP
UNI
P2P
NNI
Service
SAP SAP
Multipoint SNP SNP Multipoint
SN
SA
SNP SNP Service Service
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
The IP-20C services core provides for fully flexible C-VLAN and S-VLAN
encapsulation, with a full range of classification, preservation, and translation
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.
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.
IP-20C Services Core
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 0 00 t
g= 1
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

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.
IP-20C Services Flow
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
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.
The following figure illustrates a P2P service.
Point-to-Point Service
P2P Service
Port 1 Port 4
SP SP
SAP
SAP
Port 2
P2P Service
SP
SAP SP
SAP
Port 3 Port 5
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
Multipoint Service
Port 1 SP SP Port 4
SAP SAP
SP
SAP
Port 2
SP SP
SAP
SAP
Port 3 Port 5
Multipoint services provide the building blocks for network services such as
E-LAN EVCs (EP-LAN and EVP-LAN EVCs), and for E-Line EVCs (EPL and EVPL
EVCs) in which only two service points are active. In such a case, the user can
disable MAC address learning in the service points to conserve system
resources.
Learning and Forwarding Mechanism

IP-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.
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 the dynamic entries from the MAC forwarding table.
The MAC forwarding table can be cleared on three levels:
 Global Switch Flush – All dynamic entries for all services are erased.
 Service Flush – All dynamic entries for a specific service are flushed.9
 Port Flush – All dynamic entries associated with a specific interface are
erased. 10
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.
9
This option is planned for future release.
10
This option is planned for future release.

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

 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 126.
 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.11
 Split Horizon Group (Enable/Disable) – Service points in the same split
horizon group cannot send frames among themselves. This enables
operators to isolate different traffic streams within a single service. This
parameter defines whether to enable or disable the split horizon
mechanism. IP-20C supports up to four different split horizon groups for
each service. On the service point level, users can define which service
point belongs to which group.12
11
Reserved for future use.
12
Reserved for future use.

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.
Management Service and its Service Points
MNG
MNG MNG
MNG
MNG
MNG MNG
MNG MNG
MNG MNG
MNG
 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.
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.
SAPs and SNPs
SAP
SNP SNP
SNP
SNP
SAP SAP
SNP SNP
SNP SNP
SAP
 Pipe Service Point – Used to create traffic connectivity between two

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

Pipe Service Points
Pipe Pipe Pipe Pipe
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.
SAP, SNP and Pipe Service Points in a Microwave Network
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

The following table summarizes the service point types available per service
type.
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 set of multiple S-VLANs 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.

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
 S-Tag – All S-VLANs and untagged frames that enter the interface are
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.
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.

Service Point Type-Attached Interface Type Combinations that can Co-Exist on the Same Interface
SP Type SAP SNP Pipe MNG
Attached Bundle Bundle
SP Type 802.1q All to One QinQ 802.1q S-Tag 802.1q S-Tag 802.1q QinQ S-Tag
Interface Type C-Tag S-Tag
Only for P2P
802.1q Yes Yes No No No No No No Yes No No
Service
Only for P2P
Bundle C-Tag Yes Yes No No No No No No Yes No No
Service
SAP
Bundle S-Tag No No Yes No Yes No No No No No Yes No
Only 1 All to One
All to One No No No No No No No No No No No
SP Per Interface
QinQ No No Yes No Yes No No No No No Yes No
Only for P2P
802.1q No No No No No Yes No No Yes No No
Service
SNP
Only for P2P
S-Tag No No No No No No Yes No No No Yes
Service
Only for P2P Only for P2P Only for P2P Only one Pipe SP
802.1q No No No No No Yes No No
Service Service Service Per Interface
Pipe
Only for P2P Only one Pipe SP
S-Tag No No No No No No No No No Yes
Service Per Interface
802.1q Yes Yes No No No Yes No Yes No No No No
MNG 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

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:
Service Path Relationship on Point-to-Point Service Path
SP1 SP2
Ingress Ingress
Port 1 Port 2
Egress Egress
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.
 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. 13
 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.14
 CoS Token Bucket Admin – Enables or disables the rate meter at the
service point CoS level.15
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.
13
14
15

 Marking – Marking refers to the ability to overwrite the outgoing priority

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

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 and Logical Interfaces
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
Note: For simplicity only, this figure represents a uni-directional

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

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.
Grouped Interfaces as a Single Logical Interface on Ingress Side
Physical Interface 1 SP Logical Interface Physical Interface 3

SP
terface
al In
LAG Logic
Physical Interface 2
SP SP Logical Interface Physical Interface 4

Service

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.
Grouped Interfaces as a Single Logical Interface on Egress Side
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

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 1000Mpbs 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.16
 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.
 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.
16
This functionality is planned for future release.

Ethernet Statistics (RMON)

The FibeAir IP-20C platform stores and displays statistics in accordance with
RMON and RMON2 standards.
The following transmit statistic counters are available:
 Transmitted bytes (not including preamble) in good or bad frames. Low 32
bits.
 Transmitted bytes (not including preamble) in good or bad frames. High
32 bits.
 Transmitted frames (good or bad)
 Multicast frames (good only)
 Broadcast frames (good only)
 Control frames transmitted
 Pause control frame transmitted
 FCS error frames
 Frame length error
 Oversized frames – frames with length > 1518 bytes (1522 bytes for VLAN-
tagged frames) without errors
 Undersized frames (good only)
 Fragments frames (undersized bad)
 Jabber frames – frames with length > 1518 bytes (1522 for VLAN-tagged
frames) with errors
 Frames with length 64 bytes, good or bad
 Frames with length 65-127 bytes, good or bad
 Frames with length 512-1023 bytes, good or bad.
The following receive statistic counters are available:
 Received bytes (not including preamble) in good or bad frames. Low 32 bits.
 Received bytes (not including preamble) in good or bad frames. High 32 bits.
 Received frames (good or bad)
 Multicast frames (good only)
 Broadcast frames (good only)
 Control frames received
 Pause control frame received
 FCS error frames
 Frame length error
 Code error
 Counts oversized frames – frames with length > 1518 bytes (1522 bytes
for VLAN-tagged frames) without errors and frames with length >
MAX_LEN without errors

 Undersized frames (good only)

 Fragments frames (undersized bad)
 Counts jabber frames – frames with length > 1518 bytes (1522 for VLAN-
tagged frames) with errors
 Frames with length 64 bytes, good or bad
 VLAN-tagged frames with length 1519-1522 bytes, good or bad
 Frames with length > MAX_LEN without errors
 Frames with length > MAX_LEN with errors
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.
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.
Relationship of Logical Interfaces to the Switching Fabric
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

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 to 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.
 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.
 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.
 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 127.
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
 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).
the rate meter (policer). The field length is 4 nibbles (for example, 0x0806
- ARP).
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.
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.17
 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.
17
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.

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 (RMON) on page 118, 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.
Link Aggregation Groups (LAG)

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

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.
Up to four LAG groups can be created.
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.
QoS Block Diagram
Egress
Ingress
Marker
Rate Limit (Optional)
GE/Radio Port Classifier
(Policing) Queue Scheduler/
Manager Shaper
Port GE/Radio
(Optional)
Standard QoS/ H-QoS
Egress
Ingress
Marker
Rate Limit (Optional)
Manager Shaper
Port GE/Radio
(Optional)
Standard QoS/ H-QoS
Egress
Ingress CET/Pipe Marker
Rate Limit Services (Optional)
Manager Shaper
Port GE/Radio
(Optional)
Standard QoS/ H-QoS
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.

The following figure illustrates the difference between how standard QoS and
H-QoS handle traffic:
Standard QoS and H-QoS Comparison
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
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

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.
Hierarchical Classification
 Preserve previous decision

Service point level
 Default CoS
Port Logical Interface
SAP SNP
SAP
 Default CoS
Service level
 VLAN ID
Logical interface level
 802.1p-based CoS  Preserve Service Point Decision

 DSCP-based CoS
 MPLS EXP-based CoS
 Default CoS
SAP SNP
SNP
SAP
Service
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.
DSCP bits.
MPLS EXP field.
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.
The following figure illustrates the hierarchy of priorities among classification
methods, from highest (on the left) to lowest (on the right) priority.
Classification Method Priorities
Highest
Priority
VLAN ID 802.1p DSCP MPLS EXP Default CoS
Lowest
Priority
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 120.
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.
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

802.1 UP CFI CoS (configurable) Color (configurable)

7 0 7 Green
7 1 7 Yellow
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
DSCP Default Mapping to CoS and Color
DSCP DSCP (bin) Description CoS (Configurable) Color (Configurable)

0 (default) 000000 BE (CS0) 0 Green
10 001010 AF11 1 Green
12 001100 AF12 1 Yellow
14 001110 AF13 1 Yellow
18 010010 AF21 2 Green
20 010100 AF22 2 Yellow
22 010110 AF23 2 Yellow
26 011010 AF31 3 Green
28 011100 AF32 3 Yellow
30 011110 AF33 3 Yellow

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

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
56 111000 CS7 7 Green
Default value is CoS equal best effort and Color equal Green.
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
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.

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 C)R/E)R+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 meter18
 Service point CoS-level rate meter19
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.
18
Service point-level rate metering is planned for future release.
19
Service point and CoS-level rate metering is planned for future release.

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
Ingress Policing Model
CoS 1
Service Frame
CoS 2 Ethertype
Point Type
CoS 3
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 2 to 128 Kbytes, with
a minimum granularity of 2 Kbytes.

 Excess Information Rate (EIR) – Frames within the defined EIR are
marked Yellow and processed according to network availability. Frames
beyond the combined CIR and EIR are marked Red and dropped by the
policer. Permitted values are 0 to 1 Gbps, with a minimum granularity of
32 Kbps.
 Excess Burst Size (EBS) – Frames within the defined EBS are marked
Yellow and processed according to network availability. Frames beyond
the combined CBS and EBS are marked Red and dropped by the policer.
Permitted values are 2 to 128 Kbytes, 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 119.
 Line Compensation – A rate meter can measure CIR and EIR at Layer 1 or
Layer 2 rates. Layer 1 capacity is equal to Layer 2 capacity plus 20
additional bytes for each frame due to the preamble and Inter Frame Gap
(IFG). In most cases, the preamble and IFG equals 20 bytes, but other
values are also possible. Line compensation defines the number of bytes to
be added to each frame for purposes of CIR and EIR calculation. When Line
Compensation is 20, the rate meter operates as Layer 1. When Line
Compensation is 0, the rate meter operates as Layer 2. This parameter is
very important to users that want to distinguish between Layer 1 and
Layer 2 traffic. For example, 1 Gbps of traffic at Layer 1 is equal to
~760 Mbps if the frame size is 64 bytes, but ~986 Mbps if the frame size is
1500 bytes. This demonstrates that counting at Layer 2 is not always fair
in comparison to counting at Layer 1, that is, the physical level.
Rate Metering (Policing) at the Logical Interface Level

Rate metering at the logical interface level supports the following:
 Unicast rate meter
 Multicast rate meter
 Broadcast rate mete
 User defined Ethertype 1 rate meter
For each rate meter, the following statistics are available:
 Green Frames (64 bits)

 Green Bytes (64 bits)

 Yellow Frames (64 bits)
 Yellow Bytes (64 bits)
 Red Frames (64 bits)
 Red Bytes (64 bits)
Rate Metering (Policing) at the Service Point Level

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

Users can define a single rate meter for each CoS on a specific service point, up
to a total number of 1024 rate meters per network element at the service
point and CoS per service point levels.
The following statistics are available for each service point + CoS rate meter:
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.
The following figure depicts the queue manager. Physically, the queue
manager is located between the ingress path and the egress path.
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.
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 136.
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.
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.
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 a pre-defined read-only WRED profile that defines a tail-
drop curve. This profile is assigned profile number 31, and is configured with
the following values:
 100% Yellow traffic drop after 16kbytes occupancy.
 100% Green traffic drop after 32kbytes occupancy.
 Yellow maximum drop is 100%
 Green maximum drop is 100%
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.
The following figure provides an example of a WRED profile.

WRED Profile Curve

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
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,
 Green-Maximum Drop – Permitted values are 1% to 100%, with 1% drop
granularity.
 Yellow Minimum Threshold – Permitted values are 0 Kbytes to 8 Mbytes,
 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.
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, users can assign the egress traffic to a
single service bundle (Service Bundle ID 1).
The service bundle level represents the groups of eight priority queues. Every
eight queues are managed as a single service bundle. There are a total number
of 32 service bundles for each logical interface.

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.
The following figure provides a detailed depiction of the H-QoS levels.

Detailed H-QoS Diagram
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
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.
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
Users can attach one of the configured queue shaper profiles to each priority
queue. If no profile is attached to the queue, no egress shaping is performed
on that queue.
Service Bundle Shapers

Users can configure up to 255 dual leaky bucket shaper profiles. The profiles
can be configured as follows:
 Valid CIR values are:
0 – 32,000,000 bps – granularity of 16,000 bps
32,000,000 – 1,000,000,000 bps – granularity of 64,000 bps
 Valid PIR values are:
16,000 – 32,000,000 bps – granularity of 16,000 bps
32,000,000 – 1,000,000,000 bps – granularity of 64,000 bps
Users can attach one of the configured service bundle shaper profiles to each
service bundle. If no profile is attached to the service bundle, no egress
shaping is performed on that service bundle.
Interface Shapers
Users can configure up to 31 single leaky bucket shaper profiles. The CIR can
be set to the following values:
 0 – 8,192,000 bps – granularity of 32,000 bps
 131,072,000 – 999,424,000 bps – granularity of 8,192,000 bps

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

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.
The following table provides a sample of an interface priority profile. This
profile is also used as the default interface priority profile.

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

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

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

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

The following table provides an example of a WFQ profile.
WFQ Profile Example
Profile ID (1-7)
CoS Queue Weight (Green) Queue Weight (Yellow – not visible to users)
0 20 20
1 20 20
2 20 20
3 20 20
4 20 20
5 20 20
6 20 20
7 20 20
For each CoS, the user can define;

 Profile ID – Profile ID number. Permitted values are 2 to 6.
 Weight – Transmission quota in bytes. Permitted values are 1 to 20.
Users can attach one of the configured interface WFQ profiles to each
interface. By default, the interface is assigned Profile ID 1, the pre-defined
system profile.
Egress 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)
Interface-Level Statistics
For information on statistics at the interface level, refer to Ethernet Statistics
(RMON) on page 118.

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.
802.1q UP Marking Table (C-VLAN)
CoS Color 802.1q UP (Configurable) CFI Color (Configurable)

0 Green 0 0
0 Yellow 0 1
1 Green 1 0
1 Yellow 1 1
2 Green 2 0
2 Yellow 2 1
3 Green 3 0
3 Yellow 3 1
4 Green 4 0
4 Yellow 4 1
5 Green 5 0
5 Yellow 5 1
6 Green 6 0
6 Yellow 6 1
7 Green 7 0
7 Yellow 7 1

802.1ad UP Marking Table (S-VLAN)
CoS Color 802.1ad UP (configurable) DEI Color (configurable)

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

Standard QoS and Hierarchical QoS (H-QoS) Summary

The following table summarizes and compares the capabilities of standard
QoS and H-QoS.
Summary and Comparison of Standard QoS and H-QoS
Capability Standard QoS Hierarchical QoS

Number of transmission queues 8 256
per port
Number of service bundles 1 (always service bundle id equal 1) 32
WRED Per queue (two curves – for green Per queue (two curves – for green traffic
traffic and for yellow traffic via the and for yellow traffic via the queue)
queue)
Shaping at queue level Single leaky bucket Single leaky bucket
Shaping at service bundle level Dual leaky bucket Dual leaky bucket
Shaping at port level Single leaky bucket (this level is not Single leaky bucket
relevant since it is recommended to
use service bundle level with dual
leaky bucket)
Transmission queues priority Per queue priority (4 priorities). Per queue priority (4 priorities). All 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
20
bundles)
Marker Supported Supported

Statistics Queue level (8 queues) Queue level (256 queues)
Service bundle level (1 service bundle) Service bundle level (32 service bundles)
Port level Port level
20
WFQ on the service bundle level is planned for future release.

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 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.8.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 (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.
G.8032 Ring in Idle (Normal) State
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
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.

G.8032 Ring in Protecting State
IP-20C
RPL
(Unblocked)
Ring Node 1
Signal
Failure

Ring Node 4
(RPL Owner)
IP-20C
Ring Node 2
IP-20C
Ring Node 3
R-APS Messages
Traffic
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.
Load Balancing Example in G.8032 Ring
IP-20C
RPL for
ERPI 1
Ring Node 1
RPL for
ERPI 2
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

5.3.8.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.
 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.
 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.9 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 802.1ag, G.8013/Y.1731, MEF-17, MEF-20,
MEF-30, and MEF-31.
IP-20C End-to-End Service Management
Carrier Ethernet services (EVCs)
BNC/RNC
Fiber
Aggregation
Network
IP-20C
IP-20C IP-20C
Tail site Aggregation site Fiber site
5.3.9.1 Connectivity Fault Management (CFM)

Note: CFM is planned for future release.
The IEEE 802.1ag and G.8013/Y.1731 standards and the MEF-17, MEF-20,
MEF-30, and MEF-31 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.
IEEE 802.1ag Ethernet CFM (Connectivity Fault Management) consists of
three protocols that operate together to aid in fault management:
 Continuity check
 Link trace
 Loopback.
FibeAir IP-20C utilizes these protocols to maintain smooth system operation
and non-stop data flow.
The following are the basic building blocks of CFM:
 Maintenance domains, their constituent maintenance points, and the
managed objects required to create and administer them.

SOAM Maintenance Entities (Example)
 Protocols and procedures used by maintenance points to maintain and

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

5.3.9.2 Ethernet in the First Mile (EFM)

Note: EFM is planned for future release.
Operations, Administration and Maintenance (OAM) was originally developed
to increase the reliability and simplify the maintenance of TDM and
SONET/SDH networks. However, since Ethernet is now becoming the most
common and preferred broadband access technology, the challenge to carriers
is to maintain and debug Ethernet networks with the same effectiveness as the
traditional TDM and SONET/SDH networks. 802.3ah OAM, also known as Link
OAM, was developed to meet this challenge and to overcome the limitations of
traditional management protocols such as SNMP (which always assumes that
devices are IP-accessible and cannot function when the network is non-
operational) by detecting problems in Ethernet access links in the First Mile
(EFM), thereby addressing all EFM requirements.
From the operator s point of view, Link OAM helps to establish and maintain
networks that are more resilient and more profitable. This is because the
802.3ah protocol minimizes OPEX, first by reducing maintenance costs, and
second by maximizing profits through the optimization and documentation of
network performance, enabling operators to maintain strict SLAs with
customers. In addition 802.3ah enables operators to gain new revenue by
servicing a growing market for carrier-class EFM.
Link OAM offers visibility into the Ethernet links between adjacent NEs. The
following Link OAM capabilities enable operators to eliminate truck rolls and
benefit from OPEX savings:
 Discovery – The ability for OAM-enabled devices to discover each other
and notify each other of their capabilities.
 Link Monitoring – The ability to monitor link attributes and status
information such as errors and events (symbols, frames).
 Remote Fault Detection – The ability to detect and handle link failure,
and the ability for OAM-enabled devices to convey failure condition
information to their peers.
 Remote Loopback – The ability to test segments and links by sending test
pattern frames through them and validate connectivity.
 MIB Variable Retrieval – The ability to retrieve information from a
management information base (MIB).
EFM Maintenance Entities (Example)
Customer Provider Provider Customer
Bridge A Bridge A Bridge B Bridge B
Domain
Level
Customer Level 7 +
Provider Level
Link OAM Link OAM

0 -
Customer Level MEP Provider Level MEP
Customer Level MIP Provider Level MIP

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 GE.
 SyncE PRC Pipe Regenerator mode, providing PRC grade (G.811)
performance for pipe regenerator applications.

 IP-20C Synchronization Solution
 Available Synchronization Interfaces
 Synchronous Ethernet (SyncE)
 IEEE-1588 Transparent Clock
 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.
 SyncE PRC Pipe Regenerator mode21
PRC grade G. performance for pipe regenerator applications
 SyncE node22
 PTP optimized transport

Supports a variety of protocols, such as IEEE-1588 and NTP
Guaranteed ultra-low PDV (<0.015 ms per hop)
Unique support for ACM and narrow channels
 PTP
Supports IEEE-1588 Transparent Clock23
21
SyncE PRC Pipe Regenerator mode is planned for future release.
22
SyncE node is planned for future release.
23
IEEE-1588 Transparent Clock is planned for future release.

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.
Synchronization Interface Options
Available interfaces as frequency Available interfaces as frequency

input (reference sync source) output
 Radio carrier  Radio carrier
 GE Ethernet interfaces  GE 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

Note: SyncE PRC Pipe Regenerator Mode is planned for future
release.
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.
5.4.4 IEEE-1588 Transparent Clock

Note: IEEE-1588 Transparent Clock is planned for future release.
IP-20C supports PTP optimized transport, a message-based protocol that can
be implemented across packet-based networks. To ensure minimal packet
delay variation (PDV), IP-20C s synchronization solution includes 1588v2-
compliant Transparent Clock. Transparent Clock provides the means to
measure and adjust for delay variation, thereby ensuring low PDV.
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.
 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.
IP-20C uses 1588v2-compliant Transparent Clock to counter the effects of
delay variation. Transparent Clock measures and adjusts for delay variation,
enabling the IP-20C to guarantee ultra-low PDV.
Transparent Clock has been added to version 2 of the 1588 standard as an
improved method of forming cascaded topologies. Rather than acting as a
multi-port ordinary clock, which is what boundary clocks do, IP-20C
transparent clocks update the newly introduced time-interval correction field
in PTP event messages. This 64-bit field enables switch delay compensation to
a potential accuracy of less than a picosecond.
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 time-interval
correction field.

IP-20C supports End-to-End Transparent Clock, which updates the time-

interval correction field for the delay associated with individual packet
transfers. End-to-End Transparent Clock is the most appropriate option for
the Telecom industry.
As shown in the figure below, IP-20C measures and updates PTP messages
based on both the radio link delay variation, and the packet processing delay
variation that results from the network processor (switch operation).
Transparent Clock Delay Compensation
Radio Link
Delay Variation = ∆x
Correction Time
∆x +2∆y
1588
1588
Slave
Master
Packet Processing Packet Processing

Delay Variation = ∆y Delay Variation = ∆y
5.4.5 SSM Support and Loop Prevention

Note: SSM support is planned for future release.
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.
 )n 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)

6. FibeAir IP-20C Management

 Management Overview
 Management Communication Channels and Protocols
 Web-Based Element Management System (Web EMS)
 Command Line Interface (CLI)
 Configuration Management
 Software Management
 In-Band Management
 Local Management
 Alarms
 NTP Support
 UTC Support
 System Security Features

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.24
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.
Integrated IP-20C Management Tools
24
SNMP v3 support is planned for future release.

6.2 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.
Dedicated Management Ports
Port number Protocol Frame structure Details

161 SNMP UDP Sends SNMP Requests to the network elements
162 Configurable SNMP (traps) UDP Sends SNMP traps forwarding (optional)
25 SMTP (mail) TCP Sends the NMS reports and triggers by email
(optional)
69 TFTP UDP Uploads/ downloads configuration files (optional)
80 HTTP TCP Manages devices
443 HTTPS TCP Manages devices (optional)
From 21 port to any FTP Control Port TCP Downloads software and configuration files.
remote port (>1023) (FTP Server responds to client's control port)
(optional)
From Any port FTP Data Port TCP Downloads software and configuration files.
(>1023) to any The FTP server sends ACKs (and data) to
remote port (>1023) client's data port.
Optional
FTP server random port range can be limited
according to need (i.e., according to the number
of parallel configuration uploads).
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
 The NMS uses a number of ports and protocols for different functions:

NMS Server Receiving Data Ports

162 SNMP (traps) UDP Receive SNMP traps from network
Configurable elements
4001 Propriety TCP CeraMap Server

Configurable
69 TFTP UDP Downloads software and files (optional)
21 FTP Control TCP Downloads software and configuration
Port files. (FTP client initiates a connection)
(optional)
To any port (>1023) from any FTP Data Port TCP Downloads software and configuration
Port (>1023) files.(FTP Client initiates data connection
to random port specified by server)
(optional)
FTP Server random port range can be
limited according to needed configuration
(number of parallel configuration uploads).
9205 Propriety TCP User Actions Logger server (optional)
Configurable
9207 Propriety TCP CeraView Proxy (optional)
Configurable
Web Sending Data Ports

80 HTTP TCP Manages device
443 HTTPS TCP Manages device (optional)
Web Receiving Data Ports

21 FTP TCP Downloads software files (optional)
Data port FTP TCP Downloads software files (optional)
Additional Management Ports for IP-20C

23 telnet TCP Remote CLI access (optional)
22 SSH TCP Secure remote CLI access (optional)

6.3 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.
The Web EMS shows the actual unit configuration and provides easy access to
any interface on the unit.

6.4 Command Line Interface (CLI)

A CLI connection to the IP-20C can be opened via telnet. All parameter
configurations can be performed via CLI.
6.5 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.25
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: )n 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.
25
The option to edit the backup configuration is planned for future release.

6.6 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.
Note: Only FTP downloads are supported in Release 7.0.
After the software download is complete, the user initiates the installation. A
timer can be used to perform the installation after a defined time interval.
When an installation timer is used, the system performs an automatic reset
after the installation.26
After a software upgrade, the system automatically detects whether it is
necessary to perform a full reset, a software reset, or a limited software
component restart. This assures the minimum possible disturbance to
continuous operation.
6.6.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.
26
Installation timer is planned for future release.

6.7 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 104.
6.8 Local Management

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

6.9 Alarms
6.9.1 Configurable RSL Threshold for Alarms and Traps

Users can configure alarm and trap generation in the event of RSL degradation
beneath a user-defined threshold. An alarm and trap are generated if the RSL
remains below the defined threshold for at least five seconds. The alarm is
automatically cleared if the RSL subsequently remains above the threshold for
at least five seconds.
The RSL threshold is based on the nominal RSL value minus the RSL
degradation margin. The user defines both the nominal RSL value and the RSL
degradation margin.
6.9.2 Alarms Editing

Users can change the description text (by appending extra text to the existing
description) or the severity of any alarm in the system. This feature is
available through CLI only.
This is performed as follows:
 Each alarm 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
 The user can also return all alarms and events to their default values.
6.10 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.11 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.12 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.12.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.
Security Solution Architecture Concept

6.12.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 27
 (TTPS for access to the NE s web server
 SSH-2 for all CLI access SFTP for all software and configuration download
between NMS and NEs
All protocols run with secure settings using strong encryption techniques.
Unencrypted modes are not allowed, and algorithms used must meet modern
and client standards.
Users are allowed to disable all insecure channels.
In the network elements, the bandwidth of physical channels transporting
management communications is limited to the appropriate magnitude, in
particular, channels carrying management frames to the CPU.
Attack types addressed
 Tempering with management flows
 Management traffic analysis
 Unauthorized software installation
 Attacks on protocols (by providing secrecy and integrity to messages)
 Traffic interfaces eavesdropping (by making it harder to change
configuration)
 DoS through flooding
27
Support for SNMPv3 is planned for future release.

6.12.3 Defenses in User and System Authentication Procedures
6.12.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 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.
6.12.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.28 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.
28
Password strength enforcement is planned for future release.

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.12.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.12.3.4 RADIUS Support

Note: RADIUS support is planned for future release.
The RADIUS protocol provides centralized user management services. IP-20C
supports RADIUS server and provides a RADIUS client for authentication and
authorization.
When RADIUS is enabled, a user attempting to log into the system from any of
the management channels (CLI, WEB, SNMP) is not authenticated locally but
rather, his or her 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 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 )ANA number for this field is .
The following RADIUS servers are supported:
 FreeRADIUS
 RADIUS on Windows Server (IAS)
Windows Server 2008
Windows Server 2003
 Cisco ACS
6.12.4 Secure Communication Channels

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

Note: SSH support is planned for future release.
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.
 Supported Encryptions: aes128-cbc, 3des-cbc, blowfish-cbc, cast128-cbc,
arcfour128, arcfour256, arcfour, aes192-cbc, aes256-cbc, aes128-ctr,
aes192-ctr, aes256-ctr.
 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.
6.12.4.2 HTTPS (Hypertext Transfer Protocol Secure)

Note: HTTPS support is planned for future release.
HTTPS combines the Hypertext Transfer protocol with the SSL/TLS protocol
to provide encrypted communication and secure identification of a network
web server. IP-20C enables administrators to configure secure access via
HTTPS protocol.

6.12.4.3 SFTP (Secure FTP)

Note: SFTP support is planned for future release.
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.12.4.4 Creation of Certificate Signing Request (CSR) File

Note: CSR support is planned for future release.
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.
6.12.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.
Note: SNMP v3 support is planned for future release.

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

 FibeAir IP-20C MIB Reference, DOC- 00036524.
6.12.4.6 Server Authentication (SSL / SLLv3)

Note: SSL and SLLv3 support is planned for future release.
 All protocols making use of SSL (such as HTTPS) use SLLv3 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.12.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.12.4.8 SSH
Note: SSH support is planned for future release.
 The CLI interface supports SSH-2
Users of type of administrator or above can enable or disable SS(.
29
SNMP v3 support is planned for future release.

6.12.5 Security Log

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

System clock change

NTP enable/disable
 Security events
 Successful and unsuccessful login attempts
 N consecutive unsuccessful login attempts (blocking)
 Configuration change failure due to insufficient permissions
 SNMPv3/PV authentication failures
 User logout
 User account expired
For each recorded event the following information is available:
 User ID
 Communication channel (WEB, terminal, telnet/SSH, SNMP, NMS, etc.)
 IP address, if applicable
 Date and time

7. Standards and Certifications

 Supported Ethernet Standards
 MEF Certifications for Ethernet Services

7.1 Supported Ethernet Standards

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
7.2 MEF Certifications for Ethernet Services

Certification Description
MEF-9 Abstract Test Suite for Ethernet Services at the UNI.
Certified for all service types (EPL, EVPL & E-LAN).
MEF-14 Abstract Test Suite for Traffic Management Phase 1.
Certified for all service types (EPL, EVPL & E-LAN).

8. Specifications
 General Radio Specifications
 Frequency Accuracy
 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.

8.1 General Radio Specifications
8.1.1 6-15 GHz

Specification 6L,6H GHz 7,8 GHz 10 GHz 11 GHz 13 GHz 15 GHz
Standards EN 302 217
Operating Frequency Range 5.85-6.45, 6.4-
7.1-7.9, 7.7-8.5 10.0-10.7 10.7-11.7 12.75-13.3 14.4-15.35
(GHz) 7.1
252.04, 240, 154, 119, 161, 168, 182, 91, 315, 420,
490, 520,
Tx/Rx Spacing (MHz) 266, 300, 340, 196, 208, 245, 250, 266, 168,350, 266 475, 644,
530
160, 170, 500 300,310, 311.32, 500, 530 550 490, 728
Frequency Source Synthesizer
RF Channel Selection Via EMS/NMS
MultiCore 2+0 Single/Dual Polarization, MultiCore 2+2 SP/DP HSB, 2 x MultiCore 2+0 SP/DP
System Configurations
LoS 4x4 MIMO, LoS 2x2 MIMO
Tx Range (Manual/ATPC) Up to 25dB dynamic range
8.1.2 18-42 GHz

Specification 18 GHz 23 GHz 24UL GHz 26 GHz 28 GHz 32 GHz 38 GHz 42 GHz
Standards EN 302 217
Operating Frequency
17.7-19.7 21.2-23.65 24.0-24.25 24.2-26.5 27.35-29.5 31.8-33.4 37-40 40.55-43.45
Range (GHz)
1010, 1120, 1008, 1200, Customer- 350, 450, 490, 1000,
Tx/Rx Spacing (MHz) 800, 1008 812 1500
1008, 1560 1232 defined 1008 1260, 700
Frequency Source Synthesizer
RF Channel Selection Via EMS/NMS
System MultiCore 2+0 Single/Dual Polarization, MultiCore 2+2 SP/DP HSB, 2 x MultiCore 2+0 SP/DP
Configurations LoS 4x4 MIMO, LoS 2x2 MIMO
Tx Range Up to 25dB dynamic range
(Manual/ATPC)
8.2 Frequency Accuracy

IP-20C provides frequency accuracy of ±4 ppm30.
30
Over temperature.

8.3 Radio Capacity Specifications

Each table in this section includes ranges of capacity specifications according
to frame size, with ranges given for no Header De-Duplication, Layer-2 Header
De-Duplication, and LTE-optimized Header De-Duplication (per core).
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. A
Capacity Calculator tool is available for different
encapsulations and flow types.
ACAP and ACCP represent compliance with different ETSI
mask requirements. ACCP represents compliance with more
stringent interference requirements.
The total capacity (including Header De-Duplication) of an
IP-20C unit is double the figures in the tables below. It
should be noted that there are two IP-20C models, with a
different limitation of the top capacity per terminal (unit).
An IP-20C model that supports 80 MHz channels will
support a total capacity of 1.3 Gbps (per terminal), whereas
other models support 1 Gbps.
8.3.1 28 MHz Channel Bandwidth (ACCP)

Profile Modulation Minimum Ethernet Throughput
required
capacity No L2 Header De-
license Compression Compression Duplication
0 QPSK 50 40-49 40-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-611
6 256 QAM 200 183-224 184-270 192-696
7 512 QAM 200 202-247 203-298 212-768
8 1024 QAM (Strong FEC) 225 215-262 216-317 225-817
9 1024 QAM (Light FEC) 225 228-279 230-337 239-867
10 2048 QAM 250 244-299 246-361 257-931

8.3.2 28 MHz Channel Bandwidth (ACAP)

required
0 QPSK 50 43-52 43-63 45-162
1 8 PSK 50 62-76 62-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 FEC) 225 228-278 229-336 239-866
9 1024 QAM (Light FEC) 250 241-295 243-356 253-917
10 2048 QAM 250 263-321 265-389 276-1000

required
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-301 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


required
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 272-400 284-1000
5 128 QAM 300 327-400 329-483 343-1000
6 256 QAM 400 374-457 377-552 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-692 492-1000
10 2048 QAM 500 508-621 512-751 534-1000
8.3.5 56 MHz Channel Bandwidth (ACAP)

required
0 QPSK 100 87-106 88-128 91-331
1 8 PSK 100 127-155 128-187 133-482
2 16 QAM 200 176-215 177-260 185-670
3 32 QAM 250 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

8.3.6 80 MHz Channel Bandwidth

required
0 QPSK 100 114-140 115-169 120-435
1 8 PSK 150 162-198 163-240 170-617
2 16 QAM 250 230-283 233-342 243-880
3 32 QAM 300 302-371 306-449 319-1000
4 64 QAM 400 369-454 374-549 390-1000
5 128 QAM 450 435-536 442-649 461-1000
6 256 QAM 500 501-618 509-747 531-1000
7 512 QAM 500 551-679 560-821 583-1000
8 1024 QAM 650 599-738 609-892 634-1000
Note: Support for 80 MHz channels is planned for future release.

8.4 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.
IP-20C Standard Power
Modulation 6 GHz 7 GHz 8 GHz 10-11 GHz 13-15 GHz 18 GHz 23 GHz 24GHz UL31 26 GHz 28,32,38 GHz 42 GHz
QPSK 26 25 25 24 24 22 20 0 21 18 15
8 PSK 26 25 25 24 24 22 20 0 21 18 15
16 QAM 25 24 24 23 23 21 20 0 20 17 14
32 QAM 24 23 23 22 22 20 20 0 19 16 13
64 QAM 24 23 23 22 22 20 20 0 19 16 13
128 QAM 24 23 23 22 22 20 20 0 19 16 13
256 QAM 24 23 21 22 22 20 20 0 19 16 13
512 QAM 22 21 21 21 20 18 18 0 17 14 11
1024 QAM 22 21 21 20 20 18 18 0 17 14 11
2048 QAM 20 19 19 18 18 16 16 0 15 12 9
31
For 1ft ant or lower.
Customers in countries following EC Directive 2006/771/EC (incl. amendments) must observe
the 100mW EIRP obligation by adjusting transmit power according to antenna gain and RF line
losses.

IP-20C High Power
Modulation 6 GHz 7 GHz 8 GHz 10-11 GHz
QPSK 29 28 28 27
8 PSK 29 28 28 27
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

8.5 Receiver Threshold Specifications

Note: The values listed in this section are typical. Tolerance range is -1dB/+ 2dB.
Channel Frequency (GHz)
Profile Modulation
Spacing
6 7 8 10 11 13 15 18 23 2432 26 28-31 32 36 38 42
0 QPSK -87.0 -85.5 -85.0 -85.5 -86.5 -86.0 -85.0 -86.0 -84.5 -84.0 -84.0 -84.5 -85.5 -83.0 -82.5 -82.0
1 8 PSK -82.5 -81.0 -80.5 -81.0 -82.0 -81.5 -80.5 -81.5 -80.0 -79.5 -79.5 -80.0 -81.0 -78.5 -78.0 -77.5
2 16 QAM -80.5 -79.0 -78.5 -79.0 -80.0 -79.5 -78.5 -79.5 -78.0 -77.5 -77.5 -78.0 -79.0 -76.5 -76.0 -75.5
3 32 QAM -77.0 -75.5 -75.0 -75.5 -76.5 -76.0 -75.0 -76.0 -74.5 -74.0 -74.0 -74.5 -75.5 -73.0 -72.5 -72.0
4 64 QAM -74.0 -72.5 -72.0 -72.5 -73.5 -73.0 -72.0 -73.0 -71.5 -71.0 -71.0 -71.5 -72.5 -70.0 -69.5 -69.0
28 MHz
5 128 QAM -71.0 -69.5 -69.0 -69.5 -70.5 -70.0 -69.0 -70.0 -68.5 -68.0 -68.0 -68.5 -69.5 -67.0 -66.5 -66.0
ACCP
6 256 QAM -68.0 -66.5 -66.0 -66.5 -67.5 -67.0 -66.0 -67.0 -65.5 -65.0 -65.0 -65.5 -66.5 -64.0 -63.5 -63.0
7 512 QAM -65.5 -64.0 -63.5 -64.0 -65.0 -64.5 -63.5 -64.5 -63.0 -62.5 -62.5 -63.0 -64.0 -61.5 -61.0 -60.5
8 1024 QAM (strong FEC) -62.5 -61.0 -60.5 -61.0 -62.0 -61.5 -60.5 -61.5 -60.0 -59.5 -59.5 -60.0 -61.0 -58.5 -58.0 -57.5
9 1024 QAM (light FEC) -61.5 -60.0 -59.5 -60.0 -61.0 -60.5 -59.5 -60.5 -59.0 -58.5 -58.5 -59.0 -60.0 -57.5 -57.0 -56.5
10 2048 QAM -58.0 -56.5 -56.0 -56.5 -57.5 -57.0 -56.0 -57.0 -55.5 -55.0 -55.0 -55.5 -56.5 -54.0 -53.5 -53.0
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.


Profile Modulation
Spacing
6 7 8 10 11 13 15 18 23 2432 26 28-31 32 36 38 42
0 QPSK -87.5 -85.5 -85.0 -85.5 -87.0 -86.0 -85.0 -86.0 -84.5 -84.0 -84.0 -84.5 -85.5 -83.0 -82.5 -82.0
1 8 PSK -82.5 -80.5 -80.0 -80.5 -82.0 -81.0 -80.0 -81.0 -79.5 -79.0 -79.0 -79.5 -80.5 -78.0 -77.5 -77.0
2 16 QAM -81.0 -79.0 -78.5 -79.0 -80.5 -79.5 -78.5 -79.5 -78.0 -77.5 -77.5 -78.0 -79.0 -76.5 -76.0 -75.5
3 32 QAM -77.5 -75.0 -74.5 -75.0 -77.0 -75.5 -74.5 -75.5 -74.0 -73.5 -73.5 -74.0 -75.0 -72.5 -72.0 -71.5
4 64 QAM -74.5 -72.5 -72.0 -72.5 -74.0 -73.0 -72.0 -73.0 -71.5 -71.0 -71.0 -71.5 -72.5 -70.0 -69.5 -69.0
28 MHz
5 128 QAM -71.5 -69.0 -68.5 -69.0 -71.0 -69.5 -68.5 -69.5 -68.0 -67.5 -67.5 -68.0 -69.0 -66.5 -66.0 -65.5
ACAP
6 256 QAM -68.5 -66.0 -65.5 -66.0 -68.0 -66.5 -65.5 -66.5 -65.0 -64.5 -64.5 -65.0 -66.0 -63.5 -63.0 -62.5
7 512 QAM -66.5 -64.0 -63.5 -64.0 -66.0 -64.5 -63.5 -64.5 -63.0 -62.5 -62.5 -63.0 -64.0 -61.5 -61.0 -60.5
8 1024 QAM (strong FEC) -63.5 -61.0 -60.5 -61.0 -63.0 -61.5 -60.5 -61.5 -60.0 -59.5 -59.5 -60.0 -61.0 -58.5 -58.0 -57.5
9 1024 QAM (light FEC) -62.5 -60.0 -59.5 -60.0 -62.0 -60.5 -59.5 -60.5 -59.0 -58.5 -58.5 -59.0 -60.0 -57.5 -57.0 -56.5
10 2048 QAM -58.5 -56.0 -55.5 -56.0 -58.0 -56.5 -55.5 -56.5 -55.0 -54.5 -54.5 -55.0 -56.0 -53.5 -53.0 -52.5


Profile Modulation
Spacing
6 7 8 10 11 13 15 18 23 2432 26 28-31 32 36 38 42
0 QPSK -85.5 -84.0 -83.5 -84.0 -86.0 -84.5 -83.5 -84.5 -83.0 -82.5 -82.5 -83.0 -84.0 -81.5 -81.0 -80.5
1 8 PSK -80.5 -79.0 -78.5 -79.0 -80.5 -79.5 -78.5 -79.5 -78.0 -77.5 -77.5 -78.0 -79.0 -76.5 -76.0 -75.5
2 16 QAM -79.0 -77.5 -77.0 -77.5 -79.0 -78.0 -77.0 -78.0 -76.5 -76.0 -76.0 -76.5 -77.5 -75.0 -74.5 -74.0
3 32 QAM -75.5 -74.0 -73.5 -74.0 -75.5 -74.5 -73.5 -74.5 -73.0 -72.5 -72.5 -73.0 -74.0 -71.5 -71.0 -70.5
4 64 QAM -72.5 -71.0 -70.5 -71.0 -72.5 -71.5 -70.5 -71.5 -70.0 -69.5 -69.5 -70.0 -71.0 -68.5 -68.0 -67.5
5 128 QAM 40 MHz -69.5 -68.0 -67.5 -68.0 -70.0 -68.5 -67.5 -68.5 -67.0 -66.5 -66.5 -67.0 -68.0 -65.5 -65.0 -64.5
6 256 QAM -66.5 -65.0 -64.5 -65.0 -67.5 -65.5 -64.5 -65.5 -64.0 -63.5 -63.5 -64.0 -65.0 -62.5 -62.0 -61.5
7 512 QAM -63.5 -62.0 -61.5 -62.0 -65.0 -62.5 -61.5 -62.5 -61.0 -60.5 -60.5 -61.0 -62.0 -59.5 -59.0 -58.5
8 1024 QAM (strong FEC) -61.0 -59.5 -59.0 -59.5 -61.5 -60.0 -59.0 -60.0 -58.5 -58.0 -58.0 -58.5 -59.5 -57.0 -56.5 -56.0
9 1024 QAM (light FEC) -60.0 -58.5 -58.0 -58.5 -60.5 -59.0 -58.0 -59.0 -57.5 -57.0 -57.0 -57.5 -58.5 -56.0 -55.5 -55.0
10 2048 QAM -57.5 -56.0 -55.5 -56.0 -57.5 -56.5 -55.5 -56.5 -55.0 -54.5 -54.5 -55.0 -56.0 -53.5 -53.0 -52.5


Profile Modulation
Spacing
6 7 8 10 11 13 15 18 23 2432 26 28-31 32 36 38 42
0 QPSK -83.5 -82.0 -81.5 -82.0 -83.0 -82.5 -81.5 -82.5 -81.0 -80.5 -80.5 -81.0 -82.0 -79.5 -79.0 -78.5
1 8 PSK -79.5 -78.0 -77.5 -78.0 -79.0 -78.5 -77.5 -78.5 -77.0 -76.5 -76.5 -77.0 -78.0 -75.5 -75.0 -74.5
2 16 QAM -77.0 -75.5 -75.0 -75.5 -76.5 -76.0 -75.0 -76.0 -74.5 -74.0 -74.0 -74.5 -75.5 -73.0 -72.5 -72.0
3 32 QAM -74.0 -72.5 -72.0 -72.5 -73.5 -73.0 -72.0 -73.0 -71.5 -71.0 -71.0 -71.5 -72.5 -70.0 -69.5 -69.0
4 64 QAM -70.5 -69.0 -68.5 -69.0 -70.0 -69.5 -68.5 -69.5 -68.0 -67.5 -67.5 -68.0 -69.0 -66.5 -66.0 -65.5
56 MHz
5 128 QAM -68.0 -66.5 -66.0 -66.5 -67.5 -67.0 -66.0 -67.0 -65.5 -65.0 -65.0 -65.5 -66.5 -64.0 -63.5 -63.0
ACCP
6 256 QAM -64.5 -63.0 -62.5 -63.0 -64.0 -63.5 -62.5 -63.5 -62.0 -61.5 -61.5 -62.0 -63.0 -60.5 -60.0 -59.5
7 512 QAM -62.5 -61.0 -60.5 -61.0 -62.0 -61.5 -60.5 -61.5 -60.0 -59.5 -59.5 -60.0 -61.0 -58.5 -58.0 -57.5
8 1024 QAM (strong FEC) -59.0 -57.5 -57.0 -57.5 -58.5 -58.0 -57.0 -58.0 -56.5 -56.0 -56.0 -56.5 -57.5 -55.0 -54.5 -54.0
9 1024 QAM (light FEC) -58.0 -56.5 -56.0 -56.5 -57.5 -57.0 -56.0 -57.0 -55.5 -55.0 -55.0 -55.5 -56.5 -54.0 -53.5 -53.0
10 2048 QAM -53.5 -52.0 -51.5 -52.0 -53.0 -52.5 -51.5 -52.5 -51.0 -50.5 -50.5 -51.0 -52.0 -49.5 -49.0 -48.5


Profile Modulation
Spacing
6 7 8 10 11 13 15 18 23 2432 26 28-31 32 36 38 42
0 QPSK -84.5 -82.5 -82.0 -82.5 -83.5 -83.0 -82.0 -83.0 -81.5 -81.0 -81.0 -81.5 -82.5 -80.0 -79.5 -79.0
1 8 PSK -80.0 -78.0 -77.5 -78.0 -79.0 -78.5 -77.5 -78.5 -77.0 -76.5 -76.5 -77.0 -78.0 -75.5 -75.0 -74.5
2 16 QAM -77.5 -75.5 -75.0 -75.5 -76.5 -76.0 -75.0 -76.0 -74.5 -74.0 -74.0 -74.5 -75.5 -73.0 -72.5 -72.0
3 32 QAM -74.0 -72.0 -71.5 -72.0 -73.0 -72.5 -71.5 -72.5 -71.0 -70.5 -70.5 -71.0 -72.0 -69.5 -69.0 -68.5
4 64 QAM -71.0 -68.5 -68.0 -68.5 -69.5 -69.0 -68.0 -69.0 -67.5 -67.0 -67.0 -67.5 -68.5 -66.0 -65.5 -65.0
56 MHz
5 128 QAM -68.5 -66.0 -65.5 -66.0 -67.0 -66.5 -65.5 -66.5 -65.0 -64.5 -64.5 -65.0 -66.0 -63.5 -63.0 -62.5
ACAP
6 256 QAM -65.0 -62.5 -62.0 -62.5 -63.5 -63.0 -62.0 -63.0 -61.5 -61.0 -61.0 -61.5 -62.5 -60.0 -59.5 -59.0
7 512 QAM -63.0 -60.5 -60.0 -60.5 -61.5 -61.0 -60.0 -61.0 -59.5 -59.0 -59.0 -59.5 -60.5 -58.0 -57.5 -57.0
8 1024 QAM (strong FEC) -59.5 -57.0 -56.5 -57.0 -58.0 -57.5 -56.5 -57.5 -56.0 -55.5 -55.5 -56.0 -57.0 -54.5 -54.0 -53.5
9 1024 QAM (light FEC) -58.5 -56.0 -55.5 -56.0 -57.0 -56.5 -55.5 -56.5 -55.0 -54.5 -54.5 -55.0 -56.0 -53.5 -53.0 -52.5
10 2048 QAM -56.0 -53.5 -53.0 -53.5 -54.5 -54.0 -53.0 -54.0 -52.5 -52.0 -52.0 -52.5 -53.5 -51.0 -50.5 -50.0


Profile Modulation
Spacing
6 7 8 10 11 13 15 18 23 2432 26 28-31 32 36 38 42
0 QPSK -83.0 -81.5 -81.0 -81.5 -82.5 -82.0 -81.0 -82.0 -80.5 -77.0 -80.0 -80.5 -81.5 -79.0 -78.5 -78.0
1 8 PSK -78.0 -76.5 -76.0 -76.5 -77.5 -77.0 -76.0 -77.0 -75.5 -72.0 -75.0 -75.5 -76.5 -74.0 -73.5 -73.0
2 16 QAM -76.0 -74.5 -74.0 -74.5 -75.5 -75.0 -74.0 -75.0 -73.5 -70.0 -73.0 -73.5 -74.5 -72.0 -71.5 -71.0
3 32 QAM -72.5 -71.0 -70.5 -71.0 -72.0 -71.5 -70.5 -71.5 -70.0 -66.5 -69.5 -70.0 -71.0 -68.5 -68.0 -67.5
4 64 QAM 80 MHz -69.5 -68.0 -67.5 -68.0 -69.0 -68.5 -67.5 -68.5 -67.0 -63.5 -66.5 -67.0 -68.0 -65.5 -65.0 -64.5
5 128 QAM -67.0 -65.5 -65.0 -65.5 -66.5 -66.0 -65.0 -66.0 -64.5 -61.0 -64.0 -64.5 -65.5 -63.0 -62.5 -62.0
6 256 QAM -64.0 -62.5 -62.0 -62.5 -63.5 -63.0 -62.0 -63.0 -61.5 -58.0 -61.0 -61.5 -62.5 -60.0 -59.5 -59.0
7 512 QAM -61.0 -59.5 -59.0 -59.5 -60.5 -60.0 -59.0 -60.0 -58.5 -55.0 -58.0 -58.5 -59.5 -57.0 -56.5 -56.0
8 1024 QAM -58.5 -57.0 -56.5 -57.0 -58.0 -57.5 -56.5 -57.5 -56.0 -52.5 -55.5 -56.0 -57.0 -54.5 -54.0 -53.5
8.5.1 Overload Thresholds

 For modulations up to and including 1024 QAM (strong FEC): -20dBm
 For modulations of 1024 (light FEC) and 2048 QAM: -25dBm

8.6 Frequency Bands

Frequency Band TX Range RX Range Tx/Rx Spacing
6332.5-6393 5972-6093
300A
5972-6093 6332.5-6393
6191.5-6306.5 5925.5-6040.5
5925.5-6040.5 6191.5-6306.5
266A
6303.5-6418.5 6037.5-6152.5
6037.5-6152.5 6303.5-6418.5
6245-6290.5 5939.5-6030.5
5939.5-6030.5 6245-6290.5
260A
6365-6410.5 6059.5-6150.5
6059.5-6150.5 6365-6410.5
6226.89-6286.865 5914.875-6034.825
5914.875-6034.825 6226.89-6286.865
6L GHz 252B
6345.49-6405.465 6033.475-6153.425
6033.475-6153.425 6345.49-6405.465
6181.74-6301.69 5929.7-6049.65
5929.7-6049.65 6181.74-6301.69
6241.04-6360.99 5989-6108.95
252A
5989-6108.95 6241.04-6360.99
6300.34-6420.29 6048.3-6168.25
6048.3-6168.25 6300.34-6420.29
6235-6290.5 5939.5-6050.5
5939.5-6050.5 6235-6290.5
240A
6355-6410.5 6059.5-6170.5
6059.5-6170.5 6355-6410.5
6924.5-7075.5 6424.5-6575.5
500
6424.5-6575.5 6924.5-7075.5
7032.5-7091.5 6692.5-6751.5
340C
6H GHz 6692.5-6751.5 7032.5-7091.5
6764.5-6915.5 6424.5-6575.5
6424.5-6575.5 6764.5-6915.5 340B
6924.5-7075.5 6584.5-6735.5


6584.5-6735.5 6924.5-7075.5
6781-6939 6441-6599
6441-6599 6781-6939
340A
6941-7099 6601-6759
6601-6759 6941-7099
6707.5-6772.5 6537.5-6612.5
6537.5-6612.5 6707.5-6772.5
6767.5-6832.5 6607.5-6672.5
160A
6607.5-6672.5 6767.5-6832.5
6827.5-6872.5 6667.5-6712.5
6667.5-6712.5 6827.5-6872.5
7783.5-7898.5 7538.5-7653.5
7538.5-7653.5 7783.5-7898.5
7301.5-7388.5 7105.5-7192.5
7105.5-7192.5 7301.5-7388.5
196A
7357.5-7444.5 7161.5-7248.5
7161.5-7248.5 7357.5-7444.5
7440.5-7499.5 7622.5-7681.5
7678.5-7737.5 7496.5-7555.5
7496.5-7555.5 7678.5-7737.5
7580.5-7639.5 7412.5-7471.5
7412.5-7471.5 7580.5-7639.5
7 GHz
7608.5-7667.5 7440.5-7499.5
168C
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
7441.5-7500.5 7609.5-7668.5
7637.5-7696.5 7469.5-7528.5
168B
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
7119.5-7178.5 7280.5-7339.5
7308.5-7367.5 7147.5-7206.5
7147.5-7206.5 7308.5-7367.5
161P
7336.5-7395.5 7175.5-7234.5
7175.5-7234.5 7336.5-7395.5
7364.5-7423.5 7203.5-7262.5
7203.5-7262.5 7364.5-7423.5
7597.5-7622.5 7436.5-7461.5
7436.5-7461.5 7597.5-7622.5
161O
7681.5-7706.5 7520.5-7545.5
7520.5-7545.5 7681.5-7706.5
7587.5-7646.5 7426.5-7485.5
7426.5-7485.5 7587.5-7646.5
161M
7615.5-7674.5 7454.5-7513.5
7454.5-7513.5 7615.5-7674.5
7643.5-7702.5 7482.5-7541.5
7482.5-7541.5 7643.5-7702.5
161K
7671.5-7730.5 7510.5-7569.5
7510.5-7569.5 7671.5-7730.5
7580.5-7639.5 7419.5-7478.5
7419.5-7478.5 7580.5-7639.5
7608.5-7667.5 7447.5-7506.5
161J
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
7112.5-7192.5 7273.5-7353.5
7322.5-7402.5 7161.5-7241.5
7161.5-7241.5 7322.5-7402.5
161F
7573.5-7653.5 7412.5-7492.5
7412.5-7492.5 7573.5-7653.5
7622.5-7702.5 7461.5-7541.5
7461.5-7541.5 7622.5-7702.5
7709-7768 7548-7607
7548-7607 7709-7768
7737-7796 7576-7635
7576-7635 7737-7796
161D
7765-7824 7604-7663
7604-7663 7765-7824
7793-7852 7632-7691
7632-7691 7793-7852
7584-7643 7423-7482
7423-7482 7584-7643
7612-7671 7451-7510
7451-7510 7612-7671
161C
7640-7699 7479-7538
7479-7538 7640-7699
7668-7727 7507-7566
7507-7566 7668-7727
7409-7468 7248-7307
7248-7307 7409-7468
7437-7496 7276-7335 161B
7276-7335 7437-7496
7465-7524 7304-7363


7304-7363 7465-7524
7493-7552 7332-7391
7332-7391 7493-7552
7284-7343 7123-7182
7123-7182 7284-7343
7312-7371 7151-7210
7151-7210 7312-7371
161A
7340-7399 7179-7238
7179-7238 7340-7399
7368-7427 7207-7266
7207-7266 7368-7427
7280.5-7339.5 7126.5-7185.5
7126.5-7185.5 7280.5-7339.5
7308.5-7367.5 7154.5-7213.5
7154.5-7213.5 7308.5-7367.5
154C
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
7440.5-7499.5 7594.5-7653.5
7622.5-7681.5 7468.5-7527.5
154B
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
7426.5-7485.5 7580.5-7639.5
7608.5-7667.5 7454.5-7513.5
7454.5-7513.5 7608.5-7667.5
154A
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


8396.5-8455.5 8277.5-8336.5
8277.5-8336.5 8396.5-8455.5
119A
8438.5 – 8497.5 8319.5 – 8378.5
8319.5 – 8378.5 8438.5 – 8497.5
8274.5-8305.5 7744.5-7775.5
530A
7744.5-7775.5 8274.5-8305.5
8304.5-8395.5 7804.5-7895.5
500A
7804.5-7895.5 8304.5-8395.5
8023-8186.32 7711.68-7875
311C-J
7711.68-7875 8023-8186.32
8028.695-8148.645 7717.375-7837.325
7717.375-7837.325 8028.695-8148.645
311B
8147.295-8267.245 7835.975-7955.925
7835.975-7955.925 8147.295-8267.245
8043.52-8163.47 7732.2-7852.15
7732.2-7852.15 8043.52-8163.47
311A
8 GHz 8162.12-8282.07 7850.8-7970.75
7850.8-7970.75 8162.12-8282.07
8212-8302 7902-7992
7902-7992 8212-8302
8240-8330 7930-8020
310D
7930-8020 8240-8330
8296-8386 7986-8076
7986-8076 8296-8386
8212-8302 7902-7992
7902-7992 8212-8302
8240-8330 7930-8020
7930-8020 8240-8330
8296-8386 7986-8076 310C
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
7729.5-7840.5 8039.5-8150.5
310A
8159.5-8270.5 7849.5-7960.5
7849.5-7960.5 8159.5-8270.5
8024.5-8145.5 7724.5-7845.5
7724.5-7845.5 8024.5-8145.5
300A
8144.5-8265.5 7844.5-7965.5
7844.5-7965.5 8144.5-8265.5
8302.5-8389.5 8036.5-8123.5
266C
8036.5-8123.5 8302.5-8389.5
8190.5-8277.5 7924.5-8011.5
266B
7924.5-8011.5 8190.5-8277.5
8176.5-8291.5 7910.5-8025.5
7910.5-8025.5 8176.5-8291.5
266A
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
10501-10563 10333-10395
10333-10395 10501-10563
10529-10591 10361-10423
168A
10361-10423 10529-10591
10585-10647 10417-10479
10 GHz 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
10499-10531 10590-10622
10618-10649 10527-10558
91A
10527-10558 10618-10649
10646-10677 10555-10586
10555-10586 10646-10677
11425-11725 10915-11207
11 GHz 10915-11207 11425-11725

All
11185-11485 10700-10950
10695-10955 11185-11485
13002-13141 12747-12866
12747-12866 13002-13141
266
13127-13246 12858-12990
12858-12990 13127-13246
12807-12919 13073-13185 266A
13073-13185 12807-12919
13 GHz 12700-12775 12900-13000

12900-13000 12700-12775
12750-12825 12950-13050
12950-13050 12750-12825
200
12800-12870 13000-13100
13000-13100 12800-12870
12850-12925 13050-13150
13050-13150 12850-12925
15110-15348 14620-14858
14620-14858 15110-15348
15 GHz 490
14887-15117 14397-14627
14397-14627 14887-15117
15144-15341 14500-14697 644


14500-14697 15144-15341
14975-15135 14500-14660
14500-14660 14975-15135
475
15135-15295 14660-14820
14660-14820 15135-15295
14921-15145 14501-14725
14501-14725 14921-15145
420
15117-15341 14697-14921
14697-14921 15117-15341
14963-15075 14648-14760
14648-14760 14963-15075
315
15047-15159 14732-14844
14732-14844 15047-15159
15229-15375 14500-14647
728
14500-14647 15229-15375
19160-19700 18126-18690
18126-18690 19160-19700
1010
18 GHz 18710-19220 17700-18200
17700-18200 18710-19220
19260-19700 17700-18140
1560
17700-18140 19260-19700
23000-23600 22000-22600
1008
22000-22600 23000-23600
23 GHz 22400-23000 21200-21800

21200-21800 22400-23000
1232 /1200
23000-23600 21800-22400
21800-22400 23000-23600

33
24UL GHz
24000 - 24250 24000 - 24250 All
25530-26030 24520-25030
24520-25030 25530-26030
1008
25980-26480 24970-25480
26 GHz 24970-25480 25980-26480

25266-25350 24466-24550
24466-24550 25266-25350
800
25050-25250 24250-24450
24250-24450 25050-25250
28150-28350 27700-27900
27700-27900 28150-28350
450
27950-28150 27500-27700
27500-27700 27950-28150
28050-28200 27700-27850 350
27700-27850 28050-28200
27960-28110 27610-27760
28 GHz 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
29225-29250 29100-29125
31000-31085 31215-31300 175
31 GHz
31215-31300 31000-31085
33
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.


31815-32207 32627-33019 812
32627-33019 31815-32207
32 GHz
32179-32571 32991-33383
32991-33383 32179-32571
38820-39440 37560-38180 1260

37560-38180 38820-39440
38316-38936 37045-37676
37045-37676 38316-38936
39650-40000 38950-39300
38 GHz 38950-39300 39500-40000

39300-39650 38600-38950
38600-38950 39300-39650
700
37700-38050 37000-37350
37000-37350 37700-38050
38050-38400 37350-37700
37350-37700 38050-38400
40550-41278 42050-42778
42 GHz 42050-42778 40550-41278 1500
41222-41950.5 42722-43450
42722-43450 41222-41950.5

8.7 Mediation Device Losses

13-15 18-26 28-42
Configuration Interfaces 6-8 GHz 11 GHz
GHz GHz GHz
Remote Mount Added on remote
Flex WG 0.5 0.5 1.2 1.5 1.5
antenna mount configurations
Using Dual Core mediation
Direct Mount Integrated antenna 0.2 0.2 0.4 0.5 0.5
device
MultiCore 1+1 HSB (ready
Main Path 1.6 1.6 1.8 2 2
for 2+2) Direct Mount
with asymmetrical coupler Secondary Path 6 6 6 6 6
MultiCore 1+1 HSB (ready
Main Path 1.4 1.4 1.6 1.8 1.8
for 2+2) Remote Mount
with asymmetrical coupler Secondary Path 6 6 6 6 6
MultiCore 2+0 DP (OMT) Direct Mount Integrated antenna 0.5 0.5 0.5 0.5 0.5
MultiCore 2+2 HSB (OMT) Main Path 1.9 1.9 2.1 2.3 2.3
Remote Mount
with asymmetrical coupler Secondary Path 6.5 6.5 6.5 6.5 6.5
MultiCore 2+0/1+1 FD SP Integrated antenna 3.8 3.8 3.9 4 4
2 x MultiCore 2+0 DP
Remote Mount 4.2 4.2 4.3 4.4 4.4
(OMT)
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 typical loss per
component.

8.8 Ethernet Latency Specifications
8.8.1 Latency – 28 MHz Channel Bandwidth

ACM Modulation Latency (usec) with GE Interface
Working
Point Frame 64 128 256 512 1024 1518
Size
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

Working
Point Frame 64 128 256 512 1024 1518
Size
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


Working
Point Frame 64 128 256 512 1024 1518
Size
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

Working
Point Frame 64 128 256 512 1024 1518
Size
0 QPSK 84 90 102 124 171 216
1 8 PSK 67 71 81 98 134 168
2 16 QAM 59 62 70 83 112 139
3 32 QAM 55 58 64 76 100 123
4 64 QAM 51 54 60 70 92 112
5 128 QAM 49 52 57 67 87 106
6 256 QAM 55 58 63 72 90 108
7 512 QAM N/A N/A N/A N/A N/A N/A
8 1024 QAM (strong FEC) N/A N/A N/A N/A N/A N/A
9 1024 QAM (light FEC) N/A N/A N/A N/A N/A N/A
10 2048 QAM N/A N/A N/A N/A N/A N/A

8.9 Interface Specifications
8.9.1 Ethernet Interface Specifications

1 x 10/100/1000Base-T (RJ-45)
Supported Ethernet Interfaces for Traffic
2x1000base-X (Optical SFP) or 10/100/1000Base-T (Electrical SFP)
Supported Ethernet Interfaces for
10/100 Base-T (RJ-45)
Management
Optical 1000Base-LX (1310 nm) or SX (850 nm)
Recommended SFP Types
Note: SFP devices must be of industrial grade (-40°C to +85°C)

8.10 Carrier Ethernet Functionality

Latency over the radio link < 0.15 ms @ 400 Mbps
"Jumbo" Frame Support Up to 9600 Bytes
Enhanced link state propagation

General
Header De-Duplication
Switching capacity: 5Gbps / 3.12Mpps

Maximum number of Ethernet services: 64 plus one pre-defined
management service
Integrated Carrier Ethernet Switch
MAC address learning with 128K MAC addresses
802.1ad provider bridges (QinQ)
802.3ad link aggregation
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
QoS
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
MSTP
Network resiliency
ERP (G.8032)
CFM (802.1ag)
OAM
EFM (802.1ah)
Per port Ethernet counters (RMON/RMON2)
Radio ACM statistics
Performance Monitoring
Enhanced radio Ethernet statistics (Frame Error Rate,
Throughput, Capacity, Utilization)
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)
Supported Ethernet/IP Standards 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.11 Synchronization Functionality

 SyncE
SyncE input and output (G.8262)
 IEEE 1588v2 (Precision Time Protocol)34
Transparent Clock
8.12 Network Management, Diagnostics, Status, and Alarms

Network Management System Ceragon NMS
SNMPv1/v2c/v3
NMS Interface protocol
XML over HTTP/HTTPS toward NMS
Element Management Web based EMS, CLI
HTTP/HTTPS
Management Channels &
Telnet/SSH-2
Protocols
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
Ceragon NMS functions are in accordance with ITU-T
TMN
recommendations for TMN
35
RSL Indication Accurate power reading (dBm) available at IP-20C , and NMS
Performance Monitoring Integral with onboard memory per ITU-T G.826/G.828
8.13 Mechanical Specifications

Module Dimensions (H)230mm x (W)233mm x (D)98mm
Module Weight 6.5 kg
Pole Diameter Range (for
8.89 cm – 11.43 cm
Remote Mount Installation)
34
IEEE 1588v2 support is planned for future release.
35
Note that the voltage measured at the BNC port is not accurate and should be used only as an
aid.

8.14 Standards Compliance

Specification Standard
EN 301 489-1, EN 301 489-4, Class B
(Europe)
EMC FCC 47 CFR, part 15, class B (US)
ICES-003, Class B (Canada)
TEC/EMI/TEL-001/01, Class B (India)
EN61000-4-5, Class 4 (for PWR and
Surge
ETH1/PoE ports)
EN 60950-1
IEC 60950-1
UL 60950-1
Safety CSA-C22.2 No.60950-1
EN 60950-22
UL 60950-22
CSA C22.2.60950-22

8.15 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

8.16 Antenna Specifications

Direct Mount:
Andrew (VHLP), RFS, Xian Putian (WTG), Radio Wave, GD, Shenglu
Remote Mount:
Frequency (GHz) Waveguide Standard Waveguide Antenna
Flange Flange
6 WR137 PDR70 UDR70
7/8 WR112 PBR84 UBR84
10/11 WR90 PBR100 UBR100
13 WR75 PBR120 UBR120
15 WR62 PBR140 UBR140
18-26 WR42 PBR220 UBR220
28-38 WR28 PBR320 UBR320
42 WR22 UG383/U UG383/U
If a different antenna type (CPR flange) is used, a flange adaptor is required.

Please contact your Ceragon representative for details.
8.17 Power Input Specifications

Standard Input -48 VDC
DC Input range -40 to -60 VDC
8.18 Power Consumption Specifications

Maximum Power Consumption 6 GHz 7-8 GHz 11 GHz 13-15 GHz 18-24 GHz 26-42 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.

8.19 Power Connection Options

Power Source and
Data Connection Type Connection Length DC Cable Type / Gage
Range
≤ 100m 18AWG
Ext DC Optical
100m ÷ 300m 12AWG
-(40.5 ÷ 60)VDC
Electrical ≤ 100m 18AWG
PoE Injector Electrical ≤ 100m CAT5e (24AWG)
36
±(18 ÷ 60)VDC
36
Optional.

8.20 PoE Injector Specifications
8.20.1 Power Input

Standard Input -48 or +24VDC (Optional)
37
DC Input range ±(18 /40.5 to 60) VDC
8.20.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.20.3 Standards Compliance

Specification Standard
EN 301 489-1, EN 301 489-4, Class A
(Europe)
EMC FCC 47 CFR, part 15, class B (US)
ICES-003, Class B (Canada)
TEC/EMI/TEL-001/01, Class A (India)
EN 60950-1
IEC 60950-1
UL 60950-1
Safety CSA-C22.2 No.60950-1
EN 60950-22
UL 60950-22
CSA C22.2.60950-22
37
+18VDC extended range is supported as part of the nominal +24VDC support.

8.20.4 Mechanical
Module Dimensions (H)134mm x (W)190mm x (D)62mm
Module Weight 1kg

8.21 Cable Specifications
8.21.1 Outdoor Ethernet Cable Specifications

Electrical Requirements
Cable type CAT-5e FTP/STP, 4 pairs, according to ANSI/TIA/EIA-568-B-2
Wire gage 24 AWG
Stranding Solid
Voltage rating 70V
Shielding Braid
Pinout
Mechanical/ Environmental Requirements

Jacket PVC, double, UV resistant
Outer diameter 7-10 mm
Operating and Storage temperature -40°C - 85°C
range
Flammability rating According to UL-1581 VW1, IEC 60332-1
RoHS According to Directive/2002/95/EC

8.21.2 Outdoor DC Cable Specifications

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
Spark test 4KV
Dielectric strength 2KV AC min
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

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.
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 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 xxx - TRS 3 figures in [MHz].

block indication(Ceragon Y - Letter to indicate frequency block.
internal) 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.
The following are some examples of specific IP-20C marketing models based on the syntax specified above.
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

Ceragon IP20

Uploaded by

Copyright:

Available Formats

Ceragon IP20

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ceragon IP20

Uploaded by

Copyright:

Available Formats

ETSI Version

Copyright © 2014 by Ceragon Networks Ltd. All rights reserved.

Open Source Statement

Ceragon Proprietary and Confidential Page 2 of 227

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

5. Feature Description ........................................................................................ 41

Ceragon Proprietary and Confidential Page 3 of 227

5.3.1 Ethernet Services Overview ......................................................................................... 81

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

7. Standards and Certifications ....................................................................... 186

8. Specifications ............................................................................................... 188

Ceragon Proprietary and Confidential Page 4 of 227

8.2 Frequency Accuracy .................................................................................................. 189

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

Ceragon Proprietary and Confidential Page 5 of 227

2x2 LoS MIMO Direct Mount Configuration ........................................................ 25

Cable Gland Construction ................................................................................... 27

Separation Criteria when Working with Two Diplexer Types ............................ 32

Doubling IP-20C’s Capacity by Activating Second Core ................................... 44

Quadrupling Capacity by Leveraging LoS MIMO with IP-20C’s MultiCore

Ceragon Proprietary and Confidential Page 6 of 227

NLoS MIMO (Left) and LoS MIMO (Right) Compared ......................................... 51

Multi-Carrier ABC Traffic Flow ............................................................................ 63

Adaptive Coding and Modulation with 11 Working Points ................................ 68

Multipoint to Multipoint EVC ............................................................................... 83

Ceragon Proprietary and Confidential Page 7 of 227

E-Line Service Type Using Point-to-Point EVC .................................................. 86

E-LAN Service Type Using Multipoint-to-Multipoint EVC.................................. 88

MEF Ethernet Private LAN Example ................................................................... 90

E-Tree Service Type Using Multiple Roots ......................................................... 92

Mobile Backhaul Reference Model ..................................................................... 94

IP-20C Services Core ........................................................................................... 99

Grouped Interfaces as a Single Logical Interface on Egress Side ................. 116

Ceragon Proprietary and Confidential Page 8 of 227

Hierarchical Classification ................................................................................ 127

IP-20C Queue Manager ...................................................................................... 135

WRED Profile Curve ........................................................................................... 138

G.8032 Ring in Idle (Normal) State .................................................................... 154

IP-20C End-to-End Service Management ......................................................... 159

Transparent Clock Delay Compensation.......................................................... 166

Ceragon Proprietary and Confidential Page 9 of 227

ACM Working Points (Profiles) ........................................................................... 67

Ethernet Services Learning and Forwarding ................................................... 103

Service Point Type-Attached Interface Type Combinations that can Co-Exist on

NMS Server Receiving Data Ports .................................................................... 171

Ceragon Proprietary and Confidential Page 10 of 227

Additional Management Ports for IP-20C ......................................................... 171

IP-20C High Power ............................................................................................. 195

Ceragon Proprietary and Confidential Page 11 of 227

About This Guide

What You Should Know

Ceragon Proprietary and Confidential Page 12 of 227

1. Synonyms and Acronyms

ACAP Adjacent Channel Alternate Polarization

Ceragon Proprietary and Confidential Page 13 of 227

LMS License Management System

Ceragon Proprietary and Confidential Page 14 of 227

SAP Service Access Point

Ceragon Proprietary and Confidential Page 15 of 227

This chapter includes: