Ceragon IP10G Advanced Course Handbook V4 2 PDF

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

or contact us at training@ceragon.com
Trainee Name:
Table of Contents
Theme Page
Introduction
Case Studies 3
Ceragon in a Nutshell 29
Introduction to MW Radio 41
Introduction to Mean Square Error 57
Introduction Adaptive Coding & Modulation 69
Introduction to 802.1p, 802.1q 80
IP-10G Front Panel Description 94
IP-10G Installation 104
Introduction to RFU-C 120
Basic Configuration:
Setting IP to Chassis (CLI) 127
Performance Monitoring 133
General Parameters (In-Band, OOB, License, NTP, Versions & more) 158
L2 Switch Configuration: Single Pipe, Managed Mode, VLANs 181
L2 Switch Configuration: Trunk Port VS. Access Port 190
L2 Switch Configuration: Metro Mode 197
Advanced Features
RING RSTP 205
Introduction to Quality of Service 220
Configuring Quality of Service (Part 1 - Basic) 233
Configuring Quality of Service (Part 2 - Advanced) 247
Interfaces
Commissioning the Radio Link 254
Green Mode 271
Interface Configuration (ETH, TDM, STM, Auxiliary, SyncE, AIS) 276
Cross Connection (XC) Trail Configuration 288
Automatic State Propagation (ASP) 305
Network Resiliency
Introduction to Link Aggregation 315
Configuring Link Aggregation 329
XPIC 337
1+1 HSB Protection 353
Service Operation, Administration & Maintenance (CFM) 370
Maintenance
Loopbacks (IF, Radio, Line) 392
Configuration File Backup 400
Software Upgrade 414
EMS Security 424
Annexes 433
PAGE 2
6/9/2010
Ceragon - Company Presentation
June 2010
Ceragon Networks
Leaders in High-Capacity Wireless Backhaul
Incorporation: 1996
Personnel: 500
Revenues in 2009: $184M
NASDAQ: CRNT
2 Proprietary and Confidential
PAGE 3 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
CeragonMarketShare Links TotalShortHaulvs.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
PTPRadioShipments TotalShortHaul NextGenerationHybridTDM/Packet&
Ceragonlinksshipments
LegacyTDM
Totalmarket
Totalshorthaulmarket
Growthdrivers:
From 0.8% market share in 2005 to 6.3% market share in 2009
Highcapacity 4,800 links to 35,000
AllIP Grew in 2009 in shipments terms by 30%
Global short haul shipment dropped by 11%.
Source: SLR, EJL, Ceragon
PAGE 4 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 5 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 6 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
SplitMount AllIndoor FullOutdoor
RadioUnits:Fromcompacttohighpower
Radio Units: From compact to high power Compactandmodular FulloutdoorNodalsite,
From1+0/1+1toN+1/N+0Trunk solutions Allindoorsolutions N+0toN+N,fullyredundant,
AllRFunitsapplicable
CarrierEthernet/Native2
IP10
CarrierEthernet/ TDM Trunk

Native2 TDM
IP10 1500R
3200T
IP10
CarrierEthernet/Native2
PAGE 7 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 8 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 9 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
helpingTelceltooptimizetheradioportionofthenetwork:
Design,install.Maintain.HugeSDHinstallbase
PAGE 10 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 11 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 12 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 13 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 14 12
6/9/2010
Case Study
Adam Internet - Australia
Broadband services to Businesses and Residential subscriber

Filling Broadband holes in Adelaide metro region (5,000 km2)
Australian government partially subsidizes the network & service
Up to 12Mbps/1Mbps service per subscriber
WiMAX RAN equipment vendor : Alvarion
Backhaul Solution: Ceragons FibeAir IP-10
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 15 13
6/9/2010
Case Study
Allegro: Business services for Queenslands
outer metro areas
Services: All wireless 2Mbps to 200Mbps

PtP Ethernet microwave: 8Mbps to 200Mbps
WiMAX: 1Mbps to 6Mbps
Backhaul: All wireless 200-400Mbps

Service aware PtP Ethernet microwave
IP/MPLS based Ring topology
Allegro Value proposition:

Rapid delivery times
Competitive pricing scheme based on carefully designed
network to meet low TCO (Total Cost of Ownership)
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 16 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 17 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 18 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 19 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 20 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
(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 21 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 22 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 SCIs
20 substations and metering points
Serving SCADA, Land Mobile Radio, Video
Advanced Metering Infrastructure traffic.
Solutions
8 hops all indoor
Serves as a Main link
Ring g topology
opo ogy
Why Ceragon?
Cost efficient, Upgradeable split Native2
solution.
Maplenet Wireless with networking, services
and support
South Central Indiana REMC (SCI)
PAGE 23 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 24 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 25 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 26 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
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 27 25
6/9/2010
Thank You
51
PAGE 28 26
10/5/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 29 1
10/5/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)
Where we are
ISPs
Fixed
Networks Cable
TV
CellularBackhaul RuralAccess
PDH
xDSL IPDSLAM IP/ETH

Subscribers Customer
Network
SDH/SONETRING
PSTN
PAGE 30 2
10/5/2010
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
5
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
6 eliminates the need for external switches
PAGE 31 3
10/5/2010
Radio capacity - ETSI

7MHz 14MHz
Ethernet 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 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
Ethernet Ethernet Ethernet
ACM # of ACM # of ACM # of
Modulation Capacity Modulation Capacity Modulation Capacity
Point E1s Point E1s Point E1s
(Mbps) (Mbps) (Mbps)
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
7
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
8
N x GE/FE
PAGE 32 4
10/5/2010
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
9
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.
10
PAGE 33 5
10/5/2010
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-
IP/MPLS based networks. mapped over MPLS
based MW radio links. aware" Ethernet MW
using pseudo-wires
radio is used where fiber
or routed using IP
connections not available
11
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
12
PAGE 34 6
10/5/2010
IEEE 802.1ag CFM (Connectivity Fault Management)
A Nodal Solution
Cellulartraffic
(TDM)
STM
Rings
PAGE 35 7
10/5/2010
A Nodal Solution
IP-10G VS. IP-10R1

Feature IP-10R1 G-Series
1+0, 1+1 HSB, 1+1 SD, 2+0 with XPIC

Supported radio configurations 1+0, 1+1 HSB, 1+1 SD
2+2 HSB with XPIC
XPIC option NO Yes
500Mbps
Max radio capacity 500Mbps
1Gbps using 2+0/XPIC
Multi-radio support NO Yes
5 x FE RJ-45+ 5 x FE RJ-45+
# of Ethernet interfaces
1 x GE RJ-45 + 1 GbE SFP 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, 16 T1, None 16 E1, 16T1, None
# of E1/T1s per radio carrier 16 84
T-Card slot (additional 16 E1/T1 interfaces or

NO Yes
STM1/OC3 Mux)
Nodal/XC/SNCP support NO Yes
SyncU NO Yes
Single channel 2 x Async V.11/RS232 or

V.11/RS232 User Channel option
(Asynchronous RS-232 / V.11.) 1 x Sync V.11
Link Aggregation NO Yes
PAGE 36 8
10/5/2010
IP-10G VS. IP-10R1

Feature IP-10R1 G-Series
RSTP (RING) with QinQ NO Yes
Dual Power Feed NO Yes
Floating IP NO Yes
MAC Aging Timer Yes Yes
ACM Low Latency Scripts Yes Yes
3.5 MHZ scripts Yes Yes
Radio Disabling NO Yes
QoS Yes Enhanced
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 37 9
10/5/2010
Higher Spectral-Efficiency
Whats in it for The Operator?
Typical IP10
Microwave Radio MicrowaveRadio
TWOradio links ONE radiolink

RequiredCapacity
or using
155200Mbps
56MHz channelbandwidth 28MHzchannelbandwidth
RequiredCapacity 28MHz 14MHz
70100Mbps ChannelBandwidth ChannelBandwidth
TheoperatorsavesCAPEX
andfreeupvaluablefrequencyresources
Higher Spectral-Efficiency is not enough
RadioType Ant.Diameter Length Modulation Capacity
TypicalSystemGain 1.80m 30Km 16QAM 32xE1s
TypicalSystemGain 1.80m 21Km 128QAM STM1/OC3
TypicalSystemGain 3.00m 30Km 128QAM STM1/OC3
HighSystemGain
HighSystemGain 1.80m 30km 128QAM STM1/OC3
SpectralEfficiency
shouldalwaysbecoupledwith
SystemGain
PAGE 38 10
10/5/2010
Ceragons Management Overview
IP-10 FibeAir
Tree Topology
PAGE 39 11
10/5/2010
Thank You!
training@ceragon.com
PAGE 40 12
IntroductiontoRadio
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

1 PAGE 41
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

2 PAGE 42
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

3 PAGE 43
Radio spectrum
7
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

4 PAGE 44
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 atmospheres
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

5 PAGE 45
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

6 PAGE 46
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

7 PAGE 47
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 phasein the 2nd zone they will be 90 to 270 degrees out of phasein 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

8 PAGE 48
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)

9 PAGE 49
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 ReceivedSignalLevel
TSL TransmittedSignalLevel
Lfs Freespaceloss=92.45+20logx(distanceinkmxfrequencyinGHz)
RSL=TX TX+Gain
Losses
L+Gain RX
Ant. 1 Ant. 2 Losses
fs

10 PAGE 50
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) =

11 PAGE 51
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
45degrees Binary00
135degrees Binary01
225degrees Binary11
315degrees Binary10
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

12 PAGE 52
QPSK VS. QAM Modulation
The various flavors of QAM offer higher data rates then 8 PSK
ThevariousflavorsofQAMofferhigherdataratesthen8PSK
ThisisbecauseQAMachievesagreaterdistancebetweenadjacentpointsintheIQ
planebydistributingthepointsmoreevenly
Thepointsontheconstellationaremoredistinctanddataerrorsarereduced
Higherorder>>morebitspersymbol
Constellationpointsarecloser>>TXismoresusceptibletonoise
SNR and RSL Constellation

The higher the SNR, the better the received signal !

13 PAGE 53
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
Bitsequence 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

14 PAGE 54
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

15 PAGE 55
256QAM Modulation
Constellation of 256QAM with noise added Constellation of 256QAM
31
ThankYou!
training@ceragon com

16 PAGE 56
Mean Square Error
Agenda
Definition
E
Example l
MSE & ACM
MSE values at 56MHz (case study)
MSE values at 28MHz (case study)
Troubleshooting examples
2
1 PAGE 57
Introduction
Definition | Example
3
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
4
2 PAGE 58
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.
5
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

6
3 PAGE 59
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
7
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
8
4 PAGE 60
Calculating MSE
Error = 0 mm
Quantity
+ 2 mm = 4
-3 mm = 9
- 4 mm = 16 + 6 mm = 36
width
To evaluate the total errors, we sum all the squared errors and take the average:
16 + 9 + 0 + 4 + 36 = 65, Average (MSE) = 13
The bigger the errors (differences) >> the bigger MSE becomes
9
Calculating MSE
MSE determines how narrow / wide the Bell is
Quantity
width
10mm
When MSE is very small the Bell shaped histogram is closer to perfect
condition (straight line): errors = ~ 0
10
5 PAGE 61
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)
11
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
12
6 PAGE 62
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
13
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
14
7 PAGE 63
Using MSE
Commissioning | Troubleshooting
15
Commissioning with MSE in EMS
When you commission your

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

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

result in loss of signal
16
8 PAGE 64
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
17
Triggering ACM with MSE

When ACM is enabled, MSE values are analyzed on each side of the link
When MSE degrades or improves, the system applies the required

modulation per radio to maintain service
ACM 28MHz, MSE [-dB]:
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
18
9 PAGE 65
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
19

Lets 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
20
10 PAGE 66
ACM & MSE: Another approach
In this graph we refer to a 56MHz channel. It is easier to observe the
hysteresis of changing the ACM profile with respect to measured MSE.
As you can see,

see the radio remains @ profile 6 till MSE improves to -32.5dB:
32 5dB:
ACM
Profile
32.5
30
Profile7 Profile6 Profile5 Profile4Profile3Profile2Profile1Profile0
MSE
3128.526.123.120.816.6 15.510.2
21
ACM & MSE: Another approach

When RF signal degrades and MSE passes the upgrade point (MSE @ red point), ACM will
switch back FASTER to a higher profile (closer to an upgrade point) when MSE improves.
When RF signal degrades and MSE does not pass the upgrade point (green point) ACM
waits
it till MSE improves
i to
t the
th point
i t off nextt available
il bl upgrade
d point
i t (takes
(t k longer
l time
ti to
t
switch back to the higher profile).
ACM
Profile
32.5 30
Profile7 Profile6 Profile5
3128.526.1 MSE
22
11 PAGE 67
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
23
ThankYou!
t i i @
24
12 PAGE 68
9/13/2010
ACM - Adaptive Code Modulation
FibeAir IP-10s 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 69 1
9/13/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 70 2
9/13/2010
ACM & SLA

When ACM is enabled and link degrades, highest priority services are
maintained
200Mbps
256QAM
170Mbps
BestEffort
128QAM
112Mbps
Silvver
Premium
32QAM
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 71 3
9/13/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 72 4
9/13/2010
Adaptive Coding & Modulation (ACM)

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

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

Microwave systems shall treat services in different ways
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
10
PAGE 73 5
9/13/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
12
PAGE 74 6
9/13/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
13
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
14
PAGE 75 7
9/13/2010
Radio Capacity Calculation
Radio & PDH Capacity VS. Channel
Ethernet capacity (a.k.a. Ethernet L1 capacity) - Total bit rate from an

Ethernet user port. Taking into account the full Ethernet frame including the
IFG and d preamble
bl fifields.
ld Eth
Ethernett capacity
it iis sometimes
ti referred
f d tto as ""portt
utilization rate".
Ethernet L2 capacity - Total bit rate of net Ethernet frames running over
the Ethernet user port. Taking into account the Ethernet frame without the
IFG and preamble fields.
Radio throughput
g p - Total bit rate supported
pp by
y the radio link running
g in a
specific channel/modulation including radio frame overhead, etc.
PAGE 76 8
9/13/2010

(figures refer to ETSI + MAC Header Compression Enabled)
3.5 MHz
P fil
Profile M d l ti
Modulation Mi i
Minimum M # off Ethernet
Max Eth t capacity
it Eth
Ethernett L2 Frames per
F R di
Radio
required capacity supported (Mbps) capacity (Mbps) seconds Throughput
license E1s (Mbps)
2 16 QAM 10 4 13.60 10.36 20233.77 10.50
4 64 QAM 25 6 20.14 15.35 29974.03 15.00
7 MHz
Profile Modulation Minimum Max # of Ethernet capacity Ethernet L2 Frames per Radio
license E1s (Mbps)
0 QPSK 10 4 13 42
13.42 10 23
10.23 19976 45
19976.45 10 38
10.38
1 8 PSK 25 6 20.18 15.38 30034.94 15.03
2 16 QAM 25 8 27.87 21.24 41475.26 20.31
3 32 QAM 25 10 34.48 26.27 51304.87 24.85
4 64 QAM 25 12 40.44 30.81 60175.21 28.95
5 128 QAM 50 13 46.60 35.50 69339.64 33.19
6 256 QAM 50 16 54.53 41.55 81151.77 38.64
7 256 QAM 50 17 57.38 43.72 85389.21 40.60

14 MHz
Profile Modulation Minimum Number of Ethernet capacity Ethernet L2 Frames per Radio
required capacity support E1s (Mbps) capacity (Mbps) seconds Throughput
license (Mbps)
0 QPSK 25 8 28.90 22.02 43001.18 21.02
1 8 PSK 25 12 40.90 31.16 60857.98 29.27
2 16 QAM 50 18 60.36 45.99 89823.89 42.65
3 32 QAM 50 20 70.35 53.60 104693.80 49.52
4 64 QAM 50 24 81.78 62.31 121693.09 57.37
5 128 QAM 100 29 98.43 74.99 146471.17 68.82
6 256 QAM 100 34 115.15 87.73 171347.98 80.31
7 256 QAM 100 37 124.52 94.87 185297.74 86.76
28 MHz
Profile Modulation Minimum required Number of Ethernet capacity Ethernet L2 Frames per Radio
capacity
it lilicense supportt E1s
E1 (Mb )
(Mbps) capacity
it (Mb
(Mbps)) seconds
d Throughput
Th h t
(Mbps)
0 QPSK 50 17 57.86 44.08 86099.43 40.93
1 8 PSK 50 23 77.86 59.32 115860.75 54.68
2 16 QAM 100 33 111.32 84.81 165648.63 77.68
3 32 QAM 100 44 150.76 114.87 224346.79 104.80
4 64 QAM 150 55 187.55 142.90 279093.55 130.09
5 128 QAM 150 68 228.81 174.33 340488.46 158.46
6 256 QAM 200 76 254.71 194.07 379034.79 176.27
7 256 QAM 200 80 268.45 204.53 399476.94 185.71
PAGE 77 9
9/13/2010

40 MHz
license (Mbps)
0 QPSK 50 23 79 64
79.64 60 68
60.68 118506 13
118506.13 55 90
55.90
1 8 PSK 100 35 119.11 90.75 177239.65 83.04
2 16 QAM 100 51 174.14 132.68 259136.72 120.87
3 32 QAM 150 65 218.49 166.47 325132.27 151.36
4 64 QAM 150 81 273.67 208.51 407254.05 189.30
5 128 QAM 200 84 305.49 232.76 454605.63 211.18
6 256 QAM 200 84 346.84 264.26 516135.41 239.61
7 256 QAM 300 84 369.96 281.87 550529.12 255.50
56 MHz
i d capacity
required it supportt E1s
E1 (Mb )
(Mbps) it (Mb
capacity (Mbps)) d
seconds Th h t
Throughput
license (Mbps)
0 QPSK 100 32 108.86 82.94 161994.37 75.99
1 8 PSK 100 48 163.37 124.48 243116.10 113.47
2 16 QAM 150 64 216.60 165.03 322318.52 150.06
3 32 QAM 200 84 288.50 219.81 429314.58 199.50
4 64 QAM 300 84 358.49 273.14 533473.73 247.62
5 128 QAM 300 84 430.43 327.95 640527.34 297.08
6 256 QAM 400 84 489.77 373.16 728824.51 337.87
7 256 QAM 400 84 531.82 405.20 791403.86 366.78
19
Radio & PDH Capacity VS. Channel - 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 78 10
9/13/2010
ThankYou!
21
PAGE 79 11
Introductionto802.1P/Q
Prerequisites
Prior to taking this module, trainee should be familiar with the

following:
Ethernet Topologies
OSI 7 Layers model

1
PAGE 80
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 81
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 82
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 83
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 VLANTAG Length/Type DATA+PAD FCS
TPID=0x8100 TCI
PTAG CFI VLANID

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

5
PAGE 84
Tagging a Frame
VLAN ID uses 12 bits, therefore the number of maximum VLANs is 4096:

2^12 = 4096
VID 0 = reserved
VID 4090-4096 = reserved (dedicated for IP-10s internal purposes such as MNG etc.)
VID 1 = default
After tagging a frame, FCS is recalculated
CFI is set to 0 for ETH frames, 1 for Token Ring to allow TR frames over
ETH backbones (some vendors may use CFI for internal purposes)
TPID / ETHER-Type / Protocol Type

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

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

6
PAGE 85
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 86
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)
VLANawareSwitch
A
Device unaware of VLANs Switch tags the ingress

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

8
PAGE 87
Port Types
Trunk Port a port which is aware of VLANs

(Can tag or un-tag incoming frames)
VLANawareSwitch
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.
VLANawareSwitch
T
A
A A
ThisportisnotamemberoftheTrunk
portmembershiplist,hence,trafficis
discarded

9
PAGE 88
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 0 88A8
TPID=0x88A8 TCI TPID 0 8100
TPID=0x8100 TCI
PTAG CFI VLANID PTAG CFI VLANID

3 Bit 1 Bit 12 Bit 3 Bit 1 Bit 12 Bit
Port Types
Q-in-Q (A.K.A. Double TaggingVLAN Encapsulation)
+
VLAN
awareSwitch
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 89
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 90
Mapping ETH to MPLS and vice versa
IP-10s L2 switch can take part in the process of transporting
services through MPLS core
Frames/services are mapped to MPLS FECs according to:

VLAN ID mapped to MPLS EXP bits
VLAN P-Bit mapped to MPLS EXP bits
Hub
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 NumberofAvailableTrafficClasses
The following
Th f ll i table
t bl shows
h PTags
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
EgressPTag

12
PAGE 91
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 92
Associated IEEE Standards
IEEE802.3:Ethernet(Max.framesize=1518bytes)
IEEE802.3ac:Ethernet(Max. frame size = 1522 bytes)
IEEE802.1d:MACBridgefirstintroducedtheconceptofFiltering
Servicesinabridgedlocalnetwork
IEEE802.1q:VLANTagging
IEEE802.1p:PriorityTagging/Mapping
IEEE802.1ag:OAM(CFM)
ThankYou!

14
PAGE 93
FibeAir IP-10 G-Series
Front Panel Description
Front Panel Overview
GUI Example)
Lets go over the front panel connections of the IP-10 G-Series
We shall explain them one by one, left to right

1
PAGE 94
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 95
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 96
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 97
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 98
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 99
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 100
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 switchs 8th port (same as in IP-10)
In addition
Grounding
-48vdc Power Connector
Fan Drawer

8
PAGE 101
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 102
Thank You !

10
PAGE 103

FibeAirIP10GSeries
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)
FTPinstallationguide
isavailableat
Training.Ceragon.Com:
seeModules/
Installation

1
PAGE 104
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 105
Site Requirements
Heat Dissipation:
The IP-10 IDU overall heat dissipation is 25W max (~85 BTU/h).
The ODU heat dissipation
p is 100W max.
Antenna Location:
As with any type of construction, a local permit may be required before installing
an antenna. It is the owners responsibility to obtain any and all permits.
Packing & Transportation
The equipment is packed at the factory, and sealed moisture-absorbing bags

are inserted.
The equipment is prepared for public transportation. The cargo must be kept dry
during transportation.
Keep items in their original boxes till they reach their final destination.
If intermediate storage is required, the packed equipment must be stored in dry

and cool conditions and out of direct sunlight
When unpacking
Wh ki
Check the packing lists, and ensure that the
correct part numbers and quantities of
components arrived.

3
PAGE 106
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 107
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 108
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.

6
PAGE 109
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 110
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 111
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 112
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 113
Installing a Blank Panel IDU in a Shelf
Slide the IP-10 blank panel into the enclosure, and tighten it using 2 screws.

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

11
PAGE 114
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 115
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 116
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 117
Power Requirements
Important
Make sure to use a circuit breaker to protect the circuit from damage by
short or overload.
Dual DC Feed
In boards with dual DC feed hardware, the system will indicate whether received
voltage in each connector is above or below the threshold power (40.5v
approximately).
This will
Thi ill b
be shown
h iin ttwo ways:
1. The LED (and its WEB representation) will only be ON if the voltage is above
the threshold
2. If voltage is below the threshold an alarm will be raised
User may configure the system not to raise an alarm in case of under-voltage
for any of the supplies.
This is used for cases where the dual feed hardware is used
used, but in the
installation only one of them is actually connected, so that no alarm is
permanently raised.

15
PAGE 118
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.
ThankYou!

16
PAGE 119
6/16/2010
RFUC&MediationDevices
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 120 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 121 2
6/16/2010
RFU-C direct mount configurations
1+0 direct
5
RFU-C direct mount configurations
1+1 direct
6
PAGE 122 3
6/16/2010
RFU-C remote mount configurations
1+0 remote
7
RFU-C remote mount configurations
1+1 remote
8
PAGE 123 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 124 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 125 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 !
ThankYou!
14
PAGE 126 7

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

1
PAGE 127
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 YoumayuseanySerial
Parity: None ApplicationsuchasHyper
Stop
St bits:
bit 1 Terminal PuTTY TeraTerm
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 128
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 129
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 130
Connecting IDU to EMS
1. Connect your EMS/NMS to the IDU (port 7) with ETH CAT.5 cable
2. Verify that your PCs IP is in the same subnet
3 Make sure Link is up

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

5
PAGE 131
Back to factory defaults
Going back to factory defaults can be done with EMS or CLI

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

6
PAGE 132
10/5/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
XPI
PAGE 133 1
10/5/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 134 2
10/5/2010
EMS Main View
Graphical MENU: Click to configure
EMS Main View
Protection Status Display &

Quick Access Icons
PAGE 135 3
10/5/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 136 4
10/5/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 137 5
10/5/2010
Available PM Statistics - Radio
TDM PM
(allocated E1/T1 VCs)
TDM
(E1/T1)
ETH PM (Data + In-Band):

1. Aggregated Errors STM1
2. Throughput STM-1 PM
3. Capacity
4. Radio Link Utilization When STM-1 T-Card
5. RMON standard is is inserted in front
implemented
p as well to panel)
p )
provide detailed data
Radio Signal PM:
ETH BW is a function of 1. RSL
available radio capacity as TDM 2. MSE
and STM-1 have higher priority 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 138 6
10/5/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.
14
PAGE 139 7
10/5/2010
ETH PM RMON
15
PM RMON Special Registers

RMONregister /Counter Description
Undersizeframesreceived Framesshorterthan64bytes
Oversize frames received

Oversizeframesreceived Frames longer than 1632 bytes
Frameslongerthan1632bytes
Totalframesreceivedwithalengthofmorethan1632bytes,
Jabberframesreceived
butwithaninvalidFCS
Totalframesreceivedwithalengthoflessthan64
Fragmentsframesreceived
bytes,andaninvalidFCS
Rxerrorframesreceived TotalframesreceivedwithPhyerror
TotalframesreceivedwithCRCerror,notcounteredin
FCSframesreceived
"Fragments",
Fragments ,"Jabber"
Jabber or
or "Rx
Rxerror
error"counters
counters
Countsgoodframesthatcannotbeforwardeddueto
InDiscardFrames
lackofbuffermemory
Countsgoodframesthatwerefilteredduetoegress
InFilteredFrames
switchVLANpolicyrules
Pauseframesreceived Numberofflowcontrolpauseframesreceived
16
PAGE 140 8
10/5/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 141 9
10/5/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 142 10
10/5/2010
PM TDM Trails
Trails can only be configured in the Main

IDU/Slot #1
Extension Trails (trails via extension IDU)

are also configured in the Main IDU
TDM Trail PM can only be viewed in the

Main IDU menu
The number of trails that can be

configured is a function of available radio
BW (license + script)
21
PM TDM Trails
22
PAGE 143 11
10/5/2010
PM TDM Trails In Detail
Errored Second (ES):
A one-second period with one or more errored blocks or at least one defect
23
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.
24
PAGE 144 12
10/5/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.
25
Background Block Error (BBE):
An errored block not occurring as part of a SES.
26
PAGE 145 13
10/5/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 146 14
10/5/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
29
PM TDM Trails through Radio
30
PAGE 147 15
10/5/2010
PM E1 / DS-1 (PM received from customer)
This PM data
relates to the
TDM Line
Interfaces.
Interfaces
31
PM STM-1 (Slot #2)
32
PAGE 148 16
10/5/2010
PM Radio - RF
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 (quality of received signal)

XPI analysis (when XPIC enabled)
33
PM Radio Signal Level Using Threshold
- 40dBm = Nominal RSL for an operational Link

Level 1: 25 sec
Level 2: 15 sec
900 sec = 15min Interval
34
PAGE 149 17
10/5/2010
PM Radio Signal Level - Using Threshold
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
35
PM Radio - Aggregate
Aggregated radio
traffic analysis
36
PAGE 150 18
10/5/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.
37
PM Radio - MRMC
38
PAGE 151 19
10/5/2010
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
gg ACM
modulation changing.
Threshold can be
configured as well for
easier maintenance.
39
PM Radio - XPI
Use this report to evaluate the cross-polarization

interference
Apply a threshold to establish a better notification

40
PAGE 152 20
10/5/2010
PM Radio - Ethernet
Frame Error Rate (%) measured on radio-Ethernet
interface (port 8)
Ethernet Capacity (a.k.a. Ethernet L1 capacity) - Total

bit rate from an Ethernet user port. Taking into account
the full Ethernet frame including the IFG and preamble
fields. Ethernet capacity is sometimes referred to as
"port utilization rate".
Radio Throughput - Total bit rate supported by the

radio link running in a specific channel/modulation
including radio frame overhead, etc.
Utilization (%) is displayed as one of five bins:

0 20% 20-40%,
0-20%, 20 40% 40-60%,
40 60% 60-80%,
60 80% 80-100%
80 100%
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
PM Ethernet Frame Error Rate
42
PAGE 153 21
10/5/2010
PM Ethernet Throughput
43
PM Ethernet Capacity
44
PAGE 154 22
10/5/2010
PM Ethernet Utilization
45
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
7octets 1octet 6octets 6octets 4octets 2octets 461500 4octets 12octets

octets
DataRate:min.64 octets max.1522octets
Physicalwirerate:min.84octets max.1542octets
46
PAGE 155 23
10/5/2010
Pre. SFD DA SA VLAN ETH Type Payload+ CRC Interframe

/Length Padding Gap
7octets 1octet 6octets 6octets 4octets 2octets 461500 4octets 12octets

octets
DataRate:min.64 octets max.1522octets
Physicalwirerate:min.84octets max.1542octets
In case we use a 64 bytes frame:
Throughput (Data rate) = ~ 77% of physical transmitted rate (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

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

100 Mbps = 100 Mbps
Utilization = Throughput = 77 = 20 %
Radio Capacity 400
48
PAGE 156 24
10/5/2010
ThankYou!
PAGE 157 25
10/5/2010

EMS General Configuration
Agenda
In this module we shall explain the following

features as they appear on the EMS
navigation Menu
PAGE 158 1
10/5/2010
Menus
Menu of a Main unit
Menu of an Extension
Unit Parameters Step # 1
Configure specific
information that may
assist you later
Such info will help you

locate your site easier
and faster
PAGE 159 2
10/5/2010
VDC reading
Celsius (metric) or
Fahrenheit (Imperial)
PAGE 160 3
10/5/2010
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)
IDU Serial number is

important when you
submit your request
for a License upgrade
When you complete

configuring all
settings, click Apply.
PAGE 161 4
10/5/2010
External Alarms Collapsed Input Alarm Config.
Dry Contact Alarms (DB-9):
5 Inputs
1 Output
External Alarms Expended Input Alarm Config.
PAGE 162 5
10/5/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 Menu of Extension Slots
This is the switch MAC address
Here you can set/review the IP

address of the remote site
You can also access the EMS of the

remote site (assuming both IDUs are
configured identically in terms of
MNG)
PAGE 163 6
10/5/2010
Management Main IDU: Setting IP Address

Here you can set the IP address of
the IDU
Let us examine the following

examples to understand how and
when we use each one of these
parameters
Node / standalone, no protection:

Connect your PC to any one of the MNG ports (7,6,5)
IP: 192.168.1.10
SM: 255.255.255.0 ETH Cross Cable IP: 192.168.1.100
D.GW: 0.0.0.0 SM: 255.255.255.0
PAGE 164 7
10/5/2010

Node, Standalone, no protection, going through a Router:
Set the Default GW address
10.10.2.10
DCN
IP: 192.168.1.10
SM: 255.255.255.0
255 255 255 0
D.GW: 192.168.1.12
192.168.1.12
IP: 10.10.2.100
SM: 255.255.255.0

Node/Standalone, 1+1 Protection:
Set a Floating IP
The floating
g IP address pprovides a
single IP address that will always give
direct access to the current active
main unit.
IP Slot #1: 192.168.1.10 ETH Y-Cable

IP Slot #2: 192.168.1.11 IP: 192.168.1.100
SM: 255.255.255.0 SM: 255.255.255.0
D.GW: 0.0.0.0
Floating IP: 192.168.1.22
See 1+1 Protection PPS for further info
PAGE 165 8
10/5/2010

Node/Standalone, 1+1 Protection, going through a Router:
Set a Floating IP + D. GW
192.168.1.100
IP Slot #1: 192.168.1.10 ETH Y-Cable

IP Slot #2: 192.168.1.11 IP: 10.10.2.100
SM: 255.255.255.0 SM: 255.255.255.0
D.GW: 192.168.1.100
Floating IP: 192.168.1.22
See 1+1 Protection PPS for further info
Management Main IDU: Setting No. of MNG Ports
This is the switch MAC address
If your link is up you should be

able to see the other ends IP
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 !!!
PAGE 166 9
10/5/2010
Management Main IDU: In Band Properties
In Band Management
g
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.
Management Main IDU: Port Properties
These parameters allow

you setting the
management capacity and
ports physical properties
PAGE 167 10
10/5/2010
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)
See next slide for more info.
Trap Configuration T. Destination Configuration
PAGE 168 11
10/5/2010
Licensing Copy, Paste, Ready to start
Licenses are generated per IDU S/N (capacity / ACM / switch mode)
License upgrade requires system reset.
Licensing the IDU according to ACM
Adaptive Coding & Modulation:
Allowed / Not Allowed
When allowed, the radios assign

scripts dynamically and
automatically to maintain service
while link degrades
(bit per symbol / order of modulation changes)
PAGE 169 12
10/5/2010
Licensing the IDU according to Switch Mode
Ethernet switch license:
allows using the L2 switch in the

following
g modes-
1. Single Pipe (Default no license

required)
2. Managed switch
3. Metro switch
Licensing the IDU according to Capacity
Capacity license:
Limits the total amount of radio
capacity available:
This is sum of ETH + TDM BW
The radio modem script is a

function of this license value
This license applies only if the

TDM-only license is disabled
PAGE 170 13
10/5/2010
Licensing the IDU according to Capacity (no TDM)
TDM-only license:
Limits the amount of TDM trails

that can be mapped to a radio.
Allows minimal ETH traffic for

network management only.
If this license is allowed, any radio

script can be loaded, but the
number of trails is limited.
Licensing the IDU according to Network Resiliency
Network resiliency license:
Allows configuration of features

that make use of loop network
topologies:
o Ring RSTP
o TDM trails p
protection ((SNCP))
Note that for systems in which

these features were enabled in
previous versions, the features will
be allowed even if no resiliency
license is purchased.
PAGE 171 14
10/5/2010
Licensing the IDU according to Synchronization
Synchronization unit license:
Allows configuration of external

source as a clock source for
synchronous Ethernet output
(assuming the IDUs
IDU s hardware
supports synchronization).
If this license is not installed,

Ethernet clock source can only be
a local (internal) clock.
Per Usage License
Per-usage license:
Allows unlimited usage of all

features in the system, and
generates reports of current
usage, used d ffor usage-based
b d
billing.
In addition, system will warn user

when a chargeable feature is
enabled.
PAGE 172 15
10/5/2010
License Types: Default / Normal / Demo
"Default"
Factory default license.
No License has been purchased or

loaded.
Total 10Mbps radio traffic

No ACM
No switch capabilities (single
pipe only).
No RSTP
SNCP trails are allowed
Synch. sources for Sync ETH are
blocked
All IDUs are manufactured with

"default" license.
"Normal"
Once license is loaded

successfully to the system, it is
considered to have "normal"
license.
Normal license allows access to

features and capacities according
to the loaded "license key".
PAGE 173 16
10/5/2010
"Demo"
Temporary license that allows

access to maximum capacity and
all features.
This option is limited only to 60

days (see next slide for further
details).
An event will be raised 10 days

y
before expiration.
Licensing: General
The License key is generated per IDU serial number (S/N)
In order to upgrade license, license-key must be entered to the system

(requires cold-reset)
When system is up, its license key is checked, allowing access to new
capacities and/or features
If license key itself is not legal (typing mistake, illegal S/N) specific alarm will
be raised
When "License Violation" alarm is raised,, Radio port

p capacity
p y is automatically
y
limited to ~3Mbps, allowing only management channels to remote end
To clear the violation alarm, user must configure the system to comply with the
loaded license, and then, issue cold-reset (radio resumes full operational status
if the violation is no longer relevant)
PAGE 174 17
10/5/2010
Licensing: Demo License
Demo license is allowed for 60 days per IDU, expanding the time is not feasible
The function can be enabled and disabled from the license menu
When the function is disabled or when the 60 days are up, the system shall
perform a reset and automatically change the radio-script to the last radio-script
that was used before the demo license was enabled
An alarm is raised and a timer of the remained hours is shown on the license
menu while demo is enabled
The timer does not run when the unit is down
48 hours before the license period is completed, an alarm will be raised to

notify that the demo license is about to be ended within 48 hours
When demo is enabled, all the radio scripts are available and the user can
choose any wanted script
NTP Client Properties

Enable / Disable
Type NTP Server IP address
Expect IDU to lock on NTP Servers clock
Expected Status:
1. If locked, it returns the IP address of the server it is locked on.
2. Local if the NTP client is locked to the local elements real-time clock
3. NA - if not synchronized with any clock (valid only when Admin is set to
Disable).
The feature supports Time Offset and Daylight Saving Time.

Time Offset and Daylight Saving Time can be configured via WEB (Unit Information
page) or via CLI: /management/mng-services/time-service>
PAGE 175 18
10/5/2010
NTP Properties
NTP Properties
When using NTP with external protection 1+1, both Active and Standby
units
nits sho
should
ld be locked independentl
independently on the NTP ser
server,
er and report
independently their Sync status.
Time & Date are not copied from the Active unit to the Standby unit
When using NTP in a shelf configuration

configuration, all units in the shelf (including
standby main units) are automatically synchronized to the active main units
clock.
PAGE 176 19
10/5/2010
IP Table
Here you can manually set your neighbors network properties
SNMP
V1
V2c
V3
No security
Authentication
Authentication privacy
SHA
MD5
No Authentication
PAGE 177 20
10/5/2010
All ODU
This feature is used to feed the integrated fans of the All Outdoor Enclosure
(standalone outdoor rack)
When Enabled, the All ODU enclosure interface is activated, and the enclosure
controller can then be powered to monitor fan failure alarms.
The External Alarm Input #1 becomes an output, which together with 3.3V is
used to drive the enclosures electronic board.
External Alarm Input #2 is set with a specific text & severity, and is used to
monitor any enclosure fan failure, and to raise an alarm for it (polarity change
was required to adapt it to the enclosure behavior).
All ODU Disabled All ODU Enabled

All ODU - External Alarms Status

All ODU = Disabled
All ODU = Enabled
PAGE 178 21
10/5/2010
Versions - IDU
Versions - ODU
PAGE 179 22
10/5/2010
Versions Running / Installed / Upgrade / Downgrade
Lets 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
ThankYou!
46
PAGE 180 23
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 181 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 182 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 183 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 184 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 185 5
3/7/2010
Managed Mode
Configuration
Configuration Managed Mode
Lets 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 186 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 187 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 188 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 189 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 190 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 191 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 192 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 193 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 194 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 195 6
4/17/2010
EMS Trunk Configuration
2
1
3
ThankYou!
14
PAGE 196 7
10/5/2010

EMS Metro Switch Configuration
Agenda
Metromodereview
Configuration Guidelines
ConfigurationGuidelines
SimplifiedFlow
CommonApplications:CN PN PN CN
CommonApplications:CN PN PN PN
SwitchModeConfiguration
CNPortConfiguration
PNPortConfiguration
2
PAGE 197 1
10/5/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
3
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,

networks each associated with
a unique S-VLAN
CN ports remove the S-VLAN towards a Customer interface
Network #1
CVLAN100
S-VLAN 9 CVLAN101
Radio
R di Network 1 CVLAN102
CVLAN103
Ports CVLAN100
(PN) S-VLAN 8
Network 2
CVLAN101
CVLAN102
CVLAN103
Network #2
4
PAGE 198 2
10/5/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
5
CN-PN-PN-CN
CVLAN100
S-VLAN 9 CVLAN101
Radio BTS 2 CVLAN102
CVLAN103
BTS#2:
CVLAN100
Ports CVLAN100
CVLAN101 (PN) S-VLAN 8
BTS 1
CVLAN101
CVLAN102
CVLAN102 CVLAN103
CVLAN103
CN
CN
CN
BTS#1:
CVLAN100 CN
CVLAN101
CVLAN102
CVLAN103
6
PAGE 199 3
10/5/2010
CN-PN-PN-PN
CVLAN100
S-VLAN 9 CVLAN101
Radio BTS 2 CVLAN102
CVLAN103
BTS#2:
CVLAN100
Ports CVLAN100
CVLAN101 (PN) S-VLAN 8
BTS 1
CVLAN101
CVLAN102
CVLAN102 CVLAN103
CVLAN103
CN
CN
PN
BTS#1:
CVLAN100
CVLAN101
CustomerNetwork ProviderNetwork
CVLAN102
CVLAN103
7
Switch Mode Configuration
1 1. Set mode to Metro (requires reset)
2. Add the S-VLAN ID (set & apply)
8
PAGE 200 4
10/5/2010
CN Port Configuration
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
6. E bl PPortt L i
Learning
7. Apply & Refresh
8. See screen capture next slide
9
CN Port Configuration
3
4
10
PAGE 201 5
10/5/2010
PN Port Configuration
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
6. A l &R f h
Refresh
7. Set the required S-Tag (Ether-Type)
8. See screen capture next slide
11
PN Port Configuration
12
PAGE 202 6
10/5/2010
PN Port Configuration Setting the S-Tag
This is the bottom of the

Interfaces/ETH ports
configuration page
0x88A8
0x8100
0 8100
0x9100
7 0x9200
13
Additional Information
QoS with Metro mode:

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.
Link Configuration:
Metro switch can work with a remote Metro switch or remote Single Pipe switch
Metro switch cannot work with a remote Managed switch
RSTP with Metro mode:

RSTP is supported in Metro mode
14
PAGE 203 7
10/5/2010
ThankYou!
15
PAGE 204 8
10/17/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 205
1
10/17/2010
Student Perquisites
Viewers / end-user are required to have previous experience prior to

practicing this module:
1. End users should be familiar

f with Switch
S configuration
f
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

revertible. When the ring is set up
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 206
2
10/17/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
S can be activated only in Managed
Switch
S 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
itself.
PAGE 207
3
10/17/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
N d cold
ld resett (Pi
(Pipe and/or
d/ SSwitch).
it h)
Node power down (Pipe and/or Switch)
xSTP port disable / enable
PAGE 208
4
10/17/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
S
Switch IDUs will be configured
f to In-Band, while Single
S 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 itit.
thus,
Note When using a node (Outdoor Enclosure), there is no need to configure

Management mode for the 2nd slot
In-Band Management (2)
PAGE 209
5
10/17/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 210
6
10/17/2010
EMS
Configuration
Setup Configuration
Site#1 Site#2
1 6 7
1 6 7
Pipe(slot#2)
Pipe(slot#2)
1 1 3 4 5 6 7
1 1 3 4 5 6 7
MNG(slot#1)
MNG (slot #1)
MNG(slot#1)
Site#3
1 6 7
Pipe(slot#2)
1 1 3 4 5 6 7
MNG(slot#1)
EMS
1. You may start with out of band configuration to avoid physical loops
2. Establish the Radio links according to the setup scheme
PAGE 211
7
10/17/2010
Setup Configuration
Site#1 Site#2
1 6 7
1 6 7
Pipe(slot#2)
Pipe(slot#2)
1 1 3 4 5 6 7
1 1 3 4 5 6 7
MNG(slot#1)
MNG ( l t #1)
MNG(slot#1)
Site#3
1 6 7
Pipe(slot#2)
1 1 3 4 5 6 7
MNG(slot#1)
EMS
3. Connect between slot 2 and slot 1 using ports number 1 and fibers
4. Enable RSTP in all Managed Switch IDUs (see next slide)
Setup Configuration Enabling RSTP
PAGE 212
8
10/17/2010
Setup Configuration Configuring In Band MNG

Site#1 Site#2
1 6 7
1 6 7
Pipe(slot#2)
Pipe(slot#2)
1 1 3 4 5 6 7
1 1 3 4 5 6 7
MNG(slot#1)
MNG ( l t #1)
MNG(slot#1)
Site#3
1 6 7
Pipe(slot#2)
1 1 3 4 5 6 7
MNG(slot#1)
5. Enable In Band Management + VID 200

6. Connect the EMS PC to one of the IDUs (MNG port #7), disconnect other
connections
7. Verify all GbE ports 1 of Slots #1 are Trunk & members of VID 200 (next slide)
GbE Port #1 Configuration
Add Services of other VLANs as

well if the RING is required to pass
ETH data as well (see example
below, VID 1000)
Please note the VIDs need to be

created first in the Switch
Configuration page
PAGE 213
9
10/17/2010
RSTP Verification
Site#1 Site#2
1 6 7
1 6 7
Pipe(slot#2)
Pipe(slot#2)
1 1 3 4 5 6 7
1 1 3 4 5 6 7
MNG(slot#1)
MNG ( l t #1)
MNG(slot#1)
Site#3
1 6 7
Pipe(slot#2)
1 1 3 4 5 6 7
MNG(slot#1)
8. PING EMS to all Sites at the same time (multiple PING sessions)
RSTP Verification
9. Examine which switch is the Root Bridge and which ports are the Root Ports
10. Verify that the ring is set up properly (one Root)
PAGE 214
10
10/17/2010
RSTP Verification
11.Identify the Edge Ports and Non-Edge ports in your setup and make sure
they are configured correctly
Enabling ASP
Make sure that all RING IDUs (Pipe & Managed) support Automatic State
Propagation (enabled).
Enabling
g ASP allows RSTP Ring g to converge
g faster by yppropagating
p g g radio
alarms into the Line and thus, accelerating port state changes.
Configure the ASP Criteria as required.
PAGE 215
11
10/17/2010
Triggering a Switchover
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).
Prioritizing RSTP ports & topologies
PAGE 216
12
10/17/2010
Prioritization Criteria
1. Bridge Priority (User configurable)
2. MAC Address (unique per IDU)
3. Port Priority (User configurable)
4 Path
4. P th C
Costt (User
(U configurable)
fi bl )
Reading the Aggregated Path Cost

This value shows the time it takes for
the bridge to get to the Root Bridge
(in terms of interface capacity).
The lower this value is, the better.
Root Bridges will show this value = 0
This value indicates the aggregated

cost a bridge has to go through to get
to the Root bridge.
PAGE 217
13
10/17/2010
Setting the Bridge Priority
All bridges are given the same Bridge

Priority (32768) by default.
A bridge with lower priority are more

likely to become the Root Bridge
Setting the Port Priority
All ports are given the same priority

128
Should you wish to manually select

the Root Port, you may set a lower
value
Ports with lower priority are more

likely to be chosen as the Root Port
PAGE 218
14
10/17/2010
Setting the Path Cost
The bigger the port capacity is, the

lower this value becomes
For example:
1GbE is given lower path cost than
FE port
The bridge assigns a Root Port with

the lowest Path Cost to the Root
Bridge
ThankYou!
30
PAGE 219
15
10/17/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 220
1
10/17/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
L2ETH
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
L2ETH
stands for ADM SW
MW
Radio
PAGE 221
2
10/17/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 222
3
10/17/2010
Why do we need QoS? (2)

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

p
Operators 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?...
Whosfirst?
PAGE 223
4
10/17/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 224
5
10/17/2010
IP-10G L2 ETH Switch Ports
The IP-10Gs 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 225
6
10/17/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 226
7
10/17/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 227
8
10/17/2010
Using Queuing
Scheduling: Round Robin

Once the queues are filled with information, we need to empty them
Which queue should we empty first? Pro: no queue starvation

C
Con: no prioritization
i iti ti
Emptying cycle is fixed all queues are treated equally
Q1 Low
Q1
Q2 Q2
Q3 Q3
Q4
Q4 High
time
t1 t2 t3 t4
PAGE 228
9
10/17/2010
Scheduling: Weighted Round Robin

Emptying cycle is configurable every queue can be given specific weight
Pro: no queue starvation
Q1 Low
Q1
Q2 Q2
Q3 Q3
Q4
Q4 High time
t1 t2 t3 t4 t5
Scheduling: 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
Pro: Optimized Prioritization

Con: Queue starvation
PAGE 229
10
10/17/2010
Scheduling: All Strict Priority
The switch will empty a queue as long as the higher queue is empty
Pro: no queue starvation
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 230
11
10/17/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 231
12
10/17/2010
ThankYou!
25
PAGE 232
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 233 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 234 2
3/7/2010
IP-10G L2 ETH Switch Ports
The IP-10Gs L2 Switch has 8 ports:

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

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

Configure Port Type: Access / Trunk
Configure Port Membership
Step #3: Configure QoS per Port
PAGE 236 4
3/7/2010
Process Review
Policer per port
25
10 50
Rate Limit
PAGE 237 5
3/7/2010
3 classifiers to audit & queue Ingress Traffic
Queuing
Egress port Scheduler
Q4 Q4
Q1 Q3
Q2
Scheduling
PAGE 238 6
3/7/2010
Egress Port Shaper
Shaping
Basic Configurations
PAGE 239 7
3/7/2010
1. Ingress Rate Limiting
Lets say we want to limit Video streams

from customer interface towards the
network
Video streams are characterized with a

UDP protocol & multicast address
Therefore we shall define a Policer to

limit these parameters
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 240 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 241 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 242 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 243 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 244 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 245 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 246 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 247 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
34 Data Effort
56 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 248 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 249 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 250 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 251 5
3/7/2010
As long as the ingress frames comply to the higher conditions, the system will
not check lower conditions (Classifiers)
If higher condition is not matched, the system will proceed to the lower
condition and so on
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 252 6
3/7/2010
Thank You !
13
PAGE 253 7
10/5/2010
FibeAir IP10
Commissioning the Radio Link
Radio Link Parameters

TSL RSL
IDU ODU )) ) ODU IDU
To establish a radio link, we need to configure / monitor the following:
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. IF Interface Enable / Disable
7. Link ID must be the same on both ends
8. ATPC ON / OFF avoiding co-interferences caused by nearby antennas
9. MRMC Modem scripts (ACM or fixed capacity, channel & modulation)
10. Adaptive Power ON / OFF To allow max. transmission signal when ACM is ON
11. Green Mode (RFU-HP) please refer to Green Mode PPS
12. IFC in case of using Dual Receiver Radios
13. MAC Header Compression 45% higher throughput (Ceragon Proprietary)
2
PAGE 254 1
10/5/2010
Feature Description
(followed later with EMS Configuration Steps)
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
4
PAGE 255 2
10/5/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
5
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
6
PAGE 256 3
10/5/2010

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.
7
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
Check
Site A Site B
8
PAGE 257 4
10/5/2010
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
Site A
Check
Site B
9
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
Check
Site A Site B
10
PAGE 258 5
10/5/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.
11
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(highFEC)
At lower modulation orders the radio link will 7 256QAM(lowFEC)
tolerate lower RSL
S levels. For example:
With 16QAM the radio will drop at (-78dBm)

whereas with 8QAM the radio will drop at
(-82dBm)
12
PAGE 259 6
10/5/2010
MRMC Adaptive TX Power

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

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

When link suffers signal degradation, modulation may change from 256QAM to QPSK.
However, Max. power will increase to compensate for the signal degradation.
13
MRMC Adaptive Power = OFF
256QAM @ Monitored TSL = 18 dBm (Max.)
Signal Degradation
= Lower bit/symbol
16QAM @ MAX. TSL = 18 dBm
14
PAGE 260 7
10/5/2010
MRMC Adaptive Power = ON
256QAM @ Monitored TSL = 18 dBm(Max.)
Signal Degradation
= Lower bit/symbol
16QAM @ Monitored TSL = 24 dBm
15
MRMC Adaptive Power

It is essential that Operators ensure they do not breach any regulator-imposed
EIRP limitations by enabling Adaptive TX.
To better control the EIRP, users can select the required

q class ((Power VS.
Spectrum):
Class 2
Class 4
Class 5B
Class 6A
FCC
RFU C should
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
16
PAGE 261 8
10/5/2010
MRMC Adaptive Power

If enabled, the maximum tx power in lower constellations is limited by the
reference class configured, as listed in the following table.
Reference Class Reference Modulation

Class 2 4
Class 4 16
Class 5B 64
Class 6A 256
FCC 4
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
17
MAC Header Compression
1. No impact on User Traffic

2. Ceragon proprietary Mechanism
3. Improves the effective throughput by up to 45%
4
4. Effectiveness is reduced as the number of L2 streams is increased
MAC header compression is based on the following:

Dropping the Preamble + SFD + IFG saves 20 bytes
Dropping the Ethernet type saves 2 bytes
Adding a GFP header adds 4 bytes
In addition:
Frequently repeating SA & DA are learned
Learned DA & SA are not transmitted
A short pointer is used instead of the original 12 bytes
18
PAGE 262 9
10/5/2010
MAC Header Compression
L2ETHFrameSize[bytes] Improved Capacity

64 45%
96 29%
128 22%
256 11%
512 5%
19
EMS Configuration
PAGE 263 10
10/5/2010
Radio Settings Local Radio - 1
Radio type (displayed when comm. is OK)
Spectrum Mask
FQ spacing (gap) between channels
Monitored transmission power
Monitored received signal
Monitored MSE. Required lower than (-35dB)
Displays the current XPI value
The larger the amount, the poorer the radio link

quality. Required value = zero
Radio frequencies can be set

locally or both RFUs (box
checked) when links is up
21
Radio Settings Local Radio - 2
Enable / Disable : Requires system reset
Enable / Disable
Min. target RSL (local)
Enable = no transmission
Value depends on MRMC settings
Must be identical on both IDUs
Enable on both IDUs to get maximum

throughput (500Mbps @ 56MHz)
22
PAGE 264 11
10/5/2010
Radio Settings Local Radio 3 Disabling IF
As explained in previous slide, enabling or

disabling the IF interface requires a reset
23
Radio Settings 4: IFC

(Dual Receiver Radios for Space Diversity)
Shows current connector
RSL
S Display Selector
S
RSL current monitored level
RSL current monitored level (combined)
You can measure the RSL of:

Main Antenna
Diversity Antenna
Combined signal
To calibrate the distance between both antennas, type the distance in nano0seconds
and click Apply
24
PAGE 265 12
10/5/2010
Radio Settings 5: Remote Radio
When the radio link is up, you can configure the remote radio via the radio frames:
Make sure Remote IP is available (configurable)

Remote RSL can be read
Remote TSL can be set (values depend on MRMC script)
Remote ATPC REF level
Remote Floating IP
Remote TX MUTE can be disabled (see next slide)
25
Radio Settings 5: Un-muting Remote Radio
Simplified scheme
Sit B is
Site i NOT transmitting
t itti
but receiver is still ON
Site A is
transmitting
Site B
Site A
26
PAGE 266 13
10/5/2010
Radio Settings 6: Radio Thresholds
These settings determine the sensitivity / tolerance for triggering:
1+1 HSB switchover

Ethernet Shutdown
PM generated alarms
27
Radio Settings 7: MRMC Configuration
We shall review this page using the following slides:
28
PAGE 267 14
10/5/2010

Scroll down to the bottom of the MRMC page to select the required link
capacity by applying one of the enclosed scripts
29
MAX. Capacity
(w/out compression)
ACM Script CH. BW

Modulation
Spectrum
Mask
ACM is on
Spectrum
Class Type
30
PAGE 268 15
10/5/2010
31
Configure here:
Adaptive
p Power: Enabled / Disabled
Reference Class
32
PAGE 269 16
10/5/2010
ThankYou!
PAGE 270 17
9/19/2010
FibeAir RFU-HP
Introducing: Green Mode
Green Mode
Adjusting the power consumption is an errorless

process and designed to optimize power
consumption in normal fading environment
which is the case most of the time.
PAGE 271 1
9/19/2010
The HP Radios
1500HP / RFU-HP / RFU-A:
Radio No.ofReceivers ATPC GreenMode
Single RX/
1500HP
DualRX X
RFUHP SingleRX
Single RX/
RFUA
DualRX
Please note
1. Green Mode is supported with IP-10 IDUs only

2. When ATPC is enabled, Green Mode cannot be enabled
3. When connected to 1500R or any other IDU and operated in lower TX power, there is
considerable reduction in power consumption according to the green scale (see
later~33Watt)
ATPCVS.GREENMODE
ATPC:
UsedtoreduceinterferencetootherradiosinadenseMW
Used to reduce interference to other radios in a dense MW
environment
GreenMode:
GreenModeisenvironmentallyfriendly
SavesOPEXandCAPEXthroughlowerpowerconsumption
Oncefadingbecomessevere,actslikeATPC
PAGE 272 2
9/19/2010
Power Consumption VS. Monitored TSL
The radio operates in fixed and

pre-defined power-consumption
states:
MonitoredTX Consumed
PowerState
Power power[W]
HIGH 32dBm 72Watt

MEDIUM 28dBm 45 Watt
LOW 22dBm 33 Watt
Transition between power states is

hitless and errorless !
*X<Y<Z
Normal ATPC
Set reference level Remote TX changes accordingly
5 dB
15
10
0
RX:41dBm
Referencelevel:40dBm
When fading occurs, both transmitters try to

compensate for the losses by increasing
transmission power while maintaining RSL as
6
close as possible to the Ref. level
PAGE 273 3
9/19/2010
GREEN MODE setting the Green RSL to

-50dBm doesnt degrade fade
margin, as the mechanism will
Set GreenMode enable increase TX power if
Set GreenRSL limit [dBm] necessary.
15
10
5
0 dB
RX:52dBm
RX:37dBm
RX:42dBm
RX:47dBm
Green level: 50dBm
Greenlevel:
Greenlevel: 50dBm
When fading occurs, both transmitters

compare the monitored RSL with the Green
Level (Ref.). As long as RSL> Ref. there is no
need to increase the TSL.
7
GREEN MODE setting the Green RSL to

-50dBm doesnt degrade fade
margin, as the mechanism will
Set GreenMode enable increase TX power if
Set GreenRSL limit [dBm] necessary.
15 dB
RX:50dBm
RX:52dBm
Green level: -50dBm
50dBm
When RSL drops below the Green Ref. level,

we must increase the TSL to maintain the
fade margin and avoid low sensitivity
8
PAGE 274 4
9/19/2010
Thank You!
PAGE 275 5
10/5/2010

FibeAirIP10GSeries
Configuring Interfaces
Agenda
In this presentation we shall

explain the required steps to
configure these interfaces
PAGE 276 1
10/5/2010
ETH TDM STM1 AUX AIS SyncE
Configuring ETH ports is discussed in previous modules:
Switch Configuration
Trunk VS. Access
Metro
M t S Switch
it h C
Configuration
fi ti
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.
PAGE 277 2
10/5/2010
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.
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.
g
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 278 3
10/5/2010
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 84
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
M
Mute
t TX
TX:
Mutes the outgoing STM-1 signal, but
received signal will be used for traffic
PAGE 279 4
10/5/2010
The following configurations

are available:
Clock source:
This is a reference for the outgoing
STM-1 signal:
Internal Clock
Loop
STM VC
Synch VC
Thi
This iis th
the VC Ch
Channell which
hi h will
ill b
be
used to sync the STM-1 interface
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 pro

provide
ide 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
PAGE 280 5
10/5/2010
Line TX Protection Mode
STM-1/OC-3 interface transmission

behavior when in protection mode
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 281 6
10/5/2010
Excessive BER threshold:

Specific for STM-1 interface
Signal degrade threshold:

Specific for STM-1 interface
EOW may be used as a simple solution for on-site

communication between two technicians / installers / etc.
PAGE 282 7
10/5/2010
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.
WSC: 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.
PAGE 283 8
10/5/2010
WSC: OOB MNG in a 1+1 standalone IDUs
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.
OOB MNG in a 1+1 standalone IDUs (P. Panel)
PAGE 284 9
10/5/2010
This feature allows detection of AIS

signals in TDM traffic arriving 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
AIS Signaling in STM interface (VC 12)
In case of signal failure at the trail outgoing from the STM-1

STM 1 interface,
interface AIS
will be transmitted at the payload of the VC-12.
This table is added automatically to

the STM
STM-1 1 page when AIS is
enabled
PAGE 285 10
10/5/2010
Select Sync on slots you wish to sync the ETH ports to external source
External clock can be taken from:

TDM Line port
STM-1 VC
The ETH ports will sync on this selected port/channel
PAGE 286 11
10/5/2010
Please note
When selecting a Sync Source:
1. Y
1 You cannott sync ETH ports
t with
ith TDM ports
t off the
th same slot
l t
2. You can sync ETH ports with Radio Channels of any slot
ThankYou!
24
PAGE 287 12
9/13/2010

FibeAirIP10GSeries
XC / SNCP / Nodal Solution
Introduction
PAGE 288 1
9/13/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 p
provided for a trail in a network where full p
path redundancy
y topology
p gy 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 289 2
9/13/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
p nodes can be cascades to support
pp large
g aggregation
gg g 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 290 3
9/13/2010
FibeAir IP-10 Nodal Enclosures
Extension nodal enclosure
Main nodal enclosure
FibeAir IP-10 Scalable Nodal Enclosures

Payasyougrow!
PAGE 291 4
9/13/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
g Ethernet Switching
g
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
g Ethernet Switching
g 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 292 5
9/13/2010
Trail Configuration Guidelines
XC Trails Guidelines (1)
1. XC Trails can be configured only via Main unit
2 All Trails
2. T il are transported
t t d through
th h main
i unit(s)
it( )
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

5.
PAGE 293 6
9/13/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 (SNCP Protected Ring) = 180
9 Maximum
9. M i b off T
number il per R
Trails di = 84
Radio
Identify Trail interfaces prior to configuration

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

For SNCP we shall
Trail traverses through here: IP10 need to define 3
We shall need to define 2 interfaces
interfaces
IP10 Bypass
site Protected Trail
(Automatic)
IP10
Trail starts here:
For SNCP we shall
need to define 3
Radio Link interfaces
PAGE 294 7
9/13/2010
Pay attention to the order of configuration: 1
2 IP10
The Trail Start/End points should
be configured first (interface #1) 3
IP10 Bypass
site
Interfaces #2 and #3 can be
configured in a random order
Protected Trail
(Automatic)
2 3
IP10
Standalone non-protected Trail Configuration
PAGE 295 8
9/13/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
connector.
Your next step would be selecting
the VC number.
PAGE 296 9
9/13/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 297 10
9/13/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 298 11
9/13/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
IP10
Bypass
Node IP10
IP10
SDH interface
PAGE 299 12
9/13/2010
1st Node
PDH interface
IP10
IP10
Bypass
site
Radio CH #1 Radio CH #26

IP10
SDH iinterface
t f #1
Bypass Node
PDH interface
Radio CH #48
IP10
Bypass IP10
Node
Radio CH #1
IP10
SDH iinterface
t f
PAGE 300 13
9/13/2010
3rd Node
PDH interface
Radio CH #48
IP10
Bypass IP10
site Radio CH #26
IP10
SDH interface
Radio Capacity Calculation
PAGE 301 14
9/13/2010
Ethernet capacity (a.k.a. Ethernet L1 capacity) - Total bit rate from an

Ethernet user port. Taking into account the full Ethernet frame including the
IFG and d preamble
bl fifields.
ld Eth
Ethernett capacity
it iis sometimes
ti referred
f d tto as ""portt
utilization rate".
Ethernet L2 capacity - Total bit rate of net Ethernet frames running over
the Ethernet user port. Taking into account the Ethernet frame without the
IFG and preamble fields.
Radio throughput
g p - Total bit rate supported
pp by
y the radio link running
g in a
specific channel/modulation including radio frame overhead, etc.

3.5 MHz
P fil
Profile M d l ti
Modulation Mi i
Minimum M # off Ethernet
Max Eth t capacity
it Eth
Ethernett L2 Frames per
F R di
Radio
license E1s (Mbps)
2 16 QAM 10 4 13.60 10.36 20233.77 10.50
4 64 QAM 25 6 20.14 15.35 29974.03 15.00
7 MHz
Profile Modulation Minimum Max # of Ethernet capacity Ethernet L2 Frames per Radio
license E1s (Mbps)
0 QPSK 10 4 13 42
13.42 10 23
10.23 19976 45
19976.45 10 38
10.38
1 8 PSK 25 6 20.18 15.38 30034.94 15.03
2 16 QAM 25 8 27.87 21.24 41475.26 20.31
3 32 QAM 25 10 34.48 26.27 51304.87 24.85
4 64 QAM 25 12 40.44 30.81 60175.21 28.95
5 128 QAM 50 13 46.60 35.50 69339.64 33.19
6 256 QAM 50 16 54.53 41.55 81151.77 38.64
7 256 QAM 50 17 57.38 43.72 85389.21 40.60
PAGE 302 15
9/13/2010

14 MHz
license (Mbps)
0 QPSK 25 8 28.90 22.02 43001.18 21.02
1 8 PSK 25 12 40.90 31.16 60857.98 29.27
2 16 QAM 50 18 60.36 45.99 89823.89 42.65
3 32 QAM 50 20 70.35 53.60 104693.80 49.52
4 64 QAM 50 24 81.78 62.31 121693.09 57.37
5 128 QAM 100 29 98.43 74.99 146471.17 68.82
6 256 QAM 100 34 115.15 87.73 171347.98 80.31
7 256 QAM 100 37 124.52 94.87 185297.74 86.76
28 MHz
Profile Modulation Minimum required Number of Ethernet capacity Ethernet L2 Frames per Radio
capacity
it lilicense supportt E1s
E1 (Mb )
(Mbps) capacity
it (Mb
(Mbps)) seconds
d Throughput
Th h t
(Mbps)
0 QPSK 50 17 57.86 44.08 86099.43 40.93
1 8 PSK 50 23 77.86 59.32 115860.75 54.68
2 16 QAM 100 33 111.32 84.81 165648.63 77.68
3 32 QAM 100 44 150.76 114.87 224346.79 104.80
4 64 QAM 150 55 187.55 142.90 279093.55 130.09
5 128 QAM 150 68 228.81 174.33 340488.46 158.46
6 256 QAM 200 76 254.71 194.07 379034.79 176.27
7 256 QAM 200 80 268.45 204.53 399476.94 185.71

40 MHz
license (Mbps)
0 QPSK 50 23 79 64
79.64 60 68
60.68 118506 13
118506.13 55 90
55.90
1 8 PSK 100 35 119.11 90.75 177239.65 83.04
2 16 QAM 100 51 174.14 132.68 259136.72 120.87
3 32 QAM 150 65 218.49 166.47 325132.27 151.36
4 64 QAM 150 81 273.67 208.51 407254.05 189.30
5 128 QAM 200 84 305.49 232.76 454605.63 211.18
6 256 QAM 200 84 346.84 264.26 516135.41 239.61
7 256 QAM 300 84 369.96 281.87 550529.12 255.50
56 MHz
i d capacity
required it supportt E1s
E1 (Mb )
(Mbps) it (Mb
capacity (Mbps)) d
seconds Th h t
Throughput
license (Mbps)
0 QPSK 100 32 108.86 82.94 161994.37 75.99
1 8 PSK 100 48 163.37 124.48 243116.10 113.47
2 16 QAM 150 64 216.60 165.03 322318.52 150.06
3 32 QAM 200 84 288.50 219.81 429314.58 199.50
4 64 QAM 300 84 358.49 273.14 533473.73 247.62
5 128 QAM 300 84 430.43 327.95 640527.34 297.08
6 256 QAM 400 84 489.77 373.16 728824.51 337.87
7 256 QAM 400 84 531.82 405.20 791403.86 366.78
32
PAGE 303 16
9/13/2010
Radio & PDH Capacity VS. Channel - 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

ThankYou!
34
PAGE 304 17
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 305 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
Needtofind
alternativepath
When external devices do not support Fault Propagation
Configure the following:

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

1. Disable Local LOC
2. Enable Remote Fault to mute local transmitter in case of remote LOF / Link ID
mismatch & LOC
3. Disable Local Excessive BER - to avoid a dead lock scenario
Example: Avoiding Dead Lock in Single Pipe

Site B Site A
TX RX
RX TX
1. GbE FO breaks down or disconnects at the ingress port of Site A
PAGE 307 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 308 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 309 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
LocalCriteria:
Local Criteria:
LOC(GbE)
RadioLOF
LINKIDMismatch
ExcessiveBER
ACMprofileisbelowthreshold
1 8 8 1
Actions: Actions:
Muteport1(GbESFP) Muteport1(GbESFP)
PAGE 310 6
4/30/2010

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

Using Electrical GbE (RJ45) have identical settings:
1. ASP Enabled
LocalGbE 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 311 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 312 8
4/30/2010
Managed / Metro - Propagation Criteria

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

1. ASP Enabled
Localcriteria: 8 8
GbE LOC Actions:
Noactiontaken
ShutdownRadio
PAGE 313 9
4/30/2010
ThankYou!
19
PAGE 314 10
LinkAggregation
(IEEE802.3ad)
Agenda
Agenda
Definition
Advantages
Feature Review
Applications
Load Balance Example

1
PAGE 315
Introduction to Link Aggregation
IEEE Definition:
Link Aggregation allows one or more links to be aggregated

together to form a Link Aggregation Group
Group, such that a MAC
Client can treat the Link Aggregation Group as if it were a
single link
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 316
Benefits of using Link Aggregation
1. Increased aggregate bandwidth
Link Aggregation allows the establishment of full duplex point-to-point links

that have a higher aggregate bandwidth than the individual links that form the
aggregation.
The capacity of the multiple links is combined into one logical link.
100 Mbps
2. Improved Resiliency
In case of a failed link, remaining links take over utilization of new available BW
Traffic via LAG is distributed according to users policy improved reliability

3
PAGE 317
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 318
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
FeatureReview

5
PAGE 319
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) Last3 bits XORresult AssignedLAGPort

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 >
SA> 00:20:8f:0b:e1:03 011
>DA
111(5) Link#2
00:20:8f:0a:e1:04 100
SA> 00:20:8f:0b:e1:03 011
>DA 00:20:8f:0a:e1:01 001
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 320
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 321
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 322
Applications
pp
Introduction to Link Aggregation

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

(Nodal) Site implemented with LAG
1 2 3 4 5 6 7 8
Single Pipe
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 323
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 324
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
2+0 Multi-Radio
Static LAG
Dual (redundant) GE interfaces facing the 3rd party Switch/Router

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

1+1 HSB or
2+0 Multi-Radio
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 325
1+1 HSB With dual GbE + LAG (cont.)
1+1 HSB or
2+0 Multi-Radio
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!
LoadBalanceExample
p

12
PAGE 326
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 1 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 #1
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 327
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.
ThankYou!

14
PAGE 328
LinkAggregationGroupConfiguration
(IEEE802.3ad)
Agenda
Agenda
Guidelines Review
EMS Configuration
Using PM (RMON)

1
PAGE 329
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 330
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 331
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 332
Removing a Port from LAG
Ports removed from a LAG will keep the existing port parameters, but will
be initially disabled in order to prevent loops.
In addition, when the last port is removed from a LAG, the LAG will be
deleted.
Therefore it is necessary to remove all MEP/MIPs from a LAG before

removing the last port.
EMSConfiguration
g

5
PAGE 333
Setting Load Balance Policy
Open page:
Configuration
g / Ethernet Switch
Select Simple XOR for demos or

lab test or HASH for real traffic
Create VLAN(s) per service(s) in

the switch DB (if such VID do not
exist yet)
Creating LAG
1. Go to Configuration / Interfaces / Ethernet Ports
2. Click on Create LAG

6
PAGE 334
Selecting ports to LAG
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
Removing ports from existing LAG

1. At the bottom of the Ethernet Ports page you should see the LAG as a
new interface with its members listed as well
2 Click
2. Cli k on thi
this link
li k to
t modify
dif the
th LAG ((add/remove)
dd/ )

7
PAGE 335
Troubleshooting
1. When adding ports to LAG fails, the reasons might be:
2. QoS mismatch
3. VLAN membership mismatch
4. Physical properties mismatch (auto-neg, speed, flow control etc.)
5. Service OAM mismatch
Check the Ethernet Ports, QoS & Service OAM pages and compare these
parameters if problem continues
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

8
PAGE 336
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

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
+
=

9
PAGE 337
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
ThankYou!

10
PAGE 338
10/5/2010
IP-10G
XPIC: Introduction & Configuration
Avner Baruch
Guidelines
1. XPIC is supported with IP-10G IDUs in version 6.6.1 and higher
2. XPIC can only be configured in a node:
slots 1+2 and/or slots 3+4 and/or slots 5+6
3. IDU license determines the allowed script and link capacity
4. Identical configuration should be used in all IDUs participating in a link:
XPIC Script
Frequencies
SW version (IDU, ODU) If any of these conditions is not met, an
HW version (IDU, ODU) alarm will alert user. In addition, events will
Protection is disabled inform user of which conditions are not met.
PAGE 339 1
10/5/2010
Introduction
Introduction
Two data channels are transmitted & received over the same frequency on dual
polarization (H & V)
C
Crosstalk
t lk between
b t the
th polarizations
l i ti d
due tto iimperfect
f t antenna
t iisolation
l ti and
d
channel degradation can be effectively cancelled at the receiver using -
XPIC Cross Polarization Interference Cancellation/Canceller
* Ideal solution for frequency- crowded areas
PAGE 340 2
10/5/2010
Decoding the received signal

Both IDUs on each site communicate through the Backplane of the Nodal
Enclosure
Nodal Enclosure Nodal Enclosure
H
S M M S
S M V M S
Decoding the H signal

Each IDU accommodates 2 modems (Master and Slave)
In each site, the Main IDU communicates with the Mate IDU via the backplane
The Master modem (V) sends its signal (V) to the Mate Slave
The Mate Slave pproduces the interference signal
g ((v)) and sends it to its H-Master
Transmitter Receiver
HMaster H H+v HMaster H

backplane
Mate IDU v
Slave Slave
Slave Slave
backplane
Main IDU
VMaster V V+h VMaster V
PAGE 341 3
10/5/2010
Decoding the H signal - continued

By knowing the interference level (v), the Master Modem (H) can demodulate the
received horizontal signal (H)
The vertical channel is decoded similarly
Transmitter Receiver
HMaster H H+v HMaster H
backplane
Mate IDU v
Slave Slave
Slave Slave
backplane
Main IDU
VMaster V V+h VMaster V
XPIC Recovery Mechanism
The main purpose of the Recovery Mechanism is to recover link availability

due to hardware problem rather than fading issues
The recovery mechanism maintains a working link while attempting to recover

the faulty polarization
The mechanism applies periodic attempts to mute the problematic remote

transmitter
The time between one attempt and another is exponentially increased to

avoid unnecessary TX Mute when interference is temporary (allowing
sufficient to recover)
At the end of the process, if the problem still exists, the problematic link will
be permanently muted unless the user manually un-mutes it
PAGE 342 4
10/5/2010
XPIC Recovery Mechanism
The indication to entry the recovery mechanism is a loss of modem

preamble lock, which takes place at SNR~10dB
The number of Mute/Un-mute attempts is user-configurable:

1.Recovery attempt time
2.Initial time between attempts
3.Multiplication factor for attempt time
4.Number of retries
5.Enable / Disable
Users are advised to maintain Factory Defaults
Please Note:
Every recovery attempt will cause a brief traffic hit in the working link
2+0 2U Setup
2 IDUs are installed in each node using an enclosure shelf
We assume slot 1 is using Vertical polarization and slot 2 Horizontal polarization
V+h
Each node includes
2 x RFU-C h/v
Coupler
Dual pole antenna
H+v
H H
v v
PAGE 343 5
10/5/2010
6+0 2U Setup
6 IDUs are installed in each node using enclosure shelves
Possible configurations:
Sl
Slott 1 + slot
l t2
slot 3 + slot 4
slot 5 + slot 6
EMS Configuration
PAGE 344 6
10/5/2010
Logging in
Extension
Main
1. Log in to the EMS
2. Execute the following steps to Main IDU and

E t i IDU on b
Extension th ends
both d off th
the lilink
k
3. When configuring an IDU, make sure the relevant

unit is selected (a black line will highlight selected IDU)
Versions
Check that your IDUs and ODUs are installed with the required version
(6.6.1 or higher)
PAGE 345 7
10/5/2010
XPIC Script
Apply the required script to both IDUs (Main & Ext.) on both ends:
1. Expand the + icon next to the script in the MRMC Table

2 Click the Apply
2. Apply button
3. IDU will automatically restart to apply the new script
XPIC Script - 2
When IDUs complete the reset process, verify XPIC script is successfully
assigned.
PAGE 346 8
10/5/2010
XPIC Configured
Verify Main View in GUI shows icon next to IDUs
Radio Parameters
1. Verify that no alarms exist in the system.
2. Clear the defected blocks counter and verify that there are no errors in the
system.
3. Read the MSE and XPI and verifyy that theyy fit the link design
g ((if no values
are defined, verify that they are below -34dB and above 25dB, respectively).
PAGE 347 9
10/5/2010
Radio Parameters scroll down to bottom of page
Configure Radio Parameters and verify both links (H+V) are operational
Troubleshooting
PAGE 348 10
10/5/2010
Link Commissioning
1. Make sure IF Cables are identical in length (H and V)
2. Commission the H link as a single link system with V channel muted,

verify RSL and MSE are as expected
3. Commission the V link as a single link system with H channel muted,

verify RSL and MSE are as expected
4. Check stability of RSL readings
5. Upon confirming the above steps, proceed to configure XPIC as explained

in previous slides
Improving XPI Levels

When XPI levels < 25, antenna feeders need to be re-aligned.
One of the parameters that impacts the XPI is the antenna XPD
(Cross Polarization Discrimination) -
In the following steps, we shall measure the antenna XPD to determine the
XPD of each antenna
1. Mute H transmitters on both ends: H link is irrelevant now
2. Measure RSL on H receivers: we measure the v interference now
3. Measure RSL on V receivers calculate the difference between V and H
TX = OFF TX = OFF
RSL = -70dBm
70dBm
In this example, the XPD is
not good enough:
The difference is only 20dB
We need to aim for a bigger RSL = -50dBm

difference (better XPI)
H H
v v
PAGE 349 11
10/5/2010
Improving XPI Levels

4. Re-align the antenna feeders to read a bigger difference:
RSLH RSLV > 25dB

5. Un-mute the H transmitters
6. Repeat steps 1-4 for the V link
TX = OFF TX = OFF
78dBm
RSL = -78dBm
In this example, the XPD is
much better:
The difference 28dB

RSL = -50dBm
That means, XPI = 28dB
H H
v v
XPIC Events (EMS Event Log)
During the XPIC mechanism, events are displayed in the EMS Event log to
allow detailed description and effective troubleshooting
Various cases are encoded as a single event with a bitmask code
Event title = Insufficient conditions for XPIC
Bitmask Codes -
PAGE 350 12
10/5/2010
XPIC Events (EMS Event Log)
The following events indicate changes in the XPIC state:
Remote TX Mute (try # n) was Set by XPIC Recovery on Slot # n

Remote TX Un-mute (try # n ) was Set by XPIC Recovery on Slot # n
XPIC Recovery Started on Slot # n
XPIC Recovery Finished Successfully on Slot # n
XPIC Recovery Finished Unsuccessfully on Slot # n. Remote Mute was Set
XPIC Recovery on Slot # n Stopped Due to an External Event
XPIC Recovery (XRSM) was disabled
XPIC Recoveryy (XRSM)
( ) was enabled
XPIC Events (EMS Event Log) - Example
PAGE 351 13
10/5/2010
XPIC Performance Monitoring
Thank You!
Should you require further information, please contact us at
PAGE 352 14
8/12/2010
FibeAir IP10G
HSB / 1+1 Protection
Agenda
GeneralGuidelines
Protection Panel
ProtectionPanel
IntroductiontoExternalProtection
IntroductiontoShelfProtection
FloatingIP
EMSGUIConfiguration
ExternalProtectionProcess:1+1fromscratch
ExternalProtectionProcess:Upgrading1+0to1+1
Troubleshooting
Everybody needs Protection
PAGE 353 1
8/12/2010
General Guidelines
1. A Standby IDU is referred to as the Mate
2. When a switchover occurs, the Active IDU becomes Standby and the
Standby
Standby IDU becomes Active
Active
3. Accessing a Mate IDU can only be done via the Active IDU
4. Accessing the "Active" IDUs is achieved via unique IP addresses or via

Floating IP (supported only with IP-10G)
5. Y-Split cables must be used for Ethernet signals (fiber optics)
6. ETH Cross Cable (Protection Cable) is used to connect the protection ports
of both IDUs:
With IP-10 - use ports number 4

With IP-10G in a standalone mode use the dedicated PROT port
Protection Panel
high low
Active Active
Coupler Coupler
Mate Mate
high low
A Protection Panel (green) can be installed Active

between Active & Mate to allow a single
connection to customers DDF.
The Protection Panel has E1/DS1

connectors to support simultaneous
connectivity to IDUs and DDF.
Mate
PAGE 354 2
8/12/2010
External Protection
Achieved by using two standalone IDUs

The IDUs must be connected by an Ethernet Cross cable (dedicated protection ports)
Each IDU must have a unique IP address
Protection Panel may be in use (supports TDM only)
high low
Coupler Coupler
high low
Shelf Protection
When enabling a Shelf Protection, the following rules should be applied:
Shelf backplane replaces the external Protection Cable

Never insert or extract an IDU while powered up
Always secure IDUs to shelf enclosure with provided screws
Protection can be enabled in each pair (1+2, 3+4, 5+6)
IDU in slot 1 & 2 must have a unique IP address
6 Mate
5 Active Standalone
4 Mate
4Mate
Example:
Standalone
3 Active
2Mate
Standalone
1Active
Protected node Unprotected site
PAGE 355 3
8/12/2010
Floating IP
The Floating IP address feature is meant to provide a single IP address that will
always give direct access to the current active main unit.
1. The Floating IP and Unique IDU IPs must be in the same subnet
2
2. The Floating IP and Unique IDU IPs are user
user-configurable
configurable
3. The Floating IP is copied from Active to Mate (following Copy to Mate command)
4. When Protection is applied, the Floating IP is assigned to the STBY IDU which
becomes the Active
5. The extension IPs are irrelevant (unseen by network)
6. OSS & NMS can access all IDUs (Main and Extension) via SNMP
7. Alternatively, users may access any of the units using their local IP addresses
IDU
IDU
192.168.1.75
192.168.1.72
IDU
192.168.1.71
192.168.1.100
Setup Example (Standalone IDUs)
PAGE 356 4
8/12/2010
EMS GUI
EMS GUI
1. Configure unique IPs to slot 1 and slot 2 (when not in installed in shelf)
2. You may use a floating IP
3. Make sure all IPs are in the same subnet
PAGE 357 5
8/12/2010
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.
EMS GUI
Protection
modestatus
When2nd IDUis
properly
configuredand
connected,IP
andMACare
displayedhere
PAGE 358 6
8/12/2010
EMS GUI
Clickheretocheck
communication
withSTBYunit
EMS GUI
Toforceaswitchover
regardlessto2nd IDU AdminStateLock
qualifyingstatus
changetoONandclick
Apply
PAGE 359 7
8/12/2010
EMS GUI
Torequestaswitchover
clickhere.
If2nd IDU(Mate)does
notqualifytoActive
state,requestisignored.
EMS GUI
Clickheretocopytheconfigurationfrom
ActivetoMate
Pleasenote
Thefollowingparametersarenot copied:
MNGmode(InBand/OOB)
InBandVLAN
Switchmode
license
PAGE 360 8
8/12/2010
Configuring external 1+1 from scratch
Configuring external 1+1 from scratch (1)
1. Set all IDUs to factory defaults
2 When
2. Wh IDU
IDUs complete
l t th
the b
booting
ti sequence, verify:
if
All IDUs have the same HW version

All IDUs have the same SW version
All IDUs have the same license
Every IDU has unique IP address
Active and STBY have the same SW mode (Pipe / Managed / Metro)
All IDUs have the same Management mode (In band or OOB)
IIn case off IIn-Band,
B d allll IDU
IDUs h
have th
the same IIn-Band
B d 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.
PAGE 361 9
8/12/2010
3. Install the 1st link (make sure radio is up)
ODU ODU
4. Enable Protection on both IDUs (management will be lost for 60 sec)
5. Lock Protection on both IDUs (to avoid unnecessary switchover when 2nd IDU
is enabled)
6. I t ll 2ndd IDU iin each

6 Install h site
it (no need to configure it)
ODU ODU
ODU ODU
7. Enable protection in 2nd IDU in each site
8. Connect ETH Cross Cable between both protection ports
ODU ODU
ODU ODU
9. Disconnect the MNG cables.

10. Connect the PC to IDUs via ETH Y-Cable:
ODU ODU
PC
ODU ODU
PAGE 362 10
8/12/2010
11. Verify Active IDU shows Mates IP address
12. Verify there are no Configuration Mismatch alarms
13. Verify there are no Mate Communication failures
14. Complete system setup by configuring Active IDU
15. In Active IDU: click Copy to Mate and verify Mate is restarting
16. Unlock protection on Active IDUs
17. Initiate Manual Switchover / Forced Switchover: verify traffic is OK.
Upgrading (1+0) to (1+1)
PAGE 363 11
8/12/2010
1. Assuming 1st link operates well, configure the 2nd IDUs to match
Active IDUs:
2nd IDUs has the same HW version as Active IDU

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

ODU ODU
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
PAGE 364 12
8/12/2010
5. Enable protection in 2nd IDU in each site
6. Connect ETH Cross Cable between both protection ports
ODU ODU
ODU ODU
7. Disconnect the MNG cables.
8. Connect the PC to IDUs via ETH Y-Cable
9. Verify Active IDU shows Mates 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.
PAGE 365 13
8/12/2010
Troubleshooting Protection
Common issues followed by CLI commands
Troubleshooting
Alarm / Error Probable Cause / Workaround
1. Protection cable is not connected

2. ETH straight cable is connected instead of cross-
Protection LED is on (RED)
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 accessed

I cannot PING the STBY unit.
directly, only via Active IDU
C commands to verify
Use CLI f this IDU is in S
STBY mode, iff
Main IDU does not respond to PING
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
PAGE 366 14
8/12/2010
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
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>
PAGE 367 15
8/12/2010
To force a switchover, type the following:
IP-10:/platform/mate-idu> set protection-force-switch <on/off>
To request a manual switchover, type the following:
IP-10:/platform/mate-idu> manual-switch-cmd
To initiate a Copy-to-Mate process, type the following:
IP-10:/platform/mate-idu> copy-to-mate-cmd
Post-Configuration Changes
1. Changes should be applied to the mate IDU first

2. Initiate a switchover
3. Apply the changes to the new Mate IDU (previously used as Active)
Such changes may include

Setting a new In-Band VLAN
In-Band to OOB or vice versa
Frequencies
Etc.
PAGE 368 16
8/12/2010
ThankYou!
33
PAGE 369 17
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

1 PAGE 370
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

2 PAGE 371
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)

3 PAGE 372
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

4 PAGE 373
Configuration
Switch Configuration Mode and VIDs

5 PAGE 374
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

6 PAGE 375
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

7 PAGE 376
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

8 PAGE 377
Remote MEPs not defined yet
RIGHT IP-10
Enable CCM on both IDUs

LEFT IP-10
RIGHT IP-10

9 PAGE 378
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

10 PAGE 379
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)

11 PAGE 380
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

12 PAGE 381
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

13 PAGE 382
D1S2 Enable CCM on both IDUs
MEP 3
MEP 4
D1S2 Add Remote MEPs on both IDUs
MEP 3
MEP 4

14 PAGE 383
D1S2 Service is now ready for monitoring
D2S2 another service on another Domain
D2S2
5
6

15 PAGE 384
D2S2 another service on another Domain
Adding Local MEPs
Local MEP 5
Remote MEP 6
Local MEP 6
Remote MEP 5

16 PAGE 385
Enabling CCMsAdding 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

17 PAGE 386
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

18 PAGE 387
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

19 PAGE 388
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

20 PAGE 389
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

21 PAGE 390
Automatic Linktrace
Click Linktrace SELECTED
Thank You !
training.ceragon.com
44

22 PAGE 391
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 392 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 393 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 394 3
3/7/2010
IF Loopback Analysis using Event Log

Lets assume radio link is down LINK LED is RED
16:29:01 We enable IF LB, therefore Link alarms clear
16:29:05 Loopback replaces remote unit therefore alarm disappears
16:30:01 Loopback automatically stops, link recovers to original state
16:30:05 Radio link is down (original state)
PDH Line LB towards Line (NE)
LB towards the line
PAGE 395 4
3/7/2010
PDH Line LB towards Line (Near End)
Use this feature to evaluate connection to customers patch-panel
Alarm is displayed in CAS:
and in Event Log:
PDH Line LB towards Radio (FE)
LB towards the radio
Tester
PAGE 396 5
3/7/2010
PDH Line LB towards Radio Event Log Analysis

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

Towards System signal (trail) is looped back to
IP-10
PAGE 397 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 398 7
3/7/2010
Thank You !
15
PAGE 399 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 400 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 401 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 402 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 403 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 404 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 405 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 406 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 407 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 408 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 409 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 410 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 411 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 412 13
3/7/2010
Thank You !
27
PAGE 413 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 414 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 415 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 416 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 417 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 418 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 419 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 420 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 421 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 422 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 423 10
3/7/2010

EMS Security Configuration
Agenda
SSH
HTTPS
SFTP
Users & Groups
Password
PAGE 424 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-10s "public key".
Key exchange algorithm is RSA.
Supported Encryptions: aes128-cbc, 3des-cbc, blowfish-cbc, cast128-cbc,
arcfour128, arcfour256, arcfour, aes192-cbc, aes256-cbc, aes128-ctr,
aes192-ctr, aes256-ctr.
MAC (Message Authentication Code): SHA-1-96 (MAC length = 96 bits, key
length = 160 bit). Supported MAC: hmac-md5, hmac-sha1, 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 425 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 IDUs
digital certificate:
The upload will be done by using FTP/SFTP (s

The public key file will be in PEM format.
Click Upload Public Key
The status of the upload operation can be monitored. The returned status
values are: ready (default), in-progress, success, failed. In any case
of failure, an appropriate error message will appear.
PAGE 426 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 427 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 IDUs private key.
If one of the above tests fails, the operation will return an appropriate error
indication.
Open WEB Browser and type the URL https:\\<IP of target IDU>.
Note:
This parameter is NOT copied when copy to mate operation is initiated,
for security reasons (unsecured unit should not be able to override security
parameters of secured unit).
SFTP (Secure FTP)
SFTP can be used for the following operations:
Configuration upload/download,
Upload the unit info.
Upload public key.
Download certificate files.
SW download
PAGE 428 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 429 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 430 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 431 8
3/7/2010
Thank You !
17
PAGE 432 9
Annexes
PAGE 433
FibeAir IP-10
License
Management
Guide
Part ID: BM-0139-0

Doc ID: DOC-00019183 Rev a.00
November 2008
PAGE 434
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.
Statement of Conditions
The information contained in this document is subject to change without notice.
Ceragon Networks Ltd. shall not be liable for errors contained herein or for incidental or
consequential damage in connection with the furnishing, performance, or use of this
document or equipment supplied with it.
Information to User
Any changes or modifications of equipment not expressly approved by the manufacturer
could void the users authority to operate the equipment and the warranty for such equipment.
Copyright 2008 by Ceragon Networks Ltd. All rights reserved.
Corporate Headquarters: 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 435
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 436
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 SystemPAGE 437 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.
FibeAir IP-10 License Management System PAGE 438 2

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

FibeAir IP-10G
SW Version I6.6.1
CLI
(Command Line Interface)
User Guide
August 2010
PAGE 463
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.
TradeMarks
CeraMapTM, PolyViewTM, EncryptAirTM, ConfigAirTM, CeraMonTM, EtherAirTM, and MicroWave FiberTM, are
trademarks of Ceragon Networks Ltd.
Statement of Conditions
The information contained in this document is subject to change without notice.
Ceragon Networks Ltd. shall not be liable for errors contained herein or for incidental or consequential
damage in connection with the furnishing, performance, or use of this document or equipment supplied
with it.
Information to User
Any changes or modifications of equipment not expressly approved by the manufacturer could void the
users authority to operate the equipment and the warranty for such equipment.
Copyright 2010 by Ceragon Networks Ltd. All rights reserved.
FibeAir IP-10G CLI User Guide - I6.6.1 PAGE 464 2

Contents
General ............................................................................................................................................. 5
Getting Started ................................................................................................................................ 6
Command Groups ......................................................................................................................... 13
CLI Commands .............................................................................................................................. 16
CLI Command Parameters ........................................................................................................... 26
CLI Procedures .............................................................................................................................. 67

General
This guide explains how to work with the FibeAir IP-10 Command Line Interface (CLI).
The CLI is used to perform IP-10 configuration and obtain system statistical and performance information.
Using the CLI, you can perform configuration operations for single IP-10 units, as well as configure several
IP-10 units in a single batch command.
Access Rights
IP-10 CLI access is granted for the following user groups:
Viewer This user only has read-only access. The user can only view parameters and their values, not
modify them.
Operator This user has read-write access. The user can read parameters and their values, and modify
them. However, this user cannot add or remove other users.
Admin This user has read-write access. The user can read parameters and their values, modify them,
and add/remove other users.
Technician This user has read-write access to the OS CLI.
User access is controlled by the system Administrator and configured via the Management command group
(shown in the Command Groups section).

Getting Started
To log in to the CLI:
1. Power on your PC.
2. Make sure that your PC is connected to the management port on the front panel of the IP-10 unit.
3. Open telnet application as follows: telnet <IP address of the unit> + Enter
4. For a first-time login, use the following
User: Admin
Password: Admin
Note: When using the Hyper Terminal, you should set the terminal speed (in your PC terminal
configuration) to 155200 kpbs. In addition, it is recommended to select the VT-100 terminal type and set the
terminal size to 24 rows, 80 columns.
Getting Help
Once you are logged in, you can go to a main command group and its sub groups, type the command you
want, and press Tab twice for a list of possible parameter values.
In addition, you can type a command and then type a question mark (?) for location-specific information for
the command. For example, for the set command, typing set ? and pressing Enter will display a list of
optional parameters and a help line.
Wherever you are in the command tree, you can obtain a list of available commands by typing Help or ?.
The commands that are available are different for each location in the CLI tree and the type of user.

Basic Commands
The following basic commands are available when you first log in, if you belong to the Operator user group:
ls list entities
get get parameter
set set parameter
help help
cd change directory
exit exit CLI
logout logout from CLI
cli-ver cli version
cls clear screen
write write the current switch configuration to the configuration file
show-tree show entity tree
find search for a string in the parameter name and information fields
lsp list entity parameters and commands
In addition, you can use the up/down arrow keys, or the q key, when the word END appears at the end of
the screen.
Setting IP Addresses
To define a new IP address, do the following:
1. Log in as follows:
User: Admin or Operator
Password: Admin
2. At the command prompt, type: cd management\networking\ip-address\, and press Enter.
3. Type: get ip-address, and press Enter.

This will give you the current IP address.
4. Type: set new_ip_address, and press Enter.

For new_ip_address, enter the new address.

Finding Commands
At any point in the CLI tree, a quick way to find a command is to type find string, and press Enter.
For string you can type any word that you think is relevant for a command.
For example, if you type find user, and press Enter, you would get a list of commands relating to "user", as
follows:
1) management/mng-services/users/add-user Add user <name> <group>

2) management/mng-services/users/delete-user Delete user <name>
3) management/mng-services/users/show-users Show users
Command Example
The following example shows how you can find a command within a sub-group, and then execute the
command. The example starts with the lsp (list parameters) command, and ends with the activation of an
interface loopback test.
-----------------------------------------------
IP-10:/> cd diagnostics/loopback/radio-loopback/
IP-10:/diagnostics/loopback/radio-loopback> lsp
*********** configuration ********
timeout rw Loopback timeout in minutes
*********** statuses *************
counter ro Loopback time left
if-loopback rw IF loopback activation
rfu-rf-loopback rw RFU RF Loopback Enable Command
IP-10:/diagnostics/loopback/radio-loopback> set timeout 2

IP-10:/diagnostics/loopback/radio-loopback> set if-loopback
off on
IP-10:/diagnostics/loopback/radio-loopback> set if-loopback on
Caution: This action affects traffic.
The may cause permanent loss of Ethernet traffic & wayside.
Consider disabling or physically disconnecting the Ethernet ports of the IDM and
Wayside before the loopback activation.
Are you sure? (yes/no):yes
IP-10:/diagnostics/loopback/radio-loopback>
-----------------------------------------------
Important!
Note that bridge related commands need to be followed by a write command to be saved.
Otherwise, the commands will not be saved following a reset in the system.

Viewing the Command Tree
At any location within the command group structure, you can type show-tree and press Enter for a list of all
the commands in the group you are currently in.
The following list appears when you type show-tree.
IP-10-SLOT-1:/>show-tree
management
mng-services
cfg-service
event-service
event-log
alarm-service
alarm-current
alarm-external
pm-service
time-service
ntp
mng-software
users
networking
ip-address
floating-ip-address
mng-protocols
snmp
platform
inventory
daughter-board
license
idc-board
fpga
mate-idu
all-odu
shelf-manager
remote-idu
remote-co
remote-cl
radio

xpic
remote-cl
framer
mrmc
tdm-radio-pm[1]
tdm-radio-pm[2]
tdm-radio-pm[3]
tdm-radio-pm[4]
tdm-radio-pm[5]
tdm-radio-pm[6]
tdm-radio-pm[7]
tdm-radio-pm[8]
tdm-radio-pm[9]
tdm-radio-pm[10]
tdm-radio-pm[11]
tdm-radio-pm[12]
tdm-radio-pm[13]
tdm-radio-pm[14]
tdm-radio-pm[15]
tdm-radio-pm[16]
tdm-radio-pm[17]
tdm-radio-pm[18]
tdm-radio-pm[19]
tdm-radio-pm[20]
tdm-radio-pm[21]
tdm-radio-pm[22]
tdm-radio-pm[23]
tdm-radio-pm[24]
tdm-radio-pm[25]
tdm-radio-pm[26]
tdm-radio-pm[27]
tdm-radio-pm[28]
tdm-radio-pm[29]
tdm-radio-pm[30]
tdm-radio-pm[31]
tdm-radio-pm[32]
tdm-radio-pm[33]

tdm-radio-pm[34]
tdm-radio-pm[35]
tdm-radio-pm[36]
tdm-radio-pm[37]
tdm-radio-pm[38]
tdm-radio-pm[39]
tdm-radio-pm[40]
tdm-radio-pm[41]
tdm-radio-pm[42]
tdm-radio-pm[43]
tdm-radio-pm[44]
tdm-radio-pm[45]
tdm-radio-pm[46]
tdm-radio-pm[47]
tdm-radio-pm[48]
tdm-radio-pm[49]
tdm-radio-pm[50]
tdm-radio-pm[51]
tdm-radio-pm[52]
tdm-radio-pm[53]
tdm-radio-pm[54]
tdm-radio-pm[55]
tdm-radio-pm[56]
tdm-radio-pm[57]
tdm-radio-pm[58]
tdm-radio-pm[59]
tdm-radio-pm[60]
tdm-radio-pm[61]
tdm-radio-pm[62]
tdm-radio-pm[63]
tdm-radio-pm[64]
tdm-radio-pm[65]
tdm-radio-pm[66]
tdm-radio-pm[67]
tdm-radio-pm[68]
tdm-radio-pm[69]
tdm-radio-pm[70]

tdm-radio-pm[71]
tdm-radio-pm[72]
tdm-radio-pm[73]
tdm-radio-pm[74]
tdm-radio-pm[75]
tdm-radio-pm[76]
tdm-radio-pm[77]
tdm-radio-pm[78]
tdm-radio-pm[79]
tdm-radio-pm[80]
tdm-radio-pm[81]
tdm-radio-pm[82]
tdm-radio-pm[83]
tdm-radio-pm[84]
modem
rfu
rfu-sw-upload
rfu-co
rfu-cl
rfic
interfaces
wayside
sync
ethernet
bridge
eth-port[1]
eth-port[3]
eth-port[6]
eth-port[7]
eth-port[8]
service-oam
pdh
port-group
e1t1-port[1]
e1t1-port[2]
e1t1-port[3]
e1t1-port[4]

e1t1-port[5]
e1t1-port[6]
e1t1-port[7]
e1t1-port[8]
e1t1-port[9]
e1t1-port[10]
e1t1-port[11]
e1t1-port[12]
e1t1-port[13]
e1t1-port[14]
e1t1-port[15]
e1t1-port[16]
trails
sdh
stm1
diagnostics
rmon
loopback
line-loopback
radio-loopback
xml-interface

Command Groups
The command groups that appear when you log in include the following:
Management
Platform
Radio
Interfaces
Diagnostics
Some groups include sub groups that enable setup operations relevant to that category.
The following illustrations show the trees of each main group.
Management
Management

Platform
Radio

Interfaces
Diagnostics

CLI Commands
The following table lists the commands you can use in each command group and sub group.
Note that when you enter a group or sub group, you can type a command and then press the Tab key twice
(or type a question mark) for a list of values relevant to that command.
CommandGroup Command Description Privilege

IP-10G echo Display a line of text operator
IP-10G write Write the current switch operator
configuration into
configuration file
IP-10G show-tree Show entity tree rw
IP-10G find Search for a string in the rw
parameter's entity name

and information fields
IP-10G lsp entity name and rw
information fields list entity

parameters and
commands
Mng-services ping Ping utility operator
Mng-services telnet Telnet utility operator
cfg-service set-to-default Set to factory default operator
configuration
Event-log show Show log rw
Event-log clear Clear log operator
alarm-current show Show current alarms rw
pm-service clear-entire-pm Clear entire PM operator
mng-software versions-idu Show IDU application operator
packages set versions
mng-software versions-rfu Show supported RFU operator
version
mng-software verify-packages Verify installed packages operator
mng-software download Download newer operator
packages from remote
server (without
installation)
mng-software upgrade Upgrade all installed operator
packages or requested
package

mng-software rollback Rollback recent IDU Admin
application upgrade
transaction (1 step back).
CAUTION:
mng-software downgrade Downgrade application Admin
packages to older version
(downloaded to special
downgrade directory)
mng-software kernel-reinstall Re-install last installed Admin
Linux kernel package
(recommended for corrupt
kernel restoration)
mng-software package-download Download new package admin
(without existing version
installed) from remote
server (without
installation). NOTE:
provide
package name without
version, e.g. 'abc', not
'abc-0.0.1'.
mng-software package-install Download and install new admin
package (without existing
version installed). NOTE:
provide package name
without version, e.g. 'rfu',
not 'rfu-0.0.1
mng-software package-uninstall Uninstall SW package admin
(recommended for
independent package
removal)
mng-software show-packages Show SW packages operator
mng-software cleanup Clean up disk from old operator
duplicated (kernel)
packages and repackaged
files,or downgrade files
mng-software change-server- Change remote server admin
password password
Users add-user Add user into system's admin
users account.
syntax:add-user <user>
<privilege> <passwd
aging in day amounts>
[account expired YYYY-
MM-DD]

Users delete-user Delete user from system's admin
users
account. Syntax: delete-
user <user> show-users
Show information about
exist users
account
users show-users Show information about admin
exist users account
users change-password Change user's password. rw
syntax:
change-password
(without parameters)
floating-ip-address set-fip-lock-timer Set Floating IP lock timer operator
mng-protocols status-show Show Management operator
Protocols status
mng-protocols web-restart restart the web server admin
Snmp status-show Show SNMP status operator
snmp change-user-settings Change the settings of the admin
SNMPv3 user (security
level / username /
password)
idc-board reset-idc-hw Reset the IDC - cold operator
(HW) reset
idc-board create-archive Create archive file on operator
target
idc-board install-archive Install the requested admin
archive file on target
idc-board upload-archive Upload the archive file to operator
the PC
(host). Before activating
this command, make sure
to set host-ip, host-path,
user-name and user-
password
idc-board download-archive Get the archive file from operator
the PC (host) onto the
target. Before activating
this command, make sure
to set host-ip, host-path,
user-name and user-
password

idc-board change-user-password Change user password for operator
the ftp session. When
using default user name
(anonymous), use PC
(host) login as password
idc-board cli-script Execute, show or delete a Operator
CLI configuration script
mate-idu Show configuration operator
cfg-mismatch-details
mismatch details
mate-idu copy-to-mate-cmd Copy to mate command operator
mate-idu manual-switch-cmd Manual switch command operator
shelf-manager logon-unit Logon other unit's CLI Rw
shell
shelf-manager reset-unit Reset unit operator
shelf-manager reset-shelf Reset shelf operator
shelf-manager reset-extensions Reset extension units operator
shelf-manager shelf-versions Show units SW versions rw
information
shelf-manager cfg-backup-show Show units configuration rw
backup information
shelf-manager config-backup Backup other unit(s) operator
configuration on this Main
unit's storage device
shelf-manager config-restore Restore this and/or admin
other unit(s) configuration
from this Main unit's
backup file(s)
shelf- manager shelf-info-create Create information archive operator
including snapshot info for
all available units
remote-idu remote-reset-idc-hw Reset the remote IDC - operator
cold (HW) reset
remote-idu force-unmute Force Remote Unmute operator
Command
remote-co clear-device-error clear device error counter operator
remote-cl clear -device- error clear device error counter operator
mrmc change-script-cmd Change modem script operator
command
modem clear-counters Clear accumulated operator
counters

Rfu clear-com-device-error Clear RFU Com device operator
error
Rfu automatic-delay- RFU Automatic Delay
operator
calibration Calibration Command
internal-fw-download- Set Internal FW Download
rfu-fw-upload operator
action action
internal-fw-download- Set Internal FW Download
rfu-fw-upload operator
cancel cancel
rfu-sw-upload internal-sw-download- Set Internal SW Download operator
action action
rfu-co clear-device-error clear IDU device error operator
counter
rfu-cl clear-device-error clear device error counter operator
sync set-sync-source set-sync-source trail operator
<slot> <if-type> <if-num>
sync view-sync-source view-sync-source operator
ethernet set-gbe-mute-override Set GbE mute override operator
ethernet show-gbe-mute- Show GbE mute override rw
override
bridge show-ports-status Show status of all ports rw
bridge show-eth-statistics Show Ethernet Statistics rw
bridge show-all-traffic-statistic Show ethernet statistics rw
for all ports
bridge show-forwarding-table Shows the forwarding rw
table for a
specific VLAN
bridge qos-copy-priorities- Copy priority operator
configuration configuration from one
port to another
bridge qos-copy-rate-limiting- Copy rate limiting operator
configuration configuration from one
port to another
bridge qos-set-vlan-tag-pbit- Set VLAN tag pbits to operator
val queue allocation
bridge qos-show-vlan-tag- Show VLAN tag pbits to rw
pbit-val queue allocation
bridge qos-set-ip-pbit-val Set IP pbits to queue operator
allocation
bridge qos-show-ip-pbit-val Show IP pbits to queue rw
allocation

bridge qos-vlan-to-queue QoS VLAN to queue rw
priority
bridge qos-show-vlan-to- Show QoS VLAN to rw
queue queue priorities
bridge qos-set-scheduler-q- Set scheduler queue operator
weight weights
bridge qos-show-scheduler-q- Show scheduler queue rw
weight weights
bridge qos-policer Add/Remove a policer operator
bridge qos-policer-class Add/Remove a policer operator
class
bridge qos-show-policers Show QoS policers rw
bridge qos-static-mac-priority Set/Remove a static MAC operator
priority
bridge qos-show-static-mac- Show static MAC priorities rw
priorities
bridge clear-all-peer-info Clear all peer's operator
information
bridge show-bridge-status Show the bridge status rw
Showcurrentswitch
bridge showrunningconfig rw
operatingconfiguration
bridge showvlaninfo ShowVLANdatabase rw
Add,remove,ormodify
bridge vlan valuesassociatedwitha operator
singleVLAN
eth-port show-port-status Show port status rw
eth-port qos-set-vlan-pbits-prio- Set VLAN Pbits priority operator
remap remap
eth-port qos-show-vlan-pbits- Show VLAN Pbits priority rw
prio-remap remap
eth-port mep Add/Remove an MEP operator
eth-port show-meps-list Show MEPs list operator
eth-port show-if-table-counters Show IF table counters operator
eth-port clear-rmon Clear RMON statistics operator
eth-port qos-detach-policer Detach policer map from operator
the port
eth-port qos-show-policer- Show policer classes rw
classes
eth-port clear-peer-info Clear all peer's operator
information

eth-port show-allowed-vlans Show allowed VLANs rw
eth-port Mip Add/Remove MIP operator
eth-port show-mips-list Show MIPs list operator
eth-port set-allowed-vlans Set allowed VLANs operator
service-oam domain Add/Modify/Remove a operator
maintenance domain
service-oam association Add/Modify/Remove a Operator
maintenance association
service-oam remote-mep Add/Remove a remote operator
MEP
service-oam ccm-Admin Change continuity check operator
Admin state
service-oam ccm-interval Change continuity check operator
interval time
service-oam ping Ping message to a remote rw
MEP or MIP
service-oam linktrace Traceroute message to a rw
remote MEP or MIP
service-oam auto-linktrace Add/Remove a remote operator
MEP to the automatic
linktrace list
service-oam show-auto-linktrace-list Show the remote MEPs rw
configured in the
automatic linktrace list
service-oam show-configured-local- Show all local MEPs info rw
meps
service-oam show-configured- Show all remote MEPs rw
remote-meps info
service-oam show-domain-list Show Maintenance rw
domain list
service-oam show-domain-interval Show domain & VLAN rw
CCM interval
service-oam show-auto-linktrace- Show last auto linktrace rw
mep-status result for a remote MEP
service-oam show-auto-linktrace- Show last auto linktrace rw
maid-stat us result for all MAID remote
MEPs
service-oam show-maid-list Show the MAID list rw
service-oam show-local-meps-list Show the local MEP list rw
service-oam show-remote-meps-list Show the remote MEPs rw
list

service-oam show-mips-list Show domain & VLAN rw
MIPs list
port-group disable-all-ports Disable all E1/DS1 ports operator
port-group enable-all-ports Enable all E1/DS1 ports operator
Add/Remove eth-port rw
lag-port lag-member
to/from aggregation group
qos-show-vlan-pbits- Show VLAN Pbits priority rw
lag-port
prio-remap remap
lag-port show-allowed-vlans Show allowed VLANs rw
lag-port show-port-status Show port status rw
aggregate-port Add/remove port from
lag-port operator
aggregation group
clear-peer-info Clear all peer's
lag-port operator
information
Clear RMON statistics of a
lag-port lag-clear-rmon operator
LAG-port
Remove aggregation
lag-port lag-port-remove operator
group
lag-port mep Add/Remove a MEP operator
lag-port mip Add/Remove MIP operator
qos-set-vlan-pbits-prio- Set VLAN Pbits priority
lag-port operator
remap remap
lag-port set-allowed-vlans Set allowed VLANs operator
lag-port show-if-table-counters Show IF table counters operator
lag-port show-meps-list Show MEPs list operator
lag-port show-mips-list Show MIPs list operator
trails add-trail Add a Trail: add-trail <id> operator
<desc> <acm-prio>
<activation> <protected>
<src-slot> <src-type>
<src-num> <dest1-slot>
<dest2-type> <dest3-
num> ... <dest9-num>
Trails del-trail-by-src Delete a Trail by Source: operator
del-trail-by-src <src-slot>
<src-type> <src-num>
trails del-trail-by-id Delete a Trail by ID: del- operator
trail-by-id <id>

trails act-trail-by-id Activate(or Reserve) a operator
Trail by ID: act-trail-by-id
<id> <operatioal/
reserved>
trails show-trail-by-src Show a Trail by Source operator
Edge
show-trail-by-src <src-slot-
id>
<src-if-type> <src-if-num>
trails show-trail-by-id Show a Trail by Trail ID rw
show-trail-by-id <id
trails show-all-trails Show all Trails show-all- operator
trails
trails show-all-trail-pms Show all Trails PM show- operator
all-trail-pms
trails show-trail-pms-by-id Show Trail PM's using a operator
trail id show-all-trails <id>
trails show-all-trail-alarms Show all Trails alarms operator
show-all-trails-alarms
trails del-all-trails Delete all Trails del-all- operator
trails
trails act-all-trails Activate (or Reserve) all operator
Trails
trails protected-trail-force- Force active a protected operator
active-by-id trail <id> to
by-id some path
trails protected-trail-force- Force active all protected operator
active trails to some path
trails protected-trail-switch- Reset the switch counter operator
reset for all
protected trails <id>
trails protected-trail-switch- Reset the switch counter operator
reset-by-id for a
by-id protected trail <id>
trails show-trails-statistics Show the trails statistics operator
with options [ts|trails]
trails show-local-trails- Show the local trails admin
statistics statistics with options
[ts|trails]

trails dump-hw-table- Dumpt the HW table admin
configuration configurations for a
device <device> with
options [sum|active]
trails dump-trails-db Dumpt the trail DB for admin
[local|global]
database with options
[sum|active]
trails perform-local-trail- Verify that the local DB admin
consistency-check configuration including
HW is valid
trails add-def-trails Add default Trails (use on
standalone units with
operator
empty database) add-def-
trails
diagnostics show-files-list Show downloadable files operator
rmon get-statistics Get RMON statistics operator
rmon clear-port Clear RMON statistics operator
from a specific port
rmon clear-lag-port Clear RMON statistics of a operator
LAG-port
rmon clear-all Clear RMON statistics Operator
from all ports

CLICommandParameters
Parameter Parameter Description Privileges

Group
Event-log event-to-syslog Event to syslog OPERATOR Rw
alarm- most-severe Most severe alarm VIEWER Rw
current
alarm- external-output.group External alarm group OPERATOR Rw
external
alarm- external-output.Admin External alarm OPERATOR Rw
external output Admin
alarm- external-input.Admin[5] External input alarm OPERATOR Rw
external Admin
alarm- external-input.severity[5] External input alarm OPERATOR Rw
external severity
alarm- external-input.text[5] External input alarm OPERATOR Rw
external text
alarm- external-output External alarm state VIEWER Rw
external
alarm- External-input[5] External input state VIEWER Rw
external
time- dst-offset Daylight Savings OPERATOR Rw
service Time offset
time- dst-start-month Daylight Savings OPERATOR Rw
service Time starting month
time- dst-start-day Daylight Savings OPERATOR Rw
service Time starting day
time- dst-end-month Daylight Savings OPERATOR Rw
service Time ending month
time- dst-end-day Daylight Savings OPERATOR Rw
service Time ending day
time- gmt-offset-hours NTP offset from OPERATOR Rw
service GMT (hours part)
time- gmt-offset-minutes NTP offset from OPERATOR rw
service GMT (minutes part)
time- time-and-date OPERATOR rw
service Time and date
format: day-month-
year,
hours:mins:secs

Group
ntp server OPERATOR rw
NTP server with
which the system is
synchronised
ntp Admin NTP Administrative OPERATOR rw
state
ntp status NTP service status VIEWER ro
ntp poll-interval NTP polling interval VIEWER ro
ntp sync-server VIEWER ro
The NTP server with
which the target is
currently
synchronized.
mng- server-url OPERATOR rw
software Remote SW update
server URL, where
SW
updates reside
mng- server-login Remote server login OPERATOR rw
software
mng- download-status Last SW download VIEWER ro
software status
mng- install-status Last SW installation VIEWER ro
software status
mng- version-package-name Common (version VIEWER ro
software holder) package
name
mng- common-version-idu VIEWER ro
software Identifies installed
IDU application
package set version
mng- running-version-idu VIEWER ro
software Identifies IDU
application common
package version at
last cold restart
mng- common-version-rfu Identifies installed VIEWER ro
software RFU package
version

Group
mng- common-version-rfu-upgrade VIEWER ro
software Identifies RFU
package version for
upgrade
mng- common-version-rfu-downgrade VIEWER ro
software Identifies RFU
package version for
downgarde
mng- Last SW download VIEWER ro
status-download
software status
mng- Last SW installation VIEWER ro
status-install
software status
users login-fail-threshold ADMIN rw
Threshold of
consecutive fail
logins
which cause to
blocking the user's
login. Optional
values: 0-10 (0 is for
disable the
mechanism)
Users blocking-fail-login-time ADMIN rw
The blocking time (in
minutes) after
threshold of
consecutive fail
logins
exceed. Optional
values: 1-1440
users idle-login-time ADMIN rw
Define the idle login
time (in days)
which after that the
user's account
will be deleted.
Optional values 0-90
(0 is for disable the
mechanism)
networking number-of-ports Number of OPERATOR rw
management ports

Group
networking vlan In-Band OPERATOR rw
management VLAN
ID
networking type How management OPERATOR rw
data is passed
networking capacity Management port OPERATOR rw
capacity
networking auto-negotiation Management port OPERATOR rw
auto negotiation
networking duplex Management port OPERATOR rw
duplex
networking ethernet-rate Management port OPERATOR rw
Ethernet rate (Mbps)
ip-address ip-address Unit management IP OPERATOR rw
address
ip-address subnet-mask Unit subnet mask OPERATOR rw
ip-address default-gateway Default gateway OPERATOR rw
ip-address hw-address Hw address VIEWER ro
floating-ip- floating-ip Floating IP OPERATOR rw
address
mng- web-inactivity-timeout Web inactivity OPERATOR rw
protocols timeout, in minutes
mng- web-protocol Web protocol type ADMIN rw
protocols
mng- web-ca-certificate-Admin WEB Certificate ADMIN rw
protocols Authority (CA) digital
certificate
mng- web-Admin HTTP/S channel ADMIN rw
protocols Administrative state
for
web and NMS
access
mng- telnet-Admin Telnet Administrative ADMIN rw
protocols state
mng- communication-inactivity-time out define ADMIN rw
protocols communication
inactivity timeout of
the the management
interfaces
mng- web-status Web service status VIEWER ro
protocols

Group
mng- telnet-status Telnet service VIEWER ro
protocols status
Snmp version SNMP version ADMIN rw
Snmp trap-Admin[4] Enable/disable OPERATOR rw
sending SNMP traps
Snmp trap-manager[4 IP address of OPERATOR rw
manager to which
SNMP traps will be
sent
Snmp trap-port[4] Manager port to OPERATOR rw
which traps are sent
(default is 162)
Snmp trap-severity-filter[4] Filter for traps sent OPERATOR rw
to the manager
according to severity
snmp trap-status-change-filter[4] Send trap on OPERATOR rw
operational status
change only
snmp trap-heartbeat[4] How often (in OPERATOR rw
minutes) a trap
heartbeat is sent to
the manager (0 to
disable)
snmp v3-security-mode SNMPv3 security VIEWER ro
mode
Snmp v3-auth-algorithm SNMPv3 VIEWER ro
authentication
algorith
Snmp Admin SNMP ADMIN rw
Administrative state
Snmp read-community SNMP read OPERATOR rw
community
Snmp write-community SNMP write OPERATOR rw
community
Snmp trap-community[4] SNMP trap OPERATOR rw
community
Snmp trap-clli[4] SNMP trap clli OPERATOR rw
Snmp trap-name[4] Text for manager OPERATOR rw
name or comment
Snmp v3-username SNMPv3 single user VIEWER ro
username

Group
Snmp status SNMP service status VIEWER ro
snmp mib-version Private MIB file VIEWER ro
version
Platform system-services Number of services VIEWER ro
as provided by the
system according to
the rfc3418
Platform lan-id Lan segment i OPERATOR rw
platform system-name System name OPERATOR rw
Platform system-contact-person System contact OPERATOR rw
person
Platform system-location System location OPERATOR rw
platform system-location-bay System location bay OPERATOR rw
platform system-location-shelf System location OPERATOR rw
shelf
platform longitude Unit's longitude OPERATOR rw
coordinates
platform latitude Unit's latitude OPERATOR rw
coordinates
platform slot-label Slot Label OPERATOR rw
Platform max-physical-ports Max number of VIEWER ro
physical PDS ports
Platform max-physical-sdh-ports Max number of VIEWER ro
physical SDH ports
Platform system-description System description VIEWER ro
Platform power-supply-1- OPERATOR rw
power-supply-1-alarm-admin
alarm-admin
Inventory board-type Board type VIEWER ro
Inventory board-sub-type Board sub-type VIEWER ro

Inventory firmware Firmware VIEWER ro
Inventory hardware Hardware VIEWER ro
Inventory board-modules Board modules VIEWER ro
Inventory idc-type The type of IDC VIEWER ro
Inventory idc-sub-type The sub-type of the VIEWER ro
IDC
Inventory idc-firmware IDC firmware VIEWER ro

Group
Inventory idc-hardware-features The hardware VIEWER ro
features of the IDC
Inventory modem-type The type of modem VIEWER ro
Inventory modem-sub-type The sub-type of the VIEWER ro
modem
Inventory modem-firmware The firmware of the VIEWER ro
modem
Inventory modem-system-rate The frequency of the VIEWER ro
clock for the PVG
Inventory modem-hardware-features The hardware VIEWER ro
features of the
modem
Inventory mux-type The type of MUX VIEWER ro
Inventory mux-sub-type The sub-type of the VIEWER ro
MUX
Inventory mux-firmware The firmware of the VIEWER ro
MUX
Inventory mux-hardware-features The hardware VIEWER ro
features of the MUX
Inventory xc-type The type of XC VIEWER ro
Inventory xc-sub-type The sub-type of the VIEWER ro
XC
Inventory xc-firmware The firmware of the VIEWER ro
XC
Inventory xc-hardware-features The hardware VIEWER ro
features of the XC
Inventory chain-type Chain type VIEWER ro
Inventory chain-sub-type Chain sub-type VIEWER ro
Inventory chain-firmware Chain firmware VIEWER ro
Inventory chain-hardware-features Chain hardware VIEWER ro
features
Inventory total-num-of-interfaces Total number of VIEWER ro
interface
Inventory num-of-fe-interfaces Number of fast VIEWER ro
Ethernet interfaces
Inventory num-of-radio-interfaces Number of Radio VIEWER ro
interfaces
Inventory num-of-10-100-1000-interfaces Number of VIEWER ro
10/100/1000
interfaces

Group
Inventory num-of-sfp-interfaces Number of SFP VIEWER ro
interfaces
Inventory num-of-tdm-interfaces Number of TDM VIEWER ro
interfaces
Inventory type-of-tdm-interfaces Type of TDM VIEWER ro
interfaces
Inventory hw-supported-bit-bate HW supported bit VIEWER ro
rate
Inventory date-code Date of board testing VIEWER ro
(number of seconds
from 1/1/1970)
Inventory hass-number Number of hass VIEWER ro
testing
Inventory tx-iq-delay-index-in-fdf-table TX IQ Delay - Tx VIEWER ro
index in fdf table
Inventory tx-iq-delay TX IQ Delay - TX VIEWER ro
Delay
Inventory rx-master-iq-delay-index-in-f df-table RX IQ Delay - Rx VIEWER ro
Master index in fdf
table
Inventory rx-master-iq-delay RX IQ delay - Rx VIEWER ro
Master delay
Inventory rx-slave-iq-delay-index-in-fdf table RX IQ Delay - Rx VIEWER ro
slave index in fdf
table
Inventory rx-slave-iq-delay RX IQ delay - Rx VIEWER ro
slave delay
Inventory num-of-working-hours Counter of working VIEWER ro
hours of the board
Inventory license-demo-timer Number of hours left VIEWER ro
for license demo
mode
Inventory spare1 Spare1 VIEWER ro
Inventory Spare2 Spare2 VIEWER ro
Inventory Spare3 Spare3 VIEWER ro
Inventory pic-version The version of the VIEWER ro
pic
Inventory hw-feature HW features VIEWER ro
Inventory serial-number The serial number of VIEWER ro
the board

Group
Inventory part-number Part number of the VIEWER ro
application in the
board
Inventory license-register System license VIEWER ro
features
Inventory company-name Company name Admin rw
Inventory logo Company logo Admin rw
Inventory main-view Company main logo Admin rw
Inventory product-name Product name Admin rw
daughter- board-type VIEWER ro
board
daughter- board-sub-type VIEWER ro
board
daughter- num-of-interfaces VIEWER ro
board
daughter- running-firmware-version VIEWER ro
board
daughter- firmware VIEWER ro
board
daughter- hardware VIEWER ro
board
daughter- num-of-working-hours Counter of working VIEWER ro
board hours of theDaughter
board
daughter- date-code Date of daughter VIEWER ro
board board testing
(number of seconds
from 1/1/1970)
daughter- hass-number Number of hass DB VIEWER ro
board testing
daughter- serial-number The serial number of VIEWER ro
board the daughter board
daughter- part-number Part number of the VIEWER ro
board application in the
daughter board
daughter- comments Text description VIEWER ro
board about the daughter
board
Inventory comments Text description of OPERATOR rw
the board

Group
Inventory hw-inventory-version The hw inventory VIEWER ro
version
Inventory production-inventory-version The production VIEWER ro
inventory version
License demo-Admin Enable/disable demo OPERATOR rw
mode
License license-code The user license OPERATOR rw

code that determines
the user rights
License capacity-name Capacity rights VIEWER ro
License acm-license ACM rights VIEWER ro
License switch-application-license Switch application VIEWER ro
rights
License license-type Type of license VIEWER ro
License demo-timer Time left for license VIEWER ro
demo mode (in
hours)
License syncu-license VIEWER ro
License network-resiliency-license VIEWER ro
License tdm-capacity-license VIEWER ro
License tdm-capacity-value VIEWER ro
license per-usage-license VIEWER ro
idc-board measurement-system Measurement OPERATOR rw
system
idc-board host-ip IP of the HOST ADMIN rw
where the archive is
to be stored
idc-board file-transfer-protocol Determines whether ADMIN rw
the file transfer
protocol is secure
(SFTP) or not (FTP)
idc-board idc-clli General CLLI field OPERATOR rw

Group
idc-board host-path Relative path (under ADMIN rw
the ftp directory)
on the HOST where
the archive is to be
stored. For using
default ftp path: set
// for Windows or
set / for Linux.
idc-board user-name User name for the ftp ADMIN rw
session
idc-board cli-script-file-name The CLI OPERATOR rw
configuration script's
file name to be
downloaded
idc-board temperature IDU temperature VIEWER ro
idc-board voltage-input Voltage-input VIEWER ro
idc-board system-up-time System up time (in VIEWER ro
hundredths of
seconds)
idc-board warning-banner-download-status Status of VIEWER ro
downloading the
warning banner file
idc-board security-file-type ADMIN rw
idc-board security-file-format ADMIN rw
idc-board config-creation-status Status of the archive VIEWER ro
creation action
idc-board config-upload-status Status of the VIEWER ro
archive storage
action
idc-board config-download-status Status of the archive VIEWER ro
download action
idc-board config-install-status Status of the archive VIEWER ro
download action
idc-board unit-info-creation-status Status of the unit- VIEWER ro
info creation action
idc-board unit-info-upload-status Status of the VIEWER ro
archive storage
action
idc-board upload-pub-key-status Status of the public VIEWER ro
key uploading

Group
idc-board download-security-status Status of security file VIEWER ro
download status
idc-board download-cli-script-status Status of CLI VIEWER ro
configuration script's
file download status
idc-board slot-id Slot ID (within the VIEWER ro
XC node)
idc-board hw-mode Hardware Mode VIEWER ro
(standalone or xc)
idc-board xc-role XC Role (Main or VIEWER ro
Extension)
idc-board version IDC version VIEWER ro
idc-board kernel-modules-version Identifies current VIEWER ro
kernel-modules
package set version
idc-board warning-banner-file-name The warning banner ADMIN rw
file name to be
downloaded
idc-board security-file-name The security ADMIN rw
filename to be
downloaded
idc-board status-text-indication[2] Internal status text VIEWER ro
indication array
idc-board radio-led Radio LED VIEWER ro
idc-board idu-led IDU LED VIEWER ro
idc-board rfu-led RFU LED VIEWER ro
idc-board protection-led Protection LED VIEWER ro
idc-board remote-led Remote LED VIEWER ro
fpga main-fpga-running-fw-version Main FPGA running VIEWER ro
FW Version
fpga secondary-fpga-running-fw-version Secondary FPGA VIEWER ro
running FW Version
fpga fw-version FPGA FW Version VIEWER ro
mate-idu protection-Admin Protection Admin OPERATOR rw
mate-idu excessive-ber-switch-admin Excessive BER OPERATOR rw
switch admin
mate-idu Protection force OPERATOR rw
protection-force-switch
switch

Group
mate-idu protection-lockout Protection lockout OPERATOR rw
mate-idu Remote BER OPERATOR rw
remote-ber-adjustment-time
adjustment time
mate-idu Remote LOF OPERATOR rw
remote-lof-adjustment-time
adjustment time
mate-idu Last copy-to-mate- VIEWER
copy-to-mate-status ro
cmd execution status
mate-idu mate-ip-address Mate IP address VIEWER ro
mate-idu mate-mac-address Mate mac address VIEWER ro
mate-idu protection-mode Protection mode VIEWER ro
all-odu Admin All ODU Admin OPERATOR rw
shelf- slot-population[6] Slot Population VIEWER ro
manager
shelf- alive-slot-population[6] Alive Slot Population VIEWER ro
manager
shelf- shelf-most-severe-alarm[6] Shelf most severe VIEWER ro
manager alarm status
shelf- TDM-interfaces[6] TDM Interfaces VIEWER ro
manager
shelf- sdh-interfaces[6] SDH Interfaces VIEWER ro
manager
shelf- archives-operation-status Shelf-wide VIEWER ro
manager [configuration,unit-
info] archives
operation status
shelf- archive-operating-units Number of units still VIEWER ro
manager being processed by
the last archive
operation command
shelf- extension-units-protection-Admin[6] Protection Admin of VIEWER ro
manager Extension unit
shelf- radio-interfaces[6] Radio Interfaces VIEWER ro
manager
shelf- VIEWER ro
available-interfaces Available Interfaces
manager
shelf- Available SDH VIEWER ro
available-sdh-interfaces1
manager Interfaces
manager Interfaces 2

Group
manager Interfaces 3
remote-idu remote-ip-address Remote IDU IP OPERATOR rw
address
remote-idu remote-floating-ip-address Remote IDU OPERATOR rw
Floating IP address
configuration
remote-idu remote-subnet-mask Remote IDU subnet OPERATOR rw
mask
remote-idu remote-default-gateway Remote IDU default OPERATOR rw
gateway
remote-idu remote-atpc-Admin Remote IDU ATPC OPERATOR rw
enable/disable
configuration
remote-idu remote-atpc-ref-rx-level Remote ATPC OPERATOR rw
reference Rx level
configuration
remote-idu remote-management-type Remote OPERATOR rw
Management type
status
remote-idu remote-link-id Remote IDU Link ID OPERATOR rw
remote-idu remote-force-mute-tx Force remote Mute OPERATOR rw
transmit
configuration
remote-idu remote-force-max-tx-level Force remote Max OPERATOR rw
transmit level
configuration
remote-idu remote-web-protocol Remote IDU web VIEWER ro
protocol type
remote-idu remote-slot-id Remote slot id VIEWER ro
remote-idu remote-rx-level Remote Rx level VIEWER ro
status
remote-idu remote-most-severe-alarm Remote most VIEWER ro
severe alarm status
remote-idu remote-communication Remote VIEWER ro
Communication
Status
remote-idu remote-green-mode-admin Remote IDU OPERATOR rw
GREEN_MODE
enable/disable
configuration

Group
remote-idu remote-management-vlan Remote OPERATOR rw
Management VLAN
ID configuration
remote-co device-error Device errors VIEWER ro
remote-cl device-error Device errors VIEWER ro
radio mhc-Admin MAC header OPERATOR rw
compression Admin
radio radio-if-interface Radio Admin OPERATOR rw
radio radio-if-interface-operationa l-status Radio interface VIEWER ro
actual current state
radio interface-alias Interface alias OPERATOR rw
radio max-available-tdm-cap Maximal amount of VIEWER ro
VC<EF><BF><BD>s
that mi configured by
the radio entity
xpic xpic-status XPIC Script has VIEWER ro
been loaded
xpic events-enable Enable logging of OPERATOR rw
XPIC events
xpic xrsm-cfg-retry-length-mul-fact or Multiplication factor OPERATOR rw
of time between
tor XRSM retries
Configuration
xpic xrsm-cfg-num-of-retries Number or XRSM OPERATOR rw
attempts to re-
establish XPIC
communcations
Configuration
xpic xrsm-cfg-delay-between-retries Delay duration OPERATOR rw
between XRSM
retries to re-establish
XPIC
communcations
Configuration
xpic xrsm-cfg-duration-of-retry Delay duration of OPERATOR rw
XRSM retry to re-
establish XPIC
communcations
Configuration
xpic debug-current-config-status Current XPIC VIEWER ro
Configuration Status
Flag

Group
xpic slave-xpic-enable Allows slave to VIEWER ro
update master of
XPIC enable event
xpic slave-rfu-comm-status Allows slave to VIEWER ro
update master of
RFU comm status
event
xpic slave-mute-transmitter Allows slave to VIEWER ro
update master of
RFU
mute event
xpic slave-if-loopback Allows slave to VIEWER ro
update master of IF
loopback event
xpic user-rfu-mute Allows master to VIEWER ro
read current status if
RFU mute on disk
xpic Allows master to VIEWER ro
slave-xpic-lop request slave XPIC
LOP status
xpic Allows master to set VIEWER ro
slave-xpi-mute
slave XPIC MUTE
xpic xrsm-cfg-enable Enables the rw
operation of XRSM
when LOP is OPERATOR
detected
Configuration
framer link-id Link ID OPERATOR rw
framer radio-excessive-ber-threshold Radio Excessive OPERATOR rw
BER threshold
configuration
framer radio-signal-degrade-threshold Radio Signal OPERATOR rw
Degrade threshold
configuration
framer radio-ber Radio BER status VIEWER ro
framer oper-status Operational status VIEWER ro
framer radio-pm-15min-interval[96] Radio 15 minute VIEWER ro
interval performance
monitor
framer radio-pm-24hour-interval[30] Radio 24 hour VIEWER ro
monitor

Group
mrmc mrmc-script Radio scheme (Bit VIEWER ro
Rate, Occupied BW,
Modulation and
Grade).\n Occupied
BW Vs Channel
Separation are listed
in pairs: (Occupied
BW Range[MHz],
Channel Separation
[MHz]):\n(5-7,7); (8-
10,10); (12-14,13.75-
15); (25-29,27.5-30);
(33-38,40); (50-
55,55-56)
mrmc operation-mode Operation mode VIEWER ro
mrmc current-tx-profile Current Tx profile VIEWER ro
mrmc script-package-version Modem script VIEWER ro
package version
mrmc rfu-chosen-grade RFU chosen grade VIEWER ro
mrmc connected-rfu-grade Actual connected VIEWER ro
RFU grade
mrmc occupied-bandwidth Occupied bandwidth VIEWER ro
(MHz)
mrmc current-tx-qam Current Tx QAM VIEWER ro
mrmc current-tx-bitrate Current Tx bitrate VIEWER ro
mrmc max-available-tdm-interfaces Max available TDM VIEWER ro
interface
mrmc current-rx-profile Current Rx profile VIEWER ro
mrmc current-rx-qam Current Rx QAM VIEWER ro
mrmc current-rx-bitrate Current Rx bitrate VIEWER ro
mrmc current-rx-vc Current profile Rx VIEWER ro
TDM channels
mrmc current-tx-vc Current profile Tx VIEWER ro
TDM channels
mrmc min-rx-vc Min profile Rx VC VIEWER ro
mrmc max-rx-vc Max profile Rx VC VIEWER ro
mrmc current-script-capacity current-script- VIEWER ro
capacity
mrmc current-acm-mode current-acm-mode VIEWER ro
mrmc loaded-script-version Modem script VIEWER ro
version

Group
mrmc loaded-script-description Loaded script VIEWER ro
description
mrmc mrmc-pm-15min-interval[96] MRMC 15 minute VIEWER ro
monitor
mrmc mrmc-pm-24hour-interval[30] MRMC 24 hour VIEWER ro
monitor
mrmc When 'Automatic Operator rw
State Propagation' is
not 'None', a
GBE/Radio mute (or
eth-shutdown-threshold-profile
shutdown) will be
forced if the radio
profile degrades
below this threshold
mrmc TX maximum power VIEWER ro
adaptive-tx-power-admin
adaptation admin
mrmc TX maximum power VIEWER ro
adaptive-tx-power-reference-class adaptation reference
class
mrmc Current ACM VIEWER ro
current-acm-adaptive-rx-profile
adaptive Rx profile
mrmc Current ACM VIEWER ro
current-acm-adaptive-tx-profile
adaptive Tx profile
mrmc max-adaptive-acm-rx-profile Maximum adaptive VIEWER ro
ACM Rx profile
mrmc min-adaptive-acm-rx-profile Minimum adaptive VIEWER ro
ACM Rx profile
Tdm-radio- tdm-radio-pm-15min-interval[96] Tdm radio UAS PM VIEWER ro
pm 15 minutes
monitoring
Tdm-radio- tdm-radio-pm-24hour-interval[30] Tdm radio UAS PM VIEWER ro
pm 24 hours monitoring
modem mse-threshold MSE threshold OPERATOR rw
modem xpi-threshold XPI threshold OPERATOR rw
information
modem mse MSE VIEWER ro
modem xpi XPI level VIEWER ro
modem defected-blocks Defective blocks VIEWER ro
modem slicer-input-scaling Slicer input scaling VIEWER ro
information

Group
modem ldpc-decoder-stress LDPC decoder VIEWER ro
stress
modem pm-15min-interval[96] Modem 15 minute VIEWER ro
monitor
modem pm-24hour-interval[30] Modem 24 hour VIEWER ro
monitor
rfu pm-rx-level-threshold-1 RFU performance OPERATOR rw
monitoring Rx level
threshold 1
configuration
rfu pm-rx-level-threshold-2 RFU performance OPERATOR rw
monitoring Rx level
threshold 2
configuration
rfu pm-tx-level-threshold RFU performance OPERATOR rw
monitoring Tx level
Threshold
configuration
rfu atpc-Admin RFU ATPC OPERATOR rw
enable/disable
rfu tx-freq RFU Rx frequency OPERATOR rw
configuration
rfu atpc-ref-rx-level RFU ATPC OPERATOR rw
reference Rx Level
rfu rx-freq RFU Rx frequency OPERATOR rw
configuration
rfu mute-tx RFU mute transmitte OPERATOR rw
rfu unfaded-rsl RFU Unfaded Rx OPERATOR rw
level configuration
rfu max-tx-level RFU maximum OPERATOR rw
transmit level
configuration
rfu log-interval RFU log interval OPERATOR rw
configuration, in
seconds
rfu log-Admin RFU log OPERATOR rw
enable/disable
configuration
rfu rfu-rf-loopback RFU RF loopback OPERATOR rw
enable command

Group
rfu standard-organization RFU standard VIEWER ro
organization
rfu temp-in-celsius RFU temperature, VIEWER ro
celsius
rfu temp-in-fahrenheit RFU temperature, VIEWER ro
fahrenheit
rfu tx-level-status RFU transmit level VIEWER ro
rfu rx-level RFU receive level VIEWER ro
status
rfu synthesizer-status RFU synthesizer VIEWER ro
rfu power-supply-status RFU power supply VIEWER ro
status
rfu Band RFU band status VIEWER ro
rfu min-tx-freq RFU minimum Tx VIEWER ro
frequency status
rfu max-tx-freq RFU maximum Tx VIEWER ro
frequency status
rfu tx-rx-freq-separation RFU Tx Rx VIEWER ro
frequency separation
rfu min-bandwidth RFU minimum VIEWER ro
bandwidth status
rfu max-bandwidth RFU maximum VIEWER ro
bandwidth status
rfu Pmax RFU Pmax status VIEWER ro
rfu communication-status RFU communication VIEWER ro
to remote unit status
rfu min-rx-freq RFU minimum Rx VIEWER ro
frequency status
rfu max-rx-freq RFU maximum Rx VIEWER ro
frequency status
rfu internal-download-status RFU internal VIEWER ro
download status
rfu internal-download-counter RFU internal VIEWER ro
download counter
status
rfu rfu-type Type of connected VIEWER ro
RFU
rfu rf-loopback-support RFU RF loopback VIEWER ro
support status

Group
rfu if-loopback-support RFU IF loopback VIEWER ro
support status
rfu predistortion-support RFU predistortion VIEWER ro
support status
rfu lo-sense RFU lo sense status VIEWER ro
rfu cable-tilt RFU cable tilt status VIEWER ro
rfu ifc-support RFU IFC support VIEWER ro
status
rfu pmin RFU Pmin status VIEWER ro
rfu rfu-address RFU address status VIEWER ro
rfu rfu-installation RFU installation VIEWER ro
status
rfu rfu-xpic-support RFU XPIC support VIEWER ro
rfu data-sci-errors RFU data SCI VIEWER ro
number of errors
rfu tx-freq-local-remote RFU change Tx OPERATOR rw
frequency local
remote command
rfu rx-freq-local-remote RFU change Rx OPERATOR rw
frequency local
remote command
rfu mse-forward RFU MSE forward OPERATOR rw
command
rfu serial-number RFU serial number VIEWER ro
rfu software-version-number RFU running VIEWER ro
software version
number
with booter version
suffix
rfu part-number RFU part number VIEWER ro
rfu pm-15min-interval[96] RFU 15 minute VIEWER ro
monitor
rfu pm-24hour-interval[30] RFU 24 hour interval VIEWER ro
performance monitor
rfu pm-15min-interval-diversity[96] RFU 15 minute VIEWER ro
interval diversity

Group
rfu pm-24hour-interval-diversity[30] RFU 24 hour interval VIEWER ro
diversity
30]
performance monitor
rfu pm-15min-interval-combined[96] RFU 15 minute VIEWER ro
interval combined
performance monitor
rfu pm-24hour-interval-combined[30] RFU 24 hour VIEWER ro
interval combined
performance monitor
rfu RFU delay operator rw
delay-calibration calibration
configuration
rfu green-mode-admin Activate Green Mode operator rw
rfu RFU Green Mode operator rw
green-mode-ref-rx-level Reference Rx Level
Configuration
rfu rfu-mode RFU mode operator rw
configuration
rfu RFU RX level operator rw

rsl-connector-source connector source
configuration
rfu RFU automatic delay VIEWER ro
automatic-delay-calibration-status
calibration status
rfu RFU running FW VIEWER ro
fpga-version-number
version number
rfu RFU IFC support VIEWER ro
ifc-support
status
rfu RFU-D copartner VIEWER ro
rfu-d-copartner-carrier
carrier
rfu RFU Temperature VIEWER ro
rfu-temp
Status
rfu RFU Rx level VIEWER ro
rx-level-combined
combined status
rfu RFU Rx level VIEWER ro
rx-level-diversity
diversity
RFU internal VIEWER ro
rfu-fw-
internal-fw-download-counter firmware download
upload
counter status

Group
RFU internal VIEWER ro
rfu-fw-
internal-fw-download-status firmware download
upload
status
rfu-sw- internal-download-counter RFU internal VIEWER ro
upload download counter
status
rfu-sw- internal-download-status RFU internal VIEWER ro
upload download status
rfu-co device-error Device errors VIEWER ro
rfu-cl device-error Device errors VIEWER ro
rfic if-loopback IF loopback OPERATOR rw
activation
interfaces ais-line-detection-Admin Enabling or disabling OPERATOR rw
detection of AIS on
the interfaces. Upon
enabling, monitoring
is done for all
relevant interfaces,
both on the main
board and
the inserted T-card,
if present.
wayside Admin Enable/disable OPERATOR rw
Wayside channel
wayside capacity Wayside channel OPERATOR rw
capacity
wayside auto-negotiation Wayside auto OPERATOR rw
negotiation
wayside duplex Wayside half/full OPERATOR rw
duplex
wayside ethernet-rate Wayside Ethernet OPERATOR rw
port rate (Mbps)
ethernet clock-source clock source OPERATOR rw
ethernet acm-ethernet-threshold ACM ethernet VIEWER ro
threshold
bridge ethernet-application Ethernet application OPERATOR rw
bridge qos-ip-tos-tc-pbits-option IP priority options rw
bridge management-type Management type VIEWER ro
bridge lag-ports-max-number max number of LAG- VIEWER ro
ports in a bridge

Group
bridge ageing-time LearnedMACaddress OPERATOR rw
isremovedfromthe
forwardingtableafter
thisamountoftime
fromthelasttimethis
MACappearedinan
ingressingframe's
SourceAddress
bridge LAGloadbalancing OPERATOR rw
lag-load-balance
algorithm
bridge Maximumhopsthe OPERATOR rw
max-hops
BPDUwillbevalid
bridge Bridgepriorityfor OPERATOR rw
msti-bridge-priority eachdefinedMST
instance
bridge Priority Bridgepriority OPERATOR rw
bridge Providerport OPERATOR rw
provider-port-ethertype
ethertype
bridge stp-protocol SpanningTree OPERATOR rw
protocol
bridge bridge-id BridgeID VIEWER RO
bridge bridge-role Bridgerole VIEWER RO
bridge root-id RootID VIEWER RO
bridge root-path-cost Rootpathcost VIEWER RO
eth-port learning Learning Admin OPERATOR rw
eth-port connector-type Connector type OPERATOR rw
eth-port port-connection Port Physical Usage OPERATOR rw
eth-port peer-ip-address IP address of the OPERATOR rw
remote node
eth-port peer-slot-id ID of the remote slot OPERATOR rw
(0 for standalone
unit)
eth-port peer-port-number Remote port number OPERATOR rw
(0 for not connected)
eth-port Admin Enable/disable the OPERATOR rw
port
eth-port auto-negotiation Auto negotiation OPERATOR rw
eth-port duplex Half/full duplex OPERATOR rw
eth-port ethernet-rate Ethernet rate (mbps) OPERATOR rw

Group
eth-port qos-classify-mac-da-override First criteria: OPERATOR rw
classification
according to
destination MAC
address (MAC DA)
eth-port qos-classify-initia Third criteria OPERATOR rw
classification
eth-port qos-classify-default Priority override port OPERATOR rw
eth-port qos-classify-vid-override Second criteria: OPERATOR rw
classification
according to VLAN
ID
eth-port qos-scheduling-scheme Scheduling scheme OPERATOR rw
eth-port flow-control Flow control OPERATOR rw
eth-port qos-egress-shaper Egress shaper OPERATOR rw
eth-port qos-egress-shaper-rate Egress shaper rate. OPERATOR rw
The value should be
in steps of 64K for
values less than 1
Mbps. 1M steps for
values between 1
Mbps and 100 Mbps.
10M steps for values
between 100 Mbps
and 1000 Mbps
(GbE ports only).
eth-port oper-status Interface alias OPERATOR rw
eth-port peer-mac-address MAC address of the OPERATOR rw
remote port
eth-port peer-description Text describing the OPERATOR rw
remote interface
eth-port qos-policer-name Policer name OPERATOR rw
associated with this
port
eth-port oper-status Operational status VIEWER ro
eth-port state Port's state VIEWER ro
eth-port interface-type Interface type VIEWER ro
eth-port interface-index Interface index VIEWER ro

Group
eth-port if-table-inoctets The total number of VIEWER ro
octets received on
the interface,
including framing
characters.
eth-port if-table-inucastpkts The number of VIEWER ro
subnetwork-unicast
packets delivered to
a higher-layer
protocol.
eth-port if-table-innucastpkts The number of non- VIEWER ro
unicast packets
delivered to a higher-
layer protocol
eth-port if-table-indiscards The number of VIEWER ro
inbound packets
which
were chosen to be
discarded, even
though no errors had
been detected, to
prevent their being
deliverable to a
higher-layer protocol.
eth-port if-table-inerrors The number of VIEWER ro
inbound packets that
contained errors
preventing them
from
being delivered to a
higher-layer
protocol
eth-port if-table-inunknownprotos The number of VIEWER ro
packets received via
the
interface which were
discarded because
of an unknown or
unsupported prot
eth-port if-table-outoctets The total number of VIEWER ro
octets transmitted
out of the
interface, including
framing characters.

Group
eth-port if-table-outucastpkts The total number of VIEWER ro
packets tha thigher-
level protocols
requested be
transmitted to a
subnetwork-unicast
address, including
those that were
discarded or not sent
eth-port if-table-outnucastpkts The total number of VIEWER ro
packets thathigher-
level protocols
requested
betransmitted to a
non-unicast address,
including those that
were discarded or
not sent.
eth-port if-table-outdiscards The number of VIEWER ro
outbound packets
whichwere chosen to
be discarded, even
been detected,
toprevent them from
being transmitted.
eth-port if-table-outerrors The number of VIEWER ro
outbound packets
that could not be
transmitted because
oferrors.
eth-port bad-octets-rcv The sum of lengths VIEWER ro
of all bad Ethernet
frames received
eth-port in-uni-casts The number of good VIEWER ro
frames received that
have Unicast
destination MAC
address.
eth-port brdc-pkts-rcv The number of good VIEWER ro
have Broadcast
destination MAC
address

Group
eth-port mc-pkts-rcv The number of good VIEWER ro
have Multicast
destination MAC
address.
This does not
include frames
counted in
'Pause frames
received' or frames
counted in
'Broadcast frames
received'.
eth-port in-pause The number of good VIEWER ro
have Pause
destination MAC
address.
eth-port undersize-pkts Total frames VIEWER ro
received with a
length of less than
64 octets but with a
valid FCS
eth-port fragments-pkts Total frames VIEWER ro
received with a
length of less than
64 octets but with an
invalid FCS.
eth-port oversize-pkts Total frames VIEWER ro
received with a
length of
more than 1632
octets but with a
valid
FCS.
eth-port jabber-pkts Total frames VIEWER ro
received with a
length of more than
1632 octets but with
an
invalid FCS.
eth-port in-rx-err Total frames VIEWER ro
received with error
signal from PHY

Group
eth-port in-fcs-err Total frames VIEWER ro
received with a CRC
error not counted in
'Fragments frames
received', 'Jabber
frames received' or
'Rx error frames
received'.
eth-port pkts-64-octets Total frames VIEWER ro
received with length
of
exactly 64 octets,
including those with
errors.
eth-port pkts-65-127-octets Total frames VIEWER ro
of between 65 and
127 octets inclusive,
including those with
errors.
of between 128 and
255 octets inclusive
of between 256 and
of between 512 and
eth-port pkts-1024-max-octets Total frames VIEWER ro
of
above 1024 octets
inclusive, including
those with errors.
eth-port out-uni-casts The number of VIEWER ro
frames sent that
have a
Unicast destination
MAC address

Group
eth-port brdc-pkts-sent The number of VIEWER ro
good frames sent
that have a
Broadcast
destination MAC
address
eth-port mc-pkts-sent The number of good VIEWER ro
frames sent that
have a Multicast
destination MAC
address. This does
not include frames
counted in 'Pause
frames sent' or
frames counted in
'Broadcast frames
sent'.
eth-port out-pause The number of Flow VIEWER ro
Control frames sent
eth-port deferred The total number of VIEWER ro
successfully
transmitted frames
that experienced no
collisions but are
delayed because the
medium was busy
during the first
attempt. This counter
is applicable in
half-duplex only.
eth-port collisions The number of VIEWER ro
collision events seen
by
the MAC not
including those
counted in
'Single', 'Multiple',
'Excessive', or
'Late'. This counter is
applicable in
half-duplex only.

Group
eth-port single-collision-frame The total number of VIEWER ro
successfully
transmitted frames
that experienced
exactly one collision.
This counter is
applicable in half-
duplex only.
eth-port multiple-collision-frame The total number of VIEWER ro
frames that have
been successfully
transmitted and have
also experienced
more than one
collision. This
counter is applicable
in half-duplex only
eth-port late-collision-detect The number of VIEWER ro
times a collision is
detected later than
512 bit-times into the
transmission of a
frame. This
in half-duplex
only.
eth-port out-fcs-err The number of VIEWER ro
frames transmitted
with
an invalid FCS
eth-port in-discards A 32 bit counter that VIEWER ro
counts the number
of good, non-filtered
frames that
normally would have
been forwarded, but
could not be due to a
lack of buffer
space

Group
eth-port in-filtered A 16 bit counter that VIEWER ro
counts the number of
good frames that
were filtered due to
ingress policy rules.
The rules
include frames that
are dropped due to
802.1Q security
checks.
eth-port out-filtered A 16 bit counter VIEWER ro
that counts the
number of good
frames that were
filtered due
to egress policy
rules. The rules
include frames that
passed the ingress
port's policy but are
dropped due to
the egress policy of
this port, including
802.1Q security
checks.
eth-port actual-duplex Actual duplex VIEWER ro
eth-port actual-ethernet-rate Actual Ethernet rate VIEWER ro
eth-port mac-address MAC address VIEWER ro
eth-port good-octets-rcv The sum of lengths VIEWER ro
of all good Ethernet
frames received, that
are not bad
frames.
eth-port good-octets-sent The sum of lengths VIEWER ro
of all Ethernet
frames sent from this
MAC.
eth-port functionality-led Functionality LED VIEWER ro
eth-port Capacity threshold rw
capacity-threshold Operator
[Mbps]
eth-port Clear all peer's rw
clear-peer-info Operator
information
eth-port Clear RMON rw
clear-rmon Operator
statistics
eth-port connector-type Connector type Operator rw

Group
eth-port duplex Half/full duplex Operator rw
eth-port edge-port Enable as edge port Operator rw
eth-port ethernet-rate Ethernet rate (mbps) Operator rw
eth-port evc-name EVC name Operator rw
eth-port flow-control Flow control Operator rw
eth-port priority rw
Port's priority Operator
eth-port Throughput rw
throughput-threshold Operator
threshold [Mbps]
eth-port type Port's type Operator rw
eth-port Utilization threshold rw
utilization-threshold Operator
[%]
eth-port vlan Default VLAN ID Operator rw
eth-port designated-path-cost Designated path cost VIEWER RO
eth-port The number of VIEWER
frames dropped in
the transmit MAC
because the frame
excess-collision-drop experienced 16 RO
consecutive
collisions. This
in half-duplex only.
eth-port Management port VIEWER
management-auto-negotiation RO
auto negotiation
management-capacity RO
capacity
management-duplex RO
duplex
management-ethernet-rate RO
Ethernet rate (Mbps)
eth-port management-only Management only VIEWER RO
eth-port management-port-admin Port's admin VIEWER RO
eth-port Management VLAN VIEWER
management-vlan RO
id
eth-port 15 Minute PM VIEWER
pm-15 RO
minutes monitoring
eth-port 24 Hour PM hours VIEWER
pm-24 RO
monitoring

Group
eth-port protection-only Protection only VIEWER RO
eth-port protection-port-admin Port's admin VIEWER RO
eth-port role Port's role VIEWER RO
eth-port Wayside auto VIEWER
wayside-auto-negotiation RO
negotiation
eth-port Wayside port VIEWER
wayside-capacity RO
capacity
eth-port Wayside half/full VIEWER
wayside-duplex RO
duplex
eth-port Wayside Ethernet VIEWER
wayside-ethernet-rate RO
port rate (Mbps)
eth-port wayside-only Wayside only VIEWER RO
eth-port wayside-port-admin Port's admin VIEWER RO
service- auto-linktrace-interval Automatic linktrace OPERATOR rw
oam periodic time
[seconds]
service- remote-meps-learning-time Remote MEPs OPERATOR rw
oam learning time (for
learned remote
MEPs) (seconds)
lag-port Admin Port's admin Operator rw
lag-port auto-negotiation Auto negotiation Operator rw
lag-port duplex Half/Full duplex Operator rw
lag-port edge-port Enable as edge port Operator rw
lag-port ethernet-rate Ethernet rate (mbps) Operator rw
lag-port evc-name EVC name Operator rw
lag-port flow-control Flow control Operator rw
lag-port interface-alias Interface alias Operator rw
lag-port Learning Learning admin Operator rw
lag-port Path cost for each rw
msti-port-path-cost defined MST Operator
instance
lag-port Interface priority for rw
msti-port-priority each defined MST Operator
instance
lag-port path-cost Path cost Operator rw
lag-port Text describing the rw
peer-description Operator
remote interface

Group
lag-port IP address of the rw
peer-ip-address Operator
remote node
lag-port MAC address of the rw
peer-mac-address Operator
remote port
lag-port Remote port number rw
peer-port-number Operator
(0 for not connected)
lag-port ID of the remote slot rw
peer-slot-id (0 for standalone Operator
unit)
lag-port priority Port's priority Operator rw
lag-port qos-classify-default Priority override port Operator rw
lag-port Classifying initial rw
qos-classify-initial Operator
criteria
lag-port Classifier DA priority rw
qos-classify-mac-da-override Operator
override
lag-port Classifier VID rw
qos-classify-vid-override Operator
override priority
lag-port qos-scheduling-scheme Scheduling scheme Operator rw
lag-port type Port's type Operator rw
lag-port vlan Default VLAN ID Operator rw
lag-port designated-path-cost Designated path cost VIEWER RO
lag-port The number of VIEWER
inbound packets
which were chosen
to be discarded even
if-table-indiscards though no errors had RO
been detected to
prevent their being
deliverable to a
inbound packets that
contained errors
if-table-inerrors preventing them RO
from being
deliverable to a
lag-port The number of non- VIEWER
unicast packets
if-table-innucastpkts RO
delivered to a higher-
layer protocol.

Group
lag-port The total number of VIEWER
octets received on
if-table-inoctets the interface, RO
including framing
characters.
subnetwork-unicast
if-table-inucastpkts packets delivered to RO
a higher-layer
protocol.
packets received via
the interface which
were discarded
if-table-inunknownprotos RO
because of an
unknown or
unsupported
protocol.
outbound packets
which were chosen
to be discarded even
if-table-outdiscards RO
been detected to
prevent their being
transmitted.
outbound packets
if-table-outerrors that could not be RO
transmitted because
of errors.
packets that higher-
level protocols
requested be
if-table-outnucastpkts transmitted to a non- RO
unicast address,
including those that
were discarded or
not sent.
octets transmitted
if-table-outoctets out of the interface, RO
including framing
characters.

Group
packets that higher-
level protocols
requested be
transmitted to a
if-table-outucastpkts RO
subnetwork-unicast
address, including
those that were
discarded or not
sent.
lag-port interface-index Interface index VIEWER RO
lag-port interface-type Interface type VIEWER RO
lag-port list of LAG members VIEWER
lag-members-list which are associated RO
with the LAG-port
lag-port max number of VIEWER
lag-members-max-number members in a LAG- RO
port
lag-port mac-address MAC address VIEWER RO
lag-port management-only Management only VIEWER RO
lag-port oper-status Operational status VIEWER RO
lag-port protection-only Protection only VIEWER RO
lag-port role Port's role VIEWER RO
lag-port state Port's state VIEWER RO
lag-port wayside-only Wayside only VIEWER RO
port-group line-code-1-8 Line coding for T1 OPERATOR rw
interfaces 1-8
interfaces 9-16
port-group exber-threshold Excessive BER OPERATOR rw
threshold
port-group sd-threshold Signal degrade OPERATOR rw
threshold
port-group pdh-led[2] PDH LED color VIEWER ro
port-group line-code Line code OPERATOR rw
port-group Line coding for T1 OPERATOR rw
line-code-17-24
interfaces 17-24
interfaces 25-32
e1t1-port line-loopback Line loopback OPERATOR rw

Group
e1t1-port interface-alias Interface alias rw
e1t1-port oper-status Operational status VIEWER ro
e1t1-port Admin Enable/disable the OPERATOR ro
port
e1t1-port e1t1-priority Dynamic E1/DS1 OPERATOR ro
allocation priority
e1t1-port interface-type Interface type VIEWER ro
e1t1-port port-curr-ber E1/DS1 port current VIEWER ro
BER
e1t1-port ais-detection-status Status of AIS VIEWER ro
detection on the port
e1t1-port line-pm-15[96] Line PM 15 minute VIEWER ro
monitoring
e1t1-port line-pm-24[30] Line PM 24 hour VIEWER ro
monitoring
e1t1-port cable-length DS1 cable length OPERATOR rw
trails available-tdm-interfaces Available TDM VIEWER ro
Interfaces
trails Available SDH VIEWER ro
Interfaces
available-sdh-interfaces
trails available-radio-interfaces Available RADIO VIEWER ro
Interfaces
trails available-sync-tdm-interfaces available-sync-tdm- VIEWER ro
interface
trails available-sync-sdh-interfaces available-sync-sdh- VIEWER ro
interface
trails available-sync-radio-interfaces available-sync-radio- VIEWER ro
interface
trails trails-level-trail-trap-admin trail level trail trap rw
admin Admin
(enable/disable)
stm1 admin Enable/disable OPERATOR rw
receiving and
transmitting traffic
through the STM-1
interface
stm1 line-tx-protection-mode STM-1 interface OPERATOR rw
transmission
behavior under
protection mode

Group
stm1 clock-source The clock source OPERATOR rw
used as a reference
for the outgoing
STM-1 signal.
stm1 sync-vc The VC channel OPERATOR rw
which will be used to
synchronize the
STM-1 interface.
stm1 force-mute STM-1 mute override OPERATOR rw
stm1 trace-identifier-string-length Length of the STM-1 OPERATOR rw
signal J0 trace
identifier
stm1 excessive-ber-threshold STM-1 excessive OPERATOR rw
BER threshold
configuration
stm1 signal-degrade-threshold STM-1 signal OPERATOR rw
degrade threshold
configuration
stm1 loopback-timeout Loopback timeout in OPERATOR rw
minutes (0 for
unlimited)
stm1 node-to-node-connection The indication OPERATOR rw
whether the STM-1
interface connects
IP-10 nodes in a
network
stm1 peer-ip-address IP address of the OPERATOR rw
remote STM1
element
stm1 peer-port-number Remote STM-1 port OPERATOR rw
number
stm1 peer-slot-id Slot ID of the remote OPERATOR rw
STM1 port
stm1 ais-vc-signaling-admin Enabling or disabling OPERATOR rw
the signaling of AIS
upon receiving such
from
stm1 line-loopback Type of loopback in OPERATOR rw
the STM-1 interface

Group
stm1 transmit-trace-identifier String used as the OPERATOR rw
transmitted STM-1
signal J0 trace
identifier
stm1 expected-trace-identifier String expected to OPERATOR rw
be received as the
STM-1 signal J0
trace identifier
stm1 peer-description Description of the OPERATOR rw
remote STM1
element
stm1 oper-status Operational status VIEWER ro
stm1 interface-type Type of Interface VIEWER ro
stm1 max-num-of-vc Maximum number of VIEWER ro
VC in STM
stm1 clock-source-status The clock source VIEWER ro
that is set at the
moment
stm1 loopback-counter Loopback time left VIEWER ro
(in seconds)
stm1 ais-detection-status-on-vc[63] Status of AIS VIEWER ro
detection on a
specific VC
stm1 received-trace-identifier STM-1 signal J0 VIEWER ro
trace identifier
actually received
from the interface
stm1 pm-15[96] 15 Minutes PM VIEWER ro
monitoring
stm1 pm-24[30] 24 Hours PM VIEWER ro
monitoring
stm1 stm1-led STM-1 SFP led VIEWER ro
stm1 ds1-standard-klm-mapping Allows choosing rw
between standard
Operator
and proprietary KLM
mapping
line- timeout oopback timeout in OPERATOR rw
loopback minutes (0 for
unlimited)
line- line-loopback[16] Line loopback OPERATOR rw
loopback

Group
line- counter Loopback time left VIEWER ro
loopback
line- STM-1/OC-3 Line rw
stm1-line-loopback Operator
loopback loopback
line- STM-1/OC-3 rw
loopback Loopback timeout in
stm1-timeout Operator
minutes (0 for
unlimited)
line- stm1-counter STM-1/OC-3 ro
loopback Loopback counter in VIEWER
seconds
radio- timeout Loopback timeout in OPERATOR rw
loopback minutes
radio- if-loopback[16] IF loopback activatio OPERATOR rw
loopback
radio- rfu-rf-loopback RFU RF Loopback OPERATOR rw
loopback Enable Command
radio- counter Loopback time left VIEWER ro
loopback
eow Admin Engineering order ro
VIEWER
wire admin
user- rw
admin User channel admin Operator
channel
user- rw
type User channel type Operator
channel

CLI Procedures
This guide provides instructions for specific FibeAir IP-10 CLI based operations. It is updated up to
software release 6.6.1.
CLI (Command Line Interface) is used to perform IP-10 configuration and obtain system statistical and
performance information.
Using the CLI, you can perform configuration operations for stand-alone IP-10 units or units connected in a
stacked configuration, as well as configure several IP-10 units in a single batch command.
In a stacked configuration, all commands are available both in the main and extension units unless otherwise
stated.
Basic Commands
The following basic commands are available when you first log in, if you belong to the Operator
user group:
ls List entities
get Get parameter
set Set parameter
help Help
cd Change directory
exit Exit CLI
logout Logout from CLI
cli-ver CLI version
cls Clear screen
shell Enter secondary shell
write Write the current switch configuration to the configuration file
show-tree Show entity tree
find Search for a string in the parameter's entity name and information fields
lsp List entity parameters and commands
echo echoing free text to the console
In order to get help on a specific command, add a question mark or the parameter --help after
the command.
In addition, you can use the up and down arrow keys, or the q key, when the word END
appears at the end of the screen.

Note: To perform the operations in this guide, you should log in as follows:
User: admin or operator
Password: admin
Basic System Configuration
Setting IP Addresses
To define a new IP address, do the following at the main unit:
1. Log in as follows:
User: admin or operator

Password: admin
2. At the command prompt, type: cd management/networking/ip-address/, and press Enter.
3. Type: get ip-address, and press Enter. This will give you the current IP address.
4. Type: set ip-address <ip> (the new IP address), and press Enter.
Adding Users
To define a new user, do the following:
1. Log in.
2. At the command prompt, type: cd management/mng-services/users/, and press Enter.
3. Type: add-user <name> <group> <password aging days> <expiration date>, and press
Enter.
4. Type the password for the new user.
Navigating between Stacked Units
Going from the main unit to a different unit

After log-in, prompt is always given at the main unit. In order to change the prompt to a different
unit do the following:
1. Log in.
2. At the command prompt, type: cd /platform/shelf-manager/, and press Enter.

3. Type: logon-unit <slot number>, and press Enter.
The prompt will change according to the relevant slot ID. For example, the prompt for a unit
located in slot 3 will show:
IP-10-SLOT-3:/>
Returning to Main Unit

In order to go back to the main unit, type
1. Log in.
Adding Users
To define a new user, do the following:
1. Log in.
2. At the command prompt, type: cd management/mng-services/users/, and press Enter.
3. Type: add-user <name> <group>, and press Enter.
4. Type the password for the new user.
Performing Resets
In Stacked Configuration
In order to reset a specific unit in the shelf, do the following at the main unit:
1. Log in.
3. Type: reset-unit <slot ID> , and press Enter.
Arguments description:
Slot ID: slot of the IDU to be reset (1 6)
In order to reset all extension units (but not the main unit), do the following at the main unit:
1. Log in.

3. Type: reset-extensions <slot ID>
In order to reset all units (including the main unit), do the following at the main unit:
1. Log in.
3. Type: reset-shelf <slot ID>
In any IDU (stand-alone or shelf)

In order to reset an IDU locally (stand-alone or in extension prompt in the shelf), do the following:
1. Log in.
2. At the command prompt, type: cd /platform/idc-board/, and press Enter.
3. Type: reset-unit <slot ID> , and press Enter.
TDM Trail Management
Defining a TDM Trail

In order to define a TDM trail, do the following at the main unit:
1. Log in.
2. At the command prompt, type: cd /interfaces/pdh/trails/, and press Enter.
3. Type: add-trail <trail ID> <trail desctiption> <ACM priority> <operational/reserved>

<protected/unprotected> <interface 1 slot #> <interface 1 type> <interface 1 number>
<interface 2 slot #> <interface 2 type> <interface 2 number> , and press Enter.
Trail-ID: up to 16 alphanumeric characters
Trail description: string up to 32 characters
ACM priority: high or low
Operational/reserved: reserved trails are introduced in the database and the bandwidth
wont be used for TDM traffic (it may be used for ethernet traffic) but traffic does not flow.
For operational trails bandwidth is fully allocated and traffic flows

Protected/unprotected: unprotected trails are mappings between two interfaces only.
Protected trails are mappings between an end-point interfaces and two other interfaces, the
first of which is the primary path and the second of which is the secondary path (see SNCP
section below).
Interface slot: slot number of the IDU containing the interface (from 1 to 6)
Interface type: line (E1/T1) or radio
Interface number: the number of the E1/T1 interface or radio VC to be used.
o For E1/T1 it can be 1 to 32 (1 to 16 if no extra 16 E1 T-card is installed)
o For radio, the maximum number depends on the radio script being used
Unprotected trail example:

add-trail id1 desc1 high operational unprotected 1 line 1 1 radio 1.
See Trails Defined in the System

In order to see all the defined trails, do the following:
1. Log in.
3. To show all trails type: show-all-trails, and press Enter.
4. To show a specific trail by its ID type: show-trail-by-id <trail ID>, and press Enter.
5. To show a specific trail by its source interface type: show-trail-by-src <interface 1 slot #>
<interface 1 type> <interface 1 number>, and press Enter.
The trails will be shown in a table as follows (this is an example of a trail from E1#1 in slot 2 to
radio VC#1 in slot 3:
================================================================
Legend: s/i/n/- 's'=slot-id 'i'=if-type 'n'=if-num '-'=Empty
s(0..6) i(l=line/r=radio/s=stm-1/c=chain/s=sync_ethernet) n(1..180)
================================================================
Source Dest1 Dest2 Dest3 Dest4 Dest5 Dest6 Dest7 Dest8 Dest9
------------------------------------------------------------------------------
IndexInDb = 1, ID = t1, Desc = d1, Prio = high
Act = operational, TS = (0)

2/l/ 1 3/r/ 1 - - - - - - - -
------------------------------------------------------------------------------
Where 2/l/1 denotes slot 2/line/interface 1.
Deleting Trails
There are several ways to delete trails:
1. Log in.
3. To delete all trails type: del-all-trails, and press Enter.
4. To delete a specific trail by its ID type: del-trail-by-id <trail ID>, and press Enter.
4. To delete a specific trail by its source interface type: del-trail-by-src <interface 1 slot #>
<interface 1 type> <interface 1 number>, and press Enter.
Activating/Deactivating Trails
Trails mode can be toggled between active and reserved, as follows:
1. Log in.
3. To activate/reserve all trails type: act-all-trails, and press Enter.
4. To activate/reserve a specific trail by its ID type: act-trail-by-id <trail ID>, and press Enter.
TDM Protected Trails (SNCP)

All operations for unprotected trails are available for protected trails as well. The additional
operations for protected trails are described in this section.

Defining a Protected TDM Trail
In order to define a TDM trail, do the following at the main unit:
1. Log in.
3. Type: add-trail <trail ID> <trail desctiption> <ACM priority> <operational/reserved>

<protected/unprotected> <end-point interface slot #> < end-point interface type> < end-
point interface number> <primary path slot #> < primary path type> < primary path
number> <secondary path slot #> < secondary path type> < secondary path number>,
and press Enter.
Trail-ID: up to 16 alphanumeric characters
Trail description: string up to 32 characters
ACM priority: high or low
Operational/reserved: reserved trails are introduced in the database and the bandwidth
wont be used for TDM traffic (it may be used for ethernet traffic) but traffic does not flow.
For operational trails bandwidth is fully allocated and traffic flows
Protected/unprotected: unprotected trails are mappings between two interfaces only.

Protected trails are mappings between an end-point interfaces and two other interfaces, the
first of which is the primary path and the second of which is the secondary path
Interface slot: slot number of the IDU containing the interface (from 1 to 6)
Interface type: line (E1/T1) or radio
Interface number: the number of the E1/T1 interface or radio VC to be used.
o For E1/T1 it can be 1 to 32 (1 to 16 if no extra 16 E1 T-card is installed)
o For radio, the maximum number depends on the radio script being used
Protected trail example:

add-trail id1 desc1 high operational protected 1 line 1 2 radio 1 3 radio 1.

Forcing Trails to Active/Standby
Each protected trail can be forced to make either one of its paths active (or none of them) as
follows:
1. Log in.
3. To force all trails to one of their paths type: protected-trail-force-active <Id> <path>, and
press Enter.
4. To force a specific trail by its ID type to one of its paths type: protected-trail-force-active-by-
id <Id> <path>, and press Enter.
<Id> - trail ID
<path> - primary, secondary or none
Showing TDM Trail PMs and Status
Showing TDM Trail PM Measurements

In order to see the TDM trails end-to-end PM measurements (as measured from this systems
interface), do the following:
1. Log in.
3. To show PMs of all trails type: show-all-trail-pms, and press Enter.
4. To show a specific trails PMs by its ID type: show-trail-pms-by-id <trail ID> <15 min
interval> <24h interval>, and press Enter.
<15min/24h interval> is the interval number to be shown, where 0 is the current interval, 1 is
the previous one and so on. If no interval is selected, the current one will be shown.
Showing TDM Trail Status

In order to see the TDM trails end-to-end PM measurements (as measured from this systems
interface), do the following:
1. Log in.
3. To show PMs of all trails type: show-all-trail-alarms and press Enter.

Ethernet Switch Application Configuration
The Ethernet Switch menu includes the Switch Configuration, STP Protocol, STP Configuration,
and QoS & Rate Limiting items.
The Ethernet switching methods include:
Single Pipe - Ethernet switching is disabled, whereby only a single Ethernet interface is used for
traffic and the unit operates as a point-to-point microwave Ethernet radio.
Managed Switch - For Layer 2 802.1Q switching.
Metro switch - Ethernet Q-in-Q provider switch is enabled.
To set the Ethernet switching method, do the following:
1. Log in.
2. At the command prompt, type: cd interfaces/ethernet/bridge/, and press Enter.
3. Type: set ethernet-application <Ethernet application type> (Single pipe, Managed switch,
or Metro switch), and press Enter.
4. The system will reset (automatically).
Management Ports
Setting the Number of Management Ports
1. At the command prompt, type: cd /management/networking/, and press Enter.
2. Type: set number-of-ports <no. of ports> (0-3), and press Enter.
Setting the Management Type (inband, outband, VLAN)
1. At the command prompt, type: cd /management/networking/, and press Enter.
2. Type set type < in-band or out-of-band >, and press Enter.
If you choose in-band, you should configure management VLAN id as follows:
a) At the command prompt, type: cd /management/networking/, and press Enter.
b) Type set vlan <no. of VLAN> (1-4090), and press Enter.
Port Configuration
Flow Control (Single Pipe only)
To enable or disable flow control, do the following

1. At the command prompt, type cd interfaces/ethernet/bridge/eth-port[port no.]/, and press
Enter.
2. Type set flow-control <on/off>, and press Enter.
Managed Switch Ethernet Ports
To enable or disable port admin, do the following:

Enter.
2. Type set admin <enable/disable>, and press Enter.
To set port speed rate, do the following:

Enter.
2. Type set ethernet-rate <Rate> (10, 100 or 1000 Mbps), and press Enter.
To set port duplex, do the following:

Enter.
2. Type set duplex < full-duplex / half-duplex > ,and press Enter.
To set auto negotiation on/off, do the following:

Enter.
2. Type set auto-negotiation <on/off>, and press Enter.
To set the port type, do the following:

Enter.
2. Type set type <access or trunk>, and press Enter.
To set the default VLAN ID, do the following:

Enter.
2. Type set vlan <VLAN no.> (1-4090), and press Enter.

To enable or disable port learning, do the following:

Enter.
2. Type set learning <enable/disable>, and press Enter.
To add, remove, accept VLANS, do the following:
1. The port type must be trunk.
2. At the command prompt, type cd interfaces/ethernet/bridge/eth-port [port no.]/, and press

Enter.
3. Type set-allowed-vlans <add, except, remove> <VLAN no.>, and press Enter.
4. Type set-allowed-vlans < all, no-vlans>, and press Enter.

VLAN Configuration
To add, remove, enable, or disable VLANs, do the following:
1. At the command prompt, type cd interfaces/ethernet/bridge/, and press Enter.
2. Type vlan <VLAN no.> <add, remove, enable, disable>, and press Enter.
To add or change the VLAN name, do the following:
1. At the command prompt, type cd interfaces/ethernet/bridge/, and press Enter.
2. Type vlan <VLAN no.> name <VLAN name>, and press Enter.
QoS Configuration
Ingress Classifier
To set classify initial, do the following:

Enter.
2. Type set qos-classify-initial < ip-tos, ip-tos-over-vlan-pbits, port, vlan-pbits, vlan-pbits-

over-ip-tos>, and press Enter.
To set classify vid override, do the following:

Enter.
2. Type set qos-classify-vid-override <disable, pbit-override, queue-and-pbit-override,

queue-override>, and press Enter.
To set classify mac da override, do the following:

Enter.
2. Type set qos-classify-mac-da-override <disable, pbit-override, queue-and-pbit-override,

queue-override>, and press Enter.
To set classify default, do the following:

Enter.
2. Type set qos-classify-default<1st, 2nd, 3rd, 4th>, and press Enter.
Egress Scheduler
To set Egress scheduler, do the following:

Enter.
2. Type: set qos-scheduling-scheme < all-queues-hrr, all-queues-strict, fourth-and-third-

queues-strict, fourth-queue-strict >, and press Enter.
Egress Shaper
To set egress shaper, do the following:
1. At the command prompt, type: cd interfaces/ethernet/bridge/eth-port[port no.]/, and press

Enter.
2. Type: set qos-egress-shaper on/off, and press Enter.
3. Type: set qos-egress-shaper-rate <rate>, and press Enter.
Policer
To add/remove Policer, do the following:
2. Type: qos-policer <add, remove> <policer name>, and press Enter.
To add a class to the Policer, do the following:
2. Type: qos-policer-class <add, remove> <policer class name> <policer name> <matching
type: all, arp, first-queue, second-queue, third-queue, fourth-queue, broadcast,
multicast, non-tcp-udp, tcp-control, tcp-data, udp, unicast, unknown-unicast, unknown-
multicast> <rate> <CBS> <exceed action: drop>, and press Enter.
3. Type: qos-show-policers to verify the data, and press Enter.
QoS Tables
To set VLAN Pbits Priority Remap Table, do the following:
1. At the command prompt, type: cd interfaces/ethernet/bridge/eth-port [port no.]/, and press

Enter.

2. Type: qos-set-vlan-pbits-prio-remap <original Pbit> <Remapped Pbit>, and press Enter.
To set VLAN ID to Queue Table, do the following:
2. Type: qos-vlan-to-queue set/remove <VID> <queue ID: 1st-queue, 2nd-queue, 3rd-queue,

4th-queue >, and press Enter.
To set VLAN Pbits to Queue Table, do the following:
2. Type: qos-set-vlan-tag-pbit-val <VLAN_Pbit> <queue ID: 1st-queue, 2nd-queue, 3rd-

queue, 4th-queue >, and press Enter.
To set IP Pbits to Queue Table, do the following:
2. Type: qos-set-ip-pbit-val <IP_Pbit> <queue ID: 1st-queue, 2nd-queue, 3rd-queue, 4th-

queue>, and press Enter.
To set IP priority options, do the following:
2. Type: set qos-ip-tos-tc-pbits-option <diffserv, ip-precedence>, and press Enter.
To set static MAC table, do the following:
2. Type: qos-static-mac-priority set/remove <MAC address> <dest.port no.[1-8]> <priority

[0-7]> <VLAN ID [1-4090]> , and press Enter.
To set Queue Weights table, do the following:
2. Type: qos-set-scheduler-q-weight <queue ID: 1st-queue, 2nd-queue, 3rd-queue, 4th-

queue > <weight:1-32>, and press Enter.

Auxiliary Channels
Wayside Channel
At the command prompt, type: cd interfaces/wayside/, and press Enter.
To set port admin, do the following:
1. Type: set admin <enable/disable>, and press Enter.
To set port rate:
1. Type: set ethernet-rate <10mbps or 100mbps>, and press Enter.
To set auto negotiation on/off:
1. Type: set auto-negotiation <on/off>, and press Enter.
To set port duplex:
1. Type: set duplex <full-duplex or half-duplex>, and press Enter.
User Channel
1. At the command prompt, type: cd interfaces/auxiliary/user-channel/, and press Enter
To set port admin:
1. Type: set admin <enable/disable>, and press Enter.
To set port type:
1. Type: set type asynchronous-<rs232 or v-11>, and press Enter.

Automatic State Propagation, 1+0 Configuration Only
At the command prompt, type: cd interfaces/ethernet/, and press Enter.
To set Automatic state Propagation (also called GBE-mute-override) in Single Pipe application:
1. Type: set-gbe-mute-override <criteria: none, lof-loc, lof-loc-excber, lof-loc-remote, lof-

loc-excber-remote >, and press Enter.
To set Automatic state Propagation (also called GBE-mute-override) in Managed/Metro

application:
1. Type: set-gbe-mute-override <criteria: none, lof, lof-excber, lof-remote, lof-excber-

remote >, and press Enter.
Ethernet Shutdown (Rx) Profile Threshold (when ACM is enabled)
At the command prompt, type: cd radio/mrmc/, and press Enter
To set Ethernet shutdown (Rx) profile threshold:
1. Type: set eth-shutdown-threshold-profile < profile-0 to profile-7 >, and press Enter.
Metro Switch and Port Type Configuration

To set Metro Switch:
1. At the prompt (IP-10:/>), type cd interfaces/ethernet/bridge/, and press Enter.
2. At the new prompt, type set ethernet-application metro-switch, and press Enter.
3. Confirm by typing yes, and press Enter.
The system will restart automatically.

To set the port type (CN/PN):
1. At the prompt (IP-10:/>), type cd interfaces/ethernet/bridge/eth-port[port no.], and press

Enter.
2. At the new prompt, type set type customer-network (or provider-network), and press Enter.
To set Default VLAN on CN ports:

Enter.
2. At the new prompt, type set vlan <VLAN ID>, and press Enter.
To set Allowed VLANs on PN ports:

Enter.
2. At the new prompt, type set-allowed-vlans <add,all,except,no-vlans,remove> <VLAN ID>,

and press Enter.
To set provider port ether type:
1. At the prompt (IP-10:/>), type cd interfaces/ethernet/bridge/, and press Enter.
2. At the new prompt, type set provider-port-ethertype <0x88a8, 0x8100, 0x9100, 0x9200>,
and press Enter.

Radio Script Configuration
To set the radio script:
1. At the prompt (IP-10:/>), type cd radio/mrmc/, then press Enter.
2. At the new prompt, type change-script-cmd < Script's name> < Operational mode>
<Maximum profile> disable-adaptive-power, then press Enter.
Parameter values for the radio script include:
Script Name
10Mbps-6.5MHz-4QAM-Grade-1
155Mbps-26MHz-128QAM-Grade-1
ACM_181Mbps-26MHz-256QAM-Grade-1
ACM_367Mbps-52MHz-256QAM-Grade-1
ACM_42Mbps-6.5MHz-256QAM-Grade-1
ACM_87Mbps-12.5MHz-256QAM-Grade-1
Operational Mode
acm-adaptive-mode
acm-fixed-mode
regular-mode (for non ACM scripts)
Maximum Profile
Note: For ,choose a specific profile for ACM fixed mode . In regular mode only profile-0 is
available.
profile-0
profile-1
profile-2
profile-3
profile-4
profile-5
profile-6
profile-7

Configuration Backup
The configuration backup file must be transferred between the main unit and an external site by
FTP. Configuration files may be transferred between the extension units and the main unit.
Setting External FTP Client Site Parameters

To define the FTP settings, do the following at the main unit:
1. At the command prompt, type: /platform/idc-board, and press Enter.
2. Type: set set host-ip <ip> (the clients IP address), and press Enter.
3. Type: set host-path <path> (the site to the desired file location at the client), and press Enter.
4. Type: set set user-name <user-name> (the user name expected from client), and press
Enter.
5. Type: change-user-password and press Enter; upon prompt write the password expected
from client, and press Enter.
Creating Backup Files of Existing Configuration

1. At the command prompt, type: cd /platform/shelf-manager/
2. In order to create the backup file for a certain slot, type: config-backup --unit <slot number>,
and press Enter.
2. In order to create the backup file for a all the slots in the shelf, type: config-backup --all, and
press Enter.
Saving Configuration Files in External Site

1. At the command prompt, type: cd /platform/idc-board/
2. In order to upload the file to the FTP client, type: upload-archive configuration, and press
Enter.
3. In order to see the upload status, type: get config-upload-status, and press Enter.
"ready" means "no action was taken, ready to continue"
A successful result will give "succeeded"
Downloading Saved Configuration Files

1. At the command prompt, type: cd /platform/idc-board/
2. In order to download the file from the FTP client, type: download-archive configuration, and
press Enter.

3. In order to see the upload status, type: get config-download-status, and press Enter.
Restoring Configuration from Files

1. At the command prompt, type: cd /platform/shelf-manager/
2. In order to create the backup file:
For a certain slot, type: config-restore --unit <slot number>, and press Enter.
For all the slots in the shelf, type: config-restore --all, and press Enter.
3. In order to reset the relevant units: reset-extensions reset-shelf reset-unit
For a certain slot, type: reset-unit <slot number>, and press Enter.
For all the slots in the shelf, type: reset-shelf, and press Enter.
For all the extension slots in the shelf, type: reset-extensions, and press Enter.
Software Version Management

The software version files must be transferred between the main unit and an external site by FTP.
Form the main unit they can be deployed to the extension units.

1. At the command prompt, type: /management/mng-service/mng-software, and press Enter.
2. Type: set server-url <ip/path> (the clients IP address and files path), and press Enter.
3. Type: set server-login <user-name> (the user name expected from client), and press Enter.
5. Type: change-server-password and press Enter; upon prompt write the password expected
Upgrading to a more Advanced Version

1. Type: download, and press Enter. This will download the new package.
2. In order to install the downloaded file:

For a certain slot, type: upgrade --unit <slot number>, and press Enter.
For all the slots in the shelf, type: upgrade --all, and press Enter.
Downgrading to a Previous Version

1. Type: download --downgrade, and press Enter. This will download the package.
2. In order to install the downloaded file:
For a certain slot, type: downgrade --unit <slot number>, and press Enter.
For all the slots in the shelf, type: downgrade --all, and press Enter.
Rollback Procedure
In order to rollback to the previously installed version:
For a certain slot, type: rollback --unit <slot number>, and press Enter.
For all the slots in the shelf, type: rollback --all, and press Enter.

Using CLI scripts
CLI scripts are text files containing CLI commands which can be downloaded and run in the main
unit only.

1. At the command prompt, type: /platform/idc-board, and press Enter.
2. Type: set set host-ip <ip> (the clients IP address), and press Enter.
3. Type: set host-path <path> (the site to the desired file location at the client), and press Enter.
4. Type: set set user-name <user-name> (the user name expected from client), and press
Enter.
5. Type: change-user-password and press Enter; upon prompt write the password expected
Downloading CLI Scripts from FTP Client

1. At the command prompt, type: cd /platform/idc-board/, and press Enter.
2. Type: set cli-script-file-name<file name> (the scripts file name), and press Enter.
3. In order to download the file from the FTP client, type: download-archive cli-script, and press
Enter.
4. In order to see the upload status, type: get download-cli-script-status, and press Enter.
Managing and Executing Scripts

1. In order to see the contents of the currently loaded script, type: cli-script show, and press
Enter.
2. In order to execute the currently loaded script, type: cli-script execute, and press Enter.
3. In order to delete the currently loaded script, type: cli-script delete, and press Enter.

Radio Parameter Configurations
To set TX frequency:
1. Type cd /radio/rfu/ set tx-freq <frequency in KHz>, then press Enter.
To set RX frequency:
1. Type cd /radio/rfu/ set rx-freq <frequency in KHz>, then press Enter.
To set TX power level:
1. Type cd /radio/rfu/max-tx-level <TX level in dBm>, then press Enter.
To mute/unmute the TX:
1. Type cd /radio/rfu/ set mute-tx <disable/enable>, then press Enter.
To set ATPC reference level:
1. Type cd /radio/rfu/ set atpc-ref-rx-level <reference level in dBm>, then press Enter.
To enable ATPC:
1. Type cd /radio/rfu/ set atpc-admin <enable/disable>, then press Enter.
To set RX level PM threshold1:
1. Type cd /radio/rfu/ set pm-rx-level-threshold-1 <threshold in dBm>, then press Enter.
To set RX level PM threshold2:
1. Type cd /radio/rfu/ set pm-rx-level-threshold-2 <threshold in dBm>, then press Enter.

To set TX level PMs threshold:
1. Type cd /radio/rfu/ set pm-tx-level-threshold <threshold in dBm>, then press Enter.
To enable/disale MAC header compression:
1. Type cd /radio/ set mhc-admin <enable/disable>, then press Enter.
To set Link-ID:
1. Type cd /radio/framer/ set link-id <Link-ID number>, then press Enter.
To set radio excessive BER threshold:
1. Type cd /radio/framer/ set radio-excessive-ber-threshold <BER: 1e-3, 1e-4, 1e-5>, then

press Enter.
To set radio signal degrade threshold:
1. Type cd /radio/framer/ set radio-signal-degrade-threshold <BER: 1e-6, 1e-7, 1e-8, 1e-9>,

then press Enter.
To set MSE PMs threshold:
1. Type cd /radio/modem/set mse-threshold <Threshold in dB>, then press Enter.
NTP
To set NTP service enable/disable:
1. At the command prompt, type: cd /management/mng-services/time-service/ntp, and press

Enter.
2. Type set server 192.168.1.100, and press Enter.
3. Type set admin <enable/disable>, and press Enter.
To set NTP offset from GMT:
1. At the command prompt, type: cd management/mng-services/time-service/, and press

Enter.
2. Type set gmt-offset-hours 2, and press Enter.
3. Type set gmt-offset-minutes 0, and press Enter.

To set Daylight Saving Time:
1. At the command prompt, type: cd /management/mng-services/time-service, and press

Enter.
2. Type set dst-start-month Apr, and press Enter.
3. Type set dst-start-day 1, and press Enter.
4. Type set dst-end-month Nov, and press Enter.
5. Type set dst-end-day 1, and press Enter.
To set Date and Time, whereby the time and date format are day-month-year,hours:mins:secs:
1. At the command prompt, type : cd /management/mng-services/time-service, and press

Enter.
2. Type set time-and-date 10-3-2009,15:00:00, and press Enter.
SNMP
To set SNMP enable/disable:
1. At the command prompt, type: cd /management/mng-protocols/snmp, and press Enter.
2. Type set admin <enable /disable>, and press Enter.
To set the SNMP version:
2. Type set version v3 (or v1 for SNMP version 1), and press Enter.
SNMP Parameters for SNMP Version 3
To set the security mode to authentication, and the authentication algorithm to sha:
2. Type change-user-settings user_name_example authentication sha, and press Enter.
3. Enter the SNMPv3 Password: user_password_example, and press Enter.
To set the security mode to authentication-privacy, and the Authentication algorithm to md5:

2. Type change-user-settings user_name_example authentication-privacy md5, and press
Enter.
3. Enter the SNMPv3 Password: user_password_example, and press Enter.
To set the security mode to no-security, and the authentication algorithm to no authentication:
2. Type change-user-settings no-se-user no-security no-auth, and press Enter.
To set the telnet protocol to enable/disable:
1. At the command prompt, type: cd /management/mng-protocols, and press Enter.
2. Type set telnet-admin <enable/disable>, and press Enter.
To set web GUI to enable/disable:
2. Type set web-admin <enable/disable>, and press Enter.
The following steps are used to define the web protocol that will work with HTTPS
It is important to note the order!
Step 1: Create the NE certificate based on the NE's public key. The public key receives the public
key file through upload.
1. At the command prompt, type: cd /platform/idc-board, and press Enter.
2. Type upload-archive public-key, and press Enter.
You can find your public_key file (such as 192.168.1.18_pub_key) in your host path directory.
Step 2: Download the NE certificate.
Note: Before you download the certificate, copy your NE certificate to your ftp host path directory.
2. Type set security-file-format <pem/der>, and press Enter.
3. Type set security-file-type <target-certificate>, and press Enter.
4. Type set security-file-name <MYCERT.crt> (your certificate file name), and press Enter.
5. Type download-archive security-file, and press Enter.

Step 3: (Optional) Download the NE CA's certificate.
2. Type set security-file-format <pem/der>, and press Enter.
3. Type set security-file-type <target-ca-certificate>, and press Enter.
4. Type set security-file-name <EssentialSSLCA_2.crt> (your CA-certificate file name), and

press Enter.
5. Type download-archive security-file, and press Enter.
Step 4: (Optional) Set the web-ca-certificate-admin parameter to enable.
2. Type set web-ca-certificate-admin <enable> /<disable>, and press Enter.
Step 5: Set the web-protocol parameter to https.
2. Type set web-protocol <https> /<http>, and press Enter.
Note: Enter the URL in the WEB GUI, such as https://192.168.1.1 to use the https protocol.

CFM
Domain
Under service-oam level
Creation:
IP-10:/interfaces/ethernet/bridge/service-oam> domain add <Domain name> <Domain level [1-7]>
, and press Enter.
Deletion:
IP-10:/interfaces/ethernet/bridge/service-oam> domain remove <Domain name> <Domain level
[1-7]> , and press Enter.
Domain & Association

Creation:
IP-10:/interfaces/ethernet/bridge/service-oam> domain add <Domain name> <Domain level [1-7]>
<Association name> <VLAN ID [1-4090]> , and press Enter.
Deletion:
IP-10:/interfaces/ethernet/bridge/service-oam> domain remove <Domain name> <Domain level
[1-7]> <Association name> <VLAN ID [1-4090]> , and press Enter.
Association
Under service-oam level:
Creation
IP-10:/interfaces/ethernet/bridge/service-oam> association add <Association name> <Domain
name> <VLAN ID [1-4090]> , and press Enter.
Deletion
IP-10:/interfaces/ethernet/bridge/service-oam> association remove <Association name>
<Domain name> <VLAN ID [1-4090]> , and press Enter.
CCM
On
IP-10:/interfaces/ethernet/bridge/service-oam> ccm-admin enable <Domain level [1-7]> <VLAN
ID [1-4090]> , and press Enter.
Off
IP-10:/interfaces/ethernet/bridge/service-oam> ccm-admin disable <Domain level [1-7]> <VLAN
ID [1-4090]> , and press Enter.

Local MEP
Under interfaces level
Creation
1. IP-10:/interfaces/ethernet/bridge/eth-port [x]> mep set < MEP ID [1-8191]> < Domain level [1-
7]> <VLAN ID [1-4090]> < Direction [up/down]> <CCM VLAN Pbit priority [0-7]> , and press
Enter.
2. IP-10:/interfaces/ethernet/bridge/eth-port [x]> mep set < MEP ID [1-8191]> < Domain level [1-
7]> <VLAN ID [1-4090]> < Direction [up/down]> , and press Enter.
Deletion
IP-10:/interfaces/ethernet/bridge/eth-port [x]> mep remove < MEP ID [1-8191]> < Domain level [1-
7]> <VLAN ID [1-4090]> < Direction [up/down]> , and press Enter.
Remote MEP
Creation
1. IP-10:/interfaces/ethernet/bridge/service-oam> remote-mep set <Remote MEP ID [1-8191]>
<Domain name> <VLAN ID [1-4090]> <MAC address [xx:xx:xx:xx:xx:xx]> , and press Enter.
2. IP-10:/interfaces/ethernet/bridge/service-oam> remote-mep set <Remote MEP ID [1-8191]>
Deletion
IP-10:/interfaces/ethernet/bridge/service-oam> remote-mep remove <Remote MEP ID [1-8191]>

MIP
Under interfaces level
Creation
IP-10:/interfaces/ethernet/bridge/eth-port[x]> mip add <Domain level [1-7]> , and press Enter.
Deletion
IP-10:/interfaces/ethernet/bridge/eth-port[x]> mip remove <Domain level [1-7]> , and press Enter.
Loopback (Ping)
1. IP-10:/interfaces/ethernet/bridge/service-oam> ping mac-address <MAC address
[xx:xx:xx:xx:xx:xx]> md-name <Domain name> <VLAN ID[1-4090]> <VLAN Pbit priority[0-7]> ,
and press Enter.
[xx:xx:xx:xx:xx:xx]> md-name <Domain name> <VLAN ID[1-4090]> , and press Enter.

[xx:xx:xx:xx:xx:xx]> md-level <Domain level[1-7]> <VLAN ID[1-4090]> <VLAN Pbit priority[0-
7]> , and press Enter.
[xx:xx:xx:xx:xx:xx]> md-level <Domain level[1-7]> <VLAN ID[1-4090]> , and press Enter.
5. IP-10:/interfaces/ethernet/bridge/service-oam> ping mep-id <Remote MEP ID[1-8191]> md-
name <Domain name> <VLAN ID[1-4090]> <VLAN Pbit priority[0-7]> , and press Enter.
name <Domain name> <VLAN ID[1-4090]> , and press Enter.
level <Domain level[1-7]> <VLAN ID[1-4090]> <VLAN Pbit priority[0-7]> , and press Enter.
level <Domain level[1-7]> <VLAN ID[1-4090]> , and press Enter.
Link Trace
1. IP-10:/interfaces/ethernet/bridge/service-oam> linktrace mac-address <MAC address
[xx:xx:xx:xx:xx:xx]> md-name <Domain name> <VLAN ID[1-4090]> <VLAN Pbit priority[0-7]> ,
and press Enter.
[xx:xx:xx:xx:xx:xx]> md-name <Domain name> <VLAN ID[1-4090]> , and press Enter.
[xx:xx:xx:xx:xx:xx]> md-level <Domain level[1-7]> <VLAN ID[1-4090]> <VLAN Pbit priority[0-
7]> , and press Enter.
[xx:xx:xx:xx:xx:xx]> md-level <Domain level[1-7]> <VLAN ID[1-4090]> , and press Enter.
5. IP-10:/interfaces/ethernet/bridge/service-oam> linktrace mep-id <Remote MEP ID[1-8191]>
md-name <Domain name> <VLAN ID[1-4090]> <VLAN Pbit priority[0-7]> , and press Enter.
md-name <Domain name> <VLAN ID[1-4090]> , and press Enter.
md-level <Domain level[1-7]> <VLAN ID[1-4090]> <VLAN Pbit priority[0-7]> , and press Enter.
md-level <Domain level[1-7]> <VLAN ID[1-4090]> , and press Enter.
Auto Link Trace

Under service-oam level:
Creation
1. IP-10:/interfaces/ethernet/bridge/service-oam> auto-linktrace add <Remote MEP ID [1-8191]>
md-name <Domain name> <VLAN ID[1-4090]> <VLAN Pbit priority[0-7]> , and press Enter.
md-name <Domain name> <VLAN ID[1-4090]> , and press Enter.

md-level <Domain level[1-7]> <VLAN ID[1-4090]> <VLAN Pbit priority[0-7]> , and press Enter.
md-level <Domain level[1-7]> <VLAN ID[1-4090]> , and press Enter.
Deletion
1. IP-10:/interfaces/ethernet/bridge/service-oam> auto-linktrace remove <Remote MEP ID [1-
8191]> md-name <Domain name> <VLAN ID[1-4090]> , and press Enter.
2. IP-10:/interfaces/ethernet/bridge/service-oam> auto-linktrace remove <Remote MEP ID [1-
8191]> md-level <Domain level[1-7]> <VLAN ID[1-4090]> , and press Enter.
CCM Interval
Modification
IP-10:/interfaces/ethernet/bridge/service-oam> ccm-interval <interval time: 1-sec, 10-sec, 1-min,
10-min> <Domain level [1-7]> <VLAN ID [1-4090]> , and press Enter.
Auto Link Trace Interval

Modification
IP-10:/interfaces/ethernet/bridge/service-oam> set auto-linktrace-interval [seconds: range 60-
3600] , and press Enter.
Remote MEP Learning Time

Modification
IP-10:/interfaces/ethernet/bridge/service-oam> set remote-meps-learning-time [seconds: range
60-3600] , and press Enter.
Ring RSTP
To enable Ring RSTP:
1. Type cd /interfaces/ethernet/bridge/ set stp-protocol ring-rstp, and press Enter.
To set bridge priority:
Type cd /interfaces/ethernet/bridge/ set priority <priority no: range 0-61440, steps of 4096>,
and press Enter.

To set interfaces priority:
Type cd /interfaces/ethernet/bridge/ethe-port[port no.]/ set priority <interface priority no:

range:0-240, steps of 16>, and press Enter.
To set interfaces patch cost:
Type cd /interfaces/ethernet/bridge/ethe-port[port no.]/ set path-cost <patch cost>, and press

Enter.
To set if interface is an edge port or ring port (non-edge port):
Type cd /interfaces/ethernet/bridge/ethe-port[port no.]/ set edge-port <yes/no>, and press

Enter.

9/26/2010
FibeAir IP-10 Cables & Adapters
Preliminary Questions
Whatistherequiredlength? ________[m/ft]
Terminationtype Openend/RJ45Male/RJ45Female/75Ohm/BNC
IDUConnector Rightangled/Leftangled?
PDH(E1/DS1)
NumberofE1ports 4/8/16
ProtectionPanelrequired? YES/NO
Adaptersrequired? YES/NO
Whatistherequiredlength? ________[m/ft]
ETHERNET
Pinlayout Crosscable/Straightcable
Wh t i th i dl th?
Whatistherequiredlength? [ /ft]
________[m/ft]
FiberOptics Core/Mode MultiMode/SingleMode
LongReach? YES/NO
UserChannel Mode Synchronous/Asynchronous
PAGE 561 1
9/26/2010
ETHERNET CABLES
Protection Cable
X-WSC-E1 WA-0242-0
X-WSC-T1 WA-0242-0
Cross Ethernet CAT 5 cable (Male - Male)

Used in order to connect two IDUs in hot standby mode (Protected) when
working without enclosure
Length 0.2 M
PAGE 562 2
9/26/2010
Connection Cables
X-2FE-CON WA-0235-0
Cross Ethernet Cable CAT 5 (Male - Male).

Same as pprevious cable,, onlyy longer
g
Used for cross connection between devices
Length 2M
ETH Y-Cables
15P-PROT-CBL WA-0244-0
Ethernet CAT-5 Y Cable (2xMale 1xFemale)

Used in hot standby (protected) configurations in order to provide single
input/output from the two IDUs
Length 0.3 M
Uses extension X-2FE-CON (in order to convert the common port to Male)
15PPROTCBL
X2FECON
PAGE 563 3
9/26/2010
PDH CABLES
E1 Extension Cable
IP10-CBL-16E1-OE-3M WA-0400-0
In use to connect to the IP-10 16E1 connector on one end and have open
ends for the 16E1 on the other side ((on 120 ohm))
A male SCSI68 Left angle120 OHM cable
When conversion to 75 ohm is required a special adaptation panel is
needed
Length 3M
Additional Optional length (5, 10, 15 meter):

IP10-CBL-16IO-10M
IP10-CBL-16IO-25M
IP10-CBL-16IO-5M
PAGE 564 4
9/26/2010
T1 Extension Cable
IP10-CBL-16T1-OE-3M WA-0413-0
In use to connect to the IP-10 16E1 connector on one end and have open
ends for the 16T1 on the other side ((on 100 ohm))
A male SCSI68 Left angle100 OHM cable
Length 3M
Additional Optional length (5, 10, 15 meter):
IP10-CBL-16T1-10M
IP10-CBL-16T1-25M
IP10-CBL-16T1-5M
E1 Y-Cable
IP10-CBL-16E1-PROT-Y WA-0391-0
16E1 Y-Splitter 120 OHM cable

2 x Male connectors connect to IP
IP-10s
10s
1 x Female SCSI68 Left-angled connector
Use in protected mode 1+1 or 2+2 to connect the 2x16T1 ports of the IDUs
to external single source
Length 0.6 M
IP10CBL16E1OE3M
PAGE 565 5
9/26/2010
T1 Y-Cable
IP10-CBL-16T1-PROT-Y WA-0398-0
16T1 Y-Splitter 100 OHM cable

2 x Male connectors connect to IP
IP-10s
10s
1 x Female SCSI68 Left-angled connector
Use in protected mode 1+1 or 2+2 to connect the 2x16T1 ports of the IDUs
to external single source
Length 0.6 M
IP10CBL16T1OE3M
PDH Expansion Panels

The panels act as distribution frames for E1/T1 cables
Orders need to include: Cables + Adapters + Frames
Adapters support 75Ohm or 120 Ohm
PAGE 566 6
9/26/2010
E1 Expansion Panel with RJ45 Female Sockets

IP10-CBL-16E1MDRLA-RJ45-XD1.5m WA-0407-1 cable
kits of 8 female-female adaptors order 2

IP10-ADAP-RJ45F-E1/T1-XED x8 NM-0153-0 to connect 16 E1s
IP10-PANEL-32E1/T1-RJ45 EN-0268-0 Chassis/frame only

A male SCSI68 Left angled 120 OHM cable with
RJ 45 Adaptors
2 kits of 8 female-female adaptors should be
ordered for 16T1 (optional)
Length 1.5M
Optional length
IP10-CBL-16T1-MDRLA-RJ45-XD1.5m
IP10-CBL-16T1-MDRLA-RJ45-XD3m
T1 Expansion Panel with RJ45 Female Sockets

IP10-CBL-16T1MDRLA-RJ45-XD1.5m WA-0411-1 cable
kits of 8 female-female adaptors

IP10-ADAP-RJ45F-E1/T1-XED x8 NM-0153-0 order 2 to connect 16 E1s
IP10-PANEL-32E1/T1-RJ45 EN-0268-0 Chassis/frame only

A male SCSI68 Left angled100 OHM cable with
RJ 45 Adaptors
2 kits of 8 female-female adaptors should be
ordered for 16T1 (optional)
Length 1.5M
Optional length
IP10-CBL-16T1-MDRLA-RJ45-XD1.5m
IP10-CBL-16T1-MDRLA-RJ45-XD3m
PAGE 567 7
9/26/2010
E1 Expansion Panel with 75 Ohms Sockets

IP10-CBL-16E1-MDR-MDR-06.m WA-0402-0 cable
IP10-16E1-ADAP-PANEL-75ohm-BNC EN-0313-0 Chassis/frame only
Use for 16E1 expansion to unbalanced 75

ohm connectors with BNC
A two way male SCSI68 cable
Length 0.6M
Optional length
IP10-CBL-16E1-MDR-MDR-1.5m
IP10 CBL 16E1 MDR MDR 1.5m
IP10-CBL-16E1-MDR-MDR-5m
No. in Diagram Model Description
1 IP10CBL16E1MDRMDR0.6m/1.5m/5m IP1016E1portscablestraight0.6/1.5m/5m
2 IP10PANEL16E1ADAP75ohmBNC IP1016E1panelw/75ohmadapter,BNC
E1 Extension Cable with RJ45 Female

IP10-CBL-4E1-RJ45F-0.3m WA-0383-0
A male SCSI68 Left angle120 OHM cable with RJ 45 Adaptors

In use for 16E1 connector separation to 4 single E1s (on 120 ohm)
Length 0.3M
PAGE 568 8
9/26/2010
T1 Extension Cable with RJ45 Female

IP10-CBL-4T1-RJ45F-0.3m WA-0433-0
A male SCSI68 Left angle100 OHM cable with RJ 45 Female Adaptors

In use for 16T1 connector separation to 4 single T1s
Length 0.3M
E1 Extension Cable with RJ45 Male to Male

IP10-CBL-8E1-MDR-RJ45-1.5m WA-0431-0
A male SCSI68 Left angle120 OHM cable with RJ 45 Female Adaptors

In use for 16E1 separation to 8 single E1s (on 120 ohm)
When conversion to 75 ohm is required a special adaptation panel is
needed
Length 1.5M
Optional length and number of E1s:

IP10-CBL-4E1-MDR-RJ45-XED-0.3m
IP10-CBL-8E1-MDR-RJ45-XED-0.3m
P10-CBL-8E1-MDR-RJ45-XED-1.5m
PAGE 569 9
9/26/2010
T1 Extension Cable with RJ45 Male to Male

IP10-16T1-MDR-RJ45-XED-1.5m WA-0373-0
A male SCSI68 Left angle100 OHM cable with RJ 45 Adaptors

In use for 16E1 separation to 16 single T1 (on 100 ohm)
Length 1.5M
Optional length
IP10-CBL-16T1-MDR-RJ45-XED-3m
OPTICAL CABLES
20
PAGE 570 10
9/26/2010
Single Mode Transceiver (OTR/GBIC)

SFP-GE-LX ER-1002-0
SFP Optical interface for Gigabit Ethernet (plug-in)

Used when an Optical connection is needed up to 10KM
Optical Y-Splitter Single Mode

GBE-SPL-SM AO-0038-0
Optical Y Splitter for protected 1+1 mode (3x Male)

2 cables should be ordered: 1 for RX and 1 for TX
PAGE 571 11
9/26/2010
Optical Adapter Interface Single Mode

OP-SM-LC-LC-ADPT-DPLX AO-0043-0
Optical adaptor (Female/Female)
Used as an adaptor between the Y cable to the extension cable
2 adaptors should be ordered: 1 for RX and 1 for TX Y cables
Optical Extension Cable Single Mode

OP-SM-CBL-LC-LC-DPLX 3M AO-0071-0
Used as an extension cable to the Y cable, connected via an adaptor

Length
g 3M
Optional length
OP-SM-CBL-LC-LC-DPLX 10M
OP-SM-CBL-LC-LC-DPLX 3M
PAGE 572 12
9/26/2010
Optical H-Cable Single Mode / Multi Mode

OP-SM-HSPL-LC-LC 0.5M/0.5M AO-0087-0
OP-MM-HSPL-LC-LC 0.5M/0.5M AO-0089-0
H Optical cable
Used to interconnect between two protected terminals (logically equivalent to two
Y splitters connected to each other via their common port)
2 cables should be ordered
TX of 1 device should be connected to RX of the other
Optical H-Cable Single Mode / Multi Mode

SFP-STM-1-S1.1 AO-0072-0
SFP for channelized STM-1 / OC-3 T-Card

Single Mode
Mode, Short Haul 1310nm
All cables and adaptors from slides 12-15 and 17 are also relevant in
the STM-1/OC-3 case
PAGE 573 13
9/26/2010
ALARMS CABLES
27
Alarm Cable with Protection

IP10-EXT-ALARMS-CBL-2.5M-PROT WA-0369-0
Used for connecting 1+1 alarms with Y cable

2nd end - Open
p Cable
Length 2.5M
PAGE 574 14
9/26/2010
Alarm Cable without Protection

IP10-EXT-ALARMS-CBL-2.5M WA-0374-0
Used for connecting 1+0 alarms

2nd end - Open
p Cable
Length 2.5M
USER CHANNEL CABLES
30
PAGE 575 15
9/26/2010
User Channel Asynchronous Cable

15R-USER-CHAN-ASYNC-CBL-2.5M WA-0288-0
Asynchronous, open cable

Used when working on 1+0 for the user channel connection
Length 2.5 M
User Channel Asynchronous Cable - Protection

15R-USER-CHAN-ASYNC-CBL-2.5M WA-0288-0
Asynchronous, open cable

Used when working on 1+0 for the user channel connection
Length 2.5 M
Used when working on 1+1 or 2+2 for the user channel connection
Y cable 15P-PROT-CBL (WA-0244-0) is required
15R-USER-CHAN-ASYNC-CBL-2.5M
15P-PROT-CB
PAGE 576 16
9/26/2010
User Channel Synchronous Cable

15R-USER-CHAN-SYNC-CBL-2.5M WA-0289-0
SYNC Cable
Used when working on 1+0 user channel connection
Length 2.5 M
User Channel Synchronous Cable - Protection

15R-USER-CHAN-SYNC-CBL-2.5M WA-0289-0
SYNC Cable
Used when working on 1+1 or 2+2 for the user channel connection
Length 2.5 M
Uses the Y cable 15P-PROT-CBL
Two Y cables should be ordered to support protection mode
PAGE 577 17
9/26/2010
IF CABLES
35
IDU-ODU IF CABLE
IDU_ODU_CBL WA-0098-0
N_TYPE WA-0037-0
RG8 Cable for IF (without connectors)

IDU_ODU_CBL (Should be ordered per meter)
Optional length (pre-defined):
IDU_ODU_CBL_100Meter
IDU_ODU_CBL_200m
IDU_ODU_CBL_500m
BNC Connector
N
N-Type
Type
Needs two per cable
PAGE 578 18
9/26/2010
PART NUMBERS
37
E1
E1 Open End Termination Cables
Ceragon PN Marketing Model Marketing Description Item Description
CABLE,SCSI68 LEFT ANGLE TO

WA-0277-0 IP10-CBL-16IO-5M IP-10 16 I/O ports cable open 5M
OE,5M,120 OHM

OE,10M,120 OHM

OE,25M,120 OHM
WA-0400-0 IP10-CBL-16E1-OE-3M IP-10 16E1 cable open-end, 3M
WA-0404-0 IP10-CBL-8E1-OE-3M IP-10 8E1 cable open-end, 3M
E1RJ45female(socket)terminationcables
Ceragon P/N Marketing Model Marketing Description
WA-0383-0 IP10-CBL-4E1-RJ45F-0.3M IP-10 4E1 ports RJ45 socket (female), 0.3M
38
PAGE 579 19
9/26/2010
E1
E1RJ45maleterminationcables/panels
CeragonP/N MarketingModel MarketingDescription Itemdescription
CABLE,SCSI68MaleTO4xRJ45Male
WA03960 IP10CBL4E1MDRRJ45XED0.3m IP104E1cableMDR68RJ450.3M,cross
CROSS,0.3M,120OHM
,S S 68 a e O 8 5 ae
WA 0395 0
WA03950 IP10 CBL 8E1 MDR RJ45 XED 0 3
IP10CBL8E1MDRRJ45XED0.3m IP 10 8E1 bl MDR68 RJ45 0 3M
IP108E1cableMDR68RJ450.3M,cross
CROSS,0.3M,120OHM
CROSS,1.5M,120OHM
WA03941 IP10CBL8E1MDRRJ45XED3m IP108E1cableMDR68RJ453M,cross
CROSS,3M,120OHM
WA04091 IP10CBL16E1MDRLARJ45XD3m IP1016E1cableMDR68RJ453M,LA,cross
CABLE,SCSI68PINTO16*RJ45,1.5M,120
WA04071 IP10CBL16E1MDRLARJ45XD1.5m IP1016E1cableMDR68RJ451.5M,LA,crs
Ohm,LEFT ANGLE,CROSS
WA04440 IP10CBL16E1MDRLARJ45XD1.25m IP1016E1cableMDR68RJ45,Cross,1.25M

WA04290 IP10CBL4E1MDRRJ450.3m IP104E1cableMDR68RJ450.3M
Ohm
Ohm
Ohm
CABLE,SCSI68PINTO8*RJ45,3M,120
WA04321 IP10CBL8E1MDRRJ453m IP108E1cableMDR68RJ453M
Ohm
WA04011 IP10CBL16E1MDRLARJ451.5m IP1016E1cableMDR68RJ451.5M,L.Ang.
CABLE,SCSI68PINTO16*RJ45,3M,120
WA04351 IP10CBL16E1MDRLARJ453m IP1016E1cableMDR68RJ453M,L.Angle
Ohm,LEFT ANGLE
39
E1
E1 RJ45 couplers/panels
Status Ceragon P/N Marketing Model Marketing Description
NPI EN-0268-0 IP10-PANEL-32E1/T1-RJ45 IP-10 32E1/T1 panel, for RJ45F adapters
Released NM-0153-0 IP10-ADAP-RJ45F-E1/T1-XED x8 IP-10 RJ45F/RJ45F adapter,E1/T1,cross x8
Released NM-0154-0 IP10-ADAP-RJ45F-RJ45F x8 IP-10 RJ45F/RJ45F adapter, straight x8
E1 RJ45 - RJ45 cables

WA-0417-0 IP10-CBL-E1-RJ45-RJ45-0.6m IP-10 E1 RJ45 cable 0.6m, str. (green)
WA-0418-0 IP10-CBL-E1-RJ45-RJ45-1m IP-10 E1 RJ45 cable 1m, straight (green)
WA-0419-0 IP10-CBL-E1-RJ45-RJ45-2m IP-10 E1 RJ45 cable 2m, straight (green)
WA-0414-0 IP10-CBL-E1-RJ45-RJ45-XED-0.6m IP-10 E1 RJ45 cable 0.6m, cross (blue)
WA-0415-0
WA 0415 0 IP10-CBL-E1-RJ45-RJ45-XED-1m
IP10 CBL E1 RJ45 RJ45 XED 1m IP-10
IP 10 E1 RJ45 cable 1m, cross (blue)
WA-0416-0 IP10-CBL-E1-RJ45-RJ45-XED-2m IP-10 E1 RJ45 cable 2m, cross (blue)
E1 75ohm termination cables/panels (with optional integrated protection)

EN-0313-0 IP10-PANEL-16E1-ADAP-75ohm-BNC IP-10 16E1 panel w/ 75ohm adap , BNC
EN-0315-0 IP10-PANEL-16E1-PROT-75ohm-BNC IP-10 16E1 panel w/ 75ohm adap&prot, BNC
40
PAGE 580 20
9/26/2010
E1
E1Protectionpanels/cables
CeragonP/N MarketingModel MarketingDescription
WA03910 IP10CBL16E1PROTY IP1016E1protectionYcable,MDR68
E1MDR69 MDR69crosscables(forchainingapplications)
WA03820 IP10CBL16E1MDRMDRXED2m IP1016E1portscrossedcable2m
E1specialcables/panels(notforpricelist)
WA03750 IP10CBL16E1MDR2xDTYPE1.5m /
IP1016E1cableMDR68/2xDB371.5m
WA04081 IP10CBL16E1MDRRARJ45XD1.5m IP1016E1cableMDR68RJ451.5M,RA,crs
WA03930 IP10CBL16E1MDRRJ45XED3m IP1016E1cableMDR68RJ453M,cross
WA04030 IP10CBLE1RJ45RJ45FXED0.3m IP10E1RJ45toRJ45Fcable0.3m,cross
WA04340 IP10CBL16E1MDRMDREXT0.6m IP1016E1Extensioncable 0.6m, MDR68
WA03870 IP10CBL16E1OEPROT5M IP1016E1scableopenend,5Mw/prot.
41
T1
T1"openend"terminationcables
WA03580 IP10CBL16T15M IP1016T1portscableopen5M CABLE,SCSI68LEFTANGLETOOE,25M,100OHM
IP1016T1cableopenend,
p ,
WA 0413 0
WA04130 IP10 CBL 16T1 OE 3M
IP10CBL16T1OE3M CABLE SCSI68 LEFT ANGLE TO OE 3M 100 OHM
CABLE,SCSI68LEFTANGLETOOE,3M,100OHM
3M
42
PAGE 581 21
9/26/2010
T1
T1RJ45maletermination cables/panels
WA04121 IP10CBL16T1MDRLARJ45XD3m IP1016T1cable MDR68RJ453M,LA,cross
WA04101 IP10CBL16T1MDRLARJ451.5m IP1016T1cable MDR68RJ451.5M,L.Ang.
WA04111 IP10CBL16T1MDRLARJ45XD1.5m IP1016T1cable MDR68RJ451.5M,LA,crs
T1Protectionpanels/cables
WA03980 IP10CBL16T1PROTY IP1016T1protectionYcable,MDR68
T1RJ45female (socket)termination cables

WA04330 IP10CBL4T1RJ45F0.3M IP104T1portsRJ45socket(female),0.3M
43
T1
T1MDR69 MDR69crosscables(forchainingapplications)
CABLE,SCSI68TOSCSI68CROSS,2M,100
WA04280 IP10CBL16T1MDRMDRXED2m IP1016T1portscrossedcable2m
OHM,30AWG
T1specialcables/panels(notforpricelist)
IP10CBL16T1MDRRJ45XED3m IP1016T1cable MDR68RJ453M,cross
IP1016T1CROSSCABLEMDR68RJ45
WA03730 IP10CBL16T1MDRRJ45XED1.5m IP1016T1cableMDR68RJ451.5M,cross
1.5M
IP1016T1CABLE,MDR68Pinto
WA03370 IP10CBL16T1MDRRJ451.5m IP1016T1cableMDR68RJ451.5M
RJ45,1.5M
44
PAGE 582 22
9/26/2010
OPTICAL
STM1SFPs/patches/splitters multimode(optical)
SFPMultimode850nm1.0625Gbit/sFibreChannel
ER 8000 0
ER80000 SFP GE SX*RoHS
SFPGESX*RoHS SFP optical interface 1000Base SX
SFPopticalinterface1000BaseSX 1.25GigabitEthernetTransceiver,withpackingRoHS
1 25 Gigabit Ethernet Transcei er ith packing RoHS
compliance
SFP1000BASET1.25GBdSmallFormPluggableLow
ER80030 SFPGEELC SFPelectricalinterface1000BaseT Voltage(3.3V)ElectricalTransceiveroverCategory5
Cablewithpackage
AO00580 SFPGEZX SFPopticalinterface1000BaseZX
AO00480 OPMMCBLLCLCDPLX0.5M DuplexOpticalCableLCLCMM0.5M CABLE,FO,DUALLCTOLC,0.5M,MM,D=2MM
AO00660 OPMMCBLLCLCDPLX3M DuplexOpticalCableLCLCMM3M CABLE,FO,DUALLCTOLC,3M,MM,D=2MM
AO00670 OPMMCBLLCLCDPLX6M DuplexOpticalCableLCLCMM6M CABLE,FO,DUALLCTOLC,6M,MM,D=2MM
CABLE,FO,1X2SPLITTERLCTO
AO00390 GBESPLMM2M MM/LCOpticalsplitter62.5/1252M
LC,1M,MM,W.COUPLER50/50850NM,D=2MM
AO00590 GBESPLMM1M MM/LCOpticalsplitter62.5/1251M
LC,0.5M,MM,W.COUPLER50/50850NM,D=2MM
AO00600 GBESPLMM0.6M MM/LCOpticalsplitter62.5/1250.6M
LC,0.3M,MM,W.COUPLER50/50850NM,D=2MM
COUPLER,2X2,850NM,lCTO
AO00890 OPMMHSPLLCLC0.5M/0.5M Opt.HspltMM850nm,LC/LC,0.5M/0.5M
lC,1M,MM,50/50,D=2MM
COUPLER,2X2,850NM,lCTO
AO00900 OPMMHSPLLCLC1M/1M Opt.HspltMM850nm,LC/LC,1M/1M
lC,2M,MM,50/50,D=2MM
45
ETHERNET
Ethernetcables/splitters(copper)
WA03340 IP10CBLFE0.5M IP10FEProtcablestraight0.5m CABLE,RJ45TORJ45,0.5M,CAT5E
WA02421 XWSCE1/T1 E1/T1WSCxedcable CABLE,RJ45TORJ45CROSS,0.5M,CAT5E
CABLE,RJ45TORJ45DUALCROSS,2M,CAT
WA02350 X2FECON DualchannelEthernetxedcable
5E,100OHM
WA02440 15PPROTCBL E1/T1/Ethernetprotectioncable CABLE,RJ45TO2XRJ45F,1.34M,CAT5E
46
PAGE 583 23
9/26/2010
ETHERNET
EthernetRJ45 RJ45cables
WA04170 IP10CBLETHRJ450.6m IP10ETHRJ45cable0.6m,str.
WA04180 IP10CBLETHRJ451m IP10ETHRJ45cable1m,str.
WA04190 IP10CBLETHRJ452m IP10ETHRJ45cable2m,str.
WA04140 IP10CBLETHRJ45XED0.6m IP10ETHRJ45cable0.6m,cross
WA04150 IP10CBLETHRJ45XED1m IP10ETHRJ45cable1m,cross
WA04160 IP10CBLETHRJ45XED2m IP10ETHRJ45cable2m,cross
47
AUXILARY USER CHANNEL & ALARMS
ExternalAlarms
CABLE,D9FTOOE,2.5M,EXT
WA03740 IP10EXTALARMSCBL2.5m IP10Ext.Alarmsopencable2.5m
ALARMS
CABLE,D9Fx2TO
WA03690 IP10EXTALARMSCBL2.5mPROT Ext.Alarmscable2.5m withprotection
OE,2.5M,EXTALARMS
Userchannelandothers
WA02880 15RUSERCHANASYNCCBL2.5M 1500RAsync UserChannelsopencable2.5

WA02890 15RUSERCHANSYNCCBL2.5M 1500RSync UserChannels opencable 2.5m
WA02720 PWRCBL2.2M 48VDC2.2mPWRCABLERoHS
IP10IDU19INCHDEEP
MB09650 IDUMountears1RUW19inD50mm IDUmount.ears,1RU,W:19in,D:50mm
MOUNTEDEAR
WB00050 IP10CBLPWR48VExtendedProt IP10extend.prot.48Vpowercable
48
PAGE 584 24
9/26/2010
Thank You
Should you require further information, please contact us at
PAGE 585 25

Ceragon IP10G Advanced Course Handbook V4 2 PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Ceragon IP10G Advanced Course Handbook V4 2 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

IP-10G Advanced

Visit our Customer Training Portal at Training.Ceragon.Com

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

CarrierEthernet/ TDM Trunk

10 Proprietary and Confidential

Reduced operational costs

Ceragon's Architecture Management Concept

Ceragon Complete Offering

12 Proprietary and Confidential

13 Proprietary and Confidential

Mobile Backhaul Case Studies

Installing 700 links a month, from planning to commissioning

15 Proprietary and Confidential

Converged, 3G and Rural Broadband IP backhaul

17 Proprietary and Confidential

For network simplicity

5 layers of protection to sustain high capacity mobile

18 Proprietary and Confidential

Long haul Case Studies

SDH & IP Trunk Backbone for Mobile and ISP

n x E1 2G ECI nx STM-1 XDM-1000

migration from all TDM to all

20 Proprietary and Confidential

Full IP Backbone for an ISP (Uruguay)

Establishing a GbE link between sites

Solutions Service Aware Radio Link

nxFE / GbE Service Aware Radio Link

31.94 km 32.81 km CESP 36

Modularity and upgradeability Quilmes

High capacity all, indoor, all packet 058 15 04.00 W

Cisco partnership (CTDP) VPLA

Radio level, System level, e-t-e

21 Proprietary and Confidential

All Indoor & Split Configurations LTE Ready

Migration from 2G/3G UMTS to

22 Proprietary and Confidential

An army network backbone (Philippines)

Build an army military grade long microwave 10'

Cost-effective voice, data, and video CALBAYOG

conferencing services to satisfy command 40'

and control requirements