Ceragon Radio

IP-10G Advanced Course
Visit our Customer Training Portal at Training.Ceragon.Com

or contact us at training@ceragon.com
Trainee Name:
Ceragon Training Agenda

Product: IP-10 G + NMS
Course: Extended Operation and Maintenance
Duration: 5 days (Theory + Practice)
DAY ONE
Greetings and Course Opening
Introduction to MW Radio
Introduction to 802.1p/q VLAN Tagging
Introduction to CFM
IP-10 G-Series Nodal Solution Introduction
Introduction to ODU
Introduction to Adaptive Code Modulation and MRMC scripts
Physical Overview
v2.2
DAY TWO
System Architecture & Design:
Front Panel Overview

Standalone VS. Shelf
IP allocation in a shelf
Management Modes (In Band, OOB, WSC)
Switch Mode (Pipe, Managed, Metro)
Protection Mode
Installation (Practical Exercise using the Element Management System):
Standalone guidelines
Installing IDU in a shelf
Protection mode (Main and Extensions)
Setting IP address via CLI
Setting up a radio link (frequency, Link ID, RSL, TSL, ATPC, MSE, MRMC, ASP)
Setting MNG in a standalone IDU
Setting MNG in a shelf
Setting MNG using Wayside Channel
Troubleshooting Tools & Maintenance:
Using the Current Alarms

Using the Event Log
Using RMON Registers and Statistics
Performing Loopbacks
Saving Unit Information Files
Configuration File Upload / Download
Software File Download
Licensing (retrieving license and installing license on IDU)
v2.2

DAY THREE
Introduction to RSTP & Ring Topology
RSTP RING (Practical Exercise using the EMS):
Setting up an RSTP Ring

Demonstrating RSTP Protection on Trails
Demonstrating RSTP Protection on In Band Management
Simple Star Topology + RSTP (Practical Exercise using the EMS):
Shelf Configuration
SDH Trail XC Configuration
TDM Trail XC Configuration
Star Topology + In Band +Protection (Practical Exercise using the EMS):
Enabling Protection Mode

SDH Trail XC Configuration
TDM Trail XC Configuration
Trail Prioritization (Practical Exercise using the EMS):

(We shall use the same setup as in previous exercise)
Setting Trail Priority

Demonstrating Trail Prioritization with ACM and variable attenuator
v2.2

DAY FOUR
Introduction to Quality of Service:
What is QoS?
What is a Scheduler?
What is Rate Limiting?
What is Queuing?
How do we map ATM / MPLS to ETH ?
Quality of Service (Practical Exercise using the EMS):
Creating preliminary tables for classifiers & policers

Assigning Policers
Assigning Classifiers
Assigning a Scheduler
Quality of Service (Practical Exercise using the EMS):
QoS demonstration using Video Streaming (VLC)

QoS demonstration using Traffic Generator/Analyzer (when relevant)
DAY FIVE
Topology Configuration:
Adding Elements
Auto-Discovery
Adding Maps
Administration
Log Analysis and Filtering
System Configuration
Dynamic Poling
Static Poling
Configuration Broadcast
Configuration File Download
Software Download
FTP
Mail Server
Northbound
End to End Trap Configuration

Exam / Course Summary
v2.2
6/9/2010
Ceragon - Company Presentation

June 2010
Ceragon Networks
Leaders in High-Capacity Wireless Backhaul
Incorporation: 1996
Personnel: 500
Revenues in 2009: $184M
NASDAQ: CRNT
Proprietary and Confidential
Page 1
6/9/2010
Global Sales
(Reflecting FY2009 results)
EMEA: 38%
NA: 16%
APAC: 37%
CALA: 9%
Success factors:
Superior technology and professional services offering
Better cost position
Global Sales footprint with 19 offices worldwide
Strong partnerships with OEMs, distributors and VARs
Segment Breakdown H1 2009
Service
Providers
87%
Private
Networks
13%
Short Haul Links: Rapid Growth

Ceragon
Links
CeragonMarketShare
7.0%
35000
6.3%
6.0%
617427
507249
25000
4.3%
4.0%
35000 650000
554189 550000
30000
5.0%
Total
Links
TotalShortHaulvs.Ceragon
26698
450000
387020
20000
350000
300509
15000
3.0%
2.6%
10000
2.1%
2.0%
250000
13175
150000
8132
5000
1.0%
50000
2380
0.8%
50000
0.0%
2005
2005
2006
2007
2008
2006
2007
2008
2009
2009
PTPRadioShipments
TotalShortHaul NextGenerationHybridTDM/Packet&
Ceragonlinksshipments
LegacyTDM
Growthdrivers:
Highcapacity
AllIP
Totalmarket
Totalshorthaulmarket
From 0.8% market share in 2005 to 6.3% market share in 2009

4,800 links to 35,000
Grew in 2009 in shipments terms by 30%
Global short haul shipment dropped by 11%.
Source: SLR, EJL, Ceragon

4
Page 2
6/9/2010
Where We Play
LTE-Ready Mobile Backhaul
Mobile Operators
Backhaul Providers
Rural and WiMAX Backhaul

Alternative Carriers
Mobile Operators
Private Networks
Enterprise Networks
Governments: Local and State
Utilities
We Focus on Backhaul
High Capacity LTE/4G-Ready Wireless Backhaul Networks
Mobile Backhaul
WiMAX Backhaul
Private, Utility, State &

Local Government
Rural Broadband
Any access technology: Wire line or wireless, GSM, CDMA, HSPA, LTE or WiMAX
Access
Backhaul / Metro
Any service: Voice, data, personal broadband

6
Core
Page 3
6/9/2010
Strategic Partnerships for Growth
Opportunity to participate in large network deployments

Target Tier 1 carriers
Geographical spread
Maximize complete solution offering
OEM
Solution reselling
Per project
Vertical reselling
OEM 2
OEM 3
Global, Diversified Customer Base
Service
Providers
WiMAX Carriers
Private Networks
Over 200 Service Provider and hundreds of Private Networks in more than 130 Countries:*
8
Page 4
6/9/2010
Ceragon Product Portfolio
Capacity optimisation
Cost Efficiency
Aggregation
Access
First Mile
Backbone
Aggregated links
PDH & Ethernet Access
PDH/SONET & Ethernet
SONET& Ethernet
Trunk (Long Haul, High Power)
SDH Aggregation
Metro IP Migration
GbE rings
OC-3 Aggregation (N+1)

N x GbE Aggregation
FibeAir Trunk
SDH
FibeAir IP-10 G
Comprehensive mounting Portfolio

FibeAir Family
SplitMount
AllIndoor
Compactandmodular
Allindoorsolutions
RadioUnits:Fromcompacttohighpower
Radio
Units: From compact to high power
From1+0/1+1toN+1/N+0Trunk solutions
CarrierEthernet/Native2
FullOutdoor
FulloutdoorNodalsite,
N+0toN+N,fullyredundant,
AllRFunitsapplicable
IP10
CarrierEthernet/
Native2
IP10
TDM
Trunk
TDM
1500R
3200T
IP10
CarrierEthernet/Native2
10
Page 5
6/9/2010
PolyView:
Network Management System for Wireless Backhaul Networks
Reduced operational costs
End-to-end provisioning, Group
configuration
Faster & easier network

maintenance
Network View, User-friendly GUI
Quick and easy network

troubleshooting
Comprehensive FCAPS support,
easier root analysis
Greater network availability

Complete redundancy & backup
functionality
Smooth platform integration

Field proven, interoperable, multiplatform
Ceragon's Architecture Management Concept

11
Ceragon Complete Offering

Plan :
Network design, Service design, Radio

g , Synchronization
y
design,
g , Power
Design,
Consumption, Rack Layout, Project
deployment plan
Build:
Project Management, Site Survey,

Installation and Commissioning,
Documentation - As Built Site folder
Operate :
Full Training Program, Expert on Site

throughout initial operation, Managed
Services - Take part in Network operation
Maintain:
12
Remote Technical Support 24/7, S/W Repair,

H/W Repair , Advanced Replacements, Stock
Management, On Site Support, S/W Updates,
Review and Preventive Activities
Page 6
6/9/2010
Why Ceragon
Company:
Market leadership in migration of radio to packet
Widely deployed with top 3 position in high capacity radios
Global reach and breadth of portfolio
Culture of innovation
Financially sound
Products:
Risk free migration path from TDM to Ethernet
True packet microwave, MEF certified
Integrated networking functions, TDM and Ethernet
Highest possible capacities
Exceptional system gain and spectral efficiency
13
Mobile Backhaul Case Studies
14
Page 7
6/9/2010
Tata Indicom:
14K Links serving access and aggregation. All IP ready
Installing 700 links a month, from planning to commissioning

8 planners, 13 engineers, 14 project managers/directors
15
Telcel:
2600+ links migration to packet with LTE in mind
Optimize :
Tree to Rings
helpingTelceltooptimizetheradioportionofthenetwork:
Design,install.Maintain.HugeSDHinstallbase
16
Page 8
6/9/2010
Digitel:
1350+ links Delivering high capacity, anywhere.
Converged, 3G and Rural Broadband IP backhaul

All indoor and split trunks
17
Rogers :
850 Links long haul Enable 3G in rural
BTS/NB
A
Ethernet
TDM
FibeAir IP-10
BSC/RNC
BTS/NB
B
FibeAir IP-10
BTS/NB
Ceragon
packet/Hybrid
MW Network set
in a physical
FibeAir IP-10
B
BSC/RNC
A
FibeAir IP-10
FibeAir IP-10
BTS/NB
For network simplicity

reasons this part has
reasons,
being abstracted
ignoring transport, PW
and locations
B
FibeAir IP-10
5 layers of protection to sustain high capacity mobile

broadband services in remote locations
18
Page 9
6/9/2010
Long haul Case Studies
19
SDH & IP Trunk Backbone for Mobile and ISP

Converged Migration (Philippines)
Challenge:
Build a mix SDH and high

capacity
Solutions
2G
BTS
n x E1
TDM
Mix of all indoor and split TDM +
PDH
Microwav
e
Ethernet 1+1
Why Trunk?
7+0 4STM-1 and 3 GbE

Advanced Carrier Ethernet
20
features
Both interfaces use the same
radio equipment. Smooth
migration from all TDM to all
packet
Both type operate concurrently
on the same antenna and radio
branching - Native2
ECI
2G
n x E1 XDM-100
nxSTM-1
TDM
nx STM-1
Rings
3G
Node B
Cerago
n
FibeAir
Ceragon
FibeAir
E1
ECI
XDM-1000
63 E1
TDM
2G
BSC
STM-1c
STM-1
3G
RNC
Ceragon
FibeAir
Ethernet
PDH
Microwav
e
Ethernet
+
1*E1
IP MAX2
Ethernet
Ethernet
2xGbE
Ceragon
FibeAir
Huawei
Switch
Ceragon
FibeAir 2xGbE
Page 10
10
6/9/2010
Full IP Backbone for an ISP (Uruguay)
Challenge:
Native
Ethernet
Native
Ethernet
Native
Ethernet
Establishing a GbE link between sites

nxFE / GbE
200km apart spanning over jungles

and lakes
Cisco
7600
nxFE / GbE
Ceragon
FibeAir
Solutions
Ceragon
FibeAir
Ceragon
FibeAir
Cisco
7600
Ceragon
FibeAir
Service Aware Radio Link
Split, all packet 3X(2+0) multi radio

6 hopes
Abstraction layer at both ends. (Cisco
nxFE / GbE
nxFE /
GbE
routers)
31.94 km
Why Ceragon?
High Capacity and flexibility

Modularity and upgradeability
High capacity all, indoor, all packet
Cisco partnership (CTDP)
Multi layered availbilaity
8
.6
49
CANO
34 25 02.00 S
057 51 41.00 W
km
32.81 km CESP
ARTI
34 22 37.00 S
057 31 03
03.00
00 W
36
.53
km
34 21 02.00 S
057 09 44.00 W
RIPI
34 30 58.00 S
056 49 07.00 W
Quilmes
34 43 41.00 S
058 15 04.00 W
37
.5
5
km
RIBO
34 42 58.00 S
056 29 18.00 W
33
.7
7
km
VPLA
34 54 21.00 S
056 11 59.00 W
0'
40'
58
20'
57
40'
20'
Radio level, System level, e-t-e
21
All Indoor & Split Configurations LTE Ready

Backhaul (NA)
Challenge:
Ubiquitous network concept for
wireless backhaul serving remote

base station sites
Migration from 2G/3G UMTS to
HSPA and LTE
Native2
1+1
Tail site #1
Native2
1+1
Tail site #2
Native2
Fiber site
Native Ethernet service ("Ethernet VC")
Ethernet 1+1
1+1
1
1
1+1
Hub/Aggregation site
Solutions
Mix of all indoor and split TDM +
Native2
Native E1/E1 service ("E1/E1 VC")
Why Trunk
Highest possible capacities

Risk free migration for both all in
door and split
Advanced Carrier Ethernet

features
Native2 for native legacy and

packet support during the
migration path to all packet
22
Page 11
11
6/9/2010
An army network backbone (Philippines)

15 0'
AGUINALDO
Challenge:
Build an army military grade long microwave
Antipolo
CAPINPIN
Malacanang
10'
LUCBAN
TAGAYTAY
backbone
Connecting
g the Philippines
pp
islands with manyy
over the water links with distances of up to
100km
Cost-effective voice, data, and video
conferencing services to satisfy command
and control requirements
GUINYANGAN
PASACAO
PILI
IRIGA
20'
CAMALIG
MATNOG
30'
CALBAYOG
CATBALOGAN
40'
TACLOBAN
ORMOC
50'
Solutions
CAMOTES
CEBU
MACTAN
hops of 1+1 all indoor

7 GHz
Li k IInterface:
t f
STM
1
Link
STM-1
10 0'
BOHOL
10'
CAMIGUIN
CDO
MANTICAO
20'
Why Ceragon?
OZAMIZ
PAGADIAN
GANYANGAN
LACAUAN
High power split configuration 1+1

Integrated offering through a channel with
LINUGWAYAN
TAGUITE
networking, terminal and support
PULACAN
BALABAGAN
30'
ZAMBOANGA
6 40'
120 50'
40'
PC HILL
AWANG
UPI
MERCEDES
30'
20'
10'
125
WiMAX Case Studies
24
Page 12
12
6/9/2010
Case Study
Adam Internet - Australia
Broadband services to Businesses and Residential subscriber

Filling Broadband holes in Adelaide metro region (5,000 km2)
Australian government partially subsidizes the network & service
Up to 12Mbps/1Mbps service per subscriber
WiMAX RAN equipment vendor : Alvarion
Backhaul Solution: Ceragons FibeAir IP-10
25
Case Study
Adam Internet - Australia
Gaw ler
5 .0
7 km
79
0.
2.98 km
Gaw ler South

km
Kudla
4.31 km
Angle Vale Vf 2 .3 5
Why did Adam Internet choose

Ceragon?
Best solution for All-IP network
(native Ethernet)
Advanced protection schemes
(Ring)
Built in Carrier Ethernet Switch
Flexible & Scalable roll out
capabilities
Smithfield (Sa)
km
Smithfield
Uley Reserv e
k
4.12 km
Elizabeth m
6k
6 .3
6 00
6.
kkm
Burton
ELIZABETH VALE
48 York Terrace
Parafield Gardens
3.09 k
4 .1
km
4.04
5.66 km
m
7k
7 .1
7.45 km
km
3.06 km
5.2 1 km
9 km
3.1
5 km
Greenw ith Vf
Salisbury East
Salisbury South
Fairv iew Park
km
8.6 9 km
4. 48
Modbury North
Pooraka Vf
Gepps Cross
Gilles Plains
4. 32 km
Hope Valley West
km
5 .8 7
7.49
West Lakes
km
Ottow ay
GREENACRE
ATHELSTONE
km
Bev erley km
.0 6
New ton
Dudley Park
Glynde3
OSBOURNEGreenfields
4.14
5
3.0
km
3.09
km
4. 40
4
4.2
km
4.6
9k
Unley
Plympton
3.
62
km
2.9
2 .53 km
4.20
km
Wattle Park
GLENSIDE
BELAIR
Daw Park
Eden Hills
2.9 4
Warradale
km
4.14 km
3.3
Flagstaff
O'HALLORAN
HILL Hill
Coromandel Valley Vf
2.6
km
3
3.59
km
km
Somerton Park Vf
Marion East
4. 32
Haw thorn
8 km
2. 5
7 km
GLANDORE
3.29 k m
2.6 7 km
Adelaide Airport
3.23 km
27
4.
km
Henley Beach
ST PETERS
4. 72
km
Mile End
2.6
km
2.9
3.0 3
3.1
6 km
km
5 km
67
3.39 km
4 km
6.1 8 km
Aberfoyle Park Cherry Gardens
3.
HAPPY VALLEY
LONSDALE
4 km 4 km
Onkaparinga Hills
REYNELLA
VF
9.8
3
O'Sulliv an Beach
SHEIDOW PARK
4.
km
3.88
km
Woodcroft
Hackham West
Seaford Meadow s
3.90
Seaford
km
2.9 8 km
McLaren Vale
73 km
1 1.1
4
MOANA VF
km
26
Page 13
13
6/9/2010
Case Study
Allegro: Business services for Queenslands
outer metro areas
Services: All wireless 2Mbps to 200Mbps
PtP Ethernet microwave: 8Mbps to 200Mbps
WiMAX: 1Mbps to 6Mbps

Backhaul: All wireless 200-400Mbps
Service aware PtP Ethernet microwave
IP/MPLS based Ring topology

Allegro Value proposition:
Rapid delivery times
Competitive pricing scheme based on carefully designed

network to meet low TCO (Total Cost of Ownership)
27
Case Study
PtP Ethernet microwave for Backhaul and high
capacity services
Backhaul:
IP/MPLS based ring topology service
aware Ethernet microwave enhanced
with Adaptive Modulation
Business Access :
Service aware Ethernet microwave
enhanced with Adaptive Modulation
Or PtMP WiMAX
PtP
IP/MPLS
router
IP/MPLS
router
PtMP WiMAX
WiMAX
Base
Station
IP/MPLS
router
Page 14
14
6/9/2010
Case Study
South East Asia: National broaband based on
WiMAX
WiMAX Fi
Fixed/Mobile
d/M bil applications
li ti
Broadband Access
VoIP Fixed and VoIP handset
IP TV
Backhaul: All wireless 10-400Mbps
Service aware PtP Ethernet microwave
Carrier Ethernet based aggregation
Value proposition:
Access to a true Broadband service
Coverage and mobility
29
Ceragon IP Solution: Urban/Rural Link

planning
E-t-E delay <6msec
E-t-E delay <7msec
Challenges:
1. Multi hops (up
to 8)
2 Low delay for
2.
VoIP
3. Extremely
high capacity
4. Rapid
deployment
5. High
availability
6. Upgradable
from tree to
ring topology
7. Service aware
transport
* Latency figure are based on a 64Byte
30
Page 15
15
6/9/2010
Case Study
Aerea/WorldMAX: 1st Mobile WiMAX launch
already live in Amsterdam
Services: 512Kbps-8Mbps
USB WiMAX Dongle
10-40Euro
Aggregation: All wireless 200-400Mbps
High capacity service aware Ethernet radio at the

aggregation
Low capacity for Access

Aerea Value proposition:
Hotspot the size of Amsterdam.
Rapid, online order. Mail delivery within 2 days pending

on coverage
31
Low Cost, High Capacity

Carrier Ethernet Aggregation for WiMAX Backhaul
Low Capacity Link
1+1
Aggregation Site
BS site
Switch
Router
Ceragon
FibeAir
Ethernet Aggregation
Low Capacity Link

1+1
Core Site
XC
XC
Ceragon
FibeAir
BS site
PSN
Ceragon
FibeAir
Switch
Router
BS site
32
Ethernet
Microwave Link
Aggregation
Site
Page 16
16
6/9/2010
Verticals Case Studies
33
Simon says there are 9 distinct verticals
Municipality
Utility
Health
34
Defense
OPG
Education
Public Security
Broadcast
Finance
Page 17
17
6/9/2010
Case Study
Australia: Police, Fire & Emergency Services
Public Safety
Challenge:
Provide reliable digital voice communications and
data traffic
99.997% monthly average availability. (Equipment
reliability and propagation performance)
Low latency (275 m/s)
Small antenna to reduce wind load
Cost effective 1+0 space diversity configuration in
ring topology
Solution
FibeAir 1500R in ring topology
Management and VoIP EOW via 2Mb/s Ethernet
wayside channel
Why Ceragon?
High power split radio with integrated space diversity
Performance in ring topologies
Extremely reliable hardware
Versatile auxiliary channels
35
Police
HQ
Local
Police
Station
Local Police
Station
fiber
Case Study
Australia: South Australian Forestry
Municipality
Challenge:
Create a robust high capacity video
surveillance network for , bush fire
monitoring
Low visual foot print to reduce
vandalism and impact scenery
enjoyment
Solutions
6 hops 1+0 split (IP-10)
Link Interface: Ethernet
Some of the links are tree mounted
Why Ceragon?
Cost efficient high capacity native
Ethernet in a 1+0 configuration
Adaptive Coding and Modulation (ACM)
Integrated offering through a channel
(MIMP) with networking, services and
support
36
South Australian Forest

Photo: Forestry SA
Page 18
18
6/9/2010
Case Study
Australia: Housing Commission, Melbourne
Municipality
Challenge:
Create a high capacity network between 8
campuses in the city
Need to support closed circuit TV and
Telemetry monitoring for public housing
Solutions
8 link 1+0 ring
400Mbps all IP
unlicensed
53 u
ce sed spurs
spu s
Why Ceragon?
Cost efficient high capacity native Ethernet in
a 2+0 ready configuration
Upgradeable and modular
(Integrators Australia) with networking,
services and support
37
Case Study
Philippines: An army network backbone
15 0'
AGUINALDO
Defense
Antipolo
CAPINPIN
Malacanang
10'
LUCBAN
TAGAYTAY
Challenge:
Build an army military grade long microwave
backbone
Connecting the Philippines islands with many over
the water links with distances of up to 100km
Cost-effective voice, data, and video conferencing
services to satisfy command and control
requirements
Solutions
36 hops 1+1 all indoor
7 GHz
Link Interface: STM-1
Why Ceragon?
High power split configuration 1+1
networking, terminal and support
GUINYANGAN
PASACAO
PILI
IRIGA
20'
CAMALIG
MATNOG
30'
CALBAYOG
CATBALOGAN
40'
TACLOBAN
ORMOC
50'
CAMOTES
CEBU
MACTAN
10 0'
BOHOL
10'
CAMIGUIN
CDO
MANTICAO
20'
OZAMIZ
PAGADIAN
GANYANGAN
LACAUAN
PULACAN
BALABAGAN
30'
LINUGWAYAN
TAGUITE
ZAMBOANGA
6 40'
120 50'
40'
PC HILL
AWANG
UPI
MERCEDES
30'
20'
10'
125
Page 19
19
6/9/2010
Case Study
Australia: Wireless connectivity to SCADA for
Water Management solutions
Utility
Challenge:
Connect rural fully automated water gates
wirelessly to a SCADA (Supervisory Control
And Data Acquisition)
Provide reliability in extreme weather conations
where systems is required the most to open or
close the water gates
Rural and rough terrain
Solutions
7 hops 1+1
Why Ceragon?
Cost efficient high power radio units
Highly available radio link
SlipGateTM
39
Case Study
Spain: Water UTelco
Utility
Challenge:
Create a reliable high capacity multi service
network
Provide both internal data requirements such
as intra-communication voice, data, SCADA,
and surveillance systems while serving the
local government telecom needs
Solutions
60 hops 1+0/1+1/2+0 split
Multiple topology schemes
Why Ceragon?
Cost efficient high capacity native Ethernet in a
2+0 configuration
Adaptive Coding and Modulation (ACM)
networking, services and support
40
Page 20
20
6/9/2010
Case Study
Australia: Power utility data protection
Utility
Challenge:
g
Create an completely reliable low capacity
backbone for power surges monitoring and
protection serving rural power substation
Leverage highly available excessive capacity
to up sell telecom services: Voice and Data
Solutions
16 hops 2+1 all indoor
Serves as a Main link
Why Ceragon?
Cost efficient high power all indoor 2+1
configuration (upgradeable to 4+1)
41
Case Study
USA: Rural electrical cooperative
Utility
Challenge:
Create a reliable backbone to connect SCIs
20 substations and metering points
Serving SCADA, Land Mobile Radio, Video
Advanced Metering Infrastructure traffic.
Solutions
8 hops all indoor
Serves as a Main link
g topology
opo ogy
Ring
Why Ceragon?
Cost efficient, Upgradeable split Native2
solution.
Maplenet Wireless with networking, services
and support
42
South Central Indiana REMC (SCI)
Page 21
21
6/9/2010
Case Study
Australia: Alinta Gas pipeline
OPG
Challenge:
A long mission critical communication link
for a SCADA system
Solutions
43 hops 1+1
Why Ceragon?
Cost efficient high power radio units
Highly available radio link
43
1,300km
Case Study
France: Broadcast TV
Broadcast
Challenge:
Build a robust backup for a fiber
installation for the distribution of high
quality live video content along Nice
coast line
Solutions
All indoor, all packet 1+1
Alternate path for fiber
Why Ceragon?
High Capacity Ethernet in all indoor
configuration
Modularity and upgradability
MONTAGEL
LA BRAGUE
ST RAPHAEL
44
Page 22
22
6/9/2010
Case Study
Australia: TV network Intra-studio
communication
Broadcast
Challenge:
Broadcast
Create a reliable high capacity contribution site
network
Leverage highly available excessive capacity to
up sell telecom services: Voice and Data
Solutions
4 hops 1+0 split space diversity
Alternate path with links up to 70km with
Why Ceragon?
Cost efficient high power highly available native
Ethernet in a 1+0 configuration
Service protection support
45
XC
XC
Studio Site B
Ceragon
FibeAir
Native Ethernet
Microwave as an
alternate path
Ethernet switch
Fiber as a
primary
path
XC
XC
Ceragon
FibeAir
Studio Site A
Ethernet switch
Case Study
US: Operation Green Light - Kansas
Municipality
Challenge:
Intelligent Traffic Systems (ITS) where the
stoplights are connected to a wireless network
with IP video cameras and backhauled
wirelessly to their Traffic Management center.
Create a reliable high capacity packet
aggregation network
Low impact and integration with last mile
technologies such as WiMAX
Solutions
2+0
2 0 split
li
Link Interface: Ethernet in rings
Why Ceragon?
The highest possible capacities
Service protection support
46
Page 23
23
6/9/2010
Case Study
US: Intermountain Health Care - Utah
Health
Challenge:
Develop a high capacity network that fits
into their disaster recovery plan (mainly
earthquakes)
Needed control over network with back
using local Telco leased lines
Solutions
1+0 in Ring topology
Why Ceragon?
Cost efficient high power, high capacity
radio units
Modular and upgradable
47
WSA - North Germany Water Authority

Broadcast
Public
Safety
Utility
Challenge:
Connecting radar stations and light towers on the shore
Long haul over water
Solutions:
70 packet links
7Ghz high power with Space diversity
Why Ceragon?
High capacity long haul packet radio
Built in Space Diversity
Single turnkey supplier (Telent) for the compete network (offered by two of the bidders)
48
Page 24
24
6/9/2010
Australia: SP AusNet Smart metering

Broadcast
Public
Safety
Utility
Challenge:
Carrier grade radio backhaul to suit smart grid requirements (IP based) but also supports
traditional TDM based services i.e SCADA
Solutions:
80 links IP-10 1+1 radios over 4 years
Polyview NMS
Native2: Ethernet and E1
Why Ceragon?
Advanced Native Ethernet capabilities for smart grid & Native E1 for SCADA (Native2)
Outdoor cabinet installations with WIMAX requirement
Flexible, future proof solution
Single turnkey supplier (Motorola) for the compete network
49
Case study (Municipality)

Australia: Housing Commission, Melbourne
Municipality
Challenge:
Create a high capacity network between 75 campuses in the city
Support closed circuit TV, Voice and Telemetry monitoring for public
housing
Solutions:
8 link 1+0 ring

400Mbps all IP
53 unlicensed spurs
Why Ceragon?
Cost efficient high capacity native Ethernet
Upgradeable and modular, 2+0 ready configuration
Integrated offering through a channel (Integrators Australia)
50
Page 25
25
6/9/2010
Thank You
51
Page 26
26
6/10/2010
FibeAir IP10
Commissioning the Radio Link
Radio Link Common Attributes

TSL
IDU
ODU
))
RSL
ODU
IDU
To establish a radio link, we need to configure / monitor the following

parameters:
1. TX / RX frequencies set on every radio
2. RSL Received Signal [dBm]
3. MSE Mean Square Error [dB] (see MSE PPS)
4. Max. TSL Max. allowed Transmission Signal [dBm]
5. Monitored TSL Actual Transmission level [dBm]
6. Link ID must be the same on both ends
7. ATPC ON / OFF avoiding co-interferences caused by nearby antennas
8. MRMC Modem scripts (ACM or fixed capacity, channel & modulation)
9. Adaptive Power ON / OFF To allow max. transmission signal when ACM is ON
10. MAC Header Compression 45% higher throughput (Ceragon Proprietary)
Page 27
6/10/2010
LINK ID
LINK ID Antenna Alignment Process

To avoid pointing the antenna to a wrong direction (when both links share the
same frequency), LINK ID can be used to alert when such action is take.
# 101
# 101
# 102
Link ID
Mismatch
# 101
Link ID Mismatch
Page 28
6/10/2010

Both IDUs of the same link must use the same Link ID
Otherwise, Link ID Mismatch alarm will appear in Current Alarms Window
# 101
# 101
# 102
Link ID
Mismatch
# 101
Link ID Mismatch
ATPC
Page 29
6/10/2010
ATPC Adaptive Transmission Power Control

The quality of radio communication between low Power devices varies
significantly with time and environment.
This phenomenon indicates that static transmission power
power, transmission range
range,
and link quality, might not be effective in the physical world.
Static transmission set to max. may reduce lifetime of Transmitter

Side-lobes may affect nearby Receivers (image)
Main Lobe
Side Lobe

To address this issue, online transmission power control that adapts to
external changes is necessary.
In ATPC, each node builds a model for each of its neighbors, describing the
correlation between transmission power and link quality.
With this model, we employ a feedback-based transmission power control
algorithm to dynamically maintain individual link quality over time.
Page 30
6/10/2010

1. Enable ATPC on both sites
2. Set reference RSL (min. possible RSL to maintain the radio link)
3. ATPC on both ends establish a Feedback Channel through the radio link (1byte)
4. Transmitters will reduce power to the min. possible level
5. Power reduction stops when RSL in remote receiver reaches Ref. level
TSL Adjustments
ATPC
module
Monitored RSL
Radio
Transceiver
Radio
Radio
Receiver
Feedback
Radio
Receiver
Signal
Quality
Check
Site A
Ref. RSL
RSL
required
change
Site B
ATPC OFF = High Power Transmission
ATPC:
Disabled
ATPC:
Disabled
Max. TSL:
10 dBm
Max. TSL:
10 dBm
Monitored TSL:
Monitored RSL:
10 dBm
-53 dBm
Monitored TSL:
Monitored RSL:
8 dBm
-56 dBm
ATPC
module
Radio
Transceiver
Radio
Radio
Receiver
Feedback
Site A
10
Radio
Receiver
Signal
Quality
Check
Ref. RSL
RSL
required
change
Site B
Page 31
6/10/2010
ATPC ON =
Reduced Power, cost & long-term maintenance
ATPC:
Ref. RSL:
Enabled
-65
65 dBm
ATPC:
Ref RSL:
Ref.
Enabled
- 65 dBm
Max. TSL:
10 dBm
Max. TSL:
10 dBm
Monitored TSL:
2 dBm (before 10)
Monitored TSL:
2 dBm (before 8)
Monitored RSL:
-60 dBm (before 53)
Monitored RSL:
-63 dBm (before 56)
ATPC
module
Radio
Transceiver
Radio
Radio
Receiver
Feedback
Site A
11
Radio
Receiver
Signal
Quality
Check
Ref. RSL
RSL
required
change
Site B
MRMC Scripts
Page 32
6/10/2010
MRMC Multi Rate Multi Coding

1. Radio capacity is determined by Channel BW, Modulation and ACM (fixed
or adaptive)
2 Non
2.
N ACM scripts
i t ((old)
ld) are still
till available
il bl tto supportt N
Non-ACM
ACM radios
di
3. ACM TX profile can be different than ACM RX profile.
4. ACM TX profile is determined by remote RX MSE performance.
5. Remote Receiver (RX) initiates ACM profile upgrade or downgrade
6 When MSE is improved above predefined threshold
6.
threshold, RX generates a
request to the remote TX to upgrade its profile.
7. If MSE degrades below a predefined threshold, RX generates a request to
the remote TX to downgrade its profile.
13

Each ACM script has 8 profiles.
Profile Modulation
The radio capacity will be dictated by the

channel BW ((see next slide))
The lower the modulation the less sensitive
the receiver is:
QPSK
8QAM
16QAM
32QAM
64QAM
More system gain

Bigger fade margin
128QAM
256QAM(highFEC)
At lower modulation orders the radio link will

tolerate lower RSL
S levels. For example:
256QAM(lowFEC)
With 16QAM the radio will drop at (-78dBm)

whereas with 8QAM the radio will drop at
(-82dBm)
14
Page 33
6/10/2010
MRMC Adaptive TX Power

Designed to work with ACM in certain scenarios to allow higher Tx power
available at lower order modulation schemes for a given modulation scheme.
When Adaptive TX is disabled:

Maximum TX power is limited by the highest modulation configured in the MRMC ACM
script.
In other words, when link suffers signal degradation, modulation may change from
256QAM to QPSK. However, Max. power will be limited to the value corresponding as
Max. TX in 256QAM.
When Adaptive TX is Enable:

When link suffers signal degradation, modulation may change from 256QAM to QPSK.
However, Max. power will increase to compensate for the signal degradation.
16
Page 34
6/10/2010
MRMC Adaptive Power = OFF
256QAM @ Monitored TSL = 18 dBm (Max.)

Signal Degradation
= Lower bit/symbol
16QAM @ MAX. TSL = 18 dBm
17
MRMC Adaptive Power = ON
256QAM @ Monitored TSL = 18 dBm(Max.)

Signal Degradation
= Lower bit/symbol
16QAM @ Monitored TSL = 24 dBm
18
Page 35
6/10/2010
MRMC Adaptive Power

It is essential that Operators ensure they do not breach any regulator-imposed
EIRP limitations by enabling Adaptive TX.
To better control the EIRP, users can select the required
q
class ((Power VS.
Spectrum):
Class 2
Class 4
Class 5B
Class 6A
FCC
RFU C should
h ld h
i 2.01
2 01 (or
( hi
h ) ffor proper ffunctionality
ti
lit off
RFU-C
have version
higher)
Adaptive TX Power feature.
The Effective Isotropic Radiated Power (EIRP) is the apparent power transmitted towards the
receiver assuming that the signal power is radiated equally in all directions
19
Configuration
Page 36
10
6/10/2010
Radio Settings Local Radio

Spectrum Mask
FQ spacing (gap) between channels
Monitored transmission power
Monitored received signal
Monitored Mean Square Error
Required value = zero
Radio frequencies can be set

locally or on remote unit as
well (assuming links is up)
Enable / Disable
Min. target RSL (local)
Enable = no transmission
Value depends on MRMC settings
Must be identical on both IDUs
21
Enable on both IDUs to get maximum

throughput (500Mbps @ 56MHz)
22
Page 37
11
6/10/2010
Radio Settings Remote Radio
When the radio link is up, you can configure certain

parameters on the remote unit:
Make sure Remote IP is available
Remote RSL can be read
Remote TSL can be set (depends on remote MRMC script)
Remote TX MUTE can be disabled (see next slide)
Remote target RSL for ATPC can be set
23
Remote Un-Mute
Simplified scheme
Sit B is
Site
i NOT transmitting
t
itti
but receiver is still ON
Site A is
transmitting
Site B
Site A
24
Page 38
12
6/10/2010
Radio Thresholds
These settings determine the sensitivity / tolerance for triggering:

1+1 HSB switchover
Ethernet Shutdown
PM generated alarms
25
MRMC Configuration
We shall review this page using the following slides:

26
Page 39
13
6/10/2010
MRMC reading current script

MAX. Capacity
(w/out compression)
ACM Script
CH. BW
Modulation
Spectrum
Mask
ACM is on
Spectrum
Class Type
27
MRMC Reading current capacity
28
Page 40
14
6/10/2010
ThankYou!
training@ceragon.com
training@ceragon
com
29
Page 41
15
Mean Square Error
Agenda
Definition
E
Example
l
MSE & ACM
MSE values at 56MHz (case study)
MSE values at 28MHz (case study)
Troubleshooting examples
Page 42
Introduction
Definition | Example
MSE - Definition
MSE is used to quantify the difference between an estimated (expected)

value and the true value of the quantity being estimated
MSE measures the average of the squared errors:
MSE is a sort of aggregated error by which the expected value differs
from the quantity to be estimated.
The difference occurs because of randomness or because the receiver
does not account for information that could produce a more accurate
estimated RSL
Page 43
To simplify.
Imagine a production line where a machine needs to insert one part

into the other
Both devices must perfectly match
Let us assume the width has to be 10mm wide
We took a few of parts and measured them to see how many can
fit in.
The Errors Histogram

(Gaussian probability distribution function)
9
Quantity
Expected value
3
3
width
6mm 7mm
10mm 12mm
16mm
To evaluate how accurate our machine is, we need to know how many parts
differ from the expected value
9 parts were perfectly OK
6
Page 44
The difference from Expected value

Quantity
Error = 0 mm
Error = + 2 mm
Error = - 3 mm
Error = + 6 mm
Error = - 4 mm
width
6mm 7mm
10mm 12mm
16mm
To evaluate the inaccuracy (how sever the situation is) we measure how
much the errors differ from expected value
Giving bigger differences more weight than

smaller differences
Quantity
Error = 0 mm
+ 2 mm = 4
-3 mm = 9
- 4 mm = 16
+ 6 mm = 36
width
6mm 7mm 10mm 12mm
16mm
We convert all errors to absolute values and then we square them

The squared values give bigger differences more weight than smaller
differences, resulting in a more powerful statistics tool:
16cm parts are 36 units away than 2cm parts which are only 4 units away
8
Page 45
Calculating MSE
Quantity
Error = 0 mm
+ 2 mm = 4
-3 mm = 9
- 4 mm = 16
+ 6 mm = 36
width
To evaluate the total errors, we sum all the squared errors and take the
average:
16 + 9 + 0 + 4 + 36 = 65, Average (MSE) = 13
The bigger the errors (differences) >> the bigger MSE becomes
9
Calculating MSE
Error = 0 mm
Quantity
width
10mm
If all parts were perfectly produced than each error would be 0
This would result in MSE = 0
Conclusion: systems perform best when MSE is minimum

10
Page 46
MSE in digital modulation (Radios)

Let us use QPSK (4QAM) as an
example:
QPSK = 2 bits per symbol
01
00
2 possible states for I signal
2 possible states for Q signal
11
The graph shows the expected

values (constellation) of the
received signal (RSL)
10
11
= 4 possible states for the

combined signal

The black dots represent the
expected values (constellation)
of the received signal (RSL)
Q
01
00
The blue dots represent the
actual RSL
11
12
10
Similarly to the previous

example we can say that the
example,
bigger the errors are the
harder it becomes for the
receiver to detect & recover the
transmitted signal
Page 47
Q
01
00
MSE would be the average

errors of e1 + e2 + e3 + e4.
e1
e2
I
4
e4
When MSE is very small the

actual signal is very close to
the expected signal
e3
11
10
13
Q
01
00
When MSE is too big, the

actual signal (amplitude &
phase) is too far from the
expected signal
e1
e2
I
4
e4
11
14
e3
10
Page 48
Using MSE
Commissioning | Troubleshooting
15
Commissioning with MSE in EMS
When you commission your

radio link
link, make sure your MSE
is small (-37dB)
Actual values may be read

-34dB to -35dB
Bigger values (-18dB) will

result in loss of signal
16
Page 49
MSE and ACM

When the errors become too big,
we need a stronger error correction
(
)
mechanism (FEC)
Therefore, we reduce the number
of bits per symbol allocated for data
and re-assign the extra bits for
correction instead
For example
h greatt capacity
it but
b t
256QAM has
poor immune to noise
64QAM has less capacity but much
better immune for noise
ACM Adaptive Code Modulation
17
Triggering ACM with MSE

When ACM is enabled, MSE values are analyzed on each side of the link
When MSE degrades or improves, the system applies the required
modulation per radio to maintain service
ACM 28MHz, MSE [-dB]:

Profile
Mod
QPSK
8PSK
16QAM
32QAM
64QAM
128QAM
256QAM
256QAM
18
Downgrade ACM Profile

10-6 Threshold when MSE reaches
6.9
11
13 3
13.3
18
20
24.4
25
28
10.4
14.5
16 8
16.8
21.5
23.5
27.9
28.5
31.5
Page 50
Upgrade ACM Profile

when MSE reaches
11.9
16
18 3
18.3
23
25
29.4
30
33
Optimal
>30
>30
>30
>30
>30
>33
>35
>35

When ACM is enabled, MSE values are analyzed on each side of the link
When MSE degrades or improves, the system applies the required
modulation per radio to maintain service
ACM 56MHz, MSE [-dB]:

Profile
Mod
QPSK
8PSK
16QAM
32QAM
64QAM
128QAM
256QAM
256QAM

10-6 Threshold when MSE reaches
6.7
12
13 1
13.1
17.3
19.6
22.6
25
27.5
19
Upgrade ACM Profile

when MSE reaches
10.2
15.5
16 6
16.6
20.8
23.1
26.1
28.5
31
11.7
17
18 1
18.1
22.3
24.6
27.6
30
32.5
Optimal
>30
>30
>30
>30
>30
>33
>35
>35

Lets analyze the figures in the table below (we shall focus on the last line):
1.
2.
3
3.
4.
When the radio is in optimal conditions, MSE is near -35dB

When MSE drops below -27.5dB, we will experience high BER
To avoid High BER we change the profile when MSE reaches -31dB
Now that the radio is @ profile 6, the MSE must improve to -32.5 to recover
high capacity (profile 7)
Profile

Modulation 10-6 Threshold when MSE reaches
QPSK
8PSK
16QAM
32QAM
64QAM
128QAM
256QAM
256QAM
6.7
12
13.1
17.3
19.6
22.6
25
27.5
Upgrade ACM Profile

when MSE reaches
10.2
15.5
16.6
20.8
23.1
26.1
28.5
31
5 dB security window
20
10
Page 51
11.7
17
18.1
22.3
24.6
27.6
30
32.5
Optimal
>30
>30
>30
>30
>30
>33
>35
>35
ACM & MSE: Another approach

In this graph we refer to a 56MHz channel. It is easier to observe the
hysteresis of changing the ACM profile with respect to measured MSE.
As you can see,
see the radio remains @ profile 6 till MSE improves to -32.5dB:
32 5dB:
ACM
Profile
32.5
30
Profile7
Profile6
Profile5
Profile4Profile3Profile2Profile1Profile0
MSE
3128.526.123.120.816.6 15.510.2
21
ACM & MSE: Another approach

When RF signal degrades and MSE passes the upgrade point (MSE @ red point), ACM will
switch back FASTER to a higher profile (closer to an upgrade point) when MSE improves.
When RF signal degrades and MSE does not pass the upgrade point (green point) ACM
waits
it till MSE improves
i
to
t the
th point
i t off nextt available
il bl upgrade
d point
i t (takes
(t k longer
l
time
ti
to
t
switch back to the higher profile).
ACM
Profile
32.5
Profile7
30
Profile6
Profile5
3128.526.1
22
11
Page 52
MSE
Troubleshooting wrong modulation

When different settings of Modulation are set, MSE will be showing 99.99dB (Modulation Mismatch):
RSL = ~ (-45) dBm

MSE = -99.99 dB
23
RSL = ~ (-45) dBm

MSE = -99.99 dB
ThankYou!
t i i @
24
12
Page 53
3/31/2010
ACM - Adaptive Code Modulation
FibeAir IP-10s Key Feature

IP-10 utilizes a unique Adaptive Coding & Modulation (ACM)
odu at o range:
a ge Q
QPSK
S - 256QAM
56Q
Modulation
Modulation changes to maintain link when radio signal degrades

Mechanism automatically recovers to max. configured modulation when
received signal improves
Optimized for mobile backhaul all-IP and TDM-to-IP migration

2
Page 54
3/31/2010
Adaptive Coding and Modulation

Utilize highest possible modulation considering the changing environmental
conditions
Hitless & errorless switchover between modulation schemes

Maximize spectrum usage - Increased capacity over given bandwidth
Service differentiation with improved SLA
Increased capacity and availability
Adaptive Coding and Modulation
Voice & real time

services
Non-real time
services
Weak
FEC
Strong
FEC
When we engineer our services, we may assign certain services to

highest priority
Page 55
3/31/2010
ACM & SLA

When ACM is enabled and link degrades, highest priority services are
maintained
200Mbps
256QAM
Premium
112Mbps
32QAM
Silvver
128QAM
BestEffort
170Mbps
The above diagram shows an example when 28MHz is used

5
IP-10 Enhanced ACM Support

8 modulation/coding working points (~3db system gain for each point
change)
Hit-less and Error-less modulation/coding changes based on signal

quality
li
Throughput per radio carrier:

10 to 50 Mbps @ 7MHz Channel
25 to 100 Mbps @ 14MHz Channel
45 to 220 Mbps @ 28 MHz Channel
90 to 500 Mbps
p @ 56 MHz Channel
MSE is analyzed to trigger

ACM modulation changes
Zero downtime - A must for mission-critical services
6
Page 56
3/31/2010
IP-10 radio capacity - ETSI

7MHz
ACM
Point
Modulation
14MHz
# of
E1s
Ethernet
Capacity
(Mbps)
ACM
Point
# of
E1s
Ethernet
Capacity
(Mbps)
QPSK
9.5 13.5
QPSK
8 PSK
14 20
8 PSK
12
29 - 41
16 QAM
19 28
16 QAM
18
42 - 60
32 QAM
10
24 34
32 QAM
20
49 70
64 QAM
12
28 40
64 QAM
24
57 82
128 QAM
13
32 46
128 QAM
29
69 - 98
256 QAM
16
38 54
256 QAM
34
81 - 115
256 QAM
18
42 60
256 QAM
37
87 - 125
28MHz
20 - 29
56MHz
40MHz
Modulation
ACM
Point
Modulation
# of
E1s
Ethernet
Capacity
(Mbps)
ACM
Point
Modulation
# of
E1s
Ethernet
Capacity
(Mbps)
Modulation
ACM
Point
# of
E1s
Ethernet
Capacity
(Mbps)
76 - 109
QPSK
16
38 - 54
QPSK
23
56 - 80
QPSK
32
8 PSK
22
53 - 76
8 PSK
34
82 - 117
8 PSK
48
114 - 163
16 QAM
32
77 - 110
16 QAM
51
122 - 174
16 QAM
64
151 - 217
32 QAM
44
103 - 148
32 QAM
65
153 - 219
32 QAM
75
202 - 288
64 QAM
54
127 - 182
64 QAM
75
188 - 269
64 QAM
75
251 - 358
128 QAM
66
156 - 223
128 QAM
75
214 - 305
128 QAM
75
301 - 430
256 QAM
71
167 - 239
256 QAM
75
239 - 342
256 QAM
75
350 - 501
256 QAM
75
183 - 262
256 QAM
75
262 - 374
256 QAM
75
372 - 531
Ethernet capacity depends on average packet size

IP-10 radio capacity - FCC

10MHz
Modulation
ACM
Point
20MHz
# of
T1s
Ethernet
Capacity
(Mbps)
ACM
Point
Ethernet
Capacity
(Mbps)
28 - 40
QPSK
13 18
QPSK
16
8 PSK
10
19 27
8 PSK
22
39 - 56
16 QAM
16
28 40
16 QAM
32
57 - 81
32 QAM
18
32 46
32 QAM
38
67 - 96
64 QAM
24
42 61
64 QAM
52
93 - 133
128 QAM
28
50 71
128 QAM
58
102 - 146
256 QAM
30
54 78
256 QAM
67
118 - 169
256 QAM
33
60 85
256 QAM
73
129 - 185
40MHz
Modulation
ACM
Point
# of
T1s
30MHz
Modulation
# of
T1s
Ethernet
Capacity
(Mbps)
ACM
Point
Modulation
# of
T1s
Ethernet
Capacity
(Mbps)
ACM
Point
50MHz
Modulation
# of
T1s
Ethernet
Capacity
(Mbps)
65 - 93
QPSK
22
39 - 55
QPSK
31
56 - 80
QPSK
37
8 PSK
35
62 - 89
8 PSK
46
82 - 117
8 PSK
59
105 - 150
16 QAM
52
93 - 133
16 QAM
69
122 - 174
16 QAM
74
131 - 188
32 QAM
68
120 - 171
32 QAM
84
153 - 219
32 QAM
84
167 - 239
64 QAM
80
142 - 202
64 QAM
84
188 - 269
64 QAM
84
221 - 315
128 QAM
84
164 - 235
128 QAM
84
214 - 305
128 QAM
84
264 - 377
256 QAM
84
185 - 264
256 QAM
84
239 - 342
256 QAM
84
313 - 448
256 QAM
84
204 - 292
256 QAM
84
262 - 374
256 QAM
84
337 - 482
Ethernet capacity depends on average packet size

Page 57
3/31/2010
IP-10 Enhanced radio capacity for Ethernet traffic

Intelligent Ethernet header compression mechanism (patent pending)
Improved effective Ethernet throughput by up to 45%
No affect on user traffic
Ethernet
packet size (bytes)
Capacity increase by
compression
64
45%
96
29%
128
22%
256
11%
512
5%
IP-10 Native2 radio dynamic capacity allocation

Example: 28MHz channel bandwidth
Example
Modulation
32QAM
128QAM
256QAM
All Ethernet
112Mbps
170Mbps
200Mbps
20 E1s + Ethernet
20 E1s + 66Mbps
20 E1s + 123Mbps 20 E1s + 154Mbps
44 E1s + Ethernet
44 E1s + 10Mbps
44 E1s + 67Mbps
44 E1s + 98Mbps
66 E1s + Ethernet
66 E1s + 15Mbps
66 E1s + 47Mbps
75 E1s + Ethernet
Example
traffic mix
10
75 E1s + 25Mbps
Page 58
3/31/2010
Adaptive Coding & Modulation (ACM)

Its all about handling data...
Current Microwave systems are designed with

Availability Equal for all Services
nXT1/E1
?
99.99 %
Less availability can be accepted for many data services

Need for Services Classification :
Microwave systems shall treat services in different ways
11
Fewer Hops
1.28km fix rate

200Mbps at 99
99.999%
999%
2.5km adaptive rate

200Mbps at 99.99% and 40Mbps at 99.999%
1km
2km
3km
Assuming: 18GHz link, 28MHz channel, 1 ft antenna, Rain zone K (42mm/hr)
Optional solution for several planning constrains

Example - Reducing Hops count until reaching fiber site
12
Page 59
3/31/2010
Decreased tower loads: Wind, Space, Weight

4.5km/2.8 miles path, 56MHz channel, 400Mbps, 256QAM, 99.999% availability
Without Adaptive Modulation: requires 4 ft antennas

Modulation
Throughput (Mbps)
Availability (%)
Unavailability of
modulation
Outage 5 minutes and 15 seconds

256QAM (2)
400
99.999
4min, 28sec
With Adaptive Modulation: requires 1 ft antennas

Modulation
Throughput (Mbps)
Availability (%)
Unavailability of
modulation
Outage 5 minutes and 15 seconds

5min,, 3sec
QPSK
80
99.999
8PSK
120
99.998
9min, 3sec
16QAM
160
99.997
11min, 4sec
32QAM
210
99.996
16min, 42sec
64QAM
260
99.995
24min, 35sec
37min, 35sec
128QAM
320
99.992
256QAM (1)
360
99.989
55min, 33sec
256QAM (2)
400
99.985
1hr,18min, 13sec
Assumed rain zone K, 23 [GHz] band

Source: Ceragon Networks
ACM Benefit in TDM to IP migration scenario

SMOOTH Migration
14
Typical 4E1 radio

QPSK
7MHz channel
99.999% availability
4xE1
7MHz channel
Upgrade to 4E1 + 40Mbps Ethernet

5 TIMES THE CAPACITY
SAME ANTENNAS
Same 7MHz channel
QPSK 256QAM with ACM
99.999% availability for the E1s
Low cost, scalable, pay as you grow
4xE1 + 40Mbps
Ethernet
7MHz channel
Page 60
3/31/2010
Traffic Prioritization
When ACM is enabled and link degrades, highest priority services are
maintained while low services are dropped
When link capacity is recovered, low services are recovered as well
QoS is applied first to drop ETH low services
(e.g. Customer is advised to assign configure QoS to maintain In-Band
Management when link capacity degrades)
E1/T1 traffic has higher priority over Ethernet traffic
Each E1/T1 can be configured as High/Low priority
TDM Low priority is dropped first
TDM High priority is dropped according to order of configuration
15
ACM Working Boundaries

Link capacity is determined according to License and applied script
ACM Script consists of Channel BW, max. Capacity and Modulation
Highest modem script is applied using MRMC configuration window
When Automatic State Propagation is enabled, GbE (SFP) port can be
configured to shutdown when ACM is below a pre-defined script
16
Page 61
3/31/2010
ThankYou!
training@ceragon
com
17
Page 62
Introductionto802.1P/Q
Prerequisites
Prior to taking this module, trainee should be familiar with the

following:
Ethernet Topologies
OSI 7 Layers model
Advanced Operation & Maintenance Course
1
Page 63
Agenda
Agenda
What is VLAN?
Advantages for using VLAN
Regular Ethernet frame
Tagged frame structure
Types of VLAN
Types of connections
802.1P implementations
What is VLAN?
A Layer 2 Protocol which enables enhanced

traffic maneuvers :
Prioritization
Filtering
Provisioning
Mapping (e.g. - ATM to/from ETH)
2
Page 64
What is VLAN?
Regular ETH networks forward broadcast frames to all endpoints
What is VLAN?
VLAN networks forward broadcast frames only to pre-defined ports
(Profile Membership)
VLAN 1
Switch ports
VLAN 547
3
Page 65
Advantages of VLAN
Breaking large networks into smaller parts (Formation of virtual workgroups)

Simplified Administration (no need for re-cabling when user moves)
Improving Broadcast & Multicast traffic utilization
Mapping expensive backbones (ATM) to simpler & cheaper ETH backbones
Security establishing tunnels / trunks through the network for dedicated
users ((traffic
ff between VLANs is restricted).
)
Before we start explaining bit by bit, what is VLAN

and how does it work, let us review first the
structure of a regular ETH frame
4
Page 66
Untagged Ethernet Frame
FCS is created by the sender and recalculated by the receiver
Preamble+SFD
DA
8 Bytes
SA
6 Bytes
Length/Type
6 Bytes
2 Bytes
DATA+PAD
FCS
46 - 1500 Bytes
4 Bytes
(32-bit
CRC)
Minimum 64 Bytes < FRAME SIZE < Maximum 1518 Bytes
Length / Type < 1500 - Parameter indicates number of Data Bytes

Length / Type > 1536 - Parameter indicates Protocol Type (PPPoE, PPPoA, ARP etc.)
Tagged Ethernet Frame

Additional information is inserted
Frame size increases to 1522 Bytes
4 Bytes
Preamble+SFD
DA
SA
VLANTAG
TPID=0x88A8
Length/Type
TCI
PTAG
TPID = Tag protocol ID
TCI = Tag Control Information
CFI = 1 bit canonical Format Indicator
10
DATA+PAD
3 Bit
CFI
1 Bit
5
Page 67
VLANID
12 Bit
FCS
Tagging a Frame
VLAN ID uses 12 bits, therefore the number of maximum VLANs is 4096:

2^12 = 4096
VID 0 = reserved
VID 4090-4096 = reserved (dedicated for IP-10s internal purposes such as MNG etc.)
VID 1 = default
After tagging a frame, FCS is recalculated

CFI is set to 0 for ETH frames, 1 for Token Ring to allow TR frames over
ETH backbones (some vendors may use CFI for internal purposes)
11
TPID / ETHER-Type / Protocol Type

TPID in tagged frames in always set to
0x8100
p
that yyou understand the
It is important
meaning and usage of this parameter
Later when we discuss QoS, we shall

demonstrate how & why the system
audits this parameter
12
Protocoltype
Value
TaggedFrame
0x8100
ARP
0x0806
Q i Q (CISCO)
QinQ(CISCO)
0 8100
0x8100
QinQ(othervendors)
0x88A8
QinQ(othervendors)
0x9100
QinQ(othervendors)
0x9200
RARP
0x8035
IP
0x0800
IPv6
0x86DD
PPPoE
0x8863/0x8864
MPLS
0x8847/0x8848
ISIS
0x8000
LACP
0x8809
802.1x
0x888E
6
Page 68
VLAN Membership: By Port

Every switch port is associated with specific VLAN membership
PRO easy configured
CON no user mobility
13
8
VLAN 100
VLAN 1
VLAN 9
VLAN 333
VLAN 22
VLAN 5
For example ports 1,2 & # can see each other but cannot PING
other ports (different VLAN membership)
VLAN Membership: By MAC

PRO user mobility, no
reconfiguration when PC
moves
CON needs to be assigned
initially, not an easy task
with thousands of
endpoints
00:20:8f:40:15:31
00:20:8f:40:15:ef
00:20:8f:40:15:30
VLAN 44
00:33:ef:38:01:23
00:33:ef:38:01:a0
00:33:ef:38:01:25
VLAN 5
14
7
Page 69
VLAN Membership: By Subnet (L3 VLAN)

Membership is based on the Layer 3 header
No process of IP address is done
Main disadvantage longer overall throughput
10.10.10.12
10.10.10.122
10.10.10.13
VLAN 44
11.1.1.10.12
11.1.1.10
11.1.1.10.23
VLAN 5
15
Port Types
Access Port a port which is not aware of VLANs
(Cannot tag outgoing frames or un-tag incoming frames)
A
Device unaware of VLANs
transmits untagged
(regular) ETH frames
16
VLANawareSwitch
Switch tags the ingress

frames with VID according
to specific Tagging
mechanism
8
Page 70
Port Types
Trunk Port a port which is aware of VLANs
(Can tag or un-tag incoming frames)
A
Device unaware of VLANs
transmits untagged
(regular) ETH frames
VLANawareSwitch
Switch tags the ingress frames with VID according to

specific Tagging mechanism
Switch un-tags frames with VID received from network
and delivers untagged frames to Access ports
17
Port Types
Trunk Port can carry tagged frames with different VIDs.
This requires Port Membership configuration.
VLANawareSwitch
T
A
ThisportisnotamemberoftheTrunk
portmembershiplist,hence,trafficis
discarded
18
9
Page 71
Q-in-Q
Additional VLAN (S-VLAN) is inserted
Frame size increases to 1526 Bytes
Preamble+SFD
DA
TPID 0 88A8
TPID=0x88A8
PTAG
3 Bit
SA
4 Bytes
4 Bytes
S VLAN
C VLAN
TCI
Length/Type
TPID 0 8100
TPID=0x8100
CFI VLANID
1 Bit
DATA+PAD
TCI
PTAG
12 Bit
19
Port Types
Q-in-Q (A.K.A. Double TaggingVLAN Encapsulation)
+
VLAN
CN
awareSwitch
PN
E h
Enhanced
d security
it nott exposing
i original
i i l VID
Improved flexibility of VID in the network
(Ingress VID was already assigned in the network)
20
10
Page 72
FCS
CFI
VLANID
Introduction to QoS / CoS
21
Mapping ATM QoS over ETH CoS (RFC 1483)

We can extend the benefits of ATM QoS into Ethernet LANs to guarantee Ethernet priorities
across the ATM backbone. A L2 switch or L3 router reads incoming 802.1p or IP ToS priority
bits, and classifies traffic accordingly.
To match the priority level with the appropriate ATM service class and other parameters, the
switch then consults a mapping table with pre-defined settings.
P-Tag 6
CBR
P-Tag 4
VBR
P-Tag 0
UBR
Hub
Site
GE
FE/GE
RNC
GE
n x T1/E1
Tail site
22
FibeAir
IP-10
IP-10
STM1/
OC3
ATM
Router
11
Page 73
MPLS
Router
Core
Site
BSC/MSC
Mapping ETH to MPLS and vice versa

IP-10s L2 switch can take part in the process of transporting
services through MPLS core
Frames/services are mapped to MPLS FECs according to:

VLAN ID mapped to MPLS EXP bits
VLAN P-Bit mapped to MPLS EXP bits
Hub
Site
GE
FE/GE
RNC
GE
n x T1/E1
Tail site
FibeAir
IP-10
STM1/
OC3
IP-10
STM1/
OC3
MPLS
Router
MPLS
Router
Core
Site
23
BSC/MSC
VLAN P-Bit Remap (Traffic Classes)

IEEE Recommendation
The following
Th
f ll i table
t bl shows
h
IEEE definition of traffic
classes
It shows the ingress options
for P-Tag VS. egress P-tag
The number of egress
priorities (classes) depend
on the number of assigned
queues
Ingress
PTags
NumberofAvailableTrafficClasses
1
0(default)
EgressPTag
24
12
Page 74
VLAN P-Bit Remap (Traffic Classes)

The default priority used for transmission by end stations is 0
With a single queue, there are no choices. All traffic is Best Effort
Multiple queues are needed to isolate Network Control from the user data traffic
25
Acronyms
26
ETH Ethernet
NIC Network Internet Card
VID Vlan
Vl ID
VLAN Virtual LAN
P-TAG Priority Tag, Priority Bits
CFI Canonical Format Indicator
TPID Tag Protocol Identifier
FCS Frame Check Sequence
DA Destination Address
SA Source Address
QoS Quality of Service
13
Page 75
Associated IEEE Standards
IEEE802.3:Ethernet(Max.framesize=1518bytes)
IEEE802.3ac:Ethernet(Max. frame size = 1522 bytes)
IEEE802.1d:MACBridgefirstintroducedtheconceptofFiltering
Servicesinabridgedlocalnetwork
IEEE802.1q:VLANTagging
IEEE802.1p:PriorityTagging/Mapping
IEEE802.1ag:OAM(CFM)
27
ThankYou!
28
14
Page 76
6/13/2010
Ceragon in a Nutshell
Ceragon FibeAir Family
OA&M
Service Management
Carrier Ethernet Switch
TDM Cross Connect
ACM
Gigabit
Ethernet
Fast
Ethernet
Security
Native2
XPIC
Radio
Ethernet + TDM
Multi
Radio
10-500Mbps, 7-56MHz
SD/FD
E1/T1
Ch-STM1/
OC3
Terminal
Mux
RFU (6-38GHz)
2
Page 77
6/13/2010
RFUs
FibeAir RFU-HP
FibeAir RFU-HS
FibeAir RFU-P
FibeAir RFU-C
FibeAir RFU-D
Standard power
High power
(e.g. Smaller antennas reduced cost)
CERAGON MAST - Mobile Architecture

for Service Transport
ISPs
Fixed
Networks
Cable
TV
CellularBackhaul
RuralAccess
PDH
xDSL
Subscribers
IPDSLAM
IP/ETH
Customer
Network
SDH/SONETRING
PSTN
4
Page 78
6/13/2010
CERAGON MAST - Mobile Architecture

for Service Transport
Complete end-to-end network architecture, powering operators
with a highly efficient, scalable and cost-optimized solution for
scaling up their networks
Regardless of transport technology or the service being carried MAST

offers a complete set of tools to ensure high QoS & full OA&M
functionality across entire networks
Allows risk-free migration to IP/Ethernet
Simplifies fixed and mobile network designs
Giving
a single
point of contact for all the transport,
networking
g operators
p
g p
p
g and service
delivery needs
A true end-to-end, service-oriented package
MAST allows customers to design highly scalable, flexible and future-proof

networks in a simple and cost efficient manner
5
FibeAir IP-10R1 Main features
Unique Adaptive Coding & Modulation (ACM)

Enhanced radio efficiency and capacity for Ethernet traffic
Integrated Carrier Ethernet switching functionality
Enhanced QoS for differentiated services
Supported configurations
1+0
1+1 HSB Fully-redundant!
Nodal solution with ring
Extensive and secure management solution
6
Page 79
6/13/2010
IP-10R1 Integrated Carrier Ethernet switch

3 modes for Ethernet switching:
Metro switch Carrier Ethernet switching is enabled

Managed Switch 802.1 L2 switch
Smart pipe Carrier Ethernet switching is disabled
Only a single Ethernet interface is enabled for user traffic
The unit operates as a point-to-point Ethernet MW radio
IP-10
IP-10
Ethernet
User
Interfaces
Ethernet
User
Interface
Radio
interface
Radio
interface
Carrier Ethernet
Switch
Smart pipe mode
Metro/Managed switch mode
Extensive Carrier Ethernet feature-set

eliminates the need for external switches
IP-10R1 radio capacity - ETSI

7MHz
ACM
Point
Modulation
14MHz
# of
E1s
Ethernet
Capacity
(Mbps)
ACM
Point
Modulation
# of
E1s
Ethernet
Capacity
(Mbps)
20 - 29
QPSK
9.5 13.5
QPSK
8 PSK
14 20
8 PSK
12
29 - 41
16 QAM
19 28
16 QAM
16
42 - 60
32 QAM
10
24 34
32 QAM
16
49 70
64 QAM
12
28 40
64 QAM
16
57 82
128 QAM
13
32 46
128 QAM
16
69 - 98
256 QAM
16
38 54
256 QAM
16
81 - 115
256 QAM
16
42 60
256 QAM
16
87 - 125
28MHz
ACM
Point
56MHz
40MHz
Modulation
# of
E1s
Ethernet
Capacity
(Mbps)
ACM
Point
Modulation
# of
E1s
Ethernet
Capacity
(Mbps)
ACM
Point
Modulation
# of
E1s
Ethernet
Capacity
(Mbps)
76 - 109
QPSK
16
38 - 54
QPSK
16
56 - 80
QPSK
16
8 PSK
16
53 - 76
8 PSK
16
82 - 117
8 PSK
16
114 - 163
16 QAM
16
77 - 110
16 QAM
16
122 - 174
16 QAM
16
151 - 217
32 QAM
16
103 - 148
32 QAM
16
153 - 219
32 QAM
16
202 - 288
64 QAM
16
127 - 182
64 QAM
16
188 - 269
64 QAM
16
251 - 358
128 QAM
16
156 - 223
128 QAM
16
214 - 305
128 QAM
16
301 - 430
256 QAM
16
167 - 239
256 QAM
16
239 - 342
256 QAM
16
350 - 501
256 QAM
16
183 - 262
256 QAM
16
262 - 374
256 QAM
16
372 - 531
8
Page 80
6/13/2010
Wireless Carrier Ethernet Ring

Example configuration (1+0 ring)
N x GE/FE
N x GE/FE
N x GE/FE
Wireless
Carrier Ethernet
Ring
(up to 500Mbps)
Integrated Ethernet
Switching
9
N x GE/FE
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
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)
In addition, Native2 ensures:

Very low link latency of <0.15 msecs @ 400 Mbps.
Very low overhead mapping for both ETH & TDM traffic
High precision native TDM synchronization distribution
10
Page 81
6/13/2010
NG-SDH/SONET complementary solution

Carrier Ethernet at the access, NG-SDH/SONET at the aggregation
Carrier Ethernet (MW links)
SDH/SONET (Hybrid Fiber/MW)
Native Ethernet
Ethernet over SDH/SONET
Hub
Site
GE
FE/GE
RNC
GE
Tail site
FibeAir
IP-10
FibeAir
IP-10
NG-SDH
MSPP
NG-SDH
MSPP
Core
Site
Ethernet services are

transported natively
over Carrier Ethernet
based MW radio links.
NG-SDH/SONET MSPP
node acts as gateway
between the Carrier
Ethernet and NGSDH/SONET based
networks.
Ethernet services
are mapped over
SDH/SONET
SDH/SONET MW
links are used where
fiber connections not
available
11
IP/MPLS complementary solution

Carrier Ethernet at the access, IP/MPLS at the aggregation
Carrier Ethernet (MW links)
IP/MPLS (Hybrid Fiber/MW)
Native Ethernet
Ethernet PWs or IP routing
Hub
Site
GE
FE/GE
RNC
GE
Tail site
FibeAir
IP-10
FibeAir
IP-10
MPLS
Router
MPLS
Router
Core
Site
Ethernet services are

transported natively
over Carrier Ethernet
based MW radio links.
IP/MPLS edge router acts

as gateway between the
Carrier Ethernet and
IP/MPLS based networks.
Both Ethernet and

E1/T1 services are
mapped over MPLS
using pseudo-wires
or routed using IP
High-capacity IP/MPLSaware" Ethernet MW

radio is used where fiber
connections not available
12
Page 82
6/13/2010
IP-10R1 integrated QoS support - overview

4 CoS/priority queues per switch port
Advanced CoS/priority classification based
on L2/L3 header fields:
Priority Queues
Source Port
VLAN 802.1p
802 1
VLAN ID
IPv4 DSCP/TOS, IPv6 TC
Highest priority to BPDUs
W1 - Highest
Hi h t priority
i it
Classify
Arrivals
Advanced ingress traffic rate-limiting
Scheduling
departures
W3
per CoS/priority
Flexible scheduling scheme per port
Strict priority (SP)

Weighted Round Robin (WRR)
Hybrid any combination of SP & WRR
W2
W4 lowest priority
Shaping per port

Support differentiated Ethernet services
with SLA assurance
13
IEEE 802.1ag CFM (Connectivity Fault Management)
Page 83
6/13/2010
FibeAir IP-10G IDU: A Nodal Solution
Cellulartraffic
(TDM)
STM
Rings
15
FibeAir IP-10G IDU: A Nodal Solution
16
Page 84
6/13/2010
IP-10F IDU
Fans
drawer
Craft
Terminal
(DB9)
16 x E1s
(optional)
External
Alarms
(DB9)
Protection
Interface
(RJ45)
17
GND
RFU
interface
(N-Type)
5 x FE
Electrical
(RJ45)
Power
-48V DC
Typical Native2 network with IP-10 G & F-Series

4 E1s
25M Eth
F
4 E1s
25M Eth
1+0
(22 E1,
50M)
1+1
1+0
F
(22 E1,
50M)
4 E1s
25M Eth
(22 E1,
50M)
1+1
F
4 E1s
25M Eth
(44 E1,
100M)
(44 E1,
100M)
IP-10 G-Series
GX
IP-10 G-Series with XPIC
1+0
1+0
1+0
Native2 1+0 Ring

(Up to 44 E1
or 100M Eth)
4 E1s
25M Eth
1+0
F
F
4 E1s
25M Eth
(22 E1,
E1
50M)
Native2 1+0 Ring

(Up to 75 E1
or 500Mbps Eth)
4 E1s
25M Eth
IP-10 F-Series
1+0
1+0
F
G
4 E1s
25M Eth
4 E1s
25M Eth
4 E1s
25M Eth
1+1
1
1
1+0
G
G
F
1+0
G
4 E1s
25M Eth
2+0
GX
GX
GX
GX
Terminal configuration
2+0
0
1+0
Nodal configuration
F
1+1
F
F
(22 E1,
50M)
4 E1s
25M Eth
(22 E1,
50M)
2+0 Ring
(Up to 150 E1
or 1Gbps Eth)
GX
1+0
18
Native2
4 E1s
25M Eth
2 0
2+0
GX
4 E1s
25M Eth
2+0
4 E1s
25M Eth
Page 85
6/13/2010
IP-10G VS. IP-10F

Feature
F-Series
G-Series
Supported radio configurations
1+0, 1+1 HSB, 1+1 SD
2+0 with XPIC
XPIC option
Yes
Max radio capacity
100 Mbps
500Mbps
1Gbps using 2+0/XPIC
Multi-radio support
Yes
# of Ethernet interfaces
5 x FE RJ-45
5 x FE RJ-45+
2 x GE combo (RJ-45/SFP)
Full Carrier Ethernet switching

feature-set including ring protection
Yes
Yes
# of E1/T1 integrated IDU interfaces option
16 E1, None
16 E1, 16T1, None
# of E1/T1s per radio carrier
44 E1s
75 E1s / 84 T1s
T-Card slot (additional 16 E1/T1 interfaces or

STM1/OC3 Mux)
Yes
Nodal/XC/SNCP support
Yes
Yes
Sync unit option
Yes
Yes
V.11/RS232 User Channel option
2 x Async V.11/RS232 or
1 x Sync V.11
1+0, 1+1 HSB, 1+1 SD,

2+2 HSB with XPIC
19
Outdoor Enclosures Solution Benefits

Full Outdoor solution:
20
Dust and weather proof

Compact size reduces the cost of leasing or
purchasing rack space.
Ideal for Greenfield areas, at solar-powered sites,
and at repeater sites adjacent to highways.
One-man installation and shorter cabling reduce
installation costs.
Environment-friendly: Greener deployments, saving
on power and air-conditioning costs.
Page 86
10
6/13/2010
Higher Spectral-Efficiency
Whats in it for The Operator?
Typical
IP10
Microwave Radio
MicrowaveRadio
RequiredCapacity
155200Mbps
TWOradio links
or
56MHz channelbandwidth
ONE radiolink
using
28MHzchannelbandwidth
RequiredCapacity
70100Mbps
28MHz
ChannelBandwidth
14MHz
ChannelBandwidth
TheoperatorsavesCAPEX
andfreeupvaluablefrequencyresources
21
Higher Spectral-Efficiency is not enough

RadioType
Ant.Diameter
Length
Modulation
Capacity
TypicalSystemGain
1.80m
30Km
16QAM
32xE1s
TypicalSystemGain
1.80m
21Km
128QAM
STM1/OC3
TypicalSystemGain
3.00m
30Km
128QAM
STM1/OC3
HighSystemGain
HighSystemGain
1.80m
30km
128QAM
STM1/OC3
SpectralEfficiency
shouldalwaysbecoupledwith
SystemGain
22
Page 87
11
6/13/2010
Ceragons Management Overview
IP-10
23
FibeAir
Tree Topology
24
Page 88
12
6/13/2010
Thank You!
Page 89
13
FibeAir IP-10 G-Series

Front Panel Description
Front Panel Overview
GUI Example)
Lets go over the front panel connections of the IP-10 G-Series

We shall explain them one by one, left to right
2

Page 90
CLI Serial Connection
DB9 Craft Line Interface (CLI)

Baud: 115200
Data bits: 8
Parity: None
Stop bits: 1
Flow Control: None
3
EOW Easy Comm. Via Radio
Engineering Order Wire

To communicate with your colleague on the
other side of the radio link, simply connect
here your headset

Page 91
External Alarms
DB9 Dry Contact External Alarms

The IP-10 supports 5 input alarms and a single output alarm
The input alarms are configurable according to:
1) Intermediate, 2) Critical, 3) Major, 4) Minor and 5) Warning
The output alarm is configured according to predefined categories

5
LED Indications
LINK:
GREEN radio link is operational

ORANGE - minor BER alarm on radio
RED Loss of signal, major BER alarm on radio
IDU:
GREEN IDU functions ok

ORANGE - fan failure
RED Alarm on IDU (all severities)
RFU:
GREEN RFU functions ok

ORANGE Loss of communication (IDU-RFU)
RED ODU Failure

Page 92
LED Indications
PROT:
Main unit GREEN (when there no alarms)

STBY unit: YELLOW (when there no alarms)
ORANGE Forced switch, Protection lock
RED physical errors (no cable, cable failure)
OFF Protection is disabled, or not supported on
device
RMT:
GREEN remote unit OK (no alarms)

ORANGE minor alarm on remote unit
RED major alarm on remote unit
User Channels (1)
Two software-selectable user channels (RJ-45):

A single synchronous channel OR two asynchronous channels
Each asynchronous channel will make use of its own RJ-45 external
interface
The synchronous channel mode will make use of both interfaces
(acting as a single interface)
8

Page 93
User Channels (2)
Modes of operation:
V.11 Asynchronous (9600bps)
RS-232 Asynchronous (9600bps)
V.11 Synchronous Co-Directional (64Kbps)
V.11 Synchronous Contra Directional (64Kbps)
9
User Channels (3)
Allowed configurations:
Two RS-232 Asynchronous UCs (default)
Two V.11 Asynchronous UCs
One RS-232 Asynchronous UC, and one V.11 Asynchronous UC
One V.11 Synchronous Co-Directional
One V.11 Synchronous Contra Directional UC
> All settings are copied to Mate when working in Protected mode
10

Page 94
Protection Port
Protection Port (only for standalone units)

Protect your Main unit with a STBY unit
Protection ports on both units deliver the proprietary protocol to
support automatic or manual switchover
The FE protection port is static (only used for protection, not traffic). Its switching is performed
electrically. If the unit is a stand-alone, an external connection is made through the front panel. If the
unit is connected to a backplane, the connection is through the backplane, while the front panel port
is unused.
11
T-Cards (Add-on Mezzanines)
Field upgradeable modules (T-Cards):

16 x E1 T-Card (32 total per unit)
DS1 T-Card
STM1/OC3 MUX T-Card
12

Page 95
T-Cards (Add-on Mezzanines)
An optional STM-1 interface card can be inserted in a dedicated slot in the

system; the card can transmit and receive up to 63 E1s in a channelized
STM-1 signal.
The supported mapping is VC4 only:
VC-12->TU-12->TUG-2->TUG-3->VC-4->AU-4->AUG
The STM-1 T-card is only supported in unprotected main units or in
unprotected stand-alone IDUs
13
GbE Ports
Two GbE ports, each port with 2 physical interfaces:

Port #1: optical (SFP transceiver) or electrical
Port #2: optical (SFP transceiver) or electrical
GbE ports support QoS as in IP-10 (scheduler, policers, shaper, classifiers)
Port #2
14
Port #1

Page 96
FE Ports
5 FE ports:
Port 3:
Port 4:
Port 5,6 &7:
Data
Data or WSC (2 Mbps Wayside Channel)
Data or local management
All ports support QoS as in IP-10 (scheduler, policers, shaper, classifiers)
15
Radio and misc.
The Radio port is the switchs 8th port (same as in IP-10)
In addition
Grounding
-48vdc Power Connector
Fan Drawer
16

Page 97
XC using a Shelf Configuration
XC operation is implemented using two-unit backplanes, which

provide the interconnectivity.
Up to three backplanes, consisting of six IDUs, can be stacked to
provide an expandable system
17
XC using a Shelf Configuration

All IDUs that operate within
the XC system have
identical hardware, and act
as stand-alone units.
The 2 lower units can be configured as Main units.

The role an IDU plays is determined during installation by its position in the
traffic interconnection topology
18

Page 98
Thank You !
10

Page 99

FibeAirIP10GSeries
Installation
General
If installation requires CFG file upload & download and / or SW file
upload & down -
1.
2.
3.
Make sure FTP Server is installed on your PC

FTP is configured (RD/WR permissions)
Latest SW version is available (FTP root directory)
FTPinstallationguide
isavailableat
Training.Ceragon.Com:
seeModules/
Installation
1
Page 100
Agenda
Site Requirements
Packing & Transportation
Unpacking
Required
q
Tools
IDU Dimensions
Installing standalone IDU in a 19 Rack
Installing Nodal Enclosures in a 19 Rack
Preparing the IDU for a Shelf installation
Installing the IDU in a Shelf
Installing a Blank Panel IDU in a Shelf
Installing a T-Card into an IDU
Grounding the IDU
Lightning Protection
Power General Requirements
Installing the IDU-ODU IF cable
Site Requirements
IDU must be located indoors
The environment temperature must be between -5 C and +45 C.
Easily accessible, but only by authorized personnel.
Available power source of -48 VDC, and the site must comply with
National Electric Code (NEC) standards.
Available management connection (Ethernet or dial-up).
IDU-ODU connection (IF cable): no more than 300m
2
Page 101
Site Requirements
Heat Dissipation:
The IP-10 IDU overall heat dissipation is 25W max (~85 BTU/h).
The ODU heat dissipation
p
is 100W max.
Antenna Location:
As with any type of construction, a local permit may be required before installing
an antenna. It is the owners responsibility to obtain any and all permits.
Packing & Transportation

The equipment is packed at the factory, and sealed moisture-absorbing bags
are inserted.
The equipment is prepared for public transportation. The cargo must be kept dry
during transportation.
Keep items in their original boxes till they reach their final destination.
If intermediate storage is required, the packed equipment must be stored in dry
and cool conditions and out of direct sunlight
When unpacking
Wh
ki
Check the packing lists, and ensure that the
correct part numbers and quantities of
components arrived.
3
Page 102
Unpacking
A single FibeAir system (1+0) is shipped in 5 crates.
Upon delivery, make sure that the following items are included:
Two indoor units and accessories
Two outdoor units
For 13-38 GHz systems, verify that there is a high RFU and low RFU.
One CD with a management user guide.
Unpack the contents and check for damaged or missing parts.

If any part is damaged or missing, contact your local distributor.
Required Tools
The following tools are required to install the IDU:
Philips screwdriver #2 (for mounting the IDU to the rack and grounding screw)
Flathead small screwdriver (for PSU connector)
Sharp cutting knife (for wire stripping)
Crimping tool for ground cable lug crimping
(optional: if alternative grounding cable is used)
Setting up Management will require ETH cable (for setting management)

Serial Cable (for setting management)
8
4
Page 103
Specifications
Connector spec, cable spec & interface pin layout can be found in our complete
PDF installation guide
installation guides available

at Training.Ceragon.Com:
see Modules
M d l / Installation
I t ll ti
IDU Dimensions
42.60mm
10
5
Page 104
Installing standalone IDU in a 19 Rack
As shown in the illustration, four screws, supplied with the

installation kit,
kit are used to secure the IDU to the rack
rack.
11
12
6
Page 105

Before you install the
enclosures
Plan carefully the required
space within the rack !
Should you need to install 3
enclosures prepare at least
10Us (6Us for enclosures + 2Us free
space for maneuvering above and below
shelves)
Main Enclosure
Start the installation process

from bottom to top, e.g. Main
enclosure should be installed
first at the bottom of your rack
space
13

Step #1:
Install the IP-10 Main enclosure
in the 19 inch rack using 4
screws.
14
7
Page 106

Step #1:
screws.
Step #2:
Slide down the 2nd extension
enclosure. Male connector
should plug in smoothly into the
Main enclosure.
15

Step #1:
screws.
Step #2:
should plug in smoothly into the
Main enclosure.
Step #3:
should be plugged in smoothly
into the Main enclosure.
16
8
Page 107

Step #4:
Secure the 2nd extension into
the Main enclosure. Use the
built-in screw.
Mount the 2nd extension into the
rack using the 4 screws
17

Step #4:
Secure the 2nd extension
into the Main enclosure.
Use the built-in screw.
Mount the 2nd extension
into the rack using the 4
screws
Step #5:
Add the 3rd extension
when needed
18
9
Page 108
Preparing the IDU for a Shelf installation

Remove the two 19" brackets mounted on the IP-10 IDU by unscrewing the 3
screws at each side.
19
Installing the IDU in a Shelf

Slide the IP-10 IDU into the enclosure and tighten it using 2 screws. Repeat
this step in accordance with the configuration.
IDU insertion & extraction

should NOT be under power
20
10
Page 109
Installing a Blank Panel IDU in a Shelf

Slide the IP-10 blank panel into the enclosure, and tighten it using 2 screws.
21

Remove the IP-10 T-Card blank panel from the IDU, by releasing the 2 side
screws.
22
11
Page 110

Insert the IP-10 T-Card panel and tighten it using the 2 side screws.
23
Grounding the IDU
Single Point Stud

Grounding Wire
24
12
Page 111
Grounding the IDU

The IDU is suitable for installation in a Common Bonding Network (CBN).
Only copper wire should be used.
The wire must be at least 14 AWG.
Connector and connection surfaces must be plated. Bare conductors must be
coated with antioxidant before crimp connections are made to the screws.
FibeAir provides a ground for each IDU, via a one-hole mounted lug onto a
single-point stud.
Th stud
t d mustt b
t ll d using
i a UL
li t d ring
i ttongue tterminal,
i l and
d ttwo star
t
The
be iinstalled
UL-listed
washers for anti-rotation.
25
Lightning Protection
For antenna ports, lightning protection is used
that does not permit transients of a greater
magnitude than the following:
Open Circuit: 1.2-50us 600V
Short Circuit: 8-20us 300A
The ampacity of the conductor connecting the
IDU frame to the DC return conductor is equal to
or greater than, the ampacity of the associated DC return conductor.
26
13
Page 112
Power General Requirements

1. A readily accessible Listed branch circuit over-current protective device,
rated 15 A, must be incorporated in the building wiring.
2. This equipment is designed to permit connection between the earthed
conductor of the DC supply circuit and the earthing conductor at the
equipment.
3. The equipment shall be connected to a properly grounded supply system
4. The DC supply system is to be local, i.e. within the same premises as the
equipment
5. A disconnect device is not allowed in the grounded circuit between the DC
supply source and the frame/grounded circuit connection.
27
Power Requirements
When selecting a power source, the following must be considered:
DC power can be from -40.5 VDC to -60 VDC.
Recommended: Availability of a UPS (Uninterrupted Power Source),
battery backup, and emergency power generator.
Whether or not the power source provides constant power (i.e., power is
secured on weekends or is shut off frequently and consistently).
The power supply must have grounding points on the AC and DC sides.
The
Th user power supply
l GND mustt be
b connected
t d to
t the
th positive
iti pole
l iin th
the IDU
power supply.
Any other connection may cause damage to the system!
28
14
Page 113
Power Requirements
Important
Make sure to use a circuit breaker to protect the circuit from damage by
short or overload.
29
Installing the IDU-ODU IF cable

Route the IF Coax Cable from the IDU to the ODU/RFU and terminate it
with N-type male connectors.
Note: Make sure you fasten the cable along the ladder!
Make sure that the inner pin of the connector does not exceed the
edge of the connector.
The cable should have a maximum attenuation of 30 dB at 350 MHz.
30
15
Page 114
ThankYou!
16
Page 115
6/16/2010
RFUC&MediationDevices
The Most Comprehensive Portfolio

FibeAir Family
RFUs
6-38 GHz
Carrier Ethernet
IP-MAX2
IP-10
3200T
EMS & NMS

PolyView (NMS)
RFU-C
Multi-Service
RFU-HP
IP-10
IP-MAX2
640P
CeraView (EMS)
TDM
RFU-P, RFU-SP
1500R/1500P
3200T
2
Page 116
6/16/2010
IDU RFU Compatibility
IP-10
RFU-C
1500R
RFU-P, RFU-SP
RFU-HP
IP-IP-MAX2
RFU-SP
640P
1500P
3
IDU IDU Compatibility Across Link

1500R
1500R
IP-10
IP 10
IP-10
1500P
1500R
IP-MAX/IP-MAX2
IP-10
1500P chassis Cannot House 1500R IDC and IDMs

1500R chassis Cannot House 1500P IDC and IDMs
Must Match IDU Type Across a Link
4
Page 117
6/16/2010
RFU-C direct mount configurations
1+0 direct
5
RFU-C direct mount configurations

1+1 direct
6
Page 118
6/16/2010
RFU-C remote mount configurations
1+0 remote
7
RFU-C remote mount configurations

1+1 remote
8
Page 119
6/16/2010
RFU-C antenna adaptors
Adaptors for RFU-P direct antenna mount

Adaptors for NSN Flexi Hopper direct antenna mount
Adaptors for Ericsson R1A 23GHz direct antenna mount
Remote adaptors and configurations
9
RFU-C to NSN antenna
10
Page 120
6/16/2010
RFU-C to Ericsson antenna
(R1A 23GHz)
11
Antenna Alignment (1)
Connect Digital Volt Meter (DVM) to the AGC BNC connector

Align the antenna until
ntil voltage
oltage reading is achie
achieved
ed (1
(1.2
2 to 1.7Vdc)
1 7Vdc)
Repeat antenna alignment at each end until the minimum dc voltage is
achieved
1.30vdc = -30dBm
1.45vdc = -45dBm
1.60vdc = -60dBm
etc
12
Page 121
6/16/2010
Antenna Alignment (2)
Compare achieved RX level to

calculated RX level
Keep aligning until the achieved
level is up to 4 dB away from the
calculated received signal level
If voltage reading is more than 4
dB away or higher than 1.7vdc,
re-align antenna to remote site
13
g@ You
g !
Thank
ThankYou!
14
Page 122

FibeAirIP10GSeries
Setting Management
Agenda
Getting started
General notes
General commands
Command historyy
Reading current IP
Setting new IP
Connecting PC to IDU
Troubleshooting
Factory Defaults
2

Page 123
Getting started
Verify that physical installation is successfully completed:
IDU is properly mounted in a shelf / rack
Power + GND
IF Cable between IDU and ODU
Connect a PC to the Terminal connector and launch a serial application
Baud: 115200
Data bits: 8
Parity: None
Stop
St bits:
bit 1
Flow Control: None
YoumayuseanySerial
ApplicationsuchasHyper
Terminal PuTTY TeraTerm
Terminal,PuTTY,TeraTerm
etc
Log on using (admin/admin) for user name and password.

Now, you should be able to see the IP-10 CLI Prompt
3
General notes on CLI
IP-10:/>
Note that the
> sign indicates your current directory in the CLI tree
Most of the CLI commands are based on GET/SET concept

Some commands may require a different syntax
Ceragon strongly recommends to use CLI only for setting management IP
address when current IP is unknown
All functions & features can be configured faster and easier using the WEB
based EMS
4

Page 124
General Commands
IP-10:/ >?
IP-10:/ls
IP-10:/lsp
IP-10:// > exit
IP-10:/ > cd
IP-10:/ > cd ..
Type ? (question mark) to list helpful commands

Type ls to list your current directory
Type lsp to available commands of current directory
Type exit to terminate the session
Type cd to change directory
Type cd .. to return to root directory
5
Command History
Use the arrow keys to navigate through recent

commands
Use the TAB key to auto-complete a syntax
6

Page 125
Reading current IP
To read current IP type the following:
IP-10:/>cd management/networking/ip-address/
IP-10:/ management/networking/ip-address>
Note that the prompt has changed. Now, type get ip-address:
IP-10:/ management/networking/ip-address>get ip-address

completion the current IP will be displayed
Upon completion,
displayed, followed by the new
prompt:
IP-10:/ management/networking/ip-address>get ip-address

192.168.1.1
IP-10:/ management/networking/ip-address>
7
Setting new IP
Now, let us set a new IP for the MNG:
We assume the required IP is 192.168.1.144
Type set ip-address 192.168.1.144
IP-10:/ management/networking/ip-address>set ip-address 192.168.1.144
Upon completion, you will be prompt:
You may lose remote management connection to the unit if this value
is changed incorrectly.
Are you sure? (yes/no):
Type yes and connect the IDU to your network / PC
8

Page 126
Connecting IDU to EMS

1. Connect your EMS/NMS to the IDU (port 7) with ETH CAT.5 cable
2. Verify that your PCs IP is in the same subnet
3 Make sure Link is up
3.
4. PING the IDU
5. Launch a WEB browser with the URL set as the IDUs IP
9
Management Troubleshooting
In case PC cannot PING IDU
1. Check your ETH cable it might not be inserted properly (broken PIN)
2. Verify the management port is enabled in the EMS General/Management
configuration
3. Make sure you connect to a management-enabled port (7, 6 or 5)
4. Verify right LED is ON (see below)
5. Verify your PC is in the same subnet as the IDU
6. In case your IDU is connected to a router: set the IDUs Default GW = Router IP
7. In case your PC is connected to several IDUs (through switch/hub) make sure
every IDU has a unique IP
When ON (Green) = Port is set to Management
When OFF = Port is set to Data
10

Page 127
Back to factory defaults

Going back to factory defaults can be done with EMS or CLI
In case you need to set factory defaults with CLI type the following -
IP-10:/> cd management/mng-services/cfg-service
In the new directory type the following:
IP-10:/management/mng-services/cfg-service>set-to-default
11
ThankYou!

Page 128
4/16/2010

EMS Performance Monitoring
Agenda
EMS General Information
Faults:
Current Alarms
Event Log
PM & Counters:
Remote Monitoring
TDM Trails
TDM interfaces
Radio (RSL, TSL, MRMC and MSE)
Radio TDM
Radio ETH
Page 129
4/16/2010
EMS - General
Easy, user friendly GUI

No need to install an application WEB Based software
No need to upgrade your EMS application embedded in the IDU SW
No need for strong working station simple PC is sufficient
(For maintenance issues FTP Server is required)
Easy access simply type the IP address of the IDU on your web page
Supports all IDU versions and configurations
EMS Main View

Access application via IP address
User friendly navigation menu
Page 130
4/16/2010
EMS Main View

Graphical MENU: Click to configure
EMS Main View
Protection Status Display &

Quick Access Icons
Page 131
4/16/2010
EMS Main View

In this example slot #1 and slot #2 are configured to support 1+1 Protection
Slot #1 is selected and in Active mode.
Black Rectangular to indicate

selected slot for configuration
EMS Main View

When the user selects Slot 2 the GUI updates automatically
Page 132
4/16/2010
Faults - CAS
The CAS window shows collapsed list of alarms
By expanding a line we can see additional information:
Probable cause
Corrective Actions
Faults Event Log

The Event Log shows max. 200 lines of events
When Event #201 occurs, Event #1 is erased and #201 is logged as #200.
Page 133
4/16/2010
Available PM Statistics - Radio

TDM PM in Radio
(allocated E1s)
TDM
(16E1s)
ETH PM (Data + In-Band):
1. Aggregated Errors
2. Throughput
3. Capacity
4. Radio Link Utilization
5. RMON standard is
implemented
p
as well to
provide detailed data
11
Radio PM:
1. RSL
2. MSE
3. MRMC (ACM)
4. Aggregate
Available PM Statistics Line Interfaces
STM-1 interface facing customer equipment

g customer equipment
q p
TDM interfaces facing
End-to-End Trails
12
Page 134
4/16/2010
Clearing previous data

To erase all IDU PM data, click the CLEAR button -
13
ETH PM RMON
The system supports Ethernet statistics counters (RMON) display (depends on
port availability). The counters are designed to support:
RFC 2819 RMON MIB.
RFC 2665 Ethernet-like MIB.
RFC 2233 MIB II.
RFC 1493 Bridge MIB.
Page 135
4/16/2010
PM TDM Trails In Detail

Report Interval:
The number of trails in the list is derived from

radio link capacity (default license = 10Mbps)
Display 15 minutes intervals or single Daily interval (24 hours)

Information can be displayed as a graph
PM RMON Special Registers

RMONregister /Counter
Description
Undersizeframesreceived
Framesshorterthan64bytes
Oversize frames received

Oversizeframesreceived
Frames longer than 1632 bytes

Frameslongerthan1632bytes
Jabberframesreceived
Totalframesreceivedwithalengthofmorethan1632bytes,
butwithaninvalidFCS
Fragmentsframesreceived
Totalframesreceivedwithalengthoflessthan64
bytes,andaninvalidFCS
Rxerrorframesreceived
TotalframesreceivedwithPhyerror
FCSframesreceived
TotalframesreceivedwithCRCerror,notcounteredin
"Fragments",
Fragments ,"Jabber"
Jabber or
or "Rx
Rxerror
error"counters
counters
InDiscardFrames
Countsgoodframesthatcannotbeforwardeddueto
lackofbuffermemory
InFilteredFrames
Countsgoodframesthatwerefilteredduetoegress
switchVLANpolicyrules
Pauseframesreceived
Numberofflowcontrolpauseframesreceived
16
Page 136
4/16/2010
Troubleshooting with RMON: Filtering Example
Radio port is a
member of VID 100
Radio port is a
member of VID 100
Site A
Tagging
Untagged Frames
Tagged with default
VID 100
Site B
No membership
Access port with

default VID = 300
Site B Ingress port (Radio) receives the frame and checks the Egress port VID
membership
Egress port default VID is 300, therefore frame is filtered by the remote Radio port
17
Troubleshooting with RMON: Oversized frames

Site A
T
Site B
T
Tagged Frames with

frame size > 1632 bytes
When ingress frames exceed the maximum frame size, RMON counter Oversized frames
received is updated accordingly
18
Page 137
4/16/2010
Troubleshooting with RMON: Discarding Example

Site A
Site B
Ingress traffic does not

comply to Policer rules
Discarding Examples:
Ingress rate > Rate Limiter
Ingress frames do not qualify to Policer rules
19
Troubleshooting with RMON: Monitoring specific

traffic types
Site A
Site B
Rate Limiter
Monitor
Video streams are generally transmitted over UDP

with multicast addresses
To monitor traffic, check out the Multicast Frames
Received register
To limit MC traffic, assign a Policer with a UDP & MC
CIR rules
20
Page 138
10
4/16/2010

Errored Second (ES):
A one-second period with one or more errored blocks or at least one defect

Severely Errored Second (SES):
A one-second period, which contains 30% errored blocks or at least one
defect.
defect
SES is a subset of ES.
Page 139
11
4/16/2010

A period of unavailable time begins at the onset of 10 consecutive Severely
Errored Second (SES) events. These 10 seconds are considered to be part of
unavailable time.
A new period of available time begins at the onset of 10 consecutive non-SES
events. These 10 seconds are considered to be part of available time.

Background Block Error (BBE):
An errored block not occurring as part of a SES.
Page 140
12
4/16/2010

Number of Switches (only relevant for Protected SNCP Trails):
The number of times the IP-10 switched from Primary Path to Secondary Path
and vice versa (per 15min or 24hrs interval)

Active Path Seconds (only relevant for Protected SNCP Trails):
The number of times seconds the Active Path was available
Page 141
13
4/16/2010

Integrity:
Indicates whether information is reliable for analysis (ticked) or not
For example if clock was changed or system was restarted during this interval
then information is not reliable
PM E1 / DS-1 (Radio PM)

This PM data relates to the TDM Line Interfaces.
28
Page 142
14
4/16/2010
PM E1 / DS-1 (Radio PM)

Here we can analyze TDM PM through the radio link
29
PM STM-1 Interface
This PM data relates to the STM-1 Line Interface.
30
Page 143
15
4/16/2010
PM Radio
Signal Level RSL & TSL analysis
Allows setting RSL & TSL thresholds
EMS will notify when signal exceeds THSLD
>> Easier maintenance
Aggregated radio traffic analysis

MRMC PM related to ACM:
Associated Script
Available Bit rate
Available Radio VCs
MSE analysis
31
PM Radio Signal Level - Example
- 40dBm = Nominal RSL for an operational Link

Level 1: 25 sec
Level 2: 15 sec
900 sec = 15min Interval
Page 144
16
4/16/2010
PM Radio Signal Level - Example

Using graphical display of the THSLD analysis allows us easier
examination of the RSL & TSL state throughout certain period of time
RSL
-40
-50
-68
T [sec]
-99
10
33
10
PM Radio - Aggregate
Aggregated radio traffic analysis
34
Page 145
17
4/16/2010
PM Radio - MRMC
The information displayed in this page is derived from the license and script
assigned to the radio.
When ACM is enabled and active,
active as link quality degrades or improves
improves, the
information is updated accordingly.
35
PM Radio - MSE
The information displayed in this page is derived from the license and script
assigned to the radio. When link quality degrades or improves, the MSE reading
is updated accordingly. Differences of 3dB trigger ACM modulation changing.
Threshold can be configured as well for easier maintenance.
36
Page 146
18
4/16/2010
PM Ethernet
ETH Traffic + Threshold settings:
Frame Error Rate
Frame error rate (%) measured on radio-Ethernet
radio Ethernet
interface
Throughput data bits measured on radioEthernet interface
Capacity - overall Ethernet bits rate, data &
overhead, measured on radio-Ethernet interface
Utilization - (Actual Ethernet throughput, relative
to the potential Ethernet throughput of the radio,
excluding TDM channels).
Utilization (%) is displayed as one of five bins:
0-20%, 20-40%, 40-60%, 60-80%, 80-100%
37
Throughput / Capacity / Utilization

To better understand these terms, we shall examine the Ethernet tagged frame full
structure:
A frame viewed on the actual physical wire would show Preamble and Start Frame
Delimiter,, in addition to the other data (required
( q
by
y the p
physical
y
hardware).
)
However, these bits are stripped away at OSI Layer 1 by the Ethernet adapter before
being passed on to the OSI Layer 2 which is where data is detected.
Pre.
7octets
SFD
1octet
DA
6octets
VLAN
ETH Type
/Length
Payload+
Padding
6octets 4octets
2octets
461500 4octets
octets
SA
CRC
Interframe
Gap
12octets
DataRate:min.64 octets max.1522octets

Physicalwirerate:min.84octets max.1542octets
38
Page 147
19
4/16/2010

Pre.
7octets
SFD
1octet
DA
6octets
VLAN
ETH Type
/Length
Payload+
Padding
6octets 4octets
2octets
461500 4octets
octets
SA
CRC
Interframe
Gap
12octets
DataRate:min.64 octets max.1522octets

Physicalwirerate:min.84octets max.1542octets
In case we use a 64 bytes frame:

Throughput (Data rate) = ~ 77% of physical transmitted rate
Stripped bits = ~ 23% of physical transmitted rate
(64/84=0.77)
(20/84=0.23)
Hence, when we transmit 100Mbps, the actual throughput would be 77 Mbps

39

Throughput = 77 Mbps
Radio Capacity =
(license) = 400Mbps
Transmitted rate =
100 Mbps
Capacity = Received frame rate

= 100 Mbps
Utilization = Throughput = 77 = 20 %
Radio Capacity 400
40
Page 148
20
4/16/2010
PM Ethernet
Ethernet throughput & Capacity PMs are measured by accumulating

the number of Ethernet octets every second
Accurate analysis requires accumulating a full interval (15min/24hrs)
41
ThankYou!
training@ceragon
com
42
Page 149
21
6/13/2010

EMS General Configuration
Agenda
In this module we shall explain

the following features as they
appear on the EMS navigation
Menu
Page 150
6/13/2010
Unit Parameters Step # 1
Configure specific
information that may
assist you later
Such info will help you
locate your site easier
and faster
VDC reading
Page 151
6/13/2010
Celsius (metric) or
Fahrenheit (Imperial)
5
By default the time &

date are derived from
the operating system
clock
User may set new
values
These settings are also
used for NTP
connection (later
explained)
Page 152
6/13/2010

IDU Serial number is
important when you
submit your request
for a License upgrade
When you complete
configuring all
settings, click Apply.
Versions
This page shows the complete

package of IDU and ODU software
components
8
Page 153
6/13/2010
Versions
Lets explore this example:

3 0 92
The IDU running SW is displayed in the aidu line and currently it is 3.0.92
A new SW was downloaded sometime in the past (3.0.97)
The IDU was not upgraded yet
Versions RFU files
Th IDU holds
h ld all
ll th
fil for
f all
ll the
th
The
the SW files
components (IDU + ODU)
You can see here the different files per
ODU type
10
Page 154
6/13/2010
External Alarms Collapsed Input Alarm Config.
Dry Contact Alarms (DB-9):

5 Inputs
1 Output
11
External Alarms Expended Input Alarm Config.
12
Page 155
6/13/2010
External Alarms Configuring the Output Alarm

Group of alarms will trigger the external alarm Output.
Communication Alarms related to traffic: Radio / Ethernet line / TDM line
Q lit off Service
Quality
S i We
W do
d nott h
have specific
ifi alarms
l
off QoS
Q S
Processing Alarms related to SW: Configuration / Resets / corrupted files
Equipment Alarms related to: HW / FAN / RFU mute / Power Supply / Inventory.
Environmental Alarms of extreme temperature.
All Groups.
Test mode manual switch.
13
Management Network Properties

Here you can set the
Network Properties of
the IDU
This is the switch MAC address
If your link is up you should be able to see the other ends IP
14
Page 156
6/13/2010
Management Local Properties (Out of band)
The IDU has 3 ports for local management: Port 7, Port 6 and Port 5.
You may enable none or up to 3 ports:
Number of ports =3
Number of ports =2
Number of ports =1
Number of ports =0
15
Port 7, Port 6, Port 5

Port 7, Port 6
Port 7
NO LOCAL MANAGEMENT !!!
Management In Band Properties
In Band Management requires unique VLAN ID

This helps separating MNG traffic from other services
In Band MNG packets are transferred via the radio link
When the link is down, management is down as well.
16
Page 157
6/13/2010
Management Port Properties
These parameters
allow you setting the
managementt capacity
it
and port properties
17
Trap Configuration (OSS / NMS / Northbound)
To manage the IDU with OSS /

NMS, you will need to configure
the IP address of the OSS Server
You may configure up to 4 Servers
(Trap Destinations)
18
Page 158
6/13/2010
Licensing Default License

Demo license can be
enabled on-site, it expires
after 60 days
(operational time)
Licenses are generated per
IDU S/N upon request
(capacity / ACM / switch
mode)
License upgrade requires

system reset.
19
Licensing Demo License Enabled
Demo License allows you full

evaluation of the IDU
functionality, features and
capacities
20
Page 159
10
6/13/2010
NTP Client Properties

Enable / Disable
Type NTP Server IP address
Expect IDU to lock on NTP Servers clock
Expected Status:
1. If locked, it returns the IP address of the server it is locked on.
2. Local if the NTP client is locked to the local elements real-time clock
3. NA - if not synchronized with any clock (valid only when Admin is set to
Disable).
The feature supports Time Offset and Daylight Saving Time.
Time Offset and Daylight Saving Time can be configured via WEB (Unit
Information page) or via CLI: /management/mng-services/time-service>
21
NTP Properties
22
Page 160
11
6/13/2010
NTP Properties
When using NTP with external protection 1+1, both Active and Standby
units
nits sho
should
ld be locked independentl
independently on the NTP ser
server,
er and report
independently their Sync status.
Time & Date are not copied from the Active unit to the Standby unit
When using NTP in a shelf configuration
configuration, all units in the shelf (including
standby main units) are automatically synchronized to the active main units
clock.
23
IP Table
Here you can manually set your neighbors network properties
24
Page 161
12
6/13/2010
SNMP
V1
V3
No security
Authentication
Authentication privacy
SHA
MD5
No Authentication
25
All ODU
This feature is used to feed the integrated fans of a 3rd party Outdoor
Enclosure (standalone outdoor rack)
When enabled,
enabled the Ext.
Ext Alarms connector is modified to provide the required
power feed.
All ODU Disabled
26
All ODU Enabled
Page 162
13
6/13/2010
ThankYou!
training@ceragon
com
27
Page 163
14
3/7/2010

EMS Switch Configuration
Agenda
1. Switch mode review

2. Guidelines
3. Single Pipe Configuration
4. Managed Mode Configuration
5. Managed Mode Common Applications
Page 164
3/7/2010
Switch Modes
1. Single (Smart) Pipe (default mode, does not require license)
This application allows only single GbE interface as traffic interface (Optical
GbE-SFP or Electrical GbE - 10/100/1000).
Any traffic coming from any GbE interface will be sent directly to the radio and
vice versa.
This application allows QoS configuration.
Other FE (10/100) interfaces can be configured to be "functional" interfaces
(WSC, Protection, Management), otherwise they are shut down.
Note: (CQ20473): Single pipe discards PAUSE PDU (01-80-C2-00-00-01)
and Slow protocols PDU (01-80-C2-00-00-02).
Switch Modes
2. Managed Mode (license depended)
This application is 802.1Q VLAN aware bridge, allowing L2 switching based
on VLANs. This application also allows QoS configuration.
All Ethernet ports are allowed for traffic. Each traffic port can be configured to
be "access" port or "trunk" port:
Type
VLANs
Allowed Ingress Frames
Allowed Egress
Frames
Access
Specific VLAN should be

assigned to access the port
Only Untagged frames

(or Tagged with VID=0
"Priority Tagged )
Untagged frames
Trunk
A range of VLANs should be

assigned to access the Port
Only Tagged frames
Tagged frames
Page 165
3/7/2010
Switch Modes
3.
Metro Mode (license depended)
This application is 802.1Q VLAN aware bridge, allowing Q-in-Q (A.K.A.

VLAN Stacking). This mode allows the configuration of a PE port and CE port.
Allowed Ingress
Frames
Type
VLANs
CustomerNetwork
Specific S-VLAN should be Untagged frames, or

assigned to "Customerframes with C-tag
Network" port
(ether-type=0x8100).
ProviderNetwork
A range of S-VLANs, or
"all" S-VLANs should be
assigned to "ProviderNetwork" port
Configurable S-tag.
(ether-type)
0x88a8
0x8100
0x9100
0x9200
Allowed Egress
Frames
Untagged or C-tag
(ether-type= 0x8100)
frames.
Configurable S-tag.
(ether-type)
0x88a8
0x8100
0x9100
0x9200
Guidelines
Changing switch modes requires a reset

Resets do not change the IP-10G settings (radio,
configuration, etc.)
VLANs need to be created in the switch DB before assigned
to a port
Page 166
3/7/2010
Single Pipe
Configuration
7
Single Pipe Configuration
Untagged
VID 4
45
VID 51
IP-10 Switch
VID 100
Port 1: GbE (Optical or Electrical)

Port 3: FE (RJ45)
Port 8 (Radio)
Page 167
3/7/2010
Configuration Single Pipe
This is the default setting
Configuration Single Pipe
Only one ingress port

can be used:
Port 1 (Opt. or Elec.)

Port 3 (RJ45)
When one is enabled

the other is disabled
No need to configure
VID membership
10
Page 168
3/7/2010
Managed Mode
Configuration
11
Configuration Managed Mode

Lets use this diagram as an example Port #2 as Trunk (VID 200)
IDU-B
IDU-A
Port #3 as Trunk
(VID 300)
12
Radios as Trunk by
default
Port #2 as Trunk
(VID 200, VID 300)
Page 169
3/7/2010

Make sure both IDUs are aware of
the required VIDs
You need to create the VIDs before
you assign them to a certain port
(Set # & Apply)
13

Next steps:
1. Go to Interfaces page
2. Enable the required port (Ingress ports)
3. Configure the port type as Trunk or Access
4. Assign allowed VLAN IDs (port membership)
5. Radio port is automatically configured as Trunk, all VLANs are
allowed by default
14
Page 170
3/7/2010
4
15

Common Applications
Tagging / untangling
IP-10
Radio = Trunk Port
Access Port
Transmits and
receives
Untagged
frames
Transmits and
receives
Untagged
frames
PC
PC
192.168.1.200
192.168.1.100
16
Page 171
3/7/2010

Common Applications
Radio = Trunk Port
IP-10
Trunk Port
Multiple L2
streams, each
identified with
unique VID
Traffic
Generator
Trunk Port
17
Thank You !
18
Page 172
4/17/2010
FibeAir IP-10
Trunk VS. Access
Agenda
1. VLAN TAG Attributes

2. Access Port
3. Trunk Port
4. Extracting frames out of a trunk
5. General Guidelines
6. EMS Trunk Configuration
Page 173
4/17/2010
VLAN TAG Attributes

1.
In L2 ETH switching, L2 traffic can be engineered using the VLAN TAG

attributes
2.
L2 traffic is controlled by defining port membership: Access or Trunk
3.
Together, port membership + L2 traffic engineering convert

connectionless to connection-oriented network
4.
In such networks, services are better deployed and maintained
5.
VLAN TAG attributes include:

VLAN ID (12 bits)
Priority Bits (3 bits)
5.
Additional attributes may be used to engineer traffic:

MAC DA
Port number
Access Port
Access Port is a port which is aware of a single VLAN only
Ingress
g
traffic is expected to be Untagged,
gg
e.g.
g no VLAN
information exists within the received Ethernet frame
All frames that are received through this port are tagged with
default VLAN (VID + P bits)
All frames that exit through this port towards customer devices are
untagged (VLAN is removed)
Users can configure the L2 switch to assign different tagging

scenarios to different ports
Page 174
4/17/2010
Access Port
Let us examine the Tagging / Untagging process of a L2 switch
L2 ETH SW
DA
SA
Type
Payload
FCS
Access Port Tagging ingress frames
Let us examine the Tagging / Untagging process of Port #1
Tagging
Port #8
Port #1
DA
SA
VLAN TAG
Type
Payload
FCS
Tagged frame
DA
SA
Type
Payload
FCS
Access Port:Untagged frame

6
Page 175
4/17/2010
Access Port
Utagging frames towards customer interfacing ports
When Tagged frame from Network is forwarded to Access port, the

VLAN Tag is removed
Untagging
Port #8
Port #1
DA
SA
VLAN TAG
Type
Payload
FCS
Tagged frame
DA
SA
Type
Payload
FCS
Access Port: Untagged frame

7
Access Port Tagging multiple ports
The switch can individually tag multiple Access ports with same VID or
unique VID
Tagging
Port #8
Port #1
Port #2
DA
DA
DA SA Type Payload FCS

SA Type Payload FCS
DA
SA
SA
VLAN TAG = 10
VLAN TAG = 33
Type
Type
Payload
Payload
FCS
FCS
Access Ports: Untagged frames

8
Page 176
4/17/2010
Trunk Port multiple VIDs awareness
To be able to transmit & receive multiple VLANs, the common port has to
be configured as a Trunk Port
Trunk Port
Port #8
Port #1
Port #2
DA
DA
DA SA Type Payload FCS

SA Type Payload FCS
DA
SA
SA
VLAN TAG = 10
Type
VLAN TAG = 33
Type
Payload
Payload
FCS
FCS
Access ports: Untagged frames

9
Trunk Port multiple VIDs awareness
Any port can be configured as Trunk

In this example, port #2 is facing customer device to forward all the
network VLANs (TX&RX)
Trunk Port
Port #8
Port #2
DA
DA
DA
SA
VLAN TAG = 10
SA VLAN
TAG = 33
DA Untagged
frames
10
Type
Type
Payload
Payload
SA
SA
VLAN TAG = 10
VLAN TAG = 33
Type
Type
Payload
Payload
FCS
FCS
FCS
FCS
Page 177
4/17/2010
Trunk & Access Extracting frames out of a Trunk
DA
A certain VLAN can be extracted out of a Trunk via Access port assigned
with specific VLAN membership (Default VID)
SA
Type
Payload
FCS
DA
SA
VLAN TAG = 33
Type
Payload
FCS
Port #5: Access
Port #8: Trunk

DA
Port #2:
Trunk
SA
DA
VLAN TAG = 10
SA
VLAN TAG = 33
DA Untagged
frames
Type
Type
Payload
Payload
11
DA
SA
SA
VLAN TAG = 10
VLAN TAG = 33
Type
Type
Payload
Payload
FCS
FCS
FCS
FCS
General guidelines
Access port can only receive untagged frames from customer device
Access port can only transmit untagged frames towards customer device
Access port supports single VLAN
Access port can be connected to an Access port only
Trunk port can only receive / transmit tagged frames
Trunk port supports multiple VLANs
Trunk port can be connected to a Trunk port only
When configuring Access or Trunk port, membership needs to be defined

next (which VLANs are supported)
12
Page 178
4/17/2010
EMS Trunk Configuration
4
13
ThankYou!
training@ceragon
com
14
Page 179
4/21/2010

EMS Metro Switch Configuration
Agenda
Metro mode review

Configuration Guidelines
Simplified Flow
Common Applications: CN PN PN CN
Common Applications: CN PN PN PN
Switch Mode Configuration
CN Port Configuration
PN Port Configuration
Page 180
4/21/2010
Metro Mode (license depended)

This application is 802.1Q VLAN aware bridge, allowing Q-in-Q
(A.K.A. VLAN Stacking).
This mode allows the configuration of a PE port and CE port.
Allowed Ingress
Frames
Allowed Egress
Frames
Type
VLANs
CustomerNetwork
Specific S-VLAN should be Untagged frames, or

assigned to "Customerframes with C-tag
Network" port
(ether-type=0x8100).
ProviderNetwork
A range of S-VLANs, or
"all" S-VLANs should be
assigned to "ProviderNetwork" port
Configurable S-tag.
(ether-type)
0x88a8
0x8100
0x9100
0x9200
Untagged or C-tag
(ether-type= 0x8100)
frames.
Configurable S-tag.
(ether-type)
0x88a8
0x8100
0x9100
0x9200
Configuration guidelines
Customer Network frames are encapsulated with a 2nd VLAN (S-VLAN)

and forwarded to a PN port
PN ports transport multiple encapsulated networks, each associated with

a unique S-VLAN
CN ports remove the S-VLAN towards a Customer interface
Network #1
Radio
Ports
(PN)
S-VLAN 9
Network 1
S-VLAN 8
Network 2
C-VLAN 100
C-VLAN 101
C-VLAN 102
C-VLAN 103
C-VLAN 100
C-VLAN 101
C-VLAN 102
C-VLAN 103
Network #2
Page 181
4/21/2010
Simplified Flow
IP-10
S-VLAN 1000
S-VLAN 222
S-VLAN 1000
S-VLAN 222
CN
CN
ISP / BTS #1
ISP / BTS #2
C-VLAN 100
C-VLAN 101
C-VLAN 102
C-VLANs unknown
PN
Radio Port
CN-PN-PN-CN
Radio
Ports
(PN)
BTS #2:
C-VLAN 100
C-VLAN 101
C-VLAN 102
C-VLAN 103
C-VLAN 100
C-VLAN 101
C-VLAN 102
C-VLAN 103
S-VLAN 9
BTS 2
C-VLAN 100
C-VLAN 101
C-VLAN 102
C-VLAN 103
S-VLAN 8
BTS 1
CN
CN
CN
BTS #1:
C-VLAN 100
C-VLAN 101
C-VLAN 102
C-VLAN 103
6
CN
Page 182
4/21/2010
CN-PN-PN-PN
Radio
Ports
(PN)
BTS #2:
C-VLAN 100
C-VLAN 101
C-VLAN 102
C-VLAN 103
C-VLAN 100
C-VLAN 101
C-VLAN 102
C-VLAN 103
S-VLAN 9
BTS 2
S-VLAN 8
BTS 1
C-VLAN 100
C-VLAN 101
C-VLAN 102
C-VLAN 103
CN
CN
BTS #1:
C-VLAN 100
C-VLAN 101
C-VLAN 102
C-VLAN 103
PN
Customer Network
Provider Network
Switch Mode Configuration
2
1. Set mode to Metro (requires reset)
2. Add the S-VLAN ID (set & apply)
Page 183
4/21/2010
1. Go to Interfaces / Ethernet Ports page
2. Enable the port
3. Set the type to Customer Network
4. Type the port ID (EVC name, free string)
5. Type the S-VLAN ID
6. Enable Port Learning
7. Apply & Refresh
8. See screen capture next slide
9
2
1
3
4
5
10
Page 184
4/21/2010
1. Go to Interfaces / Ethernet Ports page
2. Enable the port
3. Set the type to Provider Network
4. Enable Port Learning
5. Edit (if needed) the allowed S-VLANs
6. Apply & Refresh
7. Set the required S-Tag (Ether-Type)
8. See screen capture next slide
11
2
1
4
6
5
12
Page 185
4/21/2010
PN Port Configuration Setting the S-Tag
13
0x88A8
0x8100
0x9100
0x9200
QoS with Metro Switch

CN ports only audits the P-Bit of C-VLANs:
Ingress frames through CN ports can be classified by applying a
VLAN P-Bit Classifier.
14
Page 186
4/21/2010
Thank You !
15
Page 187
3/7/2010

EMS RSTP Configuration
Agenda
Student Perquisites
General Overview
Limitations
Site / Node Types
Switchover Criteria
In Band Management
Out of band Management
Configuration Example
2
Page 188
3/7/2010
Student Perquisites
Viewers / end-user are required to have previous experience prior to
practicing this module:
1. End users should be familiar with Switch configuration

2. Be End users should be familiar with setting port membership
3. End users should be familiar with management mode configuration
4. End users should be familiar with configuring Automatic State Propagation
General Overview
Ceragon Networks ring solution enhances the RSTP algorithm for ring
topologies, accelerating the failure propagation relative to the regular
RSTP:
Relations between Root and Designated bridges when ring is converged in the
first time is the same as defined in the standard RSTP. Ring-RSTP itself is
different than classic RSTP, as it exploits the topology of the ring, in order to
accelerate convergence.
Ethernet-Fast-Ring-RSTP will use the standard RSTP BPDUs:
01-80-C2-00-00-00.
The ring is revertible. When the ring is set up, it is converged according to
RSTP definitions. When a failure appears (e.g. LOF is raised), the ring is
converged. When the failure is removed (e.g. LOF is cleared) the ring reverts
back to its original state, still maintaining service disruption limitations.
RSTP PDUs coming from Edge ports are discarded (and not processed or
broadcasted).
4
Page 189
3/7/2010
Ring RSTP Limitations

1. Ring RSTP is a proprietary implementation of Ceragon Networks, and
cannot interwork with other Ring RSTP implementations of other 3rd party
vendors.
2. Ring RSTP can be activated only in Managed Switch application, and is not
available in any other switch application (Single Pipe or Metro).
3. Ring RSTP should NOT be running with protection 1+1.
Site / Node Types

The ring can be constructed by two types of nodes/sites:
1. Node/Site Type A:
The site is connected to the ring with one Radio interface (e.g. East) and one
Line interface (e.g. West).
The site contains only one IP-10 IDU. The Radio interface towards one
direction (e.g. East), and one of the Gigabit (Copper or Optical) interfaces,
towards the second direction (e.g. West).
Other line interfaces are in edge mode, meaning, they are user interfaces,
and are not part of the ring itself.
Page 190
3/7/2010
Site / Node Types

The ring can be constructed by two types of nodes/sites:
2. Node/Site Type B:
The site is connected with Radios to both directions of the ring (e.g. East &
West).
Site contains two IDUs. Each IDU support the Radio in one direction
One IDU runs with the Ring RSTP, and the second
runs in Single pipe mode.
Both IDUs are connected via Gigabit interface
(either optical or electrical).
Other line interfaces are in edge mode.
Switchover / Convergence Criteria

The following failures will initiate convergence:
Radio LOF
Link ID mismatch.
Radio Excessive BER (optional)
ACM profile is below pre-determined threshold (optional).
Line LOC
Node cold reset (Pipe and/or Switch).
Node power down (Pipe and/or Switch)
xSTP port disable / enable
Page 191
3/7/2010
In-Band Management (1)

In this scenario, management is part of the data traffic, thus, management is
protected with the traffic when the ring is re-converged as a result of a ring
failure.
Managed Switch IDUs will be configured to In-Band, while Single Pipe
IDUs will be configured to Out-of-Band.
Single Pipe nodes will be connected with external Ethernet cable to the
Managed Switch for management.
The reason for that requirement is the automatic state propagation
behavior of the Single Pipe that shuts down its GbE traffic port upon failure,
thus, management might be lost to it.
In-Band Management (2)
10
Page 192
3/7/2010
Out of band Management (1)

In this scenario, all elements (Single pipe and Managed Switch IDUs)
should be configured to Out-of-band, with WSC enabled. Management will
be delivered over WSC.
External xSTP switch should be used in order to gain resilient management,

and resolve the management loops.
The following picture demonstrates 4 sites ring, with out-of-band management:
11
Out of band Management (2)
12
Page 193
3/7/2010
Configuration
Example
13
RSTP Example (1)

Site #2
Site #1
3
Pipe (slot #2)
Pipe (slot #3)

3
MNG (slot #1)
Pipe (slot #2)
MNG (slot #1)
Site #3
3
Pipe (slot #2)
MNG (slot #1)
Establish the physical connections according to the setup scheme.

Leave one link disconnected to avoid loops (for example: site #3 to site #2)
Configure In-Band MNG using VLAN #200 (or other) on all main IDUs
14
Page 194
3/7/2010
RSTP Example (2)

Site #2
Site #1
3
Pipe (slot #2)
Pipe (slot #3)

3
MNG (slot #1)
Pipe (slot #2)
MNG (slot #1)
Site #3
3
Pipe (slot #2)
MNG (slot #1)
Connect extension IDUs (port #3) to Main IDUs

(port #3 & port #4, members of VID #200). Use ETH cross-cables.
Configure Port 3 (& port 4 of site #2) of Main units as trunks members of VID 200
to transport the management packets
15
RSTP Example (3)

Site #2
Site #1
3
Pipe (slot #2)
Pipe (slot #3)

3
MNG (slot #1)
Pipe (slot #2)
MNG (slot #1)
Site #3
3
Pipe (slot #2)
MNG (slot #1)
Disconnect IDUs from Switch (except for GW IDU)

Enable RSTP on all Managed Switches (Main)
PING EMS to all Sites
Connect the broken radio link (site #1 to Site #3)
16
Page 195
3/7/2010
RSTP Example (4)
Use the EMS to learn which switch is the Root Bridge and which ports are the Root Ports.
Verify that the ring is set up properly (one Root)
17
RSTP Example (5)
Identify the Edge Ports and Non-Edge ports in your scheme and make sure they are
configured the same in your setup
18
Page 196
3/7/2010
RSTP Example (6)
Identify the Edge Ports and Non-Edge ports in your scheme and make sure they are
configured the same in your setup
19
RSTP Example (7)

Make sure that all RING
IDUs (Pipe & Managed)
are support Automatic
State Propagation
(enabled).
Enabling ASP allows RSTP
Ring to converge faster by
propagating radio alarms
into the Line and thus,
accelerating port state
changes.
20
Page 197
10
3/7/2010
RSTP Example (8)

Disconnect a radio link and make sure PING to all Main units is maintained
Restore connectivity.
Disconnect a different radio link and make sure PING to all Main units is maintained
Repeat the same tests with traffic and trails (SNCP).
21
Thank You !
22
Page 198
11
6/1/2010

QoS Concept & Implementation
Agenda
Introduction
Why do we need QoS?
Not all Traffic are the same
Traffic Engineering as a solution
QoS in IP-10
Page 199
6/1/2010
Introduction (1)
IP-10 is more than a Radio:
High capacity MW Radio

Up to 500Mbps @ 56MHz
ADM Add & Drop Multiplexer:

It enables a matrix of cross-connections
between TDM E1/T1,SDH VCs and
Radio channels
ADM
L2ETH
SW
L2 ETH Switch:
802.1p/q
P-Bit remap
Policers
Shaping
Scheduler
IPv4 / IPv6 Classification
MW
Radio
Introduction (2)
In this presentation we shall focus on the QoS implemented with the
integrated L2 ETH switch
But first, let us understand

what does Quality Of Service
stands for
ADM
L2ETH
SW
MW
Radio
4
Page 200
6/1/2010
Understanding QoS
Why do we need QoS? (1)

Without controlling our Backbone /Core infrastructure High cost of non-responsiveness: devices are deployed but not properly
allocated to transport customer traffic
On the other hand bad resource design results in congestion which will lead
to network downtime costs due to degradation of performance
QoS (e.g. - Traffic Engineering) optimizes
network resources
Page 201
6/1/2010
Why do we need QoS? (2)

Mobile operators focus on reducing costs:
Mobile Broadband growth requires Backhaul expansions, hence:
are stretching
Operators
p
g their cost-saving
g initiatives
Operators will look for new ways to drive further Backhaul savings
Operators must reduce their cost per Mbit
QoS (e.g. - Traffic Engineering) optimizes network resources
Wireless Carrier Ethernet

Backhaul Network
Business center
GE
WiMAX / 4G / LTE
Cellular site
WiMAX
STM-1 / OC-3
Ceragon
TDM
E1/T1
Ceragon
Hub / Aggregation site
2G/3G base station
Fundamental Fact
Dynamic
WWW
Static
WWW
Multimedia
FTP
Not all traffic is the same!
emails
Skype
So why treated equally?...
Whosfirst?
8
Page 202
6/1/2010
Traffic Engineering as a Solution

Your 1st assignment is identifying needs & solutions:
Dynamic
WWW
What is the BW requirement per service ?

Video requires more than voice
Static
WWW
Multimedia
Data
D t requires
i
lless th
than video
id
FTP requires more than emails
FTP
What is the delay sensitivity of each service?
emails
Delayed Voice is inacceptable

FTP can tolerate delays
Skype
Your 2nd assignment is grouping services into SLAs:
Video & Multimedia Low Services (Best Effort)
FTP Moderate Service
Skype Highest Service
Your 3rd assignment is configuring QoS in your network

9
QoS in IP-10
Page 203
6/1/2010
IP-10G L2 ETH Switch Ports
The IP-10Gs L2 Switch has 8 ports:
Port #1 GbE (Opt. / Elec.)

p / Elec.))
Port #2 GbE ((Opt.
Port #3 to port #7 FE
Port #8 (Radio port)
11
QoS Process
Q4
Q4
25
10
50
Q1
Q3
Q2
Rate Limit
Queuing
Scheduling
Egress Port (s)
Ingress Port
12
Shaping
Page 204
6/1/2010
Ingress VS. Egress

Every Switch port applies Ingress Rules and Egress Rules depending on traffic
characteristics (L2 header and applied policies)
Ingress
port
Egress
port
Customer
Network
Provider
Network
Egress
port
Ingress
port
Customer
Network
Provider
Network
13
Ingress VS. Egress: IP-10

Radio port (ETH port #8):
Ingress traffic relates to traffic received from remote IDU
Egress traffic relates to traffic sent to remote IDU
Non-Radio ports (ports 1 to 7*):

Ingress traffic relates to traffic received from customer
Egress traffic relates to traffic sent to customer
Ingress
Egress
P t 1-7*
Port
1 7*
Port 1-7*
Radio
Radio
Egress
Ingress
* Ports 7, 6 & 5 can be used as management or data
14
Page 205
6/1/2010
Ingress Rate Limiting

Users can configure maximum ingress rate per port
Exceeding traffic will be discarded
Rate limitation can be configured per type of traffic (Policers)
FE Max.
Rate
25
10
50
100Mbps
Discard
Max. Allowed
R
Rate
t
Pass
Actual
Customer
Traffic
Time
Example: Policer assigned to FE interface
15
Using Queues
Every port of the L2 switch examines the ingress traffic and then it sorts it in a
buffer according to classification criteria
This process is called Queuing
Users can configure up to 4 queues where Q4 has the max. priority and Q1
has the lowest priority
Q4
High
Q3
Q2
Q1
16
Low
Page 206
6/1/2010
Using Queuing
17
Scheduling (1)
Once the queues are filled with information, we need to empty them
Which queue should we empty first?
Round-Robin:
Emptying cycle is fixed all queues are treated equally
Q4
High
Q4
Q3
Q3
Q1
Q1
Q2
Q1
18
Q2
Q3
Q4
Q1
Q2
Q3
Q4
Q2
Pro: no queue starvation
Con: no prioritization
Low
Page 207
6/1/2010
Scheduling (2)
Weighted Round-Robin:
Emptying cycle is configurable every queue can be given specific weight
Q4
High
Q4
Q4
Q3
Q1
Q3
Q2
Q3
Q4
Q4
Q1
Q2
Q3
Q4
Q4
Q2
Q1
Low
19
Scheduling (3)
4th Strict Priority:
The switch will empty Q4 as long as it has something
Once empty switch will perform RR on lower queues
If Q4 receives a frame during the Lower-Queues-RR, it will go back to focus
on Q4
Q4
High
Q1
Q3
Q3
Q3
20
Q4
Q1
Q2
Q3
Q4
Q4
Q2
Q2
Q1
Q4
Pro: Optimized Prioritization

Con: Queue starvation
Low
Page 208
10
6/1/2010
Scheduling (4)
All Strict Priority:
The switch will empty a queue as long as the higher queue is empty
Q4
High
Q3
Q3
Q4
Q4
Q1
Q2
Q3
Q4
Q4
Q2
Q1
21
Low
Shaping
Bursts beyond a EIR (Excessive Information Rate) can be buffered and
retransmitted when capacity frees up, and only when shaping buffers are full
will packets be dropped.
22
Page 209
11
6/1/2010
Possible Scenarios
f
No need for
Ingress Queuing
Port 1-7*
Port 1-7*
Radio
Ingress
Queuing
Radio
Radio Egress
Scheduler =
Strict Priority
23
No need
g
for Egress
Scheduler
Possible Scenarios
Ingress Queuing is
required in port 8
Port 1-7*
Port 1-7*
Radio
Ingress
Queuing
24
Radio
Radio Egress
Scheduler =
Round Robin
Egress
Scheduler
is required
Page 210
12
6/1/2010
ThankYou!
training@ceragon
com
25
Page 211
13
3/7/2010

EMS Basic QoS Configuration
Perquisites
End-users must be familiar with the following items prior to taking
this module:
Introduction to Ethernet
802.1p/q
QoS (Concept)
IP-10 Switch Configuration
Trunk VS. Access
2
Page 212
3/7/2010
Agenda
Introduction
IP-10 L2 Switch ports
Step #1: Configure the switch
Step #2: Configure the switch ports
Step #3: Configure QoS per port
Process Review
Basic Configurations
Introduction (2)
In this presentation we shall focus on the L2 ETH switch:
Four priority (CoS) queues
Advanced CoS classifier:
VLAN Pbits / VLAN ID (RFC 802.1p,q)
IPv4 (RFC 791) / IPv6 (RFC 2460, RFC 2474)
MAC DA
Advanced ingress traffic policing /
rate-limiting per port/CoS
ADM
L2 ETH
SW
Flexible scheduling:
Strict Priority, WRR or HRR
Traffic shaping
MW
Radio
802.3x flow control (for loss-less) operation
Page 213
3/7/2010
IP-10G L2 ETH Switch Ports
The IP-10Gs L2 Switch has 8 ports:

Port #3 to port #7 FE
Port #8 (Radio port)
Step #1: Set your Switch

Configure the switch mode: Pipe / Managed / Metro
Configure VLAN IDs
Page 214
3/7/2010
Step #2: Configure Switch Ports

Configure Port Type: Access / Trunk
Configure Port Membership
Step #3: Configure QoS per Port
Page 215
3/7/2010
Process Review
Policer per port
25
10
50
Rate Limit
10
Page 216
3/7/2010
3 classifiers to audit & queue Ingress Traffic
Queuing
11
Egress port Scheduler
Q4
Q4
Q1
Q3
Q2
Scheduling
12
Page 217
3/7/2010
Egress Port Shaper
Shaping
13
Basic Configurations
Page 218
3/7/2010
1. Ingress Rate Limiting
Lets say we want to limit Video streams

from customer interface towards the
network
Video streams are characterized with a
UDP protocol & multicast address
Therefore we shall define a Policer to
limit these parameters
15
1. Ingress Rate Limiting Setting a Policer

There are 15 different
traffic types that we
can use
Each Policer can have
up to 5 conditions
16
Page 219
3/7/2010
1. Attaching a Policer to a port

To attach a Policer to a port simply type the Policer name
17
2. Queuing according to Ingress P-Bits

Click on the VLAN Pbits to Queue link to open the configuration table
Using this table we can map 8 priority levels to 4

queues or lower number of classes
This table is global and can be used for other tasks
as well
18
Page 220
3/7/2010
2. Queuing according to Ingress P-Bits

Select VLAN Pbits as the 3rd classifier as shown below:
Set the Egress Scheduler as required -
19
3. Queuing Ingress Frames according to MAC

Click on the Static MAC link to open the configuration table
In this example, we prioritize 3 frames according to their MAC DA.

The ingress frames are put in a queue according to the Priority settings and VLAN P-Bits to Queue
table. Ingress frames with MAC DA that are not listed in this table will be handled by the next
classifiers .
20
Page 221
10
3/7/2010
3. Queuing Ingress Frames according to MAC

Next, select Queue Decision as the 1st criteria
Frames with MAC that do not comply to the table will be classified by the 2nd &
3rd classifiers
21
4. Queuing Ingress Packets according ToS / DSCP
Click on the IP Pbits to Queue

Link to configure ToS /DSCP for IPv4
or IPv6
22
Page 222
11
3/7/2010
4. Queuing Ingress Packets according ToS / DSCP

Next, select IP-TOS as the 3rd criteria
23
5. Assigning Port traffic to a specific Queue

Select Port as the 3rd criteria
Select to which queue the port should assign the ingress frames
24
Page 223
12
3/7/2010
6. Queuing Ingress frames according to VLAN ID

Click on the VLAN ID to Queue Link to configure the table
25
6. Queuing Ingress frames according to VLAN ID

Select Queue Decision as the 2nd criteria
Frames with VID that do not comply to the table will be classified by the 3rd
classifier
26
Page 224
13
3/7/2010
7. Egress Shaper
Reducing the egress rate to a value between 64kbps and 1Mbps requires
setting it in steps of 64kbps
Reducing the egress rate to a value between 1Mbps and 100Mbps requires
setting it in steps of 1Mbps
Reducing the egress rate to a value between 100Mbps and 1Gbps requires
setting it in steps of 10Mbps
27
Thank You !
28
Page 225
14
3/7/2010

Advanced QoS Configuration
Agenda
VLAN P-Bit Re-Map Why?
Configuring the Re-Map Table
Queuing without Re-Map
Queuing with next classifier + Re-Map
Queuing + Re-Map
IP ToS over VLAN P-Bits
VLAN P-Bits over IP ToS
Using more than a single Classifier
2
Page 226
3/7/2010
P-Bit Re-Map: Why?

Re-Map table is per port (e.g. every port can apply a different map)
Can be used to re-scale Customer CoS
Can be used to guaranty certain Customer priorities are reserved for specific
purposes
Customer
network
P-Bit
Service
P-Bit*
Service
0-2
Video
0-5
34
Data
Best
Effort
56
MNG
MNG
Voice
Voice
L2 Switch
(IP-10)
Provider
network
Configuring the Mapping Table

Click on the VLAN Pbits Remap Table link to configure relevant settings
Page 227
3/7/2010
Queuing without Re-Mapping

Ingress
Tagged
frame
VID
P-bit
Ingress
Rate Limit
Queuing
according
to classifier
Egress
Scheduler
Egress
Shaper
VID
P-bit
Skipping to next classifier with Re-Map

Re-Map
Table
Ingress
Tagged
frame
VID
P-bit
Ingress
Rate Limit
Queuing
according
to next
classifier
Egress
Scheduler
Egress
Shaper
VID
P-bit*
Page 228
3/7/2010
Queuing and Re-Mapping

Re-Map
Table
Ingress
Tagged
frame
VID
P-bit
Ingress
Rate Limit
Queuing
according
to classifier
Egress
Scheduler
Egress
Shaper
VID
P-bit*
Conditional Classification
Page 229
3/7/2010
IP ToS over VLAN P-Bits

In case the ingress frame carries a VLAN and has an IP header Classification is according to IP TOS
Otherwise the switch will apply the Default Configuration (Queue number).
L2 Tagged ETH
L3 IP Header
VLAN P-Bits over IP ToS

In case the ingress frame carries a VLAN and has an IP header Classification is according to VLAN P-Bits
Otherwise the switch will apply the Default Configuration (Queue number).
L2 Tagged ETH
10
L3 IP Header
Page 230
3/7/2010

As long as the ingress frames comply to the higher conditions, the system will
not check lower conditions (Classifiers)
If higher condition is not matched, the system will proceed to the lower
condition and so on
11

Audit VID : if VID = 100 than apply High Service
if VID = 200 than apply Low Service
otherwise -
Otherwise
2nd criteria: VLAN ID
If ingress VID does not qualify (100 or 200)
100 or 200
then skip to -
Audit VLAN P-bits
Ingress
frames
VID = ?
100
Highest
100
Highest
100
Highest
100
Highest
200
Lowest
3rd criteria: P-Tag

7
Highest
6
3
Different than
100 or 200
12
2
0
Lowest
Page 231
3/7/2010
Thank You !
13
Page 232
4/30/2010
FibeAirIP10Series
Commissioning the Radio Link
Radio Link Common Attributes

# Link ID
IP10
IP10
RSL
Received Signal [dBm]
MSE
Mean Square Error [dB]:

Modulation status
Signal to Noise Ratio (SNR)
Max. TSL Max. allowed Transmission Signal [dBm]

Monitored TSL Actual Transmission level [dBm]
# - Link ID: must be the same on both ends
2
Page 233
4/30/2010
LINK ID

To avoid pointing the antenna to a wrong direction (when both links share the
same frequency), LINK ID can be used to alert when such action is take.
# 101
# 101
# 102
Link ID
Mismatch
# 101
Link ID Mismatch
Page 234
4/30/2010

Both IDUs of the same link must use the same Link ID
Otherwise, Link ID Mismatch alarm will appear in Current Alarms Window
# 101
# 101
# 102
Link ID
Mismatch
# 101
Link ID Mismatch
ATPC
Page 235
4/30/2010

The quality of radio communication between low Power devices varies
significantly with time and environment.
This phenomenon indicates that static transmission power
power, transmission range
range,
and link quality, might not be effective in the physical world.
Static transmission set to max. may reduce lifetime of Transmitter

Side-lobes may affect nearby Receivers (image)
Main Lobe
Side Lobe

To address this issue, online transmission power control that adapts to
external changes is necessary.
In ATPC, each node builds a model for each of its neighbors, describing the
correlation between transmission power and link quality.
With this model, we employ a feedback-based transmission power control
algorithm to dynamically maintain individual link quality over time.
Page 236
4/30/2010

1. Enable ATPC on both sites
2. Set reference RSL (min. possible RSL to maintain the radio link)
3. ATPC on both ends establish a Feedback Channel through the radio link (1byte)
4. Transmitters will reduce power to the min. possible level
5. Power reduction stops when RSL in remote receiver reaches Ref. level
TSL Adjustments
ATPC
module
Monitored RSL
Radio
Transceiver
Radio
Radio
Receiver
Feedback
Radio
Receiver
Signal
Quality
Check
Site A
Ref. RSL
RSL
required
change
Site B
ATPC OFF = High Power Transmission
ATPC:
Disabled
ATPC:
Disabled
Max. TSL:
10 dBm
Max. TSL:
10 dBm
Monitored TSL:
Monitored RSL:
10 dBm
-53 dBm
Monitored TSL:
Monitored RSL:
8 dBm
-56 dBm
ATPC
module
Radio
Transceiver
Radio
Radio
Receiver
Feedback
Site A
10
Radio
Receiver
Signal
Quality
Check
Ref. RSL
RSL
required
change
Site B
Page 237
4/30/2010
ATPC ON =
Reduced Power, cost & long-term maintenance
ATPC:
Ref. RSL:
Enabled
-65
65 dBm
ATPC:
Ref RSL:
Ref.
Enabled
- 65 dBm
Max. TSL:
10 dBm
Max. TSL:
10 dBm
Monitored TSL:
2 dBm (before 10)
Monitored TSL:
2 dBm (before 8)
Monitored RSL:
-60 dBm (before 53)
Monitored RSL:
-63 dBm (before 56)
ATPC
module
Radio
Transceiver
Radio
Radio
Receiver
Feedback
Site A
11
Radio
Receiver
Signal
Quality
Check
Ref. RSL
RSL
required
change
Site B
Page 238
4/30/2010

Designed to work with ACM in certain scenarios to allow higher Tx power
available at lower order modulation schemes for a given modulation scheme.
When Adaptive TX is disabled:

Maximum TX power is limited by the highest modulation configured in the MRMC ACM
script.
In other words, when link suffers signal degradation, modulation may change from
256QAM to QPSK. However, Max. power will be limited to the value corresponding as
Max. TX in 256QAM.
When Adaptive TX is Enable:

When link suffers signal degradation, modulation may change from 256QAM to QPSK.
However, Max. power will increase to compensate for the signal degradation.
13
MRMC Adaptive Power = OFF
256QAM @ Monitored TSL = 18 dBm (Max.)

Signal Degradation
= Lower bit/symbol
16QAM @ MAX. TSL = 18 dBm
14
Page 239
4/30/2010
MRMC Adaptive Power = ON
256QAM @ Monitored TSL = 18 dBm(Max.)

Signal Degradation
= Lower bit/symbol
16QAM @ Monitored TSL = 24 dBm
15
MRMC Adaptive Power

It is essential that Operators ensure they do not breach any regulator-imposed
EIRP limitations by enabling Adaptive TX.
To better control the EIRP, users can select the required
q
class ((Power VS.
Spectrum):
Class 2
Class 4
Class 5B
Class 6A
FCC
RFU C should
h ld h
i 2.01
2 01 (or
( hi
h ) ffor proper ffunctionality
ti
lit off
RFU-C
have version
higher)
Adaptive TX Power feature.
The Effective Isotropic Radiated Power (EIRP) is the apparent power transmitted towards the
receiver assuming that the signal power is radiated equally in all directions
16
Page 240
4/30/2010
Configuration

Spectrum Mask
FQ spacing (gap) between channels
Monitored transmission power
Monitored recei
received
ed signal
Monitored Mean Square Error
Required value = zero
Radio frequencies can be set

locally or on remote unit as
well (assuming links is up)
Enable / Disable
Min. target RSL (local)
Enable = no transmission
Value depends on MRMC settings
Must be identical on both IDUs
18
Page 241
4/30/2010
Enable on both IDUs to get maximum

throughput (500Mbps @ 56MHz)
19
Radio Settings Remote Radio
When the radio link is up, you can configure certain

parameters on the remote unit:
Make sure Remote IP is available
Remote RSL can be read
Remote TSL can be set (depends on remote MRMC script)
Remote TX MUTE can be disabled (see next slide)
Remote target RSL for ATPC can be set
20
Page 242
10
4/30/2010
Remote Un-Mute
Simplified scheme
Sit B is
Site
i NOT transmitting
t
itti
but receiver is still ON
Site A is
transmitting
Site B
Site A
21
Radio Thresholds
These settings determine the sensitivity / tolerance for triggering:

1+1 HSB switchover
Ethernet Shutdown
PM generated alarms
22
Page 243
11
4/30/2010

Users may set the radio to a fixed capacity or automatic adaptive capacity using ACM.
ACM radio script is constructed of a set of profiles.
Each profile is defined by modulation order (QAM) and coding rate, while these
parameters dictate profiles capacity (bps).
When ACM script is activated, system chooses automatically which profile to use
according to the channel fading conditions.
ACM TX profile can be different than ACM RX profile.
ACM TX profile is determined by remote RX MSE performance.
RX end is the one that initiates ACM profile upgrade or downgrade.
When MSE is improved above predefined threshold, RX generates a request to the
remote TX to upgrade its profile.
If MSE degrades below a predefined threshold, RX generates a request to the remote
TX to downgrade its profile.
23
MRMC Configuration
We shall review this page using the following slides:

24
Page 244
12
4/30/2010
MRMC reading current script

MAX. Capacity
(w/out compression)
ACM Script
CH. BW
Modulation
Spectrum
Mask
ACM is on
Spectrum
Class Type
25
MRMC Reading current capacity
26
Page 245
13
4/30/2010
ThankYou!
training@ceragon
com
27
Page 246
14
3/7/2010

Configuring Interfaces
Agenda
Ethernet Interfaces
TDM Interfaces
AIS Detection
AIS Signaling (STM-1)
STM-1 Interface
Auxiliary Channels
Wayside Channel (Various Configurations)
Page 247
3/7/2010
Ethernet Ports Configuration

Configuring ETH ports is discussed in previous modules:
Switch Configuration
Trunk VS. Access
Metro Switch Configuration
QoS Configuration
Interface
Rate
Functionality
Single Pipe
Managed SW / Metro
ETH 1 (SFP)
GbE
Disabled / Traffic
Disabled / Traffic
ETH 2 (RJ 45)
GbE
Disabled / Traffic
Disabled / Traffic
ETH 3 (RJ 45)
FE 10 / 100
Disabled / Protection
Disabled / Traffic / Protection
ETH 4 (RJ 45)
FE 10 / 100
Disabled / Wayside
Disabled / Traffic / Wayside
ETH 5 (RJ 45)
FE 10 / 100
Disabled / MNG
Disabled / Traffic / MNG
ETH 6 (RJ 45)
FE 10 / 100
Disabled / MNG
ETH 7 (RJ 45)
FE 10 / 100
Disabled / MNG
ETH 8 Radio
(N Type)
According to
Licensed fq.
Disabled / Traffic
Disabled / Traffic
Ethernet Ports Configuration
Page 248
3/7/2010
TDM Ports Configuration

IP-10G has 16 TDM ports + 16 additional ports when a 2nd T-Card
is installed.
Supported PHYs:
E1
DS1
Dynamic allocation:
Radio bandwidth (which may vary in ACM) is automatically allocated in the
following order:
1. High-priority TDM trails
2. Low-priority TDM trails
3. Ethernet traffic (Data + Management, QoS should be considered)
TDM trails in both sides of a link should have identical priorities.
TDM Ports Configuration Standalone IDU
E1/DS1 port #n will be mapped to

radio VC#n (n=1-16).
When Trails are configured, default
mapping (above) is overwritten by Trail
Mapping.
However, if no trails are configured (all
are deleted) system will revert to the
default setting.
When Trail is configured and set to
Operational - TDM port is activated.
When Trail is configured but set to
Reserved - TDM port is disabled.
Page 249
3/7/2010
TDM Ports Configuration Node Site
Up to 180 trails can be configured in a

Shelf / node
The number of Trails mapped to a
radio depends on radio capacity
(MRMC).
The maximum number of radio Trails
is 75 (E1) or 84 (DS1).
AIS Line Detection

This feature allows detection of AIS
signals in TDM traffic incoming from line
interfaces (E1/DS1, STM-1):
In case of detection, the following takes place:

Signal failure is generated at the corresponding trail this will cause the
far end not to receive a signal (including trail ID indications) and the trail
status to show signal failure and trail ID mismatch.
An indication is given to user at the proper interface. Notice that this is
not a system alarm, since the problem originates elsewhere in the
Network
Page 250
3/7/2010
AIS Signaling in STM interface (VC 12)

In case of signal failure at the trail outgoing from the STM-1
interface, AIS will be transmitted at the payload of the VC-12.
STM interface Configuration

The following configurations are available:
Admin: Enable / Disable
When interface is disabled:
There is no signal transmission
Received signal is ignored
Trails previously configured to STM-1 interface will get
Signal Failure
No alarms will be shown
Clock source: Internal Clock / Loop / TDM Trail
Mute TX: mutes the outgoing STM-1 signal, but received
signal will be used for traffic
Excessive BER threshold: specific for STM-1 interface
Signal degrade threshold: specific for STM-1 interface
10
Page 251
3/7/2010
AIS Signaling in STM interface (V5)

The system can be configured to signal AIS at the VC
level (AIS-V) in the V5 byte of the overhead.
This is meant to provide indications to SDH
multiplexing equipment which may not have the ability
to detect AIS at the payload level.
For example: signaling in outgoing V5 byte upon AIS
detection at payload-level (E1)
111111111
111111111
AIS @ E1 TS
11
AIS @ STM V5
STM interface Configuration

J0 trace identifier is fully supported in both
15-byte and 1-byte modes:
An alarm will be raised when the expected string
differs from the received string (but traffic will not be
affected).
Transmit, Expected and Received strings are
provided.
If a string is defined and user changes the length
from 15 bytes to 1 byte, the first byte will be analyzed
and other bytes ignored.
The string transmitted as J2 trace identifier is the Trail
ID defined for the TDM trail mapped to the
corresponding VC-12 interface.
12
Page 252
3/7/2010
Auxiliary Interfaces
Up to 19200 baud, Asynchronous RS-232.

Up to 19200 baud, Asynchronous V.11.
EOW may be used as a simple solution for on-site

communication between two technicians / installers / etc.
13
WSC Interface
WSC interface is limited to 1628 bytes.
2.048Mbps (Wide) or 64Kbps (Narrow)
Consumes BW from the total link BW
Out of band Management using WSC:

In this case, remote system is managed using Wayside channel.
On both local & remote units, Wayside channel will be connected to management port
(using cross Ethernet cable).
WSC can be configured to "narrow capacity (~64kbps) or "wide" capacity (~2Mbps).
It is recommended to use wide WSC in order to get better management performance,
since narrow WSC might be too slow.
14
Page 253
3/7/2010
OOB MNG in a 1+0 standalone link
At least 2 management ports are needed in a local unit:

One port for local management, and 2nd port that will be connected to Wayside port.
On remote unit, Wayside port will be connected to management port.
15
OOB MNG in a 1+1 standalone IDUs (Y-Splitter)
WSC port will be connected in each unit to other

available management port.
In remote site, each unit's Wayside port should be
connected to management port.
16
Active & Standby MNG

ports have 2 options to be
connected to the Host:
Using Ethernet splitter
cable connected to external
switch.
Using Protection "Patch
Panel".
Page 254
3/7/2010
OOB MNG in a 1+1 standalone IDUs (P. Panel)
17
Thank You !
18
Page 255
3/7/2010

XC / SNCP / Nodal Solution
Introduction
Page 256
3/7/2010
SNCP (ITU- G.805)
Ring topologies provide path protection for Ethernet or TDM signals
In some scenarios additional protection is required
The IP-10G Path-Protection is based on SNCP

(Sub-network Connection Protection)
Individual E1/T1 trails will be protected by defining two separate trails, with the same
end-points, which are routed through two different paths in the network
The end-points may be line interfaces or radio VCs, so partial path protection can
be provided for a trail in a network where full path redundancy topology is not
available
The end-points are also referred to as branching-points
SNCP (ITU- G.805)
With Wireless SNCP, a backup VC trail

can be optionally defined for each
individual VC trail
Main Path
Protective Path
Page 257
3/7/2010
FibeAir IP-10 Integrated Nodal Solution

IP-10 IDU can be used as a Standalone unit (1U)
or in as a Nodal Solution
Connecting 2 IDUs requires a nodal enclosure:

Best economical future upgrade
Best flexibility for network designer
Easier to Install / Maintain / expand
The solution is modular and forms a single

unified nodal device:
Common Ethernet Switch
Common E1s Cross Connect
Single IP address
Single element to manage
FibeAir IP-10 Integrated Nodal Solution

Up to 6 units can be stacked to form single nodal device
Additional units can be added in the field as required
Additional Nodal enclosures and units can be added in the field as required without
affecting traffic
Multiple nodes can be cascades to support large aggregation sites

Stacking is done using 2RU Nodal enclosures
Each enclosure has 2 slots for hot-swappable 1RU units
Front
Nodal enclosure
Rear
Page 258
3/7/2010
FibeAir IP-10 Nodal Enclosures

Extension nodal enclosure
Main nodal enclosure
FibeAir IP-10 Scalable Nodal Enclosures

Pay as you grow !
Page 259
3/7/2010
Integrated nodal solution Main units

Units located in the bottom Nodal enclosure are acting as the main units
The main unit performs the cross-connect, switching and management functions for
all the units in the node
Mandatory active main unit can be located in any of the 2 slots

Optional standby main unit can be installed in other slot
Switchover time <50msecs for all traffic affecting functions
Integrated Ethernet Switching

Integrated TDM cross-connect
Main unit
M
E
Native2
1+1 HSB
Expansion unit
Integrated nodal solution Expansion units

Units located in non-bottom Nodal enclosures are acting as expansion units
All interfaces of the expansion units (radio, TDM and Ethernet) are connected to the
main units
Expansion unit is fully managed through the main units
Radios in each pair of main/expansion units can be configured as either:
Dual independent 1+0 links

Single 1+1 HSB link
Single 2+0/XPIC link
Native2
1+0
Integrated Ethernet Switching
Integrated TDM cross-connect
Native2
1+0
E
M
Main unit
Expansion unit
Native2
2+0/XPIC
M
M
Native2
1+1 HSB
Page 260
3/7/2010
Trail Configuration Guidelines
XC Trails Guidelines (1)

1. XC Trails can be configured only via Main unit
2. All Trails are transported through main unit(s)
3. When Protection is enabled, configure trails to go via the Active unit
(XC Trails are automatically created on the STBY unit)
4. T-Cards (TDM / SDH) are not hot-swappable, do not extract / insert card
when IDU is powered up
5. Radio VCs must be identical on both sides of the radio link
12
Page 261
3/7/2010

5. Creating a TDM trail automatically activates the corresponding TDM port,
therefore an alarm will display next to the relevant T-Card accommodating
the activated port(s)
7. XC Trails can be configured between:
Radio to Line
Line to Radio
Radio to Radio
8. Maximum number of Trails per Node = 180

9. Maximum number of Trails per Radio = 75 (E1) or 84 (T1) or 168 (SNCP)
13

Identify Trail interfaces prior to configuration
Note that Trail configuration is Bi-Directional !
Trail traverses through here:

We shall need to define 2
interfaces
IP-10
IP-10
Bypass
site
Protected Trail
(Automatic)
IP-10
Radio Link
14
Trail starts here:

For SNCP we shall
need to define 3
interfaces
Trail starts here:

For SNCP we shall
need to define 3
interfaces
Page 262
3/7/2010

Pay attention to the order of configuration:
1
2
The Trail Start/End points should

be configured first (interface #1)
IP-10
IP-10
3
Bypass
site
Interfaces #2 and #3 can be

configured in a random order
Protected Trail
(Automatic)
2
IP-10
1
15
Standalone non-protected Trail Configuration
Page 263
3/7/2010
Step #1: Access Trail Page
Click on the Add button
17
Step #2: Configure 1st Interface

Click on the 1st interface connector
In this example we selected the
PDH connector.
Your next step is selecting the PDH
port number.

SDH connector.
Your next step would be selecting
the VC number.
18
Page 264
3/7/2010
Step #3: Configure 2nd Interface

Click on the 2nd interface connector
Radio as the next interface
connector.
Your next step would be selecting
the radio channel number.
Alternatively you could choose other combinations as well:

PDH to PDH
PDH to Radio (above)
PDH to SDH
SDH to Radio
SDH to Radio
Radio to SDH
Radio to PDH
19
Step #4: Configure Trail Attributes

Make sure Trail ID is unique and identical on all sites/trails
20
Page 265
10
3/7/2010
Step #5: Trail Verification

If your settings are correct, trail alarms should disappear, trail path is ready to be tested
21
SNCP Trail Configuration in a Node
Page 266
11
3/7/2010
Selecting Main IDU for Trail Configuration

In the following example we assume every node has 2 IDUs installed in a
Main Enclosure
Make sure your Main unit is selected on every Node-EMS
Enable Protection when you configure the Trails (excluding Bypass Nodes)
Trail ID should unique and identical on all nodes
23
SNCP Trail in Nodal Architecture

PDH interface
Bypass
Node
IP-10
IP-10
IP-10
SDH interface
24
Page 267
12
3/7/2010
1st Node
PDH interface
IP-10
IP-10
Bypass
site
Radio CH #1
Radio CH #26
IP-10
SDH interface #1
25
Bypass Node
PDH interface
Radio CH #48
IP-10
Bypass
Node
IP-10
Radio CH #1
IP-10
SDH interface
26
Page 268
13
3/7/2010
3rd Node
Radio CH #48
PDH interface
IP-10
Bypass
site
IP-10
Radio CH #26
IP-10
SDH interface
27
Thank You !
28
Page 269
14
4/30/2010
FibeAir IP-10 Series

Automatic State Propagation
Agenda
Introduction
Interfacing IP-10 with external devices
VS. Functionality
Configuration VS
Dead Lock Example
ASP in Managed / Metro Mode
Page 270
4/30/2010
Introduction
Automatic State Propagation ("GigE Tx mute override") enables propagation of radio
failures back to the line, to improve the recovery performance of resiliency protocols
(such as xSTP).
The feature allows the user to configure which criteria will force GbE port (or ports in case
of remote fault) to be muted / shut down, in order to allow the network find alternative
paths.
The feature is not operational in "External Protection".
Radio LOF
Needtofind
alternativepath

When external devices do not support Fault Propagation
Configure the following:
1. Enable Local LOC - to mute local GbE when LOC is raised
2. Enable Remote Fault to mute local transmitter in case of remote LOF / Link ID
mismatch & LOC
3. Enable Local Excessive BER recommended but not necessary
Page 271
4/30/2010

When external devices support Fault Propagation (another IP-10)
Configure the following:
1. Disable Local LOC
2. Enable Remote Fault to mute local transmitter in case of remote LOF / Link ID
mismatch & LOC
3. Disable Local Excessive BER - to avoid a dead lock scenario
Example: Avoiding Dead Lock in Single Pipe

Site A
Site B
TX
RX
RX
TX
1. GbE FO breaks down or disconnects at the ingress port of Site A
Page 272
4/30/2010

Site A
Site B
TX
RX
RX
TX
LOC

2. LOC alarm is raised

Site A
Site B
TX
RX
RX
LOC
TX

3. LOC alarm triggers Site A to shut down its transmitter (TX Mute)
Page 273
4/30/2010

Site A
Site B
TX
LOC
RX
RX
LOC
TX

4. Site B detects silence on ingress port and declares LOC

Site A
Site B
TX
LOC
RX
RX
LOC
TX

4. Site B detects silence on ingress port and declares LOC
5. Site B shuts down its transmitter both sites are in a state of a dead lock
10
Page 274
4/30/2010
Automatic State Propagation in Single Pipe
11
Single Pipe - Propagation Criteria

Local and remote IDUs must
have identical settings:
Using Optical GbE (SFP)
1.
2.
3.
LocalCriteria:
Local
Criteria:
LOC(GbE)
RadioLOF
LINKIDMismatch
ExcessiveBER
ACMprofileisbelowthreshold
Actions:
Muteport1(GbESFP)
12
ASP Enabled
ACM profile threshold
Excessive BER enabled
Actions:
Muteport1(GbESFP)
Page 275
4/30/2010

Using Electrical GbE (RJ45)
1.
2.
3.
LLocalCriteria:
l C it i
RadioLOF
LINKIDMismatch
ExcessiveBER
Actions:
ShutdownElec.
port
13
ASP Enabled
Actions:
ShutdownElec.
port

Using Electrical GbE (RJ45)
1.
2.
3.
LocalGbE Criteria:
LOC
ASP Enabled
Portt is
P
i logically
l i ll closed
l
db
butt nott
shut down
LOC will not trigger port shut
down (it will not be possible to
enable the port when LOC is
cleared)
14
Remote LOC will not trigger

port shut down (it will not be
possible to enable the port
when LOC is cleared)
Page 276
4/30/2010
Automatic State Propagation in Managed / Metro Mode
15
ASP in Managed / Metro Mode

Alarms are never propagated to a GbE port
GbE will never shut down
Alarms will be propagated to the Radio port
In 1+1 external protection, ASP is disabled.
16
Page 277
4/30/2010
Managed / Metro - Propagation Criteria

1.
2.
3.
ASP Enabled
LocalCriteria:
RadioLOF
LINKIDMismatch
ExcessiveBER
8
Actions:
ShutdownRadio
17
Managed / Metro - Propagation Criteria

1.
2.
3.
Localcriteria:
GbE LOC
18
ASP Enabled
8
Actions:
Noactiontaken
ShutdownRadio
Page 278
4/30/2010
ThankYou!
training@ceragon
com
19
Page 279
10
LinkAggregation
(IEEE802.3ad)
Agenda
Agenda
Definition
Advantages
Feature Review
Applications
Load Balance Example
1
Page 280
Introduction to Link Aggregation

IEEE Definition:
Link Aggregation allows one or more links to be aggregated

together to form a Link Aggregation Group
Group, such that a MAC
Client can treat the Link Aggregation Group as if it were a
single link
N
The Link Aggregation Group is consisting of N parallel

instances of full duplex point-to-point links operating at the
same data rate
Traffic
T ffi sentt tto th
the ports
t iin such
h a group iis di
distributed
t ib t d th
through
h
a load balancing function
Advantages
g
2
Page 281
Benefits of using Link Aggregation

1. Increased aggregate bandwidth
Link Aggregation allows the establishment of full duplex point-to-point links
that have a higher aggregate bandwidth than the individual links that form the
aggregation.
The capacity of the multiple links is combined into one logical link.
100 Mbps

2. Improved Resiliency
In case of a failed link, remaining links take over utilization of new available BW
Traffic via LAG is distributed according to users policy improved reliability
3
Page 282

3. Reduced Complexity & Administration
When multiple ports are allocated between two ETH switches, broadcast storms are
created due to p
physical
y
loops.
p STP is required
q
to eliminate loops
p by
y blocking
g the redundant
port.
When multiple ports are allocated between 2 Routers, Routing Protocols are required to
control traffic paths.
With LA STP or routing protocols are not needed, therefore, less processing is involved.
STP requires blocking and

path cost calculations

4. Reduced Cost
Instead of utilizing an expensive GbE port(s) to transport 200Mbps
>> we trunk N x FE ports
4
Page 283

5. Improved Network Efficiency / Security
For sites with limited IP address space that nevertheless require large amounts of
bandwidth, you need only one IP address for a large aggregation of interfaces.
For sites that need to hide the existence of internal interfaces, the IP address of
the aggregation hides its interfaces from external applications.
(These examples refer to using L2 topologies as well)
Multiple
Interfaces
Single
Interface
Customer
Network
9
Public
Network
FeatureReview
5
Page 284
LAG Distribution Policy

Traffic sent to ports in a group is distributed through a load balancing function.
Two methods are available for Link Aggregation Group traffic distribution:
1. Simple XOR:
In this method the 3 LSBs of DA and SA are XORed and the result is used to select
one of the ports in the group.
This method can be used for testing & debugging.
2. Hash (default):
In this method the hash function (used by the traffic switch for address table lookups)
is used to select one of the ports in the group.
This provides better statistical load balancing.
11
LAG Distribution: Simple XOR

We can easily demo balanced traffic distribution using the XOR method
(Configure your Traffic Generator with the following MACs)
12
Stream
MAC(HEX)
Last3 bits
XORresult
AssignedLAGPort
SA>
>DA
00:20:8f:0a:02:01
00:20:8f:0a:01:01
001
001
000(0)
Link#1
SA>
>DA
00:20:8f:0a:02:02
00:20:8f:0a:01:02
010
010
000 (0)
Link#1
SA>
>DA
00:20:8f:0a:02:03
00:20:8f:0a:01:03
011
011
000 (0)
Link#1
SA >
SA>
>DA
00:20:8f:0b:e1:03
00:20:8f:0a:e1:04
011
010
001(1)
Link#2
SA>
>DA
00:20:8f:0b:e1:03
00:20:8f:0a:e1:01
010
101
010 (2)
Link#3
SA>
>DA
00:20:8f:0b:e1:07
00:20:8f:0a:e1:04
111
100
011(3)
Link#4
6
Page 285
Static LAG guidelines

1. Only traffic ports (including radio port) can belong to a LAG
2. Management ports / WSC ports cannot be grouped in a LAG
3. LAG is supported in IDUs configured as Managed or Metro switch
4. LAG is not supported in a Single Pipe mode
5. All ports in a LAG must be in the same IDU (same switch)
6. There may be up to 3 LAGs per IDU
7. A LAG may contain from 1 to 5 physical ports
13
Static LAG guidelines (continued)

8. LAGs are virtual ports that do not permanently exist in the system
9 When a LAG is created,
9.
created it will automatically inherit all the ports
ports
characteristics, except for the following:
xSTP role (edge, non-edge)

path cost
10. The LAG will initially receive default values for these parameters
11. Dynamic Link Aggregation (LACP) is not supported
14
7
Page 286
Grouping ports in LAG

Ports 1-2 (GBE ports) and ports 3-7 (FE only ports) cannot be in the same LAG
group even if the GBE ports are configured as 100Mbps.
GbE
FE
GbE
FE
IP-10 IDU
15
IP-10 IDU

Radio port (port 8) may be in a LAG with the GBE ports only
GbE
FE
GbE
FE
IP-10 IDU
16
8
IP-10 IDU
8
Page 287
Applications
pp
Introduction to Link Aggregation

Multiple PHYs are grouped together to support a higher capacity PHY.
Grouped ports are known as LAG Link Aggregation Group.
Stackable
(Nodal) Site
Multiple Radio System

implemented with LAG
Standalone Site
1
1
GbE
PHY
Multiple FE
ports as a LAG
GbE
PHY
18
Port #2 and Radio

form a LAG
9
Page 288
1+0 LAG
1
Static LAG
3rd party
Switch or Router
Dual (redundant) GbE interfaces facing the Switch/Router

Static Link Aggregation Group (or equivalent) configured on the Switch/Router
interfaces connected to the IP-10
Any failure in the local GbE interfaces will be handled by the link aggregation mechanism
19
1+1 HSB W/O LAG
3rd party
Switch or Router
1+1 HSB or
2+0 Multi-Radio
No need for LAG
Single GE interfacing a 3rd party Switch/Router

O ti l splitter/combiner
Optical
litt /
bi
iis used
d tto connectt tto each
h off th
the IP
IP-10
10 GbE interfaces
i t f
in
i
(1+1) protected configuration
STBY IP-10 GbE interface is disabled
MW Radio link switchovers are transparent to Switch/Router
(traffic interruption <50mSecs)
20
10
Page 289
1+1 HSB With LAG
3rd party
Switch or Router
No need for LAG

1+1 HSB or
2+0 Multi-Radio
Static LAG
Dual (redundant) GE interfaces facing the 3rd party Switch/Router
Static Link Aggregation Group (or equivalent) is configured on the Switch/Router
interfaces connected to the IP-10 units
STBY IP-10 disables its Ethernet interface towards the Switch/Router
As a result, the Switch/Router sends all traffic over the Ethernet interface connected to
the active IP-10
Any failure detected in radio link or Ethernet interface will trigger a switch-over to the
back-up unit with <50msecs traffic interruption on the radio link
The Switch/Router detects the switch-over and start sending traffic over the interface
connected to the new active unit only
21
1+1 HSB With dual GbE + LAG

1+1 HSB or
2+0 Multi-Radio
Static LAG
Static LAG
3rd party
Switch or Router
Static LAG
Dual (redundant) GE interface to the Switch/Router

Static Link Aggregation Group (or equivalent) is configured on the Switch/Router
interfaces connected to the IP-10s
Static Link Aggregation Group (or equivalent) is configured on the IP-10
2 optical splitter/combiners are used to connect each of the 2 interfaces on the
Switch/Router to each of the corresponding interfaces on the IP-10s
22
11
Page 290
1+1 HSB With dual GbE + LAG (cont.)

1+1 HSB or
2+0 Multi-Radio
Static LAG
Static LAG
3rd party
Switch or Router
Static LAG
STBY IP-10 disables its Ethernet interface towards the Switch/Router

Any failure detected in radio link or equipment will trigger switch-over to the back-up
IP- 10 unit with <50msecs traffic interruption on the radio link
Any failure in the local GbE interfaces will be handled by the link aggregation
mechanism without triggering switch-over to the back-up IP-10 unit!
23
LoadBalanceExample
p
12
Page 291
Load balance example

P
GbE
PHY
50%
50%
Port #2 and Radio
form a LAG
IDU #2 is configured as Single Pipe

IDU #1 is configured as Managed Switch to support LAG
Traffic injected via GbE port #1 is distributed evenly between Port #2 & Port #8
Port #2 is linked to a Pipe IDU, hence, a Multi-Radio system is achieved:
GbE port #1 = (50% via Radio #1) + (50% via Radio #2)
25

2) Alarm is
propagated
3) Port 2 is
shut down
P
S
GbE
PHY
1)
2)
3)
4)
5)
4) Port 2 is out
of the LAG
Radio #2 encounters a signal degradation

Since ASP is
Si
i enabled,
bl d the
th alarm
l
iis propagated
t d tto portt #2
IDU #1 detects the alarms and shuts down port #2
Port #2 is not part of the LAG
Radio #1 takes full control (100%) of traffic
Enable Automatic State Propagation on both IDUs
26
13
Page 292
1) Link
Degradation
X
50%
100%
5) Radio 1
takes 100%

Shut down
64QAM
P
GbE
PHY
X
50%
256QAM
100%
100%
To improve system resiliency, Automatic State Propagation can shut down the
LAG interface when ACM degrades below a pre-determined profile.
27
ThankYou!
28
14
Page 293
LinkAggregationGroupConfiguration
(IEEE802.3ad)
Agenda
Agenda
Guidelines Review
EMS Configuration
Using PM (RMON)
1
Page 294
Static LAG guidelines

1. Only traffic ports (including radio port) can belong to a LAG
2. Management ports / WSC ports cannot be grouped in a LAG
3. LAG is supported in IDUs configured as Managed or Metro switch
4. LAG is not supported in a Single Pipe mode
5. All ports in a LAG must be in the same IDU (same switch)
6. There may be up to 3 LAGs per IDU
7. A LAG may contain from 1 to 5 physical ports
Static LAG guidelines (continued)

8. LAGs are virtual ports that do not permanently exist in the system
9 When a LAG is created,
9.
created it will automatically inherit all the ports
ports
characteristics, except for the following:
xSTP role (edge, non-edge)

path cost
10. The LAG will initially receive default values for these parameters
11. Dynamic Link Aggregation (LACP) is not supported
2
Page 295

Ports 1-2 (GBE ports) and ports 3-7 (FE only ports) cannot be in the same LAG
group even if the GBE ports are configured as 100Mbps.
GbE
FE
GbE
FE
IP-10 IDU
IP-10 IDU
Grouping ports in LAG (continued)

Radio port (port 8) may be in a LAG with the GBE ports only
GbE
FE
GbE
FE
IP-10 IDU
8
IP-10 IDU
3
Page 296
Configuring LAG
The following settings must be identical on all LAG ports
(Port(s) with different settings will not be added to the LAG)
QoS configuration (Classification Criteria, Port ReMap table, Egress Scheduler)

Speed (data rate)
Type (access/trunk or CN/PN)
interface (electrical/optical)
Full Duplex
Auto-Negotiation
VLANs
VLAN list must be identical
all is considered a different value (must be equal in all ports)
allow
allow all
Port Learning State
Please note - ports with CFM MEP/MIPs will not be added to a LAG (which may
have its own MEP/MIPs).
Configuring LAG (continued)

The following parameters CANNOT be configured on ports that are already
grouped in a LAG:
Admin status
Flow control
Ingress rate limiting Policer name
Shaper (egress rate limiting)
Peer port parameters
MAC address
IP address
Slot ID
Port number
Description
4
Page 297
Removing a Port from LAG

Ports removed from a LAG will keep the existing port parameters, but will
be initially disabled in order to prevent loops.
In addition, when the last port is removed from a LAG, the LAG will be
deleted.
Therefore it is necessary to remove all MEP/MIPs from a LAG before

removing the last port.
EMSConfiguration
g
5
Page 298
Setting Load Balance Policy

Open page:
Configuration
g
/ Ethernet Switch
Select Simple XOR or HASH
Create VLAN(s) per service(s) in
the switch DB (if such VID do not
exist yet)
11
Selecting ports to LAG

Open page: Configuration / Interfaces / Ethernet Ports
Click on LAG Configuration and select the LAG ports and group ID
Available ports highlight in blue when selected

Non-available ports (part of an existing LAG) are not configurable
12
6
Page 299
Example
1.
2.
3.
4
4.
5.
6.
We generate a data stream through GbE SFP port 1 of both lower IDUs
Port 2 & 8 form a LAG on both sites
Upper IDUs are set as Pipe
Traffic will be evenly distributed among the radio ports
Assign Radio license > Line rate
Clear all PM data
Data stream
Data stream
Using RMON (PM) to analyze LAG

Make note of received &
transmitted traffic through port 1
Please note:
Slight differences may appear
since EMS is a web based
application and data is
accumulating
Data stream
7
Page 300

Check the received & sent
registers of port 1 and LAG
ports:
Data received on Port 1 is
equally distributed through
Port 2 and Port 8
+
=

Disconnect the ETH cable
connecting lower IDU to
upper IDU (port 2)
port 2 does not
LAG p
transmit data now
Port 8 takes 100% of data
transmission
8
Page 301
ThankYou!
17
9
Page 302
6/14/2010
FibeAir IP10
1+1 Protection
Agenda
IntroductiontoExternalProtection
Introduction to Shelf Protection
IntroductiontoShelfProtection
Guidelines
ExternalProtectionProcess:1+1fromscratch
ExternalProtectionProcess:Upgrading1+0to1+1
Troubleshooting
Page 303
6/14/2010
External Protection
Achieved by using two standalone IDUs
The IDUs must be connected by an Ethernet Cross cable (via the protection
ports)
Each IDU has its unique IP address
address.
Protection Panel may be in use (shown in orange, supports TDM only)
1st IDU is Active (TX & RX), 2nd IDU is STBY (awaits a switchover command)
f1 - high
In this example 1+1

Protection is only deployed
at one site
IDU
f1 - high
f1 - low
Shelf Protection
When enabling a Shelf Protection, the following rules should be
applied:
Shelf backplane replaces the external Protection Cable
There
Th
iis only
l one IP address
dd
ffor each
h off th
the pair
i units
it
Protection can enabled in each pair (1+2, 3+4, 5+6)
Each IDU must have a unique IP address
1st IDU is Active (TX & RX), 2nd IDU is STBY (system awaits a switchover
command)
6
In this example Protection

is configured in every pair
of IDUs (slots)
5
4
3
2
1
IDU
IDU
IDU
Page 304
6/14/2010
Guidelines
A Standby IDU is referred to as the Mate
When a switchover occurs, the Active IDU becomes Standby and the
Standby
Standby IDU becomes Active
Active
Accessing a Mate IDU can only be done via the Active IDU
Accessing the new "Active" will be done using its IP address
Y-Split cables must be used for Ethernet signals (fiber optics)
Setup Example (Standalone IDUs)
Page 305
6/14/2010
Configuring external 1+1 from scratch
Configuring external 1+1 from scratch (1)

1. Set all IDUs to factory defaults
2 When
2.
Wh IDU
IDUs complete
l t th
the b
booting
ti sequence, verify:
if
All IDUs have the same HW version

All IDUs have the same SW version
Every IDU has unique IP address
Active and STBY have the same SW mode
All IDUs have the same Management mode (In band or OOB)
In case of In-Band, all IDUs have the same In-Band VID
Note:
The IDU, which is connected to the ODU fed by the
lower attenuation channel of the RF coupler, is the
IDU that should be selected as "Active.
8
Page 306
6/14/2010

3. Install the 1st link (make sure radio is up)
ODU
ODU
4. Enable Protection on both IDUs (management will be lost for 60 sec)

5. Lock Protection on both IDUs (to avoid unnecessary switchover when 2nd IDU
is enabled)
6 Install
6.
I t ll 2ndd IDU iin each
h site
it (no need to configure it)
ODU
ODU
ODU
ODU

7. Enable protection in 2nd IDU in each site
8. Connect ETH Cross Cable between both protection ports
ODU
ODU
ODU
ODU
9. Disconnect the MNG cables.

10. Connect the PC to IDUs via ETH Y-Cable:
ODU
ODU
ODU
ODU
PC
10
Page 307
6/14/2010

11. Verify Active IDU shows Mates IP address
12. Verify there are no Configuration Mismatch alarms
13. Verify there are no Mate Communication failures
14. Complete system setup by configuring Active IDU
15. In Active IDU: click Copy to Mate and verify Mate is restarting
16. Repeat steps 10 to13
17. Unlock protection on Active IDUs
18. Initiate Manual Switchover / Forced Switchover: verify traffic is OK.
11
Upgrading (1+0) to (1+1)
Page 308
6/14/2010

1. Assuming 1st link operates well, configure the 2nd IDUs to match
Active IDUs:
2nd IDUs has the same HW version as Active IDU

2nd IDU has the same SW version as Active IDU
2nd IDU has unique IP address (different than Actives IP)
2nd IDU has the same switch mode as Active IDU
2nd IDU has the same Management mode (In band or OOB)
In case of In-Band, 2nd IDU has the same In-Band VID as Active IDU
2nd IDU is configured with the same radio parameters as Active IDU
Mute transmission on 2nd IDUs
Active Link:
ODU
ODU
ODU
ODU
Standby Link (not connected)
13

2. Enable Protection on Active IDUs (management will be lost for 60 sec)
3 Lock
3.
L kP
Protection
t ti on b
both
th A
Active
ti IDU
IDUs (to avoid unnecessary switchover
when 2nd IDU is enabled)
4. Install 2nd IDU in each site (verify TX is muted before physical installation)
14
ODU
ODU
ODU
ODU
Page 309
6/14/2010

5. Enable protection in 2nd IDU in each site
6. Connect ETH Cross Cable between both protection ports
ODU
ODU
ODU
ODU
7. Disconnect the MNG cables.

8. Connect the PC to IDUs via ETH Y-Cable
9. Cancel TX mute on both Mate IDUs
15

10. Verify Active IDU shows Mates IP address
11. Verify there are no Configuration Mismatch alarms
12. Verify there are no Mate Communication failures
13. Complete system setup by configuring Active IDU
14. In Active IDU: click Copy to Mate and verify Mate is restarting
15. Repeat steps 10 to13
16. Unlock protection on Active IDUs
17. Initiate Manual Switchover / Forced Switchover: verify traffic is OK.
16
Page 310
6/14/2010
Troubleshooting Protection
Common issues followed by CLI commands
Troubleshooting
Alarm/Error
ProbableCause/Workaround
Protection LEDison(RED)
LED is on (RED)
1. Protection cableisnotconnected
2. ETHstraightcableisconnectedinsteadof
crosscable
cross
cable
3. Oneofthe2IDUsisnotconfiguredin
Protection
CheckCFGofbothIDUs:HW,SW,switchmode,
CurrentAlarmsshow Configuration
managementmode,InBandVID
Mismatchalarm
InitiateCopytoMateinActiveIDUs
IcannotPINGtheSTBYunit.
Thisisnormalbehavior, Matecannotbe
accesseddirectly,onlyviaActiveIDU
MainIDU doesnotrespondto
PING
UseCLIcommandstoverifythisIDUisinSTBY
mode,ifso,useCLItorecoverIDU
CheckthecurrentalarmsofSTBYIDU
CurrentAlarmsshows MateComm. ReportbacktoCeragonSupport
Failurealarm
ReplaceSTBYunit
ReplaceActiveunit
18
Page 311
6/14/2010
Troubleshooting Useful CLI Commands

General commands:
lsp
ls
cls
prints executable commands in current directory

prints available child
child-directories
directories
clears screen
To execute Protection commands, you will need to change directory:

IP-10:/> cd platform/mate-idu
Then to read current status of IDU
Then,
IDU, type the following (in blue):
IP-10:/platform/mate-idu> get protection-mode
The system return these values:
1. Active
2. Standby
19

To change Protection Admin mode, type the following:
IP-10:/platform/mate-idu> set protection-admin
<enable/disable>
To lock the current protection mode, type the following:

IP-10:/platform/mate-idu> set protection-lockout
20
<on/off>
Page 312
10
6/14/2010

To force a switchover, type the following:
IP-10:/platform/mate-idu> set protection-force-switch <on/off>
To request a manual switchover, type the following:

IP-10:/platform/mate-idu> manual-switch-cmd
To initiate a Copy-to-Mate process, type the following:

IP-10:/platform/mate-idu> copy-to-mate-cmd
21
ThankYou!
training@ceragon
com
22
Page 313
11
CFM (OAM IEEE 802.1ag)

Connectivity Fault Management
Module Version V2.0
Perquisites
Prior to this configuration, end-user need to

be familiar with the following modules:
Ethernet Frame Structure

802.1p/q
CFM Theory
Switch Configuration
Interfaces Configuration
Page 314
Agenda
CFM: Why?
Preliminary configuration
Setup Review
Configuration Flow
Configuration Review
Manual PING
Manual Linktrace
Automatic Linktrace
CFM: WHY ?
By definition, L3 IP or L2 ETH are Connection-less networks
In connection-less networks we are blind unable to determine packet path

or latency
This makes troubleshooting and maintenance a harder task
Solution: we need to convert our Connection-less network into a

Connection-Oriented network
IN
IN
Connection-Less
4
Connection-Oriented
Page 315
CFM: WHY ?
Connection-Oriented networks (ATM, IP/MPLS) enable administrators setting a

pre-defined packet path, reserving BW per service, faster event detection and
thus effective troubleshooting & maintenance
Such technologies are too expensive and sometimes not feasible for Mobile
Operators / Mobile Backhaul solutions
Solution: use a cheaper technology with enhanced features:
Ethernet Core + Operations, Administration & Maintenance support (CFM)
CFM enables L3 operations

such as Traceroute and
PING with a simpler ETH
infrastructure
Connection-Oriented
5
Preliminary Configuration
1. Make sure you define the required VLAN IDs in the Switch DB prior to OAM
configuration
2. Prepare a Network Design Map with required configuration
(MIP / MEP / IDs / MAC per device.)
4. Make sure IP-10 Interfaces are configured according to your Network Criteria
(Trunk / Port VID Membership ).
5. Every CFM interface (including Radio) must be aware of the required VIDs
(Port membership)
6. CFM requires physical connection, therefore make sure your interfaces are
enabled on both sides (DCE and DTE)
Page 316
Setup Review (MAIDs):
Domain 1 Services:
D1S1:
MEP 1 to MEP 2, Level 3, VLAN 1000
1
D1S2:
4
2
Domain 2 Services:
D2S2:

MEP
MIP
7
CFM Configuration Flow:

1
Create VLANs in Switch DB

Assign VID membership per port
Create Domains and Services
Assign MIPs
You may use Advanced features to

troubleshoot a L2 problem
All Steps must be configured on both IP-10s

Make sure you follow the same syntax
Page 317
Configuration
Switch Configuration Mode and VIDs
10
Page 318
Switch Configuration Port Configuration
11
Creating MAIDs
Click on the Add button to add domains
(use the setup diagram as a reference)
You will need to specify:
1.
2.
3.
4.
12
Domain Name
Level (1 to 7)
Association Name
VLAN ID
Page 319
Creating MAIDs
Create the domains as depicted in the setup diagram on both IDUs
Settings must be unique and identical
13
Domains defined
You should see the following status on your MAID list page (on both IDUs):
If you point your cursor to the No MEPs indication LED, you will be notified that MEPs
need to created as well
14
Page 320
Defining MEPs
Click on the ADD button to add a local MEP on both IDUs
Continue to next slide to observe how
15
Defining MEPs
Port #3
MEP ID: 1
Port #3
MEP ID: 2
16
Page 321
RIGHT IP-10
Remote MEPs not defined yet
17
RIGHT IP-10
LEFT IP-10
Enable CCM on both IDUs
18
Page 322
CCM enabled > Remote MEP is detected
As you can see, CCM enables auto-learning, hence both MEPs discover each other
(MAC and remote MEP ID are now known)
New alarms indicate that process of creating the remote MEP is not fully complete
19
Creating Remote MEPs
Click on the Add button to add a remote MEP on every IDU
20
10
Page 323
Creating Remote MEPs

Port #3
Local MEP ID: 1
Remote MEP: 2
Port #3
Local MEP ID: 2
Remote MEP: 1
21
Service #1 (D1S1) is ready for monitoring!
Click on the PING button to check connectivity to Remote interface

(results on next slide)
22
11
Page 324
PING results (MEP1 to MEP2)
23
D1S2 Creating another service

We shall create a new service (S2) using the same Domain (D1) (hence- same level)
To separate the 2 services, we shall assign a new VLAN
MEP1
MEP 3
MEP 4
MEP 2
New Domain: D1S2

MEP 3 to MEP 4
Level 3
VLAN 2000
The new service D1S2 will

monitor the Radio ports
24
12
Page 325
D1S2 Creating another service

Using the MAID list, add the new service on both IDUs:
MEP 3
MEP 4
25
D1S2 Creating Local MEPs

Please note - Radio port MEP should be defined as a Downstream MEP
MEP 3
MEP 4
26
13
Page 326
D1S2 Enable CCM on both IDUs
MEP 3
MEP 4
27
D1S2 Add Remote MEPs on both IDUs
MEP 3
MEP 4
28
14
Page 327
D1S2 Service is now ready for monitoring
29
D2S2 another service on another Domain
D2S2
5
6
30
15
Page 328
D2S2 another service on another Domain
31
Adding Local MEPs
Local MEP 5
Remote MEP 6
Local MEP 6
Remote MEP 5
32
16
Page 329
Enabling CCMsAdding Remote MEPs

Once you complete these tasks, your 3rd service is ready for monitoring
33
Adding MIPs to enhance Monitoring

The MIPs can be regarded as
Service-free test-points
MIPs provide more segments
regardless of VLANs and
Services
More test-point
More L2 capabilities!
We shall add a MIP point on

every Radio interface
Make sure you set the MIP

level according to the level
of the Parent domain
34
17
Page 330

In the MEP & MIP list, we can see the switch ports and there
MACs:
In our example, we need to add a MIP on the Radio port
Therefore, we shall expand the Radio port to configure the
MIP
Add MIPs on both radio ports (both IDUs)
35
Please make a note of the Radio MAC address of each IDU we shall need it later
36
18
Page 331
MAC addresses of participating interfaces

00:0A:25:01:8F:AD
00:0A:25:56:27:AC
00:0A:25:56:27:C6
00:0A:25:56:27:C2
Please note the above MACs are an example of given setup

37
Manual PING | Manual Link Trace | Automatic Link Trace
19
Page 332
Manual PING
To PING from MEP 1 to MEP 2, you will need to set the following parameters:
Remote interface MAC
Level
VLAN
Successful PING requires setting the correct path
39
Manual Linktrace
To trace an interface , you will need to set the following parameters:
Remote interface MAC
Level
VLAN
Successful Trace requires setting the correct path
Results on next slide
40
20
Page 333
Manual Linktrace Results

FDB
MIP informing us that it
received the LTM (link race
message), it is not who we
are looking for but it knows
how to reach the target
interface
We have traced 2 MIPs (on

every Radio port)
Eventually we traced MEP 1

(HIT)
41
Automatic Linktrace
To enable Auto Linktrace select the checkbox next to the target Remote MEP
and then click ADD SELECTED
42
21
Page 334
Automatic Linktrace
Click Linktrace SELECTED
43
Thank You !
training.ceragon.com
44
22
Page 335
3/7/2010

Loopback Maintenance
Agenda
In this module we shall describe

the various actions we can
perform to properly maintain and
troubleshoot the IP-10G system
Page 336
3/7/2010
RFU RF Loopback
RFU RF LB
RFU RF Loopback
Use it to verify communication from Line to ODU is OK (including ODU)
Traffic affecting TX is stopped
Configurable Timer to automatically restore traffic ( 0 = no time limits)
RFU LED is RED when Loopback is ON
LINK LED is GREEN when Loopback is ON
Alarm is displayed in Current Alarms:
and Event log:
Page 337
3/7/2010
IF Loopback
IDU IF LB
IF Loopback
Use it to verify communication from Line to IF cable is OK
Traffic affecting TX is stopped
Configurable Timer to automatically restore traffic (0 = no time limits)
LINK LED is GREEN when Loopback is ON
Alarm is displayed in Current Alarms:
and Event log (next slide):
Page 338
3/7/2010
IF Loopback Analysis using Event Log

Lets assume radio link is down LINK LED is RED
16:29:01
We enable IF LB, therefore Link alarms clear
16:29:05
Loopback replaces remote unit therefore alarm disappears
16:30:01
Loopback automatically stops, link recovers to original state
16:30:05
Radio link is down (original state)
PDH Line LB towards Line (NE)
LB towards the line
Page 339
3/7/2010
PDH Line LB towards Line (Near End)

Use this feature to evaluate connection to customers patch-panel
Alarm is displayed in CAS:
and in Event Log:
PDH Line LB towards Radio (FE)
LB towards the radio
Tester
10
Page 340
3/7/2010
PDH Line LB towards Radio Event Log Analysis

Lets assume PDH port #1 is enable but not connected
Therefore, Major alarm is on (RED)
16:59:44
We enable Line LB towards the radio
16:59:46
Loopback replaces end-device therefore alarm disappears
17:06:37
Loopback is OFF
17:06:38
PDH port alarm is ON again..
11
SDH Line LB towards System

Towards System signal (trail) is looped back to
IP-10
12
Page 341
3/7/2010
SDH Line LB towards Line

Towards Line signal (trail) is looped back to
customer interface
13
IDU-RFU Interface Monitoring
Before you leave the site, make sure that these registers are elapsed (zero)\
When one of these registers is different than 0 you need to report to
your support representative
In such case, perform the Loopbacks we have just covered to narrow down the
probable causes for the errors
14
Page 342
3/7/2010
Thank You !
15
Page 343
3/7/2010

EMS Backup Maintenance
Agenda
In this module we shall describe the various

actions we can perform to properly maintain
and troubleshoot the IP-10G system using:
1.
2.
3.
2
Configuration File
Unit Information File
FTP Server
Page 344
3/7/2010
Configuration File
The Configuration file stores the following parameters:
License
External Alarms
SNMP Trap Destination
NTP Server Properties
Radio properties: Frequency, RSL, TSL, ATPC, etc.
Switch Mode and database: Port types, VLAN membership, etc.
Interface Configuration: PDH, TDM, Ethernet Switch
Trail Configurations
Service OAM
Security: user accounts, login properties, etc.
Unit Information File

The Unit Information file stores the following parameters:
Date & Time

Daylight Saving Time properties
System name and other ID parameters
Measuring properties (voltage, temperature)
Accumulated Performance Monitoring logs
Serial numbers
Page 345
3/7/2010
Local FTP Server

Uploading or Downloading the CFG & Unit files requires an FTP Server
As long as your IP-10G communicates with the server, its location is
irrelevant
EMS PC with local FTP Server installed
Remote FTP Server

You may assign a remote server to host the configuration and unit files
EMS PC
Remote FTP Server
Page 346
3/7/2010
FTP Root Directory

Every Server has its own properties. Make sure you are familiar with
your FTP Root Directory: this is where the files are stored (software
versions, CFG & Unit).
Examples for
SW packages
Examples for
CFG & Unit
Files
7
Configure your FTP Server Properties
2
8
Page 347
3/7/2010
Upload /
Download using
standalone IP-10G
9
Uploading the CFG File (IP-10G to Server)

Click Create Archive to
allow the IP-10G zipping
all parameters into one file
10
Page 348
3/7/2010
Wait till task is

successfully completed
11

Next step:
Click Upload Archive to allow
the IP-10G transferring the
zipped file to your server
12
Page 349
3/7/2010

Wait till task is successfully
completed
13
Check your FTP Root Directory
This is your copy of

the configuration file
You may place it now
in the dedicated folder
(Configuration Files)
14
Page 350
3/7/2010

Follow the same steps to upload the Unit Information file:
1
15
2
Check your FTP Root Directory
This is a copy of your Unit Information file
16
Page 351
3/7/2010
Downloading the CFG File (Server IP-10G)

Follow the same steps to download the CFG file
When download completes successfully, you will need to restart the
system for changes to take place
Please note if the file does not exist in the root directory action will fail !
1
17
2
Upload /
Download in
a shelf
18
Page 352
3/7/2010
Shelf Backup: Creating the Nodal Shelf Backup

Uploading CFG files from a shelf is similar to a standalone
process
1. First you need to create the CFG files of all slots
2. After creating the CFG files, you need to upload them to your
FTP directory
19
Shelf Backup: Creating the Nodal Shelf Backup
First you need to create the

CFG files.
To do so, select the unit(s)
and click the relevant
Backup button
20
Page 353
10
3/7/2010
Shelf Backup: Upload from IP-10G to Server

Next, click Upload
Archive(s) and the
file(s) will be uploaded
to your FTP root
directory
21
Shelf Backup: Download from Server to IP-10G
To download a file to a
certain slot, select the
unit number and click
this button
22
Page 354
11
3/7/2010
Unified Unit Information File
A unified file is created for

all stacked units
Upload & Download
action are identical to a
standalone unit
23
Checking Backup History & Status
Click here to see the

backup history
24
Page 355
12
3/7/2010
Checking Backup History & Status
25
Setting the unit back to Factory Defaults
You can restore your system to

factory defaults
You may also set the IP address to
factory default address (192.168.1.1)
26
Page 356
13
3/7/2010
Thank You !
27
Page 357
14
4/21/2010

EMS Software Upgrade
Agenda
FTP Properties
Standalone SW Download
Standalone SW Upgrade
Nodal IDU SW Download
Nodal IDU SW Upgrade
Rollback VS. Downgrade
Page 358
4/21/2010
Local FTP Server

SW files are located on an FTP Server (local or remote)
Configure the FTP properties to point to your local server root directory
(Make sure RD/WR permissions are enabled)
EMS PC with local FTP Server installed
Remote FTP Server

If you do not have an FTP Server installed locally on your PC, you may
configure an IP address of a remote server.
EMS PC
Remote FTP Server

Page 359
4/21/2010
FTP Root Directory

Make sure you are familiar with your FTP Root Directory: this is where
the files are stored (software versions, CFG & Unit).
Examples for
SW packages
Configuring FTP Server Properties
Page 360
4/21/2010
Configuring FTP Server Properties
Type the location of the software package:

FTP IP address
SW folder (when relevant, in this example 66253)
Type the username & Password
(You may log in using CMD window to verify settings are correct)
SW Upgrade on a
standalone IP-10G
Page 361
4/21/2010
Click on the Download button and wait till Succeeded message is
displayed (next slide)
You may view at any time the download

process by clicking on the Log Icon
Download was successfully completed, you may proceed to upgrade
the IDU
10
Page 362
4/21/2010
Download completed Upgrade delayed

In case Upgrade is scheduled for later moments, the Version table will
display the following status:
11
Standalone Upgrade
Click on the Upgrade button. When upgrades completes successfully,
the IDU will restart automatically.
You may view at any time the upgrade

12
Page 363
4/21/2010
SW Upgrade in a
shelf (Node)
13
Shelf Configuration
1. Make sure your main unit (Slot 1) is upgraded with the latest version
2. If not, it is recommended to upgrade the main unit as a standalone IDU
3. Verify you are familiar with the slot number(s)
Slot 6
Slot 5
Slot 4
Slot 3
Slot 2
Slot 1
14
Page 364
4/21/2010
Shelf SW Download
Configure the FTP properties if needed

Click on the Download button and
wait till Succeeded message is
displayed
You may view at any time the download
15
Shelf SW Upgrade
Select the target slot and then click the
Upgrade button
Or click Upgrade All
Please note
1. The number of slots depend on
actual configuration
2. The slot numbers are not according
to physical allocation in the shelf
3. Failures may occur due to wrong
FTP configurations, unstable
network connection or missing files
4. IDU(s) will reset automatically upon
successful upgrade
16
Page 365
4/21/2010
Shelf SW Upgrade
Select the target slot and then click the
Upgrade button
Or click Upgrade All
Please note
1. The number of slots depend on
actual configuration
2. The slot numbers are not according
to physical allocation in the shelf
3. Failures may occur due to wrong
FTP configurations, unstable
network connection or missing files
4. IDU(s) will reset automatically upon
successful upgrade
17
Rollback
VS. Downgrade
18
Page 366
4/21/2010
Rollback
2.8.25
Upgrade #1
Upgrade #2
2.8.31
2.8.35
2.8.32
Rollback
3
Downgrade
Rollback does not revert previous Downgrade operation !

It rolls back IDU version 1 step back (prior to last Upgrade)
19
Thank You !
20
Page 367
10
3/7/2010

EMS Security Configuration
Agenda
SSH
HTTPS
SFTP
Users & Groups
Password
Page 368
3/7/2010
Security Configuration
Update first FTP connection
SSH Secured Shell

SHHv1 and SSHv2 are supported.
SSH protocol can be used as a secured alternative to "Telnet".
SSH protocol is always be operational. Admin user can choose whether to
disable
"Telnet" protocol, which will be "enabled" by default. Server authentication

will be based on IP-10s "public key".
Key exchange algorithm is RSA.

Supported Encryptions: aes128-cbc, 3des-cbc, blowfish-cbc, cast128-cbc,
arcfour128, arcfour256, arcfour, aes192-cbc, aes256-cbc, aes128-ctr,

aes192-ctr, aes256-ctr.
MAC (Message Authentication Code): SHA-1-96 (MAC length = 96 bits, key
length = 160 bit). Supported MAC: hmac-md5, hmac-sha1, hmacripemd160, hmac-sha1-96, hmacmd5-96'
The server will authenticate the user based on user name and
password. Number of failed authentication attempts is not limited.
Server timeout for authentication: 10 min. This value cannot be configured.
Page 369
3/7/2010
HTTPS
In order to manage the system using HTTPS protocol, user should
follow the following steps:
1. Create the IDU certificate based on IDU's public key.

2. Download the IDU certificate.
3. Using CA certificate (Optional steps)
i. Download the IDU CA's certificate.
ii. Enable WEB CA certificate.
4. Set WEB Protocol parameter to HTTPS
HTTPS Public Key Upload

The public key should be uploaded by the user for generating the IDUs
digital certificate:
The upload will be done by using FTP/SFTP (s

The public key file will be in PEM format.
Click Upload Public Key
The status of the upload operation can be monitored. The returned status
values are: ready (default), in-progress, success, failed. In any case
of failure, an appropriate error message will appear.
Page 370
3/7/2010
HTTPS Certificate Download (1)

Download IDU server certificate and/or IDU CA certificate (optional) :
Download is done by using FTP/SFTP.

PEM and DER certificate formats are supported.
For downloading the IDU server certificate and/or IDU's CA certificate to the system, the
following steps must be fulfilled for each file type:
Determine certificate file name (Admin privilege).

Determine the certificate file type (Admin privilege): Target Certificate (for WEB
server digital certificate) or Target CA certificate (for WEB CA digital certificate).
Determine certificate file format (Admin privilege): Format could be PEM (for PEM
formatted file), or DER (for DER formatted file).
Determine whether to include the

CA certificate into the WEB configuration
definitions. This is an optional configuration
and is recommended for adapting the
WEB interface to all the WEB browsers
applications (Admin privilege).
HTTPS Certificate Download (2)

After setting the above configurations, a Download Certificate command
should be issued.
The status of the download operation can be monitored. The returned status
values are: ready, in-progress, success, failed.
It is recommended to refresh the WEB page when certificate download

operation is terminated.
To apply the new certificate, the WEB server should be restarted (Admin
privilege). WEB server will be automatically restarted when it is configured to
HTTPS.
Page 371
3/7/2010
HTTPS - Activation
WEB interface protocol can be configured to be HTTP (default) or HTTPS
(cannot be both at the same time).
While switching to HTTPS mode, the following must be fulfilled:
WEB server certificate file exist.
Certificate public key is compatible to IDUs private key.
If one of the above tests fails, the operation will return an appropriate error
indication.
Open WEB Browser and type the URL https:\\<IP of target IDU>.
Note:
This parameter is NOT copied when copy to mate operation is initiated,
for security reasons (unsecured unit should not be able to override security
parameters of secured unit).
SFTP (Secure FTP)
SFTP can be used for the following operations:
Configuration upload/download,
Upload the unit info.
Upload public key.
Download certificate files.
SW download
Page 372
3/7/2010
USERS,
GROUPS
&
PASSWORD
Adding Users
To add / edit users & groups click on the

item as shown in the captured imaged (left)
Click Add User to add new users
Page 373
3/7/2010
Adding Users
Adding Users
New users will be required to change their

password when they log in for the first time
Page 374
3/7/2010
Changing Password
A valid password should be a mix of upper and lower case letters, digits, and other
characters.
You can use an 8 character long password with characters from at least 3 of these 4
classes. An upper case letter that begins the password and a digit that ends it do not
count towards the number of character classes used.
Changing Password
Good example:
L00pBack using capital letters, small letters and digits (zeros instead of O)
Bad example:
Loopback missing digits or other characters
Loopbacks using more than 8 characters
Page 375
3/7/2010
Thank You !
17
Page 376
6/13/2010
FibeAir Outdoor Enclosure

Same Advanced Features in a Compact,
Zero Footprint Casing
FibeAir Outdoor Enclosure Key Features
Full wireless solution at zero footprint

Outdoor Enclosure for IDUs
5RU/19 rack space outdoor enclosure

4RU for Traffic IDUs, 1RU for Panels and cables
Support for the same FibeAir product line used for indoor deployment
IP-10/IP-10G Series
1500R
Installation anywhere
Passive heat exchange - no need for air conditioning systems

External battery backup solution with enclosure (Optional)
Heating unit for frigid environments
Roof top, wall, or pole
CERAGONNETWORKSLTD.
Proprietary and Confidential information of Ceragon Networks Ltd
Page 377
6/13/2010
Outdoor Enclosure Reduced OPEX & CAPEX
Compact size and modular
Zero footprint - saves ground space at central offices / communication rooms

All outdoor nodal or ring configurations
Pole-mount, wall or roof-top installation
Sit lease
Site
l
or acquisition
i iti savings
i
Lower overall costs
Installation - Instant wireless site set-up. One man installation

Rent - Versatile installation options saves site lease costs
Power - Saves power, space and air conditioning
Easier maintenance
IP-55 certification for water and dust proofing
Elegant, Easier to Install & Maintain Solution

CERAGONNETWORKSLTD.
Outdoor Enclosure Units configurations

All configurations, interfaces, and customer needs
IP-10 & 1500R with full networking functionality
General configurations
1+0 & 1+1 HSB,
HSB 2+0,
2+0 4+0
4+0
TDM XC / grooming
Packet switch solution
All interfaces
N*E1/T1
N*Ethernet interfaces (FE, GbE)
STM-1
CERAGONNETWORKSLTD.
Page 378
6/13/2010
Outdoor Enclosure Practical experience
External alarm inputs for external fans and door opening

Sunshade for solar radiation protection
Door stopper
I t ll ti hooks
Installation
h k
Documentation pocket
Door Lock
Pole mount option or wall mount option
Light weight
Battery Backup option
CERAGONNETWORKSLTD.
Environmental Recommendation support

Environmental Standards Compliance
GR-487-CORE
ETSI EN 300 019-1-4, Class 4.1 (Non-weather protected locations)
IEC 529 IP- 55 pprotected cabinet ((dust & water))
Operating Air Temperature -40 to +55degC
Safety and Electromagnetic Standards (EMC) Compliance

UL60950-1 (Safety)
FCC 47 CFR, part 15, class B (EMC)
GR-1089-CORE (Safety & EMC part of NEBS)
CSA CS22.2 60950-1 (Safety)
ETSI EN 301 489-1
ETSI EN 301 489
489-4
4 (EMC)
CB IEC 60950-1 (Safety)
CERAGONNETWORKSLTD.
Page 379
6/13/2010
IPprotectionclasses
IP 55 What does that mean ?
First Characteristics Numeral IP XY - Foreign Bodies Protection, Solids
Index
Protection against
Human/Tool Contact
Protection against solid objects (foreign bodies)
No special protection
Back of hand, Fist
Large foreign bodies, diam. >50mm
Finger
Medium-sized foreign bodies, diam. >12
Tools and wires etc with a

thickness >2.5mm
Small foreign bodies, diam. >2.5mm
Tools and wires etc with a

thickness >1mm
Granular foreign
g bodies,, diam. >1mm
Complete protection,
Dust protected; dust deposits are permitted, but their
(limited ingress permitted) volume must not affect the function of the unit.
Complete protection
Dust-proof
7
CERAGONNETWORKSLTD.
IPprotectionclasses
IP 55 What does that mean ?
Second Characteristics Numeral IP XY - Water Protection, Liquids
Index
Protection from
condition
Protection against water
N special
No
i l protection
t ti
Water dripping/falling vertically
Condensation/Light rain
Water sprayed at an angle (up to 15 degrees from the vertical)
Light rain with wind
Spray water (any direction up to 60 degrees from the vertical)
Heavy rainstorm
Spray water from all directions, (limited ingress permitted)
Splashing
Low pressure water jets from all directions, (limited ingress

permitted)
Hose down, residential
High pressure jets from all directions, (limited ingress permitted)
Hose d
H
down,
commercial.
eg. Ship decks
Temporary immersion, 15 cm to 1m
Immersion in tank
Permanent Immersion, under pressure
For use on Titanic

recovery vehicle
7
8
8
CERAGONNETWORKSLTD.
Page 380
6/13/2010
Outdoor Enclosure Design - external

W
General Dimensions
H: 18.5 in / 47 cm
W: 24 in / 61 cm
D: 17 in / 43 cm
Weight
55 Pounds / 25Kg
CERAGONNETWORKSLTD.
Accessories list
Marketing Model
Marketing Description
OE-Enclosure
FA Outdoor Enclosure
OE-Pole-Installation
FA Outdoor Enclosure Pole installation
OE H t
OE-Heater
FA Outdoor
O td
Enclosure
E l
heater
h t
OE-Ext-Fans
FA Outdoor Enclosure external fans
OE-Fan-Drawer-Kit
Outdoor Enclosure Fan Drawer Kit
OE-Ext-Power-CBL-15M
Outdoor environment power cable (-48V). Ferrule-Ferrule 15m
ODE-NTYPE-JUMPER-CBL-3M
Outdoor Enclosure IF Jumper Cable 3m
OE-Ext-Alarms-CBL-0.45M
Outdoor Enclosure External alarms cable, D-9M - D-9F, 0.45M
IP10-OE-CBL-ETH-RJ45-15m
IP-10 ETH Outdoor RJ45 cable 15m, straight
CBL-OE-E1-RJ45-RJ45-15m
IP-10 E1 Outdoor RJ45 cable 15m, straight
CBL-OE-T1-RJ45-RJ45-15m
IP-10 T1 Outdoor RJ45 cable 15m, straight
IP10-OE-CBL-ETH-RJ45-XED-15m
IP-10 ETH Outdoor RJ45 cable 15m, Cross
CBL-OE-E1-RJ45-RJ45- XED-15m
IP-10 E1 Outdoor RJ45 cable 15m, Cross
CBL-OE-T1-RJ45-RJ45- XED-15m
IP-10 T1 Outdoor RJ45 cable 15m, Cross
OE-Sealing-Compound-1.5M
Outdoor Enclosure sealing compound
(*) all IP-10 standard accessories can be used. Enclosure space should be taken into consideration
CERAGONNETWORKSLTD.
Page 381
6/13/2010
Thank You
Page 382
FibeAir IP-10
License
Management
Guide
Part ID: BM-0139-0

Doc ID: DOC-00019183 Rev a.00
November 2008
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 is a registered trademark of Ceragon Networks Ltd.
FibeAir is a registered trademark of Ceragon Networks Ltd.
CeraView is a registered trademark of Ceragon Networks Ltd.
Other names mentioned in this publication are owned by their respective holders.
TradeMarks
CeraMapTM, PolyViewTM, EncryptAirTM, ConfigAirTM, CeraMonTM, EtherAirTM, and MicroWave
FiberTM, 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 users authority to operate the equipment and the warranty for such equipment.
Copyright 2008 by Ceragon Networks Ltd. All rights reserved.
Corporate Headquarters:
Ceragon Networks Ltd.
24 Raoul Wallenberg St.
Tel Aviv 69719, Israel
Tel: 972-3-645-5733
Fax: 972-3-645-5499
Email: info@ceragon.com
North American Headquarters:
Ceragon Networks Inc.
10 Forest Avenue,
Paramus, NJ 07652, USA
Tel: 1-201-845-6955
Toll Free: 1-877-FIBEAIR
Fax: 1-201-845-5665
Email: infous@ceragon.com
www.ceragon.com
European Headquarters:
Ceragon Networks (UK) Ltd.
4 Oak Tree Park, Burnt Meadow Road
North Moons Moat, Redditch,
Worcestershire B98 9NZ, UK
Tel: 44-(0)-1527-591900
Fax: 44-(0)-1527-591903
Email: infoeuro@ceragon.com
APAC Headquarters
Ceragon Networks (HK) Ltd.
Singapore RO
Level 34 Centennial Tower
3 Temasek Avenue
Singapore 039190
Tel - + 65 6549 7886
Fax: +65 6549 7011
Contents
General .......................................................................................................... 1
Getting Started .............................................................................................. 1
How to use the System................................................................................. 5
Managing the License .................................................................................. 6
Working with Devices .......................................................................................... 6
Working with Licenses....................................................................................... 16
Settings ............................................................................................................... 23
Generating Reports ............................................................................................ 25
General
This guide explains how to work with the FibeAir IP-10 web based License Management System.
The system enables authorised users to obtain license-related information and perform license-related
operations.
Getting Started
To start the management application:
1.
In your web browser, go to the address http://80.74.99.83/LMManage/login.aspx
2.
To log in to the system, enter your user name and password, and then click Login.
Note the following user name rules:
FibeAir IP-10 License Management System
For Demo OEM, the first five digits must be 00001. The next four digits after the first five should
be numbered starting with 0001 for end users. For example, the number 000010001 would mean
that Demo OEM end user 0001 is entering the system.
For users other than Demo OEM, the user name must start with 00000. For example, the number
000000001 would mean that non-Demo OEM user 0001 is entering the system.
For OEM Users
3a. If you enter as an OEM user, the following web page appears:
One of two modes can be selected:

Administrator (Demo OEM option) - The administrator can assign licenses and devices to
customers, who can be either another OEM customer or Demo OEM. In this mode of operation,
the OEM admin can assign licenses/devices to end users (including themself) and can generate
license keys for the devices.
End User (Customer option) - The OEM end user, or the OEM itself can generate keys for self
use. In this mode, the user can only generate licenses based on the available device database.
The user can only view his/her own devices (that were assigned to that user) and licenses.
End users that belong to that channel cannot see devices or licenses that belong to the OEM or other
customers.
After you select the operating mode, the following web page appears:
CeraView User Guide
For Non-OEM Users

3b. If you enter as a non-OEM user the following web page appears:
Note that a channel or OEM user can also enter as one of their customers. In this case, the system
identifies the user as a channel/OEM user and will display a drop-down list to enable entry under the
user's name. This will be done to allow operations for devices that the user sent to his/her customers.
How to Use the System

The menus that you can select from are grouped according to their functions. Simply click the item you want
within a menu group (such as the Devices or Settings group).
When you select an item within a group, the relevant web page will open with the details concerning that
item.
At the top of the web page for the item, a line appears with buttons that you can click to perform a particular
operation.
From within an item web page, you do not have to return to the main web page. Instead, use the tabs at the
top (Devices, Licenses, etc.) to obtain a list of items for the particluar group.
Note that in any web page, you can click Print
CeraView User Guide
to send the contents of the page to the printer.
Managing the License

The following sections describe the system menus and options that you can select to obtain information
concerning your licenses and to perform license-related operations.
Working with Devices

The Devices group includes items that can be selected to perform device-related operations, such as to obtain
information about the devices included in your license, or import a device list from another source.
Device List
To obtain a list of devices:
In the Devices group, select All Devices, or click the Devices tab at the top of the web page (if it appears).
The following web page appears:
Note that for OEM users, the Generate Keys button is replaced with Assign to Customer
.
The list includes all the devices you purchased from Ceragon.
Click Device ID for a more deatiled description of the device.
In this page, you can assign the current ID to an end user, using the drop-down list in the Assign to
Customer field.
CeraView User Guide
Search for Devices

In the main device list web page, you can click Search
registered in the system.
to locate a particular device that is
Select the criteria (filters) you want for the search, and then click Search.
To clear the criteria you selected, click Clear.
Import Devices
In the toolbar, click Import
to import a list of devices from an external source.
You will be prompted to locate the file with the device list. Once you locate and select the file, click Import.
The device list file must be a text file with the following columns:
Device ID Customer
Country
Region /
Network
Link
Side
In the Device ID column, use only upper case letters.
Adding and Deleting Devices

To add a new device, in the toolbar, click New
CeraView User Guide
Enter a valid device ID in the field and click Save.

The device will be added to your device list.
.
To delete a device, select the device in the list, and click Delete
Exporting a Device List
To export a device list to a file, click Export
The list will be saved in an Excel file with the extension csv (Comma Separated Values).
Generating Keys
To generate license keys for one or more devices, select the devices in the main list by marking the
checkboxes beside them, and click Generate Keys
In this web page, only the devices you selected will appear.
10
The All Relevant Licenses area shows only the licenses that are common to all devices you selected
(meaning their lowest common denominator).
The current license types include the following:
1 = ACM
2 = Networking
3 = Capacity Upgrade
The following tables list the current license possibilities:
Capacity Upgrade
License
Type
Value
IP10-CAP-010
Feature disabled
IP10-CAP-025
Radio Cap. Upgrade 10->25 Mbps
IP10-CAP-050
IP10-CAP-100
IP10-CAP-150
IP10-CAP-200
Radio Cap Upgrade 10->200 Mbps
IP10-CAP-300
IP10-CAP-400
IP10-UPG-025-050
IP10-UPG-025-100
10
IP10-UPG-025-150
11
IP10-UPG-025-200
12
IP10-UPG-025-300
13
IP10-UPG-025-400
14
IP10-UPG-050-100
15
IP10-UPG-050-150
16
IP10-UPG-050-200
17
IP10-UPG-050-300
18
IP10-UPG-050-400
19
IP10-UPG-100-150
20
IP10-UPG-100-200
21
IP10-UPG-100-300
22
IP10-UPG-100-400
23
IP10-UPG-150-200
24
IP10-UPG-150-300
25
IP10-UPG-150-400
26
IP10-UPG-200-300
27
IP10-UPG-200-400
28
IP10-UPG-300-400
CeraView User Guide
Description
Name in License
Management Site
11
ACM
License
Type
Value
Name in License
Managament Site
Description
Feature disabled
IP10-ACM
ACM
Networking (Metro Switch Enabled)

License
Type
Value
Name in License
Management Site
Description
Feature disabled
IP10-Metro
Metro Switch
To add a license for which you want to generate a key, select the license in the All Relevant Licenses area
and click Add to add it to the Selected Licenses area.
Important! You can only select one license from each category (ACM, Networking, Capacity Upgrade). If
you select a capacity upgrade license and want to add a different capacity upgrade license, you must first
remove the first capacity upgrade license and then add the other one.
Once you select the licenses you want, click Generate Keys.
After you confirm your selection, the following example web page appears.
12
Assigning Devices to a Customer

For OEM users, you can assign devices to other users by selecting Assign Devices to a Customer in the
main web page Devices group. Or, you can click Assign to Customer
at the top of the
page.
In the Select Customer field, use the drop-down list to choose the customer you want to assign the devices
to.
Click Show Available Devices for a list of devices you can choose from.
In the available list of devices, click Filter & Sort to customize the device list, as shown in the following
example page.
CeraView User Guide
13
You can specify the ID of the device you want to include in the list, and select the list sort order (ascending
or descending).
After you click Go to generate the list, in the Available Devices list, select the devices you want to assign to
the user, and click Add to add them to the Assigned Devices list.
When you complete the operation, click Save.
In the confirmation page, click Confirm.
The following example page appears:
14
Click Continue to go back to the device list page.

The device list page will appear with the updated information.
CeraView User Guide
15
Working with Licenses

In the Licenses group, select All Licenses, or click the Licenses tab at the top of the web page (if it appears).
The web page displays all the licenses you currently own.
To search for a particular license, click Search, specify the criteria you want, and click Search again.
Click the number in the Qty Assigned column for a list of licenses assigned to customers.
16
Click the number in the Qty Generated column for a list of licenses used to generate keys.
CeraView User Guide
17
To generate license keys, select Generate Keys in the Licenses group in the main web page, or click
Generate Keys in the web page that appears when you click the Licenses tab.
To add a license for which you want to generate a key, select the license in the All Available Licenses area
and click Add to add it to the Selected Licenses area.
Click Show Relevant Devices for a list of devices associated with the licenses you chose.
18
To add a device for which you want to generate a key, select the device in the All Available Devices area
and click Add to add it to the Selected Devices area.
Once you select the devices you want, click Generate Keys.
The keys will be generated, as shown in the following example page, and the database will be updated.
CeraView User Guide
19
20
Assigning Licenses to a Customer

For OEM users, you can assign licences to other users by selecting Assign Licenses to a Customer. Or, you
can click the Assign to Customer button
at the top of the page.
In the Select Customer field, use the drop-down list to choose the customer you want to assign the licenses
to.
Click Show Available Licenses for a list of licenses you can choose from.
CeraView User Guide
21
In the Filter by Type field, click the drop-down list and choose the license type (Capacity, ACM,
Networking).
For License Code, click the drop-down list and choose the license specifications.
For Quantity to Assign, enter the amount of licenses you want to assign to that customer. The maximum
quantity is limited to the available quantity for the license you choose.
After you complete the filter options, click Add to add the licenses to the Assigned Licenses list. You can
repeat this procedure more than once to add other license types.
For Quantity to Return, enter the amount of unused licenses you would like to return (if relevant).
Click Save to save the license assigment information in the database.
In the page that appears, click Confirm to confirm the assignment.
A page will appear informing you that the operation was successful, and the main license list will be updated
with the information.
22
Settings
In the main web page, the Settings group includes items you can select for system information and
configuration.
Managing Users
Select the Manage Users item to define users and modify their properties. You can also access this item by
clicking the Settings tab at the top of the page (if it appears).
Use the Search button at the top

To define a new user, click New
CeraView User Guide
to locate a particular user.

.
The following page appears:
23
In this page, enter the information in the fields, and then click Save.
To delete one or more users, in the user list, mark the checkboxes beside the users you want to delete, and
click Delete
. Confirm your choice(s) in the page that appears and the users will be deleted.
Modifying your Profile

In the main Settings page, select the My Profile item to modify your personal information.
The same page appears as that for a new user. Modify the information as desired and click Save.
24
Generating Reports
In the main web page, you can select a report to generate: an Orders report, or a Devices and Activations
report.
To generate a report, select Orders Report or Devices & Activations Report in the main web page, or click
the Reports tab at the top of the page (if it appears).
For an Orders Report:

For Order No., you can select All or Between. If you select Between, specify the range of order numbers
you want to include in the report.
For Order Date, you can select All or Between. If you select Between, you will need to specify the range of
dates you want to include in the report.
In the Include field, you can select All for all types of orders, Closed orders only, or Open orders only.
When you are done selecting the report criteria, click Create Report.
CeraView User Guide
25
For a Devices & Activations Report:

For Devices, you can select All or Between. If you select Between, specify the range of device IDs you want
to include in the report.
For Activation Date, you can select All or Between. If you select Between, specify the range of activation
dates you want to include in the report.
When you are done selecting the report criteria, click Create Report.
26

Ceragon Radio

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ceragon Radio

Uploaded by

Copyright:

Available Formats

IP-10G Advanced Course

Visit our Customer Training Portal at Training.Ceragon.Com

Ceragon Training Agenda

Ceragon Training Agenda

Ceragon Training Agenda

System Architecture & Design:

Front Panel Overview

Installation (Practical Exercise using the Element Management System):

Troubleshooting Tools & Maintenance:

Using the Current Alarms

Licensing (retrieving license and installing license on IDU)

Ceragon Training Agenda

Ceragon Training Agenda

RSTP RING (Practical Exercise using the EMS):

Setting up an RSTP Ring

Simple Star Topology + RSTP (Practical Exercise using the EMS):

Star Topology + In Band +Protection (Practical Exercise using the EMS):

Enabling Protection Mode

Trail Prioritization (Practical Exercise using the EMS):

Setting Trail Priority

Ceragon Training Agenda

Ceragon Training Agenda

Quality of Service (Practical Exercise using the EMS):

Creating preliminary tables for classifiers & policers

Quality of Service (Practical Exercise using the EMS):

QoS demonstration using Video Streaming (VLC)

End to End Trap Configuration

Ceragon Training Agenda

Ceragon - Company Presentation

Leaders in High-Capacity Wireless Backhaul

Proprietary and Confidential

Segment Breakdown H1 2009

Proprietary and Confidential

Short Haul Links: Rapid Growth

From 0.8% market share in 2005 to 6.3% market share in 2009

Source: SLR, EJL, Ceragon

Proprietary and Confidential

Rural and WiMAX Backhaul

Proprietary and Confidential

Private, Utility, State &

Any service: Voice, data, personal broadband

Proprietary and Confidential

Strategic Partnerships for Growth

Opportunity to participate in large network deployments

Proprietary and Confidential

Global, Diversified Customer Base

Proprietary and Confidential

Ceragon Product Portfolio

PDH & Ethernet Access

PDH/SONET & Ethernet

Trunk (Long Haul, High Power)

OC-3 Aggregation (N+1)

Comprehensive mounting Portfolio

Proprietary and Confidential

Faster & easier network

Quick and easy network

Greater network availability

Smooth platform integration

Ceragon's Architecture Management Concept

Proprietary and Confidential

Ceragon Complete Offering

Network design, Service design, Radio

Project Management, Site Survey,