Ceragon - IP-10R1 ADV - Book - v1.3 PDF

©
CERAGON FIBEAIR
COURSE HANDBOOK
Installation, Commissioning
& System Configuration
2010
Visit our Customer Training Portal at Training.Ceragon.Com
or contact us at training@ceragon.com
Trainee Name:
24/7 access to eLearning provides a first eLearning
constantly increasing tier of support to users of is proven to be less
on-line DB of the new technologies, intimidating than
latest information! resulting in an estimated Instructor led training.
30% reduction in support Concerns about making
costs related to mistakes in front of peers
implementation of new and management are
applications & business eliminated.
eLearning is a great processes.
complementary solution to
your classroom sessions as
some modules are only
available on-line
Ceragon Training Center
Ceragon eLearning
solutions can shorten the
Ceragon eLearning users enjoy amount of time it takes to
frequent & updated modules as get learners up to speed on
Ceragon Training Center is designed new features and products are
to help you get a comprehensive new products and
released without needing to processes.
understanding with Ceragon's update users’ account properties.
technology, products and network Users who need to "brush
solutions. up" on a process can
access a module instantly,
While individuals focus on particular practice, test themselves
modules, Managers on the other and resume their work.
hand can sign up their staff members
to a Learning Program with
compulsory items such as quizzes &
procedures.
• Want to find out more?
• Need an Account
Ceragon Training Comparison Table?
Knowledgebase is available to • Need a proposal?
your employees without • Case studies?
sacrificing additional room
space or time-consuming Please contact us at
lectures. training@ceragon.com

Ceragon Training Agenda
Product: IP-10
Course: IP10AO&M Extended Operation and Maintenance
Duration: 3 days
DAY ONE
Introduction to Radio Microwave:
 Parameters affecting propagation (Fresnel Zone, Duct, Multipath)

 Digital Modulation Basics
 Radio Link Components
 MSE
Introduction to 802.1:
 The need for smaller broadcast domains

 Standard Ethernet Frame
 VLAN Tagging
 P-Bits & VID
 Q-in-Q
Introduction to IP-10 IDU
IP-10 Front Panel Description
Introduction to RFU-C / or other ODU type
Installation:
 Physical Installation of IDU + ODU

 IP address using CLI
Commissioning:
 System name & Contact Details (Unit Info)

 Reading Versions
 External Alarms
 Setting IP Address and Management (In Band / OOB)
 Trap Destination
 Updating the license
Radio Link Commissioning:
 Frequencies
 TSL & RSL & MSE
 ATPC
 Management (In band / OOB)
 Link ID
 Local & Remote frequency change
1 Ceragon Training Agenda v2.0
Ceragon Training Handbook - Page 1

Ceragon Training Agenda
DAY TWO
Adaptive Coding & Modulation (ACM)
Switch Mode Configuration:
 Single Pipe
 Managed Mode
 Metro Mode
Interface Configuration:
 ETH Ports (Trunk VS. Access)

 E1 Ports
Troubleshooting Tools & Maintenance:
 Using the Current Alarms

 Using the Event Log
 Using RMON Registers and Statistics
 Performing Loopbacks
 Saving Unit Information Files
 Configuration File Upload / Download
 Software File Download
DAY THREE
1+1 Protection: Configuration Review
1+1 Protection: Practical Exercise
QoS: Configuration Review
QoS: Practical Exercises
Introduction to CFM (802.1ag)
CFM: Practical Exercises
Q-in-Q: Configuration Review
Q-in-Q: Practical Exercise
2 Ceragon Training Agenda v2.0

3/8/2010
Ceragon in a Nutshell
Products
Agenda
“Think Backhaul Networks”
1. 1500R IDU
2. IP-MAX^2 IDU
3. IP-10 IDU
4. IP-10G IDU
5. Nodal Solutions
6. 3200T IDU
7. Outdoor units
8. Outdoor Enclosures
2 Proprietary and Confidential

1
3/8/2010
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)
IDU 1500R – Point to Point SDH Radio Link
STM Ring STM Ring

2
3/8/2010
IDU 1500R – SDH RING
ADM/MSPP
N x STM-1/OC-3
XC
XC
Ceragon
FibeAir 1500R
Aggregation
Site PSN
IP-MAX^2 IDU: GbE Backhaul
ETH
IP/ETH
Provider
network

3
3/8/2010
IP-10 IDU: Enhanced Cellular Backhaul
Cellular
traffic
(TDM)
IP/ETH
Provider
network
N x ETH
IP-10G IDU: A Nodal Solution
Cellular traffic
(TDM)
STM
Rings

4
3/8/2010
3200T All Indoor: High Capacity Trunk
SDH
3200T Split Mount: High Capacity Trunk
SDH

5
3/8/2010
RFUs
FibeAir RFU-HP FibeAir RFU-HS FibeAir RFU-P FibeAir RFU-C
High power Standard power

(e.g. Smaller antennas – reduced cost)
Proprietary and Confidential
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.

6
3/8/2010
Hybrid aggregation network for migration

Native2 at the access, IP/MPLS & SDH/SONET at the aggregation
Native2 (MW links) IP/MPLS (Hybrid Fiber/MW)
SDH/SONET (Hybrid Fiber/MW)

Native Ethernet
Ethernet over IP/MPLS
Native E1/T1
E1/T1 over SDH/SONET
STM1/
OC3
STM1/ NG-SDH
OC3 MSPP BSC/MSC
FE/GE NG-SDH
MSPP Core
n x T1/E1
Site
FibeAir GE
Tail site IP-10 FibeAir
IP-10
GE
Hub
Site RNC
MPLS
MPLS Router
Router
Native2 - Is a technology for carrying both TDM and Ethernet traffic Natively
over the same microwave links with dynamic bandwidth allocation.
Aggregating WiMAX / LTE Ready
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
Access Metro / Aggregation Core IP Backbone

• WiMAXPoint to Multipoint • Ceragon’s Point to Point backhaul • Ethernet (GE) is sent over to an
solution for Ethernet traffic supports Native Ethernet with traffic IP/MPLS Layer
aggregation and statistical QoS awareness
multiplexing for a mix of Business • TDM (STM-1/OC-3) is sent over to
and mobile offload Ceragon Point • Ethernet traffic is “tunneled” through an SDH/SONET layer
to Point for TDM aggregation E-LAN/ E-Line EVCs
• TDM traffic (E1/T1) are being • Ceragon High-capacity "MPLS-
aggregated using Ceragon integrated aware" Ethernet microwave radio is
TDM cross connect used where fiber connections not
available.

7
3/8/2010
Ceragon’s Advantages
High Spectral-Efficiency
High System-Gain
Multi-Service Concentration capabilities
High Level of Redundancy
Adaptive Modulation
Pay-as-you-grow concept
High Spectral-Efficiency
(i.e. 256QAM modulation)
• Providing more capacity at any given frequency resources
• e.g. 18xE1 or 50Mbps @ 7MHz channel-bandwidth
• Better utilizing valuable frequency resources

• e.g. using high spectral efficiency we provide 155-200Mbps @ 28MHz,
using a Single wireless link!
• Average microwave will require Two links causing higher CAPEX and
consume additional valuable frequency
Get the same capacity

with ONE link
instead of TWO!

8
3/8/2010
Higher Spectral-Efficiency
What’s in it for The Operator?
Typical IP10
Microwave Radio Microwave Radio
TWO radio links ONE radio link

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

and free-up valuable frequency resources
Higher Spectral-Efficiency is not enough…
Radio Type Ant. Diameter Length Modulation Capacity
Typical System Gain 1.80 m 30 Km 16QAM 32 x E1s
Typical System Gain 1.80 m 21 Km 128QAM STM-1/OC-3
Typical System Gain 3.00 m 30 Km 128QAM STM-1/OC-3
High
HighSystem
SystemGain
Gain 1.80 m 30 km 128QAM STM-1/OC-3
Spectral Efficiency
should always be coupled with
System Gain

9
3/8/2010
Ceragon’s Management Overview
IP-10 FibeAir
We adjust to customers’
requirements

10
3/8/2010
Thank You!
training@ceragon.com

11
Introduction to 802.1 P/Q
Module Version v2.6

Objectives
• Understand the need for smaller broadcast domains
• Understand what is VLAN
• Understand the difference between tagged and untagged frame
• Understand VLAN applications
Advanced Operation & Maintenance Course

1
Associated IEEE Standards
• IEEE 802.3 : Ethernet (Max. frame size = 1518 bytes)
• IEEE 802.3ac : Ethernet (Max. frame size = 1522 bytes)
• IEEE 802.1 d : MAC Bridge first introduced the concept of Filtering

Services in a bridged local network
• IEEE 802.1 q : VLAN Tagging
• IEEE 802.1 p : Priority Tagging / Mapping
• IEEE 802.1ag : OAM (CFM)
Agenda
Agenda
• What is VLAN?
• Advantages for using VLAN

• Regular Ethernet frame
• Tagged frame structure

• Types of VLAN
• Types of connections
• 802.1P implementations

2 of 19

2
What is VLAN?
A Layer 2 Protocol which enables enhanced

traffic maneuvers :
• Prioritization
• Filtering
• Provisioning
• Mapping (e.g. - ATM to/from ETH)

4 of 19
What is VLAN?
Regular ETH networks forward broadcast frames to all endpoints

5 of 19

3
What is VLAN?
VLAN networks forward broadcast frames only to pre-defined ports

(Profile Membership)
VLAN 1
Switch ports
VLAN 547

6 of 19
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 between VLANs is restricted).

3 of 19

4
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

7 of 19
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.)

8 of 19

5
Tagged Ethernet Frame
• Additional information is inserted

• Frame size increases to 1522 Bytes
4 Bytes
Preamble + SFD DA SA Length / Type Length / Type DATA + PAD FCS
TPID = 0x8100 TCI

16 Bit
TPID = Tag protocol ID

TCI = Tag Control Information
P-TAG CFI VLAN ID CFI = 1 bit canonical Format Indicator
3 Bit 1 Bit 12 Bit

4 of 19
9 42
Tagging a Frame
VLAN ID uses 12 bits, therefore the number of maximum VLANs is

4094:
• 2^12 = 4096
• VID 0 = reserved
• VID 4096 = reserved (every vendor may use some VIDs for 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)

6
TPID / ETHER-Type / Protocol Type…
TPID in tagged frames in always set to Protocol type Value
0x8100 Tagged Frame 0x8100
ARP 0x0806
Q-in-Q (CISCO) 0x8100
Q-in-Q (other vendors) 0x88A8
Q-in-Q (other vendors) 0x9100
Q-in-Q (other vendors) 0x9200
RARP 0x8035
It is important that you understand IP 0x0800
the meaning and usage of this IPv6 0x86DD
parameter
PPPoE 0x8863/0x8864
MPLS 0x8847/0x8848
Later when we discuss QoS, we IS-IS 0x8000
shall demonstrate how & why the LACP 0x8809

system audits this parameter 802.1x 0x888E
VLAN types
Membership by Port
VID1
Port VID
1 1 VID1
2 1
3 44
4 200 VID 44
PRO – easy configured

CON – no user mobility VID200

10 of 19

7
VLAN types
Membership by MAC
MAC VID
00:33:ef:38:01:23 1
00:01:de:22:42:ae 1
00:20:8f:40:15:ef 44
00:20:32:35:ea:11 200
PRO – user mobility, no reconfiguration when PC moves
CON – needs to be assigned initially, not an easy task with

thousands of endpoints

11 of 19
VLAN types
Membership by Subnet Address (a.k.a. Layer 3 VLAN)
Subnet Address VID

10.0.0.0 / 24 1
20.0.0.0 / 30 1
11.0.0.0 / 24 44
192.168.1.0 / 24 200
Membership is based on the Layer 3 header

No process of IP address is done
Main disadvantage – longer overall throughput

12 of 19

8
VLAN types
Membership by Protocol Type
Protocol Type VID

IP 1
IPX 44
The VID is derived from the protocol type field

found in the Layer 2 header

13 of 19
Port Types
Access Port – a port which is not aware of VLANs

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

A
Device unaware of VLANs Switch tags the ingress

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

14 of 19

9
Port Types
Trunk Port – a port which is aware of VLANs

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

A T
Device unaware of VLANs Switch tags the ingress frames with VID according to
transmits untagged specific Tagging mechanism
(regular) ETH frames
Switch un-tags frames with VID received from network
and delivers untagged frames to Access ports

14 of 19
Port Types
Trunk Port can carry tagged frames with different VIDs.

This requires Port Membership configuration.
VLAN aware Switch

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

port membership list, hence, traffic is
discarded

14 of 19

10
Port Types
Q-in-Q (A.K.A. Double Tagging…VLAN Encapsulation…)
+
VLAN
aware Switch
CN PN
Enhanced security – not exposing original VID
Improved flexibility of VID in the network

(Ingress VID was already assigned in the network)
21 Proprietary and Confidential 15 of 19
Introduction to QoS / CoS
22

11
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
Mapping ETH to MPLS and vice versa

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

• VLAN ID mapped to MPLS EXP bits
• VLAN P-Bit mapped to MPLS EXP bits
Hub
GE
Site
FE/GE RNC
GE
STM1/
n x T1/E1
FibeAir OC3
STM1/
Tail site IP-10 OC3
MPLS
IP-10 MPLS Router
Router
Core
Site BSC/MSC
24 Proprietary and Confidential 16 of 19

12
VLAN P-Bit Remap (Traffic Classes)
802.1P utilizes Traffic Classes:
A switch port allocates ingress frames to

queues (buffers) according to their P-Tag
value
P-Bits 6-7
The more queues – the more prioritizing
levels (classes)
Downside – more time, more memory… Q4 High

P-Bits 4-5
Normally 4 queues (TCs) are sufficient
Q3
In this example the port groups a few Bits

into a single queue Q2
P-Bits 0-3
8 priority levels become 3 classes Q1 Low
VLAN P-Bit Remap (Traffic Classes)
IEEE Recommendation
Ingress Number of Available Traffic Classes
The following table shows P-Tags
IEEE definition of traffic 1 2 3 4 5 6 7 8
classes 0 (default) 0 0 0 0 0 1 1 1
It shows the ingress options 1 0 0 0 0 0 0 0 0

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

13
Acronyms
• ETH – Ethernet
• NIC – Network Internet Card
• VID – Vlan 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
Thank You !

14
Mean Square Error
Agenda
• MSE – Definition
• Expected value
• The Error Histogram
• Giving bigger differences more weight than smaller differences
• Calculating MSE
• MSE in digital modulation
• Commissioning with MSE
• MSE and ACM
1 Ceragon Training Handbook - Page 28

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
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 10cm wide
We took a few of parts and measured them to see how many can
fit in….

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

The difference from Expected value…
Quantity
Error = 0 cm
Error = + 2 cm
Error = - 3 cm
Error = + 6 cm
Error = - 4 cm
width
To evaluate the inaccuracy (how sever the situation is) we measure how
much the errors differ from expected value

3
Giving bigger differences more weight than
smaller differences
Quantity
Error = 0 cm
+ 2 cm = 4
-3 cm = 9
- 4 cm = 16 + 6 cm = 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
Calculating MSE
Quantity
Error = 0 cm
+ 2 cm = 4
-3 cm = 9
- 4 cm = 16 + 6 cm = 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

4
Calculating MSE
Quantity Error = 0 cm
width
10cm
If all parts were perfectly produced than each error would be 0
This would result in MSE = 0
Conclusion: systems perform best when MSE is minimum
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)

5
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
bigger the errors are – the
harder it becomes for the
11 10 receiver to detect & recover the
transmitted signal
Q
01 00 MSE would be the average
e1 errors of e1 + e2 + e3 + e4….
e2
I
When MSE is very small the
e4 actual signal is very close to
e3
the expected signal
11 10

6
Q
01 00 When MSE is too big, the
e1 actual signal (amplitude &
e2 phase) is too far from the
expected signal
I
e4
e3
11 10
Commissioning with MSE in EMS
When you commission your

radio 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

7
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 assign the extra bits for
correction instead
For example –
256QAM has great capacity but
poor immune to noise
64QAM has less capacity but much

better immune for noise
ACM – Adaptive Code Modulation
Thank You !
16

8
3/8/2010
ACM - Adaptive Code Modulation
FibeAir IP-10’s Key Feature
• IP-10 utilizes a unique Adaptive Coding & Modulation (ACM) –
Modulation range: QPSK - 256QAM
• 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

1
3/8/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
FEC FEC
Non-real time
services
When we engineer our services, we may assign certain services to highest

priority
When ACM is enabled and link degrades, highest priority services are
maintained

2
3/8/2010
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
• E1/T1 traffic has higher priority over Ethernet traffic
• Each E1/T1 service is assigned a priority - enables differentiated E1/T1 dropping
during severe link degradation
• Integrated QoS with intelligent congestion management - ensures high priority
Ethernet traffic is not affected during link fading
Throughput per radio carrier:

10 to 50 Mbps @ 7MHz Channel
25 to 100 Mbps @ 14MHz Channel MSE is analyzed to trigger
45 to 220 Mbps @ 28 MHz Channel ACM modulation changes
90 to 500 Mbps @ 56 MHz Channel
Zero downtime - A must for mission-critical services
IP-10 radio capacity - ETSI

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


3
3/8/2010
IP-10 radio capacity - FCC

10MHz 20MHz
Modulation # of Ethernet Modulation # of Ethernet
ACM T1s Capacity ACM T1s Capacity
Point (Mbps) Point (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
Modulation # of Ethernet Modulation # of Ethernet Modulation # of Ethernet
ACM T1s Capacity ACM T1s Capacity ACM T1s Capacity
Point (Mbps) Point (Mbps) Point (Mbps)
1 QPSK 22 39 - 55 1 QPSK 31 56 - 80 1 QPSK 37 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

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%

4
3/8/2010
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
Adaptive Coding & Modulation (ACM)

It’s all about handling data...
• Current Microwave systems are designed with

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

Microwave systems shall treat services in different ways

5
3/8/2010
Fewer Hops
1.28km fix rate

200Mbps at 99.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
11
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

6
3/8/2010
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
13
Thank You !
14

7
3/9/2010
Introduction to IP-10
Agenda
• IP-10 Carrier Ethernet features overview

• IP-10 integrated QoS support – overview
• IP-10 based Wireless Carrier Ethernet rings
• Ethernet Service OAM (802.1ag)
• IP-10 management support overview

1
3/9/2010
IP-10 Integrated Carrier Ethernet switch
2 main modes for Ethernet switching:

• Metro switch – Carrier Ethernet switching is enabled
• 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 switch mode Smart pipe mode
Extensive Carrier Ethernet feature-set

eliminates the need for external switches
What is Carrier Ethernet?
The MEF has defined Carrier Ethernet as:

A ubiquitous, standardized, carrier-class
Service and Network defined by five
attributes that distinguish it from familiar
LAN based Ethernet

2
3/9/2010
Carrier Ethernet – Standard service types
E-Line Service type

• E-Line service used to create:
• Ethernet Private Lines
Point-to-Point EVC
• Virtual Private Lines UNI UNI
• Ethernet Internet Access CE

CE
Carrier Ethernet
Network
• E-LAN service used to create:

E-LAN Service type
• Multipoint L2 VPNs
• Transparent LAN Service CE
• Foundation for IPTV and UNI

Multicast networks etc.
Carrier Ethernet
Network
UNI: User Network Interface, CE: Customer Equipment
MEF certified Carrier Ethernet products UNI

Multipoint-to-Multipoint EVC CE
IP-10 – Carrier Ethernet platform (MEF Certified)
• The MEF Certification Program

• An important part of the MEF’s mission to accelerate the deployment of
Carrier Ethernet in the Access, MAN & WAN
• Certification for Carrier Ethernet equipment supplied to service providers
• Current certification program comprises
• MEF-9 - Service certification
• MEF-14 - Traffic management and service performance
• Approved Certification Lab - Approved independent lab: Iometrix Inc.
IP-10 is fully MEF-9 & MEF-14 certified

for all Carrier Ethernet service types
(E-Line and E-LAN)

3
3/9/2010
IP-10 - Carrier Ethernet functionality
Standardized Quality of Service

Scalability Reliability
Services Service Management
MEF-9 & MEF-14 Up to 500Mbps per Advanced CoS Highly reliable & Extensive multi-
certified for all radio carrier classification integrated design layer management
service types (EPL, capabilities
Integrated Advanced traffic Fully redundant 1+1
EVPL and E-LAN) non-blocking switch policing/rate-limiting HSB & nodal 802.1ag Ethernet
with 4K VLANs configurations service OA&M
CoS based packet
802.1ad provider queuing/buffering Hitless ACM Advanced Ethernet
bridges (QinQ) Flexible scheduling (QPSK – 256QAM) statistics
for enhanced radio
Scalable nodal schemes
link availability
solution Traffic shaping
Wireless Ethernet
Scalable networks
Ring (RSTP based)
(1000’s of NEs)
802.3ad link
aggregation
Fast link state
propagation
<50msec restoration
time (typical)
Carrier Ethernet World Congress

Interoperability Showcase 2008

4
3/9/2010
At this event Ceragon

particularly focused on the
following Interoperability
tests:
• Wireless Ethernet OA&M (Operational
Administration & Maintenance)
Interoperability
• ACM (Adaptive coding & modulation) in a

wireless Ethernet radio link
• Provision EVCs (Ethernet Virtual Circuit)

and several types of Ethernet service while
providing UNI (User Network Interface)
• Pseudo-wire service and clock recovery
• Nodal solution for aggregating and

statistical multiplexing at hub/Aggregation
site
• Embedded switching capabilities which

eliminate the need for an external switch

5
3/9/2010
IP-10 integrated QoS support - overview
• 4 CoS/priority queues per switch port Priority Queues
• Advanced CoS/priority classification based W1 - Highest priority

on L2/L3 header fields:
• Source Port Classify Scheduling
• VLAN 802.1p Arrivals W2 departures
• VLAN ID
• IPv4 DSCP/TOS, IPv6 TC W3
• Highest priority to BPDUs

• Advanced ingress traffic rate-limiting
per CoS/priority W4 – lowest priority
• Flexible scheduling scheme per port
• Strict priority (SP)
• Weighted Round Robin (WRR)
• Hybrid – any combination of SP & WRR
• Shaping per port Support differentiated Ethernet services
with SLA assurance
IP-10 based Wireless Carrier Ethernet rings
FibeAir IP-10
Tail site #1 Packet or TDM

FibeAir
IP-10
Ring site based fiber
#1 aggregation
network
or leased lines
FibeAir
IP-10
FibeAir IP-10
Wireless
Tail site #2
Carrier Ethernet Fiber site
Ring RNC
FibeAir
IP-10
Ring site
#2
FibeAir
IP-10
Ring site
#3
FibeAir IP-10
Tail site #3

6
3/9/2010
IP-10 based Wireless Carrier Ethernet ring

With redundant site connection to fiber aggregation network (“dual-homing”)
FibeAir IP-10
Tail site #1
FibeAir
IP-10
Ring site
#1
FibeAir
IP-10
FibeAir IP-10 Packet or TDM
Wireless Fiber site #1 based fiber
Tail site #2
Carrier Ethernet aggregation
Ring Fiber site network
or leased lines
FibeAir
IP-10
Ring site
FibeAir
#2
IP-10 RNC
FibeAir
Fiber site #2
IP-10
Ring site
#3
FibeAir IP-10
Tail site #3
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

N x GE/FE

7
3/9/2010
Wireless Carrier Ethernet Ring

Example aggregation site
FibeAir
IP-10
Ring site Wireless

Carrier Ethernet
Ring
Wireless
Carrier Ethernet
Ring
N x GE/FE
Integrated Ethernet
Switching
Ethernet services – End-to-end multi-layer OA&M
1+0 1+1
Packet or TDM
based fiber
aggregation
FibeAir IP-10 FibeAir IP-10 network
FibeAir IP-10 or leased lines
Tail site Agg. site Fiber site
Carrier Ethernet service
Native EVC (802.1ag CFM)
GE/FE Radio link Radio link GE/FE

Interface Interface
Full set of OA&M functionality is provided at multiple layers:

• Alarms and events
• Maintenance signals (LOS, AIS, RDI, etc.)
• Performance monitoring
Support service provisioning, OA&M and SLA assurance
• Maintenance commands (Loop-backs, APS commands, etc.)

8
3/9/2010
IEEE 802.1ag CFM (Connectivity Fault Management)
IP-10 Management Overview
• Integrated web based element manager

• HTTP based Northbound
• Full set of EMS functionality - configuration, NMS
CeraMap
performance monitoring, remote diagnostics,
alarm reports, etc. CeraMap
• SNMP interface to Ceragon’s PolyView NMS NMS Platform

PolyView
• Extensive CLI interface via local terminal or Telnet
IP-10 Web IP-10 Web

EMS EMS
SNMP
HTTP HTTP
CLI
Craft
HTTP
18

9
3/9/2010
Extensive radio capacity/utilization statistics
• Statistics are collected for 15-minutes, and 24-hours intervals

• Statistics history is maintained
• Capacity/ACM statistics
• Maximum modulation in interval
• Minimum modulation in interval
• # of seconds in interval in which active modulation was below a user-
configured threshold
• Utilization statistics
• Maximal radio link utilization in interval
• Average radio link utilization in interval
• # of seconds in interval in which radio link utilization was above
a user-configured threshold
Ethernet in-band management
• IP-10 can optionally be managed through the traffic carrying radio and
Ethernet interfaces
• The in-band management support is based on a dedicated management
VLAN
• The management VLAN ID is user configurable
Eliminates the need for dedicated management interfaces and network

10
3/9/2010
Thank You !

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

1500R/1500P 3200T

1
3/9/2010
IDU – RFU Compatibility
RFU-C
1500R IP-10
RFU-P, RFU-SP
RFU-HP
RFU-SP
IP-MAX/IP-MAX2 640P 1500P
IDU – IDU Compatibility Across Link
1500R 1500R
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

2
3/9/2010
RFU-C direct mount configurations
1+0 direct
RFU-C direct mount configurations
1+1 direct

3
3/9/2010
RFU-C remote mount configurations
1+0 remote
RFU-C remote mount configurations
1+1 remote

4
3/9/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
RFU-C to NSN antenna

5
3/9/2010
RFU-C to Ericsson antenna (R1A 23GHz)
Thank You !

6
FibeAir ® IP-10
Installation
Agenda
• Unpacking
• Required Tools
• Installing the IDU in a rack
• Grounding
• Lightning Protection
• Connecting to a Power Supply
• IDU Front Panel
• Connecting RFU coax cable
• Interface Specification
• Protection Patch Panel
• Logging in, assigning IP address

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
• 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 (for mounting the IDU to the rack and grounding
screw)
• Flathead small screwdriver (for PSU connector and to unlock the
IDC/IDMs from the chassis)
• Sharp cutting knife (for wire stripping)
• Crimping tool for ground cable lug crimping (optional: if alternative
grounding cable is used)

Installing the IDU in a rack
The FibeAir IP-10 IDU is installed

in a standard ETSI 19" rack:
secure the IDU with four screws

(supplied)
IDU dimensions:
D: 187.80 mm
W: 435 mm
H: 42.60 mm
Grounding
Connect the grounding

cable between the IDU and
the rack using a single
screw with two washers
Only copper wire should be

used (at least 6 AWG).
FibeAir provides a ground

for each IDU, via a one-hole
mounted lug onto a single-
point stud (installed using a UL-
listed ring tongue terminal, and
two star washers for anti-
Rotation).

Lightning Protection
Lightning protection kit is installed upon request between IDU and ODU
It prevents transients of a greater magnitude than the following:
Open Circuit: 1.2-50us 600V

Short Circuit: 8-20us 300A
Connecting to a Power Supply
When selecting a power source, the following must be considered:
• DC power can be from -40.5 VDC to -72 VDC.

• Recommended: Availability of a UPS and power generator
• The power supply must have grounding points on the AC and DC sides
• The user power supply GND must be connected to the positive pole in the
IDU power supply.

Connecting to a Power Supply
-48 vdc 0
(-) (+)
PSU
(GND)
IP-10 Front Panel
16 x E1 / T1 1 GbE RFU N-Type

CLI (DB9)
(Optional) SFP Interface
Baud: 115200
Data bits: 8
Parity: None
Stop bits: 1
Flow Control: None

IP-10 Front Panel
FE Copper FE Copper
External 10/100 RJ45 10/100 RJ45
Alarms Or Or
(DB9) Protection Wayside
Channel Channel
EOW 1 GbE Copper Fans

(Engineering User Channel 10/100/1000 FE Copper
Order Wire) V11,RS232 RJ45 10/100 RJ45
(RJ45) Or
Up to 19.2Kbps Out-Of-Band
MNG
The FE interfaces can be configured as either FE, protection, wayside, or MNG

Connecting RFU coax cable
The Coax Cable that connects between the IDU and the RFU should
be terminated with N-type male connectors
Important! 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.

Interface Specification
Gigabit Ethernet (Optical)
1000Base-SX (Multi Mode)
Wavelength: 850 nm
Receptacle: MSA compliant SFP
Connector: LC
Max Segment Length: 220 m (1351 ft), 500 m (1650 ft)
Cable Type: For Max. Segment = 220 m: 62.5 µm MMF
For Max. Segment = 500 m: 50 µm MMF
Gigabit Ethernet (Optical)
1000Base-LX (Single Mode)
Wavelength: 1350 nm
Connector: LC
Max Segment Length: 550 m (1805 ft), 5000 m (16404 ft)
Cable Type: For Max. Segment = 550 m: 62.5 µm MMF
For Max. Segment = 5000 m: 10 µm SMF

Gigabit Ethernet / Fast Ethernet (Electrical)
1000BaseT (Twisted Pair Cable)

Connector: RJ-45
Max Segment Length: Up to 100 m (328 ft) per IEEE802.3
Cable Type: Compatible with shielded and unshielded twisted
pair category 5 cables
Optional 16xE1/T1
Connector: MDR 69 pin, twisted pair

Interface Type: E1/T1
Number of ports: 16 per unit (optional)
Timing mode: Retimed
Framing: Unframed (full transparency)
Coding E1: HDB3
Coding T1: AMI/B8ZS
Range: 5m
Line Impedance: 120 Ω/100 Ω balanced,75 Ω unbalanced (OPT)
Compatible Standards: ITU-T G.703, G.736, G.775, G.823, G.824,
G.828, ITU-T I.432, ETSI ETS 300 147, ETS
300 417, ANSI T1.105, T1.102-1993, T1.231,
Bellcore GR-253-core, TR-NWT-000499

ETH Interfaces (Wayside, MNG, Protection)
Connector: Shielded RJ-45

Used with: UTP Cat 5
Protocols supported: Ethernet (10/100BaseT), half or full duplex
Timing mode: Retimed
Range: 100 m
Impedance: 100 Ω
Order Wire Channel Interface
Termination Type: Headset stereo plug, 2.5 mm

Frequency band (KHz): 0.3-3.4
Input impedance (ohms): ~2000
Output impedance (ohms): 32
(64Kbps)

User Channel Interface
The interface can be used for one of the following:
• Asynchronous RS-232
• Asynchronous V-11
• Up to 9.6 Kbps
CVSD - Continuously variable slope delta modulation
Antenna Alignment (1)
• Connect the headset to AGC monitor BNC/TNC connector on ODU

• Connect Digital Volt Meter (DVM) to the AGC BNC connector
• Align the antenna until voltage reading is achieved (1.2 to 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

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
Commissioning and Acceptance
• Link is up (LED is green)

• All LEDs are green (unless there is no input signal on the Line)
• RSL is up to +/- 4dB from un-faded (calculated) RSL at both ends of the
link
• Radio BER 10E-11 or better
• No Errors on BER test of line STM1 interfaces
• Proper function of management software
Please refer to the “FibeAir Commissioning and Acceptance Procedure” document

for detailed information

LEDS
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
LEDS
PROT: GREEN – protection is configured and connected

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

Logging in, assigning IP address
Verify that physical installation is successfully completed:
• IDU mounting in rack

• Power + GND
• IF Cable between IDU and ODU
Connect a PC to the Terminal connector and launch a serial application

(Hyper Terminal, PuTTY, TeraTerm etc…)
Log on using (admin/admin) for user name and password.

Now, you should be able to see the IP-10 CLI Prompt:
Note that the > sign

IP-10:/>
> indicates your
location in the CLI
tree
CLI basic commands:
IP-10:/ >? Type ? (question mark) to list helpful commands
IP-10:/ > exit Type exit to terminate the session
IP-10:/ > cd Type cd to navigate in the entity tree

IP-10:/ > cd .. Type cd .. to return to “root” of entity tree
Use the arrow keys to navigate through recent

commands
Use the TAB key to auto-complete a syntax

To read current MNG 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
Upon completion, the current IP will be 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>
Now, let us set a new IP for the MNG (we assume your new 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 continue to next step:

More CLI commands
Editing Users -
IP-10:/> cd management/mng-services/users
IP-10:/management/mng-services/users>
Adding JOHN as a user:
IP-10:/management/mng-services/users> add-user JOHN
More CLI commands
Adding JOHN as ADMIN user:
IP-10:/management/mng-services/users> add-user JOHN admin
Deleting JOHN (or other user) –
IP-10:/management/mng-services/users> delete-user JOHN

User groups
CLI access groups:
Viewer read-only access

Operator read-write access but cannot add/remove other users
Admin read-write access including add/remove other users
Tech (highest) read-write access including add/remove other users as
well as access to a bridge-specific CLI shell
More CLI commands
To go back to factory defaults -
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

Logging in to the EMS
Connect your working

station to the IDU with
ETH CAT.5 cable:
• Verify that your WS IP

is in the same subnet
• Make sure Link is up
• PING the IDU
• Launch a WEB
browser with a URL set
as the IDU’s IP
User name: admin

Password: admin
Logging in to the EMS
The homepage of the web-browser EMS should display the

main view of the IP-10:
Now, we are ready to start configuring the system

Thank You !
35

3/8/2010
FibeAir ® IP-10
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

1
3/8/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
Faults - CAS
The CAS window shows collapsed list of alarms
By expanding a line we can see additional information:
• Probable cause
• Corrective Actions

2
3/8/2010
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.
PM – Clearing previous data

To erase all IDU PM data, click the CLEAR button -

3
3/8/2010
PM – RMON
The system supports Ethernet statistics counters (RMON) display. The counters
are designed to support:
• RFC 2819 – RMON MIB.

• RFC 2665 – Ethernet-like MIB.
• RFC 2233 – MIB II.
• RFC 1493 – Bridge MIB.
PM – RMON – Special Registers
RMON register / Counter Description
Undersize frames received Frames shorter than 64 bytes
Oversize frames received Frames longer than 1632 bytes
Total frames received with a length of more than 1632 bytes,

Jabber frames received
but with an invalid FCS
Total frames received with a length of less than 64
Fragments frames received
bytes, and an invalid FCS
Rx error frames received Total frames received with Phy-error
Total frames received with CRC error, not countered in

FCS frames received
"Fragments", "Jabber" or "Rx error" counters
Counts good frames that cannot be forwarded due to
In Discard Frames
lack of buffer memory
Counts good frames that were filtered due to egress
In Filtered Frames
switch VLAN policy rules
Pause frames received Number of flow-control pause frames received


4
3/8/2010
PM – E1 / DS-1 (Radio PM)
This PM data relates to the TDM Line Interfaces.
PM – E1 / DS-1 (Radio PM)
Here we can analyze TDM PM through the radio link

5
3/8/2010
PM – Radio
Signal Level – RSL & TSL analysis
Allows setting RSL & TSL thresholds

EMS will notify when signal exceeds THSLD
>> Easier maintenance
Aggregated radio traffic analysis
MRMC – PM related to ACM:
• Scripts
• Bit rate
• Radio VCs
MSE analysis
PM – Radio – Signal Level - Example
- 40dBm = Nominal RSL for an operational Link

Level 1: 25 sec
Level 2: 15 sec
900 sec = 15min Interval

6
3/8/2010
PM – Radio – Signal Level - Example
Using graphical display of the THSLD analysis allows us easier

examination of the RSL & TSL state throughout certain period of time
RSL
-40
-50
-68
-99 T [sec]
10 5 10
PM – Radio - Aggregate
Aggregated radio traffic analysis

7
3/8/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, as link quality degrades or improves, the
information is updated accordingly.
PM – Radio - MSE
The information displayed in this page is derived from the license and script
assigned to the radio. When link quality degrades or improves, the MSE reading
is updated accordingly. Differences of 3dB trigger ACM modulation changing.
Threshold can be configured as well for easier maintenance.

8
3/8/2010
PM – Ethernet
ETH Traffic + Threshold settings:
Frame Error Rate –

Frame error rate (%) measured on radio-Ethernet
interface
Throughput – data bits measured on radio-

Ethernet interface
Capacity - overall Ethernet bits rate, data &

overhead, measured on radio-Ethernet interface
Utilization - (Actual Ethernet throughput, relative

to the potential Ethernet throughput of the radio,
excluding TDM channels).
Utilization (%) is displayed as one of five bins:

0-20%, 20-40%, 40-60%, 60-80%, 80-100%
PM – Ethernet
Ethernet throughput & Capacity PMs are measured by accumulating

the number of Ethernet octets every second, as they are counted by the
RMON counters

9
3/8/2010
Thank You !
19

10
3/8/2010
FibeAir ® IP-10
EMS General Configuration
Agenda
In this module we shall explain
the following features as they
appear on the EMS navigation
Menu

1
3/8/2010
Unit Parameters – Step # 1
Configure specific
information that may
assist you later
Such info will help you

locate your site easier
and faster
VDC reading

2
3/8/2010
Celsius (metric) or
Fahrenheit (Imperial)
By default the time &

date are derived from
the operating system
clock
User may set new

values
These settings are also

used for NTP
connection (later
explained)

3
3/8/2010
IDU Serial number is

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

configuring all
settings, click Apply.
Versions
This page shows the complete

package of IDU and ODU software
components

4
3/8/2010
Versions
Let’s explore this example:
• The IDU running SW is displayed in the aidu line and currently it is 3.0.92
• A new SW was downloaded sometime in the past (3.0.97)
• The IDU was not upgraded yet
Versions – RFU files
The IDU holds all the SW files for all the

components (IDU + ODU)
You can see here the different files per

ODU type

10

5
3/8/2010
External Alarms – Collapsed Input Alarm Config.
Dry Contact Alarms (DB-9):
5 Inputs
1 Output

11
External Alarms – Expended Input Alarm Config.

12

6
3/8/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
Quality of Service – We do not have specific alarms of QoS
Processing – Alarms related to SW: Configuration / Resets / corrupted files
Equipment – Alarms related to: HW / FAN / RFU mute / Power Supply / Inventory.
Environmental – Alarms of ‘extreme temperature’.
All Groups.
Test mode – manual switch.

13
Management – Network Properties
Here you can set the

Network Properties of
the IDU
This is the switch MAC address
If your link is up – you

should be able to see
the other end’s IP

14

7
3/8/2010
Management – Local Properties (Out of band)
The IDU has 3 ports for local management: Port 7, Port 6 and Port 5.
You may enable none or up to 3 ports:
Number of ports =3 Port 7, Port 6, Port 5

Number of ports =2 Port 7, Port 6
Number of ports =1 Port 7
Number of ports =0 NO LOCAL MANAGEMENT !!!
15
Management – In Band Properties
In Band Management requires unique VLAN ID
This helps separating MNG traffic from other services
In Band MNG packets are transferred via the radio link
When the link is down, management is down as well.

16

8
3/8/2010
Management – Port Properties
These parameters
allow you setting the
management capacity
and port properties

17
Trap Configuration (OSS / NMS / Northbound)
To manage the IDU with OSS /

NMS, you will need to configure
the IP address of the OSS Server
You may configure up to 4 Servers

(Trap Destinations)

18

9
3/8/2010
Licensing – Default License
“Demo” license can be

enabled on-site, it expires
after 60 days
(operational time)
Licenses are generated per

IDU S/N upon request
(capacity / ACM / switch
mode)
License upgrade requires

system reset.

19
Licensing – Demo License Enabled
Demo License allows you full
evaluation of the IDU
functionality, features and
capacities

20

10
3/8/2010
NTP Client Properties

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

“Time Offset” and “Daylight Saving Time” can be configured via WEB (“Unit
Information” page) or via CLI: /management/mng-services/time-service>

21
NTP Properties

22

11
3/8/2010
NTP Properties
When using NTP with external protection 1+1, both “Active” and “Standby”
units should be locked independently on the “NTP server”, and report
independently their “Sync” status.
Time & Date are not copied from the “Active” unit to the “Standby” unit
(CQ19584)
When using NTP in a shelf configuration, all units in the shelf (including
standby main units) are automatically synchronized to the active main unit’s
clock.

23
IP Table
Here you can manually set your neighbor’s network properties

24

12
3/8/2010
SNMP
• V1
• V3
• No security
• Authentication
• Authentication privacy
• SHA
• MD5
• No Authentication

25
Thank You !
26

13
3/8/2010
FibeAir ® IP-10
EMS Switch Configuration
Agenda
1. Switch mode review
2. Guidelines
3. Single Pipe Configuration
4. Managed Mode Configuration
5. Managed Mode Common Applications

1
3/8/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.
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

2
3/8/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-10 settings (radio, configuration, etc.)
• VLANs need to be created in the switch DB before assigned

to a port

3
3/8/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 2: FE (RJ45)

4
3/8/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 2 (RJ45)
When one is enabled

the other is disabled
No need to configure
VID membership

5
3/8/2010
Managed Mode
Configuration
Configuration – Managed Mode
Let’s use this diagram as an example -
Port #2 as Trunk (VID 200)
IDU-B
IDU-A
Radios as Trunk by
default Port #2 as Trunk
Port #3 as Trunk
(VID 200, VID 300)
(VID 300)

6
3/8/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

7
3/8/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

8
3/8/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

9
3/9/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

1
3/9/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 traffic is expected to be Untagged, e.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

2
3/9/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

3
3/9/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

4
3/9/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

5
3/9/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…)

6
3/9/2010
EMS Trunk Configuration
2
1
3
Thank You !
14

7
3/8/2010
FibeAir® IP-10
EMS Metro Switch Configuration
Agenda
1. Metro mode review
2. Common Applications: CN – PN – PN – CN
3. Common Applications: CN – PN – PN – PN
4. Switch Mode Configuration
5. CN Port Configuration
6. PN Port Configuration

1
3/8/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
Common Configurations: CN – PN – PN – CN
Provider-Facing Port (PN)
1st VID is hidden
Only S-VLAN is visible
Customer-Facing Port (CN)

Ingress frame (C-VLAN) is
encapsulated with 2nd VID (S-VLAN) Ingress frame (C-VLAN) is
encapsulated with 2nd VID (S-VLAN)
CN port removes S-VLAN on
opposite direction CN port removes S-VLAN on
opposite direction

2
3/8/2010
Common Configurations: CN – PN – PN – PN
1st VID is hidden
Only S-VLAN is visible

Ingress frame (C-VLAN) is
encapsulated with 2nd VID (S-VLAN) S-VLAN is not removed
CN port removes S-VLAN on

opposite direction
Switch Mode Configuration
1. Set mode to Metro (requires reset)
2. Add the S-VLAN ID (set & apply)

3
3/8/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 Port Learning
7. Apply & Refresh
8. See screen capture next slide
CN Port Configuration
1 3
4
5

4
3/8/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 & Refresh
7. Set the required S-Tag (Ether-Type)
8. See screen capture next slide
PN Port Configuration
1
3
1
6
5

5
3/8/2010
PN Port Configuration – Setting the S-Tag
• 0x88A8
• 0x8100
• 0x9100
7 • 0x9200
Thank You !
12

6
3/8/2010
FibeAir ® IP-10
EMS RSTP Configuration
Agenda
• Student Perquisites
• General Overview
• Limitations
• Site / Node Types
• Switchover Criteria
• In Band Management
• Out of band Management
• Configuration Example

1
3/8/2010
Student Perquisites
Viewers / end-user are required to have previous experience prior to

practicing this module:
1. End users should be familiar with Switch configuration
2. Be End users should be familiar with setting port membership
3. End users should be familiar with management mode configuration
4. End users should be familiar with configuring Automatic State Propagation
General Overview
Ceragon Networks ring solution enhances the RSTP algorithm for ring
topologies, accelerating the failure propagation relative to the regular
RSTP:
• Relations between Root and Designated bridges when ring is converged in the
first time is the same as defined in the standard RSTP. Ring-RSTP itself is
different than “classic” RSTP, as it exploits the topology of the ring, in order to
accelerate convergence.
• Ethernet-Fast-Ring-RSTP will use the standard RSTP BPDUs:

01-80-C2-00-00-00.
• The ring is revertible. When the ring is set up, it is converged according to
RSTP definitions. When a failure appears (e.g. LOF is raised), the ring is
converged. When the failure is removed (e.g. LOF is cleared) the ring reverts
back to its original state, still maintaining service disruption limitations.
• RSTP PDUs coming from “Edge” ports are discarded (and not processed or
broadcasted).

2
3/8/2010
Ring RSTP Limitations
1. Ring RSTP is a proprietary implementation of Ceragon Networks, and

cannot interwork with other Ring RSTP implementations of other 3rd party
vendors.
2. Ring RSTP can be activated only in “Managed Switch” application, and is

not available in any other switch application (“Single Pipe” or “Metro”).
3. Ring RSTP should NOT be running with protection 1+1.
Site / Node Types
The ring can be constructed by two types of nodes/sites:
1. Node/Site Type A:
• The site is connected to the ring with one Radio interface (e.g. East) and one
Line interface (e.g. West).
• The site contains only one IP-10 IDU. The Radio interface towards one
direction (e.g. East), and one of the Gigabit (Copper or Optical) interfaces,
towards the second direction (e.g. West).
• Other line interfaces are in “edge” mode, meaning, they are user interfaces,
and are not part of the ring itself.

3
3/8/2010
Site / Node Types
The ring can be constructed by two types of nodes/sites:
2. Node/Site Type B:
• The site is connected with Radios to both directions of the ring (e.g. East &
West).
• Site contains two IDUs. Each IDU support the Radio in one direction
• One IDU runs with the “Ring RSTP”, and the second
runs in “Single pipe” mode.
• Both IDUs are connected via Gigabit interface

(either optical or electrical).
• Other line interfaces are in “edge” mode.
Switchover / Convergence Criteria

The following failures will initiate convergence:
• Radio LOF
• Link ID mismatch.
• Radio Excessive BER (optional)
• ACM profile is below pre-determined threshold (optional).
• Line LOC
• Node cold reset (“Pipe” and/or “Switch”).
• Node power down (“Pipe” and/or “Switch”)
• xSTP port disable / enable

4
3/8/2010
In-Band Management (1)

In this scenario, management is part of the data traffic, thus, management is
protected with the traffic when the ring is re-converged as a result of a ring
failure.
• “Managed Switch” IDUs will be configured to “In-Band”, while “Single Pipe”

IDUs will be configured to “Out-of-Band”.
• “Single Pipe” nodes will be connected with external Ethernet cable to the
“Managed Switch” for management.
• The reason for that requirement is the “automatic state propagation”

behavior of the “Single Pipe” that shuts down its GbE traffic port upon failure,
thus, management might be lost to it.
In-Band Management (2)

5
3/8/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)

6
3/8/2010
Configuration
Example
RSTP Example (1)

Site #1 Site #2
3 4 5 6 7 3 4 5 6 7
Pipe (slot #2) Pipe (slot #3)
3 4 5 6 7 3 4 5 6 7
MNG (slot #1) Pipe (slot #2)
3 4 5 6 7
MNG (slot #1)
X Site #3
3 4 5 6 7
Pipe (slot #2)
3 4 5 6 7
MNG (slot #1)
• Establish the physical connections according to the setup scheme.

• Leave one link disconnected to avoid loops (for example: site #3 to site #2)
• Configure In-Band MNG using VLAN #200 (or other) on all main IDUs

7
3/8/2010
RSTP Example (2)

Site #1 Site #2
3 4 5 6 7 3 4 5 6 7
3 4 5 6 7 3 4 5 6 7
3 4 5 6 7
MNG (slot #1)
X Site #3
3 4 5 6 7
Pipe (slot #2)
3 4 5 6 7
MNG (slot #1)
• Connect extension IDUs (port #3) to Main IDUs

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

Site #1 Site #2
3 4 5 6 7 3 4 5 6 7
3 4 5 6 7 3 4 5 6 7
3 4 5 6 7
MNG (slot #1)
Site #3
3 4 5 6 7
Pipe (slot #2)
3 4 5 6 7
MNG (slot #1)
• Disconnect IDUs from Switch (except for GW IDU)

• Enable RSTP on all Managed Switches (Main)
• PING EMS to all Sites
• Connect the broken radio link (site #1 to Site #3)

8
3/8/2010
RSTP Example (4)
• Use the EMS to learn which switch is the Root Bridge and which ports are the Root Ports.
• Verify that the ring is set up properly (one Root)
RSTP Example (5)
• Identify the Edge Ports and Non-Edge ports in your scheme and make sure they are
configured the same in your setup

9
3/8/2010
RSTP Example (6)
• Identify the Edge Ports and Non-Edge ports in your scheme and make sure they are
configured the same in your setup
RSTP Example (7)

Make sure that all RING
IDUs (Pipe & Managed)
are support Automatic
State Propagation
(enabled).
Enabling ASP allows RSTP

Ring to converge faster by
propagating radio alarms
into the Line and thus,
accelerating port state
changes.

10
3/8/2010
RSTP Example (8)
• Disconnect a radio link and make sure PING to all Main units is maintained
• Restore connectivity.
• Disconnect a different radio link and make sure PING to all Main units is maintained
•Repeat the same tests with traffic and trails (SNCP).
Thank You !
22

11
3/8/2010
FibeAir ® IP-10
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

1
3/8/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

2
3/8/2010
Why do we need QoS? (2)

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

• Operators are stretching their cost-saving 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
Ceragon Ceragon
Hub / Aggregation site
TDM
E1/T1
2G/3G base station
Fundamental Fact
Static
Dynamic WWW
WWW
Multimedia
emails
FTP
Not all traffic is the same!

Skype
So why treated equally?...
Who’s first?

3
3/8/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 requires less than video

• 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

4
3/8/2010
IP-10G L2 ETH Switch Ports
The IP-10’s L2 Switch has 8 ports:
• Port #1 GbE (Opt. / Elec.)

• Port #2 GbE (Opt. / 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)

5
3/8/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 Rate
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 for max. resolution of priorities
Q4 High
Q3
Q2
Q1 Low

6
3/8/2010
Custom Queuing
Packets sent through

interface
Sent packets
Interface
Egress
Scheduling
Queuing
Scheduling (1)
Once the queues are filled with information, we need to empty them
Which queue should we empty first?
Round-Robin:
Emptying cycle is fixed – all queues are treated equally
Q4 High
Q3
Q4 Q3
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
Q2 Q1 Q2
Pro: no “queue starvation”
Q1 Low Con: no prioritization

7
3/8/2010
Scheduling (2)
Weighted Round-Robin:
Emptying cycle is configurable – every queue can be given specific weight
Q4 High
Q4 Q4
Q3
Q3 Q4 Q4 Q1 Q2 Q3 Q4 Q4
Q1 Q3
Q2
Q2
Q1 Low
Scheduling (3)
4th Strict Priority:
The switch will empty Q4 as long as it has something

Once empty – switch will perform RR on lower queues
If Q4 receives a frame during the Lower-Queues-RR, it will go back to focus
on Q4
Q4 High
Q3 Q1 Q3
Q3 Q4 Q4 Q1 Q2 Q3 Q4 Q4
Q2 Q2
Pro: Optimized Prioritization
Q1 Low Con: “Queue starvation”

8
3/8/2010
Scheduling (4)
All Strict Priority:
The switch will empty a queue as long as the higher queue is empty
Q4 High
Q3
Q3 Q4 Q4 Q1 Q2 Q3 Q4 Q4
Q2

Q1 Low
Shaping
Bursts beyond a EIR (Excessive Information Rate) can be buffered and
retransmitted when capacity frees up, and only when shaping buffers are full
will packets be dropped.

9
3/8/2010
Thank You !
19

10
3/9/2010
FibeAir ® IP-10
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

1
3/9/2010
Agenda
• Step #1: Configure the switch
• Step #2: Configure the switch ports
• Step #3: Configure QoS per port
• Process Review
• Basic Configurations
Step #1: Set your Switch

• Configure the switch mode: Pipe / Managed / Metro
• Configure VLAN IDs

2
3/9/2010
Step #2: Configure Switch Ports

• Configure Port Type: Access / Trunk
• Configure Port Membership
Step #3: Configure QoS per Port

3
3/9/2010
Process Review
Policer per port
25
10 50
Rate Limit

4
3/9/2010
3 classifiers to audit & queue Ingress Traffic
Queuing
Egress port Scheduler
Q4 Q4
Q1 Q3
Q2
Scheduling

5
3/9/2010
Egress Port Shaper
Shaping
Basic Configurations

6
3/9/2010
1. Ingress Rate Limiting
Let’s say we want to limit Video streams

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

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

limit these parameters
1. Ingress Rate Limiting – Setting a Policer

There are 15 different
traffic types that we
can use
Each Policer can have

up to 5 conditions

7
3/9/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

8
3/9/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 .

9
3/9/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

10
3/9/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

11
3/9/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

12
3/9/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 !
26

13
3/9/2010
FibeAir ® IP-10
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

1
3/9/2010
P-Bit Re-Map: Why?

• Re-Map table is per port (e.g. every port can apply a different map)
• Can be used to re-scale Customer CoS
• Can be used to guaranty certain Customer priorities are reserved for specific
purposes
P-Bit Service P-Bit* Service
0-2 Video 0-5 Best
3–4 Data Effort
5–6 MNG 6 MNG

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

Click on the “VLAN Pbits Remap Table” link to configure relevant settings

2
3/9/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

3
3/9/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

4
3/9/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

5
3/9/2010
Using more than a single Classifier
As long as the ingress frames comply to the higher conditions, the system will
not check lower conditions (Classifiers)
If higher condition is not matched, the system will proceed to the lower
condition and so on…
Using more than a single Classifier
Audit VID : if VID = 100 than apply “High Service” otherwise -

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

6
3/9/2010
Thank You !
13

7
3/9/2010
FibeAir® IP-10
Commissioning the Radio Link
Radio Link Common Attributes
IP-10 IP-10
RSL – Received Signal [dBm]

MSE– Mean Square Error [dB]:
• Modulation status
• Signal to Noise Ratio (SNR)
Max. TSL – Max. allowed Transmission Signal [dBm]

Monitored TSL – Actual Transmission level [dBm]
Ceragon Training Handbook - Page 164 1

3/9/2010
ATPC
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, transmission 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

3/9/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.
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

3/9/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
Check
Site A Site B
ATPC ON =
Reduced Power, cost & long-term maintenance
ATPC: Enabled ATPC: Enabled

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

3/9/2010
MRMC Adaptive TX Power
MRMC Adaptive TX Power

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

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

When link suffers signal degradation, modulation may change from 256QAM to QPSK.
However, Max. power will increase to compensate for the signal degradation.

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

3/9/2010
MRMC Adaptive Power

It is essential that Operators ensure they do not breach any regulator-imposed
EIRP limitations by enabling Adaptive TX.
To better control the EIRP, users can select the required class (Power VS.
Spectrum):
• Class 2
• Class 4
• Class 5B
• Class 6A
• FCC
RFU-C should have version 2.01 (or higher) for proper functionality of
“Adaptive TX Power” feature.
The Effective Isotropic Radiated Power (EIRP) is the apparent power transmitted towards the
receiver assuming that the signal power is radiated equally in all directions
Configuration

3/9/2010
Radio Settings – Local Radio
Spectrum Mask
FQ spacing (gap) between channels
Monitored transmission power
Monitored received signal
Monitored Mean Square Error
Required value = zero
Radio frequencies can be set

locally or on remote unit as
well (assuming links is up)
Enable / Disable
Min. target RSL (local)
Enable = no transmission
Value depends on MRMC settings
Encryption: must be identical on
both IDUs
Radio Settings – Local Radio
Enable on both IDUs to get maximum

throughput (500Mbps @ 56MHz)

3/9/2010
Radio Settings – Remote Radio
When the radio link is up, you can configure certain

parameters on the remote unit:
• Make sure Remote IP is available

• Remote RSL can be read
• Remote TSL can be set (depends on remote MRMC script)
• Remote TX MUTE can be disabled (see next slide)
• Remote target RSL for ATPC can be set
Remote Un-Mute
Simplified scheme
Site B is NOT transmitting
but receiver is still ON
Site A is
transmitting
Site B
Site A

3/9/2010
Radio Thresholds
These settings determine the sensitivity / tolerance for triggering:
• 1+1 HSB switchover

• Ethernet Shutdown
• PM generated alarms
MRMC – Multi Rate Multi Coding

Users may set the radio to a fixed capacity or automatic adaptive capacity using ACM.
ACM radio script is constructed of a set of profiles.
Each profile is defined by modulation order (QAM) and coding rate, while these
parameters dictate profile’s capacity (bps).
When ACM script is activated, system “chooses” automatically which profile to use
according to the channel fading conditions.
ACM TX profile can be different than ACM RX profile.
ACM TX profile is determined by remote RX MSE performance.
RX end is the one that initiates ACM profile upgrade or downgrade.
When MSE is improved above predefined threshold, RX generates a request to the

remote TX to ‘upgrade’ its profile.
If MSE degrades below a predefined threshold, RX generates a request to the remote

TX to “downgrade’ its profile.

3/9/2010
MRMC
We shall review this page using the following slides:
MRMC – reading current script
MAX. Capacity
(w/out compression)
ACM Script CH. BW

Modulation
Spectrum
Mask
ACM is on
Spectrum
Class Type

3/9/2010
MRMC – Reading current capacity
Thank You !
24

3/9/2010
FibeAir ® IP-10
Configuring Interfaces
Agenda
• Ethernet Interfaces
• TDM Interfaces
• Auxiliary Channels
• Wayside Channel (Various Configurations)

3/9/2010
Ethernet Ports Configuration

Configuring ETH ports is discussed in previous modules:
• Switch Configuration
• Trunk VS. Access
• Metro Switch Configuration
• QoS Configuration
Interface Rate Functionality

Single Pipe Managed SW / Metro
ETH 1 (SFP) GbE Disabled / Traffic Disabled / Traffic
ETH 2 (RJ 45) GbE Disabled / Traffic Disabled / Traffic
ETH 3 (RJ 45) FE 10 / 100 Disabled / Protection Disabled / Traffic / Protection
ETH 4 (RJ 45) FE 10 / 100 Disabled / Wayside Disabled / Traffic / Wayside
ETH 5 (RJ 45) FE 10 / 100 Disabled / MNG Disabled / Traffic / MNG
ETH 8 Radio According to Disabled / Traffic Disabled / Traffic

(N Type) Licensed fq.
Ethernet Ports Configuration

3/9/2010
TDM Ports Configuration
IP-10 has 16 TDM ports
Supported PHYs:
• E1
• DS1
Dynamic allocation:
Radio bandwidth (which may vary in ACM) is automatically allocated in the
following order:
1. High-priority TDM trails

2. Low-priority TDM trails
3. Ethernet traffic (Data + Management, QoS should be considered)
TDM trails in both sides of a link should have identical priorities.
TDM Ports Configuration
Priority is used for ACM –
When throughput reaches max. link

capacity the system will drop first ETH
traffic and then TDM low priority ports

3/9/2010
Auxiliary Interfaces
• Up to 19200 baud, Asynchronous RS-232.

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

communication between two technicians / installers / etc.
WSC Interface
• WSC interface is limited to 1628 bytes.
• 2.048Mbps (Wide) or 64Kbps (Narrow)
• Consumes BW from the total link BW
Out of band Management using WSC:
In this case, remote system is managed using Wayside channel.
On both local & remote units, Wayside channel will be connected to management port
(using cross Ethernet cable).
WSC can be configured to "narrow“ capacity (~64kbps) or "wide" capacity (~2Mbps).
It is recommended to use “wide” WSC in order to get better management performance,

since “narrow” WSC might be too slow.

3/9/2010
OOB MNG in a 1+0 standalone link
At least 2 management ports are needed in a local unit:
One port for local management, and 2nd port that will be connected to Wayside port.
On remote unit, Wayside port will be connected to management port.

OOB MNG in a 1+1 standalone IDUs (Y-Splitter)
Active & Standby MNG

ports have 2 options to be
connected to the Host:
Using Ethernet splitter
cable connected to external
switch.
Using Protection "Patch
Panel".
WSC port will be connected in each unit to other
available management port.
In remote site, each unit's Wayside port should be
connected to management port.

3/9/2010
OOB MNG in a 1+1 standalone IDUs (P. Panel)
Thank You !
12

3/9/2010
FibeAir ® IP-10
Automatic State Propagation
Agenda
• Introduction
• Interfacing IP-10 with external devices
• Configuration VS. Functionality
• Dead Lock Example
• ASP in Managed / Metro Mode

1
3/9/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".
Interfacing IP-10 with external devices
When external devices do not support Fault Propagation –
Configure the following:

1. Enable Local LOC - to mute local GbE when LOC is raised
2. Enable Remote Fault – to mute local transmitter in case of remote LOF / Link ID
mismatch & LOC
3. Enable Local Excessive BER – recommended but not necessary

2
3/9/2010
Interfacing IP-10 with external devices
When external devices support Fault Propagation (another IP-10) –
Configure the following:

1. Disable Local LOC
2. Enable Remote Fault – to mute local transmitter in case of remote LOF / Link ID
mismatch & LOC
3. Disable Local Excessive BER - to avoid a dead lock scenario
Configuration VS. Functionality

3
3/9/2010
Configuration VS. Functionality
Configuration
VS.
Functionality

4
3/9/2010
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

Site B Site A
TX RX LOC
RX TX

2. LOC alarm is raised

5
3/9/2010

Site B Site A
TX RX LOC
RX X TX

3. LOC alarm triggers Site A to shut down its transmitter (TX Mute)

Site B Site A
TX RX LOC
LOC
RX X TX

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

6
3/9/2010

Site B Site A
TX X RX LOC
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
ASP in Managed 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.

7
3/9/2010
Thank You !
15

8
3/9/2010
FibeAir® IP-10
1+1 External Protection
Introduction
• When a switchover occurs, and previous "Active" becomes

"Standby", accessing the new "Active" will be done using its IP
address
• A "Protection Panel" or protection split cable is designed to

implement E1/DS1 splitters.
• Y-Split cables must be used for Ethernet signals.

3/9/2010
Setup Example (Standalone IDUs)
Configuration Steps (1)
Item Step Description Check
1 Set both IDUs to factory default

2 Active (1st IDU) + Standby (2nd IDU) should have identical HW
(same P/Ns…T-Cards…Auxiliary interfaces etc.)
3 Active (1st IDU) + Standby (2nd IDU) should have identical SW version
4 Active (1st IDU) + Standby (2nd IDU) should have identical License
5 Configure Active + Standby IDUs to have identical Switch Mode

(Pipe…Managed…Metro)
6 Active (1st IDU) + Standby (2nd IDU) should have unique IP address per chassis
7 Active (1st IDU) + Standby (2nd IDU) should have the same Management settings
(Out of band / In-Band & VID)
8 Install 1st IDU

3/9/2010

9 1st IDU: Enable Protection (MNG will be lost for 60 sec.)
10 1st IDU: Lock Protection
11 Install 2nd IDU
12 2nd IDU: Enable Protection
13 Connect ETH cross-cable between the protection ports of the two IDUs
(when units are not in a shelf)
14 Disconnect the MNG cables from both IDUs
15 Connect ETH Y-splitter to both IDUs (to the MNG ports)
16 Connect your MNG cable to the Y-Splitter cable and verify both IDUs can be
managed
17 Verify Active IDU shows Mate IP address
18 Click “Open Mate” and log in to the mate IDU
19 Verify there are no “Configuration Mismatch” alarms
20 Verify there are no “Mate Communication failures”
21 Complete system setup (cabling & configuration)
22 In Active IDU – click “Copy to Mate” (STBY IDU will restart)
23 Initiate Manual Switchover and Forced Switchover: verify traffic is OK.
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".
Note: The same procedure should be issued in the remote end, while installing
the radio.

3/9/2010
Thank You !

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
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
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
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
Configuration
Switch Configuration – Mode and VIDs

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

6
Creating MAIDs
Create the domains as depicted in the setup diagram on both IDUs
Settings must be unique and identical
Domains defined…
You should see the following status on your MAID list page (on both IDUs):
If you point your cursor to the “No MEPs” indication LED, you will be notified that MEPs
need to created as well

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

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

LEFT IP-10
RIGHT IP-10

9
CCM enabled > Remote MEP is detected
As you can see, CCM enables auto-learning, hence – both MEPs discover each other
(MAC and remote MEP ID are now known)
New alarms indicate that process of creating the remote MEP is not fully complete
Creating Remote MEPs
Click on the Add button to add a remote MEP on every IDU

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

(results on next slide)

11
PING results (MEP1 to MEP2)
“D1S2” – Creating another service

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

monitor the Radio ports

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

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

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

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

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

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

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

regardless of VLANs and
Services 1
More test-point –
More L2 capabilities!
We shall add a MIP point on

every Radio interface
Make sure you set the MIP

level according to the level
of the “Parent” domain

17
In the MEP & MIP list, we can see the switch ports and there
MACs:
In our example, we need to add a MIP on the Radio port
Therefore, we shall expand the Radio port to configure the

MIP
Add MIPs on both radio ports (both IDUs)
Please make a note of the Radio MAC address of each IDU – we shall need it later

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

Manual PING | Manual Link Trace | Automatic Link Trace

19
Manual PING
To PING from MEP 1 to MEP 2, you will need to set the following parameters:
• Remote interface MAC

• Level
• VLAN
Successful PING requires setting the correct path
Manual Linktrace
To trace an interface , you will need to set the following parameters:
• Remote interface MAC

• Level
• VLAN
Successful Trace requires setting the correct path
Results on next slide

20
Manual Linktrace Results
FDB –
MIP informing us that it

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

every Radio port)
Eventually we traced MEP 1

(HIT)
Automatic Linktrace
To enable Auto Linktrace – select the checkbox next to the target Remote MEP
and then click “ADD SELECTED”

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

22
3/9/2010
FibeAir ® IP-10
Loopback Maintenance
Agenda
In this module we shall describe

the various actions we can
perform to properly maintain and
troubleshoot the IP-10 system

1
3/9/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:

2
3/9/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):

3
3/9/2010
IF Loopback – Analysis using Event Log

Let’s assume radio link is down – LINK LED is RED
16:29:01 We enable IF LB, therefore Link alarms clear
16:29:05 Loopback replaces remote unit – therefore alarm disappears
16:30:01 Loopback automatically stops, link recovers to original state
16:30:05 Radio link is down (original state)
PDH Line LB towards Line (NE)
LB towards the line

4
3/9/2010
PDH Line LB towards Line (Near End)
Use this feature to evaluate connection to customer’s patch-panel
Alarm is displayed in CAS:
and in Event Log:
PDH Line LB towards Radio (FE)
LB towards the radio
Tester

5
3/9/2010
PDH Line LB towards Radio – Event Log Analysis

Let’s assume PDH port #1 is enable but not connected
Therefore, Major alarm is on (RED)
16:59:44 We enable Line LB towards the radio
16:59:46 Loopback replaces end-device – therefore alarm disappears
17:06:37 Loopback is OFF
17:06:38 PDH port alarm is ON again…..
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

6
3/9/2010
Thank You !
13

7
3/9/2010
FibeAir ® IP-10
EMS Backup Maintenance
Agenda
In this module we shall describe the various

actions we can perform to properly maintain
and troubleshoot the IP-10 system using:
1. Configuration File
2. Unit Information File
3. FTP Server

1
3/9/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

2
3/9/2010
Local FTP Server
Uploading or Downloading the CFG & Unit files requires an FTP Server
As long as your IP-10 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

3
3/9/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

4
3/9/2010
Upload /
Download
Uploading the CFG File (IP-10 to Server)
Click “Create Archive” to

allow the IP-10 zipping all
parameters into one file

5
3/9/2010
Wait till task is

successfully completed
Next step:
Click “Upload Archive” to allow
the IP-10 transferring the zipped
file to your server

6
3/9/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)

7
3/9/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

8
3/9/2010
Downloading the CFG File (Server IP-10)
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
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)

9
3/9/2010
Thank You !
19

10
3/9/2010
FibeAir ® IP-10
EMS Security Configuration
Agenda
• SSH
• HTTPS
• SFTP
• Users & Groups
• Password

1
3/9/2010
Security Configuration
Update first FTP connection
SSH – Secured Shell

• SHHv1 and SSHv2 are supported.
• SSH protocol can be used as a secured alternative to "Telnet".
• SSH protocol is always be operational. Admin user can choose whether to
disable
• "Telnet" protocol, which will be "enabled" by default. Server authentication
will be based on IP-10’s "public key".
• Key exchange algorithm is RSA.
• Supported Encryptions: aes128-cbc, 3des-cbc, blowfish-cbc, cast128-cbc,
arcfour128, arcfour256, arcfour, aes192-cbc, aes256-cbc, aes128-ctr,
aes192-ctr, aes256-ctr.
• MAC (Message Authentication Code): SHA-1-96 (MAC length = 96 bits, key
length = 160 bit). Supported MAC: hmac-md5, hmac-sha1, hmac-
ripemd160, hmac-sha1-96, hmacmd5-96'
• The server will authenticate the user based on “user name” and
“password”. Number of failed authentication attempts is not limited.
• Server timeout for authentication: 10 min. This value cannot be configured.

2
3/9/2010
HTTPS
In order to manage the system using HTTPS protocol, user should
follow the following steps:
• 1. Create the IDU certificate based on IDU's public key.
• 2. Download the IDU certificate.
• 3. Using CA certificate (Optional steps)

i. Download the IDU CA's certificate.
ii. Enable WEB CA certificate.
• 4. Set WEB Protocol parameter to HTTPS
HTTPS – Public Key Upload

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

• The public key file will be in PEM format.
• Click “Upload Public Key”
• The status of the “upload” operation can be monitored. The returned status
values are: “ready” (default), “in-progress”, “success”, “failed”. In any case
of failure, an appropriate error message will appear.

3
3/9/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.

4
3/9/2010
HTTPS - Activation
WEB interface protocol can be configured to be HTTP (default) or HTTPS

(cannot be both at the same time).
While switching to HTTPS mode, the following must be fulfilled:

• WEB server certificate file exist.
• Certificate public key is compatible to IDU’s private key.
• If one of the above tests fails, the operation will return an appropriate error
indication.
• Open WEB Browser and type the URL ”https:\\<IP of target IDU>”.
Note:
This parameter is NOT copied when “copy to mate” operation is initiated,
for security reasons (unsecured unit should not be able to override security
parameters of secured unit).
SFTP (Secure FTP)
SFTP can be used for the following operations:
• Configuration upload/download,
• Upload the unit info.
• Upload public key.
• Download certificate files.
• SW download

5
3/9/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…

6
3/9/2010
Adding Users
Adding Users
New users will be required to change their

password when they log in for the first time

7
3/9/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

8
3/9/2010
Thank You !
17

9
FibeAir® IP-10
License
Management
Guide
Part ID: BM-0139-0

Doc ID: DOC-00019183 Rev a.00
November 2008

Notice
This document contains information that is proprietary to Ceragon Networks Ltd.
No part of this publication may be reproduced, modified, or distributed without prior written
authorization of Ceragon Networks Ltd.
This document is provided as is, without warranty of any kind.
Registered TradeMarks
Ceragon Networks® is a registered trademark of Ceragon Networks Ltd.
FibeAir® is a registered trademark of Ceragon Networks Ltd.
CeraView® is a registered trademark of Ceragon Networks Ltd.
Other names mentioned in this publication are owned by their respective holders.
TradeMarks
CeraMapTM, PolyViewTM, EncryptAirTM, ConfigAirTM, CeraMonTM, EtherAirTM, and MicroWave
FiberTM, are trademarks of Ceragon Networks Ltd.
Other names mentioned in this publication are owned by their respective holders.
Statement of Conditions
The information contained in this document is subject to change without notice.
Ceragon Networks Ltd. shall not be liable for errors contained herein or for incidental or
consequential damage in connection with the furnishing, performance, or use of this
document or equipment supplied with it.
Information to User
Any changes or modifications of equipment not expressly approved by the manufacturer
could void the user’s authority to operate the equipment and the warranty for such equipment.
Copyright © 2008 by Ceragon Networks Ltd. All rights reserved.
Corporate Headquarters: European Headquarters:

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

Contents
General .......................................................................................................... 1
Getting Started .............................................................................................. 1
How to use the System................................................................................. 5
Managing the License .................................................................................. 6
Working with Devices .......................................................................................... 6
Working with Licenses....................................................................................... 16
Settings ............................................................................................................... 23
Generating Reports ............................................................................................ 25

General
This guide explains how to work with the FibeAir® IP-10 web based License Management System.
The system enables authorised users to obtain license-related information and perform license-related
operations.
Getting Started
To start the management application:
1. In your web browser, go to the address http://80.74.99.83/LMManage/login.aspx
2. To log in to the system, enter your user name and password, and then click Login.
Note the following user name rules:
Ceragon
FibeAir® IP-10 License Management Training Handbook - Page 245
System 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 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 Ceragon Training Handbook - Page 247 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.


Ceragon - IP-10R1 ADV - Book - v1.3 PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Ceragon - IP-10R1 ADV - Book - v1.3 PDF

Enviado por

Direitos autorais:

Formatos disponíveis

©

Ceragon Training Center

Course: IP10AO&M Extended Operation and Maintenance

Introduction to Radio Microwave:

 Parameters affecting propagation (Fresnel Zone, Duct, Multipath)

 The need for smaller broadcast domains

Introduction to IP-10 IDU

IP-10 Front Panel Description

Introduction to RFU-C / or other ODU type

 Physical Installation of IDU + ODU

 System name & Contact Details (Unit Info)

Radio Link Commissioning:

1 Ceragon Training Agenda v2.0

Ceragon Training Handbook - Page 1

Adaptive Coding & Modulation (ACM)

Switch Mode Configuration:

 ETH Ports (Trunk VS. Access)

Troubleshooting Tools & Maintenance:

 Using the Current Alarms

1+1 Protection: Configuration Review

1+1 Protection: Practical Exercise

QoS: Configuration Review

QoS: Practical Exercises

Introduction to CFM (802.1ag)

CFM: Practical Exercises

Q-in-Q: Configuration Review

Q-in-Q: Practical Exercise

2 Ceragon Training Agenda v2.0

Ceragon Training Handbook - Page 2

“Think Backhaul Networks”

2 Proprietary and Confidential

Ceragon Training Handbook - Page 3

Ceragon FibeAir Family

OA&M Service Management Security

Carrier Ethernet Switch TDM Cross Connect

ACM XPIC Ch-STM1/

3 Proprietary and Confidential

IDU 1500R – Point to Point SDH Radio Link

STM Ring STM Ring

4 Proprietary and Confidential

Ceragon Training Handbook - Page 4

IDU 1500R – SDH RING

5 Proprietary and Confidential

IP-MAX^2 IDU: GbE Backhaul

6 Proprietary and Confidential

Ceragon Training Handbook - Page 5

IP-10 IDU: Enhanced Cellular Backhaul

7 Proprietary and Confidential

IP-10G IDU: A Nodal Solution

8 Proprietary and Confidential

Ceragon Training Handbook - Page 6

3200T All Indoor: High Capacity Trunk

9 Proprietary and Confidential

3200T Split Mount: High Capacity Trunk

10 Proprietary and Confidential

Ceragon Training Handbook - Page 7

FibeAir RFU-HP FibeAir RFU-HS FibeAir RFU-P FibeAir RFU-C

High power Standard power

Proprietary and Confidential

Outdoor Enclosures – Solution Benefits

Full Outdoor solution:

• Dust and weather proof

Proprietary and Confidential