IP-MAX GbE Course Handbook v1.0

Ceragon Training Center
Training.Ceragon.Com
FibeAir®IP-MAX
Course Handbook
Page 1 Ceragon Training Center

Ceragon Training Agenda
Product: IP-MAX^2
Course: Operation and Maintenance
Duration: 2 days
DAY ONE
IP-MAX ^2 Introduction:
• Feature Description
• Front Panel Description
• Power Consumption
• Architecture
Installation:
• Physical Installation of IDU + ODU

• IP address using Craft Terminal
Management Review:
• In Band
• Out of band
• Wayside Channel
Preliminary Commissioning (using CV EMS):
• Logging in to the CV EMS

• System Information
• System Versions
• Disk File
• Configuration Report
• Configuration File Upload / Download
• Saving Unit File
• SW Download
Commissioning:
• External Alarms
• Auxiliary Channels
• MRMC + ACM (fixed, adaptive)
• The Radio Link
• The Radio interface
• The GbE interface
• The TDM interface
• Management: setting subnet mask, In-Band configuration
• Management: SNMP, NTP, Trap destination, Neighbors report
1 Ceragon Training Agenda v2.2

Ceragon Training Agenda
DAY TWO
Performance Monitoring:
• Reading Current Alarms

• Reading Event Log
• Using Thresholds
• Radio PM
• Line PM
• Front Panel LEDs
Troubleshooting Tools & Maintenance:
• Loopbacks
• PRBS Tests
• Built-in tests
• System Resets
• Clearing PM
• Setting system to default configuration
• Enabling Temporary License
• Forcing remote TX level
• Un-muting remote TX
Protection:
• Protection Modes
• Configuration
Protection: Practical Exercises
Exam / Course Summary
2 Ceragon Training Agenda v2.2

FibeAir IP-MAX | IP-MAX^2 IDU
Introduction – Part 1
Module Topics
• Advantages
• Components
• Power Consumption
• Native Ethernet
• Wireless IP Backhaul
• IP-MAX Solutions
• FE System
• IDU Block Diagram
• IDM Module
• HW Options
Ceragon Networks proprietary and confidential
1 Page 4 Ceragon Training Center

FibeAir IP-MAX Advantages
Strong economic value with pay-as-you-grow concept to Reduce

network costs
Optimize each network nodes for today’s deployments
Network versatility - seamless integration into multiple networks
Enables future growth capacity as needed
FibeAir IP-MAX Advantages

FibeAir IP-MAX Components
IDM - In Door Module: IDM - In Door Module:

IDC - In Door Controller
2xFE / GbE w/wo TDM 2xFE / GbE w/wo TDM
FibeAir IP-MAX Power Consumption
While Muted
Current [A] Power [W] Current [A]
Only RFU: RFU HP 2.04 97.92 0.6
RFU LP 1.52 72.96 0.6
Only IDU IDC + Drawer_A 0.66 31.68

only Drawer B 0.36 17.28
Complete IDU(IDC+DrawerA+DrawerB) 1.02 48.96
RFU+IDU drawerA: RFU HP+IDC+DrawerA 2.7 129.6

RFU LP+IDC+DrawerA 2.18 104.64

Native Ethernet
IP-MAX
A Native Ethernet Platform
without mapping Ethernet packets over SDH/SONET or PDH
Highest throughput
Lowest latency (< 0.15 msec for GbE@400 Mbps)
Vital for VoIP & delay-sensitive applications
Transparent to MAC addresses
Optional native TDM with native IP traffic, whereby none is mapped over the other,
yet both IP and TDM dynamically share the same overall bandwidth.
Wireless IP Backhaul
IP-MAX
800 Mbps (GbE)
• GbE or nxFE solution
• 50 - 800 Mbps full duplex
• 1+0, 2+0 & 1+1 Hot Stand-By (HSB)
Less then 50 msec switch time 400 Mbps (GbE)
• East and West

• Space diversity (SD)
• Hitless errorless switching 150-200 Mbps (2 FE)
• Double capacity per given BW (XPIC)
• Ideally suited for any architecture
(PTP, ring, mesh, 1+1, etc.)
50/100 Mbps (FE)
Simple migration path to higher capacities

FibeAir IP-Max Solutions
Fast recovery time to support RSTP
Highest priority level for BPDU packets
TDM voice transmission with dynamic allocation
Built in layer 2 switch, provides fast Ethernet traffic aggregation
QoS support - by port / VLAN 802.1p / DiffServ (packet queuing and

priority)
Longer distances / smaller antennas with high power RF Unit at low frequencies
FibeAir IP-Max Solutions
GbE + 8xE1 IDM

150, 300, 400 Mbps throughputs on a single carrier
1, 2xFE + 8xE1 IDM

50, 100, 150, 200 Mbps throughputs on a single carrier

IDU Block Diagram
IPS - IDU power supply

falcon
MUX IF section
board MODEM
section
Back plane
FE #1
Left Radio
FE#2
IDM
8xE1/8xT1/FE only
IDC 2x64K/2M 10BaseT

AUX
board 2xEth WSC +EOW EOW
Eth, PPP/SLIP,Ext Alarms, Leds
Fans module
Fast Ethernet System
2xFE+
xFE 8xE1/T1’s
8xE1/T1 2xFE 8xE1/T1 2xFE

Fast Ethernet System
FE wireless connectivity for IP networks @ 6-38 GHz
Frequency – 6-38 GHz standard or high power ODU for 6-11 GHz
Capacity – 50, 100, 116, 150, 200 Mbps per carrier and 400 Mbps per single
channel
Bandwidth - 10/20/14/28/50/56 MHz ETSI/FCC (software selectable)
Configurations - 1+0, 1+1, East-West, XPIC, Hitless-errorless Diversity, 2+0
in a single 1U IDU
Interfaces per IDM – 1 or 2xFE and 8xE1/T1 with dynamic BW allocation
up to 4xFE customer ports per IDU with full 400 Mbps throughput
Optional AES encryption
IDM – In Door Module
Two independent IDMs per IDU
Components:
Power supply – DC to IDM, IDC and ODU
IF card – IF frequency conversion, cable interface and IDU loop
MUX – (Ethernet) line interface unit (1/2 FE, 8xE1/T1), multiplexing
and frame construction, framing
Modem – ASIC based (QPSK, 16, 32, 64, 128, 256 QAM),
modulation/demodulation, equalizer, FEC, pre-distortion

HW Options
IDCs with 2xEth wayside can work with IDC with 2xEth or IDC with
2xETH+EOW across the link.
IDCs on both sides of the link may have a different GigE S/W package.
IDM (FE)
IDM-50 1xFE port, 50Mbps capacity
IDM-100 1xFE port, 100Mbps capacity
IDM-150/200 2xFE port, 150/200Mbps capacity
SFP IDM and 10/100/1000 can work across a link or as 2+0.

However, same IDM type must be used for 1+1 HSB and XPIC configurations.
Same HW for 1xFE and 2xFE
With or without 8xE1/T1
Thank You !
training@ceragon.com
16

FibeAir IP-MAX | IP-MAX^2 IDU
Introduction – Part 2
Module Topics
• Licensing
• IDU – ODU Compatibility
• ETH throughput
• ETH latency
• Frame Structure
• FE Supported Systems
• FE main features
• IP-MAX^2 GbE
• MRMC
• ACM
• QoS
• Multi-Radio

Licensing
Four types of capacity options are available:
GigE, 100Mbps, +8xE1/T1 – total capacity of 100Mbps
Two types of Radio modes are available:

ACM supported
ACM not supported
SW license can be purchased for upgrading the capacity/mode:

SW licenses from 100Mbps to: 200Mbps, 300Mbps or 400Mbps
SW license from 200Mbps to: 300Mbps or 400Mbps
SW license from 300Mbps to: 400Mbps
SW license from no ACM to ACM support
Supported IDCs:
IDC with dual Ethernet wayside
IDC AUX Eth – dual Ethernet wayside with EOW
IDU – ODU Compatibility

ODU
IDM
FibeAir 1500P* 1500HP** 1500SP***
1 IDM –GigE (max capacity configured) 100/150Mbps GO GO GO GO
2 IDM –GigE (max capacity configured) 200Mbps NO GO GO GO GO
3 IDM –GigE (max capacity configured) 300Mbps NO GO GO NO GO NO GO
* 1500P ODUs in 11/13 GHz – Wideband ODUs should be used for higher capacities requiring occupied
BW>30.5 MHz
** 1500HP RFUs – support capacities requiring occupied BW <=30.5 MHz

*** 1500SP RFUs – support capacities requiring occupied BW <=30.5 MHz For
higher capacities requiring occupied BW (36-54 MHz) for 300/400 Mbps wideband RFUs should be used.

IDU – ODU Compatibility / ODU FQs
ODU
IDM
FibeAir 1500P* 1500HP** 1500SP***
1 IDM –GigE (max capacity configured) 100/150Mbps GO GO GO GO
2 IDM –GigE (max capacity configured) 200Mbps NO GO GO GO GO
Operating frequency bands:

• FibeAir ODU – 6-38 GHz
• 1500P ODU – 11-38 GHz
• 1500P Wide ODU – 11/13 GHz
• 1500HP RFU – 6-11 GHz
• 1500SP RFU – 6-8 GHz
• 1500SP Wide RFU – 6-8 GHz
Ethernet Throughput
Ethernet throughput depends on the system configuration, capacity selected and

packet size (throughput results may vary when using ACM):
• 100 Mbps Configuration – actual throughput 85-135 Mbps


Ethernet Latency
Ethernet latency depends on the system configuration, capacity selected and
packet size.
• For fixed modulation the latency is 70 to 250 uSec.

• For ACM adaptive mode the latency is 250-570 uSec
Ceragon allows changing radio latency in order

to achieve minimal latency of the Ethernet packets:
• Low = Interleaver is set Off

• High = Interleaver is set On
Standard scripts can be configured for low latency (reducing ~200 uSec) or high
latency (adding ~0.2 dB to the system gain) – the default is Low.
The 3756 and ACM Modem scripts are LOW latency by design and configuring it to
high latency does not change the latency.
Frame Structure
Maximum frame length:

SFP IDM – 12000 bytes
10/100/1000 IDM – 9000 bytes
Dynamic allocation:
In GigE system, the data space of the unused E1/T1s (disabled ports) is
automatically allocated to the Ethernet transmission.
E1/T1 enabled/disabled ports must have similar configurations on both sides of

the link or GigE traffic will not work properly.

Frame Structure
Proprietary frame is constructed to transport the Ethernet and 8xE1/T1s.
Frame size depends on the system type (capacity).
The frame consists 81 bytes for overhead, and bytes for Ethernet and E1/T1s payload:
2 bytes for frame synch (F6 & 28).

24 consecutive frames are required to change LOF state
3 bytes (192Kbps) for wayside, user channel and EOW
1 byte for management (local-remote and in-band)
1 byte for ATPC and Link ID
1 byte for “Change Remote” command for 1+1 configuration
3 spare bytes (1 for encryption, 2 for future use)
1 byte for BIP (radio error calculation)
1 byte for stuffing the 8xE1/T1 channels (required for carrying their clock
32 bytes for wayside channel (2 Mbps capacity for wayside)
Three bytes for ACM
Two bytes for graceful degradation on multi radio
Other bytes – reserved
FE Supported Systems
# Modem Bit Rate Channel BW (Occupied Modulation IDM Interface
Script [Mbps] BW)
[MHz]
1 1125 104Mbps 25 (22.5) 32QAM 1/2xFE
2 1228 116Mbps 28 (26.5) 32QAM 1/2xFE

3 1528 155Mbps 28 (26) 128QAM 2xFE
4 1550 155Mbps 50/56 (45) 16QAM 2xFE
5 1540 155Mbps 40 (30.5) 64QAM 2xFE
6 1540W 155Mbps 40 (36) 32QAM 2xFE
7 2050 200Mbps 50/56 (46.5) 32QAM 2xFE
8 2030 200Mbps 30 (28) 256QAM 2xFE
9 4410 45Mbps 10 (9) 64QAM 1/2xFE
10 4420 45Mbps 20 (15.5) 16QAM 1/2xFE
11 5814 57Mbps 14 (13.5) 32QAM 1/2xFE
12 4228 41Mbps 28 (24.5) QPSK 1/2xFE
13 4440 45Mbps 40 (28) QPSK 1/2xFE

FE Main Features
Capacity: 41, 45, 57, 104, 116, 155, 200 Mbps

Configurations: 1+0, 1+1, 2+0 XPIC, East-West, Space/Frequency Diversity
Support for all ODU/RFU types
Dynamic bandwidth allocation of E1/T1 from Ethernet capacity
2xFE ports separation using VLANs (no external configuration required)
QOS
SW license for capacity upgrade
FibeAir IP-MAX2 Gigabit
Optical (SFP)
Electrical 10/100/1000 Mbps (RJ45)
• Unique Adaptive modulation (QPSK-256QAM)

• 56 MHz channels 100, 200,250,300,350,400 Mbps
• 50 MHz channels 80,150,200,250,300,350 Mbps
• 28/30 MHz channels 50,100,120,140,170,200 Mbps
• Dual-radio Support for single GbE interface

• Flow Control
• Quality of Service (QoS)
• Ethernet Statistics (Radio and Line)

FibeAir IP-MAX2 (G)
Supports GBE+8E1, GBE+8T1 and GBE only.

Full capacity over all 6-38 GHz frequency bands
Ultra low latency (< 0.15 ms)
Multiple network topology support - Ring, Mesh, Chain, Star and Tree
Way-Side Channel Interface Dual Ethernet 10/100BaseT RJ45
Order-Wire Interface.
External alarms, 5 inputs, and 3 outputs.
First Ethernet Microwave to achieve MEF certification
13 Ceragon Networks proprietary and confidential
Main Features
In-band management channel rates:

64kb/s – proprietary (one byte per frame).
192kb/s – Dccr (three bytes per frame).
256kb/s – Media specific (4 bytes per frame).
Second layer, Media Access Controller (MAC).
Jumbo frames (up to 9600 bytes) and Super Jumbo Frames (up to
12000 bytes).
Rapid Ethernet Tx Mute on radio fault (SD/EBER/LOF) and on line fault

(GBE LOS). Configurable radio fault trigger and Tx mute on remote.

Multi Rate Multi Constellation
Modem Bit Rate Channel BW Modulation

Script [Mbps] (Occupied BW)
[MHz]
1528 150Mbps 28 (26) 128QAM
1550 150Mbps 50/56 (45) 16QAM
1540 150Mbps 40 (30.5) 64QAM
1540W* 150Mbps 40 (36) 32QAM
3150 300Mbps 50 (45) 256QAM

3156 300Mbps 56/80 (52) 128QAM
3756 400Mbps 56/80 (54) 256QAM
A28* 40-200Mbps 56/80 (26) QPSK-256QAM
A50* 90-360Mbps 50 (47) QPSK-256QAM
A56* 100-400Mbps 56/80 (54) QPSK-256QAM
Dynamic Adaptive Modulation
Goal
Increase network capacity (access and backhaul transmission)
How does it work?

Utilize highest possible modulation according to the link quality
degradation
Hitless switchover between modulation schemes based on MSE
criterion
Maximize spectrum usage
Increased capacity over given bandwidth

Ceragon’s Dynamic Adaptive Modulation
Extra 4 x capacity on a given Channel Bandwidth
Throughput
For each signal carrier:
100 to 400 Mbps @ 56 MHz Ch BW
50 to 200 Mbps @ 28 MHz Ch BW
Continuous traffic for Voice & real time services
Availability and capacity
Rx 256 QAM
level
99.9 %
128 QAM
99.95 %
64 QAM
99.99 %
32 QAM
99.995 %
16 QAM
99.999 %
QPSK
Capacity
200 170 200 140 100 200 120 200 Mbps
( @ 28 MHz channel)
Unavailability
Hitless switch-over , step by step down/up thru 6 modulation schemes


Adaptive Modulation principle example
256-QAM Data
400 Mbps
Voice
56 MHz
32-QAM Data
Data
250 Mbps Voice
56 MHz
Continuous traffic for Voice & real time services
Adaptive Modulation Configuration
User choice:
• Adaptive modulation or Fixed modulation
• Maximum and minimum modulation setup

FE QoS
Priority Queues
Four priorities queues
W1 - Highest priority
Highest priority to BPDU Packets
(Bridge Protocol Data Unit).
Classify Scheduling
Arrivals departures
Classifying according to: W2
Port
802.1p VLAN
W3
TOS - IP precedence
Scheduling according to
Strict priority
Weighted Round Robin 8/4/2/1 W4 – lowest priority
GbE QoS
Four priorities queues
Highest priority to BPDUs
Classifying according to:
VLAN 802.1p
TOS / TC - IP precedence
MPLS exp field
VLAN ID
UDP packets
Scheduling according to:
Strict priority
Configurable Hierarchical
Weighted Round Robin (16 – 1
weights)
Or, first queue strict and others WRR

Flow Control
Supports Flow Control according to IEEE 802.3x

When flow control is enabled, FibeAir IP-MAX sends back PAUSE
frames, for signaling that the incoming buffer is full
Multi Radio
The GigE traffic is divided among 2 radios on the ingress and assembled back
to one stream on the egress side. All other data is duplicated on both radios
(E1s/T1s, WSC, EOW).
The system supports 8 E1s/T1s on this mode (not 16) and only one WSC and
one EOW.
In case of radio failure on one radio link, the ETH traffic will be allocated only to
the working radio, reducing the capacity by half.
The E1/T1s will be taken from the working radio (traffic hit of up to 50 mSec).
When failure is fixed, ETH traffic is automatically allocated to both radios
allowing full capacity.
Alarm is raised in case of radio failure on one link and ETH traffic is blocked on
ingress or egress port.
Event is reported in case of E1/T1 radio source (Right/Left) is changed

Multi Radio - Maintenance
User may block Ethernet traffic on Right or Left (or both) for maintenance
purposes
Ethernet allocation to the restored link might take up to 20 seconds after link is
up in order to assure link stability before Ethernet is allocated.
In case automatic GbE Tx mute is configured, Ethernet port will be muted only
in case of radios at both ends have failure.
Multi Radio – Line Protection is Off
The Ethernet and E1/T1s interfaces must be connected only to the right IDM.
There is no protection or graceful degradation in case of line failure or total Right

IDM failure (only radio failures are protected in Right or Left IDMs).

Multi Radio – Line Protection is On
The Ethernet interfaces on Right and Left IDMs should be connected with splitters
(for 50mSec switching time) or connected to a switch for link aggregation
(note that static LAG provides faster switching times than LACP configurations).
E1/T1s interfaces should be connected using splitting panel.
Multi Radio – Line Protection is On
In case of radio failure, the radio graceful degradation mechanism will block the
faulty radio.
In case of line failure, the line protection mechanism will perform a switch.
In case of total IDM failure, both mechanisms will react.
Protection maintenance options in this mode (Switch request, Force switch and
Lockout) are applied on the line interfaces (and not on radio, which has separate
Multi Radio protection commands).

Multi Radio with XPIC + ACM
The feature can be applied with XPIC, ACM or both.
2+0 Ethernet Traffic (XPIC supported) with graceful degradation ability

to one carrier
1+1 HSB for 8xE1s
Multi Radio - ACM

Multi Radio & Adaptive modulation –
Independence behavior for each radio carrier Maximize spectrum efficiency
8E1 GbE 8E1 GbE

Thank You !
31

Management Review
Objectives
This presentation explains the process of planning the in-band

management network with respect to the following products:
• FibeAir 1500R
• FibeAir 1500P
• FibeAir IP-MAX^2
• FibeAir IP-MAX
Advanced Operation & Maintenance Course

Agenda
• Ceragon Proprietary Protocol

• Smaller Broadcast Domains
• Ring IP
• Out of band VS. In-Band
• WSC
• In-Band management channels
• Managing external devices using PPPoE
Ceragon Proprietary Algorithm

Ceragon in-band management is a proprietary algorithm based on “subnet routing”
For each in-band management network, only one (or two, in a ring configuration)
element is handling the communication from the in-band management network and the
‘outside world’ – the customer’s management network
Each Ceragon element contains internal router used for in-band management decisions
ETH MGMT Port

Radio: Line:
•DCCR •DCCR
•DCCM •DCCM
•MS •MS
•Proprietary •PPPoE
Local MGMT Processor

Each Ceragon element is assigned a status, which defines the operation of its internal
router: Network Element (NE) or Gateway Network Element (GNE)
These two definitions are necessary to manage management traffic flow & prevent
broadcasting of unnecessary messages in management sub-networks
Each element, based on its configuration, decides whether to take the packet to itself
(local processor for its own management), take the packet into (or out of) the in-band
management network, or to transfer it from one side of the in-band to the other side
(Line to Radio or Radio to Line)
The in-band network should be regarded as internal LAN (between Ceragon elements
only) that is part of the ‘external’ LAN, where the GNE and the customer’s management
network is (NMS, LAN or Router)
A subnet, of any size, should be allocated for the Ceragon elements. This is the In-band
Management Ring IP range. Only Ceragon elements should be on this subnet. The
router, the NMS and other in-band management networks should be out of this subnet.
The GNE is the only element that communicates to elements on the customer’s
management networks. All communication of NEs are handled by the GNE (the GNE
answers ARP requests for all NEs).

Ceragon Proprietary Algorithm - Simplified
Management
Management LAN Network
GNE
GNE
NE
GNE
NE
NE
NE
NE
Chain Topology Chain Topology NE
with a Spur
Ceragon Proprietary Algorithm - Simplified
Management
Management LAN Network
Ring Topologies GNE NE
GNE GNE
NE NE
NE NE
NE
NE
NE NE
NE
NE NE

Breaking the network into smaller Broadcast Domains
EMS / NMS Site A Site B Site C
Broadcast Domain / subnet Broadcast Domain / subnet Broadcast Domain /

subnet
In-Band Ring
Customer Ethernet Network Plan
Smaller Broadcast domains minimize the total IP addresses required to

manage all the network elements (NEs).
RING IP
EMS / NMS Site A Site B Site C
Broadcast Domain / subnet Broadcast Domain / subnet Broadcast Domain /

subnet
MGMT IP ADDRS In-Band Ring
Customer Ethernet Network Plan
The MGMT PC IP must be outside of the RINP subnet mask

Out of Band VS. In-Band
Out of band Management
Line
Line
IP Network
Out of band Management requires setting up additional network, to support additional traffic
related to management
Advantages:
• Secured link for MNG
• MNG does not consume data bandwidth out of the Radio link

ETH
HUB
• IP-MAX has 2 MNG RJ45 connections (function as a 2 port

HUB)
• Configure IP address to IP-MAX
• Assign IP of the same subnet to your laptop
• Connect your laptop to the IP-MAX (any of the 2 RJ45s)
• Out-Of-Band requires local connection per IDU
Make sure In-Band checkbox is NOT

selected on all IDUs participating in the
network topology

In band Management
Data
Line Line
ETH
GbE
In-Band Management is a mechanism used to transport management information

seamlessly through the existing network (radio link)
Advantages:
Reduced costs on equipment & maintenance
No need for a additional network
Data and MNG are separated
Data bandwidth & MNG bandwidth are fixed and are not derived one from the other
Drawback:
When link goes down – MNG goes down as well
Out of band via the Radio Link (Wayside Channel)
Line
Line
We can allocate Out of band Management in the WSC bytes (2Mbps)
Make sure In-Band is not configured

Wayside Channel
ETH
Enable
PPPoE
WSC
ETH crossed cable connects ETH to WSC on every IDU
Wayside Channel - Configuration
Disable In-Band on all IDUs
Access the Auxiliary Channel config.
Enable WSC on the relevant IDM

Managing ext. equipment with PPPoE
Management frames encapsulated to PPPoE are propagated to nearby

element over a simple crossover Ethernet cable
PPPoE requires unique Network ID
PPPoE / ETH Cross cable
Managing ext. equipment with PPPoE
Line Line Line Line
ETH
SW
Enable In-Band and PPPoE on both IDUs

GW IDU should be selected as GW
Other IDUs should be selected as Network
Elements

In-Band in Chain
Enable Enable
DCCR DCCR
Enable
DCCR
ETH
Enable
PPPoE
In-Band packets are placed in the DCCR bytes
To maintain transport along the radio link we must enable DCCR on all Radio ports on
all IDUs
FO maintains chain connection for Data and Management
In-Band in Chain Enable Enable
DCCR DCCR
Enable
DCCR
ETH
Enable
PPPoE

Managing Ceragon IDUs and 3rd party devices
Enable Enable
DCCR DCCR
Enable
DCCR
ETH
Enable
Enable
PPPoE Enable
PPPoE
PPPoE
• In East-West scenario, we simply connect an ETH cable between the 2 IDUs
• This loop, will transport the In-band management packets through the subnet
Calculating Subnet Masks

• We divide our ring to subnets to minimize the broadcast traffic
• The Gateway and all the NEs must be on this ring, e.g. the same IP address
range
• GW IP can only be defined when we configure the IDU as a Gateway

• The first and last IP address of the subnet cannot be used
Example:
Gateway Ring Subnet Address – 192.168.1.0
Gateway Ring Subnet Mask – 255.255.255.240
That means IPs 192.168.1.0 to 192.168.1.15 are on the Gateway Ring Subnet
and 192.168.1.1 to 192.168.1.14 are valid IP addresses
That also means that you may use up to 14 NEs on that subnet:
192.168.1.0 to 192.168.1.15 = 16 addresses
192.168.1.0 and 192.168.1.15 cannot be assigned to any NE

Your subnet masks should be determined according to the number of

managed NEs:
IP: 192.168.1.100 IP: 192.168.1.6

SM: 255.255.255.0 SM: 255.255.255.252
Local
PC
NMS
GW
IP: 192.168.1.1 IP: 192.168.1.5

SM: 255.255.255.0 SM: 255.255.255.252
Why did we set it this way?

IP: 192.168.1.6
192.168.1.0 IP: 192.168.1.100
SM: 255.255.255.252
SM: 255.255.255.0
.1.1
.1.2
.1.3 NMS
Local
.1.4 PC
GW
.1.5
.1.6
IP: 192.168.1.1 IP: 192.168.1.5
.1.7 SM: 255.255.255.0 SM: 255.255.255.252
.1.8
.1.9
.1.10
.1.11
The NMS needs to manage all NEs, therefore we set a subnet mask that can support a
large number of NEs
Local PC only needs to a single NE (local IDU). Therefore, its subnet mask was set to
minimum - 255.255.255.252 (allows 4 NEs but the first and last cannot be assigned to NEs)

Your subnet masks should be determined according to the number of
managed NEs:
Site A Site B Site C
IDU-2 IDU-4 IDU-6
NMS
IDU-1 IDU-3 IDU-5
2+0
or
2+0 XPIC
Local Local
As an exercise , try setting the IPs and Subnet Masks for Site A & B
(Answers are given in the next slide)

NMS
We need to manage all the network
We need at least 5 IP addresses We need at least 3 IP addresses

So we mask a subnet for 8 (first available): (not shown in the table below)
255.255.255.248 > 6 hosts excluding
broadcast and network IPs
Site A Site B
IDU 1 IDU 2 NMS IDU 3 IDU 4 IDU 5 IDU 6 Local PC
IP
192.168.1.1 192.168.1.2 192.168.1.100 192.168.1.9 192.168.1.10 192.168.1.11 192.168.1.12 192.168.1.13
address
Subnet
255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.248 255.255.255.248 255.255.255.248 255.255.255.248 255.255.255.248
Mask

You may use the following examples when you calculate the
necessary masking:
255.255.255.0 254 available hosts

GNE Routing Protocol

IP packet received
Y
Is it
my own GNE IP Packet is locally by
address? processed by GNE’s router
Y Packet is sent on
Packet Y Packet Radio default
received from ETH is within Ring IP
port (LAN) ? subnet? Packet is sent on
line (LOF on Radio)
No, packet is received N
from in-band network
(Radio / Line) Packet is discarded
Packet Y If packet was received from radio than packet is sent on line
Sending packet via in-
is within Ring IP
band to the other side If packet was received from line than packet is sent on radio
subnet?
Packet is taken out of the in-band

network and sent to LAN ETH ports

NE Routing Protocol
IP packet received
Y
Is it
my own IP Packet is locally by
address? processed by GNE’s router
N Packet
received from ETH
port (LAN) ?
No, packet is
received from in- Y
band network
(Radio / Line)
Packet Y
is within my own NE ignores the packet
subnet mask?
N
If packet was received from radio than packet is sent on line
Sending packet via in-
band to the other side
If packet was received from line than packet is sent on radio
Scenario # 1
NMS
PPPoE
IP 192.168.1.200 192.168.1.1 192.168.1.5 192.168.1.9 192.168.1.13

S.M. 255.255.255.0 255.255.255.0 255.255.255.252 255.255.255.252 255.255.255.252
Element
Type NMS GNE NE NE NE
Local PC 192.168.1.6 192.168.1.10 192.168.1.14

S.M. 255.255.255.0 255.255.255.252 255.255.255.252 255.255.255.252
Ring IP 192.168.1.0
Ring S.M. 255.255.255.240
Network ID 1 1 1 1 1
Site B Site C Site D

Site A EMS / NMS
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 18 * * * 199 200
RING S.M.

Scenario # 2
Site A Site B Site C Site D Site E
NMS
PPPoE
192.168.1.18
#1 SW 255.255.255.240
#7
NMS Site A B to A C to B C to D D to C D to E E to D
IP 192.168.1.200 192.168.1.1 192.168.1.17 192.168.1.5 192.168.1.9 192.168.1.13 192.168.1.33 192.168.1.37
S.M. 255.255.255.0 255.255.255.0 255.255.255.240 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252
Element NMS GNE NE NE NE NE NE NE

Local PC #1 IP 192.168.1.19 192.168.1.6 192.168.1.10 192.168.1.14 192.168.1.34 192.168.1.38
Local PC #1 S.M. 255.255.255.240 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252
Local PC #1 Default GW 192.168.1.17
Local PC #7 IP 192.168.1.25
Local PC #7 S.M. 255.255.255.240
Local PC #7 Default GW 192.168.1.17
Ring IP 192.168.1.0
Ring S.M. 255.255.255.240
Network ID 1 1 1 1 1
Thank You !
34

1/25/2010
IP-MAX^2 CeraView EMS

Preliminary System Setup
Agenda
1. Logging in
2. CV EMS GUI
3. Reading System Information
4. Reading Versions
5. Reading Disk Files
6. Configuration Report
7. Configuration File: Upload & Download
8. Saving Unit Information
9. SW download
10. Launching a new CV session
11. Launching a new remote CV session
Page 45 Ceragon Training Center 1

1/25/2010
Logging in
CV application remembers your

1. Install CeraView EMS application
previous sessions…
2. CV icon will appear on your desktop
3. Double click CV icon
4. Log in :
Username: admin
Password: ceragon
CV EMS GUI
Title shows Release
version & IP address Main Menu Command Bar
Shortcuts /
Quick Access Buttons
IDC
Right
Left IDM
IDM
Protection Status Message Local Comm. Status Message
You may launch as many sessions as needed – your only limitation is your
screen resolution

1/25/2010
CV EMS GUI – Quick Access Buttons

System Information (Time, Description & Temperature)
SNMP Trap Configuration
Current Alarms
Alarm Log Refresh
External Alarms Online Help

(5 in, 1 out)
CV EMS GUI – Quick Access Buttons
Right Radio /IDM Loopbacks
Left Radio /IDM Loopbacks

Top Most Alarm + Access to CAS
Right Radio Configuration
Left Radio Configuration

1/25/2010
Reading System Information
Reading current versions
Please send your local support engineer the current versions or

alternatively you may send a screen-captures of these tabs

1/25/2010
Reading versions after reset (sw download)
Please send your local support engineer the current versions or

alternatively you may send a screen-captures of these tabs
Reading serial numbers
Please send us the Modem & Mux serial numbers to allow us

generating new licenses
Alternatively you may send a screen-captures of these tabs

1/25/2010
Reading Disk Files
Disk Files shows current capacity and utilization of the internal disk space
Information be exported and saved
Reading Disk Files
Indicates a system CRC file Indicates that the file is

compressed.

1/25/2010
Saving Disk Files
Configuration Report
All the configuration data can be displayed on screed,

printed and saved as a text file
Example is given in the next slide
Use this information to compare between 2 sites and

more
Save & send this file to your local support engineer

1/25/2010
Configuration Report
Uploading the Configuration File
Backup your IDU by uploading and

storing a copy of your CFG file
You may download this file onto your

IDU in your simulation lab
You may also send this file to your local

support engineer

1/25/2010
Downloading the Configuration File
When download completes, you will be asked to restart your IDC
Saving the Unit Information File
Why & When:
• Backup
• Contacting your Support
• Maintenance
• Troubleshooting
Where?
C:\Program Files\CeraView\logs\log_192.168.1.20_04_Jan_10_10_22

1/25/2010
Software Download
Before you commence the process, verify TFTP is configured
Configuring TFTP is located in the CeraView Configuration

Application (utility):
Start / Program Files / ceraView Configuration
Or –
C:\Program Files \ CeraView
Username: admin
Password: ceragon
Software Download – configuring TFTP

1/25/2010
Software Download
After completing the TFTP
configuration, restart your CV sessions
and proceed with the SW download
1. You may download a single file

package (SFD) or individual files
per component (when relevant)
2. You may initiate an auto-reset or

manually reset the IDU
Software Download
1. Select the SFD SW package
2. SFD is selected
You can select more than one file for the Firmware (MUX), Firmware (Modem), and Configuration (Modem) fields.
This is done by holding down the Shift or Ctrl button.
3. You may chose to reset the IDC automatically when download completes
4. File download begins….

1/25/2010
Software Download
5. When Download completes – the IDC will restart automatically (when feature enabled)
6. When IDC completes the reset – the download log shows IDC is up again:
7. Check versions to verify SW download was successful.
Launching another CV session / remote session

1/25/2010
Thank you!

1/25/2010
IP-MAX^2 CeraView EMS

Configuration
Agenda
1. External Alarms
2. Auxiliary channel – WSC, UC, EOW
3. MRMC – modulation, XPIC & channel BW
4. ACM – fixed, adaptive
5. Radio link – FQ, RSL, TSL & ATPC
6. The Radio interface – BER & Link ID settings
7. The GbE interface – QoS and PHY settings
8. The TDM interface
9. Management – reading IP, setting subnet
10. Management – setting In-Band / OOB
11. Management – setting SNMP
12. Management – setting NTP
13. Management – setting Trap Destinations
14. Management – enabling Neighbors reports

1/25/2010
External Alarms: 5 in, 1 out
External Alarms: 5 in, 1 out
Output Type: Input Severity: The microcontroller in the IDU reads alarm inputs (dry contact) and
• Critical • Critical transmits them to the CeraView management system. This allows
• Major • Major FibeAir to report external alarms that are not related to its own system.
• Minor • Minor
• Warning • Warning
• External • Event The alarm outputs are Form C Relays. Each output relay provides
• Power three pins, as follows:
• BER Normally Open (NO), Normally Closed (NC), Common (C).
• Line
Select the output alarm type (Major, Minor, Warning, External, Power,
• Loopback
etc.). The default for all relays is "Power".
• LOF
• IDU The relays may be connected to customer-specific applications.
• RFU
• Cable
• Remote
• Test on
• Off

1/25/2010
Auxiliary Channel
Configure here:
• EOW – 64Kbps
• Wayside channel per IDM -2Mbps
• User channel per IDM- 64Kbps
• When using WSC to transport out of

band packets, prior to enabling WSC,
make sure In-Band is disabled
MRMC
MRMC allows you setting:
• Occupied BW
• Modulation

1/25/2010
ACM – adaptive mode
• Minimum constellation
• Maximum constellation
• ACM requires license
ACM – fixed mode

1/25/2010
Radio Link Configuration
Access configuration
window using main menu
or Quick Access Button
Left & Right IDMs require

individual settings
ODU FQ range
Settings FQ according to standard channel

spacing (when available)
TX & RX frequencies
When link is up you may change the link

settings (local & remote)
TSL & ATPC settings,

RSL reading

1/25/2010
When link is up, link status becomes green
Configuring the Radio interface
For Latency Type, select High if you want

the ATM and channel interleavers to be
active.
Select Low to bypass the interleavers.
If you select Low, the latency of the link will

be lower than the high latency by 50-200
Note: If you change the latency value and mSecs (depending on the modem
click Apply, you will be prompted to reset Fsymbol), and the system gain will be
the drawer you were configuring. approximately 0.2 dB lower.

1/25/2010
Configuring the Radio interface – The Interleaver
Interleaver off (low latency) – bulk data transport, higher risk of loss
Interleaver on (high latency) – data is inteleaved to avoid mass losses
Configuring the GbE interface

1/25/2010

Select Enabled to activate the channel.
Tx Mute Criteria:
Excessive BER
If the excessive BER threshold of the radio is exceeded, the
local GbE output will be muted. The excessive BER threshold is
set in the Radio Configuration window (menu: Configuration,
Local/Remote, Interfaces, Radio).
Signal Degrade
If the signal degrade BER threshold of the radio is exceeded,
the local GbE output will be muted. The signal degrade BER
threshold is set in the Radio Configuration window (menu:
Configuration, Local/Remote, Interfaces, Radio).
Remote Fault
If the remote GbE input is lost (GbE loss of carrier is detected
at the remote end) or there is a radio fault at the remote end
(LOF, EBER - if configured), SD - if configured), the local GbE
output will be muted.
Speed and Duplex (for an SFP interface):

Select either Auto Negotiation, to allow the system to
control the flow of data, or 1000 Mb/s Full Duplex.
Flow Control:
Select Pause-Frames Generating if you want the system
to send a "pause" signal to the transmission source so that
it will stop sending packets and enable the flow of packets
to proceed at a manageable pace.
Select Pause-Frames Forwarding if you want the system

to allow a "pause" signal to pass through directly to the
transmission source, to cause the source to stop sending
packets.
Note that when Pause-Frames Generating is enabled on

the local side, Pause-Frames Forwarding must be disabled
on the remote side, and vice versa (when Pause-Frames
Forwarding is enabled on the local side, Pause-Frames
Generating must be disabled on the remote side).

1/25/2010
Configuring the GbE interface - QoS
Queues 1 - 4

The system will examine the incoming traffic and give
the priority according to the marking of the packets
(based on the user L2/L3 marking in the packet).
In case of congestion in the ingress port, low priority

packets will be discarded first.
First priority is given by default to Ethernet

management frames.
Ethernet management frames include Spanning Tree

BPDU packets and the following destination address:
0180C2000000-0180C200002F and 01000CCCCCCD

which are used by Cisco proprietary STP.

1/25/2010

Configuration options:
• UDP frames – first priority to UDP frames
• VLAN ID – up to 20 ranges of VLAN ID. Each range can have

1 to 4096 VLANs.
• VLAN priority bits (802.1p) – as there are 4 queues, 6&7 are

first priority, 4&5 second, 2&3 third and 0&1 forth.
• IPv4 TOS / IPv6 TC IP precedence bits – as there are 4

queues, 6&7 are first priority, 4&5 second, 2&3 third and 0&1
forth.
• MPLS EXP – Priority according to Experimental bits on MPLS

label (6&7 are first priority, 4&5 second, 2&3 third and 0&1
forth).
• Priority of tagged bits – if the frame is tagged, use VLAN

priority bits, if not, use TOS/TC/EXP bits.

In the Quality of Service window Third Rule area,
select the traffic type that you want to give precedence
to after the first and second rule traffic types.
In the Scheduler area, select the queuing scheme:
Strict Priority is an algorithm used to ensure that a queue with a

higher priority is always served before a queue with a lower priority.
Hierarchical Round Robin is a dynamic scheduling method that

provides fair bandwidth allocation to all network traffic. The method
applies priority or weights to identified traffic, to classify traffic into
conversations and determine how much bandwidth each
conversation is allowed relative to other conversations. The
algorithm is flow-based, simultaneously scheduling interactive traffic
to the front of a queue to reduce response time and evenly share
the remaining bandwidth among high-bandwidth flows.
If you select Hierarchical Round Robin, you can assign a strict

schedule to the first queue by selecting the Strict option.

1/25/2010
Configuring the TDM interface
Management – IP Address
CV does allow changing the IP – to do

so, you will need to use the serial
connection (CLI)

1/25/2010
Management – In Band / OOB
This step is explained in a different

module
Please see “IP-MAX MNG”

presentation for further information
Management – SNMP

1/25/2010
Management – NTP
Management – Trap Destination

1/25/2010
Management – Neighbors
Management – Neighbors
The Neighbors window shown above lists all STM-1 interfaces (radio, line, trib) and their
remote connections.
For 2 x Fast Ethernet or 1 to 3 x DS3/E3 interfaces, the appropriate name (such as: Right
DS3 #1, Left Fast Ethernet, etc.) will appear in the Interface column.
Note: A Fast Ethernet or DS3/E3 interface can connect only to another Fast Ethernet or
DS3/E3 interface.
Select Manual in the Detect Mode column to enter the unit's IP address manually.
When you enter an IP address, CeraView will try to connect to the unit and learn the
Neighbor Type and Interface.
If the IP address you entered is not configured or not able to be reached, the Neighbor
Type field will display “Unknown”, and the Neighbor Interface field will list all available
options than can be configured.

1/25/2010
Thank you!

1/25/2010
IP-MAX CeraView EMS

Performance
Agenda
1. Reading CAS
2. Reading the Alarm Log
3. PM – using Thresholds
4. Reading Radio PM
5. Reading Line PM
6. IDC LEDs

1/25/2010
CAS
To display the current alarms you may

click on the Bell (Quick access button) or
navigate your way through the command
main menu
CAS – sorting & backing up info
You may save current info for

future analysis
By clicking on each tab, you

may sort the information:
• According to time of registry

• According to severity
• According to origin
• According to description

1/25/2010
CAS – Quick access to Top Most Alarm
The Bell icon on the right

side of the IDU allows you
faster reading of IDU’s status
Just by moving the cursor over the icon the CV EMS displays the top most alarm in the
system. Clicking on the Bell icon will launch the CAS window with alarms sorted
according to severity.
Alarm Log
The internal log file is intended to help
troubleshooting problems in the field, without
performing actions that will cause traffic interruptions
The log file contains a list of IDM and RFU

parameters which values are continuously saved in
each IDM (max. 100 lines), thus providing constant
system monitoring
To display the alarm log you may click on the Quick

access button or navigate your way through the
command main menu
To log more than 100 lines per IDM, user is advised

to maintain an external log file (see following slides)

1/25/2010
Alarm Log
Filtering alarms
by severity
Sorting by
column
Click here save the current log file
Alarm Log – Maintaining an external log file
To log more than 100 lines per IDM, user

is advised to maintain an external log file

1/25/2010
Performance
In the following slides we shall examine how PM data is

collected and displayed in the CV EMS
Such information can be used to better analyze the link

performance & stability
Performance – using thresholds
RSL
-40
In this example we set:
1st threshold = -50 dBm

-50
2nd threshold = -68 dBm
-68
-99 T [sec] RSL threshold readings:

10 5 10
Level 1: 25 sec
Level 2: 15 sec
When your RSL vary dramatically, you may set threshold

flags to trigger time counting whenever it falls below the
THSLD value
You may implement this mechanism on TSL & MSE as well

1/25/2010
Performance – Radio – RSL

Time Elapsed is the
current interval in seconds.
The value can be between
0 and 900 (15 minutes).
Current MSE is the Mean

Square Error value, which
quantifies the performance
of the receiver. The value
should be less than -33 dB.
Current XPI is the Cross

Polarization Interference
value which represents the
difference in signal
strengths between the
main and cross channels in
an XPIC link. The value
should be greater than 25
dB.
Performance – Radio – RSL

Doubtful values are values
that were not generated
during normal system
operation.
For example, the values

may have been generated
during a system reset or
failure.
Unfaded RSL is the

theoretical expected RSL
value (not the actual
value), which can be
calculated by the user (as
a function of distance,
frequency, etc.).
The value is used only for

reference purposes.

1/25/2010
Performance – Radio – RSL – History

The Integrity column
indicates whether or not
the values received at
that time and date are
reliable.
A red x in the column

indicates that the values
are not reliable due to a
possible power surge or
power failure that
occurred at that time.
The values in this column

are indicated in the graph
as "Doubtful" (red)
values.
Performance – Radio – TSL

1/25/2010
Performance – Radio – TSL – History
Performance – Radio – ACM

1/25/2010
Performance – Radio – Aggregate

UAS is the Unavailable
Seconds value of the current
interval. The value can be
between 0 and 900 seconds
(15 minutes).
ES is the number of seconds

during which errors occurred.
SES is the number of severely

errored seconds.
BBE is the number of

background block errors.
OFS is the number of out-of-

frame seconds.
Performance – Tributary

1/25/2010
Performance – Ethernet - Monitoring
The Gigabit Ethernet monitoring

window displays Ethernet-related
values measured every 15 minutes,
over the last 24 hours.
Performance – Ethernet – Statistics

1/25/2010
IDC LEDs
LED name Indication Severity
Green - valid signal (when the Wayside channel is supported in
-----
hardware)
CH1 (HW
activated) Red - LOS in line Major
Gray - interface is not supported, or Wayside channel is
-----
disabled
CH2 (HW Green or blinking green - active signal -----
activated) Gray - no link or no cable -----
Green - IDC OK
Yellow - configuration/firmware
IDC Warning
mismatch, or fan failure
Red - hardware failure in IDC module Major
Red - major alarm in one or both of the remote drawers

Major
Red - local remote communication error
Green – OK -----
RMT
Yellow - minor alarm in one or both of the remote drawers. (If
there are both minor and major alarms in the remote, the LED
Minor
will be red indicating the worst alarm)
Yellow - fan failure in the remote
Green - protection cable OK -----
Prot Red - protection cable failure Minor
Gray - protection disabled -----
IDM Main LEDs

IDM LEDs:
• Drawer
• ODU
• CBL
• LPBK
• RADIO
• GbE
•8xE1
LED name Indication Severity
Green - drawer OK -----
Drawer Yellow - drawer in standby mode -----
Red - drawer hardware failure Major
Green - ODU OK -----
ODU
All LEDs should be green when Red - ODU failure Major
system is operational Red - cable open Major
CBL Red - cable short Major
Green - OK -----
Green - OK -----
LPBK
Red - loopback in progress Major
Green - OK -----
Radio Red - LOF/EXC Major
Yellow - SD Minor
Gray – Port is disabled -----
GbE / E1 Green – Port is enabled, link is up -----
Red – Port is enabled, LOC Major

1/25/2010
Thank you!

1/25/2010
IP-MAX CeraView EMS

Maintenance
Agenda

1/25/2010
Loopbacks
To display the Loopback options you may click

on the Quick access buttons or navigate your
way through the command main menu
Loopbacks
1. RF link is up but data link is down (GUI)
2. Transmitters maintain transmission – Link LED is ON
3. Loopbacks can be limited by a timer RFU loopback

4. Clear counter when LBs are set
Line loopback
towards Radio
Link
IF loopback
Line loopback
towards line (DDF)
Defective Blocks shows the number of modem-

generated defective blocks that were received

1/25/2010
PRBS (Pseudo-Random-Binary-Sequence) test
The PRBS test is designed for maintenance testing of a radio link.
When the test is activated, the local modem sends a pseudo-random-binary-sequence

to the remote side, and the quality of the link can be evaluated based on the amount of
defective blocks detected by the remote (receiving) modem (the larger the amount is,
the poorer the radio link quality).
PRBS should be enabled on local IDM with loop on remote line interface (remote IDM)
PRBS (Pseudo-Random-Binary-Sequence) test
To perform a PRBS test, do the following:

1. If you prefer not to interrupt traffic, transmit the tested carrier over the protecting channel, and lock
the MUX to its mate input.
2. Activate the PRBS test in the local IDM (a warning will appear informing you of traffic interruption).
3. Reset the defective block counter in the same carrier in the remote IDM. This will start the
counting from zero.
4. Wait for x hours/days depending on the required test time.
5. Check the resulting amount of defective blocks. The value indicates the quality of the link.
6. Stop the test, unlock the MUX, and change the cross-connect back to its previous configuration.
Note that upon activating the test, a PRBS alarm will be raised in the local IDU. In addition, if you did
not perform step 1 above, an LOF alarm will be raised in the remote drawer until the test is stopped.

1/25/2010
Built-in test
The system supports Ethernet Built In test.
The built in test is traffic affecting and cannot run during live traffic.
Loopback must be applied on the line using fiber and on the radio using IF-LB, RF-LP or
fiber on the remote side.
After the test is enabled, the system counts the number of seconds on which at least
one Ethernet frame that the system transmitted to the radio did not received on the line.
IDC SW Reset

1/25/2010
HW Reset
PM Clearance

1/25/2010
Setting Default Configuration
Hard reset required
Copy configuration
Some scenarios require exact settings on all IDMs. Such scenarios include Protection
and Multi Radio where exact configuration should be applied to all 4 IDMs in the link.

1/25/2010
Temporary License
Temp. License allows 30 days of temporary of feature evaluation. The user can
configure the system to any capacity/configuration.
The temporary license 30 days period is accumulative and the timer runs only when
this feature is enabled and the IDM is powered on.
The purpose of the feature is to allow users to test their requested configuration before
purchasing a permanent license and offer an interim solution if IDM is replaced.
Temporary License
An alarm is raised and a timer of the remaining hours is shown on the Ceraview
main display while the function is enabled.
Once enabled, all MRMCs are showed on the MRMC window and the user can
choose any MRMC and ACM adaptive mode will be available.
Once permanent license is installed for operative MRMC, temporary license will be
disabled automatically.
If the temporary license is disabled or the 30 days period expires, the IDM will
reboot automatically and will come up with the original MRMC and radio mode that
was active before it was enabled.

1/25/2010
TSL remote settings
Disabling Remote Muting (Remote Mute Off)

1/25/2010
Thank you!

1/25/2010
IP-MAX CeraView EMS

Protection
Agenda
1. Introduction (guidelines)
2. Protection Configurations
3. EMS configuration

1/25/2010
Introduction
• The system can be configured to support internal or external

protection to provide line and radio protection.
• IDC and backplane are not protected.
• Faulty MUX or missing IDM will disable protection switching over
• Internal Protection - 2 IDMs are required per IDU
• External Protection – 2 IDUs are required
Protection
Configurations

1/25/2010
1+0 No protection
1+1 Internal protection (HSB)
HSB performed by MUXes

1/25/2010
Diversity (Hitless switchover)

• Space Diversity (2 Antennas)
• Frequency Diversity (single antenna)
Space Diversity:
IFC (using 1500HP) – outdoor unit accommodates 2 receivers and sends only single IF
towards IDU
BB switchover – IDU is equipped with 2 IDMs - each modem analyses FEC & MSE for
triggering the switchover
Frequency Diversity

1/25/2010
2+0 XPIC
V
H
XPIC
Multi Radio with Line Protection

1/25/2010
EMS
Configuration
Setting protection mode
Your options are:

1/25/2010
Displaying Protection State
When you enable protection, new icons are added to the right
side of the IDU (shields)
• Grey shield represents a standby IDM

• Gold shield represents an active IDM
• Gold shield with a key represents an active unit in a lock state
H/W Protection Configuration
Your next step would be setting the trigger to a

switchover:
1. Radio Line Loss of Frame (on by default)

2. Radio Excessive BER
3. Radio SD
4. External input alarm #5

1/25/2010
Copying configuration from active to standby IDM
When you complete configuring your active IDM, the next step would be copying the
CFG to the standby IDM (Mate)
Requesting a switchover
User may trigger a manual switchover request.
However, if the mate IDM / IDU encounters sever errors (LOS, LOF) the switchover
will not take place.

1/25/2010
Forced Switchover
To ignore Mate’s qualification state, we can simply force a switchover
Switchover Lockout
If you wish to lock current state, you may do so using this command.
If active IDM is locked, a switchover will not take place (forced or manual).

1/25/2010
Diversity Configuration
Here you may configure –
Diversity options:
Space Diversity
Frequency Diversity
Revertive Mode:
On / Off
Hold off time before switching back
Diversity Commands
When Diversity is enabled (FD or SD), user may trigger manual switchover or lock
current status.

1/25/2010
Thank you!

IP-MAX GbE Course Handbook v1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IP-MAX GbE Course Handbook v1.0

Uploaded by

Copyright:

Available Formats

Ceragon Training Center

Page 1 Ceragon Training Center

Course: Operation and Maintenance

• Physical Installation of IDU + ODU

Preliminary Commissioning (using CV EMS):

• Logging in to the CV EMS

1 Ceragon Training Agenda v2.2

Page 2 Ceragon Training Center

• Reading Current Alarms

Troubleshooting Tools & Maintenance:

Protection: Practical Exercises

Exam / Course Summary

2 Ceragon Training Agenda v2.2

Page 3 Ceragon Training Center

Ceragon Networks proprietary and confidential

1 Page 4 Ceragon Training Center

Strong economic value with pay-as-you-grow concept to Reduce

Optimize each network nodes for today’s deployments

Network versatility - seamless integration into multiple networks

Enables future growth capacity as needed

Ceragon Networks proprietary and confidential

FibeAir IP-MAX Advantages

Ceragon Networks proprietary and confidential

2 Page 5 Ceragon Training Center

IDM - In Door Module: IDM - In Door Module:

Ceragon Networks proprietary and confidential

FibeAir IP-MAX Power Consumption

Only IDU IDC + Drawer_A 0.66 31.68

RFU+IDU drawerA: RFU HP+IDC+DrawerA 2.7 129.6

Ceragon Networks proprietary and confidential

3 Page 6 Ceragon Training Center

Ceragon Networks proprietary and confidential

• East and West

Simple migration path to higher capacities

Ceragon Networks proprietary and confidential

4 Page 7 Ceragon Training Center

Fast recovery time to support RSTP

Highest priority level for BPDU packets

TDM voice transmission with dynamic allocation

Built in layer 2 switch, provides fast Ethernet traffic aggregation

QoS support - by port / VLAN 802.1p / DiffServ (packet queuing and

Ceragon Networks proprietary and confidential

FibeAir IP-Max Solutions

GbE + 8xE1 IDM

1, 2xFE + 8xE1 IDM

Ceragon Networks proprietary and confidential

5 Page 8 Ceragon Training Center

IPS - IDU power supply

IDC 2x64K/2M 10BaseT

Ceragon Networks proprietary and confidential

Fast Ethernet System

8xE1/T1 2xFE 8xE1/T1 2xFE

Ceragon Networks proprietary and confidential

6 Page 9 Ceragon Training Center

FE wireless connectivity for IP networks @ 6-38 GHz

Ceragon Networks proprietary and confidential

IDM – In Door Module

Two independent IDMs per IDU

Ceragon Networks proprietary and confidential

7 Page 10 Ceragon Training Center

SFP IDM and 10/100/1000 can work across a link or as 2+0.

Ceragon Networks proprietary and confidential

8 Page 11 Ceragon Training Center