XpandIP+ Basic Course

Evo XPAND IP+ Introduction
I6.8
XPAND IP+
Functional Block Diagram
OA&M ServiceManagementSecurity
PWE3
CarrierEthernetSwitch (CESoP/SAToP
TDMCrossConnect
)
Gigabit ACM XPIC ChSTM1/

Ethernet Fast NativePacketRadio Multi OC3
Ethernet (OptionalNativeTDM) ChannelABC
E1/
(Opticalor DS1 Terminal
Electrical) 10Mbps1Gbps,3.556MHz Mux
Diversity
ODU(638GHz)
Proprietary and Confidential

2
Main features
Unique Adaptive Coding & Modulation (ACM)

Enhanced radio efficiency and capacity for Ethernet traffic
Integrated Carrier Ethernet switching functionality
Enhanced QoS for differentiated services
Supported configurations
1+0
1+1 HSB Fully-redundant!
Nodal solution with ring
2+2 HSB
XPIC
Multi Channel ABC
Space Diversity
Extensive and secure management solution
3
Integrated Carrier Ethernet switch
3 modes for Ethernet switching:
Metro Switch Carrier Ethernet switching is enabled
Managed Switch 802.1 L2 switch
Single 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
XPAND IP+ XPAND IP+
Ethernet Ethernet
Radio Radio
User interface User interface
Interfaces Interface
Carrier Ethernet
Switch
Metro/Managed switch mode Smart pipe mode
Extensive Carrier Ethernet feature-se eliminates the need for external switches
4
Radio capacity - ETSI
7MHz 14MHz
Ethernet Ethernet
ACM # of ACM # of
Modulation Capacity Modulation Capacity
Point E1s Point E1s
(Mbps) (Mbps)
1 QPSK 4 9.5 13.5 1 QPSK 8 20 - 29
2 8 PSK 6 14 20 2 8 PSK 12 29 41
3 16 QAM 8 19 28 3 16 QAM 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 33 47 6 128 QAM 29 69 98
7 256 QAM 16 38 55 7 256 QAM 34 81 115
8 256 QAM 17 40 57 8 256 QAM 37 87 125
28MHz 40MHz 56MHz
Ethernet Ethernet Ethernet
ACM # of ACM # of ACM # of
Modulation Capacity Modulation Capacity Modulation Capacity
Point E1s Point E1s Point E1s
(Mbps) (Mbps) (Mbps)
1 QPSK 17 40 58 1 QPSK 23 56 - 80 1 QPSK 32 76 - 109
2 8 PSK 23 54 78 2 8 PSK 35 83 - 119 2 8 PSK 48 114 - 163
3 16 QAM 33 78 111 3 16 QAM 51 122 174 3 16 QAM 64 151 - 217
4 32 QAM 44 105 151 4 32 QAM 65 153 - 218 4 32 QAM 84 202 - 288
5 64 QAM 55 131 188 5 64 QAM 81 191 274 5 64 QAM 84 251 - 358
6 128 QAM 68 160 229 6 128 QAM 84 214 305 6 128 QAM 84 301 - 430
7 256 QAM 76 178 255 7 256 QAM 84 243 347 7 256 QAM 84 343 490
8 256 QAM 80 188 268 8 256 QAM 84 259 370 8 256 QAM 84 372 - 532
5
Wireless Carrier Ethernet Ring
Example configuration (1+0 ring)
6
Native2 Microwave Radio Technology
At the heart of the XPAND IP+ solution is Nera's market-leading Native2
microwave technology.
With this technology, the microwave carrier supports native IP/Ethernet
traffic together with optional native PDH.
Neither traffic type is mapped over the other, while both dynamically share
the same overall bandwidth.
This unique approach allows you to plan and build optimal all-IP or hybrid
TDM-IP backhaul networks which make it ideal for any RAN (Radio Access
Network)
Native
In addition, Native2 ensures:
Very low link latency of <0.15 msecs @ 400 Mbps.
Very low overhead mapping for both ETH & TDM traffic
High precision native TDM synchronization distribution
7
NG-SDH/SONET complementary solution
Carrier Ethernet at the access, NG-SDH/SONET at the aggregation
Carrier Ethernet (MW links) SDH/SONET (Hybrid Fiber/MW)
Native Ethernet
Ethernet over SDH/SONET
Hub
GE
Site
FE/GE RNC
GE
IP+
Tail site IP+ NG-SDH
NG-SDH MSPP
MSPP
Core
Site
Ethernet
Ethernet services
services areare NG-SDH/SONET
NG-SDH/SONET MSPP MSPP
transported natively
transported natively node acts as gateway
node acts as gateway SDH/SONET
SDH/SONET MW MW
Ethernet
Ethernet services
services
over
over Carrier
Carrier Ethernet
Ethernet between
between the
the Carrier
Carrier links
links are
are used
used where
where
are
are mapped
mapped over
over
based
based MW radio links.
MW radio links. Ethernet
Ethernet and
and NG-
NG- fiber
fiber connections not
connections not
SDH/SONET
SDH/SONET
SDH/SONET based
SDH/SONET based available
available
networks.
networks.
8
IP/MPLS complementary solution
Carrier Ethernet at the access, IP/MPLS at the aggregation
Carrier Ethernet (MW links) IP/MPLS (Hybrid Fiber/MW)
Native Ethernet
Ethernet PWs or IP routing
Hub
GE
Site
FE/GE RNC
GE
IP+
Tail site IP+ MPLS
MPLS Router
Router
Core
Site
Ethernet IP/MPLS edge router

Ethernet services
services areare
transported natively acts as gateway between Both
Both Ethernet
Ethernet and
and
transported natively
over the Carrier Ethernet and E1/T1
E1/T1 services are
services are
over Carrier
Carrier Ethernet
Ethernet High-capacity
High-capacity IP/MPLS-
IP/MPLS-
based IP/MPLS based mapped
mapped over
over MPLS
MPLS
based MW radio links.
MW radio links. aware"
aware" Ethernet
Ethernet MW
MW
networks. using
using pseudo-wires
pseudo-wires
radio
radio is
is used
used where
where fiber
fiber
or
or routed using
routed using IP
IP
connections not available
connections not available
9
Integrated QoS support - overview
4 CoS/priority queues per switch port
Advanced CoS/priority classification based
on L2/L3 header fields:
Priority Queues
Source Port
VLAN 802.1p W1 - Highest priority
VLAN ID
Classify Scheduling
IPv4 DSCP/TOS, IPv6 TC Arrivals W2 departures
Highest priority to BPDUs
Advanced ingress traffic rate-limiting W3
per CoS/priority
Flexible scheduling scheme per port
Strict priority (SP)
W4 lowest priority
Weighted Round Robin (WRR)
Hybrid any combination of SP & WRR
Shaping per port
Support differentiated Ethernet services
with SLA assurance
10
XPAND IP+ Enhanced QoS
Ultra-low delay variation
Dedicated channel for ultra Low Delay Variation (<20sec)
Sync over packet optimized transport
IEEE-1588/NTP
control frames
Latency Optimized
Radio link
QoS
Classifier
More granular service

classification
Multi-Layer MPLS-aware
QoS Classifier
High granularity traffic management

Improved utilization of TCP Hierarchical scheduling
8 Queues
flows CIR + EIR support 4 priorities
Intelligent congestion Per queue statistics WFQ within the same priority
management (WRED) Shaping per queue and per port
Enables differentiated services with strict SLA

and maximizing network resources utilization
11
IEEE 802.1ag CFM (Connectivity Fault Management)

A Nodal Solution
13
XPAND IP+ Integrated Nodal Solution
y Same 1RU XPAND IP+ unit can be used

for terminal and nodal solution
y The solution is stackable and modular
y Forms a single unified nodal device

y Common Ethernet Switch
y Common E1/DS1s Cross Connect
y Single IP address
y Single element to manage
14
XPAND IP+ (R3)
Hardware update for XPAND IP+
Same interfaces and architecture as the current IP+ (R2) design
Supports enhanced functionality, most notably:
Full SyncE support including SyncE regenerator for smart pipe
applications
Multi-Layer header compression
Payload compression
QoS and latency enhancements
Full compatibility with XPAND IP+ (R2)

Fully compatible with current IP+ (R2) install base
R3 and R2 can be used in the same node and in the same link
Same software version and configuration file
R3 is supported in SW version i6.7 and above
15
Thank You
Introduction to Radio
Agenda
RF Principals
Parameters Affecting Propagation
Atmospheric Refraction
Multipath
Duct
Rain Fading
Fresnel
RF Link Basic Components

Link Calculation
Modulation
2
RF Principals
A Radio Link requires two end stations

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

Easier installation
Faster installation
Cheaper installation
Easier maintenance
4
RF Principals
RF - System of communication employing electromagnetic waves (EMW)

propagated through space
EMW travel at the speed of light (300,000 km/s)
The wave length is determined by the frequency as follows -
c where c is the propagation velocity of electromagnetic
Wave Length =
f waves in vacuum (3x108 m/s)
Microwave refers to very short waves (millimeters) and typically relates to
frequencies above 1GHz:
300 MHz ~ 1 meter
10 GHz ~ 3 cm
5
Polarization and Rain
Raindrops have sizes ranging from 0.1 millimeters to 9 millimeters mean

diameter (above that they tend to break up)
Smaller drops are called cloud droplets, and their shape is spherical.
As a raindrop increases in
size, its shape becomes more
oblate, with its largest
cross-section facing the
oncoming airflow.
Large rain drops become

Increasingly flattened on the
Bottom;
very large ones are shaped
like parachutes
6
RF Principals
We can see the relationship between colour, wavelength and amplitude using
this animation
7
Radio spectrum
8
Dispersion
Humidity/gas absorption
Multipath/ducting
Atmospheric conditions (refraction)
Terrain (flatness, type, Fresnel zone clearance, diffraction)
Climatic conditions (rain zone, temperature)
Rain attenuation
9
Dispersion
Electromagnetic signal propagating in a physical medium is degraded

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

High frequencies have shorter wavelength and refract more
10
Atmospheric Refraction
Deflection of the beam towards the ground due to different electrical

characteristics of the atmospheres is called Dielectric Constant.
The dielectric constant depends on pressure, temperature & humidity in the
atmosphere, parameters that are normally decrease with altitude
Since waves travel faster through thinner medium, the upper part of the wave
will travel faster than the lower part, causing the beam to bend downwards,
following the curve of earth
With Atmosphere
No Atmosphere
11
Multipath
Multipath occurs when there is more then one beam reaching the receiver
with different amplitude or phase
Multipath transmission is the main cause of fading in low frequencies
Direct beam
Delayed beam
12
Duct
Atmospheric duct refers to a horizontal layer in the lower atmosphere with vertical refractive
index gradients causing radio signals:
Remain within the duct
Follow the curvature of the Earth
Experience less attenuation in the ducts than they would if the ducts were not present
Duct Layer
Duct Layer
Terrain
13
Rain Fading
Refers to scenarios where signal is absorbed by rain, snow, ice

Absorption becomes significant factor above 11GHz
Signal quality degrades
Represented by dB/km parameter which is related the rain density
which represented mm/hr
Rain drops falls as flattened droplet
V better than H (more immune to rain fading)
14
Rain Fading
Heavier rain >> Heavier Atten.
Higher FQ >> Higher Attenuation
15
Fresnel Zone
3rd
2nd
1. EMW propagate in beams
1st RX
2. Some beams widen therefore, their path is longer
TX
3. A phase shift is introduced between the direct and indirect
beam
4. Thus, ring zones around the direct line are created
Duct Layer0
Terrain
16
Fresnel Zone
Note that there are many possible Fresnel zones, but we are chiefly concerned
with zone 1.
If this area were blocked by an obstruction, e.g. a tree or a building, the signal
arriving at the far end would be diminished.
When building wireless links, we therefore need to be sure that these zones are
kept free of obstructions.
In wireless networking the area containing about 40-60 percent of the first Fresnel
zone should be kept free.
3rd
2nd
1st RX
TX
17
Antennas
Antennas are devices used to radiate electromagnetic energy into space.
OMNI-DIRECTIONAL antennas radiate & receive energy from all directions

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

outward from the antenna.
The radiation pattern contains small minor lobes (weak with little effect on
the main radiation pattern)
18
Parabolic Reflector Radiation (antenna)
Microwaves travel in straight lines - it can be focused and reflected just as

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

surface, all paths from source to the reflector and
back to end user are the same length
19
Link Calculation Basic Example
Link Calculation
+Gant1 +Gant2
+Lfs
TX
IDU TX Losses RX Losses IDU RSL
RSL ReceivedSignalLevel
TSL TransmittedSignalLevel
Lfs Freespaceloss=92.45+20logx(distanceinkmxfrequencyinGHz)
RSL=TX TXLoss +GainAnt1 LFreeSpace +GainAnt2 RXLoss
20
Digital Modulation
Modulation
Modulation is used to transfer a message (voice, image, data, etc.) on to a

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

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

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

high fq. Carrier (down) =
22
QPSK Modulation
Quadrature Phase Shift Keying is a phase modulation algorithm
The phase of the carrier wave is modulated to encode bits of digital

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

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

seven bits generate 128 states, and so on
24
QPSK VS. QAM Modulation
ThevariousflavorsofQAMofferhigherdataratesthen8PSK
ThisisbecauseQAMachievesagreaterdistancebetweenadjacentpointsintheIQ
planebydistributingthepointsmoreevenly
Thepointsontheconstellationaremoredistinctanddataerrorsarereduced
Higherorder>>morebitspersymbol
Constellationpointsarecloser>>TXismoresusceptibletonoise
25
SNR and RSL Constellation
The higher the SNR, the better the received signal !
26
8QAM
Diagram for 8QAM: 3bit represent 8 different states
Bitsequence Amplitude Phase(degrees)

000 1/2 0(0)
000 1 0(0)
010 1/2 pi/2(90)
011 1 pi/2(90)
100 1/2 pi(180)
101 1 pi(180)
110 1/2 3pi/2(270)
111 1 3pi/2(270)
27
16QAM
Constellation diagram for 16QAM:

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

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

data rate
This is why we modulate
29
256QAM Modulation
Constellation of 256QAM with noise added Constellation of 256QAM
30
Thank You
XPAND IP+ Front Panel Description
Evo XPAND IP+ : IFU
Split-mount architecture
Fans
drawer
5 x FE
2 x GE combo
Electrical
Craft 16 x E1/DS1s ports
External (RJ45) Power
Terminal (optional) Electrical (RJ45)
Alarms GND
(DB9) Protection or Optical (SFP) ODU -48V DC
(DB9) User Interface interface
Engineering order- Channel (RJ45) (N-Type) (dual-feed
wire (optional) option)
(optional) (RJ45)
NeraProperiteryandconfidential
Front Panel Overview
GUI Example)
Lets go over the front panel connections of the XPAND IP+
Lets explain them one by one
CLI Serial Connection
DB9 Craft Line Interface (CLI)
Baud: 115200
Data bits: 8
Parity: None
Stop bits: 1
Flow Control: None
EOW Easy Comm. Via Radio
Engineering Order Wire
To communicate with your colleague on the

other side of the radio link, simply connect
here your headset
5
External Alarms
DB9 Dry Contact External Alarms

XPAND IP+ supports 5 input alarms and a single output alarm
The input alarms are configurable according to:

1) Intermediate, 2) Critical, 3) Major, 4) Minor and 5) Warning
The output alarm is configured according to predefined categories
LED Indications
LINK: GREEN radiolinkisoperational

ORANGE - minor BER alarm on radio
RED Lossofsignal,majorBERalarmonradio
PPR
LLII
OOD
RRM
IIFF
ROO
NNK
DUU
MT
UU
K
T
TT
IFU:GREEN IFUfunctionsok
ORANGE fanfailure
RED AlarmonIFU(allseverities)
ODU: GREEN ODUfunctionsok

ORANGE Lossofcommunication(IFUODU)
RED ODUFailure
LED Indications
PROT: Main unit GREEN (when there no alarms)

STBY unit: YELLOW (when there no alarms)
ORANGE Forced switch, Protection lock
RED physical errors (no cable, cable failure)
PPR
LLII
OOD
RRM
IIFF
ROO
NNK
OFF Protection is disabled, or not supported on

DUU
MT
UU
K
T
TT
device
RMT: GREEN remote unit OK (no alarms)

ORANGE minor alarm on remote unit
RED major alarm on remote unit
User Channels (1)
Two software-selectable user channels (RJ-45):
A single synchronous channel OR two asynchronous channels
Each asynchronous channel will make use of its own RJ-45 external
interface
The synchronous channel mode will make use of both interfaces

(acting as a single interface)
9
User Channels (2)
Modes of operation:
V.11 Asynchronous (9600bps)
RS-232 Asynchronous (9600bps)
V.11 Synchronous Co-Directional (64Kbps)
V.11 Synchronous Contra Directional (64Kbps)
User Channels (3)
Allowed configurations:
Two RS-232 Asynchronous UCs (default)

Two V.11 Asynchronous UCs
One RS-232 Asynchronous UC, and one V.11 Asynchronous UC
One V.11 Synchronous Co-Directional
One V.11 Synchronous Contra Directional UC
> All settings are copied to Mate when working in Protected mode
Protection Port
Protection Port (only for standalone units)
Protect your Main unit with a STBY unit
Protection ports on both units deliver the proprietary protocol to

support automatic or manual switchover
The FE protection port is static (only used for protection, not traffic). Its switching is performed
electrically. If the unit is a stand-alone, an external connection is made through the front panel. If the
unit is connected to a backplane, the connection is through the backplane, while the front panel port
is unused.
T-Cards (Add-on Mezzanines)
Field upgradeable modules (T-Cards):
16 x E1 T-Card (32 total per unit)

DS1 T-Card
STM1/OC3 MUX T-Card
T-Cards (Add-on Mezzanines)
An optional STM-1 interface card can be inserted in a dedicated slot in the

system; the card can transmit and receive up to 63 E1s in a channelized
STM-1 signal.
The supported mapping is VC4 only:

VC-12->TU-12->TUG-2->TUG-3->VC-4->AU-4->AUG
The STM-1 T-card is only supported in unprotected main units or in
unprotected stand-alone IFUs
GbE Ports
Two GbE ports, each port with 2 physical interfaces:
Port #1: optical (SFP transceiver) or electrical
Port #2: optical (SFP transceiver) or electrical
9 GbE ports support QoS as in IP-10 (scheduler, policers, shaper,

classifiers)
Port #1
Port #2
FE Ports
5 FE ports:
Port 3: Data
Port 4: Data or WSC (2 Mbps Wayside Channel)
Port 5,6 &7: Data or local management
9 All ports support QoS as in XPAND IP+ (scheduler, policers, shaper,

classifiers)
Radio and misc.
The Radio port is the switchs 8th port
In addition
Grounding
-48vdc Power Connector
Fan Drawer
XC using a Shelf Configuration
XC operation is implemented using two-unit backplanes, which

provide the interconnectivity.
Up to three backplanes, consisting of six IFUs, can be stacked to

provide an expandable system
XC using a Shelf Configuration
All IFUs that operate within
the XC system have
identical hardware, and act
as stand-alone units.
The 2 lower units can be configured as Main units.
The role an IFU plays is determined during installation by its position

in the traffic interconnection topology
XPAND IP+ : Ethernet only
Fans
drawer
Craft
External GND
Terminal ODU
Alarms
(DB9) interface Power
(DB9) Protection 2 x GE combo 5 x FE (N-Type) -48V DC
Interface ports Electrical (dual-feed option)
(RJ45) Electrical (RJ45) (RJ45)
or Optical (SFP)
Thank You
Installation
Agenda
Site Requirements
Packing & Transportation
Unpacking
Required Tools
IFU Dimensions
Installing standalone IFU in a 19 Rack
Installing Nodal Enclosures in a 19 Rack
Preparing the IFU for a Shelf installation
Installing the IFU in a Shelf
Installing a Blank Panel IFU in a Shelf
Installing a T-Card into an IFU
Grounding the IFU
Lightning Protection
Power General Requirements
Installing the IFU-ODU IF cable
2 Proprietary and Confidential

Site Requirements
IFU must be located indoors
The environment temperature must be between -5 C and +45 C.
Easily accessible, but only by authorized personnel.
Available power source of -48 VDC, and the site must comply with
National Electric Code (NEC) standards.
Available management connection (Ethernet or dial-up).

IFU-ODU connection (IF cable): no more than 300m

Site Requirements
Heat Dissipation:
The XPAND IP+ IFU overall heat dissipation is 25W max (~85 BTU/h).
The ODU heat dissipation is 100W max.
Antenna Location:
As with any type of construction, a local permit may be required before installing
an antenna. It is the owners responsibility to obtain any and all permits.

Packing & Transportation
The equipment is packed at the factory, and sealed moisture-absorbing bags

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

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

Unpacking
A single XPAND IP+ system (1+0) is shipped in 4 crates.
Upon delivery, make sure that the following items are included:
Two indoor units and accessories (if ordered)

Two outdoor units
For 13-38 GHz systems, verify that there is a high ODU and low ODU.
Unpack the contents and check for damaged or missing parts.

If any part is damaged or missing, contact your local distributor.

Required Tools and Materials
The following tools are required to install the IDU:
Crimping tool for IF cable

Crimping tool for ground cable lug crimping
(optional: if alternative grounding cable is used)
Philips screwdriver #2 (for mounting the IDU to the rack and grounding screw)
Flathead small screwdriver (for PSU connector)
Sharp cutting knife (for wire stripping)
Sealing Materials
Setting up Management will require -
ETH cable (for setting management)

Serial Cable (for setting management)

IDU Dimensions
0mm
7.8
18 43
5m
m
42.60mm

Installing standalone IDU in a 19 Rack
As shown in the illustration, four screws are used to secure

the IDU to the rack.


Before you install the

enclosures
Plan carefully the required

space within the rack !
Should you need to install 3

enclosures prepare at least
10Us (6Us for enclosures + 2Us free
space for maneuvering above and below
Main Enclosure shelves)
Start the installation process

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

Step #1:
Install the XPAND IP+ Main
enclosure in the 19 inch rack
using 4 screws.

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

Step #1:
using 4 screws.
Step #2:
should plug in smoothly into the
Main enclosure.
Step #3:
should be plugged in smoothly
into the Main enclosure.

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

rack using the 4 screws

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

into the rack using the 4
screws
Step #5:
Add the 3rd extension
when needed

Preparing the IFU for a Shelf installation
Remove the two 19" brackets mounted on the XPAND IP+ IFU by unscrewing
the 3 screws at each side and replace with brackets supplied with enclosure.

Installing the IFU in a Shelf
Slide the XPAND IP+ IFU into the enclosure and tighten it using 2 screws.
Repeat this step in accordance with the configuration.
IFU insertion & extraction

should NOT be under power

Installing a Blank Panel IFU in a Shelf
Slide the XPAND IP+ blank panel into the enclosure, and tighten it using 2
screws.

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

Insert the XPAND IP+ T-Card panel and tighten it using the 2 side screws.

Grounding the IFU
Single Point Stud
Grounding Wire

Grounding the IDU
The IFU is suitable for installation in a Common Bonding Network (CBN).
Only copper wire should be used.
The wire must be at least 14 AWG.
Connector and connection surfaces must be plated. Bare conductors must be

coated with antioxidant before crimp connections are made to the screws.
Equipment provides a ground for each IFU, via a one-hole mounted lug onto a
single-point stud.
The stud must be installed using a UL-listed ring tongue terminal, and two star
washers for anti-rotation.

Lightning Protection
For antenna ports, lightning protection is used

that does not permit transients of a greater
magnitude than the following:
Open Circuit: 1.2-50us 600V

Short Circuit: 8-20us 300A
The ampacity of the conductor connecting the

IFU frame to the DC return conductor is equal to
or greater than, the ampacity of the associated DC return conductor.

Power General Requirements
1. A readily accessible Listed branch circuit over-current protective device,

rated 15 A, must be incorporated in the building wiring.
2. This equipment is designed to permit connection between the earthed

conductor of the DC supply circuit and the earthing conductor at the
equipment.
3. The equipment shall be connected to a properly grounded supply system
4. The DC supply system is to be local, i.e. within the same premises as the
equipment
5. A disconnect device is not allowed in the grounded circuit between the DC

supply source and the frame/grounded circuit connection.

Power Requirements
When selecting a power source, the following must be considered:
DC power can be from -40.5 VDC to -57.5 VDC.
Recommended: Availability of a UPS (Uninterrupted Power Source),

battery backup, and emergency power generator.
Whether or not the power source provides constant power (i.e., power is
secured on weekends or is shut off frequently and consistently).
The power supply must have grounding points on the AC and DC sides.
The user power supply GND must be connected to the positive pole in the IFU
power supply.
Any other connection may cause damage to the system!

Power Requirements
Important
Make sure to use a circuit breaker to protect the circuit from damage by
short or overload.

Dual DC Feed
In boards with dual DC feed hardware, the system will indicate whether received
voltage in each connector is above or below the threshold power (40.5v
approximately).
This will be shown in two ways:

1.The LED (and its WEB representation) will only be ON if the voltage is above
the threshold
2.If voltage is below the threshold an alarm will be raised
User may configure the system not to raise an alarm in case of under-voltage
for any of the supplies.
This is used for cases where the dual feed hardware is used, but in the
installation only one of them is actually connected, so that no alarm is
permanently raised.

Installing the IFU-ODU IF cable
Route the IF Coax Cable from the IDU to the ODU and terminate it with N-
type male connectors.
Note: Make sure you fasten the cable along the ladder!
Make sure that the inner pin of the connector does not exceed the
edge of the connector.
The cable should have a maximum attenuation of 30 dB at 350 MHz.

Thank You
EMS General Configuration
I6.8
Agenda
In this module we shall explain the following

features as they appear on the EMS
navigation Menu

Menus
Menu of a Main unit
Menu of an Extension

Unit Parameters Step # 1
Configure specific
information that may
assist you later
Such info will help you

locate your site easier
and faster

VDC reading

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)

IDU Serial number is

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

configuring all
settings, click Apply.

External Alarms Collapsed Input Alarm Config.
Dry Contact Alarms (DB-9):
5 Inputs
1 Output
External Alarms Expended Input Alarm Config.

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 / ODU mute / Power Supply / Inventory.
Environmental Alarms of extreme temperature.
All Groups.
Test mode manual switch.

Management Menu of Extension Slots
This is the switch MAC address
Here you can set/review the IP

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

remote site (assuming both IDUs are
configured identically in terms of
MNG)

Management Main IDU: Setting IP Address
Here you can set the IP address of
the IDU
Let us examine the following

examples to understand how and
when we use each one of these
parameters

Node / standalone, no protection:
Connect your PC to any one of the MNG ports (7,6,5)
IP: 192.168.1.10 ETH Cross Cable IP: 192.168.1.100

SM: 255.255.255.0 SM: 255.255.255.0
D.GW: 0.0.0.0

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

Node/Standalone, 1+1 Protection:
Set a Floating IP
The floating IP address provides a

single IP address that will always give
direct access to the current active
main unit.
IP Slot #1: 192.168.1.10 ETH Y-Cable

IP Slot #2: 192.168.1.11 IP: 192.168.1.100
SM: 255.255.255.0 SM: 255.255.255.0
D.GW: 0.0.0.0
Floating IP: 192.168.1.22 See 1+1 Protection PPS for further info

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

IP Slot #2: 192.168.1.11 IP: 10.10.2.100
SM: 255.255.255.0 SM: 255.255.255.0
D.GW: 192.168.1.100
Floating IP: 192.168.1.22 See 1+1 Protection PPS for further info

Management Main IDU: Setting No. of MNG Ports
This is the switch MAC address
If your link is up you should be

able to see the other ends IP
The IDU has 3 ports for local management:

Port 7, Port 6 and Port 5.
You may enable none or up to 3 ports:
Number of ports =3 Port 7, Port 6, Port 5

Number of ports =2 Port 7, Port 6
Number of ports =1 Port 7
Number of ports =0 NO LOCAL MANAGEMENT !!!

In-Band Vs. Out of Band
Out of Band Management
MNG workstation is connected directly & locally via ETH cable to XPAND IP+
Management data does not consume Radio Data BW (not part of the radio link)
Every Link (two ends) is associated with unique Link ID
Management BW can be set to:

64Kbps to 2048Kbps (recommended)

In-Band Management
All units must be members of the same subnet / LAN unless Router is used
MNG data consumes BW of the total Radio link
Every Link (two ends) is associated with unique Link ID an VLAN ID
MNG BW can be configured via GUI: 64Kbps to 2048Kbps (recommended)
Remote units are managed via Radio Link

Management Main IDU: Port 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.
We reco
mmend
:
Do NOT
S
equal to et VID
1

Wayside Channel (WSC) Management
All units must be members of the same subnet / LAN unless Router is used
MNG data consumes BW of the total Radio link
Every Link (two ends) is associated with unique Link ID
MNG BW can be configured via GUI:

Wide (2048Kbps recommended) or Narrow (64Kbps)
Remote units are managed via Radio Link Feels

lik
No n e In-Band
eed to ac
associ ts like OOB
ate MN
G to V
LAN
WSC MGT WSC MGT
WSC port should be connected to MGT port via crossed ETH cable, on both ends

Management Main IDU: Port Properties
These parameters allow

you setting the
management capacity and
ports physical properties

Trap Configuration (OSS / NMS / Northbound)
To manage the IDU with OSS / NMS, you will need to configure the IP address
of the OSS Server
You may configure up to 4 Servers (Trap Destinations)
See next slide for more info.

Trap Configuration T. Destination Configuration

Licensing Copy, Paste, Ready to start
Licenses are generated per IDU S/N (capacity / ACM / switch mode)
License upgrade requires system reset.

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

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

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
When using NTP in a shelf configuration, all units in the shelf (including
standby main units) are automatically synchronized to the active main units
clock.

IP Table
Here you can manually set your neighbors network properties

SNMP
V1
V2c
V3
No security
Authentication
Authentication privacy
SHA
MD5
No Authentication

All ODU
This feature is used to feed the integrated fans of the All Outdoor Enclosure
(standalone outdoor rack)
When Enabled, the All ODU enclosure interface is activated, and the enclosure
controller can then be powered to monitor fan failure alarms.
The External Alarm Input #1 becomes an output, which together with 3.3V is
used to drive the enclosures electronic board.
External Alarm Input #2 is set with a specific text & severity, and is used to
monitor any enclosure fan failure, and to raise an alarm for it (polarity change
was required to adapt it to the enclosure behavior).
All ODU Disabled All ODU Enabled

All ODU - External Alarms Status
All ODU = Disabled
All ODU = Enabled

Versions - IDU

Versions Running / Installed / Upgrade / Downgrade
Lets explore this example:
The IDU running SW is displayed in the aidu line and currently it is 3.0.92
A new SW was downloaded sometime in the past (3.0.97)
The IDU was not upgraded yet

Thank You
XPAND IP+ Licensing
Licensing Copy, Paste, Ready to start
The License key is generated per IFU serial number (S/N):

Licensing: General
In order to upgrade license, license-key must be entered to the system

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

limited to ~3Mbps, allowing only management channels to remote end
To clear the violation alarm, user must configure the system to comply with the
loaded license, and then, issue cold-reset (radio resumes full operational status
if the violation is no longer relevant)

Licensing: Factory Defaults
ACM L2 SWITCH Asymmetric CAPACITY RESILIENCY

SyncE TDM En. QoS DEMO
When no license has been purchased or loaded, all IFUs support the following:
10Mbps radio traffic (ETH + TDM)

No ACM
No switch capabilities (single pipe only)
No RSTP
SNCP trails are allowed
Synch. sources for Sync ETH are blocked
4
Licensing: Automatic Coding & Modulation

ACM enables automatic & dynamic radio scripts. New scripts are available
(Release I6.6.2):
ACM-56MHz, QPSK 256QAM

5
Licensing: L2 Switch

This license enables 2 L2 switching modes:

1.Metro Switch (QnQ, A.K.A VLAN Stacking)
2.Managed Switch
The following features are supported as well -

LAG
Automatic State Propagation
QoS (Enhanced QoS requires additional license)
Ring RSTP (requires additional license)

Licensing: Asymmetrical Links

This license enables to use the asymmetrical MRMC scripts

Supported either in 28MHz or 56MHz
Allowing having 50% more traffic on the downlink on the expanse of the uplink.

Licensing: Radio Capacity

Limits the total amount of radio capacity available:
This is the sum of ETH + TDM bandwidth

The available radio scripts (MRMC) are automatically derived from the applied
license
This license applies only if the TDM-only license is disabled
8
Licensing: Network Resiliency

Allows configuration of features that make use of loop network topologies:
Ring RSTP
TDM trails protection (SNCP)
Note that for systems in which these features were enabled in previous versions, the
features will be allowed even if no resiliency license is purchased.

Licensing: Synchronization Unit

Allows configuration of external source as a clock source for synchronous

Ethernet output (assuming the IFUs hardware supports synchronization).
If this license is not installed, Ethernet clock source can only be a local (internal)
clock.
With SyncE BTS are accurately synchronized across the entire topology over Ethernet

Licensing: TDM Only

SyncU TDM En. QoS DEMO
Limits the amount of TDM trails that can be mapped to a radio.
Allows minimal ETH traffic for network management only.
If this license is allowed, any radio script can be loaded, but the number of trails is
limited.
11
Licensing: Enhanced Quality of Service

In addition to standard QoS features (no license required), the following

features are added:
WRED
Eight Queues
Shaping per queues

Licensing: Demo

Allowed for 60 days, auto reset is applied when expired (radio restores previously
assigned script)
When Demo license is enabled:

1.An alarm & timer are displayed in GUI (Timer is off when IFU is off)
2.All radio scripts and features are configurable
13
Order Examples
License Description License Code

XPAND IP+ License for Adaptive Coded Modulation. One license per LIC-XPANDIP+ACM
ODU
XPAND IP+ License for TDM ONLY - 16 E1-cross-connect. One license LIC-XPANDIP+16E-x
per Terminal
XPAND IP+ License for TDM ONLY - 75 E1-cross-connect. One license LIC-XPANDIP+75E-x
per Terminal
XPAND-IP+ Licence for 25 Mbit/s transmission capacity. One license per LIC-XPANDIP+25M
ODU
XPAND-IP+ Licence for maximum transmission capacity. One license per LIC-XPANDIP+Max
ODU
XPAND-IP+ License for Enhanced QoS. One license per IFU LIC-XPANDIP+QoS
XPAND-IP+ License for Ethernet Metro Switching. One license per IFU LIC-XPANDIP+SWITCH
that requires the use of two or more Ethernet ports
XPAND-IP+ License for Network Resilency (RSTP, SNCP). One license LIC-XPANDIP+NR
per east-west configuration (terminal)
XPAND IP+ License for Synchronous Ethernet functions. One license per LIC-XPANDIP+SYNCE
IFU required Sync E

Applications
1+1 HSB
No special license is required for 1+1 behavior

Install 2 ACM licenses per link (no HSB)
Install 4 ACM licenses per HSB link
A
A A
A

Metro Switch
When Aggregation is required
When more than 1 ETH port is needed
IFUs of both ends of a link should be installed with the same configuration:
Metro VS. Metro
Pipe VS. Pipe
Metro VS. Pipe is not supported
BTS10
M
M
BTS1
BTS11
BTS2
BTS3

Metro Switch
Metro switch license may be applied in first and last IFUs to allow
Secure tunneling of Customer Services (QnQ)

Easier IFU configuration: no need to pre-configure C-VLANs
Reduced costs due to fewer licenses in the topology
CVLANs
leavehere
BTS M M
Pipe Mode does not require a license

CVLANs
enterhere

SNCP & In-Band in RSTP Ring
When In-Band Management is required in a ring
Install Metro license in Main IFUS

Install Network Resiliency in Main IFUs
Enable RSTP or Ring RSTP in Main IFUs
In this example, SNCP is supported as well
R M
R M
R M
R M
R M
R M

SNCP without In-Band in RSTP Ring
When SNCP is required without In-Band Management
Install Network Resiliency license in Main IFUs
R
R

SyncE
The receiving IFU is fed with a time reference clock (TDM port)
The clock is transported over ETH frame
The clock is distributed in the topology using TDM XC Trail management
The terminating IFU drops the clock
Only 2 SyncE licenses are required
S S
TDM XC Trail Management
Clock

SyncE (Detect and distribute)
User can choose to configure Trails to distribute the clock or let the system
detect and distribute it automatically (more licenses are required)
S S
TDM XC Trail Management

Clock
S S S S S S S
Automatic Detection & Distribution
Clock
22
Exercise:
Tree, Aggregation, Enhanced QoS
Design your license requirements according to the following scheme
s
bp
M
0 0
1 CM
1. A
2 .
1. 200 Mbps
2. ACM
1. 400 Mbps
2. ACM 10
3. Enhanced QoS 0 Mb
ps
23
Solution
Q Enhanced QoS license
A ACM license
M Metro/Managed license
400 Capacity
A 100
A 200
Q A M 400
100
24
Solution 2: HSB
A 100
A 200
Q A M 400
Q A M 400
100
HSB
100
25
Solution 3: HSB + LAG
Dual GE interfaces connect to the Switch/Router
Static LAG is configured on the Switch/Router interfaces connected to the IFUs
Static LAG is configured on the pair of IFUs
2 optical splitter/combiners are used to connect each of the 2 interfaces on the
Switch/Router to each of the corresponding interfaces on the IFUs
A 100
A 200
Q A M 400
Q A M 400
LAG
100
HSB
100
See next slide
26
Solution 3: HSB + LAG
1+1 HSB
Static LAG
Static LAG 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
3rd party
Switch or Router Static LAG
STBY IP+ disables its Ethernet interface towards the Switch/Router

Any failure detected in radio link or equipment will trigger switch-over to the back-up
IP+ unit with <50msecs traffic interruption on the radio link
Any failure in the local GbE interfaces will be handled by the link aggregation
mechanism without triggering switch-over to the back-up IP+ unit!
27
Thank You
EMS Switch Configuration
Agenda
1. Switch mode review
2. Guidelines
3. Single Pipe Configuration

Switch Modes
1. Single (Smart) Pipe (default mode, does not require license)
Only single GbE interface is supported (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.
Single pipe does not forward PAUSE PDU (01-80-C2-00-00-01) and Slow
protocols PDU (01-80-C2-00-00-02).

Switch Modes
2. Managed Switch (license depended)
This application is 802.1Q VLAN aware bridge, allowing L2 switching based

on VLANs.
All Ethernet ports are allowed for traffic. Each traffic port can be configured to
be "access" port, "trunk" port or hybrid:
AllowedEgress
Type VLANs AllowedIngressFrames
Frames
OnlyUntaggedframes
SpecificVLANshouldbe
Access (orTaggedwithVID=0 Untaggedframes
assignedtoaccesstheport
"PriorityTagged )
ArangeofVLANsshouldbe
Trunk OnlyTaggedframes Taggedframes
assignedtoaccessthePort
SpecificVLANandarangeof Onlytaggedframeaslisted
Taggedand
Hybrid VLANsshouldbeassignedto ontheportanduntagged
Untaggedframes
accesstheport frames

Switch Modes
3. Metro Switch (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 XPAND IP+ settings (radio,

configuration, etc.) but affects traffic
VLANs need to be created in the switch DB before assigned

to a port

Single Pipe Configuration
Single Pipe Configuration
Untagged
VID 4 45
VID 51 IP+ Switch
VID 100
Port 1: GbE (Optical or Electrical) Port 8 (Radio)

Port 3: FE (RJ45)

Configuration Single Pipe
This is the default setting

Configuration Single Pipe
Only one ingress port

can be used:
Port 1 (Opt. or Elec.)
Port 3 (RJ45)
When one is enabled

the other is disabled
No need to configure
VID membership
Thank You
Commissioning the Radio Link
Version 6.8
Radio Link Parameters
TSL RSL
IDU ODU ) )) )) ) ODU IDU
To establish a radio link, we need to configure / monitor the following:
1.TX / RX frequencies set on every radio

2.RSL Received Signal [dBm]
3.MSE Mean Square Error [dB] (see MSE PPS)
4.Max. TSL Max. allowed Transmission Signal [dBm]
5.Monitored TSL Actual Transmission level [dBm]
6.IF Interface Enable / Disable
7.Link ID must be the same on both ends
8.ATPC ON / OFF avoiding co-interferences caused by nearby antennas
9.MRMC Modem scripts (ACM or fixed capacity, channel & modulation)
10.Adaptive Power ON / OFF To allow max. transmission signal when ACM is ON
11.IFC in case of using Dual Receiver Radios
12.MAC Header Compression 45% higher throughput (Nera Proprietary)
2
Feature Description
(followed later with EMS Configuration Steps)
LINK ID Antenna Alignment Process
To avoid pointing the antenna to a wrong direction (when both links share the
same frequency), LINK ID can be used to alert when such action is take.
# 101
# 101
# 102
Link ID
Mismatch
# 101
Link ID Mismatch
4
LINK ID Antenna Alignment Process
Both IDUs of the same link must use the same Link ID
Otherwise, Link ID Mismatch alarm will appear in Current Alarms Window
# 101
# 101
# 102
Link ID
Mismatch
# 101
Link ID Mismatch
5
ATPC Automatic Transmit 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
6
To address this issue, online transmission power control that adapts to
external changes is necessary.
In ATPC, each node builds a model for each of its neighbors, describing the
correlation between transmission power and link quality.
With this model, we employ a feedback-based transmission power control

algorithm to dynamically maintain individual link quality over time.
7
1. Enable ATPC on both sites
2. Set reference RSL (min. possible RSL to maintain the radio link)
3. ATPC on both ends establish a Feedback Channel through the radio link (1byte)
4. Transmitters will reduce power to the min. possible level
5. Power reduction stops when RSL in remote receiver reaches Ref. level
TSL Adjustments Monitored RSL
Radio Radio
ATPC Radio
module
Transceive
Receiver
Ref. RSL
r
Feedback Signal RSL

Radio
Quality required
Receiver change
Check
Site A Site B
8
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
Radio Radio
ATPC Radio
module
Transceive
Receiver
Ref. RSL
r
Feedback Signal RSL

Radio
Quality required
Receiver change
Check
Site A Site B
9
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)
Note: in case of Radio LOF the power is increased up to configured maximum

power level
Radio Radio
ATPC Radio
module
Transceive
Receiver
Ref. RSL
r
Feedback Signal RSL

Radio
Quality required
Receiver change
Check
Site A Site B
10
ATPC Override Timer
power level
As a result the transmitter may cause interferences

The ATPC Override Timer enables limit this interference
The timer counts seconds passed since maximum power reached
Once the timer expires the transmission level is as defined by ATPC
override Tx level
power level
Radio Radio
ATPC Radio
module
Transceive
Receiver
Ref. RSL
r
Feedback Signal RSL

Radio
Quality required
Receiver change
Check
Site A Site B
11
MRMC Multi Rate Multi Coding
1. Radio capacity is determined by Channel BW, Modulation and ACM (fixed

or adaptive)
2. Non ACM scripts (old) are still available to support Non-ACM radios
3. ACM TX profile can be different than ACM RX profile.
4. ACM TX profile is determined by remote RX MSE performance.
5. Remote Receiver (RX) initiates ACM profile upgrade or downgrade
6. When MSE is improved above predefined threshold, RX generates a

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

the remote TX to downgrade its profile.
12
MRMC Multi Rate Multi Coding
Each ACM script has 8 profiles. Profile Modulation
0 QPSK
The radio capacity will be dictated by the
channel BW (see next slide) 1 8QAM
2 16QAM
The lower the modulation the less sensitive
3 32QAM
the receiver is:
4 64QAM
More system gain 5 128QAM
Bigger fade margin
6 256QAM(highFEC)
At lower modulation orders the radio link will 7 256QAM(lowFEC)
tolerate lower RSL levels. For example:
With 16QAM the radio will drop at (-78dBm)

whereas with 8QAM the radio will drop at
(-82dBm)
13
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.
14
MRMC Adaptive Power = OFF
256QAM @ Monitored TSL = 18 dBm (Max.)
Signal Degradation
= Lower bit/symbol
16QAM @ MAX. TSL = 18 dBm
15
MRMC Adaptive Power = ON
256QAM @ Monitored TSL = 18 dBm(Max.)
Signal Degradation
= Lower bit/symbol
16QAM @ Monitored TSL = 24 dBm
er s pan
Long
16
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
The Effective Isotropic Radiated Power (EIRP) is the apparent power transmitted towards the receiver assuming that the
signal power is radiated equally in all directions
17
MRMC Adaptive Power
If enabled, the maximum tx power in lower constellations is limited by the
reference class configured, as listed in the following table.
Reference Class Reference Modulation

Class 2 4
Class 4 16
Class 5B 64
Class 6A 256
FCC 4
18
MAC Header Compression
1. No impact on User Traffic

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

Dropping the Preamble + SFD + IFG saves 20 bytes
Dropping the Ethernet type saves 2 bytes
Adding a GFP header adds 4 bytes
In addition:
Frequently repeating SA & DA are learned
Learned DA & SA are not transmitted
A short pointer is used instead of the original 12 bytes
19
MAC Header Compression
L2ETHFrameSize[bytes] ImprovedCapacity
64 45%
96 29%
128 22%
256 11%
512 5%
20
EMS Configuration
Radio Settings Local Radio - 1
Radio type (displayed when comm. is OK)
Spectrum Mask
FQ spacing (gap) between channels
Monitored transmission power
Monitored received signal
Monitored MSE. Required lower than (-35dB)
The larger the amount, the poorer the radio link

quality. Required value = zero
Radio frequencies can be set

locally or both ODUs (box
checked) when links is up
22
Radio Settings Local Radio - 2
Enable / Disable : Requires system reset
Enable = no transmission
Must be identical on both IDUs
Enable on both IDUs to get maximum

throughput (500Mbps @ 56MHz)
23
ATPC Local Radio - 3
Enable / Disable
Min. target RSL (local)
24
Radio Settings Local Radio 4 Disabling IF
As explained in previous slide, enabling or disabling the IF interface

requires a reset
25
Radio Settings 5: Remote Radio
When the radio link is up, you can configure the remote radio via the radio frames:
Make sure Remote IP is available (configurable)

Remote RSL can be read
Remote TSL can be set (values depend on MRMC script)
Remote ATPC REF level
Remote Floating IP
Remote TX MUTE can be disabled (see next slide)
26
Radio Settings 5: Un-muting Remote Radio
Simplified scheme
Site B is NOT transmitting
but receiver is still ON
Site A is transmitting
u n- mute
ed
Forc
s m ission
ta r t tran
S
Site B
Site A
27
Radio Settings 6: Radio Thresholds
These settings determine the sensitivity / tolerance for triggering:
1+1 HSB switchover

Ethernet Shutdown
PM generated alarms
28
Radio Settings 7: MRMC Configuration
29
l i st? page
t h is MC
i n d MR
f
t tthe
Ca nan
l d ow
ol
Scr
30
MAX. Capacity
(w/out
compression)
ACM Script CH. BW
Modulation
Spectrum
Mask
ACM is on
Spectrum
Class Type
31
32
Configure here:
Adaptive Power: Enabled / Disabled

Reference Class
33
Thank You
Configuring Interfaces
Version I6.8
Agenda
In this presentation we shall

explain the required steps to
configure these interfaces

ETH TDM STM1 AUX AIS Sync
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 Disabled / Traffic
ETH 3 (RJ 45) FE 10 / 100 Disabled / Traffic Disabled / Traffic
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.


IP+ has 16 TDM ports + 16 additional ports when a 2nd T-Card is

installed.
Supported PHYs:
E1
DS1
Dynamic allocation:
Radio bandwidth (which may vary in ACM) is automatically allocated in the
following order:
1. High-priority TDM trails

2. Low-priority TDM trails
3. Ethernet traffic (Data + Management, QoS should be considered)
TDM trails in both sides of a link should have identical priorities.

Standalone IFU
E1/DS1 port #n will be mapped to

radio VC#n (n=1-16).
When Trails are configured, default

mapping (above) is overwritten by
Trail Mapping.
However, if no trails are configured (all

are deleted) system will revert to the
default setting.
When Trail is configured and set to

Operational - TDM port is activated.
When Trail is configured but set to

Reserved - TDM port is disabled.

Node Site
Up to 180 trails can be configured in a
Shelf / node
The number of Trails mapped to a

radio depends on radio capacity
(MRMC).
The maximum number of radio Trails

is 84

The following configurations are

available:
Admin: Enable / Disable
When interface is disabled:

There is no signal transmission
Received signal is ignored
Trails previously configured to STM-1
interface will get Signal Failure
No alarms will be shown
Mute TX:
Mutes the outgoing STM-1 signal, but
received signal will be used for traffic

The following configurations

are available:
Clock source:
This is a reference for the outgoing
STM-1 signal:
Internal Clock
Loop
STM VC
Synch VC
This is the VC Channel which will be
used to sync the STM-1 interface

AIS Signaling in STM interface (V5) The system can be configured to signal
AIS at the VC level (AIS-V) in the V5
byte of the overhead.
This is meant to provide indications to

SDH
multiplexing equipment which may not
have the ability to detect AIS at the
payload level.
For example: signaling in outgoing V5

byte upon AIS detection at payload-level
(E1)
111111111 111111111
AIS @ E1 TS AIS @ STM V5

Line TX Protection Mode
STM-1/OC-3 interface transmission

behavior when in protection mode

J0 trace identifier is fully supported in

both 15-byte and 1-byte modes:
An alarm will be raised when the expected
string differs from the received string (but
traffic will not be affected).
Transmit, Expected and Received strings are

provided.
If a string is defined and user changes the

length from 15 bytes to 1 byte, the first byte
will be analyzed and other bytes ignored.
The string transmitted as J2 trace identifier is

the Trail ID defined for the TDM trail mapped
to the corresponding VC-12 interface.

Excessive BER threshold:

Specific for STM-1 interface
Signal degrade threshold:

Specific for STM-1 interface

EOW may be used as a simple solution for on-site

communication between two technicians / installers / etc.

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

since narrow WSC might be too slow.
WSC: OOB MNG in a 1+0 standalone link
At least 2 management ports are needed in a local unit:

One port for local management, and 2nd port that will be connected to Wayside port.
On remote unit, Wayside port will be connected to management port.
WSC: OOB MNG in a 1+1 standalone IFUs
Active & Standby MNG

ports have 2 options to be
connected to the Host:
Using Ethernet splitter
cable connected to external
switch.
Using Protection "Patch
Panel".
WSC port will be connected in each unit to other
available management port.
In remote site, each unit's Wayside port should be
connected to management port.
OOB MNG in a 1+1 standalone IFUs (P. Panel)

This feature allows detection of AIS

signals in TDM traffic arriving from line
interfaces (E1/DS1, STM-1):
In case of detection, the following takes place:
Signal failure is generated at the corresponding trail this will cause the far end not to
receive a signal (including trail ID indications) and the trail status to show signal failure
and trail ID mismatch.
An indication is given to user at the proper interface. Notice that this is not a system
alarm, since the problem originates elsewhere in the Network

AIS Signaling in STM interface (VC 12)
In case of signal failure at the trail outgoing from the STM-1 interface, AIS
will be transmitted at the payload of the VC-12.
This table is added automatically to

the STM-1 page when AIS is
enabled

The synchronization is used to sync the BTS or other equipment and

not Neras equipment
The clock frequency is E1/T1 based*
Up to four clock sources can be defined in a chassis or a node
At any given unit only one interface can be used as synchronization
destination
* There is also an option of 25MHz clock, explained afterwards

Sync Source Clock Source

(Sync Destination)
Clock Distribution
Direction

Sync Source
Clock Source
(Sync Destination)
Sync Source
Clock Source
(Sync Destination)
Clock Distribution
Direction

Here the Sync Source is the E1 #1, this E1 cant be used for traffic
Possible Sync Sources:

TDM Trails
E1/T1 Interfaces
STM-1/OC-3 Interfaces
STM-1/OC-3 VC-11/12s
Radio Channels
Gigabit Ethernet Interfaces*
24 * Supported by specific HW revision Proprietary and Confidential
Using Synchronization Status Messages (SSM)

In SSM each sync source has quality and priority.
When an IFU require to determine which sync source
to use the decision is based on:
1. Clock Quality
2. Sync Source (Priority) used in identical quality
case


The clock quality options are:
Automatic determines the clock quality automatically*
G.811 PRC quality clock (Highest quality)
SSU A G.812 Type I or IV clock
SSU B G.812 Type VI clock
G.813/8262 default clock level (Lowest quality)
DO NOT USE
* Supported by interfaces were SSM is implemented (Radio Port)


Synchronization mode can be either automatically or
to be forced for a specific interface
In case of a failure in the current sync source
The next sync source is used
In case the failed clock is good again the unit
can revert to it after a certain time period (Sync
source revertive timer
* Supported by interfaces were SSM is implemented (Radio Port)

Here the Radio channel is a clock source to the sync
Possible Clock Sources:

E1/T1 Interfaces
STM-1/OC-3 VC-11/12s
Radio Channels
Gigabit Ethernet Interfaces

PRC Regenerator Mode

Frequency of 25MHz clock is applicable in the following conditions
Hardware revision R3
Single Pipe operation
Ethertnet #1 (GBE) must be enabled
The Ethernet interface is not used as a synchronization source
PRC Regenerator Mode is set to enabled
Single Pipe

Thank You
XC / SNCP / Nodal Solution
Introduction
SNCP (ITU- G.805)
Ring topologies provide path protection for Ethernet or TDM signals
In some scenarios additional protection is required
The XPAND IP+ Path-Protection is based on SNCP

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

SNCP (ITU- G.805)
With Wireless SNCP, a backup VC trail

can be optionally defined for each
individual VC trail
Main Path
Protective Path

y IP+ IFU can be used as a Standalone unit (1U) or

in as a Nodal Solution
y Connecting 2 IFUs requires a nodal enclosure:

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

unified nodal device:
Common Ethernet Switch
Common E1s Cross Connect
Single IP address
Single element to manage

Up to 6 units can be stacked to form single nodal device

Additional units can be added in the field as required
Multiple nodes can be cascades to support large aggregation sites
Stacking is done using 2RU Nodal enclosures
Each enclosure has 2 slots for hot-swappable 1RU units
Additional Nodal enclosures and units can be added in the field as required without
affecting traffic
Front Nodal enclosure

Rear

Integrated nodal solution Main units
Units located in the bottom Nodal enclosure are acting as the main units
The main unit performs the cross-connect, switching and management functions for
all the units in the node
Mandatory active main unit can be located in any of the 2 slots
Optional standby main unit can be installed in other slot
Switchover time <50msecs for all traffic affecting functions
Integrated Ethernet Switching
Integrated TDM cross-connect
M Main unit
E
Expansion unit

Integrated nodal solution Expansion units
Units located in non-bottom Nodal enclosures are acting as expansion units
All interfaces of the expansion units (radio, TDM and Ethernet) are connected to the
main units
Expansion unit is fully managed through the main units
Radios in each pair of main/expansion units can be configured as either:
Dual independent 1+0 links
Single 1+1 HSB link
Single 2+0/XPIC link
Integrated Ethernet Switching
Integrated TDM cross-connect
M Main unit
E
Expansion unit

Trail Configuration Guidelines
XC Trails Guidelines (1)
1. XC Trails can be configured only via Main unit
2. All Trails are transported through main unit(s)
3. When Protection is enabled, configure trails to go via the Active unit

(XC Trails are automatically created on the STBY unit)
4. T-Cards (TDM / SDH) are not hot-swappable, do not extract / insert card
when IDU is powered up
5. Radio VCs must be identical on both sides of the radio link

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

Identify Trail interfaces prior to configuration

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

For SNCP we shall
Trail traverses through here: IP+ need to define 3
We shall need to define 2 interfaces
interfaces
IP+ Bypass
site Protected Trail
(Automatic)
IP+
Trail starts here:
For SNCP we shall
need to define 3
Radio Link interfaces

Pay attention to the order of configuration: 1
2 IP+
The Trail Start/End points should
be configured first (interface #1) 3
IP+ Bypass
site
Interfaces #2 and #3 can be
configured in a random order
Protected Trail
(Automatic)
2 3
IP+

Standalone non-protected Trail Configuration
Step #1: Access Trail Page
Click on the Add button

Step #2: Configure 1st Interface
Click on the 1st interface connector
In this example we selected the

PDH connector.
Your next step is selecting the PDH
port number.

SDH connector.
Your next step would be selecting
the VC number.

Step #3: Configure 2nd Interface
Click on the 2nd interface connector

Radio as the next interface
connector.
Your next step would be selecting
the radio channel number.
Alternatively you could choose other combinations as well:
PDH to PDH
PDH to Radio (above)
PDH to SDH
SDH to Radio
SDH to Radio
Radio to SDH
Radio to PDH

Step #4: Configure Trail Attributes
Make sure Trail ID is unique and identical on all sites/trails

Step #5: Trail Verification
If your settings are correct, trail alarms should disappear, trail path is ready to be tested

SNCP Trail Configuration in a Node
Selecting Main IDU for Trail Configuration
In the following example we assume every node has 2 IFUs installed in a

Main Enclosure
Make sure your Main unit is selected on every Node-EMS
Enable Protection when you configure the Trails (excluding Bypass Nodes)
Trail ID should unique and identical on all nodes

SNCP Trail in Nodal Architecture
PDH interface
IP+
Bypass
Node IP+
IP+
SDH interface

1st Node
PDH interface
IP+
IP+
Bypass
site
Radio CH #1 Radio CH #26

IP+
SDH interface #1

Bypass Node
PDH interface
Radio CH #48
IP+
Bypass IP+
Node
Radio CH #1
IP+
SDH interface

3rd Node
PDH interface
Radio CH #48
IP+
Bypass IP+
site Radio CH #26
IP+
SDH interface

Radio Capacity Calculation
Radio & PDH Capacity VS. Channel
Ethernet capacity (a.k.a. Ethernet L1 capacity) - Total bit rate from an

Ethernet user port. Taking into account the full Ethernet frame including the
IFG and preamble fields. Ethernet capacity is sometimes referred to as "port
utilization rate".
Ethernet L2 capacity - Total bit rate of net Ethernet frames running over
the Ethernet user port. Taking into account the Ethernet frame without the
IFG and preamble fields.
Radio throughput - Total bit rate supported by the radio link running in a
specific channel/modulation including radio frame overhead, etc.

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

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

40 MHz
license (Mbps)
0 QPSK 50 23 79.64 60.68 118506.13 55.90
1 8 PSK 100 35 119.11 90.75 177239.65 83.04
2 16 QAM 100 51 174.14 132.68 259136.72 120.87
3 32 QAM 150 65 218.49 166.47 325132.27 151.36
4 64 QAM 150 81 273.67 208.51 407254.05 189.30
5 128 QAM 200 84 305.49 232.76 454605.63 211.18
6 256 QAM 200 84 346.84 264.26 516135.41 239.61
7 256 QAM 300 84 369.96 281.87 550529.12 255.50
56 MHz
license (Mbps)
0 QPSK 100 32 108.86 82.94 161994.37 75.99
1 8 PSK 100 48 163.37 124.48 243116.10 113.47
2 16 QAM 150 64 216.60 165.03 322318.52 150.06
3 32 QAM 200 84 288.50 219.81 429314.58 199.50
4 64 QAM 300 84 358.49 273.14 533473.73 247.62
5 128 QAM 300 84 430.43 327.95 640527.34 297.08
6 256 QAM 400 84 489.77 373.16 728824.51 337.87
7 256 QAM 400 84 531.82 405.20 791403.86 366.78

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

ACM # of ACM # of ACM # of
Modulation Capacity Modulation Capacity Modulation Capacity
Point E1s Point E1s Point E1s
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

Thank You
Mean Square Error (MSE)
Agenda
Definition
Example
MSE & ACM
MSE values at 56MHz (case study)
MSE values at 28MHz (case study)
Troubleshooting examples
2
Introduction
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 an aggregated error by which the expected value differs from the
quantity to be estimated.
The difference occurs because of randomness or because the receiver

does not account for information that could produce a more accurate
estimated RSL
4
To simplify.
Imagine a production line where a machine needs to insert one part

into the other
Both devices must perfectly match
Let us assume the width has to be 10mm wide
We took a few of parts and measured them to see how many can
fit in.
5
The Errors Histogram
(Gaussian probability distribution function)
Quantity 9 Expected value
3
3
2
1
width
6mm 7mm 10mm 12mm 16mm
To evaluate how accurate our machine is, we need to know how many parts differ
from the expected value
9 parts were perfectly OK

6
The difference from Expected value
Quantity
Error = 0 mm
Error = + 2 mm
Error = - 3 mm
Error = + 6 mm
Error = - 4 mm
width
To evaluate the inaccuracy (how sever the situation is) we measure how much the
errors differ from expected value
7
Giving bigger differences more weight than
smaller differences
Quantity
Error = 0 mm
+ 2 mm = 4
-3 mm = 9
- 4 mm = 16 + 6 mm = 36
width
We convert all errors to absolute values and then we square them
The squared values give bigger differences more weight than smaller differences,
resulting in a more powerful statistics tool:
16cm parts are 36 units away than 2cm parts which are only 4 units away
8
Calculating MSE
Error = 0 mm
Quantity
+ 2 mm = 4
-3 mm = 9
- 4 mm = 16 + 6 mm = 36
width
To evaluate the total errors, we sum all the squared errors and take the average:
16 + 9 + 0 + 4 + 36 = 65, Average (MSE) = 13
The bigger the errors (differences) >> the bigger MSE becomes
9
Calculating MSE
MSE determines how narrow / wide the Bell is
Quantity
width
10mm
When MSE is very small the Bell shaped histogram is closer to perfect
condition (straight line): errors = ~ 0
10
MSE in digital modulation (Radios)
Let us use QPSK (4QAM) as an

example:
Q
QPSK = 2 bits per symbol
01 00
2 possible states for I signal
2 possible states for Q signal
= 4 possible states for the

I combined signal
The graph shows the expected

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

expected values (constellation)
Q of the received signal (RSL)
01 00
The blue dots represent the
actual RSL
I
As indicated in 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
12
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
13
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
14
Using MSE
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
16
MSE and ACM
When the errors is too big, we need

a stronger error correction
mechanism (FEC)
Therefore, we reduce the number

of bits per symbol allocated for data
and re-assign the extra bits for
correction instead
For example
256QAM has great capacity but
poor immune to noise
64QAM has less capacity but much

better immune for noise
ACM Adaptive Code Modulation
17
Triggering ACM with MSE
When ACM is enabled, MSE values are analyzed on each side of the link
When MSE degrades or improves, the system applies the required

modulation per radio to maintain service
ACM 28MHz, MSE [-dB]:
Downgrade ACM Profile Upgrade ACM Profile

Profile Mod 10-6 Threshold when MSE reaches when MSE reaches Optimal
0 QPSK 6.9 10.4 11.9 >30
1 8PSK 11 14.5 16 >30
2 16QAM 13.3 16.8 18.3 >30
3 32QAM 18 21.5 23 >30
4 64QAM 20 23.5 25 >30
5 128QAM 24.4 27.9 29.4 >33
6 256QAM 25 28.5 30 >35
7 256QAM 28 31.5 33 >35
18
When ACM is enabled, MSE values are analyzed on each side of the link
When MSE degrades or improves, the system applies the required

modulation per radio to maintain service
ACM 56MHz, MSE [-dB]:

Profile Mod 10-6 Threshold when MSE reaches when MSE reaches Optimal
0 QPSK 6.7 10.2 11.7 >30
1 8PSK 12 15.5 17 >30
2 16QAM 13.1 16.6 18.1 >30
3 32QAM 17.3 20.8 22.3 >30
4 64QAM 19.6 23.1 24.6 >30
5 128QAM 22.6 26.1 27.6 >33
6 256QAM 25 28.5 30 >35
7 256QAM 27.5 31 32.5 >35
19
Lets analyze the figures in the table below (we shall focus on the last line):
1.When the radio is in optimal conditions, MSE is near -35dB

2.When MSE drops below -27.5dB, we will experience high BER
3.To avoid High BER we change the profile when MSE reaches -31dB
4.Now that the radio is @ profile 6, the MSE must improve to -32.5 to recover high
capacity (profile 7)
Profile Modulation 10-6 Threshold when MSE reaches when MSE reaches Optimal
0 QPSK 6.7 10.2 11.7 >30
1 8PSK 12 15.5 17 >30
2 16QAM 13.1 16.6 18.1 >30
3 32QAM 17.3 20.8 22.3 >30
4 64QAM 19.6 23.1 24.6 >30
5 128QAM 22.6 26.1 27.6 >33
6 256QAM 25 28.5 30 >35
7 256QAM 27.5 31 32.5 >35
5 dB security window
20
ACM & MSE: Another approach
In this graph we refer to a 56MHz channel. It is easier to observe the

hysteresis of changing the ACM profile with respect to measured MSE.
As you can see, the radio remains @ profile 6 till MSE improves to -32.5dB:
ACM
Profile
32.5
30
Profile7 Profile6 Profile5 Profile4Profile3Profile2 Profile1Profile0
MSE
3128.526.123.120.816.6 15.510.2
21
ACM & MSE: Another approach
When RF signal degrades and MSE passes the upgrade point (MSE @ red point), ACM will
switch back FASTER to a higher profile (closer to an upgrade point) when MSE improves.
When RF signal degrades and MSE does not pass the upgrade point (green point) ACM
waits till MSE improves to the point of next available upgrade point (takes longer time to
switch back to the higher profile).
ACM
Profile 32.5 30
Profile7 Profile6 Profile5
3128.526.1 MSE
22
Troubleshooting wrong modulation
When different settings of Modulation are set, MSE will be showing -
99.99dB (Modulation Mismatch):
RSL = ~ (-45) dBm RSL = ~ (-45) dBm

MSE = -99.99 dB MSE = -99.99 dB
23
Thank You
Adaptive Code & Modulation (ACM)
XPAND IP+s Key Feature
IP+ 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

Adaptive Coding and Modulation
Utilize highest possible modulation considering the changing environmental

conditions
Hitless & errorless switchover between modulation schemes
Maximize spectrum usage - Increased capacity over given bandwidth
Service differentiation with improved SLA
Increased capacity and availability

Adaptive Coding and Modulation
Voice & real time

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

highest priority

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

IP+ 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
Throughput per radio carrier:

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

modulation changes
Zero downtime - A must for mission-critical services

IP+ Enhanced radio capacity for Ethernet traffic
Intelligent Ethernet header compression mechanism (patent pending)

Improved effective Ethernet throughput by up to 45%
No affect on user traffic
Ethernet Capacity increase by

packet size (bytes) compression
64 45%
96 29%
128 22%
256 11%
512 5%

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

Traffic Prioritization
When ACM is enabled and link degrades, there are 3 scenarios that might
apply based on the configuration
ScenarioI ScenarioII ScenarioIII

(Default)
1st Priority TDMHighPriority EthernetHighPriority TDMHighPriority
HighTDMover HighEthernet TDM

2nd Priority EthernetHighPriority TDMHighPriority TDMLowPriority
HighEthernet over over
3rd Priority TDMLowPriority TDMLowPriority Ethernet
TDM Ethernet
4th Priority EthernetLowPriority EthernetLowPriority
9
High TDM over High Ethernet Scenario I
In this scenario the QoS drops the traffic as

follows:
1.Ethernet traffic with low priority discarded first
ScenarioI 2.TDM trails with low priority discarded second
3.Ethernet traffic with high priority discarded third
1st Priority TDMHighPriority 4.TDM High priority traffic is dropped according to
order of configuration
2nd Priority EthernetHighPriority
3rd Priority TDMLowPriority
4th Priority EthernetLowPriority
10
High Ethernet over TDM Scenario II
In this scenario the QoS drops the traffic as follows:
1.Ethernet traffic with low priority discarded first
2.TDM trails with low priority discarded second
3.TDM trails with high priority ScenarioII
discarded third
4.Ethernet traffic 1st Priority EthernetHighPriority
with high
priority
discarded last 2nd Priority TDMHighPriority
3rd Priority TDMLowPriority
4th Priority EthernetLowPriority
11
Traffic Prioritization
In this scenario the QoS drops the traffic as

follows:
1.Ethernet traffic discarded first ScenarioIII
2.TDM trails with low priority discarded second (Default)
3.TDM High priority traffic is dropped 1st Priority TDMHighPriority

according to order of configuration
2nd Priority TDMLowPriority
3rd Priority Ethernet
12
Traffic Prioritization - Configuration
Two parameters required to be configured

1.The traffic priority scheme, as described earlier
2.High priority Ethernet BW amount, defines the portion of the High priority
Ethernet traffic (equivalent to CIR)
13
ACM Working Boundaries
Link capacity is determined according to License and applied script
ACM Script consists of Channel BW, max. Capacity and Modulation
Highest modem script is applied using MRMC configuration window
When Automatic State Propagation is enabled, GbE (SFP) port can be

configured to shutdown when ACM is below a pre-defined script
14
Radio Capacity Calculation
Ethernet capacity (a.k.a. Ethernet L1 capacity) - Total bit rate from an

Ethernet user port. Taking into account the full Ethernet frame including the
IFG and preamble fields. Ethernet capacity is sometimes referred to as "port
utilization rate".
Ethernet L2 capacity - Total bit rate of net Ethernet frames running over
the Ethernet user port. Taking into account the Ethernet frame without the
IFG and preamble fields.
Radio throughput - Total bit rate supported by the radio link running in a
specific channel/modulation including radio frame overhead, etc.

3.5 MHz
license E1s (Mbps)
2 16 QAM 10 4 13.60 10.36 20233.77 10.50
4 64 QAM 25 6 20.14 15.35 29974.03 15.00
7 MHz
license E1s (Mbps)
0 QPSK 10 4 13.42 10.23 19976.45 10.38
1 8 PSK 25 6 20.18 15.38 30034.94 15.03
2 16 QAM 25 8 27.87 21.24 41475.26 20.31
3 32 QAM 25 10 34.48 26.27 51304.87 24.85
4 64 QAM 25 12 40.44 30.81 60175.21 28.95
5 128 QAM 50 13 46.60 35.50 69339.64 33.19
6 256 QAM 50 16 54.53 41.55 81151.77 38.64
7 256 QAM 50 17 57.38 43.72 85389.21 40.60

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

40 MHz
license (Mbps)
0 QPSK 50 23 79.64 60.68 118506.13 55.90
1 8 PSK 100 35 119.11 90.75 177239.65 83.04
2 16 QAM 100 51 174.14 132.68 259136.72 120.87
3 32 QAM 150 65 218.49 166.47 325132.27 151.36
4 64 QAM 150 81 273.67 208.51 407254.05 189.30
5 128 QAM 200 84 305.49 232.76 454605.63 211.18
6 256 QAM 200 84 346.84 264.26 516135.41 239.61
7 256 QAM 300 84 369.96 281.87 550529.12 255.50
56 MHz
license (Mbps)
0 QPSK 100 32 108.86 82.94 161994.37 75.99
1 8 PSK 100 48 163.37 124.48 243116.10 113.47
2 16 QAM 150 64 216.60 165.03 322318.52 150.06
3 32 QAM 200 84 288.50 219.81 429314.58 199.50
4 64 QAM 300 84 358.49 273.14 533473.73 247.62
5 128 QAM 300 84 430.43 327.95 640527.34 297.08
6 256 QAM 400 84 489.77 373.16 728824.51 337.87
7 256 QAM 400 84 531.82 405.20 791403.86 366.78

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

ACM # of ACM Modulatio # of ACM # of
Modulation Capacity Capacity Modulation Capacity
Point E1s Point n E1s Point E1s
1 QPSK 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

Thank You
1+1 HSB Protection
Agenda

What is Protection?
A method of using one or more devices in a

standby mode in order to have a secondary
link up when failure occurred to the active link
In order to achieve a full protected link each

and every device should be protected
The number of multiplied devices depends on

the link importance
The process of keeping (something or someone) safe

Wikipedia.com
Everybody needs Protection

General Guidelines
1. A Standby IFU is referred to as the Mate
2. When a switchover occurs, the Active IFU becomes Standby and the
Standby IFU becomes Active
3. Accessing a Mate IFU can only be done via the Active IFU
4. Accessing the "Active" IFUs is achieved via unique IP addresses or via

Floating IP
5. Y-Split cables must be used for Ethernet signals
6. ETH Cross Cable* (Protection Cable) is used to connect the protection ports
of both IFUs by using dedicated PROT port.
* Unless units are in chassis

External Protection
Achieved by using two standalone IFUs
The IFUs must be connected by an Ethernet Cross cable (dedicated protection ports)
Each IFU must have a unique IP address
Protection for interfaces is done by:
E1 Y-Cable
GbE Optical Y-Cable
FE Y-Calbe
high low
Coupler Coupler
high low

Shelf Protection
When enabling a Shelf Protection, the following rules should be applied:
Shelf backplane replaces the external Protection Cable

Never insert or extract an IFU while powered up
Always secure IFUs to shelf enclosure with provided screws
Protection can be enabled in each pair (1+2, 3+4, 5+6)
IFU in slot 1 & 2 must have a unique IP address
6 Mate
5 Standalon
Active e
4Mate
Example: Standalon
3
e
Active
2Mate
Standalon
1Active e
Protected node Unprotected site

Floating IP
The Floating IP address feature is meant to provide a single IP address that
will always give direct access to the current active main unit.
1.The Floating IP and Unique IFU IPs must be in the same subnet
2.The Floating IP and Unique IFU IPs are user-configurable
3.The Floating IP is copied from Active to Mate (following Copy to Mate command)
4.When Protection is applied, the Floating IP is assigned to the STBY IFU which
becomes the Active
5.The extension IPs are irrelevant (unseen by network)
6.OSS & NMS can access all IFUs (Main and Extension) via SNMP
7.Alternatively, users may access any of the units using their local IP addresses
IFU
192.168.1.100
IFU
192.168.1.75
192.168.1.72
IFU
192.168.1.71

Configuring external 1+1 from scratch
Configuring external 1+1 from scratch (1)
1. Set all IFUs to factory defaults
2. When IFUs complete the booting sequence, verify:
All IFUs have the same HW version (same P/N)

All IFUs have the same SW version
All IFUs have the same license
Every IFU has unique IP address (within the same subnet)
Active and STBY have the same SW mode (Pipe / Managed / Metro)
All IFUs have the same Management mode (In band or OOB)
In case of In-Band, all IFUs have the same In-Band VID
Note:
The IFU, which is connected to the ODU fed by the lower
attenuation channel of the RF coupler, is the IFU that should be
selected as "Active.

3. Install the first link (make sure radio is up)
ODU ODU
4. Enable Protection on both IFUs (management will be lost for 60 sec)
5. Lock Protection on both IFUs (to avoid unnecessary switchover when second IFU is
enabled)
6. Install second IFU in each site (no need to configure it)
ODU ODU
ODU ODU

7. Enable protection in second IFU in each site
8. Connect ETH Cross Cable between both protection ports
ODU ODU
ODU ODU
9. Disconnect the MNG cables
10. Connect the PC to IFUs via ETH Y-Cable:
ODU ODU
ODU ODU

11. Verify Active IFU shows Mates IP address
12. Verify there are no Mate Communication failures
13. Complete system setup by configuring Active IFU
14. In Active IFU: click Copy to Mate and verify Mate is restarting
15. Verify there are no Configuration Mismatch alarms
16. Unlock protection on Active IFUs
17. Initiate Manual Switchover / Forced Switchover: verify traffic is OK.

EMS GUI
EMS GUI
1. Configure unique IPs to slot 1 and slot 2 (when not in installed in shelf)
2. You may use a floating IP
3. Make sure all IPs are in the same subnet

EMS GUI
Select 1+1 HSB and then click Apply
The IFU will block management for 60 seconds to allow

setting up the correct mode (Active or STBY)
This action is not traffic effective.

EMS GUI
Protection
mode
status
When2nd IFUis
properly
configuredand
connected,IP
andMACare
displayedhere

EMS GUI
Clickheretocheck
communication
withSTBYunit

EMS GUI
AdminStateLock
Toforceaswitchover
regardlessto2nd IFU
qualifyingstatus
changetoON andclick
Apply

EMS GUI
Torequestaswitchover
clickhere.
If2nd IFU(Mate)doesnotqualifytoActivestate,
requestisignored.

EMS GUI
Clickheretocopytheconfigurationfrom
ActivetoMate
Pleasenote
Thefollowingparametersarenot copied:
MNGmode(InBand/OOB)
InBandVLAN
Switchmode
license

Upgrading (1+0) to (1+1)
1. Assuming 1st link operates well, configure the 2nd IFUs to match Active IFUs:
2nd IFUs has the same HW version as Active IFU

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

ODU ODU

2. Enable Protection on Active IFUs (management will be lost for 60 sec)
3. Lock Protection on both Active IFUs (to avoid unnecessary switchover when 2nd IFU is
enabled)
4. Install 2nd IFU in each site (verify TX is muted before physical installation)
ODU ODU
ODU ODU

5. Enable protection in 2nd IFU in each site
6. Connect ETH Cross Cable between both protection ports
ODU ODU
ODU ODU
7. Disconnect the MNG cables.
8. Connect the PC to IFUs via ETH Y-Cable

9. Verify Active IFU shows Mates IP address
10. Verify there are no Mate Communication failures
11. Complete system setup by configuring Active IFU
12. In Active IFU: click Copy to Mate and verify Mate is restarting
13. Verify there are no Configuration Mismatch alarms
14. Unlock protection on Active IFUs
15. Initiate Manual Switchover / Forced Switchover: verify traffic is OK.

1+1 With Diversity
SD
Using Space Diversity

Two are better than One
As the equipment is doubled, we can use
the standby unit to receive the signal as
well
The baseband signal, after demodulation,
is transferred to the active IFU
The active IFU decides whether to use is
own signal or the signal received by the
standby unit
Valid only in a shelf installation

SD
Space Diversity
IFU 1 is active and IFU 2 is standby

IFU A is active and IFU B is standby
Both IFU A and IFU B receives the signal of IFU 1
IFU B demodulates the signal and transfer the bits to IFU A
IFU A decides whether to use the bits arrived from IFU B or is own received
demodulated bits
IFU 1 IFU A
ODU ODU
IFU 2 IFU B
ODU ODU

FD
Frequency Diversity
IFU 1 is active and IFU 2 is standby

Both IFU transmit on, each one on different frequency
IFU A receives signal of IFU 1 and IFU B receives signal of IFU 2
IFU B demodulates the signal and transfer the bits to IFU A
IFU A decides whether to use the bits arrived from IFU B or is own received
demodulated bits
IFU 1 IFU A
ODU ODU
IFU 2 IFU B
ODU ODU

Line Protection
Line Protection
Enables protection on the line interfaces (both Ethernet and Trails)
Protects both Electrical and Optical Ethernet interfaces
Line protection is Suitable for Multi Channel ABC (2+0) links

When using electrical GbE Multi Unit LAG should be used
For Ethernet traffic the link is 2+0

For TDM traffic the link is 1+1

XPAND IP+
Highly flexible redundancy options
Full protection Full protection
HW protection with Single interface using splitter +LAG using Multi-Unit LAG
using optical splitter (For switch mode) (For Smart-pipe mode)
2+0/1+1 2+0/1+1 2+0/1+1
GE GE GE GE GE GE
Optical Optical
splitter splitters
Static
Static LAG
LAG
Switch/Router Switch/Router Switch/Router
Flexible Line protection, completely independent from Radio

configuration

XPAND IP+ Multi-Unit LAG
IFU/Radio protection with dual (redundant) GE interface
2+0/1+1
Dual (redundant) GE/FE (Optical or Electrical) interfaces

to the Switch/Router
One GE/FE interface is connected to each of the IP+ units
Both interfaces are active/enabled GE GE
Static Link Aggregation Group (or equivalent) needs to be
configured on the Switch/Router interfaces connected to Static
LAG
the IP+ units
GE/FE Interfaces towards the Switch/Router on both
active and backup IP+ units are active
Switch/Router
In 2+0 ABC any failure detected in radio link (ODU or remote side)
will trigger graceful degradation and will be transparent
to the Switch/Router
Only in case of IP+ unit failure (active or standby) the connected GE/FE interface will
be disabled.
For Smart-pipe mode only

Thank You
Cross Polarization Interference Cancellation
(XPIC)
Introduction
Introduction
Two data channels are transmitted & received over the same frequency on dual
polarization (H & V)
Crosstalk between the polarizations due to imperfect antenna isolation and

channel degradation can be effectively cancelled at the receiver using -
XPIC Cross Polarization Interference Cancellation/Canceller
A
Ideal solution for frequency- crowded areas
Using one frequency for two carriers
V
H fx

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

Decoding the H signal
Each IFU accommodates 2 modems (Master and Slave)
In each site, the Main IFU communicates with the Mate IFU via the backplane
The Master modem (V) sends its signal (V) to the Mate Slave
The Mate Slave produces the interference signal (v) and sends it to its H-Master
Transmitter Receiver
HMaster H H+v HMaster H
backplane
Mate IFU v
Slave Slave
Slave Slave
backplane
Main IFU
VMaster V V+h VMaster V
5
Decoding the H signal - continued
By knowing the interference level (v), the Master Modem (H) can demodulate the
received horizontal signal (H)
The vertical channel is decoded similarly
Transmitter Receiver
HMaster H H+v HMaster H
backplane
Mate IFU v
Slave Slave
Slave Slave
backplane
Main IFU
VMaster V V+h VMaster V

Guidelines
1. XPIC is supported with IP+ IFUs in version 6.6.1 and higher
2. XPIC can only be configured in a node:
slots 1+2 and/or slots 3+4 and/or slots 5+6
3. IFU license determines the allowed script and link capacity
4. Identical configuration should be used in all IFUs participating in a link:
XPIC Script
Frequencies
SW version (IFU, ODU) If any of these conditions is not met, an
HW version (IFU, ODU) alarm will alert user. In addition, events will
Protection is disabled inform user of which conditions are not met.

XPIC Recovery Mechanism
The main purpose of the Recovery Mechanism is to recover link availability

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

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

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

avoid unnecessary TX Mute when interference is temporary (allowing
sufficient to recover)
At the end of the process, if the problem still exists, the problematic link will
be permanently muted unless the user manually un-mutes it

XPIC Recovery Mechanism
The indication to entry the recovery mechanism is a loss of modem

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

1. Recovery attempt time
2. Initial time between attempts
3. Multiplication factor for attempt time
4. Number of retries
5. Enable / Disable
Users are advised to maintain Factory Defaults
Please Note:
Every recovery attempt will cause a brief traffic hit in the working link

2+0 2U Setup
2 IFUs are installed in each node using an enclosure shelf
We assume slot 1 is using Vertical polarization and slot 2 Horizontal polarization
V+h
Each node includes
2 x ODU-SP h/v
Coupler
Dual pole antenna
H+v

6+0 6U Setup
6 IFUs are installed in each node using enclosure shelves
Possible configurations:
Slot 1 + slot 2
Slot 3 + slot 4
Slot 5 + slot 6

Multi Channel ABC Configuration
What is Multi-Channel ABC?
Allows splitting traffic from one Ethernet port

into two links in a 2+0 configuration
ABC saves the need to have an external
device to combine traffic from two Ethernet
ports in order to reach beyond 567Mb
The 2+0 configuration can be either XPIC or
different frequencies

How Does it Work?
Every byte is transmitted either over the master or the slave

The distribution is proportional to the available bandwidth in every link
If both links have the same capacity, half the data is sent through each
link
If the links use different modulations, data is distributed proportionally in
order to maximize the available bandwidth
If the links have different capacity, data is distributed proportionally in
order to maximize the available bandwidth
Slave Slave
Master Master

EMS Configuration
Logging in
Extension
Main
1. Log in to the EMS
2. Execute the following steps to Main IFU and

Extension IFU on both ends of the link
3. When configuring an IFU, make sure the relevant unit

is selected (a black line will highlight selected IFU)

Versions
Check that your IFUs and ODUs are installed with the required version
(6.6.1 or higher)

XPIC Script
Apply the required script to both IFUs (Main & Ext.) on both ends:
1. Expand the + icon next to the script in the MRMC Table

2. Click the Apply button
3. IFU will automatically restart to apply the new script

XPIC Script - 2
When IFUs complete the reset process, verify XPIC script is successfully
assigned.

XPIC Configured
Verify Main View in GUI shows icon next to IFUs

Radio Parameters
1. Verify that no alarms exist in the system.
2. Clear the defected blocks counter and verify that there are no errors in the
system.
3. Read the MSE and XPI and verify that they fit the link design (if no values
are defined, verify that they are below -34dB and above 25dB, respectively).

Radio Parameters scroll down to bottom of page
Configure Radio Parameters and verify both links (H+V) are operational

Troubleshooting
Link Commissioning
1. Make sure IF Cables are identical in length (H and V)
2. Commission the H link as a single link system with V channel muted,

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

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

in previous slides

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

RSL = -50dBm
difference (better XPI)

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

5. Un-mute the H transmitters
6. Repeat steps 1-4 for the V link

TX = OFF TX = OFF
RSL = -78dBm
In this example, the XPD is
much better:
The difference 28dB

RSL = -50dBm
That means, XPI = 28dB

XPIC Events (EMS Event Log)
During the XPIC mechanism, events are displayed in the EMS Event log to
allow detailed description and effective troubleshooting
Various cases are encoded as a single event with a bitmask code
Event title = Insufficient conditions for XPIC
Bitmask Codes -

XPIC Events (EMS Event Log)
The following events indicate changes in the XPIC state:
Remote TX Mute (try # n) was Set by XPIC Recovery on Slot # n

Remote TX Un-mute (try # n ) was Set by XPIC Recovery on Slot # n
XPIC Recovery Started on Slot # n
XPIC Recovery Finished Successfully on Slot # n
XPIC Recovery Finished Unsuccessfully on Slot # n. Remote Mute was Set
XPIC Recovery on Slot # n Stopped Due to an External Event
XPIC Recovery (XRSM) was disabled
XPIC Recovery (XRSM) was enabled

XPIC Events (EMS Event Log) - Example

XPIC Performance Monitoring

Thank You
2+2 HSB Protection
2+2 Protection Agenda
1. Topology scheme
2. Setup scheme
3. Configuration
4. Operation
5. Maintenance
6. XPIC & 2+2

2+2 HSB XPIC - Setup Scheme
STBY STBY
fL fH
H H
fL fH
V V
V V
fL H H fH
H H
fL fH
V V
Active Pair Active Pair

2+2 Configuration
The 2+2 configuration consists of two pairs of IFUs, Each pair is an 2+0 link
(can be in XPIC configuration or in different frequencies).
The two pairs are inserted into separate chassis and are connected by a
protection cable between the main IFUs in slot #1 only.
Protection is performed between the pairs - at any given time one pair is
active and the other is stand-by.
STBY
Active

2+2 Configuration
For this configuration we define the following terminology:
1.Master unit (lower IFU in each pair): in a pair belonging to a 2+2 configuration, a unit
which is responsible for the following:
Sending/receiving traffic from/to user through line interfaces
Receiving protection information from mate (slave)
Sending/receiving protection information to second master at any one time one master
is decision and the other is report.
2. Slave unit (upper IFU in each pair):

Sending/receiving traffic from/to user through line interfaces
Sending protection information to mate in shelf (master)
Slave units always behave as report (are told by master whether to be active or stand-
by)

2+2 Configuration
The 2+2 configuration is possible

only between the units in the
main backplane in each shelf
(slots 1-2).
Using the other IFUs in the

shelves (slots 3-6) is not
supported.

2+2 Configuration
When a new 2+2 protection mode is defined
A system may either be in 1+1, 2+2 or protection disabled. The configuration

is separate in each of the four units, and user should configure all four units to
2+2.
In order to switch from 1+1 to 2+2 the system must go through protection
disabled. The following table summarizes the possible changes between the
configurations:
Origin ProtectionDisabled 1+1HSB 2+2HSB

Slot#1 NoResetisrequired
Disabled NoResetisrequired NoResetisrequired
Slot#2 Resetisrequired
Slot#1 NoResetisrequired
1+1HSB NoResetisrequired Blocked
Slot#2 Resetisrequired
2+2HSB NoResetisrequired Blocked NoResetisrequired

2+2 Configuration
All the conditions for 1+1 HSB protection apply for 2+2 as well (between
master units)
While in 2+2 mode, all commands and configurations available for 1+1
protection are available as follows:
o Locking, forcing protection is done from master units only

o Copy to mate operation is available separately in master units and slave units

2+2 Operation
The principles of 2+2 operation are an extension of 1+1 protection:
The same criteria (interfaces LOS, LOC, LOF) are monitored and compared
between active and stand-by units (Comparing is carried out by master units)
All enabled interfaces of all four IFUs are monitored
A missing slave unit is interpreted as LOS in its interfaces. A missing master

is a no mate condition During 2+2 operation

2+2 Maintenance
The following procedures are relevant when changing units in a 2+2 node:
Replacing slave units (extensions)
1. Protection lockout to the Master-active.

2. Insert new unit.
3. Power it up.
4. Enable protection 2+2 HSB.
5. Copy to Mate
6. Connect the ODU to relevant Eth, PDH/SDH Y-cables/fibers.

2+2 Maintenance
The following procedures are relevant when changing units in a 2+2 node:
Replacing a STBY Master unit
1. Protection lockout to the Master-active.

2. Set to default the new card in SA mode.
3. Reset.
4. Configure same management type (in/out of band), management VLAN and Ethernet
application.
5. Insert the unit.
6. Power it up.
7. Connect the protection cable.
8. Enable protection 2+2 HSB.
9. Copy2mate.
10. Connect the ODU to relevant Eth, PDH/SDH Y-cables/fibers.

XPIC & 2+2 Protection
2+2 XPIC is a common application.
Since these two are unrelated mechanisms, a number of safeguards have

been put in place to assure their proper operation in tandem.
When configured as 2+2, the XPIC recovery mechanism is disabled.
The reason for this is that in case of a failure in a link, the system will switch to
the stand-by pair instead of attempting to recover the link, as done in 2+0
XPIC.
Additionally, in order to assure that the conditions for XPIC exist (in particular
having the same radio script and frequencies), the following mechanisms are
active in a 2+2 configuration:

XPIC & 2+2 Protection
The following parameters can be changed only at the master unit; they will be
automatically changed at the slave unit accordingly:
Radio script
Radio TX frequency
Radio RX frequency
Should the change at the slave unit fail for any reason, the change at the
master will be rolled back and user will be given an error message.

Thank You
EMS Performance Monitoring
Agenda
General Information
Faults:
Current Alarms
Alarm Editing
Event Log
PM & Counters:
Remote Monitoring
TDM Trails
TDM interfaces
Radio (RSL, TSL, MRMC and MSE)
Radio TDM
Radio ETH
XPI

General Information
Maximum frame length:
1632 bytes for all Ethernet traffic interfaces
WSC interface is limited to 1628 bytes
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
For this mechanism to work properly, each TDM trail in both sides of a link
should be associated with the same priority.
Overhead bytes:
Proprietary frame is constructed to transport the ETH and TDM (E1/DS1) traffic.
Frame size depends on the system type (capacity).
The frame consists 18 bytes for overhead, and bytes for Ethernet and E1/DS1s
payload.

EMS Main View
Access application via IP address
User friendly navigation menu

EMS Main View
Graphical MENU: Click to configure

EMS Main View
Protection Status Display & Quick Access

Icons

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

for configuration

EMS Main View
When the user selects Slot 2 the GUI updates automatically
8
Faults Current Alarms
The Current Alarms window shows collapsed list of alarms
By expanding a line we can see additional information:
Probable cause
Corrective Actions
9
Faults Event Log
The Event Log shows max. 200 lines of events
When Event #201 occurs, Event #1 is erased and #201
is logged as #200.

Available PM Statistics - Radio
TDM PM
(allocated E1/T1 VCs)
TDM
(E1/T1)
ETH PM (Data + In-Band):

1.Aggregated Errors STM1
2.Throughput STM-1 PM
3.Capacity
4.Radio Link Utilization When STM-1 T-Card
5.RMON standard is is inserted in front
implemented as well to provide panel)
detailed data
Radio Signal PM:
ETH BW is a function of 1.RSL
available radio capacity as TDM 2.MSE
and STM-1 have higher priority 3.MRMC (ACM)
4.Aggregate
11
Available PM Statistics Line Interfaces
STM-1 interface facing customer equipment

TDM interfaces facing customer equipment
End-to-End Trails
12
Clearing previous data
To erase all IFU PM data, click the CLEAR button -
13
ETH PM RMON
The system supports Ethernet statistics counters (RMON) display (depends on
port availability). The counters are designed to support:
RFC 2819 RMON MIB.

RFC 2665 Ethernet-like MIB.
RFC 2233 MIB II.
RFC 1493 Bridge MIB.
14
ETH PM RMON
15
PM RMON Special Registers
RMONregister/Counter Description
Undersizeframesreceived Framesshorterthan64bytes
Oversizeframesreceived Frameslongerthan1632bytes
Totalframesreceivedwithalengthofmorethan1632bytes,
Jabberframesreceived
butwithaninvalidFCS
Totalframesreceivedwithalengthoflessthan64
Fragmentsframesreceived
bytes,andaninvalidFCS
Rxerrorframesreceived TotalframesreceivedwithPhyerror
TotalframesreceivedwithCRCerror,notcounteredin
FCSframesreceived
"Fragments","Jabber"or"Rxerror"counters
Countsgoodframesthatcannotbeforwardeddueto
InDiscardFrames
lackofbuffermemory
Countsgoodframesthatwerefilteredduetoegress
InFilteredFrames
switchVLANpolicyrules
Pauseframesreceived Numberofflowcontrolpauseframesreceived
16
Troubleshooting with RMON: Filtering
Example
Radio port is a Radio port is a
Site A member of VID 100 member of VID 100 Site B
A Tagging T No membership
T A
Untagged Frames Access port with

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

frame size > 1632 bytes
When ingress frames exceed the maximum frame size, RMON counter Oversized frames
received is updated accordingly
18
Troubleshooting with RMON: Discarding Example
Site A Site B
T T T A
Ingress traffic does not

comply to Policer rules
Discarding Examples:
Ingress rate > Rate Limiter

Ingress frames do not qualify to Policer rules
19
Troubleshooting with RMON: Monitoring specific
traffic types
Site A Site B
Rate Limiter
T T
Monitor
Video streams are generally transmitted over UDP

with multicast addresses
To monitor traffic, check out the Multicast Frames

Received register
To limit MC traffic, assign a Policer with a UDP & MC

CIR rules
20
PM TDM Trails
Trails can only be configured in the Main

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

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

Main IFU menu
The number of trails that can be

configured is a function of available radio
BW (license + script)
21
PM TDM Trails
22
PM TDM Trails In Detail
Errored Second (ES):
A one-second period with one or more errored blocks or at least one defect
23
Severely Errored Second (SES):
A one-second period, which contains 30% errored blocks or at least one

defect.
SES is a subset of ES.
24
A period of unavailable time begins at the onset of 10 consecutive Severely

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

events. These 10 seconds are considered to be part of available time.
25
Background Block Error (BBE):
An errored block not occurring as part of a SES.
26
Number of Switches (only relevant for Protected SNCP Trails):
The number of times the IP+ switched from Primary Path to Secondary Path
and vice versa (per 15min or 24hrs interval)

Active Path Seconds (only relevant for Protected SNCP Trails):
The number of times seconds the Active Path was available

Integrity:
Indicates whether information is reliable for analysis (ticked) or not
For example if clock was changed or system was restarted during this interval
then information is not reliable
29

PM TDM Trails through Radio
30
PM E1 / DS-1 (PM received from customer)
This PM data
relates to the
TDM Line
Interfaces.
31
PM STM-1 (Slot #2)
32
PM Radio - RF
Signal Level RSL & TSL analysis
Allows setting RSL & TSL thresholds

EMS will notify when signal exceeds THSLD
>> Easier maintenance
Aggregated radio traffic analysis
MRMC PM related to ACM:
Associated Script
Available Bit rate
Available Radio VCs
MSE analysis (quality of received signal)

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

Level 1: 25 sec
Level 2: 15 sec
900 sec = 15min Interval
34
PM Radio Signal Level - Using Threshold
Using graphical display of the THSLD analysis allows us easier

examination of the RSL & TSL state throughout certain period of time
RSL
-40
-50
-68
-99 T [sec]
10 5 10
35
PM Radio - Aggregate
Aggregated radio
traffic analysis
36
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.
37
PM Radio - MRMC
38
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.
39
PM Radio - XPI
Use this report to evaluate the cross-polarization

interference
Apply a threshold to establish a better notification
40
PM Radio - Ethernet
Frame Error Rate (%) measured on radio-Ethernet
interface (port 8)
Ethernet Capacity (a.k.a. Ethernet L1 capacity) - Total

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

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

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

accumulating the number of Ethernet octets every
second
Accurate analysis requires accumulating a full interval

(15min/24hrs)
41
PM Ethernet Frame Error Rate
42
PM Ethernet Throughput
43
PM Ethernet Capacity
44
PM Ethernet Utilization
45
Throughput / Capacity / Utilization
To better understand these terms, we shall examine the Ethernet tagged frame full
structure:
A frame viewed on the actual physical wire would show Preamble and Start Frame
Delimiter, in addition to the other data (required by the physical hardware).
However, these bits are stripped away at OSI Layer 1 by the Ethernet adapter before
being passed on to the OSI Layer 2 which is where data is detected.
Pre. SFD DA SA VLAN ETHType Payload+ CRC Interframe

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

octets octets
DataRate:min.64octets max.1522octets
Physicalwirerate:min.84octets max.1542octets
46
Pre. SFD DA SA VLAN ETHType Payload+ CRC Interframe

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

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

Stripped bits = ~ 23% of physical transmitted rate (20/84=0.23)
Hence, when we transmit 100Mbps, the actual throughput would be 77 Mbps
47
Throughput = 77 Mbps
Radio Capacity =
(license) = 400Mbps
Transmitted rate = Capacity = Received frame rate

100 Mbps = 100 Mbps
Throughput 77 Mbps
Utilization = = = 19.25% ~ 20%
Capacity 400 Mbps
48
Thank You
Loopbacks
Agenda
In this module we shall describe

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

ODU RF Loopback
ODU RF LB

ODU 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)
ODU LED is RED when Loopback is ON
LINK LED is GREEN when Loopback is ON

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):

IF Loopback Analysis using Event Log
Lets assume radio link is down LINK LED is RED
16:29:01 We enable IF LB, therefore Link alarms clear
16:29:05 Loopback replaces remote unit therefore alarm disappears
16:30:01 Loopback automatically stops, link recovers to original state
16:30:05 Radio link is down (original state)

PDH Line LB towards Line (NE)
LB towards the line

PDH Line LB towards Line (Near End)
Use this feature to evaluate connection to customers patch-panel
Alarm is displayed in CAS:
and in Event Log:

PDH Line LB towards Radio (FE)
LB towards the radio
Tester

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

SDH Line LB towards System
Towards System signal (trail) is looped back to IP+

SDH Line LB towards Line
Towards Line signal (trail) is looped back to
customer interface

IFU-ODU 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

Thank You
Configuration Files
Agenda
In this module we shall describe the various actions we can perform to

properly maintain and troubleshoot the XPAND IP+ system:
1.Configuration File
2.Unit Information File
3.Setting FTP Properties
4.Upload/Download in a Standalone IFU
5.Upload/Download in a Node

Configuration File
The Configuration file stores the following parameters:
Backup
y our
License service
External Alarms s !
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:
Backup
y our
Date & Time
Logs !
Daylight Saving Time properties
System name and other ID parameters
Measuring properties (voltage, temperature)
Accumulated Performance Monitoring logs
Serial numbers

FTP Properties
Local FTP Server
You may install FTP Server on your PC and connect locally to the IFU

Remote FTP Server
You may configure the IFU to communicate with a remote PC where

FTP server is installed
E
FIL
G
CF
Remote FTP Server
l oad
Up load
o wn
D
EMS PC

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
Upload/Download Using Stand Alone IP+
10
Uploading the CFG File (IP+ to Server)
Click Create Archive to

allow the IP+ zipping all
parameters into one file

Wait till task is successfully

completed

Next step:
Click Upload Archive to allow
the IP+ transferring the zipped
file to your server

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)

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

Downloading the CFG File (Server IP+)
Follow the same steps to download the CFG file
When download completes successfully, you will need to restart the

system for changes to take place
Please note if the file does not exist in the root directory action will fail !
1 2
Upload/Download in a Node
Step #1: Creating CFG files
The Main unit can store the

CFG files of each slot
Select the IFU(s) and click

Backup
Slot 4
Slot 3
Slot 2
Slot 1

Step #2: Upload CFG files
Next, click Upload

Archive(s) and the
file(s) will be uploaded
to your FTP root
directory

Step #3: Downloading files to slot(s)
Click Download to send the

CFG files from your FTP root
directory onto each IFU
Slot 4
CFG file
Slot 3
Slot 2
Slot 1
Do
w nlo
CF ad
G
f il e
s

Step #4: Restoring IFU(s)
Assuming Main IFU stores the
most updated CFG files, when
clicking Restore, the Main
IFU will download the files to
relevant IFUs
Slot 4
CFG file
Slot 3
Slot 2
Slot 1
Re
sto
re

Unified Unit Information File
A unified file is created for

all stacked units
Upload & Download

action are identical to a
standalone unit

Checking Backup History & Status
Click here to see the

backup history

Checking Backup History & Status

Setting the unit back to Factory Defaults
You can restore your system to

factory defaults
You may also set the IP address to

factory default address (192.168.1.1)
Thank You
Software Upgrade
Agenda

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

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

FTP Root Directory
Make sure you are familiar with your FTP Root Directory: this is where
the files are stored (software versions, CFG & Unit).
Examplesfor
SWpackages

Configuring FTP Server Properties
2
Configuring FTP Server Properties
Type the location of the software package:

FTP IP address
SW folder (when relevant, in this example 66253)
Type the username & Password

(You may log in using CMD window to verify settings are correct)

Software Upgrade Standalone XPAND IP+
Standalone SW Download
Click on the Download button and wait till Succeeded message is

displayed (next slide)
Youmayviewatanytimethedownload
processbyclickingontheLogIcon

Standalone SW Download
Download was successfully completed, you may proceed to upgrade
the IFU

Download completed Upgrade delayed
In case Upgrade is scheduled for later moments, the Version table will
display the following status:

Standalone Upgrade Regular
Click on the Upgrade button. When upgrades completes successfully,
the IFU will restart automatically.
Youmayviewatanytimetheupgrade
processbyclickingontheLogIcon

Standalone Upgrade - Timed
Choose in Installation Type Timed option, after that you can set time
for later scheduled upgrade
Youcansetscheduletimefrom1minup
to1440min(24hour)andclicktoApply

Standalone Upgrade Regular vs. Timed
Click on Upgrade to start schedule timer, you can see Timer Status,
anytime you can abort scheduled installation

Software Upgrade Nodal XPAND IP+
Nodal SW Download
Important note !
IP+ systems with software version 3.0.34 must be upgraded to an

officially released version while in stand-alone mode (not in shelf
configuration) prior to a Shelf (Nodal) SW download

Shelf Configuration
1. Make sure your main unit (Slot 1) is upgraded with the latest version
2. If not, it is recommended to upgrade the main unit as a standalone IFU
3. Verify you are familiar with the slot number(s)
Slot 6
Slot 5
Slot 4
Slot 3
Slot 2
Slot 1

Shelf SW Download
Configure the FTP properties if needed
Click on the Download button and

wait till Succeeded message is
displayed
You may view at any time the download

process by clicking on the Log Icon

Shelf SW Upgrade
Select the target slot and then click the

Upgrade button
Or click Upgrade All
Please note
1.The number of slots depend on actual

configuration
2.The slot numbers are not according to

physical allocation in the shelf
3.Failures may occur due to wrong FTP

configurations, unstable network
connection or missing files
4.IFU(s) will reset automatically upon

successful upgrade
Rollback vs. Downgrade
Rollback VS. Downgrade
1 2
Upgrade #1 Upgrade #2
2.8.25 2.8.31 2.8.35
2.8.32
Rollback 4 3
Downgrade
Rollback does not revert previous Downgrade operation !
It rolls back IFU version 1 step back (prior to last Upgrade)

Thank You

XpandIP+ Basic Course

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

XpandIP+ Basic Course

Transféré par

Droits d'auteur :

Formats disponibles

Evo XPAND IP+ Introduction

Gigabit ACM XPIC ChSTM1/

Proprietary and Confidential

Unique Adaptive Coding & Modulation (ACM)

Metro/Managed switch mode Smart pipe mode

Carrier Ethernet (MW links) SDH/SONET (Hybrid Fiber/MW)

Carrier Ethernet (MW links) IP/MPLS (Hybrid Fiber/MW)

Ethernet IP/MPLS edge router

More granular service

High granularity traffic management

Enables differentiated services with strict SLA

Proprietary and Confidential

y Same 1RU XPAND IP+ unit can be used

y The solution is stackable and modular

y Forms a single unified nodal device

y Common E1/DS1s Cross Connect

y Single element to manage

Full compatibility with XPAND IP+ (R2)

RF Link Basic Components

A Radio Link requires two end stations

Advantages (compared to alternative cable/fiber infrastructure) :

RF - System of communication employing electromagnetic waves (EMW)

Raindrops have sizes ranging from 0.1 millimeters to 9 millimeters mean

Large rain drops become

Electromagnetic signal propagating in a physical medium is degraded

Low frequencies have longer wavelength and refract less

Deflection of the beam towards the ground due to different electrical

Refers to scenarios where signal is absorbed by rain, snow, ice

Heavier rain >> Heavier Atten.

Higher FQ >> Higher Attenuation

Antennas are devices used to radiate electromagnetic energy into space.

OMNI-DIRECTIONAL antennas radiate & receive energy from all directions

DIRECTIONAL antennas radiate energy in LOBES (or BEAMS) that extend

Microwaves travel in straight lines - it can be focused and reflected just as

Because of the special shape of a parabolic

RSL=TX TXLoss +GainAnt1 LFreeSpace +GainAnt2 RXLoss

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

A low frequency that comprises the message (baseband) is translated to a

Modulation allows higher data rate transmissions

The process of modulation is reversible.

A device that performs modulation is known as a modulator and a device that

Low fq. Signal (up) +

Quadrature Phase Shift Keying is a phase modulation algorithm

The phase of the carrier wave is modulated to encode bits of digital

Quadrature Amplitude Modulation employs both phase modulation (PM) and

In 64QAM, each six bits generates 64 modulation states; in 128QAM, each

Diagram for 8QAM: 3bit represent 8 different states

Bitsequence Amplitude Phase(degrees)

Constellation diagram for 16QAM:

Constellation diagram for 128QAM:

Higher QAM order results in a higher

This is why we modulate

Constellation of 256QAM with noise added Constellation of 256QAM

Lets go over the front panel connections of the XPAND IP+

Lets explain them one by one

DB9 Craft Line Interface (CLI)

Engineering Order Wire

To communicate with your colleague on the

DB9 Dry Contact External Alarms

The input alarms are configurable according to:

The output alarm is configured according to predefined categories

LINK: GREEN radiolinkisoperational

ODU: GREEN ODUfunctionsok

PROT: Main unit GREEN (when there no alarms)