IP-10G Advanced Course Handbook v3.3

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
Dear Customer,
Please find below a detailed course agenda and setup requirements. We would appreciate your
efforts in reviewing and confirming the enclosed information prior to conducting the course.
Should you require further information, please do not hesitate to contact us at

training@ceragon.com.
I thank you in advance for your kind cooperation,
Avner Baruch
Ceragon Training Manager
General
Product IP-10G
Course Name IPEO&M: IP-10R1 extended operations and maintenance
Duration 4 days
Scope Product-oriented Theory + Hands-on
Number of trainees 10
Minimum required setup (to be provided by customer):
Item Quantity
IP-10G IDU 6
ODU 6
-48 VDC power supply (capable of feeding at least 2 IDUs) 2
Test Kit (RF to WG adapters, attenuators, SMA cable) 3 (1 per link)

ETH Cross-Cable (CAT.5) 7
ETH standard cable (CAT.5) 7
ETH Y-Cable (1+1 Protection kit) 2
NMS (PolyView) PC (FileZilla FTP Server installed) 1
1 per 2
PC / laptop
trainees
Craft (Serial) cable (USB to DB-9) 1
Variable attenuator + 2 SMA cables (optional) 1
L2 ETH Traffic Generator supporting 802.1p/q, multi streams & header analysis 1
TDM / SDH / SONET Traffic Generator 1
Main Shelf 3
Extension Shelf 3
1 Ceragon Training Agenda v3.0
Page 1
DAY 1
Introduction to Ceragon Company
Introduction to IP-10G
IP-10G IDU Front Panel Description
Shelf / Node Installation – Physical Inspection
Commissioning:
 System name & Contact Details (Unit Info)

 Reading Versions
 External Alarms
 Setting IP Address and Management (In Band / OOB)
 Trap Destination
 License Update (Demo ON/OFF, applying a new license)
Radio Link Commissioning:
 Frequencies
 Modulation Script
 TSL, RSL & MSE
 ATPC
 Link ID
 Local & Remote frequency change
 MAC Header Compression
 Local Radio Mute
 Remote Radio Settings
Introduction to ACM
L2 ETH Switch Modes:
 Single Pipe
 Managed Switch
 Creating VLANs in Switch Database
 Metro Mode
Interface Configuration:
 Ethernet switch port

 TDM
 SDH / SONET
 Wayside Channel
Page 2
DAY 2
TDM/SDH Cross-Connect - Configuration Review
TDM/SDH Cross-Connect – Practical Exercises
Performance Monitoring:
 Using the Current Alarms

 Using the Event Log
 Using RMON Registers and Statistics
 Radio statistics
 Interface statistics
Troubleshooting & Maintenance:
 Radio Loopbacks
 Line Loopbacks
 Configuration file
 Unit information file
 Setting IDU to factory defaults
 SW download
1+1 Internal Protection - Configuration Review
1+1 Internal Protection - Practical Exercises
Page 3
DAY 3
Introduction to Quality of Service & Traffic Engineering
QoS - Practical Exercises:
 Ingress Rate Limiter (Policer)

 Ingress Classification by MAC DA
 Ingress Classification by VLAN ID
 Ingress Classification by VLAN P-Bit
 Ingress Classification by IP ToS
 Egress Scheduler
 Egress Shaper
RSTP - Configuration Review
Network Resiliency (RSTP) - Practical Exercises:
 Enabling RSTP
 Investigating Bridge Mode per IDU
 Investigating Port State (Edge / Non-Edge / Blocked / Forwarding)
Q-in-Q (Metro) – Configuration Review
Q-in-Q (Metro) - Practical Exercises
Page 4
DAY 4
Introduction to Link Aggregation
Link Aggregation – Practical Exercises
XPIC – Configuration Review
XPIC - Practical Exercises
NMS (PV) Setup Configuration:
 Manual configuration of elements (IDUs)

 Auto-Discovery
 Site Polling
NMS End-2-End XC - Configuration Review
NMS End-2-End XC - Practical Exercises (various applications)
Exam
Evaluation Form
Course Summary
Page 5
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
2 Proprietary and Confidential
Page 6
1
6/9/2010
Global Sales
(Reflecting FY2009 results)
EMEA: 38%
NA: 16%
APAC: 37%
CALA: 9%
Segment Breakdown H1 2009

Success factors:
• Superior technology and professional services offering
• Better cost position Service Private
Networks
• Global Sales footprint with 19 offices worldwide Providers
13%
87%
• Strong partnerships with OEMs, distributors and VARs
Short Haul Links: Rapid Growth

Ceragon Total
Ceragon Market Share Links Total Short Haul vs. Ceragon Links
7.0% 35000 35000 650000
617427
6.3%
6.0% 30000 554189 550000
507249
26698
5.0% 25000 450000
387020
4.3% 20000 350000
4.0%
300509
15000 250000
3.0% 13175
2.6%
10000 150000
2.0% 2.1% 8132
5000 50000
1.0% 2380
0.8%
0 ‐50000
0.0% 2005 2006 2007 2008 2009
2005 2006 2007 2008 2009
PTP Radio Shipments
Ceragon ‐ Total Short Haul ‐ Next Generation Hybrid TDM/Packet &
links shipments
Legacy TDM
Total
Total market
short haul market
Growth drivers:
• From 0.8% market share in 2005 to 6.3% market share in 2009
•High capacity • 4,800 links to 35,000
•All IP • Grew in 2009 in shipments terms by 30%
• Global short haul shipment dropped by 11%.
Source: SLR, EJL, Ceragon
Page 7
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
Proprietary and Confidential
We Focus on Backhaul
High Capacity LTE/4G-Ready Wireless Backhaul Networks
Mobile Backhaul WiMAX Backhaul
Private, Utility, State & Rural Broadband

Local Government
Any access technology: Wire line or wireless, GSM, CDMA, HSPA, LTE or WiMAX
Access Backhaul / Metro Core
Any service: Voice, data, personal broadband
Page 8
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:*
Page 9
4
6/9/2010
Ceragon Product Portfolio
Capacity optimisation
Cost Efficiency
Access Aggregation Backbone

First Mile Aggregated links
PDH & Ethernet Access PDH/SONET & Ethernet SONET& Ethernet Trunk (Long Haul, High Power)
• SDH Aggregation • OC-3 Aggregation (N+1)
• Metro IP Migration • N x GbE Aggregation
• GbE rings
FibeAir Trunk
SDH
FibeAir IP-10 G
Comprehensive mounting Portfolio
FibeAir® Family
Split Mount All Indoor Full Outdoor
Radio Units: From compact to high power Compact and modular Full outdoor Nodal site,
From 1+0/1+1 to N+1/N+0 Trunk solutions All indoor solutions N+0 to N+N, fully redundant,
All RF units applicable
Carrier Ethernet / Native2
IP‐10
Carrier Ethernet/ TDM Trunk

Native2 TDM
IP‐10 1500R
3200T
IP‐10
Carrier Ethernet / Native2
Page 10
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, multi-
platform
Ceragon's Architecture Management Concept

Ceragon Complete Offering
Plan :
• Network design, Service design, Radio
g , Synchronization
Design, y design,
g , Power
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:
• 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 11
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
Mobile Backhaul Case Studies
14
Page 12
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
Telcel:
2600+ links migration to packet with LTE in mind
Optimize :
Tree to Rings
helping Telcel to optimize the radio portion of the network:

Design, install. Maintain. Huge SDH install base
Page 13
8
6/9/2010
Digitel:
1350+ links Delivering high capacity, anywhere.
Converged, 3G and Rural Broadband IP backhaul

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

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

broadband services in remote locations
Page 14
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
2G 2G
63  E1
• Solutions BTS
ECI
TDM
BSC
n x E1 2G ECI nx STM-1 XDM-1000

• Mix of all indoor and split TDM + TDM n x E1 XDM-100
nxSTM-1 Rings STM-1c
PDH TDM
Ethernet 1+1 Microwav Ceragon Cerago
e FibeAir n
STM-1 3G
FibeAir
RNC
• Why Trunk? E1
Ceragon
FibeAir
• 7+0 4STM-1 and 3 GbE 3G
Ethernet
Node B
• Advanced Carrier Ethernet PDH
Microwav IP MAX2
features e
Ethernet
Huawei
Ethernet Switch
Ethernet
• Both interfaces use the same + 2xGbE
Ceragon Ceragon
1*E1
radio equipment. Smooth FibeAir FibeAir 2xGbE
migration from all TDM to all

packet
• Both type operate concurrently
on the same antenna and radio
branching - Native2
Page 15
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 nxFE / GbE
200km apart spanning over jungles
and lakes Cisco Ceragon Ceragon Ceragon Ceragon Cisco
7600 FibeAir FibeAir FibeAir FibeAir 7600
• Solutions Service Aware Radio Link
nxFE / GbE Service Aware Radio Link

nxFE /
• Split, all packet 3X(2+0) multi radio Service Aware Radio Link GbE
• 6 hopes
• Abstraction layer at both ends. (Cisco
routers)
31.94 km 32.81 km CESP 36

.53
• Why Ceragon? CANO
34 25 02.00 S
ARTI
34 22 37.00 S
057 31 03
03.00
00 W
34 21 02.00 S
057 09 44.00 W
km
•
RIPI
High Capacity and flexibility .6
8
km 057 51 41.00 W
34 30 58.00 S
056 49 07.00 W
37
.5
49 5
km
• Modularity and upgradeability Quilmes

34 43 41.00 S
• High capacity all, indoor, all packet 058 15 04.00 W

RIBO
34 42 58.00 S
056 29 18.00 W
33
.7
7
km
• Cisco partnership (CTDP) VPLA

34 54 21.00 S
• Multi layered availbilaity 0' 58° 40' 20' 57° 40'
056 11 59.00 W
20'
• Radio level, System level, e-t-e
All Indoor & Split Configurations – LTE Ready

Backhaul (NA)
• Challenge:
• Ubiquitous network concept for Native2
1+1
wireless backhaul serving remote Tail site #1 Native2
Native2
base station sites 1+1 1+1
1 1
• Migration from 2G/3G – UMTS to

HSPA and LTE
Tail site #2
Native2
1+1
Hub/Aggregation site
• Solutions Fiber site
• Mix of all indoor and split TDM + Native Ethernet service ("Ethernet VC")
Ethernet 1+1
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
Page 16
11
6/9/2010
An army network backbone (Philippines)

15° 0'
• Challenge:
AGUINALDO
Malacanang Antipolo
CAPINPIN
• Build an army military grade long microwave 10'

TAGAYTAY
LUCBAN
backbone GUINYANGAN
PASACAO PILI
• Connectingg the Philippines
pp islands with manyy 20'
IRIGA
CAMALIG
over the water links with distances of up to
100km 30'
MATNOG
• Cost-effective voice, data, and video CALBAYOG
conferencing services to satisfy command 40'

CATBALOGAN
and control requirements

TACLOBAN
ORMOC
50'
• Solutions CEBU
MACTAN
CAMOTES
• hops of 1+1 all indoor 10° 0'
• 7 GHz BOHOL
• Link
Li k IInterface:
t f STM 1
STM-1 10' CAMIGUIN
CDO
• Why Ceragon? 20'

OZAMIZ
MANTICAO
PAGADIAN
• High power split configuration 1+1 GANYANGAN
LACAUAN PULACAN
BALABAGAN
30' LINUGWAYAN
• Integrated offering through a channel with TAGUITE
PC HILL
AWANG
networking, terminal and support ZAMBOANGA MERCEDES UPI
6° 40'
120° 50' 40' 30' 20' 10' 125°
WiMAX Case Studies
24
Page 17
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: Ceragon’s FibeAir IP-10
Case Study
Adam Internet - Australia Gaw ler
5 .0
7 km
Gaw ler South

Angle Vale Vf 2 .3 5
km
Kudla
Why did Adam Internet choose
2.98 km
0.
4.31 km
Smithfield (Sa)
79
km
Smithfield
Ceragon? Elizabeth m
6k
Uley Reserv e
4.12 km
6 .3
Burton 6 00
6.
• Best solution for All-IP network

kkm
k
ELIZABETH VALE
48 York Terrace
Parafield Gardens
3.09 k
m
5.2 1 km 9 km
(native Ethernet)
3.06 km
3.1
5 km Greenw ith Vf
OSBOURNEGreenfields Salisbury East 4 .1
Salisbury South Fairv iew Park

8.6 9 km
4. 48
km
7 .1
• Advanced protection schemes

7.45 km
Modbury North
7k
Pooraka Vf
km
m
Gepps Cross
5.66 km
4.04
4. 32 km Gilles Plains
km Hope Valley West
km
5 .8 7
(Ring) 5 km
West Lakes 7.49 3.0
4.14
Ottow aykm
GREENACRE
km ATHELSTONE
3.09
Bev erley km .0 6
km
Glynde3
Dudley Park New ton
4
• Built in Carrier Ethernet Switch

4. 40
4.2
ST PETERS
4. 72
km
4.
Henley Beach km
Mile End
27
3.23 km
Wattle Park
km
km
m
Unley 4. 32
9k
Adelaide Airport
• Flexible & Scalable roll out GLENSIDE

2.6 7 km
4.6
km
Plympton
3.29 k m
62
3.
GLANDORE Haw thorn

2.9
7 km
capabilities
2. 5
8 km
Warradale BELAIR 2.9 4

km
2 .53 km
km
4.20 Daw Park
Somerton Park Vf
Eden Hills
Marion East 4.14 km
Coromandel Valley Vf
km
3
3.59
Flagstaff
HILL Hill
2
3.3
O'HALLORAN
km
2.6
6.1 8 km
4 km
3.39 km
5 km
SHEIDOW PARK
2.6
3.
Aberfoyle Park Cherry Gardens
67
km
HAPPY VALLEY
6 km
LONSDALE 3.0 3
2.9
km
REYNELLA VF 9.8 4 km 4 km Onkaparinga Hills

O'Sulliv an Beach 3 4.
3.1
4 km
km
3.88 Woodcroft
Hackham West
Seaford Meadow s
3.90
km
Seaford McLaren Vale

2.9 8 km
km
MOANA VF
4
73 km
1 1.1
Page 18
13
6/9/2010
Case Study
Allegro: Business services for Queensland’s
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)
Case Study
PtP Ethernet microwave for Backhaul and high
capacity services
Business Access : Backhaul:
Service aware Ethernet microwave IP/MPLS based ring topology service
enhanced with Adaptive Modulation aware Ethernet microwave enhanced
Or PtMP WiMAX with Adaptive Modulation
PtP IP/MPLS IP/MPLS

router router
PtMP -
WiMAX
IP/MPLS
WiMAX router
Base
Station
Page 19
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
Ceragon IP Solution: Urban/Rural Link

planning
Challenges:
1. Multi hops (up
to 8)
2 Low delay for
2.
VoIP
3. Extremely
high capacity
4. Rapid
E-t-E delay <6msec
deployment
5. High
availability
6. Upgradable
from tree to
ring topology
7. Service aware
E-t-E delay <7msec transport
* Latency figure are based on a 64Byte
Page 20
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
Low Cost, High Capacity

Carrier Ethernet Aggregation for WiMAX Backhaul
Low Capacity Link
1+1
Aggregation Site
BS site
Switch
Router Ceragon
FibeAir
Core Site
Low Capacity Link Ethernet Aggregation XC
XC
1+1
Ceragon
FibeAir
BS site
PSN
Ethernet
Switch Ceragon
FibeAir Microwave Link
Router
Aggregation
Site
BS site
Page 21
16
6/9/2010
Verticals Case Studies
33
Simon says… there are 9 distinct verticals
Municipality Defense Public Security
Utility OPG Broadcast
Health Education Finance
Page 22
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) Police
HQ
• 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 Local
• Performance in ring topologies Police
Station Local Police
• Extremely reliable hardware Station
• Versatile auxiliary channels 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 South Australian Forest
Photo: Forestry SA
support
Page 23
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
• 53 u unlicensed
ce sed spurs
spu s
• Why Ceragon?
• Cost efficient high capacity native Ethernet in
a 2+0 ready configuration
• Upgradeable and modular
• Integrated offering through a channel
(Integrators Australia) with networking,
services and support
Case Study
Philippines: An army network backbone
15° 0'
AGUINALDO
Defense Malacanang Antipolo
CAPINPIN
10' LUCBAN
TAGAYTAY
GUINYANGAN
• Challenge: PASACAO PILI
IRIGA
• Build an army military grade long microwave 20'
CAMALIG
backbone
MATNOG
30'
• Connecting the Philippines islands with many over CALBAYOG
the water links with distances of up to 100km CATBALOGAN
40'
• Cost-effective voice, data, and video conferencing
services to satisfy command and control TACLOBAN
ORMOC
50'
requirements CAMOTES
• Solutions
CEBU
MACTAN
10° 0'
• 36 hops 1+1 all indoor BOHOL
• 7 GHz 10' CAMIGUIN
• Link Interface: STM-1

• Why Ceragon? 20'
CDO
MANTICAO
OZAMIZ
• High power split configuration 1+1 PAGADIAN

GANYANGAN
LACAUAN PULACAN
• Integrated offering through a channel with 30'

TAGUITE
LINUGWAYAN
BALABAGAN
PC HILL
networking, terminal and support ZAMBOANGA MERCEDES
AWANG
UPI
6° 40'
120° 50' 40' 30' 20' 10' 125°
Page 24
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
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)
• Integrated offering through a channel with
networking, services and support
Page 25
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)
Case Study
USA: Rural electrical cooperative
Utility
• Challenge:
• Create a reliable backbone to connect SCI’s
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
• Ring g topology
opo ogy
• Why Ceragon?
• Cost efficient, Upgradeable split Native2
solution.
• Integrated offering through a channel –
Maplenet Wireless with networking, services
and support
South Central Indiana REMC (“SCI”)
Page 26
21
6/9/2010
Case Study
Australia: Alinta Gas pipeline
OPG
• Challenge:
• A long mission critical communication link
1,300km
for a SCADA system
• Solutions
• 43 hops 1+1
• Why Ceragon?
• Cost efficient high power radio units
• Highly available radio link
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? MONTAGEL
• High Capacity Ethernet in all indoor

configuration
LA BRAGUE
• Modularity and upgradability

ST RAPHAEL
Page 27
22
6/9/2010
Case Study
Australia: TV network Intra-studio
communication
Broadcast
XC
XC
• Challenge: Broadcast
Studio Site B
• Create a reliable high capacity contribution site
network Ceragon
Ethernet switch
• Leverage highly available excessive capacity to FibeAir
up sell telecom services: Voice and Data
• Solutions
• 4 hops 1+0 split space diversity
Native Ethernet Fiber as a
• Link Interface: Ethernet Microwave as an primary
• Alternate path with links up to 70km with alternate path path
• Why Ceragon?
XC
• Cost efficient high power highly available native XC
Ethernet in a 1+0 configuration

• Service protection support Ceragon Studio Site A
FibeAir
networking, services and support 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
Page 28
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
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)
Page 29
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
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
 Link Interface: Ethernet
 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)
Page 30
25
6/9/2010
Thank You
51
Page 31
26
Introduction to Radio
Agenda
• RF Principals
• Parameters Affecting Propagation
• Atmospheric Refraction
• Multipath
• Duct
• Rain Fading
• Fresnel
• RF Li kB
Link i C
Basic Components
• Link Calculation
• Modulation
2
Advanced Operation & Maintenance Course

Page 32
1
RF Principals
• A Radio Link requires two end stations

• A line of sight (LOS) or nLOS (near LOS) is required
• Microwave Radio Link frequencies occupy 1-80GHz
Local Remote
3
Why Radio?
Advantages (compared to alternative cable/fiber infrastructure) :

• Easier installation
• Faster installation
• Cheaper installation
• Easier maintenance
4

Page 33
2
RF Principals
• RF - System of communication employing electromagnetic waves (EMW)

propagated through space
• EMW travel at the speed of light (300,000 km/sec)
• The wave length is determined by the frequency as follows -
Wave Length = c where c is the propagation velocity of electromagnetic

f waves in vacuum (3x10^8 m/s)
• Microwave – refers to very short waves (millimeters) and typically relates to
frequencies above 1GHz:
 300 MHz ~ 1 meter
 10 GHz ~ 3 cm
5
RF Principals
We can see the relationship between colour, wavelength and amplitude using
this animation
6

Page 34
3
Radio spectrum
7
Parameters Affecting Propagation
• Dispersion
• Humidity/gas
H midit /gas absorption
• Multipath/ducting
• Atmospheric conditions (refraction)
• Terrain (flatness, type, Fresnel zone clearance, diffraction)
• Climatic conditions (rain zone, temperature)
• Rain attenuation
8

Page 35
4
Parameters Affecting Propagation –
Dispersion
• Electromagnetic signal propagating in a physical medium is degraded

because the various wave components (i.e., frequencies, wavelengths) have
different propagation velocities within the physical medium:
• Low frequencies have longer wavelength and refract less

• High frequencies have shorter wavelength and refract more
9

Atmospheric Refraction
• Deflection of the beam towards the ground due to different electrical

characteristics of the atmosphere’s
atmosphere s is called Dielectric Constant.
• The dielectric constant depends on pressure, temperature & humidity in the
atmosphere, parameters that are normally decrease with altitude
• Since waves travel faster through thinner medium, the upper part of the wave
will travel faster than the lower part, causing the beam to bend downwards,
following the curve of earth
With Atmosphere
No Atmosphere
10

Page 36
5
Multipath
• Multipath occurs when there is more then one beam reaching the receiver
with
ith different amplit
amplitude
de or phase
• Multipath transmission is the main cause of fading in low frequencies
Direct beam
Delayed beam
11

Duct
Atmospheric duct refers to a horizontal layer in the lower atmosphere with vertical refractive
index gradients causing radio signals:
• Remain within the duct
• Follow the curvature of the Earth
• Experience less attenuation in the ducts than they would if the ducts were not present
D tL
Duct Layer
Duct Layer
Terrain
12

Page 37
6
Rain Fading
• Refers to scenarios where signal is absorbed by rain, snow, ice

• Absorption becomes significant factor above 11GHz
• Signal quality degrades
• Represented by “dB/km” parameter which is related the rain density
which represented “mm/hr”
• Rain drops falls as flattened droplet
 V better than H (more immune to rain fading)

Rain Fading
Heavier rain >> Heavier Atten.
Hi h FQ >> Higher
Higher Hi h Attenuation
Att ti

Page 38
7
Fresnel Zone
3rd
2nd
1. EMW propagate in beams
1st RX
2. Some beams widen – therefore, their path is longer
TX
3. A p
phase shift is introduced between the direct and indirect
beam
4. Thus, ring zones around the direct line are created
Duct Layer0
Terrain
15

Fresnel Zone
Obstacles in the first Fresnel zone will create signals that will be 0 to 90 degrees
out of phase…in the 2nd zone they will be 90 to 270 degrees out of phase…in 3rd
zone, they will be 270 to 450 degrees out of phase and so on…
Odd numbered zones are constructive and even numbered zones are destructive.
16

Page 39
8
Fresnel Zone
Note that there are many possible Fresnel zones, but we are chiefly concerned
with zone 1.
If this area were blocked by an obstruction, e.g. a tree or a building, the signal
arriving at the far end would be diminished.
When building wireless links, we therefore need to be sure that these zones be
kept free of obstructions.
In wireless networking we should check that that the area containing about 40-60
percent of the first Fresnel zone should be kept free.
3rd
2nd
1st RX
TX
17
RF Link Basic Components –

Antennas
Antennas are devices used to radiate electromagnetic energy into space.
OMNI-DIRECTIONAL antennas radiate & receive energy from all directions

at once (seldom used)
DIRECTIONAL antennas radiate energy in LOBES (or BEAMS) that extend

outward from the antenna.
The radiation pattern contains small minor lobes (weak with little effect on
the main radiation pattern)

Page 40
9
RF Link Basic Components –
Parabolic Reflector Radiation (antenna)
Microwaves travel in straight lines - it can be focused and reflected just as

light rays.
rays
A feeder receives the microwaves from the WG and then transmits them
towards a parabolic dish (reflecting surface)
The wave-front reaches the reflecting surface of the antenna, and then it
leaves the antenna in parallel paths
Because of the special

p shape
p of a parabolic
p
surface, all paths from source to the reflector and
back to end user are the same length
Link Calculation – Basic Example

Link Calculation
+Gant1 +Gant2
+Lfsf
TX
IDU TX Losses RX Losses IDU RSL
RSL ‐ Received Signal Level

TSL – Transmitted Signal Level
Lfs ‐ Free‐space loss = 92.45 + 20 log x(distance in km x frequency in GHz)
RSL = TX – TX + Gain
Losses
‐ L + Gain
Ant. 1
‐ RXAnt. 2 Losses
fs

Page 41
10
Digital Modulation
Modulation
Modulation is used to transfer a message (voice, image, data, etc.) on to a

carrier wave for transmission
transmission.
A low frequency that comprises the message (baseband) is translated to a

higher range of frequencies
Modulation allows higher data rate transmissions
The process of modulation is reversible.
A device that performs modulation is known as a modulator and a device that

performs the inverse operation of modulation is known as a demodulator
Digital Modulation
Modulation
Low fq. Signal (up) +

high fq. Carrier (down) =

Page 42
11
QPSK Modulation
Quadrature Phase Shift Keying is a phase modulation algorithm
The phase of the carrier wave is modulated to encode bits of digital

information in each phase change
Because QPSK has 4 possible states, QPSK is able to encode two bits per
symbol
QPSK is more tolerant of link degradation than 8PSK, but does not provide as
much data capacity
45 degrees Binary 00
QAM Modulation
Quadrature Amplitude Modulation employs both phase modulation (PM) and

p
amplitude modulation ((AM))
The input stream is divided into groups of bits based on the number of
modulation states used.
In 8QAM, each three bits of input, which provides eight values (0-7) alters
the phase and amplitude of the carrier to derive eight unique modulation states
In 64QAM, each six bits generates 64 modulation states; in 128QAM, each

bi generate 128 states, and
seven bits d so on

Page 43
12
QPSK VS. QAM Modulation
The various flavors of QAM offer higher data rates then 8‐PSK
8 PSK
This is because QAM achieves a greater distance between adjacent points in the I‐Q
plane by distributing the points more evenly
The points on the constellation are more distinct and data errors are reduced
Higher order >> more bits per symbol
Constellation points are closer >>TX is more susceptible to noise
SNR and RSL Constellation

The higher the SNR, the better the received signal !

Page 44
13
4QAM VS. QPSK
The symbols are determined by modulating The symbols are determined by modulating
the Phase, and Amplitude of the carrier the Phase of the carrier signal.
signal.
8QAM
Diagram for 8QAM: 3bit represent 8 different states
Bit sequence Amplitude Phase (degrees)

000 1/2 0 (0 )
000 1 0 (0 )
010 1/2 pi/2 (90 )
011 1 pi/2 (90 )
100 1/2 pi (180 )
101 1 pi (180 )
110 1/2 3pi/2 (270 )
111 1 3pi/2 (270 )
28

Page 45
14
16QAM
Constellation diagram for 16QAM:

4bit represent 16 different states
29
128QAM Modulation
Constellation diagram for 128QAM:

7bit represent
p 128 different states
Higher QAM order results in a higher

data rate
This is why we modulate…
30

Page 46
15
256QAM Modulation
Constellation of 256QAM with noise added Constellation of 256QAM
31
Thank You !
training@ceragon com
training@ceragon.com

Page 47
16
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 48
1
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 49
2
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)
Quantity 9 Expected value
3
3
2
1
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

Page 50
3
The difference from Expected value…
Quantity
Error = 0 mm
Error = + 2 mm
Error = - 3 mm
Error = + 6 mm
Error = - 4 mm
width
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
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
Page 51
4
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
Calculating MSE
Quantity Error = 0 mm
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
Page 52
5
MSE in digital modulation (Radios)
Let us use QPSK (4QAM) as an
example:
Q
QPSK = 2 bits per symbol
01 00
2 possible states for I signal
2 possible states for Q signal
= 4 possible states for the

I combined signal
The graph shows the expected

values (constellation) of the
11 10 received signal (RSL)
The black dots represent the

expected values (constellation)
Q of the received signal (RSL)
01 00
The blue dots represent the
actual RSL
I
Similarly to the previous
example we can say that the
example,
bigger the errors are – the
harder it becomes for the
11 10 receiver to detect & recover the
transmitted signal
Page 53
6
Q
01 00 MSE would be the average
e1 errors of e1 + e2 + e3 + e4….
e2
I
When MSE is very small the
4
e4 actual signal is very close to
e3
the expected signal
11 10
Q
01 00 When MSE is too big, the
e1 actual signal (amplitude &
e2 phase) is too far from the
expected signal
I
4
e4
e3
11 10
Page 54
7
Using MSE
Commissioning | Troubleshooting
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
Page 55
8
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
256QAM has it but
b t
poor immune to noise
64QAM has less capacity but much

better immune for noise
ACM – Adaptive Code Modulation
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]:
Downgrade ACM Profile Upgrade ACM Profile

Profile Mod 10-6 Threshold when MSE reaches… when MSE reaches… Optimal
0 QPSK 6.9 10.4 11.9 >30
1 8PSK 11 14.5 16 >30
2 16QAM 13 3
13.3 16 8
16.8 18 3
18.3 >30
3 32QAM 18 21.5 23 >30
4 64QAM 20 23.5 25 >30
5 128QAM 24.4 27.9 29.4 >33
6 256QAM 25 28.5 30 >35
7 256QAM 28 31.5 33 >35
Page 56
9
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 10-6 Threshold when MSE reaches… when MSE reaches… Optimal
0 QPSK 6.7 10.2 11.7 >30
1 8PSK 12 15.5 17 >30
2 16QAM 13 1
13.1 16 6
16.6 18 1
18.1 >30
3 32QAM 17.3 20.8 22.3 >30
4 64QAM 19.6 23.1 24.6 >30
5 128QAM 22.6 26.1 27.6 >33
6 256QAM 25 28.5 30 >35
7 256QAM 27.5 31 32.5 >35

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

2. When MSE drops below -27.5dB, we will experience high BER
3
3. To avoid High BER we change the profile when MSE reaches -31dB
4. 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… when MSE reaches… Optimal
0 QPSK 6.7 10.2 11.7 >30
1 8PSK 12 15.5 17 >30
2 16QAM 13.1 16.6 18.1 >30
3 32QAM 17.3 20.8 22.3 >30
4 64QAM 19.6 23.1 24.6 >30
5 128QAM 22.6 26.1 27.6 >33
6 256QAM 25 28.5 30 >35
7 256QAM 27.5 31 32.5 >35
5 dB security window
Page 57
10
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
Profile 7 Profile 6 Profile 5 Profile 4 Profile 3 Profile 2 Profile 1 Profile 0
MSE
‐31 ‐28.5 ‐26.1 ‐23.1 ‐20.8 ‐16.6 ‐ 15.5 ‐10 .2
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 ‐30
Profile 7 Profile 6 Profile 5
‐31 ‐28.5 ‐26.1 MSE
Page 58
11
Troubleshooting wrong modulation
When different settings of Modulation are set, MSE will be showing -
99.99dB (Modulation Mismatch):
RSL = ~ (-45) dBm RSL = ~ (-45) dBm

MSE = -99.99 dB MSE = -99.99 dB
Thank You !
t i i @
24
Page 59
12
7/7/2010
ACM - Adaptive Code Modulation
FibeAir IP-10’s Key Feature
• IP-10 utilizes a unique Adaptive Coding & Modulation (ACM) –
odu at o range:
Modulation a ge QQPSK
S - 256QAM
56Q
• 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
Page 60
1
7/7/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 Strong
Weak
Non-real time FEC FEC
services
When we engineer our services, we may assign certain services to

highest priority
Page 61
2
7/7/2010
ACM & SLA

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

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
Page 62
3
7/7/2010
IP-10 radio capacity - ETSI

7MHz Ethernet 14MHz Ethernet
ACM # of ACM # of
Modulation Capacity Modulation Capacity
Point E1s Point E1s
(Mbps) (Mbps)
1 QPSK 4 9.5 – 13.5 1 QPSK 8 20 - 29
2 8 PSK 6 14 – 20 2 8 PSK 12 29 - 41
3 16 QAM 8 19 – 28 3 16 QAM 18 42 - 60
4 32 QAM 10 24 – 34 4 32 QAM 20 49 – 70
5 64 QAM 12 28 – 40 5 64 QAM 24 57 – 82
6 128 QAM 13 32 – 46 6 128 QAM 29 69 - 98
7 256 QAM 16 38 – 54 7 256 QAM 34 81 - 115
8 256 QAM 18 42 – 60 8 256 QAM 37 87 - 125
28MHz 40MHz 56MHz

Ethernet Ethernet Ethernet
ACM # of ACM Modulatio # of ACM # of
Modulation Capacity Capacity Modulation Capacity
Point E1s Point n E1s Point E1s
(Mbps) (Mbps) (Mbps)
1 QPSK
Q 16 38 - 54 1 QPSK 23 56 - 80 1 QPSK 32
3 76
6 - 109
09
2 8 PSK 22 53 - 76 2 8 PSK 34 82 - 117 2 8 PSK 48 114 - 163
3 16 QAM 32 77 - 110 3 16 QAM 51 122 - 174 3 16 QAM 64 151 - 217
4 32 QAM 44 103 - 148 4 32 QAM 65 153 - 219 4 32 QAM 75 202 - 288
5 64 QAM 54 127 - 182 5 64 QAM 75 188 - 269 5 64 QAM 75 251 - 358
6 128 QAM 66 156 - 223 6 128 QAM 75 214 - 305 6 128 QAM 75 301 - 430
7 256 QAM 71 167 - 239 7 256 QAM 75 239 - 342 7 256 QAM 75 350 - 501
8 256 QAM 75 183 - 262 8 256 QAM 75 262 - 374 8 256 QAM 75 372 - 531
Ethernet capacity depends on average packet size

IP-10 radio capacity - FCC

10MHz Ethernet 20MHz Ethernet
ACM # of ACM # of
Point E1s Point E1s
(Mbps) (Mbps)
1 QPSK 7 13 – 18 1 QPSK 16 28 - 40
2 8 PSK 10 19 – 27 2 8 PSK 22 39 - 56
3 16 QAM 16 28 – 40 3 16 QAM 32 57 - 81
4 32 QAM 18 32 – 46 4 32 QAM 38 67 - 96
5 64 QAM 24 42 – 61 5 64 QAM 52 93 - 133
6 128 QAM 28 50 – 71 6 128 QAM 58 102 - 146
7 256 QAM 30 54 – 78 7 256 QAM 67 118 - 169
8 256 QAM 33 60 – 85 8 256 QAM 73 129 - 185
30MHz 40MHz 50MHz

ACM # of ACM Modulatio # of ACM # of
Modulation Capacity Capacity Modulation Capacity
Point E1s Point n E1s Point E1s
1 QPSK
Q 22 39 - 55 1 QPSK 31 56 - 80 1 QPSK 37
3 65 - 93
2 8 PSK 35 62 - 89 2 8 PSK 46 82 - 117 2 8 PSK 59 105 - 150
3 16 QAM 52 93 - 133 3 16 QAM 69 122 - 174 3 16 QAM 74 131 - 188
4 32 QAM 68 120 - 171 4 32 QAM 84 153 - 219 4 32 QAM 84 167 - 239
5 64 QAM 80 142 - 202 5 64 QAM 84 188 - 269 5 64 QAM 84 221 - 315
6 128 QAM 84 164 - 235 6 128 QAM 84 214 - 305 6 128 QAM 84 264 - 377
7 256 QAM 84 185 - 264 7 256 QAM 84 239 - 342 7 256 QAM 84 313 - 448
8 256 QAM 84 204 - 292 8 256 QAM 84 262 - 374 8 256 QAM 84 337 - 482
Ethernet capacity depends on average packet size

Page 63
4
7/7/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 Capacity increase by

packet size (bytes) compression
64 45%
96 29%
128 22%
256 11%
512 5%
IP-10 Native2 radio dynamic capacity allocation

Example: 28MHz channel bandwidth
Example 32QAM 128QAM 256QAM

Modulation
Example
traffic mix
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 - - 75 E1s + 25Mbps
Page 64
5
7/7/2010
Adaptive Coding & Modulation (ACM)

It’s 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
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%
0 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 65
6
7/7/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

Unavailability of
Modulation Throughput (Mbps) Availability (%) modulation
Outage – 5 minutes and 15 seconds
256QAM (2) 400 99.999 4min, 28sec
With Adaptive Modulation: requires 1 ft antennas

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

QPSK 80 99.999 5min,, 3sec
8PSK 120 99.998 9min, 3sec
16QAM 160 99.997 11min, 4sec
32QAM 210 99.996 16min, 42sec
64QAM 260 99.995 24min, 35sec
128QAM 320 99.992 37min, 35sec
256QAM (1) 360 99.989 55min, 33sec

256QAM (2) 400 99.985 1hr,18min, 13sec
Assumed rain zone K, 23 [GHz] band
Proprietary and Confidential Source: Ceragon Networks
ACM Benefit in TDM to IP migration scenario

SMOOTH Migration
• Typical 4E1 radio

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

 5 TIMES THE CAPACITY
 SAME ANTENNAS
4xE1 + 40Mbps
 Same 7MHz channel
Ethernet
 QPSK – 256QAM with ACM
 99.999% availability for the E1s 7MHz channel
 Low cost, scalable, pay as you grow
14
Page 66
7
7/7/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 67
8
7/7/2010
Thank You !
17
Page 68
9
Introduction to 802.1 P/Q
Prerequisites
Prior to taking this module, trainee should be familiar with the

following:
• Ethernet Topologies
• OSI 7 Layers model

1
Page 69
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 70
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 71
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 72
Untagged Ethernet Frame
FCS is created by the sender and recalculated by the receiver
Preamble + SFD DA SA Length / Type DATA + PAD FCS
4 Bytes
8 Bytes 6 Bytes 6 Bytes 2 Bytes 46 - 1500 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 VLAN TAG Length / Type DATA + PAD FCS
TPID = 0x8100 TCI
P‐TAG CFI VLAN ID

TPID = Tag protocol ID
3 Bit 1 Bit 12 Bit
TCI = Tag Control Information
CFI = 1 bit canonical Format Indicator

5
Page 73
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-10’s 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)
TPID / ETHER-Type / Protocol Type…

TPID in tagged frames in always set to Protocol type Value
0x8100 Tagged Frame 0x8100
ARP 0x0806
p
It is important that yyou understand the Q i Q (CISCO)
Q‐in‐Q 0 8100
0x8100
meaning and usage of this parameter
Q‐in‐Q (other vendors) 0x88A8
Q‐in‐Q (other vendors) 0x9100
Later when we discuss QoS, we shall Q‐in‐Q (other vendors) 0x9200
demonstrate how & why the system RARP 0x8035

audits this parameter IP 0x0800
IPv6 0x86DD
PPPoE 0x8863/0x8864
MPLS 0x8847/0x8848
IS‐IS 0x8000
LACP 0x8809
802.1x 0x888E

6
Page 74
VLAN Membership: By Port
Every switch port is associated with specific VLAN membership
• PRO – easy configured

• CON – no user mobility
For example – ports 1,2 & # can see each other but cannot PING
other ports (different VLAN membership)
1 2 3 4 5 6 7 8
VLAN 22
VLAN 5
VLAN 9
VLAN 333
VLAN 100
VLAN 1
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
00:20:8f:40:15:31
endpoints
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

7
Page 75
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
Port Types
Access Port – a port which is not aware of VLANs

(Cannot tag outgoing frames or un-tag incoming frames)
VLAN aware Switch

A
Device unaware of VLANs Switch tags the ingress

transmits untagged frames with VID according
(regular) ETH frames to specific Tagging
mechanism

8
Page 76
Port Types
Trunk Port – a port which is aware of VLANs

(Can tag or un-tag incoming frames)
VLAN aware Switch

A T
Device unaware of VLANs Switch tags the ingress frames with VID according to
transmits untagged specific Tagging mechanism
(regular) ETH frames
Switch un-tags frames with VID received from network
and delivers untagged frames to Access ports
Port Types
Trunk Port can carry tagged frames with different VIDs.

This requires Port Membership configuration.
VLAN aware Switch

T
A
A A
This port is not a member of the Trunk

port membership list, hence, traffic is
discarded

9
Page 77
Q-in-Q
• Additional VLAN (S-VLAN) is inserted

• Frame size increases to 1526 Bytes
4 Bytes 4 Bytes
Preamble + SFD DA SA S ‐ VLAN C ‐ VLAN Length / Type DATA + PAD FCS
TPID = 0x88A8
0 88A8 TCI TPID = 0x8100
0 8100 TCI
P‐TAG CFI VLAN ID P‐TAG CFI VLAN ID

3 Bit 1 Bit 12 Bit 3 Bit 1 Bit 12 Bit
Port Types
Q-in-Q (A.K.A. Double Tagging…VLAN Encapsulation…)
+
VLAN
aware Switch
CN 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)

10
Page 78
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
GE
Site
FE/GE RNC
GE
STM1/
n x T1/E1
FibeAir OC3
Tail site IP-10 MPLS
IP-10 ATM Router
Router Core
Site BSC/MSC

11
Page 79
Mapping ETH to MPLS and vice versa
IP-10’s 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
GE
Site
FE/GE RNC
GE
STM1/
n x T1/E1
FibeAir OC3
STM1/
Tail site IP-10 OC3
MPLS
IP-10 MPLS Router
Router
Core
Site BSC/MSC
VLAN P-Bit Remap (Traffic Classes)
IEEE Recommendation
Ingress Number of Available Traffic Classes
The following
Th f ll i table
t bl shows
h P‐Tags
IEEE definition of traffic 1 2 3 4 5 6 7 8
classes 0 (default) 0 0 0 0 0 1 1 1
It shows the ingress options 1 0 0 0 0 0 0 0 0

for P-Tag VS. egress P-tag 2 0 0 0 1 1 2 2 2
3 0 0 0 1 1 2 3 3
The number of egress
priorities (classes) depend 4 0 1 1 2 2 3 4 4
on the number of assigned 5 0 1 1 2 2 3 4 5
queues
6 0 1 2 3 3 4 5 6
7 0 1 2 3 4 5 6 7
Egress P‐Tag

12
Page 80
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
Acronyms
• 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 81
Associated IEEE Standards
• IEEE 802.3 : Ethernet (Max. frame size = 1518 bytes)
• IEEE 802.3ac : Ethernet (Max. frame size = 1522 bytes)
• IEEE 802.1 d : MAC Bridge first introduced the concept of Filtering

Services in a bridged local network
• IEEE 802.1 q : VLAN Tagging
• IEEE 802.1 p : Priority Tagging / Mapping
• IEEE 802.1ag : OAM (CFM)
Thank You !

14
Page 82
6/13/2010
Ceragon in a Nutshell
Ceragon FibeAir Family
OA&M Service Management Security
Carrier Ethernet Switch TDM Cross Connect
ACM XPIC Ch-STM1/

Gigabit Fast Native2 Radio Multi E1/T1 OC3
Ethernet Ethernet Ethernet + TDM Radio
Terminal
10-500Mbps, 7-56MHz SD/FD Mux
RFU (6-38GHz)
Page 83
1
6/13/2010
RFUs
FibeAir RFU-HP FibeAir RFU-HS FibeAir RFU-P FibeAir RFU-C FibeAir RFU-D
High power Standard power

(e.g. Smaller antennas – reduced cost)
CERAGON MAST - Mobile Architecture

for Service Transport
ISPs
Fixed
Networks Cable
TV
Cellular Backhaul Rural Access
PDH
xDSL IP DSLAM IP/ETH

Subscribers Customer
Network
SDH/SONET RING
PSTN
Page 84
2
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
• Givingg operators
p a single
g p point of contact for all the transport,
p networking
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
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 85
3
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 Ethernet
Radio Radio
User interface User interface
Interfaces Interface
Carrier Ethernet
Switch
Metro/Managed switch mode Smart pipe mode

Extensive Carrier Ethernet feature-set
7 eliminates the need for external switches
IP-10R1 radio capacity - ETSI

7MHz 14MHz
Ethernet Ethernet
ACM # of ACM # of
Point E1s Point E1s
(Mbps) (Mbps)
1 QPSK 4 9.5 – 13.5 1 QPSK 8 20 - 29
2 8 PSK 6 14 – 20 2 8 PSK 12 29 - 41
3 16 QAM 8 19 – 28 3 16 QAM 16 42 - 60
4 32 QAM 10 24 – 34 4 32 QAM 16 49 – 70
5 64 QAM 12 28 – 40 5 64 QAM 16 57 – 82
6 128 QAM 13 32 – 46 6 128 QAM 16 69 - 98
7 256 QAM 16 38 – 54 7 256 QAM 16 81 - 115
8 256 QAM 16 42 – 60 8 256 QAM 16 87 - 125
28MHz 40MHz 56MHz
ACM # of ACM # of ACM # of
Modulation Capacity Modulation Capacity Modulation Capacity
Point E1s Point E1s Point E1s
1 QPSK 16 38 - 54 1 QPSK 16 56 - 80 1 QPSK 16 76 - 109
2 8 PSK 16 53 - 76 2 8 PSK 16 82 - 117 2 8 PSK 16 114 - 163
3 16 QAM 16 77 - 110 3 16 QAM 16 122 - 174 3 16 QAM 16 151 - 217
4 32 QAM 16 103 - 148 4 32 QAM 16 153 - 219 4 32 QAM 16 202 - 288
5 64 QAM 16 127 - 182 5 64 QAM 16 188 - 269 5 64 QAM 16 251 - 358
6 128 QAM 16 156 - 223 6 128 QAM 16 214 - 305 6 128 QAM 16 301 - 430
7 256 QAM 16 167 - 239 7 256 QAM 16 239 - 342 7 256 QAM 16 350 - 501
8 256 QAM 16 183 - 262 8 256 QAM 16 262 - 374 8 256 QAM 16 372 - 531
8
Page 86
4
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 87
5
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
GE
Site
FE/GE RNC
GE
FibeAir
Tail site IP-10 FibeAir NG-SDH
IP-10 NG-SDH MSPP
MSPP
Core
Site
Ethernet services are NG-SDH/SONET MSPP

transported natively node acts as gateway SDH/SONET MW
Ethernet services
over Carrier Ethernet between the Carrier links are used where
are mapped over
based MW radio links. Ethernet and NG- fiber connections not
SDH/SONET
SDH/SONET based available
networks.
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
GE
Site
FE/GE RNC
GE
FibeAir
Tail site IP-10 FibeAir MPLS
IP-10 MPLS Router
Router
Core
Site
Ethernet services are IP/MPLS edge router acts

as gateway between the Both Ethernet and
transported natively
Carrier Ethernet and E1/T1 services are
over Carrier Ethernet High-capacity “IP/MPLS-
based MW radio links. IP/MPLS based networks. mapped over MPLS
aware" Ethernet MW
using pseudo-wires
radio is used where fiber
or routed using IP
connections not available
12
Page 88
6
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 W1 - Highest
Hi h t priority
i it
• VLAN ID
Classify
• IPv4 DSCP/TOS, IPv6 TC Arrivals W2
Scheduling
departures
• Highest priority to BPDUs
• Advanced ingress traffic rate-limiting W3
per CoS/priority
• Flexible scheduling scheme per port
• Strict priority (SP)
W4 – lowest priority
• Weighted Round Robin (WRR)
• Hybrid – any combination of SP & WRR
• Shaping per port
Support differentiated Ethernet services
with SLA assurance
13
IEEE 802.1ag CFM (Connectivity Fault Management)
Page 89
7
6/13/2010
FibeAir IP-10G IDU: A Nodal Solution
Cellular traffic
(TDM)
STM
Rings
FibeAir IP-10G IDU: A Nodal Solution
Page 90
8
6/13/2010
IP-10F IDU
Fans
drawer
Craft 16 x E1s
Terminal External GND
(optional)
(DB9) Alarms RFU
(DB9) interface Power
Protection
5 x FE (N-Type) -48V DC
Interface
(RJ45) Electrical
(RJ45)
Typical Native2 network with IP-10 G & F-Series

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

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

Yes Yes
feature-set including ring protection
# 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

- Yes
STM1/OC3 Mux)
Nodal/XC/SNCP support Yes Yes
Sync unit option Yes Yes
2 x Async V.11/RS232 or
V.11/RS232 User Channel option -
1 x Sync V.11
Outdoor Enclosures – Solution Benefits
Full Outdoor solution:
• 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 92
10
6/13/2010
Higher Spectral-Efficiency
What’s in it for The Operator?
Typical IP10
Microwave Radio Microwave Radio
TWO radio links ONE radio link

Required Capacity
or using
155‐200Mbps
56MHz channel bandwidth 28MHz channel bandwidth
Required Capacity 28MHz 14MHz
70‐100Mbps Channel Bandwidth Channel Bandwidth
The operator saves CAPEX

and free‐up valuable frequency resources
Higher Spectral-Efficiency is not enough…
Radio Type Ant. Diameter Length Modulation Capacity
Typical System Gain 1.80 m 30 Km 16QAM 32 x E1s
Typical System Gain 1.80 m 21 Km 128QAM STM‐1/OC‐3
Typical System Gain 3.00 m 30 Km 128QAM STM‐1/OC‐3
High
HighSystem
SystemGain
Gain 1.80 m 30 km 128QAM STM‐1/OC‐3
Spectral Efficiency
should always be coupled with
System Gain
Page 93
11
6/13/2010
Ceragon’s Management Overview
IP-10 FibeAir
“Tree Topology”
Page 94
12
6/13/2010
Thank You!
Page 95
13
FibeAir ® IP-10 G-Series
Front Panel Description
Front Panel Overview
GUI Example)
Let’s go over the front panel connections of the IP-10 G-Series
We shall explain them one by one, left to right…

1
Page 96
CLI – Serial Connection
DB9 Craft Line Interface (CLI)
Baud: 115200
Data bits: 8
Parity: None
Stop bits: 1
Flow Control: None
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

2
Page 97
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
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

3
Page 98
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)

4
Page 99
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)
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

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

6
Page 101
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
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 Port #1

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

8
Page 103
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
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

9
Page 104
Thank You !

10
Page 105
FibeAir ® IP‐10 G‐Series
Installation
General
If installation requires CFG file upload & download and / or SW file

upload & down -
1. Make sure FTP Server is installed on your PC

2. FTP is configured (RD/WR permissions)
3. Latest SW version is available (FTP root directory)
FTP installation guide

is available at
Training.Ceragon.Com:
see Modules /
Installation

1
Page 106
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 107
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 owner’s 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 108
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)

4
Page 109
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

5
Page 110
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.
Installing Nodal Enclosures in a 19” Rack

6
Page 111
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
Main Enclosure shelves)
Start the installation process

from bottom to top, e.g. – Main
enclosure should be installed
first at the bottom of your rack
space
Step #1:
Install the IP-10 Main enclosure
in the 19 inch rack using 4
screws.

7
Page 112
Step #1:
screws.
Step #2:
Slide down the 2nd extension
enclosure. Male connector
should plug in smoothly into the
Main enclosure.
Step #1:
screws.
Step #2:
should plug in smoothly into the
Main enclosure.
Step #3:
should be plugged in smoothly
into the Main enclosure.

8
Page 113
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 #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

9
Page 114
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.
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

10
Page 115
Installing a Blank Panel IDU in a Shelf
Slide the IP-10 blank panel into the enclosure, and tighten it using 2 screws.
Installing a T-Card into an IDU

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

11
Page 116
Installing a T-Card into an IDU
Insert the IP-10 T-Card panel and tighten it using the 2 side screws.
Grounding the IDU
Single Point Stud
Grounding Wire

12
Page 117
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
• The t d mustt b
be iinstalled
t ll d using
i a UL li t d ring
UL-listed i ttongue tterminal,
i l and
d ttwo star
t
washers for anti-rotation.
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.

13
Page 118
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.
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!

14
Page 119
Power Requirements
Important –
Make sure to use a circuit breaker to protect the circuit from damage by
short or overload.
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.

15
Page 120
Thank You !

16
Page 121
6/16/2010
RFU‐C & Mediation Devices
The Most Comprehensive Portfolio
FibeAir® Family
RFUs Carrier Ethernet EMS & NMS
6-38 GHz IP-10 IP-MAX2 3200T PolyView (NMS)
RFU-C
Multi-Service
RFU-HP IP-10 IP-MAX2 640P
CeraView (EMS)
RFU-P, RFU-SP TDM

1500R/1500P 3200T
2
Page 122
1
6/16/2010
IDU – RFU Compatibility
RFU-C IP-10
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 123
2
6/16/2010
RFU-C direct mount configurations
1+0 direct
5
RFU-C direct mount configurations
1+1 direct
6
Page 124
3
6/16/2010
RFU-C remote mount configurations
1+0 remote
7
RFU-C remote mount configurations
1+1 remote
8
Page 125
4
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 126
5
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 127
6
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
Thank g !
14
Page 128
7
FibeAir ® IP‐10 G‐Series
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

1
Page 129
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 You may use any Serial
• Parity: None Application such as Hyper
• Stop
St bits:
bit 1 Terminal PuTTY,
Terminal, PuTTY TeraTerm
etc…
• Flow Control: None
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

2
Page 130
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

3
Page 131
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

4
Page 132
Connecting IDU to EMS
1. Connect your EMS/NMS to the IDU (port 7) with ETH CAT.5 cable
2. Verify that your PC’s 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 IDU’s 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 IDU’s 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

5
Page 133
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
Thank You !

6
Page 134
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 135
1
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 136
2
4/16/2010
EMS Main View
Graphical “MENU”: Click to configure
EMS Main View
Protection Status Display &

Quick Access Icons
Page 137
3
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
8
Page 138
4
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
9
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 139
5
4/16/2010
Available PM Statistics - Radio
TDM PM in Radio
(allocated E1s)
TDM
(16 E1s)
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
Radio PM:
1. RSL
2. MSE
3. MRMC (ACM)
4. Aggregate
11
Available PM Statistics – Line Interfaces
• STM-1 interface facing customer equipment

g customer equipment
• TDM interfaces facing q p
• End-to-End Trails
12
Page 140
6
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 141
7
4/16/2010
PM – TDM Trails – In Detail

The number of trails in the list is derived from
Report Interval: 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

RMON register / Counter Description
Undersize frames received Frames shorter than 64 bytes
Oversize frames received Frames longer than 1632 bytes

Total frames received with a length of more than 1632 bytes,
Jabber frames received
but with an invalid FCS
Total frames received with a length of less than 64
Fragments frames received
bytes, and an invalid FCS
Rx error frames received Total frames received with Phy‐error
Total frames received with CRC error, not countered in
FCS frames received
"Fragments",
Fragments , "Jabber"
Jabber or "Rx
Rx error"
error counters
Counts good frames that cannot be forwarded due to
In Discard Frames
lack of buffer memory
Counts good frames that were filtered due to egress
In Filtered Frames
switch VLAN policy rules
Pause frames received Number of flow‐control pause frames received
16
Page 142
8
4/16/2010
Troubleshooting with RMON: Filtering Example

Radio port is a Radio port is a
Site A member of VID 100 member of VID 100 Site B
A Tagging T No membership
T A
Untagged Frames Access port with

Tagged with default default VID = 300
VID 100
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 Site B
T T T A
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 143
9
4/16/2010
Troubleshooting with RMON: Discarding Example
Site A Site B
T T T A
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
T T
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 144
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 145
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 146
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 147
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 148
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 149
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 150
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
-99 T [sec]
10 5 10
33
PM – Radio - Aggregate
Aggregated radio traffic analysis
34
Page 151
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 152
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 radio-

Ethernet 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. SFD DA SA VLAN ETH Type Payload + CRC Interframe

/ Length Padding Gap
7 octets 1 octet 6 octets 6 octets 4 octets 2 octets 46‐1500 4 octets 12 octets

octets
Data Rate: min. 64 octets – max. 1522 octets
Physical wire rate: min. 84 octets – max. 1542 octets
38
Page 153
19
4/16/2010
Pre. SFD DA SA VLAN ETH Type Payload + CRC Interframe

/ Length Padding Gap
7 octets 1 octet 6 octets 6 octets 4 octets 2 octets 46‐1500 4 octets 12 octets

octets
Data Rate: min. 64 octets – max. 1522 octets
Physical wire rate: min. 84 octets – max. 1542 octets
In case we use a 64 bytes frame:
Throughput (Data rate) = ~ 77% of physical transmitted rate (64/84=0.77)

Stripped bits = ~ 23% of physical transmitted rate (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 = Capacity = Received frame rate

100 Mbps = 100 Mbps
Utilization = Throughput = 77 = 20 %
Radio Capacity 400
40
Page 154
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
Thank You !
42
Page 155
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 156
1
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 157
2
6/13/2010
Celsius (metric) or
Fahrenheit (Imperial)
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 158
3
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
Page 159
4
6/13/2010
Versions
Let’s explore this example:
• The IDU running SW is displayed in the aidu line and currently it is 3.0.92
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
The h ld all
ll th fil for
the SW files f all
ll the
th
components (IDU + ODU)
You can see here the different files per

ODU type
Page 160
5
6/13/2010
External Alarms – Collapsed Input Alarm Config.
Dry Contact Alarms (DB-9):
5 Inputs
1 Output
External Alarms – Expended Input Alarm Config.
Page 161
6
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 – WeW 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.
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 end’s IP
Page 162
7
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 Port 7, Port 6, Port 5

Number of ports =2 Port 7, Port 6
Number of ports =1 Port 7
Number of ports =0 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.
Page 163
8
6/13/2010
Management – Port Properties
These parameters
allow you setting the
managementt capacity it
and port properties
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)
Page 164
9
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.
Licensing – Demo License Enabled
Demo License allows you full
evaluation of the IDU
functionality, features and
capacities
Page 165
10
6/13/2010
NTP Client Properties

• Enable / Disable
• Type NTP Server IP address
• Expect IDU to lock on NTP Server’s 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 element’s 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>
NTP Properties
Page 166
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 unit’s
clock.
IP Table
Here you can manually set your neighbor’s network properties
Page 167
12
6/13/2010
SNMP
• V1
• V3
• No security
• Authentication
• Authentication privacy
• SHA
• MD5
• No Authentication
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 All ODU Enabled
Page 168
13
6/13/2010
Thank You !
27
Page 169
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 170
1
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:
Allowed Egress
Type VLANs Allowed Ingress Frames
Frames
Only Untagged frames

Specific VLAN should be
Access (or Tagged with VID=0 – Untagged frames
assigned to access the port
"Priority Tagged“ )
A range of VLANs should be Tagged frames

Trunk Only Tagged frames
assigned to access the Port
Page 171
2
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 Allowed Egress

Type VLANs
Frames Frames
Specific S-VLAN should be Untagged frames, or Untagged or C-tag

Customer-
assigned to "Customer- frames with C-tag (ether-type= 0x8100)
Network
Network" port (ether-type=0x8100). frames.
Configurable S-tag. Configurable S-tag.

A range of S-VLANs, or (ether-type) (ether-type)
Provider- "all" S-VLANs should be 0x88a8 0x88a8
Network assigned to "Provider- 0x8100 0x8100
Network" port 0x9100 0x9100
0x9200 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 172
3
3/7/2010
Single Pipe
Configuration
Single Pipe Configuration
Untagged
VID 4 45
VID 51 IP-10 Switch
VID 100
Port 1: GbE (Optical or Electrical) Port 8 (Radio)

Port 3: FE (RJ45)
Page 173
4
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
Page 174
5
3/7/2010
Managed Mode
Configuration
Configuration – Managed Mode
Let’s use this diagram as an example -
Port #2 as Trunk (VID 200)
IDU-B
IDU-A
Radios as Trunk by
default Port #2 as Trunk
Port #3 as Trunk
(VID 200, VID 300)
(VID 300)
Page 175
6
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)
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
Page 176
7
3/7/2010
2
1
4

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

– Common Applications
Radio = Trunk Port
IP-10
Trunk Port
Multiple L2
streams, each Traffic
identified with
unique VID Generator
Trunk Port
Thank You !
18
Page 178
9
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 179
1
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 180
2
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
Access Port:Untagged frame
Page 181
3
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
Access Port: Untagged frame

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 SA VLAN TAG = 10 Type Payload FCS
DA SA Type Payload FCS DA SA VLAN TAG = 33 Type Payload FCS

Access Ports: Untagged frames
Page 182
4
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 SA Type Payload FCS DA SA VLAN TAG = 33 Type Payload FCS

Access ports: Untagged frames

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
SA VLAN
DA Untagged TAG = 33
frames Type Payload FCS
Page 183
5
4/17/2010
Trunk & Access – Extracting frames out of a Trunk
• A certain VLAN can be extracted out of a Trunk via Access port assigned
with specific VLAN membership (Default VID)

Port #5: Access
Port #8: Trunk

Port #2:
Trunk DA SA VLAN TAG = 33 Type Payload FCS
SA
DA Untagged VLAN TAG = 33
frames Type Payload 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…)
Page 184
6
4/17/2010
EMS Trunk Configuration
2
1
3
Thank You !
14
Page 185
7
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 186
1
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 Allowed Egress

Type VLANs
Frames Frames
Specific S-VLAN should be Untagged frames, or Untagged or C-tag

Customer-
assigned to "Customer- frames with C-tag (ether-type= 0x8100)
Network
Network" port (ether-type=0x8100). frames.
Configurable S-tag. Configurable S-tag.

A range of S-VLANs, or (ether-type) (ether-type)
Provider- "all" S-VLANs should be 0x88a8 0x88a8
Network assigned to "Provider- 0x8100 0x8100
Network" port 0x9100 0x9100
0x9200 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
C-VLAN 100
S-VLAN 9 C-VLAN 101
Radio Network 1 C-VLAN 102
C-VLAN 103
Ports C-VLAN 100
(PN) S-VLAN 8
Network 2
C-VLAN 101
C-VLAN 102
C-VLAN 103
Network #2
Page 187
2
4/21/2010
Simplified Flow
IP-10
S-VLAN 1000
S-VLAN 222
S-VLAN 1000
S-VLAN 222
PN CN CN
Radio Port
ISP / BTS #1 ISP / BTS #2
C-VLAN 100 C-VLANs unknown

C-VLAN 101
C-VLAN 102
CN-PN-PN-CN
C-VLAN 100
S-VLAN 9 C-VLAN 101
Radio BTS 2 C-VLAN 102
C-VLAN 103
BTS #2:
C-VLAN 100
Ports C-VLAN 100
C-VLAN 101 (PN) S-VLAN 8
BTS 1
C-VLAN 101
C-VLAN 102
C-VLAN 102 C-VLAN 103
C-VLAN 103
CN
CN
CN
BTS #1:
C-VLAN 100 CN
C-VLAN 101
C-VLAN 102
C-VLAN 103
Page 188
3
4/21/2010
CN-PN-PN-PN
C-VLAN 100
S-VLAN 9 C-VLAN 101
Radio BTS 2 C-VLAN 102
C-VLAN 103
BTS #2:
C-VLAN 100
Ports C-VLAN 100
C-VLAN 101 (PN) S-VLAN 8
BTS 1
C-VLAN 101
C-VLAN 102
C-VLAN 102 C-VLAN 103
C-VLAN 103
CN
CN
PN
BTS #1:
C-VLAN 100
C-VLAN 101
Customer Network Provider Network
C-VLAN 102
C-VLAN 103
Switch Mode Configuration
1. Set mode to Metro (requires reset)
2. Add the S-VLAN ID (set & apply)
Page 189
4
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
1
3
4
5
Page 190
5
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
1
3
6
5
Page 191
6
4/21/2010
PN Port Configuration – Setting the S-Tag
• 0x88A8
• 0x8100
7 • 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.
Page 192
7
4/21/2010
Thank You !
15
Page 193
8
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
Page 194
1
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).
Page 195
2
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 196
3
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 197
4
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)
Page 198
5
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:
Out of band Management (2)
Page 199
6
3/7/2010
Configuration
Example
RSTP Example (1)

Site #1 Site #2
3 4 5 6 7 3 4 5 6 7
Pipe (slot #2) Pipe (slot #3)
3 4 5 6 7 3 4 5 6 7
MNG (slot #1) Pipe (slot #2)
3 4 5 6 7
MNG (slot #1)
X Site #3
3 4 5 6 7
Pipe (slot #2)
3 4 5 6 7
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
Page 200
7
3/7/2010
RSTP Example (2)

Site #1 Site #2
3 4 5 6 7 3 4 5 6 7
3 4 5 6 7 3 4 5 6 7
3 4 5 6 7
MNG (slot #1)
X Site #3
3 4 5 6 7
Pipe (slot #2)
3 4 5 6 7
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
RSTP Example (3)

Site #1 Site #2
3 4 5 6 7 3 4 5 6 7
3 4 5 6 7 3 4 5 6 7
3 4 5 6 7
MNG (slot #1)
Site #3
3 4 5 6 7
Pipe (slot #2)
3 4 5 6 7
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)
Page 201
8
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)
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
Page 202
9
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
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.
Page 203
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).
Thank You !
22
Page 204
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 205
1
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
L2 ETH
between TDM E1/T1,SDH VCs and
Radio channels ADM SW
L2 ETH Switch:
• 802.1p/q
• P-Bit remap MW
• Policers
• Shaping Radio
• Scheduler
• IPv4 / IPv6 Classification
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
L2 ETH
stands for… ADM SW
MW
Radio
Page 206
2
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 207
3
6/1/2010
Why do we need QoS? (2)

Mobile operators focus on reducing costs:
• Mobile Broadband growth requires Backhaul expansions, hence:

• Operators
p are stretching
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

Business center Backhaul Network
GE
WiMAX / 4G / LTE
Cellular site
WiMAX
STM-1 / OC-3
Ceragon Ceragon
Hub / Aggregation site
TDM
E1/T1
2G/3G base station
Fundamental Fact
Static
Dynamic WWW
WWW
Multimedia
emails
FTP
Not all traffic is the same!

Skype
So why treated equally?...
Who’s first?
Page 208
4
6/1/2010
Traffic Engineering as a Solution

Your 1st assignment is identifying needs & solutions:
Static
Dynamic WWW
What is the BW requirement per service ? WWW
• Video requires more than voice Multimedia
• Data
D t requires
i lless th
than video
id
• FTP requires more than emails…
emails
What is the delay sensitivity of each service? FTP
• 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
QoS in IP-10
Page 209
5
6/1/2010
IP-10G L2 ETH Switch Ports
The IP-10G’s L2 Switch has 8 ports:
• Port #1 GbE (Opt. / Elec.)

• Port #2 GbE ((Opt.
p / Elec.))
• Port #3 to port #7 FE
• Port #8 (Radio port)
QoS Process
Q4 Q4
25
10 50
Q1 Q3
Q2
Rate Limit Queuing Scheduling Shaping
Ingress Port Egress Port (s)
Page 210
6
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 Egress
port port
Customer Provider
Network Network
Egress Ingress
port port
Customer Provider
Network Network
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
Port 1-7* P t 1-7*

Port 1 7*
Radio Radio
Egress
Ingress
* Ports 7, 6 & 5 can be used as management or data

Page 211
7
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. 100Mbps
Rate
25 Discard
Max. Allowed
10 50 R
Rate
t
Pass
Actual
Customer
Traffic
Time
Example: Policer assigned to FE interface
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 Low
Page 212
8
6/1/2010
Using Queuing
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
Q3
Q4 Q3
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
Q2 Q1 Q2
Pro: no “queue starvation”
Q1 Low Con: no prioritization
Page 213
9
6/1/2010
Scheduling (2)
Weighted Round-Robin:
Emptying cycle is configurable – every queue can be given specific weight
Q4 High
Q4 Q4
Q3
Q3 Q4 Q4 Q1 Q2 Q3 Q4 Q4
Q1 Q3
Q2
Q2
Q1 Low
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
Q3 Q1 Q3
Q3 Q4 Q4 Q1 Q2 Q3 Q4 Q4
Q2 Q2
Pro: Optimized Prioritization
Q1 Low Con: “Queue starvation”
Page 214
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 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.
Page 215
11
6/1/2010
Possible Scenarios
No need for
f
Ingress Queuing
Port 1-7* Port 1-7*
Radio Radio
Ingress Radio Egress No need

Queuing Scheduler = g
for Egress
Strict Priority Scheduler
Possible Scenarios
Ingress Queuing is
required in port 8
Port 1-7* Port 1-7*
Radio Radio
Ingress Radio Egress Egress

Queuing Scheduler = Scheduler
Round Robin is required
Page 216
12
6/1/2010
Thank You !
25
Page 217
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
Page 218
1
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
L2 ETH
• Advanced ingress traffic policing /
rate-limiting per port/CoS
ADM SW
• Flexible scheduling:
Strict Priority, WRR or HRR
• Traffic shaping
• 802.3x flow control (for loss-less) operation

MW
Radio
Page 219
2
3/7/2010
IP-10G L2 ETH Switch Ports
The IP-10G’s 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 220
3
3/7/2010
Step #2: Configure Switch Ports

• Configure Port Type: Access / Trunk
• Configure Port Membership
Step #3: Configure QoS per Port
Page 221
4
3/7/2010
Process Review
Policer per port
25
10 50
Rate Limit
Page 222
5
3/7/2010
3 classifiers to audit & queue Ingress Traffic
Queuing
Egress port Scheduler
Q4 Q4
Q1 Q3
Q2
Scheduling
Page 223
6
3/7/2010
Egress Port Shaper
Shaping
Basic Configurations
Page 224
7
3/7/2010
1. Ingress Rate Limiting
Let’s 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
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
Page 225
8
3/7/2010
1. Attaching a Policer to a port

To attach a Policer to a port simply type the Policer name
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
Page 226
9
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 -
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 .
Page 227
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
4. Queuing Ingress Packets according ToS / DSCP
Click on the “IP Pbits to Queue”

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

Next, select “IP-TOS ” as the 3rd criteria
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
Page 229
12
3/7/2010
6. Queuing Ingress frames according to VLAN ID

Click on the “VLAN ID to Queue” Link to configure the table
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
Page 230
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
Thank You !
28
Page 231
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
Page 232
1
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
P-Bit Service P-Bit* Service
0-2 Video 0-5 Best
3–4 Data Effort
5–6 MNG 6 MNG

7 Voice 7 Voice
L2 Switch
Customer (IP-10) Provider
network network
Configuring the Mapping Table

Click on the “VLAN Pbits Remap Table” link to configure relevant settings
Page 233
2
3/7/2010
Queuing without Re-Mapping
Ingress
Tagged
frame Queuing
Ingress Egress Egress
VID P-bit according VID P-bit
Rate Limit Scheduler Shaper
to classifier
Skipping to next classifier with Re-Map

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

Re-Map
Table
Ingress
Tagged
frame
Queuing
Ingress Egress Egress
VID P-bit according VID P-bit*
Rate Limit Scheduler Shaper
to classifier
Conditional Classification
Page 235
4
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 L3 IP Header
Page 236
5
3/7/2010
Using more than a single Classifier
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…
Using more than a single Classifier
Audit VID : if VID = 100 than apply “High Service” otherwise -

if VID = 200 than apply “Low Service”
Otherwise –
2nd criteria: VLAN ID
100 Highest
If ingress VID does not qualify (100 or 200)
100 or 200 100 Highest
then skip to - 100 Highest
100 Highest
200 Lowest
Audit VLAN P-bits Ingress
VID = ?
frames 3rd criteria: P-Tag
7 Highest
6
3
Different than 2
100 or 200
0 Lowest
Page 237
6
3/7/2010
Thank You !
13
Page 238
7
6/10/2010
FibeAir ®IP‐10
Commissioning the Radio Link
Radio Link Common Attributes

TSL RSL
IDU ODU )) ) 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 239 1
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 240 2
6/10/2010
LINK ID – Antenna Alignment Process

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 241 3
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 242 4
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 Monitored RSL
ATPC Radio Radio Radio

module Transceiver Receiver ‐ Ref. RSL
Feedback Signal RSL

Radio
Quality required
Receiver change
Site A
Check
Site B
ATPC OFF = High Power Transmission
ATPC: Disabled ATPC: Disabled
Max. TSL: 10 dBm Max. TSL: 10 dBm
Monitored TSL: 10 dBm Monitored TSL: 8 dBm

Monitored RSL: -53 dBm Monitored RSL: -56 dBm

Feedback Signal RSL

Radio
Quality required
Receiver change
Check
Site A Site B
Page 243 5
6/10/2010
ATPC ON =
Reduced Power, cost & long-term maintenance
ATPC: Enabled ATPC: Enabled

Ref. RSL: -65
65 dBm Ref RSL:
Ref. - 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)

Feedback Signal RSL

Radio
Quality required
Receiver change
Site A
Check
Site B
MRMC Scripts
Page 244 6
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.
MRMC – Multi Rate Multi Coding

Each ACM script has 8 profiles. Profile Modulation
0 QPSK
The radio capacity will be dictated by the
channel BW ((see next slide)) 1 8QAM
2 16QAM
The lower the modulation the less sensitive
3 32QAM
the receiver is:
4 64QAM
• More system gain 5 128QAM
• Bigger fade margin
6 256QAM (high FEC)
At lower modulation orders the radio link will 7 256QAM (low FEC)
tolerate lower RSL
S levels. For example:
With 16QAM the radio will drop at (-78dBm)

whereas with 8QAM the radio will drop at
(-82dBm)
Page 245 7
6/10/2010
MRMC Adaptive TX Power
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.
Page 246 8
6/10/2010
MRMC Adaptive Power = OFF
256QAM @ Monitored TSL = 18 dBm (Max.)
Signal Degradation
= Lower bit/symbol
16QAM @ MAX. TSL = 18 dBm
MRMC Adaptive Power = ON
256QAM @ Monitored TSL = 18 dBm(Max.)
Signal Degradation
= Lower bit/symbol
16QAM @ Monitored TSL = 24 dBm
Page 247 9
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
RFU-C h ld h i 2.01
have version 2 01 (or
( hi h ) ffor proper ffunctionality
higher) ti lit off
“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
Configuration
Page 248 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
Radio Settings – Local Radio
Enable on both IDUs to get maximum

throughput (500Mbps @ 56MHz)
Page 249 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
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
Page 250 12
6/10/2010
Radio Thresholds
These settings determine the sensitivity / tolerance for triggering:
• 1+1 HSB switchover

• Ethernet Shutdown
• PM generated alarms
MRMC Configuration
We shall review this page using the following slides:
Page 251 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
MRMC – Reading current capacity
Page 252 14
6/10/2010
Thank You !
29
Page 253 15
3/7/2010
FibeAir® IP-10 G-Series

Configuring Interfaces
Agenda
• Ethernet Interfaces
• TDM Interfaces
• AIS Detection
• AIS Signaling (STM-1)
• STM-1 Interface
• Auxiliary Channels
• Wayside Channel (Various Configurations)
Page 254 1
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 8 Radio According to Disabled / Traffic Disabled / Traffic

(N Type) Licensed fq.
Ethernet Ports Configuration
Page 255 2
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 256 3
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 257 4
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
Page 258 5
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 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.
Page 259 6
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.
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.
Page 260 7
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.

OOB MNG in a 1+1 standalone IDUs (Y-Splitter)
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".
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.
Page 261 8
3/7/2010
OOB MNG in a 1+1 standalone IDUs (P. Panel)
Thank You !
18
Page 262 9
3/7/2010
FibeAir® IP-10 G-Series

XC / SNCP / Nodal Solution
Introduction
Page 263 1
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 264 2
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
• 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
• Additional “Nodal enclosures” and units can be added in the field as required without
affecting traffic
Front Nodal enclosure
Rear
Page 265 3
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 266 4
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
Native2
M Main unit 1+1 HSB
M
E
Expansion unit M
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 Native2
• Single 2+0/XPIC link 1+0
Native2
1+0
Integrated Ethernet Switching E
E
Integrated TDM cross-connect E Native2
E 2+0/XPIC
M Main unit
M
E
Expansion unit M Native2
1+1 HSB
Page 267 5
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
Page 268 6
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)
Identify Trail interfaces prior to configuration

Note that Trail configuration is Bi-Directional !
Trail starts here:

For SNCP we shall
Trail traverses through here: IP-10 need to define 3
We shall need to define 2 interfaces
interfaces
IP-10 Bypass
site Protected Trail
(Automatic)
IP-10
Trail starts here:
For SNCP we shall
need to define 3
Radio Link interfaces
Page 269 7
3/7/2010
Pay attention to the order of configuration: 1
2 IP-10
The Trail Start/End points should
be configured first (interface #1) 3
IP-10 Bypass
site
Interfaces #2 and #3 can be
configured in a random order
Protected Trail
(Automatic)
2 3
IP-10
Standalone non-protected Trail Configuration
Page 270 8
3/7/2010
Step #1: Access Trail Page
Click on the Add button
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.
Page 271 9
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
Step #4: Configure Trail Attributes

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

If your settings are correct, trail alarms should disappear, trail path is ready to be tested
SNCP Trail Configuration in a Node
Page 273 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
SNCP Trail in Nodal Architecture
PDH interface
IP-10
Bypass
Node IP-10
IP-10
SDH interface
Page 274 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
Bypass Node
PDH interface
Radio CH #48
IP-10
Bypass IP-10
Node
Radio CH #1
IP-10
SDH interface
Page 275 13
3/7/2010
3rd Node
PDH interface
Radio CH #48
IP-10
Bypass IP-10
site Radio CH #26
IP-10
SDH interface
Thank You !
28
Page 276 14
4/30/2010
FibeAir ® IP-10 Series

Automatic State Propagation
Agenda
• Introduction
• Interfacing IP-10 with external devices
• Configuration VS
VS. Functionality
• Dead Lock Example
• ASP in Managed / Metro Mode
Page 277
1
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
Need to find
alternative path
Interfacing IP-10 with external devices
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 278
2
4/30/2010
Interfacing IP-10 with external devices
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 B Site A
TX RX
RX TX
1. GbE FO breaks down or disconnects at the ingress port of Site A
Page 279
3
4/30/2010

Site B Site A
TX RX LOC
RX TX

2. LOC alarm is raised

Site B Site A
TX RX LOC
RX X TX

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

Site B Site A
TX RX LOC
LOC
RX X TX

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

Site B Site A
TX LOC
X RX
LOC
RX X 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
Page 281
5
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. ASP Enabled
2. ACM profile threshold
3. Excessive BER enabled
Local Criteria:
• LOC (GbE)
• Radio LOF
• LINK ID Mismatch
• Excessive BER
• ACM profile is below threshold
1 8 8 1
Actions: Actions:
Mute port 1 (GbE ‐SFP) Mute port 1 (GbE ‐SFP)
Page 282
6
4/30/2010

Using Electrical GbE (RJ45)
1. ASP Enabled
LLocall C
Criteria:
it i
• Radio LOF
• Excessive BER
8 8
Actions: Actions:
Shut down Elec. Shut down Elec.
port port

Using Electrical GbE (RJ45) have identical settings:
1. ASP Enabled
Local GbE Criteria: 8 8

• LOC
Portt is
P i logically
l i ll closed
l dbbutt nott
shut down
LOC will not trigger port shut Remote LOC will not trigger
down (it will not be possible to port shut down (it will not be
enable the port when LOC is possible to enable the port
cleared) when LOC is cleared)
Page 283
7
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.
Page 284
8
4/30/2010
Managed / Metro - Propagation Criteria

1. ASP Enabled
Local Criteria:
• Radio LOF
• Excessive BER
8 8
Actions:
Shut down Radio
Managed / Metro - Propagation Criteria

1. ASP Enabled
Local criteria: 8 8
• GbE LOC Actions:
No action taken
Shut down Radio
Page 285
9
4/30/2010
Thank You !
19
Page 286
10
Link Aggregation
(IEEE 802.3ad)
Agenda
Agenda
Definition
Advantages
Feature Review
Applications
Load Balance Example

1
Page 287
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
• The Link Aggregation Group is consisting of N parallel N

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 288
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 user’s policy – improved reliability

3
Page 289
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 290
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 Public
Network Network
Feature Review

5
Page 291
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.
LAG Distribution: Simple XOR

We can easily demo balanced traffic distribution using the XOR method –
(Configure your Traffic Generator with the following MACs)
Stream MAC (HEX) Last 3 bits XOR result Assigned LAG Port
SA ‐> 00:20:8f:0a:02:01 001
000 (0) Link #1
‐ > DA 00:20:8f:0a:01:01 001
SA ‐> 00:20:8f:0a:02:02 010
‐ > DA 00:20:8f:0a:01:02 010
000 (0) Link #1
SA ‐> 00:20:8f:0a:02:03 011
‐ > DA 00:20:8f:0a:01:03 011
000 (0) Link #1
SA ‐>> 00:20:8f:0b:e1:03 011
‐ > DA
001 (1) Link #2
00:20:8f:0a:e1:04 010
SA ‐> 00:20:8f:0b:e1:03 010
‐ > DA 00:20:8f:0a:e1:01 101
010 (2) Link #3
SA ‐> 00:20:8f:0b:e1:07 111
‐ > DA 00:20:8f:0a:e1:04 100
011 (3) Link #4

6
Page 292
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

7
Page 293
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
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
IP-10 IDU IP-10 IDU

Radio port (port 8) may be in a LAG with the GBE ports only
GbE FE GbE FE
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
IP-10 IDU IP-10 IDU

8
Page 294
Applications
pp

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

(Nodal) Site implemented with LAG
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
GbE
1 2 3 4 5 6 7 8 PHY
Multiple FE
ports as a LAG
GbE
PHY Port #2 and Radio
form a LAG

9
Page 295
1+0 LAG
1 2 3 4 5 6 7 8
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
1+1 HSB W/O LAG 1+1 HSB or

2+0 “Multi-Radio”
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
3rd party
No need for LAG
Switch or Router
• 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)

10
Page 296
1+1 HSB With LAG
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
3rd party No need for LAG

Switch or Router 1+1 HSB or
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
1+1 HSB With dual GbE + LAG

1+1 HSB or
Static LAG
Static LAG 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
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

11
Page 297
1+1 HSB With dual GbE + LAG (cont.)
1+1 HSB or
Static LAG
Static LAG 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
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!
Load Balance Example

p

12
Page 298
Load balance example
1 2 3 4 5 6 7 8 50%
P
1 2 3 4 5 6 7 8
S
GbE 50%
PHY
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)

2) Alarm is
propagated
3) Port 2 is 1) Link
shut down Degradation
1 2 3 4 5 6 7 8
P
1 2 3 4 5 6 7 8
S
GbE 4) Port 2 is out X

50% 100%
PHY of the LAG
5) Radio 1
takes 100%
1) Radio #2 encounters a signal degradation
2) Since ASP is
Si i enabled,
bl d the
th alarm
l iis propagated
t d tto portt #2
3) IDU #1 detects the alarms and shuts down port #2
4) Port #2 is not part of the LAG
5) Radio #1 takes full control (100%) of traffic
Enable Automatic State Propagation on both IDUs

13
Page 299
Shut down
64QAM 256QAM
1 2 3 4 5 6 7 8
P
1 2 3 4 5 6 7 8
S
GbE X
50% 100%
PHY
100%
To improve system resiliency, Automatic State Propagation can shut down the
LAG interface when ACM degrades below a pre-determined profile.
Thank You !

14
Page 300
Link Aggregation Group Configuration
(IEEE 802.3ad)
Agenda
Agenda
Guidelines Review
EMS Configuration
Using PM (RMON)

1
Page 301
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 302
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
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
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
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
IP-10 IDU IP-10 IDU

3
Page 303
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
 “allow all” is considered a different value (must be equal in all ports)
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 304
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.
EMS Configuration
g

5
Page 305
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)
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

6
Page 306
Example
1. We generate a data stream through GbE SFP port 1 of both lower IDUs
2. Port 2 & 8 form a LAG on both sites
3. Upper IDUs are set as Pipe
4
4. Traffic will be evenly distributed among the radio ports
5. Assign Radio license > Line rate
6. Clear all PM data
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
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
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
Data stream

7
Page 307
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)
LAG pport 2 does not

transmit data now
Port 8 takes 100% of data

transmission

8
Page 308
Thank You !

9
Page 309
8/10/2010
FibeAir ® IP‐10
HSB / 1+1 Protection
Agenda
Active VS. Standby (Mate)
Introduction to External Protection
Introduction to Shelf Protection
Guidelines
EMS GUI Configuration
External Protection Process: 1+1 from scratch
External Protection Process: Upgrading 1+0 to 1+1
Troubleshooting
Everybody needs Protection
Page 310 1
8/10/2010
Active VS. Standby (Mate)

f1 - high f1 - low
Active Active
Coupler Coupler
Mate Mate
f1 - high f1 - low
1. ETH Cross Cable (Protection Cable) is Active

connecting ports 3 of both IDUs (shown in
red)
2. Antennas are replaced in lab with testing kits

(RF to WG adaptors, attenuators and SMA
cables)
3. Protection Panels may be in use to improve

E1 wiring to DDF (right diagram) Mate
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 IDU
at one site
f1 - low
f1 - high
Page 311 2
8/10/2010
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
IDU
In this example Protection 5
is configured in every pair 4
of IDUs (slots) IDU
3
2
IDU
1
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)
Page 312 3
8/10/2010
Setup Example (Standalone IDUs)
EMS GUI
Select “Enable” and then click “Apply”
The IDU will block management for 60

seconds to allow setting up the correct mode
(Active or STBY)
This action is not traffic effective.
Page 313 4
8/10/2010
EMS GUI
Protection
mode status
When 2nd IDU is

properly
configured and
connected, IP
and MAC are
displayed here
EMS GUI
Click here to check

communication
with STBY unit
Page 314 5
8/10/2010
EMS GUI
To force a switchover
regardless to 2nd IDU Admin State Lock
qualifying status –
change to “ON” and click
“Apply”
EMS GUI
To request a switchover –
click here.
If 2nd IDU (Mate) does

not qualify to Active
state, request is ignored.
Page 315 6
8/10/2010
EMS GUI
Click here to copy the configuration from

Active to Mate
Please note –
The following parameters are not copied :
• MNG mode (In‐Band / OOB)

• In‐Band VLAN
• Switch mode
• license
Configuring external 1+1 from scratch
Page 316 7
8/10/2010
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“.
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. I t ll 2ndd IDU iin each

6 Install h site
it (no need to configure it)
ODU ODU
ODU ODU
Page 317 8
8/10/2010
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
PC
ODU ODU
11. Verify Active IDU shows Mate’s 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. Unlock protection on Active IDUs
17. Initiate Manual Switchover / Forced Switchover: verify traffic is OK.
Page 318 9
8/10/2010
Upgrading (1+0) to (1+1)
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 Active’s 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
Standby Link (not connected)

ODU ODU
Page 319 10
8/10/2010
2. Enable Protection on Active IDUs (management will be lost for 60 sec)
3 Lock
3. L kPProtection
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)
ODU ODU
ODU ODU
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
Page 320 11
8/10/2010
9. Verify Active IDU shows Mate’s IP address
10. Verify there are no “Configuration Mismatch” alarms
11. Verify there are no “Mate Communication failures”
12. Complete system setup by configuring Active IDU
13. In Active IDU: click “Copy to Mate” and verify Mate is restarting
14. Unlock protection on Active IDUs
15. Initiate Manual Switchover / Forced Switchover: verify traffic is OK.
Troubleshooting Protection
Common issues followed by CLI commands
Page 321 12
8/10/2010
Troubleshooting
Alarm / Error Probable Cause / Workaround
1. Protection cable is not connected
2. ETH straight cable is connected instead of
Protection LED is on (RED) cross‐cable
cross cable
3. One of the 2 IDUs is not configured in
Protection
Check CFG of both IDUs: HW, SW, switch mode,
Current Alarms show “Configuration
management mode, In Band VID
Mismatch” alarm
Initiate “Copy to Mate” in Active IDUs
This is normal behavior, Mate cannot be
“I cannot PING the STBY unit….”
accessed directly, only via Active IDU
“Main IDU does not respond to Use CLI commands to verify this IDU is in STBY
PING” mode, if so, use CLI to recover IDU
Check the current alarms of STBY IDU
Current Alarms shows “Mate Comm. Report back to Ceragon Support
Failure” alarm Replace STBY unit
Replace Active unit
Troubleshooting – Useful CLI Commands
General commands:
lsp prints executable commands in current directory

ls prints available child
child-directories
directories
cls 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
Page 322 13
8/10/2010
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 <on/off>
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
Page 323 14
8/10/2010
Thank You !
29
Page 324 15
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 325
1
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 Connection-Oriented

Page 326
2
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
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 327
3
Setup Review (MAIDs):
Domain 1 Services:
D1S1:
MEP 1 to MEP 2, Level 3, VLAN 1000
1
D1S2:
MEP 3 to MEP 4, Level 3, VLAN 2000
3
4
Domain 2 Services:
D2S2: 5
MEP 5 to MEP 6, Level 2, VLAN 1000 6
MEP
MIP
CFM Configuration Flow:
Create VLANs in Switch DB

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

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

Make sure you follow the same syntax…

Page 328
4
Configuration
Switch Configuration – Mode and VIDs

Page 329
5
Switch Configuration – Port Configuration
Creating MAIDs
Click on the Add button to add domains
(use the setup diagram as a reference)
You will need to specify:
1. Domain Name
2. Level (1 to 7)
3. Association Name
4. VLAN ID

Page 330
6
Creating MAIDs
Create the domains as depicted in the setup diagram on both IDUs
Settings must be unique and identical
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

Page 331
7
Defining MEPs
Click on the ADD button to add a local MEP on both IDUs
Continue to next slide to observe how…
Defining MEPs
Port #3
MEP ID: 1
Port #3
MEP ID: 2

Page 332
8
Remote MEPs not defined yet…
RIGHT IP-10
Enable CCM on both IDUs

LEFT IP-10
RIGHT IP-10

Page 333
9
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
Creating Remote MEPs
Click on the Add button to add a remote MEP on every IDU

Page 334
10
Creating Remote MEPs
Port #3
Local MEP ID: 1
Remote MEP: 2
Port #3
Local MEP ID: 2
Remote MEP: 1
Service #1 (D1S1) is ready for monitoring!
Click on the “PING” button to check connectivity to Remote interface

(results on next slide)

Page 335
11
PING results (MEP1 to MEP2)
“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

Page 336
12
“D1S2” – Creating another service
Using the MAID list, add the new service on both IDUs:
MEP 3
MEP 4
“D1S2” – Creating Local MEPs

Please note - Radio port MEP should be defined as a Downstream MEP
MEP 3
MEP 4

Page 337
13
“D1S2” – Enable CCM on both IDUs
MEP 3
MEP 4
“D1S2” – Add Remote MEPs on both IDUs
MEP 3
MEP 4

Page 338
14
“D1S2” Service is now ready for monitoring
“D2S2” – another service on another Domain
“D2S2”
5
6

Page 339
15
“D2S2” – another service on another Domain
Adding Local MEPs
Local MEP 5
Remote MEP 6
Local MEP 6
Remote MEP 5

Page 340
16
Enabling CCMs…Adding Remote MEPs…
Once you complete these tasks, your 3rd service is ready for monitoring
Adding MIPs to enhance Monitoring

The MIPs can be regarded as
Service-free test-points
MIPs provide more segments

regardless of VLANs and
Services 1
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

Page 341
17
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)
Please make a note of the Radio MAC address of each IDU – we shall need it later

Page 342
18
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

Manual PING | Manual Link Trace | Automatic Link Trace

Page 343
19
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
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

Page 344
20
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)
Automatic Linktrace
To enable Auto Linktrace – select the checkbox next to the target Remote MEP
and then click “ADD SELECTED”

Page 345
21
Automatic Linktrace
Click “Linktrace SELECTED”
Thank You !
training.ceragon.com
44

Page 346
22
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 347
1
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 348
2
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 349
3
3/7/2010
IF Loopback – Analysis using Event Log

Let’s 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 350
4
3/7/2010
PDH Line LB towards Line (Near End)
Use this feature to evaluate connection to customer’s patch-panel
Alarm is displayed in CAS:
and in Event Log:
PDH Line LB towards Radio (FE)
LB towards the radio
Tester
Page 351
5
3/7/2010
PDH Line LB towards Radio – Event Log Analysis

Let’s 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…..
SDH Line LB towards System

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

Towards Line – signal (trail) is looped back to
customer interface
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
Page 353
7
3/7/2010
Thank You !
15
Page 354
8
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. Configuration File
2. Unit Information File
3. FTP Server
Page 355
1
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 356
2
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 357
3
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
Configure your FTP Server Properties
2
Page 358
4
3/7/2010
Upload /
Download using
standalone IP-10G
Uploading the CFG File (IP-10G to Server)
Click “Create Archive” to

allow the IP-10G zipping
all parameters into one file
Page 359
5
3/7/2010
Wait till task is

successfully completed
Next step:
Click “Upload Archive” to allow
the IP-10G transferring the
zipped file to your server
Page 360
6
3/7/2010
Wait till task is successfully

completed
Check your FTP Root Directory
This is your copy of

the configuration file
You may place it now

in the dedicated folder
(Configuration Files)
Page 361
7
3/7/2010
Follow the same steps to upload the Unit Information file:
1 2
Check your FTP Root Directory
This is a copy of your Unit Information file
Page 362
8
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 2
Upload /
Download in
a shelf
Page 363
9
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
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
Page 364
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
Shelf Backup: Download from Server to IP-10G
To download a file to a
certain slot, select the
unit number and click
this button
Page 365
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
Checking Backup History & Status
Click here to see the

backup history
Page 366
12
3/7/2010
Checking Backup History & Status
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)
Page 367
13
3/7/2010
Thank You !
27
Page 368
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 369
1
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 370
2
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 371
3
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 372
4
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
Page 373
5
4/21/2010
Download completed – Upgrade delayed

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

Page 374
6
4/21/2010
SW Upgrade in a
shelf (Node)
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
Page 375
7
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

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
Page 376
8
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
Rollback
VS. Downgrade
Page 377
9
4/21/2010
Rollback
1 2
Upgrade #1 Upgrade #2
2.8.25 2.8.31 2.8.35

2.8.32
Rollback 4 3
Downgrade
Rollback does not revert previous “Downgrade” operation !
It rolls back IDU version 1 step back (prior to last Upgrade)
Thank You !
20
Page 378
10
3/7/2010

EMS Security Configuration
Agenda
• SSH
• HTTPS
• SFTP
• Users & Groups
• Password
Page 379
1
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-10’s "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, hmac-
ripemd160, 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 380
2
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 IDU’s
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 381
3
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 382
4
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 IDU’s 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 383
5
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 384
6
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 385
7
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 386
8
3/7/2010
Thank You !
17
Page 387
9
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
• Roof top, wall, or pole
• Passive heat exchange - no need for air conditioning systems
• External battery backup solution with enclosure (Optional)
• Heating unit for frigid environments
© CERAGON NETWORKS LTD. Proprietary and Confidential information of Ceragon Networks Ltd
Page 388 1
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

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
Page 389 2
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
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)
Page 390 3
6/13/2010
IP IP
protection classes
55 – What does that mean ?
First Characteristics Numeral IP XY - Foreign Bodies Protection, Solids
Index
Protection against
Protection against solid objects (foreign bodies)
Human/Tool Contact
0 No special protection
1 Back of hand, Fist Large foreign bodies, diam. >50mm
2 Finger Medium-sized foreign bodies, diam. >12
3
Tools and wires etc with a
Small foreign bodies, diam. >2.5mm
thickness >2.5mm
4
Tools and wires etc with a
Granular foreign
g bodies,, diam. >1mm
thickness >1mm
5
Complete protection, Dust protected; dust deposits are permitted, but their
(limited ingress permitted) volume must not affect the function of the unit.
6 Complete protection Dust-proof
7
IP IP
protection classes
55 – What does that mean ?
Second Characteristics Numeral IP XY - Water Protection, Liquids

Index Protection from
Protection against water
condition
0 N special
No i l protection
t ti
1 Water dripping/falling vertically Condensation/Light rain
2 Water sprayed at an angle (up to 15º degrees from the vertical) Light rain with wind
3 Spray water (any direction up to 60º degrees from the vertical) Heavy rainstorm
4 Spray water from all directions, (limited ingress permitted) Splashing
5 Low pressure water jets from all directions, (limited ingress
Hose down, residential
permitted)
6 Hose d
H down,
High pressure jets from all directions, (limited ingress permitted) commercial.
eg. Ship decks
7 Temporary immersion, 15 cm to 1m Immersion in tank
8
For use on Titanic
Permanent Immersion, under pressure
recovery vehicle
8
Page 391 4
6/13/2010
Outdoor Enclosure Design - external

D W
• General Dimensions
• H: 18.5 in / 47 cm
• W: 24 in / 61 cm
• D: 17 in / 43 cm
• Weight
• 55 Pounds / 25Kg
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
Page 392 5
6/13/2010
Thank You
Page 393 6
FibeAir® IP-10
License
Management
Guide
Part ID: BM-0139-0

Doc ID: DOC-00019183 Rev a.00
November 2008
Page 394
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 user’s authority to operate the equipment and the warranty for such equipment.
Copyright © 2008 by Ceragon Networks Ltd. All rights reserved.
Corporate Headquarters: European Headquarters:

Ceragon Networks Ltd. Ceragon Networks (UK) Ltd.
24 Raoul Wallenberg St. 4 Oak Tree Park, Burnt Meadow Road
Tel Aviv 69719, Israel North Moons Moat, Redditch,
Tel: 972-3-645-5733 Worcestershire B98 9NZ, UK
Fax: 972-3-645-5499 Tel: 44-(0)-1527-591900
Email: info@ceragon.com Fax: 44-(0)-1527-591903
www.ceragon.com Email: infoeuro@ceragon.com
North American Headquarters: APAC Headquarters
Ceragon Networks Inc. Ceragon Networks (HK) Ltd.
10 Forest Avenue, Singapore RO
Paramus, NJ 07652, USA Level 34 Centennial Tower
Tel: 1-201-845-6955 3 Temasek Avenue
Toll Free: 1-877-FIBEAIR Singapore 039190
Fax: 1-201-845-5665 Tel - + 65 6549 7886
Email: infous@ceragon.com Fax: +65 6549 7011
Page 395
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
Page 396
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 Page 397 1

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 Page 399 3

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

Search for Devices
In the main device list web page, you can click Search to locate a particular device that is
registered in the system.
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:
Region /
Device ID Customer Country Link Side
Network
In the Device ID column, use only upper case letters.
Adding and Deleting Devices
To add a new device, in the toolbar, click New .

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.

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 Name in License
Value Description
Type Management Site
3 0 IP10-CAP-010 Feature disabled
3 1 IP10-CAP-025 Radio Cap. Upgrade 10->25 Mbps
3 5 IP10-CAP-200 Radio Cap Upgrade 10->200 Mbps
3 8 IP10-UPG-025-050 Radio Cap. Upgrade 25->50 Mbps
3 12 IP10-UPG-025-300 Radio Cap Upgrade 25->300 Mbps

ACM
Value Description
Type Managament Site
1 0 Feature disabled
1 1 IP10-ACM ACM
Networking (Metro Switch Enabled)

Value Description
Type Management Site
2 0 Feature disabled
2 1 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.

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.

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:

Click Continue to go back to the device list page.
The device list page will appear with the updated information.

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.

Click the number in the Qty Generated column for a list of licenses used to generate keys.

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.

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.

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.

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.

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 locate a particular user.
To define a new user, click New . The following page appears:

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.

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.

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.

RF Units
Ceragon's RF Units were designed with sturdiness, power, simplicity, and compatibility in mind. These advanced systems
provide high-power transmission for short and long distances and can be assembled and installed quickly and easily. In
addition, the RFUs can operate with different FibeAir Indoor Units, depending on the desired configuration.
FibeAir RFUs (Radio Frequency Unit) delivers the maximum capacity over 7-56 MHz channels with configurable
modulation schemes from QPSK to 256QAM. The RFU supports low to high capacities for traditional voice, mission
critical and for emerging Ethernet services, with any mix of interfaces pure Ethernet, Pure TDM or hybrid Ethernet and
TDM interfaces (Native2)
High spectral efficiency is ensured using the same bandwidth for double the capacity, via a single carrier, with vertical
and horizontal polarizations. This feature is implemented by a built-in Cross Polarization Interference Canceller (XPIC)
mechanism.
Ceragon range of RFUs address any network need be it Mobile backhaul, Backbone networks, Rural Broadband or
private networks applications.
RFU-C
FibeAir ® RFU-C
High Performance, small footprint 6-38 GHz Radio Frequency Unit
RFU-C is a fully software configurable, state-of-the-art RFU (Radio Frequency Unit) that supports a broad range of
interfaces and capacities from 10Mbps up to 500Mbps . This innovative and compact unit uses an “on-the-fly” upgrade
method, whereby network operators only buy capacity as needed, savings on initial investments and ongoing OPEX.
With RFU-C traffic capacity throughput and spectral efficiency are optimized with the desired channel bandwidth. For
maximum user choice flexibility, channel bandwidths can be selected together with a range of modulations from QPSK to
256 QAM over 7-56 MHz channels bandwidth
• More power in a Smaller package
Up to 24 dBm for extended distance, enhanced availability, use of smaller antennas
• Broad Capacity range – from Low to High
Delivers 10 Mbps up to 500 Mbps over a single carrier
• Compact, lightweight form factor
Reduces installation and warehousing costs
• Supported configurations:
1+0,1+1,2+0 ,2+2
• Efficient and easy installation
Direct mount installation with different antenna types
Ceragon RF Units 1
Page 423
RFU-HS
FibeAir® RFU-HS
High capacity and High Power, 6-8 GHz Radio Frequency Unit
The FibeAir RFU-HS is a high transmit power RFU (Radio Frequency Unit) for long-haul applications. Based on
Ceragon’s field-proven RFU-HP technology, this RF unit supports capacities of up to 500 Mbps for TDM and IP
interfaces.
With its high transmit power, FibeAir RFU-HS is designed to enable high quality wireless communication in the most
cost-effective manner, reaching over longer distances while enabling the use of smaller antennas.
• Ultra high transmit power

Up to 30 dBm for longer distances, enhanced availability, smaller antennas
• High-Capacity
Up to 56 MHz Channels to deliver up to 500 Mbps on a single channel
• Direct or remote Mount
Flexible installation saves costs and reduces transmission loss
• Supported configurations
1+0,1+1,2+0 ,2+2
RFU-HP
FibeAir® RFU-HP (1500HP)

High Power 6-11 GHz Radio Frequency Unit
FibeAir RFU-HP (1500HP) is a high transmit power RFU (Radio Frequency Unit). Within its unique branching design,
RFU-HP can chain up to five carriers per single antenna port, making it ideal for Trunk or Multi Carrier applications.
Depending on customer preference, the RFU-HP can be installed in either indoor or outdoor configurations.
Ceragon RF Units 1-2

Page 424
The field proven FibeAir RFU-HP was designed to enable high quality wireless communication in the most cost-effective
manner. With tens of thousands of units deployed worldwide, the FibeAir RFU-HP serves mobile operators enabling
them to reach over longer distances while enabling the use of smaller antennas.
In order to ensure the maximum flexibility and transmission efficiency, FibeAir RFU-HP includes two receivers and one
transmitter in a single transceiver unit. This design gives it a built-in Diversity capability which increases the reliability of
the link.
• Ultra high transmit power

Up to 33 dBm for longer distances, enhanced availability, smaller antennas
• High-Capacity
Up to 30 MHz channels to deliver up to 250 Mbps on a single channel
• Built-in diversity
Single RFU with two receivers
• Innovative IF combining
Improve system gain
• Split-mount and all-indoor configurations
Installation flexibility
• Multiple carries
Up to 10 carrier per one antenna
• Space and Frequency Diversity
RF Units (RFUs) - Quick Selection Guide

1. For the 13-38 GHz frequency range, use FibeAir RFU-C.
2. For low frequencies, please refer to the three selection options below:
Ceragon RF Units 1-3

Page 425

IP-10G Advanced Course Handbook v3.3

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

IP-10G Advanced Course Handbook v3.3

Uploaded by

Copyright:

Available Formats

IP-10G Advanced Course

Visit our Customer Training Portal at Training.Ceragon.Com

Should you require further information, please do not hesitate to contact us at

I thank you in advance for your kind cooperation,

Course Name IPEO&M: IP-10R1 extended operations and maintenance

Scope Product-oriented Theory + Hands-on

Minimum required setup (to be provided by customer):

Test Kit (RF to WG adapters, attenuators, SMA cable) 3 (1 per link)

1 Ceragon Training Agenda v3.0

IP-10G IDU Front Panel Description

Shelf / Node Installation – Physical Inspection

 System name & Contact Details (Unit Info)

Radio Link Commissioning:

L2 ETH Switch Modes:

 Ethernet switch port

2 Ceragon Training Agenda v3.0

TDM/SDH Cross-Connect - Configuration Review

TDM/SDH Cross-Connect – Practical Exercises

 Using the Current Alarms

Troubleshooting & Maintenance:

1+1 Internal Protection - Configuration Review

1+1 Internal Protection - Practical Exercises

3 Ceragon Training Agenda v3.0

Introduction to Quality of Service & Traffic Engineering

QoS - Practical Exercises:

 Ingress Rate Limiter (Policer)

RSTP - Configuration Review

Network Resiliency (RSTP) - Practical Exercises:

Q-in-Q (Metro) – Configuration Review

Q-in-Q (Metro) - Practical Exercises

4 Ceragon Training Agenda v3.0

Introduction to Link Aggregation

Link Aggregation – Practical Exercises

XPIC – Configuration Review

XPIC - Practical Exercises

NMS (PV) Setup Configuration:

 Manual configuration of elements (IDUs)

NMS End-2-End XC - Configuration Review

NMS End-2-End XC - Practical Exercises (various applications)

5 Ceragon Training Agenda v3.0

Ceragon - Company Presentation

Leaders in High-Capacity Wireless Backhaul

2 Proprietary and Confidential

Segment Breakdown H1 2009

3 Proprietary and Confidential

Short Haul Links: Rapid Growth

4 Proprietary and Confidential

LTE-Ready Mobile Backhaul

Rural and WiMAX Backhaul

Proprietary and Confidential

Mobile Backhaul WiMAX Backhaul

Private, Utility, State & Rural Broadband

6 Proprietary and Confidential

Strategic Partnerships for Growth

• Opportunity to participate in large network deployments

OEM Solution reselling Per project Vertical reselling

7 Proprietary and Confidential

Global, Diversified Customer Base

8 Proprietary and Confidential

Ceragon Product Portfolio

Access Aggregation Backbone

9 Proprietary and Confidential

Comprehensive mounting Portfolio