IP-10 G-Series - PD - 10-2010 - V30 PDF

FibeAir® IP-10 G-Series (R2)
Product Description
Document Version: 30
October 2010
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.
Registered Trademarks
® ® ®
Ceragon Networks , FibeAir and CeraView are registered trademarks of Ceragon Networks Ltd.
Other names mentioned in this publication are owned by their respective holders.
Trademarks
TM TM TM TM, TM TM TM
CeraMap , ConfigAir , PolyView , EncryptAir CeraMon , EtherAir , and MicroWave Fiber , 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.
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.
Copyright © 2010 by Ceragon Networks Ltd. All rights reserved.
Corporate Headquarters Asia Pacific North America

Ceragon Networks Ltd. Ceragon Networks APAC Ceragon Networks, Inc.
Tel Aviv, Israel (S’pore) Ltd. New Jersey, USA
Tel: +972-3-645-5733 Singapore Tel: +1-201-845-6955
Fax: +972-3-645-5499 Tel: +65-6339-3110 Fax: +1-201-845-5665
Fax: +65-6339-1310 Toll free: 1-877-FIBEAIR
Europe MEA CALA

Ceragon Networks Ceragon Networks, Ceragon Networks,
(UK) Limited Johannesburg S.A. de C.V
Redditch, UK South Africa Mexico D.F, Mexico
Tel: +44-(0)-1527-591900 Tel: +27-01-1452-2777 Tel: +52-55-5663-2914
Fax: +44-(0)-1527-591903 Fax: +27-01-1452-2777 Fax: +52-55-5663-2841
www.ceragon.com
Table of Contents
1 Introduction .................................................................................................. 7
1.1 FibeAir IP-10 G-Series main features ........................................................................ 8
1.2 Applications............................................................................................................. 9
1.2.1 Mobile Backhaul ..........................................................................................................9
1.2.2 Converged Fixed/Wireless Networks ............................................................................9
1.3 Advantages ............................................................................................................ 10
2 Overview .................................................................................................... 11
2.1 System Overview ................................................................................................... 11
2.1.1 Interfaces .................................................................................................................. 12
2.1.2 Available Assembly Options *..................................................................................... 14
2.2 RF Unit .................................................................................................................. 15
2.3 FibeAir IP-10 Value Structure ................................................................................. 16
2.4 FibeAir IP-10 Functionality ..................................................................................... 17
2.5 Features ................................................................................................................ 18
2.5.1 High Spectral Efficiency .............................................................................................. 18
2.5.2 Native2 Microwave Radio Technology ......................................................................... 19
2.5.3 Adaptive Coding & Modulation .................................................................................. 20
2.5.4 Enhancing Spectral Efficiency using XPIC ..................................................................... 21
2.5.5 Integrated Carrier Ethernet Switching ......................................................................... 22
2.5.6 Integrated Quality of Service (QoS)............................................................................. 23
2.5.7 Intelligent Ethernet Header Compression (patent-pending)......................................... 24
2.5.8 Extensive Radio Capacity/Utilization Statistics ............................................................ 24
2.5.9 In-Band Management ................................................................................................ 24
2.5.10 Synchronization Solution............................................................................................ 25
2.5.11 Integrated Nodal Solution .......................................................................................... 25
2.5.12 TDM Cross-Connect Unit ............................................................................................ 26
2.5.13 ABR - Capacity Doubling Innovation ........................................................................... 27
3 Main Features ............................................................................................. 28

3.1 Adaptive Coding and Modulation ........................................................................... 28
FiberAir IP-10 G-Series (R2) – Product Description 3

3.1.1 Overview ................................................................................................................... 28
3.1.2 Adaptive Modulation and Built-in Quality of Service ................................................... 29
3.1.3 ACM with Adaptive Tx Power ..................................................................................... 30
3.1.4 ACM for E1/DS1 services ............................................................................................ 31
3.2 Multi-Radio with ACM support............................................................................... 32
3.3 XPIC support .......................................................................................................... 33
3.3.1 Implementation ......................................................................................................... 33
3.3.2 XPIC and Multi-Radio ................................................................................................. 35
3.4 Integrated Carrier Ethernet support ....................................................................... 36
3.4.1 Carrier Grade Ethernet ............................................................................................... 36
3.4.2 Carrier Ethernet solution overview ............................................................................. 38
3.4.3 MEF Certified ............................................................................................................. 39
3.4.4 Integrated QoS Support ............................................................................................. 40
3.4.5 Ethernet Statistics ...................................................................................................... 44
3.4.6 Ethernet resilient networks support ........................................................................... 46
3.4.7 End to End Multi-Layer OA&M ................................................................................... 51
3.4.8 FibeAir IP-10 Carrier Ethernet Services Example .......................................................... 52
3.5 Integrated Nodal Solution ...................................................................................... 55
3.5.1 IP-10 Nodal Design ..................................................................................................... 55
3.5.2 IP-10 Nodal Stacking Concept – Advantages ................................................................ 57
3.5.3 IP-10 Nodal Stacking Method ..................................................................................... 57
3.5.4 Nodal Enclosure Design .............................................................................................. 58
3.5.5 Nodal Solution Management ...................................................................................... 59
3.5.6 Nodal solution Ethernet connectivity .......................................................................... 59
3.6 Cross-Connect (XC) Unit ......................................................................................... 60
3.6.1 XC Basics.................................................................................................................... 60
3.6.2 XC Features................................................................................................................ 61
3.6.3 TDM Trail Status Handling .......................................................................................... 62
3.6.4 Wireless SNCP............................................................................................................ 63
3.7 ABR (Adaptive Bandwidth Recovery) ...................................................................... 66
3.7.1 Overview ................................................................................................................... 66
3.7.2 Comparing Ring Protection Schemes .......................................................................... 66

3.7.3 A Novel Approach to Bandwidth Recovery .................................................................. 70
3.7.4 Protected Adaptive Bandwidth Recovery (ABR) .......................................................... 70
3.7.5 Dual Homing .............................................................................................................. 71
3.7.6 Hybrid Fiber / Microwave Networks ........................................................................... 71
3.7.7 ABR with ACM ........................................................................................................... 71
3.7.8 Trail Management...................................................................................................... 71
3.7.9 ABR – Case Study ....................................................................................................... 72
3.7.10 Ethernet Ring Failure States ....................................................................................... 74
3.7.11 Comparison of Protection Methods – To Allocate or not to Allocate ............................ 75
3.7.12 Risk Free Bandwidth Re-allocation ............................................................................. 76
3.7.13 ABR Benefits .............................................................................................................. 76
3.7.14 Summary ................................................................................................................... 78
3.8 Synchronization support ........................................................................................ 79
3.8.1 Wireless Network Synchronization ............................................................................. 79
3.8.2 Wireless IP Synchronization Challenges ...................................................................... 79
3.8.3 ToP (Timing over Packet) ............................................................................................ 79
3.8.4 Synchronous Ethernet (SyncE) .................................................................................... 80
3.8.5 Ceragon's Native2 Sync Solution ................................................................................. 81
3.8.6 Synchronization using Native E1/T1 Trails ................................................................... 81
3.8.7 PTP optimized Transport ............................................................................................ 82
3.8.8 SyncE ......................................................................................................................... 83
3.8.9 “Native Sync Distribution” Mode ................................................................................ 84
4 Typical Configurations................................................................................. 85
4.1 Point to point configurations ................................................................................. 85
4.1.1 1+0 ............................................................................................................................ 85
4.1.2 1+1 HSB ..................................................................................................................... 86
4.1.3 1+0 with 32 E1s/T1s ................................................................................................... 87
4.1.4 1+0 with 64 E1s/T1s ................................................................................................... 87
4.1.5 2+0/XPIC Link, with 64 E1/T1s, “no Multi-Radio” Mode .............................................. 88
4.1.6 2+0/XPIC Link, with 64 E1/T1s, “Multi-Radio” Mode ................................................... 89
4.1.7 2+0/XPIC Link, with 32 E1/T1s + STM1/OC3 Mux Interface, no Multi-Radio, up to 168
E1/T1s over the radio ............................................................................................................... 90

4.1.8 1+1 HSB with 32 E1s/T1s ............................................................................................ 90
4.1.9 1+1 HSB with 64 E1s/T1s ............................................................................................ 91
4.1.10 1+1 HSB with 84 E1/T1s.............................................................................................. 91
4.1.11 1+1 HSB Link with 16 E1/T1s + STM1/OC3 Mux Interface (Up to 84 E1s/T1s over the
radio) .................................................................................................................................. 92
4.1.12 Native2 2+2/XPIC/Multi-Radio MW Link, with 2xSTM1/OC3 Mux (up to 168 E1/T1s over
the radio) ................................................................................................................................. 92
4.2 Nodal Configurations ............................................................................................. 93
4.2.1 Chain with 1+0 Downlink and 1+1 HSB Uplink, with STM1/OC3 Mux ........................... 93
4.2.2 Node with 2 x 1+0 Downlinks and 1 x 1+1 HSB Uplink ................................................. 94
4.2.3 Chain with 1+1 Downlink and 1+1 HSB Uplink, with STM1/OC3 Mux ........................... 95
4.2.4 Native2 Ring with 3 x 1+0 Links + STM1/OC3 Mux Interface at Main Site ...................... 96
4.2.5 Native2 Ring with 3 x 1+1 HSB Links + STM-1 Mux Interface at Main Site...................... 97
4.2.6 Node with 1 x 1+1 HSB Downlink and 1 x 1+1 HSB Uplink, with STM1/OC3 Mux .......... 98
4.2.7 Native2 Ring with 4 x 1+0 Links, with STM1/OC3 Mux ................................................. 99
4.2.8 Native2 Ring with 3 x 1+0 Links + Spur Link 1+0 ......................................................... 100
4.2.9 Native2 Ring with 4 x 1+0 MW Links and 1 x Fiber Link (5 hops total), with STM1/OC3
Mux ................................................................................................................................ 101
4.2.10 Native2 Ring with 2 x 2+0/XPIC MW Links and 1 x Fiber Link (3 hops total), with 2 x
STM1/OC3 Mux ...................................................................................................................... 102
5 Network Management .............................................................................. 103

5.1 Overview ............................................................................................................. 103
5.2 Management System ........................................................................................... 104
5.3 Web-based Management ..................................................................................... 104
5.4 PolyView ............................................................................................................. 104
5.5 CLI (Command Line Interface) .............................................................................. 105

1 Introduction
FibeAir IP-10 is Ceragon's comprehensive high capacity IP and Migration-to-IP network solution. The
innovative IP-10 was designed as a native Ethernet microwave radio platform that can integrate smoothly
in any network, while providing a broad range of software-configurable licensed channel schemes.
IP-10 follows in the tradition of Ceragon's Native2, which allows your network to benefit from both native
TDM and native Ethernet using the same radio. Flexible bandwidth sharing between the TDM and
Ethernet traffic ensures optimal throughput for all your media transfer needs.
With the Metro Ethernet Networking trend growing, IP-10 is poised to fill in the gap and deliver high
capacity IP communication quickly, easily, and reliably.
nXT1/E1
n X T1/E1
MEN
ETH
Control
IP-10 features impressive market-leading throughput capability together with advanced networking
functionality.
Some of the quick points that place IP-10 at the top of the wireless IP offerings:
Supports all licensed bands, from 6 to 38 GHz
Supports channel bandwidths of from 3.5 MHz to 56 MHz
Supports throughputs of from 10 to 500 Mbps per radio carrier (QPSK to 256 QAM)
Incorporates advanced integrated Ethernet switching capabilities
In addition, using unique Adaptive Coding & Modulation (ACM), your network benefits from non-stop,
dependable, capacity deliverance.

1.1 FibeAir IP-10 G-Series main features
This product description covers FibeAir IP-10 G Series.
The main features of the IP-10 G-Series are as follows:
IP-10 G-Series
Supported radio configurations 1+0, 1+1 HSB, 1+1 SD/FD,
2+0 with XPIC
2+2 HSB with XPIC
XPIC option Yes
Max radio capacity 500Mbps
1Gbps using 2+0/XPIC
Multi-radio support 2+0 and 2+2 HSB
# of Ethernet interfaces 5 x FE RJ-45+
2 x GE combo (RJ-45/SFP)
Full Carrier Ethernet switching Yes
feature-set including ring
protection
# of E1/T1 integrated IDU 16 E1, 16T1, None
interfaces option
# of E1/T1s per radio carrier 84 E1/T1s
T-Card slot (additional 16 E1/T1 Yes
interfaces or STM1/OC3 Mux)
Nodal/XC/SNCP 1+1 support Yes
ABR (SNCP 1:1) support Yes
Sync unit option Yes
V.11/RS232 User Channel option 2 x Async V.11/RS232 or
1 x Sync V.11
FibeAir IP-10 G-series

1.2 Applications
1.2.1 Mobile Backhaul
For Cellular Networks, FibeAir IP-10 family supports both Ethernet and TDM for cellular backhaul
network migration to IP, within the same compact footprint. The system is suitable for all migration
scenarios where carrier-grade Ethernet and legacy TDM services are required simultaneously.
For WiMAX Networks, FibeAir IP-10 family enables connectivity between WiMAX base stations and
facilitating the expansion and reach of emerging WiMAX networks, FibeAir IP-10 provides a robust and
cost-efficient solution with advanced native Ethernet capabilities.
FibeAir IP-10 family offers cost-effective, high-capacity connectivity for carriers in cellular, WiMAX and
fixed markets. The FibeAir IP-10 platform supports multi-service and converged networking
requirements for both legacy and the latest data-rich applications and services.
1.2.2 Converged Fixed/Wireless Networks
Ceragon‟s FibeAir IP-10 delivers integrated high speed data, video and voice traffic in the most optimum
and cost-effective manner. Operators can leverage FibeAir IP-10 to build a converged network
infrastructure based on high capacity microwave to support multiple types of service.
FibeAir IP-10 is fully compliant with MEF-9 & MEF-14 standards for all service types (EPL, EVPL and
E-LAN) making it the ideal platform for operators looking to provide high capacity Carrier Ethernet
services meeting customers demand for coverage and stringent SLA.
Figure 1: Typical FibeAir IP-10 Applications

1.3 Advantages
IP-10 has many advantages that cover the many aspects of flexible and reliable network building.
Incomparable Economic Value: The IP-10 pay-as-you-grow concept reduces network costs.
Each network node is optimized individually, with future capacity growth in mind. Whenever
needed, additional functionality is enabled via upgrade license, using the same hardware. Using
this flexible economic approach, a full duplex throughput of more than 400 Mbps over a single
channel can be achieved.
Experience Counts: IP-10 was designed with continuity in mind. It is based on Ceragon‟s well-
established and field-proven IP-MAX Ethernet microwave technology. With Ceragon's large
install base, years of experience in high-capacity IP radios, and seamless integration with all
standard IP equipment vendors, IP-10 is poised to be an IP networking standard-bearer.
Native2: With Native2, you get optimal all-IP or hybrid TDM-IP backhaul networking - ideal for
any RAN evolution path!
User-Management Traffic Integration: In-Band Management significantly simplifies backhaul
network design and maintenance, reducing both CapEx and OpEx. It also dramatically improves
overall network availability and reliability, enabling support for services with stringent SLA
(Service Level Agreement).
Unique Full Range Adaptive Modulation: Provides the widest modulation range on the market
from QPSK to 256 QAM with multi-level real-time hitless and errorless modulation shifting
changing dynamically according to environmental conditions - while ensuring zero downtime
connectivity.
Guaranteed Ultra Low Latency (< 0.15 ms @ 400Mbps): Suitable for delay-sensitive
applications, such as VoIP and Video over IP.
Extended Quality of Service (QoS) Support: Enables smart packet queuing and prioritization.
Fully Integrated L2 Ethernet Switching Functionality: Including VLAN based switching,
MAC address learning, QinQ and Ring-RSTP support.
Multiple Network Topology Support: Mesh, Ring, Chain, Point-to-Point.
Longer Transmission Distances, Smaller Antennas: Reduces network costs and enables a
farther reach to the other end.

2 Overview
2.1 System Overview
Split-mount architecture (IDU and RFU/ODU)
Compatible with all existing Ceragon RFUs/ODUs.
Dimensions
 Height: 42.6 mm (1RU)
 Width: 439 mm (<19")
 Depth: 188 mm (fits in ETSI rack)

DC input voltage nominal rating: -48V
Fans
TDM interfaces drawer
add-on slot
Craft 16 x E1/T1s
External
Terminal (optional) GND
Alarms RFU
(DB9)
(DB9) interface Power
Protection
Interface 2 x GE ”combo” 5 x FE (N-Type) -48V DC
Engineering User ports Electrical
order-wire (RJ45)
Channel Electrical (RJ45) (RJ45)
(optional) (optional) or Optical (SFP)
(RJ45)
Figure 2: IP-10 G-Series Front Panel and Interfaces

2.1.1 Interfaces
Main Interfaces:
5 x 10/100Base-T
2 x GbE combo ports: 10/100/1000Base-T or SFP 1000Base-X
16 x T1/E1 (optional)
RFU/ODU interface, N-type connector
Additional Interfaces:
TDM T-Card Slot options:
16 x E1
16 x T1
1 x STM-1/OC-3

16 x E1/T1 T-Card
STM-1/OC-3 Mux T-Card
The T-cards are field-upgradable, and add a new dimension to the FibeAir IP-10 migration flexibility.
TDM interfaces
add-on card
(T-Card)
Terminal console
AUX package (optional):
Engineering Order Wire (EOW)
User channel (V.11 Asynchronous, RS-232)

External alarms (4 inputs & 1 output)
PROT: Ethernet protection control interface (for 1+1 HSB mode support)

In addition, each of the FE traffic interfaces can be configured to support an alternate mode of operation:
MGT: Ethernet out-of-band management (up to 3 interfaces)
WS: Ethernet wayside
2.1.2 Available Assembly Options *
TDM options:
o Ethernet only (no TDM)
o Ethernet + 16 x E1 + T-Card Slot
o Ethernet + 16 x T1 + T-Card Slot
Sync unit
XPIC support
With or without AUX package - EOW, User channel

2.2 RF Unit
FibeAir IP-10 is based on the latest Ceragon technology, and can be installed together with any FibeAir
RFU, including:
FibeAir 1500HP (FibeAir RFU-HP)
FibeAir 1500HS (FibeAir RFU-HS)
FibeAir 1500SP (FibeAir RFU-SP)
FibeAir 1500P (FibeAir RFU-P)
FibeAir RFU-C
FibeAir RFUs support multiple capacities, frequencies, modulation schemes, and configurations for
various network requirements. The RFUs operate in the frequency range of 6-38 GHz, and support
capacities of from 10 Mbps to 500 Mbps, for TDM and IP interfaces.
IP-10 works with:

2.3 FibeAir IP-10 Value Structure
FibeAir IP-10 offers a pay-as-you-grow concept to reduce network costs. Future capacity growth and
additional functionality is enabled with license keys and an innovative stackable nodal solution using the
same hardware. The FibeAir IP-10 offers the following Value structure:
Additional IDUs
Software license keys Assembly options Add-ons (IDU stacking)
• Radio ACM • Sync. Unit • Nodal enclosures • Redundancy

• Carrier Ethernet Switch • TDM interfaces • Main • Diversity
• Network resiliency • 16 E1 • Expansion • Addition radio
• Sync. Unit • 16 DS1 • SFPs directions in node
• Enhanced QoS • T-card slot • Cables • Capacity doubling

• Radio Capacity • XPIC support • T-Cards • XPIC
• AUX • 16 E1 • Multi-radio
• 10M
• 25M • UC (V.11/RS-232) • 16 DS1
• 50M • EOW • STM1-Mux
• 100M
• 150M
• 200M
• 300M
• All / 500M

2.4 FibeAir IP-10 Functionality
The diagram below provides a high level functional block diagram of FibeAir IP-10.
OA&M Service Management Security
Carrier Ethernet Switch TDM Cross Connect
ACM XPIC Ch-STM1/

Gigabit Fast Native2 Radio Multi E1/ OC3
Ethernet Ethernet Ethernet + TDM Radio DS1
Terminal
10-500Mbps, 7-56MHz Diversity Mux
RFU (6-38GHz)
Figure 3: FibeAir IP-10 – functional block diagram

2.5 Features
2.5.1 High Spectral Efficiency
Modulations: QPSK to 256 QAM

Radio capacity:
ETSI – up to 50/100/220/280/500 Mbps over 7/14/28/40/56 MHz channels
FCC – up to 70/140/240/320/450 Mbps over 10/20/30/40/50 MHz channels
All licensed bands: L6, U6, 7, 8, 10, 11, 13, 15, 18, 23, 26, 28, 32, 38 GHz
Highest scalability: From 10 Mbps to 500 Mbps, using the same hardware, including the same
ODU/RFU!
Configurations: 1+0 or 1+1 Hot Standby (fully redundant), 1+1 SD/FD, 2+0 XPIC, 2+2 XPIC
hot-standby (fully redundant).
TDM Voice Transmission with Dynamic Allocation - With the n x E1/T1 option, only enabled
E1/T1 ports are allocated with capacity. The remaining capacity is dynamically allocated to the
Ethernet ports to ensure maximum Ethernet capacity.
XPIC Multi-Radio Space /Frequency Diversity

Same Frequency Different Polarization Ultra High Capacity Link Increase Availability and Avoid Multipath Fading
Space Diversity Frequency Diversity
V - Polarization
F1
Multi GbE
H - Polarization F2
Figure 4: FibeAir IP-10 - Supported configurations

2.5.2 Native2 Microwave Radio Technology
At the heart of the IP-10 solution is Ceragon's market-leading Native2 microwave technology.
With this technology, the microwave carrier supports native IP/Ethernet traffic together with optional
native PDH. Neither traffic type is mapped over the other, while both dynamically share the same overall
bandwidth.
This unique approach allows you to plan and build optimal all-IP or hybrid TDM-IP backhaul networks
which make it ideal for any RAN (Radio Access Network) evolution path selected by the wireless
provider (including Green-Field 3.5G/4G all-IP installations).
In addition, Native2 ensures:
Very low link latency of <0.15 msecs @ 400 Mbps.
Very low overhead mapping for both Ethernet and TDM traffic, to the microwave radio frame.
High precision native TDM synchronization distribution.
2
Figure 5: Native Microwave Radio Technology

2.5.3 Adaptive Coding & Modulation
ACM employs the highest possible modulation during changing environmental conditions, which may be
from QPSK to 256 QAM.
The benefits of this dynamic feature include:
Maximized spectrum usage
Increased capacity over a given bandwidth
8 modulation/coding work points (~3 db system gain for each point change)
Supports both Ethernet and E1/T1 traffic
Hitless and errorless modulation/coding changes, based on signal quality
Adaptive Radio Tx Power per modulation for maximal system gain per working point
Configurable drop priority between E1/T1 traffic and Ethernet traffic
An integrated QoS mechanism enables intelligent congestion management to ensure that your
high priority traffic is not affected during link fading
Each E1/T1 is assigned a priority to enable differentiated E1/T1 dropping during severe link
degradation
Figure 6: Adaptive Coding and Modulation with 8 working points

2.5.4 Enhancing Spectral Efficiency using XPIC
XPIC (Cross Polarization Interference Canceller) is one of the best ways to break the barriers of spectral
efficiency. Using dual-polarization radio over a single-frequency channel, a dual polarization radio
transmits two separate carrier waves over the same frequency, but using alternating polarities. Despite its
obvious advantages, one must also keep in mind that typical antennas cannot completely isolate the two
polarizations.
V - Polarization
H - 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
interferences, higher modulation schemes cannot and require cross-polarization interference canceler
(XPIC). The XPIC algorithm allows detection of both streams even under the worst levels of XPD such
as 10 dB. This is done by adaptively subtracting from each carrier the interfering cross carrier, at the right
phase and level. For high-modulation schemes such as 256 QAM, an improvement factor of more than 20
dB is required so that cross-interference does not limit performance anymore. XPIC implementation
involves system complexity and cost since the XPIC system requires each demodulator to cancel the other
channel interference.

2.5.5 Integrated Carrier Ethernet Switching
IP-10 supports two modes for Ethernet switching:

Smart Pipe - In this mode, Ethernet switching functionality is disabled and only a single Ethernet
interface is enabled for user traffic. The unit effectively operates as a point-to-point Ethernet
microwave radio.
Carrier Ethernet Switch - In this mode, Ethernet switching functionality is enabled.
The following table lists the different aspects of IP-10 functionality.
Standardized Scalability Quality of Reliability Service

services Service Management
 MEF-9 & MEF-14  Up to 500Mbps per  Advanced CoS  Highly reliable &  Extensive multi-
certified for all radio carrier classification integrated design layer management
service types (EPL, capabilities
 Up to 1Gbps per  Advanced traffic  Fully redundant
EVPL and E-LAN)
channel (with XPIC) policing/rate-limiting 1+1/2+2 HSB &  Ethernet service
 CoS based packet nodal configurations OA&M – 802.1ag
 Multi-Radio
queuing/buffering  Hit-less ACM and Y.1731.
 Integrated (QPSK – 256QAM)
with 8 queues  Advanced Ethernet
non-blocking switch for enhanced radio
support statistics
with 4K VLANs link availability
 802.1ad provider  Hierarchical
scheduling schemes  RSTP/MSTP
bridges (QinQ)
 Traffic shaping  Wireless Ethernet
 Scalable nodal Ring/Mesh support
solution  Tail-drop or WRED
 802.3ad link
 Scalable networks  Color- aggregation
(1000’s of NEs)
awareness  Fast link state
(CIR/EIR support) propagation
 <50msec restoration
time (typical)

2.5.6 Integrated Quality of Service (QoS)
IP-10 integrated QoS enables support for differentiated Ethernet services with SLA assurance.
Two levels of QoS are supported – “Standard QoS” and “Enhanced QoS”.
The table below lists the main QoS features supported.
Feature Standard QoS Enhanced QoS*

# of CoS queues per port 4 8
Source Port, VLAN 802.1p
CoS classification criteria VLAN ID, MAC SA/DA, Also: UDP port, MPLS EXP bits
IPv4 DSCP/TOS, IPv6 TC
Per port, CoS and traffic type Per port, CoS and traffic type
ingress traffic rate-limiting (policing)
(Broadcast, Multicast, etc.) (Broadcast, Multicast, etc.)
Hierarchical scheduling:
Scheduling method SP, WRR or Hybrid 4 scheduling priorities + WFQ between
queues in same priority
Also: Statistics per CoS queue
Ethernet statistics RMON
(Transmitted & Dropped frames)
Shaping Per port Also: per queue
Congestion management Also: Weighted Random Early Discard

Tail-drop
(WRED)
CIR/EIR support
CIR only CIR + EIR
(“Color-awareness” )
* A software license key is required to enable “Enhanced QoS”

2.5.7 Intelligent Ethernet Header Compression (patent-pending)
Intelligent Ethernet Header Compression improves effective throughput by up to 45% and does not affect
user traffic.
Ethernet Capacity increase by
packet size (bytes) compression
64 45%
96 29%
128 22%
256 11%
512 5%
2.5.8 Extensive Radio Capacity/Utilization Statistics
Statistics are collected at 15-minute and 24-hour intervals

Historical statistics are stored and made available when needed
Capacity/ACM statistics:
Maximum modulation in interval
Minimum modulation in interval
# of seconds in an interval, during which active modulation was below the user-configured
threshold
Utilization statistics:
Maximal radio link utilization in an interval
Average radio link utilization in an interval
-# of seconds in an interval, during which radio link utilization was above the user-configured
threshold
2.5.9 In-Band Management
IP-10 can optionally be managed in-band, via its radio and Ethernet interfaces. This method of
management eliminates the need for a dedicated interface and network. In-band management uses a
dedicated management VLAN, which is user-configurable.

2.5.10 Synchronization Solution
FibeAir IP-10 synchronization solution ensures maximum flexibility by enabling the operator to select
any combination of techniques suitable for the network.
Any combinations of the following techniques can be used:
 Synchronization using native E1/DS1 trails
 “PTP optimized transport” transport
o Support IEEE-1588, NTP, etc.
o Guaranteed ultra-low PDV (<0.05 msec per hop)
o Unique support ACM and narrow channels
 SyncE support (G.8262)
2.5.11 Integrated Nodal Solution
The Nodal solution features integrated Native2 networking functionality between all ports/radios, with
native Ethernet switching and native E1/Ti cross-connect, up to 84 E1s or 84 T1s per radio carrier, and
full high-availability support, including Cross-connect/switching elements, control/management elements,
radio carriers, and TDM/Ethernet interfaces.
 Same 1RU IP-10 unit can be used for terminal

and nodal solution
 The solution is stackable and modular
 Forms a single unified nodal device

 Common Ethernet Switch
 Common E1s Cross Connect
 Single IP address
 Single element to manage

The stackable nodal solution offers many advantages.
For green-field deployments:
 Low initial investment without compromising future growth potential
 Risk-free deployment in face of unknown future growth pattern:
o Additional capacity
o Additional sites
o Additional redundancy
For migration/replacement deployments:
 Optimized tail-site solution
 Low initial foot-print required for node sites
 Additional foot-print only required gradually as legacy equipment is being swapped
2.5.12 TDM Cross-Connect Unit
The FibeAir IP-10 Cross Connect (XC) is a high-speed circuit connection scheme for transporting TDM
traffic from any given port "x" to any given port "y".
The system is composed of several inter-connected (stacked) IDUs, with integrated and centralized TDM
traffic switching.
The XC capacity is 180 E1 VCs (Virtual Containers) or 180 T1 VCs, whereby each E1/T1 interface or
"logical interface" in a radio in any unit of the stack can be assigned to any VC.
Integrated TDM Cross Connect is performed by defining end to end trails. Each trail consists of segments
represented by Virtual Containers (VCs). The XC functions as the forwarding mechanism between the
two ends of a trail.

2.5.13 ABR - Capacity Doubling Innovation
Ceragon‟s native support for TDM traffic leverages the resiliency advantages of wireless SDH rings, with
their intrinsic Sub-Network Connection Protection (SNCP) path-protection capabilities. In SNCP,
information is redundantly transmitted on the ring in both “east” and “west” directions, while the receiver
selects which transmission to receive.
In today‟s super-competitive mobile industry, many carriers wish to reallocate the redundant protection
bandwidth for other uses, such as low-priority, high-volume data transfer. The benefits are clear –
exciting sales opportunities arise as newly-generated capacity can be sold to support the interpersonal
communications shift to Facebook, as well as the ever-growing demand for YouTube access.
No less importantly, this reallocation of bandwidth from TDM to Ethernet – and back – must be risk-free,
with no interruption of revenue-generating services.
In response to the needs described above, Ceragon proposes a novel approach to improve the efficiency of
ring-based protection, using a technique called Protected Adaptive Bandwidth Recovery (“ABR”),
which enables full utilization of the bidirectional capabilities inherent in ring technologies. With ABR,
the TDM-based information is transmitted in one direction only, while the unused protection capacity is
allocated for Ethernet traffic. In the event of a failure, the unused capacity is re-allocated for TDM
transmission.
This technique extends the Native2 approach to dynamic allocation of link capacity between TDM and
Ethernet flows to the network level.
Free bandwidth
for broadband E1 Main path
E1 alternate
path. Reserved
& allocated
Doubling E1 alternate
reserved path,
capacity no allocated
bandwidth
ABR (Adaptive Bandwidth Recovery)

Conventional Protection
Based on SNCP 1+1
Protection based on SNCP 1:1
• Each E1/T1 flow consists of a primary and • Each E1 flow consists of a primary and a protection path
protection path • Capacity is RESERVED but NOT ALLOCATED. Capacity
• Both paths RESERVE & ALLOCATE capacity allocation happens only on demand during failure
• All allocated bandwidth is consumed and • In normal state, primary path consumes capacity while
cannot be used by other applications the rest can be used for other applications, such as
mobile broadband
ABR - Protect critical services. Free bandwidth for broadband

3 Main Features
3.1 Adaptive Coding and Modulation
3.1.1 Overview
Adaptive Coding and Modulation refers to the automatic adjustment that a wireless system can make in
order to optimize over-the-air transmission and prevent weather-related fading from causing
communication on the link to be disrupted. When extreme weather conditions, such as a storm, affect the
transmission and receipt of data and voice over the wireless network, an ACM-enabled radio system
automatically changes modulation allowing real-time applications to continue to run uninterrupted.
Varying the modulation also varies the amount of bits that are transferred per signal, thereby enabling
higher throughputs and better spectral efficiencies. For example, a 256 QAM modulation can deliver
approximately four times the throughput of 4 QAM (QPSK).
Ceragon Networks employs full-range dynamic ACM in its new line of high-capacity wireless backhaul
product - FibeAir IP-10. In order to ensure high transmission quality, Ceragon solutions implement
hitless/errorless ACM that copes with 90 dB per second fading. A quality of service awareness
mechanism ensures that high priority voice and data packets are never “dropped”, thus maintaining
even the most stringent service level agreements (SLAs).
The hitless/errorless functionality of Ceragon‟s ACM has another major advantage in that it ensures that
TCP/IP sessions do not time-out. Lab simulations have shown that when short fades occur (for example if
a system has to terminate the signal for a short time to switch between modulations) they may lead to
timeout of the TCP/IP sessions – even when the interruption is only 50 milliseconds. TCP/IP timeouts are
followed by a drastic throughput decrease over the time it takes for the TCP sessions to recover. This may
take as long as several seconds. With a hitless/errorless ACM implementation this problem can be
avoided.
So how does it really work? Let's assume a system configured for 128 QAM with ~170 Mbps capacity
over a 28 MHz channel. When the receive signal Bit Error Ratio (BER) level arrives at a predetermined
threshold, the system will preemptively switch to 64 QAM and the throughput will be stepped down to
~140 Mbps. This is an errorless, virtually instantaneous switch. The system will then run at 64 QAM until
the fading condition either intensifies, or disappears. If the fade intensifies, another switch will take the
system down to 32 QAM. If, on the other hand, the weather condition improves, the modulation will be
switched back to the next higher step (e.g. 128QAM) and so on, step by step .The switching will continue
automatically and as quickly as needed, and can reach all the way down to QPSK during extreme
conditions.

Rx 256 QAM
level
99.9 %
128 QAM
99.95 %
64 QAM
99.99 %
32 QAM
99.995 %
16 QAM
99.999 %
QPSK
200 170 200 140 100 200 120 200 Mbps Capacity
(@ 28 MHz channel)
Unavailability
Figure 7: Adaptive Coding and Modulation
3.1.2 Adaptive Modulation and Built-in Quality of Service
Ceragon's Adaptive Modulation has a remarkable synergy with the equipment's built-in Layer 2 Quality
of Service mechanism. Since QoS provides priority support for different classes of service, according to a
wide range of criteria (see below) it is possible to configure the system to discard only low priority
packets as conditions deteriorate. The FibeAir IP-10 platform can classify packets according to the most
external header, VLAN 802.1p, TOS / TC - IP precedence and VLAN ID. All classes use 4 levels of
prioritization with user selectable options between strict priority queuing and weighted fair queuing with
user configurable weights.
If the user wishes to rely on external switches QoS, Adaptive Modulation can work with them via the
flow control mechanism supported in the radio.

3.1.3 ACM with Adaptive Tx Power
When planning ACM-based radio links, the radio planner attempts to apply the lowest transmit power
that will perform satisfactorily at the highest level of modulation. During fade conditions requiring a
modulation drop, most radio systems cannot increase transmit power to compensate for the signal
degradation, resulting in a deeper reduction in capacity. Ceragon‟s FibeAir IP-10 is capable of adjusting
power on the fly, optimizing the available capacity at every modulation point, as illustrated in Figure 8:
below. In the diagram, it is shown that operators that want to use ACM to benefit from high levels of
modulation (say, 256 QAM) will have to settle for low system gain, in this case, 18 dB for all the other
modulations as well. With FibeAir IP-10, operators can automatically adjust power levels, achieving the
extra 4 dB system gain that is required to maintain optimal throughput levels under all conditions.
Figure 8: Ceragon’s unique ACM with Adaptive Power vs. plain ACM

3.1.4 ACM for E1/DS1 services
Another unique advantage of the FibeAir system is its ability to use these sophisticated adaptive
techniques also in a hybrid, TDM/packet model. Using Ceragon‟s innovative Native2 migration solution,
in which TDM and Ethernet traffic is natively and simultaneously carried over a single microwave link,
Both E1/DS1 and Ethernet services can have configurable priority. When more than one E1/DS1 channel
is connected to a cell site, one of the channels can be given a higher priority in order to maintain network
synchronization as well as a minimum level of service. The rest of the E1/DS1 channels may be
forwarded at a lower priority.
Figure 9: Ceragon’s unique Adaptive Coding & Modulation adaption for TDM
There are substantial benefits to be reaped from applying ACM in TDM networks as well. An operator
may increase capacity on an existing link while maintaining the same availability for its existing revenue-
generating services. Additional data E1/DS1s are easily offloaded in this virtual link to a channel offering
slightly lower availability. Optimally, one E1/DS1 can be given a higher priority connection to maintain
synchronization and a minimum level of service at all times (higher than five-9s).
The rest of the E1s/DS1s may be associated with a lower priority. When migrating to a packet network,
this model can still be effectively applied. It is important to note that it is possible to define packet-based
services at a higher priority than for TDM services, as some real-time services may run on new Ethernet
ports, while other, best-effort data services are forwarded over legacy TDM networks.

3.2 Multi-Radio with ACM support
When operating in a dual-carrier configuration the system can be optionally configured to work in “multi-
radio” mode.
While in this mode, Traffic is divided among the two carriers optimally at the radio frame level without
requiring Ethernet Link Aggregation, and is not dependent on the number of MAC addresses, the number
of traffic flows or on their momentary traffic capacity. During fading events which causes 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; traffic load is balanced based on instantaneous radio
capacity per carrier and is independent of data/application characteristics (# of flows, capacity per flow
etc.).
Typical 2+0 “multi-radio” Link Configuration
F1 + F2
GE/FE 2+2
(protected) Up to 1Gbps
F1 + F2
FE connection for
HSB protection signaling
Typical 2+2 “multi-radio” Terminal Configuration with HSB protection

3.3 XPIC support
Using dual-polarization radio over a single-frequency channel means transmission of two separate carrier
waves over the same frequency, but using alternating polarities. However, the typical antennas cannot
completely isolate the two polarizations, and isolation better than 30 dB is hard to achieve. In addition,
propagation effects such as rain can cause polarization rotation, making cross-polarization interferences
unavoidable.
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
interferences, higher modulation schemes cannot and require cross-polarization interference canceller
(XPIC). The XPIC algorithm allows detection of both streams even under the worst levels of XPD such
as 10 dB. This is done by adaptively subtracting from each carrier the interfering cross carrier, at the right
phase and level. For high-modulation schemes such as 256 QAM, an improvement factor of more than 20
dB is required so that cross-interference does not limit performance anymore. XPIC implementation
involves system complexity and cost since the XPIC system requires each demodulator to cancel the other
channel interference.
3.3.1 Implementation
In a single channel application, when an interfering channel is transmitted on the same bandwidth as the
desired channel, the interference that results may lead to BER in the desired channel.
The ETSI standard specifies that for systems that carry a bit rate of STM-1 (155Mb/s) over a channel
separation of 27.5 MHz, the required co-channel interference sensitivity is 37 dB. (ETSI EN 302 217-2-2
V1.1.3 (2004-12), section D.4.3) This means that if the interfering channel is 37 dB below the desired
channel, the receiver will be at a threshold of BER=10e-6.
Ceragon products support a co-channel sensitivity of 33 dB at a BER of 10e-6. When applying XPIC, in
order to prevent interferences between the two transmitters, the system transmits the data using two
polarizations: horizontal and vertical. These polarizations, in theory, are orthogonal to each other, as
shown in the figure below
Figure 10: XPIC - Orthogonal polarizations

In a link installation, there is a separation of 30 dB of the antenna between the polarizations, and due to
misalignments and/or channel degradation, the polarizations are no longer orthogonal. This is shown in
the following illustration.
Figure 11: XPIC - misalignments and/or channel degradation impact
Note that at the right side of the figure you can see that “CarrierR” receives the “H+v” signal, which 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 in “CarrierL” = “V+h”. The XPIC mechanism takes the
data from “CarrierR” and “CarrierL” and, using a cost function, produces the desired data.
The XPIC mechanism takes the data from “CarrierR” and “CarrierL” and, using a cost function, produces
the desired data. According to the ESTI standard, the limits of the co-channel interference sensitivity are
17 dB at 1 dB degradation and 13 dB at 3 dB degradation, for the system to be at a BER of 10e-6. (ETSI
EN 302 217-2-1 V1.1.3 (2004-12), section 6.5.2.1).
Figure 12: XPIC - misalignments and/or channel degradation impact
Ceragon XPIC reaches a BER of 10e-6 at a co-channel sensitivity of 5 dB! The improvement factor in an
XPIC system is defined as the SNR@threshold of 10e-6, with or without the XPIC mechanism.

3.3.2 XPIC and Multi-Radio
XPIC radio may be used to deliver two separate data streams, such as 2xSTM1 or 2xFE, as shown at
Figure 4a. But it can also deliver a single stream of information such as gigabit Ethernet, or STM-4, as
shown at Figure 4b. The latest case requires a de-multiplexer to split the stream into two transmitters, and
it also needs a multiplexer to join it again in the right timing because the different channels may
experience a different delay. This feature is called “Multi-radio".
(a) XPIC system, delivering two independant data streams
V
data V H data
V reciever
stream 1 transmitter stream 1
OMT OMT xpic
data H data
H reciever
stream 2 transmitter stream 2
(b) XPIC system, delivering a single data stream ("Multi-Radio")

V
V H
data V reciever
transmitter Alignment data
stream De-Mux OMT OMT xpic
& Mux stream
H
H reciever
transmitter
Figure 13: (a) XPIC system delivering two independent data streams.
(b) XPIC system delivering a single data stream (multi-radio).

3.4 Integrated Carrier Ethernet support
3.4.1 Carrier Grade Ethernet
Carrier Ethernet is a high speed medium for MANs (Metro Area Networks). It defines native Ethernet
packet access to the Internet and is today being deployed more and more in wireless networks.
The first native Ethernet services to emerge were point to point-based, followed by emulated LAN
(multipoint to multipoint-based). Services were first defined and limited to metro area networks. They
have now been extended across wide area networks and are available worldwide from many service
providers.
The term "carrier Ethernet" implies that Ethernet services are "carrier grade". The benchmark for carrier
grade was set by the legacy TDM telephony networks, to describe services that achieve "five nines
(99.999%)" uptime. Although it is debatable whether carrier Ethernet will reach that level of reliability,
the goal of one particular standards organization is to accelerate the development and deployment of
services that live up to the name.
Carrier Ethernet is poised to become the major component of next-generation metro area networks, which
serve as the aggregation layer between customers and core carrier networks. A metro Ethernet network,
which uses IP Layer 3 MPLS forwarding, is currently the primary focus of carrier Ethernet activity.
The standard service types for Carrier Ethernet include:
E-Line Service: This service is employed for Ethernet private lines, virtual private lines, and
Ethernet Internet access.
Figure 14: E-Line Service Type

E-LAN Service: This service is employed for multipoint L2 VPNs, transparent LAN service,
foundation for IPTV, and multicast networks.
Figure 15: E-LAN Service Type
3.4.1.1 Metro Ethernet Forum (MEF)

The Metro Ethernet Forum (MEF) is a global industry alliance started in 2001. In 2005, the MEF
committed to this new carrier standard, and launched a Carrier Ethernet Certification Program to facilitate
delivery of services to end users.
The MEF 6 specification defines carrier Ethernet as "A ubiquitous, standardized, carrier-class Service and
Network defined by five attributes that distinguish it from familiar LAN based Ethernet". The five
attributes include:
Standardized Services
Quality of Service (QoS)
Service Management
Scalability
Reliability
3.4.1.2 The Benefits

For service providers, the technology convergence of Carrier Ethernet ensures a decrease in CAPEX and
OPEX.
Access networks employ Ethernet to provide backhaul for IP DSLAMs, PON, WiMAX, and direct
Ethernet over fiber/copper. Flexible Layer 2 VPN services, such as private line, virtual private line, or
emulated LAN, offer new revenue streams.
For Enterprises, a reduction in cost is achieved through converged networks for VoIP, data, video
conferencing, and other services.
In addition, Ethernet standardization reduces network complexity.

3.4.2 Carrier Ethernet solution overview
Ceragon's FibeAir IP-10 includes a built-in Carrier Ethernet switch. The switch operates in one of two
modes:
Carrier Ethernet Switch - Carrier Ethernet is active.
IP-10
Ethernet
Radio
User Interface
Interfaces
Carrier Ethernet
Switch
Metro Switch Mode
Smart Pipe - Carrier Ethernet is not active.
IP-10
Ethernet
Radio
User Interface
Interface
Smart Pipe Mode

Using Smart Pipe, only a single Ethernet interface is enabled for user traffic and IP-10 acts as a point-to-
point Ethernet microwave radio.
FibeAir IP-10 is equipped with an extensive Carrier Ethernet feature set which eliminates the need for an
external switch.

3.4.3 MEF Certified
The Metro Ethernet Forum (MEF) runs a Certification Program with the aim of promoting the
deployment of Carrier Ethernet in Access Networks, MANs, and WANs. The program offers certification
for Carrier Ethernet equipment supplied to service providers.
The program covers the following areas:
MEF-9: Service certification
MEF-14: Traffic management and service performance
FibeAir IP-10 is fully MEF-9 & MEF-14 certified for all Carrier Ethernet services (E-Line & E-LAN).
IP-10 meets all Carrier Ethernet Service specifications, in each category:
Standardized Services MEF-9 and MEF-14 certified for all service types (EPL, EVPL, and E-
LAN)
Scalability - Up to 500 Mbps per radio carrier
- Integrated non-blocking switch with 4K VLANs
- 802.1ad provider bridges (QinQ)
- Scalable nodal solution
- Scalable networks (1000s of NEs)
Quality of Service (QoS) - Advanced CoS classification

- Advanced traffic policing/rate-limiting
- CoS based packet queuing/buffering
- Flexible scheduling schemes
- Traffic shaping
Reliability - Highly reliable & integrated design

- Fully redundant 1+1 HSB & nodal configurations
- Hitless ACM (QPSK - 256 QAM) for enhanced radio link
availability
- Wireless Ethernet Ring (RSTP based)
- 802.3ad link aggregation
- Fast link state propagation
- <50 msec restoration time (typical)
Service Management - Extensive multi-layer management capabilities

- 802.1ag Ethernet service OA&M
- Advanced Ethernet statistics

3.4.4 Integrated QoS Support
3.4.4.1 Overview
QoS is a method of classifications and scheduling employed to ensure that Ethernet packets are forwarded
and discarded according to their priority.
QoS works by slowing unimportant packets down, or, in cases of extreme network traffic, discarding
them entirely. This leaves room for important packets to reach their destination as quickly as possible.
Basically, once the router knows how much data it can queue on the modem at any given time, it can
"shape" traffic by delaying unimportant packets and "filling the pipe" with important packets first, then
using any leftover space to fill the pipe in descending order of importance.
Since QoS cannot speed up packets, it takes the total available upstream bandwidth, calculates how much
of the highest priority data it has, puts that in the buffer, and then goes down the line in priority until it
runs out of data to send, or the buffer fills up. Any excess data is held back or "re-queued" at the front of
the line, where it will be evaluated in the next pass.
Importance is determined by the priority of the packet. The number of levels depends on the router. As
the names imply, Low/Bulk priority packets get the lowest priority, while High/Premium packets get the
highest priority.
QoS packets may be prioritized by a number of criteria, including generated by applications themselves,
but the most common techniques are MAC Address, Ethernet Port, and TCP/IP Port.
Two levels of QoS are supported in IP-10 – “Standard QoS” and “Enhanced QoS”.

3.4.4.2 Smart Pipe Mode QoS Traffic Flow
The following illustration shows the QoS flow of traffic with IP-10 operating in Smart Pipe mode.
Figure 16: Smart Pipe Mode QoS Traffic Flow
3.4.4.3 Carrier Ethernet Switch Mode QoS Traffic Flow

The following illustration shows the QoS flow of traffic with IP-10 operating in Metro Switch mode.
Figure 17: Metro Switch Mode QoS Traffic Flow

3.4.4.4 Standard QoS - Traffic Classification and Policing
The system examines the incoming traffic and assigns the desired priority according to the marking of the
packets (based on the user port/L2/L3 marking in the packet). In case of congestion in the ingress port,
low priority packets will be discarded first.
The user has the following classification options:
Source Port
VLAN 802.1p
VLAN ID
MAC SA/DA
IPv4 TOS/DSCP
IPv6 Traffic Class
After classification traffic policing/rate-limiting can optionally be applied per port/CoS.
3.4.4.5 Standard QoS - Queuing and Scheduling

The system has four priority queues that are served according to three types of scheduling, as follows:
Strict priority: all top priority frames egress towards the radio until the top priority queue is
empty. Then, the next lowest priority queue‟s frames egress, and so on. This approach ensures
that high priority frames are always transmitted as soon as possible.
Weighted Round Robin (WRR): each queue can be assigned with a user-configurable weight
from 1 to 32.
Hybrid: One or two highest priority queues as "strict" and the other according to WRR.
Shaping is supported per interface on egress

3.4.4.6 Enhanced QoS
“Enhanced QoS” is additional functionality that can optionally be enabled (requires SW license key) on
the egress path towards the radio interface in addition to the “standard QoS” processing.
It is supported in both “Smart Pipe” and “Carrier Ethernet Switch” modes.
The following main features are supported:
 8 queues
 Classification
o Classifier assigns each frame a queue + CIR/EIR designation.
o Criteria – Same as standard QoS with addition of:
 MPLS EXP bits
 UDP port
 Remarking of 802.1p bit in the frame VLAN header (optional).
 Configurable frame buffer size per queue
 Congestion management
o Tail-drop or WRED
o Color awareness (EIR/CIR support)
 Tx and dropped traffic counters per queue
 Hierarchical scheduling scheme
o 4 scheduling priorities (each queue can be independently configured to any of the 4
priorities)
o WFQ between queues in same priority with configurable weights
 Shaping per port and per queue

3.4.5 Ethernet Statistics
The FibeAir IP-10 platform stores and displays statistics in accordance with RMON and RMON2
standards.
The following groups of statistics can be displayed:
Ingress line receive statistics
Ingress radio transmit statistics
Egress radio receive statistics
Egress line transmit statistics
The statistics that can be displayed within each group include the following:
Ingress Line Receive Statistics
Sum of frames received without error
Sum of octets of all valid received frames
Number of frames received with a CRC error
Number of frames received with alignment errors
Number of valid received unicast frames
Number of valid received multicast frames
Number of valid received broadcast frames
Number of packets received with less than 64 octets
Number of packets received with more than 12000 octets (programmable)
Frames (good and bad) of 64 octets
Frames (good and bad) of 65 to 127 octets
Ingress Radio Transmit Statistics
Sum of frames transmitted to radio
Sum of octets transmitted to radio
Number of frames dropped
Egress Radio Receive Statistics
Sum of valid frames received by radio
Sum of octets of all valid received frames
Sum of all frames received with errors
Egress Line Transmit Statistics

Sum of valid frames transmitted to line
Sum of octets transmitted
Notes:
Statistic parameters are polled each second, from system startup.
All counters can be cleared simultaneously.
The following statistics are displayed every 15 minutes (in the Radio and E1/T1 performance
monitoring windows):
o Utilization - four utilizations: ingress line receive, ingress radio transmit, egress radio receive,
and egress line transmit
o Packet error rate - ingress line receive, egress radio receive
o Seconds with errors - ingress line receive

3.4.6 Ethernet resilient networks support
IP-10 supports the following Ethernet resiliency protocols:

 RSTP (802.1w)
 Carrier Ethernet Wireless Ring-optimized RSTP
 MSTP (802.1s)
3.4.6.1 RSTP/MSTP support

RSTP/MSTP (Rapid/Multiple Spanning Tree Protocol) ensures a loop-free topology for any bridged
LAN. Spanning tree allows a network design to include spare (redundant) links for automatic backup
paths, needed for cases in which an active link fails. The backup paths can be included with no danger of
bridge loops, or the need for manual enabling/disabling of the backup links. Bridge loops must be avoided
since they result in network "flooding".
RSTP/MSTP algorithms are designed to create loop-free topologies in any network design, which makes
it sub-optimal to ring topologies.
In a general topology, there can be more than one loop, and therefore more than one bridge with ports in a
blocking state. For this reason, RSTP/MSTP defines a negotiation protocol between each two bridges, and
processing of the BPDU (Bridge Protocol Data Units), before each bridge propagates the information.
This "serial" processing increases the convergence time.
3.4.6.2 Wireless Carrier Ethernet Rings

Carrier-class Ethernet rings offer topologies built for resiliency, redundancy throughout the core,
distribution and access, and a self-healing architecture that can repair potential problems before they
reach end users. Such rings are designed for increased capacity, performance, and scalability, with
beneficial increased value, stability, and a reduction in costs. By implementing Carrier-Class Ethernet
rings, providers are able to expand their LANs to WANs. FibeAir IP-10 is a superb choice for Carrier
Ethernet ring development.

3.4.6.3 Basic IP-10 Wireless Carrier Ethernet Ring
The following illustration is a basic example of an IP-10 wireless Carrier Ethernet ring.
Figure 18: Basic IP-10 Wireless Carrier Ethernet Ring

3.4.6.4 IP-10 Wireless Carrier Ethernet Ring with "Dual-Homing"
(redundant site connection to fiber aggregation network)
Figure 19: IP-10 Wireless Carrier Ethernet Ring with "Dual-Homing"

IP-10 Wireless Carrier Ethernet Ring - 1+0
Figure 20: IP-10 Wireless Carrier Ethernet Ring - 1+0
IP-10 Wireless Carrier Ethernet Ring - Aggregation Site
Figure 21: IP-10 Wireless Carrier Ethernet Ring - Aggregation Site

3.4.6.5 Carrier Ethernet Wireless Ring-optimized RSTP – Theory of operation
In a ring topology, after the convergence of RSTP, only one port is in a blocking state. We can therefore
enhance the protocol for ring topologies, and transmit the notification of the failure to all bridges in the
ring (by broadcasting the BPDU).
Ceragon's IP-10 G supports Wireless Carrier Ethernet Ring topologies. A typical ring constructed by IP10
is shown in the following illustration.
Ceragon's IP-10 supports native Ethernet rings of up to 500 Mbps in 1+0, and can reach Gigabit capacity
in a 2+0 configuration with XPIC.
Ceragon's ring solution enhances the RSTP algorithm for ring topologies, so that failure propagation is
much faster than the regular RSTP. Instead of serially propagation link by link, the failure is propagated
in parallel to all bridges. In this way, the bridges that have ports in alternate states immediately place them
in the forwarding state.
The following illustration shows an example of such a ring.
Figure 22: Ring-optimized RSTP Solution

3.4.7 End to End Multi-Layer OA&M
3.4.7.1 Overview
FibeAir IP-10 provides complete OA&M functionality at multiple layers, including:
Alarms and events
Maintenance signals (LOS, AIS, RDI, …)
Performance monitoring
Maintenance commands (Loopbacks, APS commands, …)
Figure 23: OA&M Functionality
3.4.7.2 Connectivity Fault Management (CFM)

The IEEE 802.1ag standard defines Service Layer OAM (Connectivity Fault Management). The standard
facilitates the discovery and verification of a path through 802.1 bridges and local area networks (LANs).
In addition, the standard:
Defines maintenance domains, their constituent maintenance points, and the managed objects
required to create and administer them.
Defines the relationship between maintenance domains and the services offered by VLAN-aware
bridges and provider bridges.
Describes the protocols and procedures used by maintenance points to maintain and diagnose
connectivity faults within a maintenance domain.
Provides means for future expansion of the capabilities of maintenance points and their protocols.
IEEE 802.1ag Ethernet CFM (Connectivity Fault Management) protocols consist of three protocols that
operate together to aid in debugging Ethernet networks: continuity check, link trace, and loopback.
FibeAir IP-10 utilizes these protocols to maintain smooth system operation and non-stop data flow.

3.4.8 FibeAir IP-10 Carrier Ethernet Services Example
The following is a series of illustrations showing how FibeAir IP-10 is used to facilitate Carrier Ethernet
Services. The second and third illustrations show how IP-10 handles a node failure.
Carrier Ethernet Services Based on IP-10
Figure 24: Carrier Ethernet Services Based on IP-10

Carrier Ethernet Services Based on IP-10 - Node Failure
Figure 25: Carrier Ethernet Services Based on IP-10 - Node Failure

Carrier Ethernet Services Based on IP-10 - Node Failure (continued)
Figure 26: Carrier Ethernet Services Based on IP-10 - Node Failure (continued)

3.5 Integrated Nodal Solution
Up to six IP-10 Native2 radios can be stacked with FibeAir IP-10 operating within nodal enclosures. This
configuration supports any combination of 1+0, 1+1, and 2+0/XPIC.
Each IDU can be configured as a "main" or "extension" unit. The role an IDU plays is determined during
installation by its position in the traffic interconnection topology. A main unit includes a Central
controller, management, TDM traffic cross-connect, and radio and line interfaces. An extension unit
includes radio and line interfaces.
3.5.1 IP-10 Nodal Design
Each IDU can be configured as a "main" or "extension" unit. The role an IDU plays is determined during
installation by its position in the traffic interconnection topology.
A main unit includes the following functions:
Central controller, management
TDM traffic cross-connect
Radio and line interfaces
An extension unit includes the following functions:
Radio and line interfaces
IP-10 design for the nodal solution is based on a "blade" approach. Viewing the unit from the rear, each
IDU can be considered a "blade" within a nodal enclosure. The same IP-10 unit can be used for both
terminal and nodal solutions.

Figure 27: IP-10 Rear View
Figure 28: IP-10 Nodal Enclosure
A "blade" can operate as a stand-alone unit at a tail site.
The "rack chassis" is also modular, for optimum economical

future upgrade, network design flexibility, and efficient
installation, maintenance, and expansion.
The solution is stackable and modular and forms a single

unified nodal device, with a common Ethernet Switch,
common E1 Cross-Connect, single IP address, and a single
element to manage.

3.5.2 IP-10 Nodal Stacking Concept – Advantages
For migration, the stacking concept offers an optimized tail-site solution and low initial foot-print
requirement for node sites. Additional foot-print is only required gradually as legacy equipment is being
swapped
For Greenfield, the stacking concept offers Low initial investment without compromising future growth
potential, and Risk-free deployment in face of unknown future growth pattern, including additional
capacity, additional sites, and additional redundancy.
3.5.3 IP-10 Nodal Stacking Method
IP-10 can be stacked using 2RU nodal enclosures. Each enclosure includes two slots for hot-swappable
1RU units. Additional nodal enclosures and units can be added in the field as required, without affecting
traffic. Up to six 1RU units (three adapters) can be stacked to form a single unified nodal device.
Using the stacking method, units in the bottom nodal enclosure act as main units, whereby a mandatory
active main unit can be located in either of the two slots, and an optional standby main unit can be
installed in the other slot. The switchover time is <50 msecs for all traffic affecting functions. Units
located in nodal enclosures other than the one on the bottom act as expansion units.
Radios in each pair of units can be configured as either dual independent 1+0 links, or single fully-
redundant 1+1 HSB links.
Figure 29: IP-10 Stacking Method

3.5.4 Nodal Enclosure Design
The following photos show the Nodal Enclosures and how they are stacked.
Figure 30: Extension Nodal Enclosure
Figure 31: Main Nodal Enclosure
The nodal enclosure is a scalable unit. Each enclosure can be added to another enclosure for modular rack
installation.
Figure 32: Scalable Nodal Enclosure

3.5.5 Nodal Solution Management
The nodal solution management enables users to control the node as an integrated system, and provides
the means for the exchange of information between the IDUs in the stack.
The node is managed in an integrated manner through centralized management channels. The main unit‟s
control CPU is the node‟s central controller, and all management frames received from or sent to external
management applications must pass through it.
The node has a single IP management address, which is the address of the main unit (two addresses in
case of main unit protection).
Several methods can be used for IP-10 node management:
Local terminal CLI
CLI via telnet
Web based management
SNMP
PolyView NMS represents the node as a single unit
The Web EMS allows access to all IDUs in the stack from main window
In addition, the management system provides access to other network equipment through in-band or out-
of-band network management.
To ease the reading and analysis of several IDU alarms and logs, the system time should be synchronized
to the main unit‟s time.
Feature Configuration
Some features configuration is done through the main unit only: TDM XC, user registration, login,
alarms. Other features are configured individually in each extension unit: radio parameters, Ethernet
switch configuration.
3.5.6 Nodal solution Ethernet connectivity
Ethernet traffic in a nodal configuration is supported by interconnecting IDU switches with external
cables. Traffic flow (dropping to local ports, sending to radio) is performed by the switches, in
accordance with learning tables.
Each IDU in the stack can individually be configured for "smart pipe" or "carrier Ethernet switch" modes.

3.6 Cross-Connect (XC) Unit
3.6.1 XC Basics
E1/T1 VC (Virtual Container) trails are supported, based on the integrated E1/T1 cross-connect. The XC
(cross-connect) function is performed by the active main unit. If a failure occurs, the backup main unit
takes over (<50 msecs down time). The XC capacity is 180 E1 VCs or 180 T1 VCs.
Each E1/T1 interface or "logical interface" in a radio in any unit in the stack can be assigned to any VC.
The XC is performed between two interfaces or "logical interfaces" with the same VC. XC functionality
is fully flexible. Any pair of E1/T1 interfaces, or radio "logical interfaces", can be connected. Each VC is
timed independently by the XC.
Integrated TDM Cross Connect is performed by defining end to end trails. Each trail consists of segments
represented by Virtual Containers (VCs). The XC functions as the forwarding mechanism between the
two ends of a trail.
The following illustration shows the basic XC concept.
Basic XC Operation
As shown in the illustration, trails are defined from one end of a line to the other. The XC forwards
signals generated by the radios to/from the IDUs based on their designated VCs. As in the example, The
cross connect may forward signals on Trail C from Radio 1, VC 3 to Radio 4, VC 1.

3.6.2 XC Features
Cross Connect system highlights include:

E1/T1 trails are supported based on the integrated E1/T1 cross-connect
XC capacity is 180 E1/T1 trails
XC is performed between any two physical or logical interfaces in the node, including:
E1/T1 interface
Radio “VC” (84 “VCs” supported per radio carrier)
STM1/OC3 mux VC12
Each trail is timed independently by the XC
XC function is performed by the “active” main unit
In a failure occurs, backup main unit takes over (<50 msecs down time)
Modularity and flexibility
Modular design: pay-as-you-grow
Simplicity, with minimum components (IDU, backplane)
Supports XPIC, Multi-Radio, and Diversity
The cross connect function provides connectivity for the following types of configurations:
Line to Radio Radio to Radio Line to Line
STM1/OC3
STM1/OC3
Interface
Interface
E1/T1
E1/T1
Interface
s Interfaces
E1/T1 trails are supported based on the integrated E1/T1 cross-connect (XC). The XC capacity is 180
E1/T1 bi-directional VC trails.
XC is performed between any two physical or logical interfaces in the node (in any main or expansion
unit) such as E1/T1 interface, radio VC (84 VCs supported per radio carrier), and STM1/OC3 mux
VC11/VC12. The function is performed by the “active” main unit. If a failure occurs, the backup main
unit takes over (<50 msecs down time).
Each VC trail is timed independently by the XC.

For each trail, the following end-to-end OA&M functions are supported:
Alarms and maintenance signals (AIS, RDI, etc.)
Performance monitoring counters (ES, SES, UAS, etc.)
Trace ID for provisioning mismatch detection.
A VC overhead is added to each VC trail to support the end-to-end OA&M functionality and
synchronization justification requirements.
The following illustration is an example of XC aggregation:
STM1/OC3
Interface
IP-10
Integrated
XC
IP-10 integrated
STM1/OC3 Mux
MW
Radio
Link
E1/T1 E1/T1 E1/T1

interfaces interfaces interfaces
3.6.3 TDM Trail Status Handling
For trouble shooting end-to-end E1/T1 trails across the network, additional PM (performance monitoring)
is necessary. A trail is defined as E1/T1 data delivered unchanged from one line interface to another,
through one or more radio links.
In each node along the trail path, data can be assigned to a different VC number, but its identity across the
network is maintained by a “Trail ID” defined by the user.
Additional PM functionality provides end-to-end monitoring over data sent in a trail over the network.

3.6.4 Wireless SNCP
IP-10 supports an integrated VC trail protection mechanism called Wireless SNCP (Sub network
Connection Protection).
With Wireless SNCP, a backup VC trail can optionally be defined for each individual VC trail.
For each backup VC, the following needs to be defined:
Two “branching points” from the main VC that it is protecting.
A path for the backup VC (typically separate from the path of the main VC that it is protecting).
For each direction of the backup VC, the following is performed independently:
At the first branching point, duplication of the traffic from the main VC to the backup VC.
At the second branching point, selection of traffic from either the main VC or the backup VC.
Traffic from the backup VC is used if a failure is detected in main VC.
Switch-over is performed within <50 msecs.
Wireless SNCP operation is shown in the following illustration.
E1
IP-10
B
Main
Backup
VC
VC
IP-10
A
E1

For each main VC trail, the branching points can be any XC node along the path of the trail.
IP-10
D
IP-10
B
IP-10 IP-10 E1 #2
E1 #2
C A E1 #1
IP-10
B
E1 #1
3.6.4.1 Support for Wireless SNCP in a Mixed Wireless-Optical Network

Wireless SNCP is supported over fiber links using IP-10 STM-1/OC-3 mux interfaces.
Thits feature provides a fully integrated solution for protected E1/T1 services over a mixed wireless-
optical network.
IP-10
Integrated XC
IP-10
D IP-10 integrated
STM-1/OC-3 mux
STM1/OC3
fiber link
IP-10 IP-10 MW radio link

E1 #2
C A
IP-10
B
E1 #1

3.6.4.2 TDM Rings
SNCP replaces a failed sub network connection with a standby sub network connection. In the FibeAir
product line, this capability is provided at the points where trails leave sub networks.
The switching criterion is based on SNCP/I. This protocol specifies that automatic switching is performed
if an AIS or LOP fault is detected in the working sub network connection. If neither AIS nor LOP faults
are detected, and the protection lockout is not in effect, the scheme used is 1+1 singled-ended.
The NMS provides Manual switch to protection and Protection lockout commands. A notification is sent
to the management station when an automatic switch occurs. The status of the selectors and the sub
network connections are displayed on the NMS screen.
3.6.4.3 Wireless SNCP Advantages

Flexibility
All network topologies are supported (ring, mesh, tree)
All traffic distribution patterns are supported (excels in hub traffic concentration)
Any mix of protected and non-protected trails is supported
No hard limit on the number of nodes in a ring
Simple provisioning of protection
Performance
Non traffic-affecting switching to protection (<50 msec)
Switch to protection is done at the E1/T1 VC trail level, works perfectly with ACM (no need
to switch the entire traffic on a link)
Optimal latency under protection
Interoperability
Protection is done at the end points, independent of equipment/vendor networks
Interoperable with networks that use other types of protection (such as BLSR)

3.7 ABR (Adaptive Bandwidth Recovery)
3.7.1 Overview
Ceragon proposes a novel approach to improve the efficiency of ring-based protection, using a technique
called Protected Adaptive Bandwidth Recovery (“ABR”), which enables full utilization of the
bidirectional capabilities inherent in ring technologies. With ABR, the TDM-based information is
transmitted in one direction only, while the unused protection capacity is allocated for Ethernet traffic. In
the event of a failure, the unused capacity is re-allocated for TDM transmission. In this paper, we take a
closer look at this solution, and at the technologies that are used to implement it. This technique extends
the Native2 approach to dynamic allocation of link capacity between TDM and Ethernet flows to the
network level.
3.7.2 Comparing Ring Protection Schemes
Having selected a ring topology for wireless backhauling, a range of alternative protection schemes are
available for implementation.
A major drawback of ring topology is the allocation of redundant bandwidth in order to ensure network
availability. For example, the widely-implemented SNCP 1+1 unidirectional protection scheme, which
requires the simultaneous transmission of information in both directions on the ring, causes a loss of up to
50% of the ring‟s total bandwidth capacity.
A number of techniques have been devised for recovering and utilizing the lost bandwidth. The
techniques are described in the following sections.
3.7.2.1 Ethernet & Spanning Tree Protocol

The rapid advance in Ethernet-based technologies has made the eventual migration of transport networks
from SONET/SDH to packet a foregone conclusion. This move to packet transport has challenged the
Ethernet community to exploit the resilience benefits of the physical ring structure, while adhering to the
logical tree structure required by Ethernet networks, thus ensuring a loop-free topology and avoiding
broadcast storms. These conflicting requirements have led to the development and widespread adoption
of the Rapid Spanning Tree Protocol (RSTP) and its variations.
In order to forward TDM-based traffic over Ethernet-based rings, vendors have had to adopt Pseudowire
technologies. Pseudowire, the emulation of a native service over a Packet Switched Network (PSN), is
used to map Legacy TDM or ATM services (such as E1 traffic), by creating TDM tunnels over the PSN.
While Pseudowire helped accomplish the goal of creating an Ethernet infrastructure for TDM services, it
significantly raised network cost and reduced total capacity due to the heavy encapsulation requirements.
Some microwave equipment vendors, including Ceragon, are able to provide complete, ring-based
transport networks, without the need for external networking equipment such as switches and routers.
These networks use a ring-optimized RSTP to form a logical tree over the physical wireless ring. This
logical tree topology increases the ring‟s efficiency, allowing operators to leverage the bidirectional
characteristic of the ring in order to double its bandwidth capacity, as illustrated in the figure below.

Doubling Ring Capacity using Spanning Tree Protocol
3.7.2.2 Hybrid TDM & Ethernet Systems

Hybrid systems that support the native transmission of both TDM and Ethernet flows can also be used to
reduce wasted protection bandwidth. Ceragon‟s Native2 (“Native Squared”) migration strategy offers a
unique hybrid approach, in which both Carrier Ethernet and TDM traffic are carried natively over
microwave links without using expensive encapsulation methods – resulting in significant cost savings,
while smoothing the way to a future all-IP network.
Native2 allows unparalleled flexibility in the dynamic allocation of the link‟s bandwidth into TDM and
Ethernet flows. The bandwidth available to each flow can be easily re-allocated in real time using
Ceragon‟s PolyView™ Network Management System – without resetting the link!
As the volume of data transfer in mobile networks continues to grow, the percentage of time-critical voice
& TDM traffic in these networks continues to drop. By limiting native TDM traffic to a minimum, the
amount of redundant protection-path bandwidth can be significantly minimized.

3.7.2.3 Legacy TDM Systems
As the trend toward packet-based networks gains momentum, there remains a huge demand for legacy E1
transport solutions that offer path protection. A variety of protection schemes are listed here:
Diverse Path. Usually involving redundant equipment and/or links, this scheme depends on the
availability of alternative ports, cell sites, and base stations.
Bidirectional Line Switch Ring (BLSR). A bidirectional ring, in which logical “working” and
“protection” rings forward traffic in opposite directions. Protection switching is performed on a
per-link basis (not per E1), and is often wasteful of bandwidth capacity, while possibly increasing
delay.
SNCP 1+1 Unidirectional Protection. The most widely implemented of ring-based protection
schemes. Each E1 flow consists of a primary path and a protection or standby path, represented
in Error! Reference source not found. by the blue arrow and the green arrow, respectively.
SNCP 1:1 Based. A protection scheme developed exclusively by Ceragon Networks (and described in
detail in this paper). Each E1 flow consists of a primary path, and a protection path whose
bandwidth is used for protection signaling and Ethernet traffic, represented in Error! Reference
source not found. by the blue arrow and the gray-white arrow, respectively.
Protection based on Protection based on

SNCP 1+1 SNCP 1:1
Graphical Depiction of TDM Ring Protection Schemes

3.7.2.4 Comparison of Protection Mechanisms
The following table compares each of the TDM-based ring protection schemes in regard to resiliency and
capacity:
Protection Scheme Resilience Capacity Requirements
Diverse Path Handled at cell site or base No spare capacity

station and core sites. requirement.
Very Fast. Protection is per-link,

Some spare capacity is
BLSR and not per E1. Risk of increased
required.
delay and delay variation.
SNCP 1+1 Very Fast. Phone service and For 100% recovery, ring must
Unidirectional synchronization not affected. reserve 50% spare capacity.
ABR (SNCP 1:1 Very Fast. Phone and No spare capacity

Bidirectional) synchronization not affected. requirement.
Protection Scheme Comparison
These protections schemes must be able to deal with additional challenges that add complexity to TDM
ring protection:
Hybrid Fiber/Microwave Rings. Microwave rings containing fiber segments must be able to
propagate E1 frames, fault indications, and other signals vital to the network.
Dual Homing. Protection rings remain vulnerable in situations where a fiber node suffers an
equipment failure. In order to ensure network availability, protection schemes must be able to
handle the forwarding of primary and standby transmissions from 2 different points of entry,
as shown in Error! Reference source not found. below.
2
Dual Homing with ABR-based Native

3.7.3 A Novel Approach to Bandwidth Recovery
Ceragon‟s Native2 hybrid TDM & Ethernet technology, which allows for the transport of both TDM and
packet traffic over a unified microwave link, offers additional tools for the optimization of TDM traffic
over wireless rings.
In a typical SDH network, the receiving node monitors the transmission quality at its “east” and “west”
link interfaces, and selects the direction from which it will receive transmissions. The transmitting node,
therefore, sends traffic in both the east and west directions, causing the redundant use of bandwidth. This
form of protection is known as SNCP 1+1 Unidirectional Protection, and while it can generally provide
50 millisecond protection switching, it does so by reserving large quantities of bandwidth over a very
expensive wireless spectrum.
Ceragon‟s novel approach to the reduction of redundant protection bandwidth involves a change in the
role of the transmitting element. In this approach, the transmitting element determines the direction of
information transmission – east or west. The decision is based on the monitoring of status information
that the transmitting node receives from the network. The receiving node continues to monitor both
directions for the arrival of information, as described previously. This method achieves the goal of
protecting traffic without wasting capacity on unused reserved bandwidth.
The following section provides technological details on the implementation of this innovative feature, in
which Protected Adaptive Bandwidth Recovery (“ABR”) is applied to enable better spectrum
utilization for Ethernet services.
3.7.4 Protected Adaptive Bandwidth Recovery (ABR)
In Protected Adaptive Bandwidth Recovery (ABR), a protection mechanism based on SNCP 1:1
technology, the transmitting node selects a single direction in which to transmit information. The
direction is determined independently for each E1 path, based on status information sent periodically by
the receiving node back to the transmitter.
In the standby direction, the transmitting node – along with all the nodes in the standby path to the
receiver – removes the E1 bandwidth allocation, and sends periodic signals to the receiver to help it
monitor the transmissions from east and west. (Note: This requires special handling in hybrid fiber /
microwave networks). The de-allocated (recovered) E1 bandwidth can now be utilized by Ethernet
traffic.
The receiving node continues to accept information flows from either the east or west direction, and
detects the path in which the E1 payload is actually transmitted.
When a failure occurs in the working direction, the receiving node sends a Reverse Defect Indication
(RDI) signal to the transmitter, which automatically switches to the standby path.
ABR can be selected for any number of E1 channels, and the resulting path co-exists with all other paths
in the network – be they unidirectional, bidirectional, protected, or unprotected. The case study below
describes a real-life example of how ABR delivers normal-state Ethernet capacity that may triple the
Ethernet capacity delivered when using SNCP 1+1. While malfunctions under SNCP 1+1 automatically
result in network degradation to a worst-case scenario (known as “failure state”), a network fault under
ABR results in a level of degradation that depends on the exact location of the failure, and worst-case
degradation is usually avoided.

3.7.5 Dual Homing
ABR can also be used in a dual homing configuration – in which there are 2 possible points of entry into
the ring network. This provides added resiliency in case of failure in the transmitting node. In dual
homing mode, one transmission node sends the E1 payload, while the other transmission node sends
“standby” signaling as mentioned earlier.
3.7.6 Hybrid Fiber / Microwave Networks
In segments of a microwave network that are connected by fiber-optic links, E1 frames must be
propagated onto the optical cable, and restored again on the next microwave segment. The same goes for
fault indicators. When a wireless E1 is de-allocated and its bandwidth freed for Ethernet traffic, the
periodic signals sent from the transmitter to the receiver are also propagated optically and then
regenerated on the next microwave segment.
3.7.7 ABR with ACM
Ceragon‟s Native2 technology enables the implementation of highly-efficient Adaptive Coding

Modulation (ACM) techniques in order to optimize network availability. When the received Signal-to-
Noise Ratio (SNR) degrades to a predetermined threshold, the system will pre-emptively switch to a
lower modulation level. When implemented correctly, ACM allows the platform to adjust itself,
allocating capacity in favor of high-priority traffic, and reducing the possibility of a total service outage.
Ceragon‟s implementation enables hitless and errorless operation, and it can be enhanced with QoS
mechanisms to ensure that only pre-defined low-priority traffic is dropped. For both TDM traffic and
Ethernet traffic, the operator can define traffic priorities based on network planning and on the current
stage of migration. For example, in new 3G Node Bs, voice traffic is carried by Ethernet, requiring
changes in drop precedence (giving higher priority to some Ethernet flows vis-a-vis TDM), and in path
protection as well.
3.7.8 Trail Management
In order to enable full utilization of the FibeAir platform‟s networking capabilities, Ceragon offers
PolyView™ - Ceragon‟s innovative, user-friendly Network Management System (NMS), designed for
managing large-scale wireless backhaul networks. PolyView, a fully integrated radio and networking
management platform, provides complete trail management support.
PolyView‟s efficient trail maintenance capabilities allow network technicians to create, delete, modify,
and monitor TDM trails. Trails can be built either automatically, based on user-defined trail endpoints, or
manually, according to varying degrees of manual input, with full resource control.

3.7.9 ABR – Case Study
In Error! Reference source not found. below, the traffic emanating from 18 cell sites is merged into 4
ggregation sites, making up a metro ring consisting of 28 MHz channels in a 1+0 configuration. In our
basic scenario, 2G BTSs support 4 E1s each, yielding a total of 72 E1s. SNCP 1+1 Protection is
employed.
TDM and Ethernet Aggregation Case Study
In this scenario, the main question is how to migrate the network to support 3G-based data services, given
the severe spectrum limitations. This common legacy configuration leaves us with almost no capacity for
Ethernet traffic – in this case, approximately 2.3 Mbps per site of guaranteed Ethernet traffic (assuming
64 Bytes frame size).
TDM-only Aggregation Ring with 100% Protection Based on SNCP 1+1
In the simple, TDM-only, SNCP 1+1 case presented in the figure above, all E1s flow in both directions,
meaning that 50% of the total capacity is reserved for failure states. In case of such a failure, E1s traffic
is forwarded in the opposite direction. From a capacity point of view, there is no difference between
normal state and failure state.

TDM Aggregation Ring - SNCP 1:1 Protection Bandwidth is used for Ethernet
In the SNCP 1:1 scenario depicted in the above figure, TDM-only E1s flow only in one direction. An
alternate path is reserved, but no capacity is allocated. In case of a failure, E1s are re-routed in the
opposite direction over the reserved path, receiving the non-allocated capacity.
When planning a data network for broadband services, one should compute the guaranteed traffic
(Committed Information Rate – CIR), as well as the possible upside (Excess Information Rate – EIR).
Given the availability of bandwidth for both classes, we can determine the subscriber‟s overall Quality of
Experience.
A Native Ethernet Ring with 100% or partial protection based on STP
In the scenario that appears in the figure above, when applying 100% protection – or in case of a worst
case failure, up to 14.5 Mbps of Ethernet capacity are available per site. The whole ring can support 262
Mbps of traffic. So if the 262 Mbps of protected path bandwidth is reserved but not allocated, Ethernet
capacity is increased to 29 Mbps per cell site aggregated into 116 Mbps in aggregation site S2 etc. In
Ethernet, the various failure state scenarios each have a different effect on capacity, as described in the
next section.

3.7.10 Ethernet Ring Failure States
The figure below depicts 3 failure states of varying severities: ((denoted „2‟, „3‟ and „4‟)
Non-Affecting Failure. The failure in link A3 does not affect traffic, as STP has in any case
blocked this link. Ethernet traffic does not traverse this link.
Medium-Severity Failure. The link failure at A2 causes some traffic to flow normally, while
some traffic uses the reserved alternate path.
Worst-Case Scenario Failure – A failure in link A1 causes all traffic to flow over the reserved
alternate path
Ethernet rings: Different Severities of Failure States
There is no need for an STP block in any of the failure scenarios (1-3), since at least one link in the ring is
in any case out of service.

3.7.11 Comparison of Protection Methods – To Allocate or not to Allocate
Traditional protection schemes include bandwidth reservation and actual allocation of capacity for the
alternate path. The reasoning for this was simple – in failure state, the network would not be able to
restore connectivity in a timely fashion. Today, higher processing speeds and improved network recovery
algorithms allow products such as Ceragon‟s FibeAir IP-10 to restore connectivity instantly – without
pre-allocation of capacity. Therefore, while high-priority E1 traffic is protected, alternate path capacity is
reserved, but the unused capacity can be utilized for the delivery of broadband services, allowing data
users to enjoy additional capacity when it becomes available. Let‟s review an example:
2
A Native Ring with Protected-ABR at work
While 72 E1s lines are delivered all the time, only the relevant 36 E1s are actually carried on each path.
On the Ethernet side, up to 262 Mbps of data are available in normal state, while 41 Mbps guaranteed at
failure (in the worst case scenario).
Much more, even in failures states:
 17 Mbps of data per cell site vs. 2.3 mbps in SNCP 1+1
 17 Mbps per cell site for A3 failure
 6.4 Mbps per cell site for A2/A4 failure
In summary, ABR can provide much higher capacities in all scenarios, with the exception of worst case
failures. The increased capacity allows operators to improve customer stratification, and enhance
subscribers‟ overall Quality-of-Experience (QoE) with better performance in mail delivery, content
sharing, backup services, Facebook access, and video streaming.

3.7.12 Risk Free Bandwidth Re-allocation
Ceragon‟s ABR feature allows operators to reclaim unused E1 bandwidth and re-allocate it for Ethernet
traffic – without putting critical revenue-generating services at risk. Synchronization and other critical
signaling systems are preserved.
3.7.13 ABR Benefits
Ceragon‟s ABR approach has significant benefits over Pseudowire-based techniques when applied in a
2G-to-3G migration environment. It enables an operator to enjoy the inherent benefits of hybrid TDM
and Ethernet Microwave environments:
ABR Benefits: Double Data Capacity, with no Impact on TDM in Failure State
Doubles ring capacity by using the TDM protection path to provide extra capacity for Ethernet services.
Leaves revenue-generating 2G voice traffic unaffected in the migration process, with no need for protocol
conversion.
Protects network synchronization and clock using currently deployed E1s, without the need to test and
verify new clock recovery mechanisms. Clock recovery techniques are sensitive to delay and delay
variation, and therefore have a severe impact on the operator‟s deployment strategy, often limiting the
number of links in a chain or a ring.

Streamlines the phase-out of legacy E1s in the network, easing the preparation for deployment of all-
packet backhaul networks.
QoS awareness enables the operator to associate the appropriate class of availability and class of service
to each traffic type:
Protected or not protected
Special low delay considerations
Low, medium, or high priority – TDM or Ethernet

3.7.14 Summary
Mobile carriers operating wireless backhaul networks are discovering the advantages of deploying ring-
based topologies, which include enhanced quality and reduced costs. While carriers can exploit the
inherent strengths of such networks – such as unequalled reliability, it is understood that the price to be
paid in bandwidth capacity may be too high.
Ceragon offers a range of solutions for capacity recovery, based on its Native2 TDM-to-packet migration
strategy, and on the Protected Adaptive Bandwidth Recovery (ABR) feature described in the previous
sections.
These solutions enable a risk-free migration from 2G TDM-based communications, to a mixed 2G and 3G
network carrying both TDM and Ethernet, to an all-packet multi-RAN environment. They can be
deployed both in a single link with dynamic allocation of capacity between TDM and Ethernet, and in a
ring where a protection scheme such as SNCP 1:1 can be selected to recover capacity for 3G traffic.
Ceragon‟s innovative ABR mechanism maintains TDM protection levels and bandwidth reservation, but
performs bandwidth allocation “just in time” when a fault condition occurs. As a result, the cell site
bandwidth capacity is significantly increased, while the subscriber‟s overall quality of experience is
enhanced as well. In short – Ceragon‟s solutions provide the simplest, most cost-effective, and most
reliable way to migrate to 3G while doubling capacity at “zero” incremental expense.
The flexibility of Ceragon‟s FibeAir® IP-10 family allows carriers to implement a wide range of
backhauling strategies – whether TDM-based, packet, or a combination thereof. Designed to help carriers
reach their IP migration goals, Ceragon‟s Native2 solution is an excellent platform for capacity
optimizations – in any topology.

3.8 Synchronization support
3.8.1 Wireless Network Synchronization
Synchronizing the network is an essential part of any network design plan. Event timing determines how
the network is managed and secured, and provides the only frame of reference between all devices in the
network.
Several unique synchronization issues need to be addressed for wireless networks:
Phase/Frequency Lock: Applicable to GSM and UMTS-FDD networks.
o Limits channel interference between carrier frequency bands.
o Typical performance target: frequency accuracy of < 50 ppb.
Sync is the traditional technique used, with traceability to a PRS master clock carried over PDH/SDH
networks, or using GPS.
Phase Lock with Latency Correction: Applicable to CDMA, CDMA-2000, UMTS-TDD, and
WiMAX networks.
o Limits coding time division overlap.
o Typical performance target: frequency accuracy of < 20 - 50 ppb, phase difference of
< 1-3 msecs.
o GPS is the traditional technique used.
3.8.2 Wireless IP Synchronization Challenges
Wireless networks set to deploy over IP networks require a solution for carrying high precision timing to
base stations.
Throughout the globe, legacy SDH/PDH based TDM networks are being fragmented, leading to “islands
of TDM”.
Traditional TDM services are being carried over packet networks using Circuit Emulation over Packet
techniques (CESoP).
Two new approaches are being developed in an effort to meet the challenge of migration to IP:
Various ToP (Timing over Packet) techniques
Synchronous Ethernet
3.8.3 ToP (Timing over Packet)
ToP refers to the distribution of frequency, phase, and absolute time information across an asynchronous
packet switched network.
The timing packet methods may employ a variety of protocols to achieve distribution, such as IEEE1588,
NTP, or RTP.

Figure 33: ToP (Timing over Packet)
3.8.4 Synchronous Ethernet (SyncE)
SyncE is standardized in ITU-T G.8261 and refers to a method whereby the clock is delivered on the
physical layer.
The method is based on SDH/TDM timing, with similar performance, and does not change the basic
Ethernet standards.
Figure 34: Synchronous Ethernet (SyncE)

3.8.5 Ceragon's Native2 Sync Solution
Ceragon's synchronization solution ensures maximum flexibility by enabling the operator to select any
combination of techniques suitable for the network.
Combinations of the following techniques can be used:
Synchronization using native E1/T1 trails
“PTP optimized transport” transport
o Support IEEE-1588, NTP, etc.
o Guaranteed ultra-low PDV (<0.05 msec per hop)
o Unique support ACM and narrow channels
SyncE support (G.8262)
3.8.6 Synchronization using Native E1/T1 Trails
Using this technique, each T1/E1 trail carries a native TDM clock, which is compliant with GSM and
UMTS synchronization requirements.
Figure 35: Synchronization using Native E1/T1 Trails
Ceragon's IP-10 implements PDH-like mechanism for providing the high precision synchronization of the
native TDM trails. This implementation ensures high-quality synchronization while keeping cost &
complexity low since it eliminates the need for sophisticated centralized SDH-grade "clock unit" at each
node. System is designed to deliver E1 traffic and recover E1 clock, complying with G.823
“synchronization port” jitter and wander. That means that user can use any (or all) of the system‟s E1
interfaces in order to deliver synchronization reference via the radio to remote site (e.g. Node-B).

Each trail is independent of the other, meaning that IP-10 does not imply any restrictions on the source of
the TDM trails. (Meaning that each trail can have its own clock, and no synchronization between trails is
assumed).
Each E1 trail is mapped independently over the radio frame and the integrated cross-connect elements.
Timing can be distributed over user traffic carrying T1/E1 trails or dedicated “timing” trails.
This method eliminates the need to employ emerging PTP techniques.
3.8.7 PTP optimized Transport
Ceragon's unique PTP optimized transport mechanism ensures that PTP control frames (IEEE-1588, NTP,
etc.) are transported with maximum reliability and minimum delay variation, to provide the best possible
timing accuracy (frequency and phase) meeting the stringent requirement of emerging 4G technologies
(LTE, etc.).
PTP control frames are identified using the advanced integrated QoS classifier.
Frame delay variation of <0.05msec per hop for PTP control frames is supported including when ACM is
enabled and when operation with narrow radio channels.
Figure 36: PTP Optimized Transport

3.8.8 SyncE
The SyncE technique supports synchronized Ethernet outputs as the timing source to an all-IP RBS. This
method offers the same synchronization quality provided over E1 interfaces to legacy RBS.
Ceragon's SyncE supports two modes:
“Sync from Co-Located E1” Mode

The clock for SyncE interfaces can be derived from any co-located traffic-carrying E1 interface at the
BTS site.
Figure 37: “Sync from Co-Located E1” Mode

3.8.9 “Native Sync Distribution” Mode
Synchronization is distributed natively over the radio links. In this mode, no TDM trails or E1 interfaces
at the tail sites are required!
Synchronization is provided by the E1/STM-1 clock source input at the fiber hub site (SSU/GPS).
Figure 38: Native Sync Distribution” Mode

4 Typical Configurations
4.1 Point to point configurations
4.1.1 1+0
1 IP-10, 1 RFU unit required

Integrated Ethernet switching can be enabled for multiple local Ethernet interfaces support
Figure 39: FibeAir IP-10 G-Series Typical Configurations – 1:1+0

4.1.2 1+1 HSB
2 IP-10, 2 RFU units required

Integrated Ethernet switching can be enabled for multiple local Ethernet interfaces support
Redundancy covers failure of all control and data path components
Local Ethernet & TDM interfaces protection support via Y-cables or protection-panel
<50mSecs switch-over time
Figure 40: FibeAir IP-10 G-Series Typical Configurations 1+1 HSB

4.1.3 1+0 with 32 E1s/T1s
Figure 41: FibeAir IP-10 G-Series Typical Configurations - +0 with 32 E1s/T1s
4.1.4 1+0 with 64 E1s/T1s
Figure 42: FibeAir IP-10 G-Series Typical Configurations - 1+0 with 64 E1s/T1s

4.1.5 2+0/XPIC Link, with 64 E1/T1s, “no Multi-Radio” Mode
Ethernet traffic - Each of the 2 units:

o Feeding Ethernet traffic independently to its radio interface.
o Can be configured independently for “switch” or “pipe” operation
o No Ethernet traffic is shared internally between the 2 radio carriers
TDM traffic
o Each of the 2 radio interfaces supports separate E1/T1 services
o E1/T1 Services can optionally be protected using SNCP
Figure 43:2+0/XPIC Link, with 64 E1/T1s, “no Multi-Radio” Mode

4.1.6 2+0/XPIC Link, with 64 E1/T1s, “Multi-Radio” Mode
Ethernet traffic
o One of the units is acting as the "master" unit and is feeding
Ethernet traffic to both radio carriers
o Traffic is distributed between the 2 carries at the radio frame level
o The "Master" IDU can be configured for switch or pipe operation.
o The 2nd ("Slave") IDU has all its Ethernet interfaces and functionality effectively disabled.
TDM traffic
o Each of the 2 radio interfaces supports separate E1/T1 services
o E1/T1 Services can optionally be protected using SNCP
Figure 44: 2+0/XPIC Link, with 64 E1/T1s, “Multi-Radio” Mode

4.1.7 2+0/XPIC Link, with 32 E1/T1s + STM1/OC3 Mux Interface,
no Multi-Radio, up to 168 E1/T1s over the radio
Figure 45:2+0/XPIC Link, with 32 E1/T1s + STM1/OC3 Mux Interface, no Multi-Radio, up to 168 E1/T1s
over the radio
4.1.8 1+1 HSB with 32 E1s/T1s
Figure 46: 1+1 HSB with 32 E1s/T1s

4.1.9 1+1 HSB with 64 E1s/T1s
Figure 47: 1+1 HSB with 64 E1s/T1s
4.1.10 1+1 HSB with 84 E1/T1s
Figure 48: 1+1 HSB with 84 E1/T1s

4.1.11 1+1 HSB Link with 16 E1/T1s + STM1/OC3 Mux Interface
(Up to 84 E1s/T1s over the radio)
Figure 49: 1+1 HSB Link with 16 E1/T1s + STM1/OC3 Mux Interface
(Up to 84 E1/T1s over the radio)
4.1.12 Native2 2+2/XPIC/Multi-Radio MW Link, with 2xSTM1/OC3 Mux

(up to 168 E1/T1s over the radio)
2
Figure 50: Native 2+2/XPIC/Multi-Radio MW Link, with 2xSTM1/OC3 Mux
(up to 168 E1/T1s over the radio)

4.2 Nodal Configurations
4.2.1 Chain with 1+0 Downlink and 1+1 HSB Uplink, with STM1/OC3 Mux
Figure 51: Chain with 1+0 Downlink and 1+1 HSB Uplink, with STM1/OC3 Mux

4.2.2 Node with 2 x 1+0 Downlinks and 1 x 1+1 HSB Uplink
Figure 52: Node with 2 x 1+0 Downlinks and 1 x 1+1 HSB Uplink

4.2.3 Chain with 1+1 Downlink and 1+1 HSB Uplink, with STM1/OC3 Mux
Figure 53: Chain with 1+1 Downlink and 1+1 HSB Uplink, with STM1/OC3 Mux

4.2.4 Native2 Ring with 3 x 1+0 Links + STM1/OC3 Mux Interface at Main Site
2
Figure 54: Native Ring with 3 x 1+0 Links + STM1/OC3 Mux Interface at Main Site

4.2.5 Native2 Ring with 3 x 1+1 HSB Links + STM-1 Mux Interface at Main Site
2
Figure 55: Native Ring with 3 x 1+1 HSB Links + STM-1 Mux Interface at Main Site

4.2.6 Node with 1 x 1+1 HSB Downlink and 1 x 1+1 HSB Uplink,
with STM1/OC3 Mux
Figure 56: Node with 1 x 1+1 HSB Downlink and 1 x 1+1 HSB Uplink,

4.2.7 Native2 Ring with 4 x 1+0 Links, with STM1/OC3 Mux
2
Figure 57: Native Ring with 4 x 1+0 Links, with STM1/OC3 Mux

4.2.8 Native2 Ring with 3 x 1+0 Links + Spur Link 1+0
2
Figure 58: Native Ring with 3 x 1+0 Links + Spur Link 1+0

4.2.9 Native2 Ring with 4 x 1+0 MW Links and 1 x Fiber Link (5 hops total),
with STM1/OC3 Mux
2
Figure 59: Native Ring with 4 x 1+0 MW Links and 1 x Fiber Link (5 hops total),

4.2.10 Native2 Ring with 2 x 2+0/XPIC MW Links and 1 x Fiber Link (3 hops total),
with 2 x STM1/OC3 Mux
2
Figure 60: Native Ring with 2 x 2+0/XPIC MW Links and 1 x Fiber Link (3 hops total), with 2 x STM1/OC3
Mux

5 Network Management
5.1 Overview
Ceragon provides state-of-the-art management based on SNMP and HTTP.
With the Integrated Web Based Element Manager, each device includes an HTTP based element manager
that enables the operator to perform element configuration, RF, Ethernet, and PDH performance
monitoring, remote diagnostics, alarm reports, and more.
PolyView™ is Ceragon's NMS server that includes CeraMap™ , its friendly and powerful client
graphical interface. PolyView can be used to update and monitor network topology status, provide
statistical and inventory reports, define end-to-end traffic trails, download software and configure
elements in the network. In addition, it can integrate with Northbound NMS platforms, to provide
enhanced network management. The application is written in Java code and enables management
functions at both the element and network levels. It runs on Windows 2000/2003/XP/Vista and Sun
Solaris.
Figure 61: Integrated IP-10 Web EMS and PolyView NMS

5.2 Management System
FibeAir is managed by Ceragon's management applications:
PolyView™ - End-to-End Network Manager
Web-based Management - FibeAir IP-10 Management System
Command Line Interface
5.3 Web-based Management

The FibeAir IP-10 Web Based Management is used to perform configuration operations and obtain
statistical and performance information related to the system.
5.4 PolyView
PolyView is Ceragon‟s powerful yet user-friendly NMS (Network Management System) that integrates
with other NMS platforms and systems in which no NMS is used. It provides management functions for
Ceragon‟s FibeAir systems at the network level, as well as at the individual network element level.
Using PolyView, you can perform the following for Ceragon elements in the network:
Performance Reporting
Inventory Reporting
Software Download
Configuration Management
Trail Management
View Current Alarms (with alarm synchronization)
View an Alarm Log
Create Alarm Triggers
PolyView's user interface, CeraMap™, enables fast and easy design of multi-layered network element
maps. CeraMap helps manage the network from its building stage to its ongoing maintenance and
configuration procedures.
PolyView supports all Ceragon FibeAir products, and compliments Ceragon‟s CeraView® and CeraWeb
by providing a higher (network) level of management support. PolyView is implemented in Java, which
enables it to run on different operating systems.
PolyView is security-protected, whereby configuration and software download operations can only be
performed by authorized system administrators.

5.5 CLI (Command Line Interface)
CLI (Command Line Interface) is used to perform IP-10 configuration and obtain system statistical and
performance information.
Using the CLI, you can perform configuration operations for stand-alone IP-10 units or units connected in
a stacked configuration, as well as configure several IP-10 units in a single batch command.
In a stacked configuration, all commands are available both in the main and extension units unless
otherwise stated.

IP-10 G-Series - PD - 10-2010 - V30 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

IP-10 G-Series - PD - 10-2010 - V30 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

FibeAir® IP-10 G-Series (R2)

Corporate Headquarters Asia Pacific North America

Europe MEA CALA

3 Main Features ............................................................................................. 28

FiberAir IP-10 G-Series (R2) – Product Description 3

FiberAir IP-10 G-Series (R2) – Product Description 4

FiberAir IP-10 G-Series (R2) – Product Description 5

5 Network Management .............................................................................. 103

FiberAir IP-10 G-Series (R2) – Product Description 6

FiberAir IP-10 G-Series (R2) – Product Description 7

FibeAir IP-10 G-series

FiberAir IP-10 G-Series (R2) – Product Description 8

1.2.2 Converged Fixed/Wireless Networks

Figure 1: Typical FibeAir IP-10 Applications

FiberAir IP-10 G-Series (R2) – Product Description 9

FiberAir IP-10 G-Series (R2) – Product Description 10

 Height: 42.6 mm (1RU)

 Width: 439 mm (<19")

 Depth: 188 mm (fits in ETSI rack)

Figure 2: IP-10 G-Series Front Panel and Interfaces

FiberAir IP-10 G-Series (R2) – Product Description 11

FiberAir IP-10 G-Series (R2) – Product Description 12

STM-1/OC-3 Mux T-Card

Engineering Order Wire (EOW)

User channel (V.11 Asynchronous, RS-232)

FiberAir IP-10 G-Series (R2) – Product Description 13

2.1.2 Available Assembly Options *

FiberAir IP-10 G-Series (R2) – Product Description 14

IP-10 works with:

FiberAir IP-10 G-Series (R2) – Product Description 15

• Radio ACM • Sync. Unit • Nodal enclosures • Redundancy

• Enhanced QoS • T-card slot • Cables • Capacity doubling

FiberAir IP-10 G-Series (R2) – Product Description 16

OA&M Service Management Security

Carrier Ethernet Switch TDM Cross Connect

ACM XPIC Ch-STM1/

FiberAir IP-10 G-Series (R2) – Product Description 17

Modulations: QPSK to 256 QAM

XPIC Multi-Radio Space /Frequency Diversity

Space Diversity Frequency Diversity

Figure 4: FibeAir IP-10 - Supported configurations

FiberAir IP-10 G-Series (R2) – Product Description 18

FiberAir IP-10 G-Series (R2) – Product Description 19

Figure 6: Adaptive Coding and Modulation with 8 working points

FiberAir IP-10 G-Series (R2) – Product Description 20

FiberAir IP-10 G-Series (R2) – Product Description 21

IP-10 supports two modes for Ethernet switching:

The following table lists the different aspects of IP-10 functionality.

Standardized Scalability Quality of Reliability Service

FiberAir IP-10 G-Series (R2) – Product Description 22

Feature Standard QoS Enhanced QoS*

Shaping Per port Also: per queue

Congestion management Also: Weighted Random Early Discard

* A software license key is required to enable “Enhanced QoS”

FiberAir IP-10 G-Series (R2) – Product Description 23

2.5.8 Extensive Radio Capacity/Utilization Statistics

Statistics are collected at 15-minute and 24-hour intervals

2.5.9 In-Band Management

FiberAir IP-10 G-Series (R2) – Product Description 24

2.5.11 Integrated Nodal Solution

 Same 1RU IP-10 unit can be used for terminal

 The solution is stackable and modular

 Forms a single unified nodal device