Handbook - FibeAir IP-20G Advanced Training Course T7.9 Ver1 PDF

Ceragon Course Handbook
COURSE HANDBOOK
Commissioning | Installation | System Configuration
FibeAir IP-20G Advanced Training Course

Updated for T7.9
Visit our Customer Training Portal at training.ceragon.com or contact us at training@ceragon.com
Trainee Name: _________________
December
www.ceragon.com
2014
Copyright 2012 Ceragon Networks Ltd. cts.ceragon.com
FibeAir IP‐20G Ceragon Training Course
Table of Content
Intro to Radio Systems ………………………………………………………………………………………………………… 005
Introduction to Ethernet ……………………………………………………………………………………………………… 029
IP‐20G Overview………………………………………………………………………………………………………………….. 047
Radio Frequency Units…………………………………………………………………………………………………………. 061
IP‐20G Installation Guide…………………………………………………………………………………………………….. 077
First Login…………………………………………………………………………………………………………………………... 103
Radio Link Parameters…………..…………………………………………………………………………………………… 115
ACM & MSE….…………………………………………………………..…………………………………………………………. 121
Automatic Transmit Power Control – ATPC………………………………………………………………………… 133
IP‐20G Licensing………………………………………………………………………………………………………………… 139
Service Model in IP‐20………………………….……………………………………………………………………………. 149
Quality of Service ‐ QoS …………………………………………………………..………………………………………. 173
XPIC Configuration……………………………….…………………………………………………………………………….. 199
Protection System Configuration……………………………………………………………………………………….. 207
Configuration Management & Software Download…………………………………………………………… 215
Native TDM ………………………………………………………………………………………………………………………… 229
TDM Pseudowire………………………………………………………………………………………………………………… 243
Troubleshooting………………………………………………………………………………………………………………….. 365
MSTP…………………………………………………………………………………………………………………………………. 283
G.8032……………………………………………………………………………………………………………………………….. 305
Synchronous Ethernet ‐ Sync E…………………………………………………………………………………………… 325
Security Features………………………………………………………………………………………………………………… 339
Link Layer discovery Protocol ‐ LLDP …………………………………………………………………………………… 347
Frame Cut‐Through …………………………………………………………………………………………………………….. 351
Cascading Port ……………………………………………………………………………………………………………………. 355
Automatic State Propagation……………………………………………………………………………………………… 361
CERAGON TRAINING PROGRAM – IP‐20G Advanced Training Course Sw 7.9

Page 3
FibeAir IP‐20G Ceragon Training Course

Link Aggregation Group ‐LAG…………………………………………………………………………………………….. 365
Course Evaluation Form………………………………………………………………………………………………………. 373
CERAGON TRAINING PROGRAM – IP‐20G Advanced Training Course Sw 7.9

Page 4
Introduction to Radio Systems
October 2014
Version 3
Agenda
• Radio Relay Principles
• Parameters affecting propagations:

• Dispersion
• Humidity/gas absorption
• Multipath/ducting
• Atmospheric conditions (refraction)
• Terrain (flatness, type, Fresnel zone clearance, diffraction)
• Climatic conditions (rain zone, temperature)
• Rain attenuation
• Modulation
2 Proprietary and Confidential
Page 5
Digital Transmission Systems
Radio Relay Principles
f1
RF Signal
f1’
Path Terrain
• 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
Page 6
High and Low frequency station
Tx(f1)=11500 MHz Rx(f1)=11500 MHz

Full duplex
Local site Remote site
High station Low station
Rx(f1’)=11000 MHz Tx(f1’)=11000 MHz
High station means: Tx(f1) >Rx(f1’)
Low station means: Tx(f1’) < Rx(f1)
Standard frequency plan patterns

Only Low stations can interfere High stations
Frequency reuse:
Low 1,3V High 1,3V Low High
1,3H 1,3H 1,3H
Tx Tx Tx Tx Tx
Reduced risk for overshoot
Frequency shift:
1,3H 1,3V 2,4V 2,4H 1,3H
Tx Tx Tx Tx Tx
Tx Tx in upper part of band

Reduced risk for overshoot Tx Tx in lower part of band
Page 7
Preferred site location structure
Radio Principal Block Diagram
Input
signal
Z' E' A' B' C' D'
Digital Branching
Modulator Transmitter RF Tx Filter Feeder
Line interface Network(*)
TRANSMITTER PATH
D C B A E Z
Branching RF Rx Filter Demodulator Digital
Feeder Receiver
Network(*) Line interface Output
signal
RECEIVER PATH
Page 8
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  waves in vacuum (3x108 m/s)
f
• Microwave – refers to very short waves (millimeters) and typically

relates to frequencies above 1GHz:
 300 MHz ~ 1 meter
 10 GHz ~ 3 cm
RF Principals
• We can see the relationship between colour, wavelength and amplitude
using this animation
Page 9
Radio Spectrum
Parameters Affecting Propagation
12
Page 10
• Dispersion
• Humidity/gas absorption
• Multipath/ducting
• Atmospheric conditions (refraction)
• Terrain (flatness, type, Fresnel zone clearance, diffraction)
• Climatic conditions (rain zone, temperature)
• Rain attenuation
Parameters Affecting Propagation – Dispersion

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

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

characteristics of the atmosphere’s is called Dielectric Constant.
• The dielectric constant depends on pressure, temperature &
humidity in the atmosphere, parameters that are normally decrease
with altitude
• Since waves travel faster through thinner medium, the upper part of the
wave will travel faster than the lower part, causing the beam to bend
downwards, following the curve of earth
With Atmosphere
No Atmosphere
Wave in atmosphere
Page 12
Parameters Affecting Propagation – 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
Parameters Affecting Propagation – 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
Page 13
Parameters Affecting Propagation - 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
Parameters Affecting Propagation – 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)
Page 14
Parameters Affecting Propagation – Rain Fading
Heavier rain >> Heavier Atten.
Higher FQ >> Higher Attenuation
Parameters Affecting Propagation – 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
Page 15
Parameters Affecting Propagation – Fresnel Zone
• Obstacles in the first Fresnel zone will create signals that will be 0 to 90 degrees out
of phase…in the 2nd zone they will be 90 to 270 degrees out of phase…in 3rd zone,
they will be 270 to 450 degrees out of phase and so on…
• Odd numbered zones are constructive and even numbered zones are destructive.
• 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.
Example: First condition
Page 16
RF Link Basic Components – Parabolic Reflector Radiation (antenna)
RSSI Curve for RFU-C
1,9V
1,6V
1,3V
-30dBm -60dbm -90dBm
Page 17
Main Parabolic Antenna Types
• Standard performance antennas (SP,LP)

• Used for remote access links with low capacity. Re-using frequencies on adjacent links is not
normally possible due to poor front to back ratio.
• High performance antennas (HP)
• Used for high and low capacity links where only one polarization is used. Re-using
frequencies is possible. Can not be used with co-channel systems.
• High performance dual polarized antennas (HPX)
• Used for high and low capacity links with the possibility to utilize both polarizations. Re-using
frequencies is possible. Can be used for co-channel systems.
• Super high performance dual polarized antennas (HSX)
• Normally used on high capacity links with the possibility to utilize both polarizations. Re-using
frequencies is possible with high interference protection. Ideal for co-channel systems.
• Ultra high performance dual polarized antennas (UHX)
• Normally used on high capacity links with high interference requirements. Re-using
frequencies in many directions is possible. Can be used with co-channel systems.
Passive Repeaters
Back-to-back
antennas
Plane
reflector
Page 18
Link Calculation – Basic Example (in vacuum)
Lfs
TSL Ga Lfsl Ga Lw
RSL ‐ Received Signal Level
Lb
TSL – Transmitted Signal Level
Lfsl ‐ Free‐space loss = 92.45 + 20 log x(distance in km x frequency in GHz)
Lf ‐ Filter loss
Lf
Lb ‐ Branching loss
Lw ‐ Waveguide loss
Ga – Antenna gain RSL
RSL=TSL+Ga‐Lfsl+Ga‐Lw‐Lb‐Lf
Atmospheric attenuation
Starts to contribute to the total attenuation above approximately 15GHz
Aa   a  d [dB]
Parameters in a:
 Frequency
 Temperature
 Air pressure
 Water vapour
Page 19
Objective examples
• Typical objectives used in real systems
• 99.999%
• Month: 25.9 sec
• Year: 5 min 12 sec
• 99.995 %
• Month: 2 min 10 sec
• Year: 26 min
• 99.99%
• Month: 260 sec
• Year: 51 min
• Performance requirements generally higher than Availability.

• ITU use worst month for Performance Average year for Availability
Modulation
32
Page 20
Modulation
Modulation
Analog Digital
Modulation Modulation
AM - Amplitude modulation ASK – Amplitude Shift Keying

FM - Frequency modulation FSK – Frequency Shift Keying
PM – Phase modulation PSK – Phase Shift Keying
QAM – Quadrature Amplitude modulation
Digital modulation
1 0 1 1 0 1 1 0
1 0 1 1 0 1 1 0 ASK modulation changes the amplitude to the analog

Modem signale.”1” and “ 0” have different amplitude.
1 0 1 1 0 1 1 0
1 0 1 1 0 1 1 0
PSK modulation changes the phase to the transmitted
Modem
signal. The simplest method uses 0 and 1800 .
1800 phase shift
1 0 1 1 0 1 1
1 0 1 1 0 1 1 0 FSK modulation is a method of represent the two

Modem binary states ”1” and ”0” with different
spcific frequencies.
F1 F2 F1 F1 F2 F1 F1
Page 21
QAM Modulation
• Quadrature Amplitude Modulation employs both phase modulation
(PSK) and amplitude modulation (ASK)
• The input stream is divided into groups of bits based on the number
of modulation states used.
• In 8 QAM, 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 64 QAM, each six bits generates 64 modulation states; in 128
QAM, each seven bits generate 128 states, and so on
4QAM 2bits/symbol 256QAM 8bits/symbol

64QAM 6bits/symbol
128QAM 7bits/symbol
Why QAM and not ASK or PSK for higher modulation?

• This is because QAM achieves a greater distance between adjacent points
in the I-Q plane by distributing the points more evenly
• The points on the constellation are more distinct and data errors are
reduced
• Higher modulation >> more bits per symbol
• Constellation points are closer >>TX is more susceptible to noise
Page 22
Constellation diagram
• In a more abstract sense, it represents the possible symbols that may be
selected by a given modulation scheme as points in the complex plane.
Measured constellation diagrams can be used to recognize the type of
interference and distortion in a signal.
8 QAM Modulation Example

We have stream: 001-010-100-011-101-000-011-110
DIGITAL QAM (8QAM)
Bit sequence Amplitude Phase (degrees)

000 1 None
001 2 None
010 1 pi/2 (90°)
011 2 pi/2 (90°)
100 1 pi (180°)
101 2 pi (180°)
110 1 3pi/2 (270°)
111 2 3pi/2 (270°)
How does constellation diagram look?
Page 23
4QAM VS. 16QAM
4QAM 16QAM
2048 QAM
Page 24
Bandwidth vs. Modulation
2-PSK
4-PSK
Modulation Bandwidth
Complixity Decreases
Increases 8-PSK
16-QAM
64-QAM
Signal / Noise
• Example: S/N influence at QPSK Demodulator
• Each dot detected in wrong quadrant result in bit errors
BER≈0 BER<10-13 BER=10-6 BER=10-3

Signal
Signal
S/N Signal
Power
Power
Power
Power
S/N Signal
S/N S/N
Noise Noise Noise Noise
Page 25
BER Impact on Transmission Quality
10 -3
10 -4
10 -5
BER change ratio vs. Noise is
dependent on Noise Power distribution
and coding
10 -6
10 -7
BER

10 -8
-75 -72 -69 -66
Receiver input level [dBm ]
RSL Vs. Threshold

RSL (dBm) BER>10-6
-20
-30 Nominal Input Level
Fading Margin
-73 Threshold level BER=10-6
BER>10-6 S/N=23dB for 128QAM (37 MHz)

-96 Receiver amplifies thermal noise
-99 K – Boltzmann constant

T – Temperature in Kelvin
Thermal Noise=10*log(k*T*B*1000) B – Bandwidth
Time (s)
Page 26
Thank you
45
Page 27
Page 28
Introduction to Ethernet
November 2014
Version 3
Agenda
• Local Area Network (LAN)
• Network Devices
• OSI Layers
• Ethernet Frame
• VLAN concept
Page 29
The Local Area Network (LAN)
Network Devices
The various devices used to build a data communication network can be classified into type of
equipment depending on how Ethernet packets are forwarded.
ROUTER
BRIDGE / SWITCH
HUB
Page 30
Functions of OSI layers
OSI model layers
Application Type of communication: e-mail, file transfer, web browsing
Presentation Encryption, data conversion: ASCII to EBCDIC, BCD to binary et.
Session Starts, stops sessions. Maintains order
Transport Ensure delivery of entire file or message
Network Routes data to different LANs and WANs based on network addresses
Data Link Transmits packets from node to node based on station address
Physical Electrical signals and cabling (physical medium)
Protocols in OSI layers
OSI model layers
Application HTTP, FTP, IRC, SSH, DNS, SNMP
Presentation SSL, SFTP, IMAP, SSH, Jpeg, GIF, TIFF, MPEG, MIDI, mp3
Session VARIOUS API’S, SOCKETS
Transport TCP, UDP, ECN, SCTP, DCCP
Network IP, IP Sec, ICMP, IGMP
Data Link Ethernet, Token Ring, SLIP, PPP, FDDI
Physical Coax, Fiber, Wireless
Page 31
Ethernet frame
OSI and TCP/IP model

OSI model OSI model
TCP/IP model
layers layers
Application Protocol
Application Application
Presentation Protocol
Presentation Presentation
Application DATA
Session Protocol
Session Session
Transport Transport TCP/UDP DATA Transport
Internet Network IPv4/6 TCP/UDP DATA Network
MPLS IPv4/6 TCP/UDP DATA

Layer 2,5 Layer 2,5 Layer 2,5
E
Data Link MAC S‐VLAN C-VLAN MPLS L IPv4/6 TCP/UDP DATA FCS Data Link
Network
Interface Physical P SFD MAC S‐VLAN C-VLAN MPLS
E
L
IPv4/6 TCP/UDP DATA FCS Physical
Size in bytes: 7 1 12 4 4 4 2 20/40 20/8 4
P Preamble TCP Transmission control protocol

46-1500
SFD Start frame Delimiter UDP User datagram protocol
MAC = Destination + Source MAC Address FCS Frame check sequence
EL Ether Length/Type
VLAN Virtual local area network
MPLS Multiprotocol Label Switching
IP Internet protocol
Page 32
L2
L3
Page 33
L4
UDP Header
TCP Header
Inter-frame gap
Ethernet works in Layer 1, Layer 2 and “Layer 2,5”
Page 34
TCP Protocol
13
Transmission Control Protocol
A TCP packet walks into a bar and

says, “I’d like a beer.”
The bartender replies, “You want a

beer?”
The TCP packet replies, “Yes, I’d

like a beer.”
Page 35
Transmission Control Protocol
TCP- Segment format
Page 36
TCP- Control field
TCP- Connection establishment using three-way handshake
Passive
Active open
open seq: 8000
UAPRS F
SYN
seq: 15000
Connection ack: 8001
opened nd: 5000
U A P R S F rw
SYN + ACK
seq: 8000
ack: 15001
UAPRS F
rwnd: 10000
ACK
Means “no data” !
seq: 8001 if piggybacking
Page 37
TCP- Numbering System
• The bytes of data transferred in each connection are numbered.
Numbering starts with an arbitrarily generated number.
• The value in the sequence number field of a segment defines the

number assigned to the first data byte contained in that segment.
• The value of the acknowledgment field in a segment defines the

number of the next byte expected to be received.
TCP- Data Transfer
seq: 8001
Send
request ack: 15001
UAPRSF
Data Receive
bytes: 8001-9
000
Send seq: 9001

request ack: 15001
UAPRS F
Data Receive
bytes: 9001-1
000 0
seq: 15001 Send

ack: 10001 request
U A P R SF
Data
17000
bytes: 15001-
seq: 10000
ack: 17001
UAPRS F
rwnd:10000
Connection Termination
Page 38
TCP- Connection termination using three-way handshake
TCP- Congestion Control:

Slow start, exponential increase
1
cwnd
RTT
2
cwnd
RTT
4
cwnd
RTT
8
cwnd
Page 39
TCP- Congestion Control:
Congestion avoidance, additive increase
TCP- Congestion example
Page 40
TCP- Calculating maximum throughput of one TCP stream
TCP window size [Bytes] = Bandwidth [bps] * RTD [Sec] /8
* Example:
TCP ideal window size = 1*109*30*10-3/8 = 3.75MBytes
VLAN concept
Page 41
Virtual Local Area Network (VLAN) concept
• Imagine that you have a network and three different customer
• Customer 1
• Customer 2
• Customer 3
NETWORK
Virtual Local Area Network (VLAN) concept
VLANs are created to provide the segmentation services traditionally provided by routers
in LAN configurations
The most common protocol used today in configuring virtual LANs is IEEE 802.1Q
Page 42
OSI and TCP/IP model
OSI model OSI model
TCP/IP model
layers layers
Application Protocol
Application Application
Presentation Protocol
Presentation Presentation
Application DATA
Session Protocol
Session Session
Transport Transport TCP/UDP DATA Transport
Internet Network IPv4/6 TCP/UDP DATA Network
MPLS IPv4/6 TCP/UDP DATA

Layer 2,5 Layer 2,5 Layer 2,5
E
Data Link MAC S‐VLAN C-VLAN MPLS L IPv4/6 TCP/UDP DATA FCS Data Link
Network
Interface Physical P SFD MAC S‐VLAN C-VLAN MPLS
E
L
IPv4/6 TCP/UDP DATA FCS Physical
Size in bytes: 7 1 12 4 4 4 2 20/40 20/8 4
P Preamble TCP Transmission control protocol

46-1500
SFD Start frame Delimiter UDP User datagram protocol
MAC = Destination + Source MAC Address FCS Frame check sequence
EL Ether Length/Type
VLAN Virtual local area network
MPLS Multiprotocol Label Switching
IP Internet protocol
Ethernet frame
Page 43
Untagged Ethernet Frame
FCS is created by the sender and recalculated by the receiver
Preamble + SFD DA SA Length / Type DATA + PAD FCS
4 Bytes
8 Bytes 6 Bytes 6 Bytes 2 Bytes 46 - 1500 Bytes (32-bit
CRC)
Minimum 64 Bytes < FRAME SIZE < Maximum 1518 Bytes
Length / Type < 1500 - Parameter indicates number of Data Bytes

Length / Type > 1536 - Parameter indicates Protocol Type (PPPoE, PPPoA, ARP etc.)
Tagged Ethernet Frame
• Additional information is inserted

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

TPID = Tag protocol ID
3 Bit 1 Bit 12 Bit
TCI = Tag Control Information
CFI = 1 bit canonical Format Indicator
Page 44
Tagging a Frame
VLAN ID uses 12 bits, therefore the number of maximum VLANs is 4096:

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

Protocol type Value
TPID in tagged frames in always set to
0x8100 Tagged Frame 0x8100
ARP 0x0806
It is important that you understand the Q‐in‐Q (CISCO) 0x8100
meaning and usage of this parameter Q‐in‐Q (other vendors) 0x88A8
Q‐in‐Q (other vendors) 0x9100
Q‐in‐Q (other vendors) 0x9200
RARP 0x8035
IP 0x0800
IPv6 0x86DD
PPPoE 0x8863/0x8864
MPLS 0x8847/0x8848
IS‐IS 0x8000
LACP 0x8809
802.1x 0x888E
Page 45
Q-in-Q
• Additional VLAN (S-VLAN) is inserted

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

3 Bit 1 Bit 12 Bit 3 Bit 1 Bit 12 Bit
Thank you
36
Page 46
IP-20G Overview
December 2014
Version 3
Agenda
• FibeAir IP-20 Product Family
• Network topology with IP-20G
• IP-20G Introduction and Highlights
• IP-20G Front Panel Description
• IP-20G Block Diagram
Page 47
FibeAir IP-20 Product Family
IP-20G
IP-20N 1RU & 2RU
IP-20E IP-20S
IP-20C
IP‐20
Platform
IP-20A= IP20N + RFU-A
IP-20LH
FibeAir IP-10 Product Line - 2011

Ethernet + Optional TDM Ethernet Only
IP-10G IP-10E IP-10C
Compact
All-Outdoor
Terminal / Terminal /
Single-Carrier Single-Carrier
IP-10Q
Aggregation
Nodal Nodal
Optimized for “Full GE”

Multi-Carrier pipes
Ultra-high density
Optimized Solution for Any Network

Page 48
FibeAir IP-X0 Product Line - 2012 (Introducing IP-20G)
Ethernet + Optional TDM Ethernet Only
IP-10G IP-10E IP-10C
Compact
All-Outdoor
Terminal / Terminal /
Single-Carrier Single-Carrier
IP-20G IP-10Q
Aggregation
Optimized for “Full GE”

Multi-Carrier pipes
Ultra-high density
Optimized Solution for Any Network

Network Topology Example (Tree)
C C
1+1 1+0
C C
IP‐20N
C
C
2+0
1+1
C
IP‐20N
C
C IP‐20N
1+0 C C
C
1+0
2+0
C
2+0 1+0
IP‐10G C C
IP‐20N
IP‐20G
C C
IP‐20G IP‐10G
Page 49
IP-20G Introduction
IP-20G hardware characteristics:
• 6 x 1 GE interfaces total
• 2 x dual mode GE electrical or cascading interfaces (RJ-45)
• 2 x GE electrical interfaces (RJ-45)
• 2x GE optical interfaces (SFP)
• Optional: 16 x E1 interfaces
• Single or dual radio interfaces (TNC)
• Single or dual power-feeds (-48v)
• Sync in/out interface
• Management interfaces
• Terminal – RS232 (RJ-45)
• 2x FE electrical interfaces (RJ-45)
• External alarms interface
• RFU-C, 1500HP / RFU-HP support
• IP-20G maintains high capacity, with up to 1024QAM modulation in its first SW release (T7.7),
and up to 2048QAM in future release
IP-20G Highlights
• Optimized tail/edge solution supporting seamless integration of radio (L1)
and end-to-end Carrier Ethernet transport/services (L2) functionality
• Rich packet processing feature set for support of engineered end-to-end
Carrier Ethernet services with strict SLA
• Integrated support for multi-operator and converged backhaul business
models, such as wholesale services and RAN-sharing
• Highest capacity, scalability and spectral efficiency
• High precision, flexible packet synchronization solution combining SyncE
and 1588v2
• Best-in-class integrated TDM migration solution
• Specifically built to support resilient and adaptive multi-carrier radio links,
scaling to GE capacity
• Future-proof with maximal investment protection
• Supports RFU-Ce for modulations up to 2048QAM.
Page 50
Reference Configurations
IP-20G Dual Modem Activation

• A single-carrier IP-20G unit with dual-modem hardware can be converted via
software upgrade to a dual-modem unit
Page 51
IP-20G IDU Cascading with Dual Modems
• A dual-modem IP-20G in an East-West configuration, with a cascading link to a pair
of IP-20G units
• A cascading connection between these two units enables hybrid Ethernet/TDM traffic
to pass among all three units
IP-20G Chained Network
Page 52
IP-20G Ring with Spur
• A ring consisting of three IP-20G nodes connected via 1+0 radio links, with a spur to
a fourth IP-20G node
• All of the IP-20G units in the ring utilize dual-modem configurations, except for the
node at the bottom in the figure
IP-20G Aggregation/POP Site
Page 53
IP-20G Front Panel Description
15
FibeAir IP-20G – Front panel description
Passive cooling
(Fan-less design)
1RU
Power
16 x E1/DS1s External
1 or 2 RFU -48V DC
(optional) Alarms 2 x FE
2 x GE interfaces (Single-feed &
MDR69 connector (DB9) Management via
Optical (TNC) Dual-feed options)
splitter cable 2 x Dual-Mode: (SFP)
(RJ45) GE Electrical or
Sync in/out
‘Cascading’
(RJ45)
Terminal (RJ45) 2 x GE
(RJ45) Electrical
(RJ45)
Purpose-built for tail/edge nodal sites

Same features/capabilities as IP-20N/A Aggregation Nodes
Page 54
SM- Card
• The SM-Card holds the configuration and software for the IDU. The SM-
Card is embedded in the SM-Card Cover, so re-using the existing SM-Card
Cover is necessary to ensure that the unit’s software and configuration is
maintained.
• Contains only software with configuration
Ethernet Management Interface IP-20G

• FibeAir IP-20G contains two FE management interfaces, which connect to a single RJ-45 physical
connector on the front panel (MGMT).
• If the user only needs to use a single management interface, a standard Cat5 RJ-45 cable (straight or
cross) can be connected to the MGMT interface.
• To access both management interfaces, a special 2 x FE splitter cable can be ordered from Ceragon.
• Port Status LED – The LED for management interface 1 is located on the upper left of the MGMT
interface. The LED for management interface 2 is located on the upper right of the MGMT interface.
Page 55
E1/DS1 - Interface
• Optionally, FibeAir IP-20G can be ordered with an MDR69 connector in which 16
E1/DS1 interfaces are available (ports 1 through 16).
• In SW 7.7. is E1 option only available
• In SW 7.9. also DS1 option available
• The E1/DS1 interface has the following LEDs
• ACT LED – Indicates whether the TDM card is working properly (Green) or if there is
an error or a problem with the card’s functionality (Red).
• E1/DS1 LED – Indicates whether the interfaces are enabled with no alarms (Green),
with alarms (Red), or no interfaces enabled (Off).
Radio Interfaces
• In 7.7 is supported only single radio carrier.
• In 7.7.5 is supported 2x 1+0 East / West Terminal
• In 7.9 is supported 2+0 XPIC
• In future software release will be available 2+0 ABC
• In 7.7 is supported only RFU-C (up to 256QAM) and RFU-Ce (up to 1024
QAM)
• In 7.9 RFU-HP, 1500HP, RFU-A supported
• The IDU and RFU are connected by a coaxial cable RG-223 (100 m/300 ft),
Belden 9914/RG-8 (300 m/1000 ft) or equivalent, with an N-type connector
(male) on the RFU and a TNC connector on the IDU.
RFU-C / RFU-Ce 1500HP / RFU-HP RFU-A
Page 56
Radio Interfaces - LEDs
• ACT – Indicates whether the interface is working properly (Green) or if there is

an error or a problem with the interface’s functionality (Red), as follows:
• Off – The radio is disabled.
• Green – The radio is active and operating normally.
• Blinking Green – The radio is operating normally and is in standby mode.
• Red – There is a hardware failure.
• Blinking Red – Troubleshooting mode.
• LINK – Indicates the status of the radio link, as follows:
• Green – The radio link is operational.
• Red – There is an LOF or Excessive BER alarm on the radio.
• Blinking Green – An IF loopback is activated, and the result is OK.
• Blinking Red – An IF loopback is activated, and the result is Failed.
• RFU – Indicates the status of the RFU, as follows:
• Green – The RFU is functioning normally.
• Yellow – A minor RFU alarm or a warning is present, or the RFU is in TX
mute mode, or, in a protected configuration, the RFU is in standby mode.
• Red – A cable is disconnected, or a major or critical RFU alarm is present.
• Blinking Green – An RF loopback has been activated, and the result is OK.
• Blinking Red – An RF loopback has been activated, and the result is
Failed.
Power Interfaces
• FibeAir IP-20G receives an external supply of -48V current via one or two power
interfaces (the second power interface is optional for power redundancy).
• The IP-20G monitors the power supply for under-voltage and includes reverse
polarity protection, so that if the positive (+) and negative (-) inputs are mixed up, the
system remains shut down.
• The allowed power input range for the IP-20G is -40V to -60V. An under voltage
alarm is triggered if the power goes below the allowed range, and an over voltage
alarm is triggered if the power goes above the allowed range.
• There is an ACT LED for each power interface.

• The LED is Green when the voltage being fed to the power interface is within range,
and Red if the voltage is not within range or if a power cable is not connected.
Page 57
Synchronization Interface
• FibeAir IP-20G includes an RJ-45 synchronization interface for T3 clock input and T4 clock output.
The interface is labeled SYNC.
• The synchronization interface contains two LEDs, one on the upper left of the interface and one
on the upper right of the interface, as follows:
• T3 Status LED – Located on the upper left of the interface. Indicates the status of T3 input clock,
as follows:
• Off – There is no T3 input clock, or the input is illegal.
• Green – There is legal T3 input clock.
• T4 Status LED – Located on the upper right of the interface. Indicates the status of T4 output
clock, as follows:
• Off – T4 output clock is not available.
• Green – T4 output clock is available.
• Blinking Green – The clock unit is in a holdover state.
External Alarms
• IP-20G includes a DB9 dry contact external alarms interface. The external alarms
interface supports five input alarms and a single output alarm.
• The input alarms are configurable according to:

• 1 Intermediate
• 2 Critical
• 3 Major
• 4 Minor
• 5 Warning
• The output alarm is configured according to predefined categories.
Page 58
Terminal Interface
• FibeAir IP-20G includes an RJ-45 terminal interface (RS-232). A local craft
terminal can be connected to the terminal interface for local CLI
management of the unit.
• Bits per Second – 115,200

• Data Bits – 8
• Parity – None
• Stop Bits – 1
• Flow Control - None
IP-20G Block Diagram
Page 59
Unique Feature Set
ACM 4‐2048QAM
Extended Modulations Range
(11 ACM points)
Frequency bands 6‐42GHz
30, 40, 50MHz (FCC)
Wide range of channels
7, 14, 28, 40, 56MHz (ETSI)
1+0
2x 1+0 EW
System Configurations
1+1 HSB
2+0 XPIC
Traffic Aware “Smart Pipe”
Traffic Manager
Multi Service, Carrier Ethernet 2.0 Switch
Radio Connection RFU‐C, RFU‐Ce, 1500HP, RFU‐HP
Thank You
28
Page 60
Radio Frequency Units
IP-20G
V1
1
December 2014
Agenda
• Radio Frequency units for IP20
• RFU Selection Guide
• RFU-C
• 1500HP / RFU – HP
• Split Mount Configuration and Branching
• New Outdoor Circulator Block OCB
• Split Mount Configurations
Page 61
Radio Frequency units
• Standard Power
• FibeAir RFU-C
• High Power
• FibeAir 1500HP SD
• FibeAir RFU-HP
• The following RFUs can be installed in a split-mount configuration:

• FibeAir RFU-C (6–42 GHz)
• FibeAir 1500HP (6–11 GHz)
• RFU-HP (6–8 GHz)
• The following RFUs can be installed in an all-indoor configuration:

• FibeAir 1500HP/RFU-HP (6–11 GHz)
• The IDU and RFU are connected by a coaxial cable RG-223 (up to 100 m/300 ft),
Belden 9914/RG-8 (up to 300 m/1000 ft) or equivalent, with an N-type connector
(male) on the RFU and a TNC connector on the RMC in the IP-20N chassis.
FibeAir ® Radio Frequency Units
Standard Power (Max 24 dbm)

6-42 GHz
FibeAir RFU-C 7-56Mhz Ch. Bandwidth
QPSK-2048QAM
Very Compact
Ultra High Power (Max 33 dbm)

6-8 GHz
7-56Mhz Ch. Bandwidth
FibeAir RFU-HP - 1RX Low Loss Chaining
QPSK-2048QAM
High Power (Max 33 dbm)

6-11 GHz
10-40Mhz Ch. Bandwidth
FibeAir 1500-HP/SD QPSK-2048QAM
Low Loss Chaining
Dual RX with IFC (Single Rx available for 11GHz)
Page 62
RFU Selection Guide
1500HP RFU‐HP RFU‐C RFU‐Ce

Character (6 – 11 GHz) (6‐8 GHz) (6 – 42 GHz) (6 – 42 GHz)
Split Mount √ √ √ √
Installation Type
All‐Indoor √ √  
1+0/2+0/1+1/2+2 √ √ √ √
Configuration N+0 ( N>2) √ √  
SD support √ (IFC, BBS) BBS √ (BBS) √ (BBS)
Adjustable Power
Power Saving Mode √ √  
Consumption
QPSK to 256 QAM √ √ √ √
Modulation
512 to 2048 QAM √ √  √
• 1500HP 1RX for 11GHz supports channel bandwidth 10-30 MHz

• RFU-HP does not support 56 MHz channels at 11 GHz
• IFC at 40MHz is supported only for the 11GHz frequency band
RFU – C
Page 63
RFU – C 6-42GHz
• Standard RFU – C
• Support up to 256 QAM modulation
•
• Premium RFU-Ce
• Support up to 1024 QAM modulation
• RMC-B is required for radio link with IP-20N
• Main Features of RFU-C:

• Frequency range – Operates in the frequency range 6 – 42 GHz
• More power in a smaller package - Up to 26 dBm for extended distance, enhanced
availability, use of smaller antennas
• Configurable Modulation – QPSK – 1024 QAM
• Configurable Channel Bandwidth – 7 MHz – 56MHz
• Compact, lightweight form factor - Reduces installation and warehousing costs
• Supported configurations:
• 1+0 – direct and remote mount
• 2+2 – remote mount
• 4+0 – remote mount
• Efficient and easy
Example of RFU-C direct 1+1 mount configurations
1+1 direct
Page 64
Orthogonal Mode Transducer (OMT) Installation for 2+0 Configuration
Switch to the circular adaptor

(removing the
existing rectangular transition,
swapping the O-ring, and
replacing on the circular
transition).
OMT Installation Example
Note: RFUs are at sub 11GHz band

Page 65
1500HP / RFU–HP
11
Main Features of 1500HP/RFU-HP

• Frequency range:
• 1500HP 2RX: 6-11GHz
• 1500HP 1RX: 11GHz
• RFU-HP 1RX: 6-8GHz
• Frequency source – Synthesizer
• Installation type – Split mount – remote mount, all indoor (No direct mount)
• Diversity – Optional innovative IF Combining Space Diversity for improved system gain (for 1500HP), as
well as BBS Space Diversity (all models)
• High transmit power – Up to 33dBm in all indoor and split mount installations
• Configurable Modulation – QPSK – 1024 QAM
• Configurable Channel Bandwidth –
• 1500HP 2RX (6-11 GHz): 10-30 MHz
• 1500HP 1RX (11 GHz): 10-30 MHz
• 1500HP 1RX (11 GHz wide): 24-40 MHz
• RFU-HP 1RX (6-8GHz): 7-56 MHz
• System Configurations – Non-Protected (1+0), Protected (1+1), Space Diversity, 2+0/2+2 XPIC, N+0, N+1
• XPIC and CCDP – Built-in XPIC (Cross Polarization Interference Canceller) and Co-Channel Dual Polarization
(CCDP) feature for double transmission capacity, and more bandwidth efficiency
• Power Saving Mode option - Enables the microwave system to automatically detect when link conditions allow it
to use less power (for RFU-HP)
• Tx Range (Manual/ATPC) – Up to 20 dB dynamic range
• ATPC (Automatic Tx Power Control)
• RF Channel Selection – Via EMS/NMS
• NEBS – Level 3 NEBS compliance
Page 66
1500 HP 2RX in 1+0 SD Configuration
1500 HP 1RX in 1+0 SD Configuration
Page 67
RFU-HP 1RX in 1+0 SD Configuration
HP Comparison Table
Feature 1500HP 2RX 1500HP 1RX RFU‐HP Notes
Frequency Bands Support 6L,6H,7,8,11GHz 6L,6H,7,8,11GHz 6L,6H,7,8GHz
Up to 30 MHz
Channel Spacing Support Up to 30 MHz 11 GHz version for Up to 56 MHz
40 MHz
All are compatible with OCBs
Split‐Mount √ √ √
from both generations
All‐Indoor √ √ √ All are compatible with ICBs
IFC ‐ IF Combining
Space Diversity BBS and IFC BBS BBS
BBS ‐ Base Band Switching
Frequency Diversity √ √ √
1+0/2+0/1+1/2+2 √ √ √
N+1 √ √ √
N+0 ( N>2) √ √ √
High Power √ √ √
Remote Mount Antenna √ √ √
Power consumption changes
Power Saving Mode ‐‐ ‐‐ √
with TX power
1500 HP (11 GHz ) 40 MHz bandwidth does not support IF Combining. For this frequency, space diversity is only available via BBS.
Page 68
Split Mount Configuration and Branching
Split Mount Configuration and Branching Network
• Outdoor Circulator Block OCB – The Tx and the Rx path

circulate together to the main OCB port. When chaining
multiple OCBs, each Tx signal is chained to the OCB Rx
signal and so on (uses S-bend section). For more details,
refer to 1500HP/RFU-HP OCBs
• Indoor Circulator Block ICB – All the Tx signals are

chained together to one Tx port (at the ICC) and all the Rx
signals are chained together to one Rx port (at the ICC). The
ICC circulates all the Tx and the Rx signals to one antenna
port.
Page 69
Split Mount Configuration and Branching Network
All- Indoor Vertical Branching Split-Mount Branching and All Indoor Compact
New OCB
20
Page 70
New OCB – Outdoor Circulator Block
The OCB has the following main purposes:

1. Hosts the circulators and the attached filters.
2. Chain and accumulate radio signal ( multiple carriers )
3. Routes the RF through the filters and circulators.
4. Allows RFU connection to the Main and Diversity antennas.
New OCB Components

• RF Filters - are used for specific frequency channels and Tx/Rx separation. The filters are attached to the OCB,
and each RFU contains one Rx and one Tx filter. In a Space Diversity using IF combining configuration, each RFU
contains two Rx filters (which combine the IF signals) and one Tx filter. The filters can be replaced without
removing the OCB. The RF filter is installed with every configuration.
• DCB - Diversity Circulator Block An external block which is added in Space Diversity configurations. DCB is
connected to the diversity port and chains two OCBs.
• Coupler Kit is used for 1+1 Hot Standby configurations. (loss 1.6 /6dB)
• Symmetrical Coupler Kit is used for: (loss of 3/3 dB) • When chaining adjacent channels (only 28/30 MHz) • 1+1
Hot Standby configurations with a symmetrical loss of 3dB in each direction Note: CPLRs loss tolerance is ±0.7
dB
• U Bend The U Bend connects the chained DCB (Diversity Circulator Block) in N+1/N+0 configurations.
• S Bend The S Bend connects the chained OCB (Outdoor Circulator Block) in N+1/N+0 configurations.
• Pole Mount Kit The Pole Mount Kit is used to fasten up to five OCBs and the RFUs to the pole. The kit enables
fast and easy installation.
Page 71
1+1 and 2+2 HSB Configuration
N+0/N+1 Configuration
Page 72
2+0 XPIC
Split mount applications
Page 73
Split mount applications 4+0
S-Bend
Split mount applications 4+0 SD
DCB DCB
S-Bend
28 Proprietary and Confidential U-Bend
Page 74
Thank You
Page 75
Page 76
IP-20G Installation Guide
May 2014
Version 1
Agenda
• Electromagnetic Fields, ESD and Laser Protection
• General Requirements for Packing and Transportation and
Environment
• IP-20G Rack Installation
• Rack Installation
• Grounding the IP-20G
• Replacing SM-Card
• Power Cable
• Mechanical Specifications
• Earth Bonding of Equipment
• IP-20G to RFU-C connection
• Antenna Installation
• RFU-C Installation
Page 77
High Frequency Electromagnetic Fields!
• Exposure to strong high frequency electromagnetic fields may cause
thermal damage to personnel. The eye (cornea and lens) is easily exposed.
• Any unnecessary exposure is undesirable and should be avoided.
• In radio-relay communication installations, ordinary setup for normal
operation, the general RF radiation level will be well below the safety limit.
• In the antennas and directly in front of them the RF intensity normally will
exceed the danger level, within limited portions of space.
• Dangerous radiation may be found in the neighborhood of open waveguide
flanges or horns where the power is radiated into space.
• To avoid dangerous radiation the following precautions must be taken:
• During work within and close to the front of the antenna; make sure that
transmitters will remain turned off.
• Before opening coaxial - or waveguide connectors carrying RF power,
turn off transmitters.
• Consider any incidentally open RF connector as carrying power, until
otherwise proved. Do not look into coaxial connectors at closer than
reading distance (1 foot). Do not look into an open waveguide unless
you are absolutely sure that the power is turned off.
ESD & LASER

• ESD
• This equipment contains components which are sensitive to "ESD" (Electro
Static Discharge). Therefore, ESD protection measures must be observed
when touching the IDU.
• Anyone responsible for the installation or maintenance of the FibeAir IDU
must use an ESD Wrist Strap.
• Additional precautions include personnel grounding, grounding of work
bench, grounding of tools and instruments as well as transport and storage
in special antistatic bags and boxes.
• LASER
• Use of controls or adjustments or performance of procedures other than
those specified herein may result in hazardous radiation exposure.
• The optical interface must only be serviced by qualified personnel, who are
aware of the hazards involved to repair laser products.
Page 78
General Requirements
Transportation & Inspection

• The equipment cases are prepared for
shipment by air, truck, railway and sea,
suitable for handling by forklift trucks and
slings. The cargo must be kept dry during
transport and storage.
• It is recommended that the equipment be

transported to the installation site in its
original packing case.
• If intermediate storage is required, the

packed equipment must be stored in a dry
and cool environment, and out of direct
sunlight, in accordance with ETS 300 019-
1-1, Class 1.2.
• Check the packing lists and verify that the

correct equipment part numbers and
quantities are in the delivered packages.
Page 79
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.
General Requirements
1. Environmental specification for IDU: -5C (23F) to +55C (131F)
2. Environmental specification for RFU: -33C (-27F) to +55C (131F) high reliability
3. -45C (-49F) to +60C (140F) with limited margins
4. Cold startup requires at least -5C (23F)
5. Humidity: 5%RH to 95%RH for IP-20G
6. Humidity: 5%RH to 100%RH for RFU-C
7. IDU standard Input is -48VDC (-40 to -60VDC)
8. This equipment is designed to permit connection between the earthed conductor of

the DC supply circuit and the Earthing conductor at the equipment.
9. The equipment shall be connected to a properly grounded supply system
10. The DC supply system is to be local, i.e. within the same premises as the equipment
11. A disconnect device is not allowed in the grounded circuit between the DC supply
source and the frame/grounded circuit connection.
8 8 Proprietary and Confidential
Page 80
IP-20G Rack Installation
Installing the IP-20G IDU
Kits required to perform the installation:
• IP-20G chassis 1x
• 19” rack/ sub rack 1x
• SM-Card Cover 1x
Tools:
Philips screwdriver
Flat screwdriver
Page 81
Rack Installation
• Insert and hold the IP-20G IDU in the rack, as shown in the following
figures. Use four screws (not supplied with the installation kit) to fasten the
IDU to the rack.
Grounding the IP-20G

• Connect a grounding wire first to the single-point stud shown in the figure
below, and then to the rack, using a single screw and two washers.
• The grounding wire must be 16 AWG or thicker
Page 82
Replacing an IP-20G IDU or SM-Card
• If you should need to replace the IP-20G IDU, you must first remove the SM-Card Cover so that
you can insert it into the new IDU.
• The SM-Card holds the configuration and software for the IDU. The SM-Card is embedded in the
SM-Card Cover, so re-using the existing SM-Card Cover is necessary to ensure that the unit’s
software and configuration is maintained.
• In some cases, you may need to replace the SM-Card itself in order to upgrade the unit’s
configuration.
To remove the SM-Card Cover:
1. Loosen the screws of the SM-Card Cover and remove it from the IDU.
Replacing an IP-20G IDU or SM-Card

2. In the new IDU or, if you are upgrading the SM-Card, the old IDU, make sure that there is no
foreign matter blocking the sockets in the opening where the SM-Card is installed.
3. Gently place the SM-Card Cover in its place and tighten the screws, using a Phillips screwdriver.
Page 83
Power Requirements
When selecting a power source, the following must be considered:
• DC power can be from -40 VDC to -60 VDC.
• Installation Codes: The equipment must be installed according to country national

electrical codes. For North America, equipment must be installed in accordance to the
US National Electrical Code, Articles 110-16, 110-17 and 110-18, and the Canadian
Electrical Code, Section 12.
• Overcurrent Protection: A readily accessible listed branch circuit overcurrent

protective device, rated 15 A, must be incorporated in the building wiring.
• Grounded Supply System: The equipment shall be connected to a properly grounded

supply system. All equipment in the immediate vicinity shall be grounded the same
way, and shall not be grounded elsewhere.
• Local Supply System: The DC supply system is to be local, i.e. within the same
premises as the equipment.
• Disconnect Device: A disconnect device is not allowed in the grounded circuit

between the DC supply source and the frame/grounded circuit connection.
15 15 Proprietary and Confidential
Power Interface
• FibeAir IP-20G receives an external supply of -48V current via one or two power interfaces (the
second power interface is optional for power redundancy). The IP-20G monitors the power supply for
under-voltage and includes reverse polarity protection, so that if the positive (+) and negative (-)
inputs are mixed up, the system remains shutdown.
• The allowed power input range for the IP-20G is -40V to -60V. An under voltage alarm is triggered if
the power goes below the allowed range, and an over voltage alarm is triggered if the power goes
above the allowed range.
• Make sure to use a circuit breaker to protect the circuit from damage by short or overload. In a
building installation, the circuit breaker shall be readily accessible and incorporated external to the
equipment. The maximum rating of the overcurrent protection shall be 10 Amp, while the
maximum current rating is 5 Amp.
Page 84
Power Cable
Power cables
Page 85
Mechanical Specifications
Earth Bonding of Equipment
Copyright © 2009 – 2013 Nera Networks AS All rights reserved. I-79113-EN rev. A
Page 86
Typical Earthing Network
Note 1: Structure or cable riser directly connected to Station

Earth Network.
Note 2: Main Earth Bar in equipment room, connected to
Station Earth Network.
Note 3: Earth Bus Bar/Cable connected to main earth bar.
Note 4: Coax Signal Cable.
Note 5: Over voltage protection integrated in units.
Note 1
Feeder - Earthing Kit (pos.1)

Ceragon Networks provides one
Earthing kit per feeder as standard
Earthing Kit staggered to ensure smooth,
There are three logical positions where uniform jumper transition to point of bonding.
a Waveguide/Feeder Earthing Kit should be installed:
1. Highest priority is at the bottom of the vertical

Custom Earthing Kit supplied from the
feeder run, on the straight section just above the
bend where it transitions from vertical to
Feeder Manufacturer – use only kit that are
horizontal. compatible.
2. Jumper Leads from the kit should be bonded to Never intermix components from different
the Tower Structure: Manufacturers.
- directly (bolted connection)
- via a earth termination plate (if provided)
- stainless steel angle adaptor (ANDREW)
3. Earth Kit on the feeder should be positioned
so that each jumper lead has a uniform smooth
transition down to the point of bonding – this may
mean staggering their position as shown here.
4. It is preferred that each jumper is bonded

separately.
Jumper lead between Earthing Kit
SEE NEXT TWO SLIDES and buried earth radial bonded to base
of the Tower Leg.
Recommended 70mm² PVC Coated Conductor
Page 87
Second line of defence
The second position in order of priority is just before the

waveguide/feeder enters the shelter through the wall plate.
Earth Termination Plate
1. Again it is important that the jumper lead forms a smooth
transition downwards to earth. In this case the bonding
point is on the earth termination plate mounted below the Earth Kit
cable bridge.
2. It is preferred that each jumper is bonded separately. Earth

Termination Plate usually have multiple bonding holes pre-
drilled.
3. To shape each conductor correctly begin at the earth

termination plate and form the cable to the best transition
back to the feeder. From there you will establish the
location to fit the earth kit. Treat each earthing kit
Jumper lead between Earthing Kit
separately. and Earth Termination Plate outside
shelter.
Recommended 70mm² PVC Coated
Conductor or 3mm x 25mm Copper
Common Errors Tape.
Fitting or, finding the Earth Termination Plate too high on the Conductor / Tape should be run out
shelter wall often prevent achieving the required earth to the
jumper transition. Buried earth loop at a depth of
600mm.
The third position in order of priority is at the antenna position.

Here, the Earthing Kit is fitted on the vertical straight
section of feeder just after the transition from horizontal to
vertical.
1. Once again it is important that the jumper lead forms a

smooth transition downwards to earth. It is usual to use the
tower structure itself as the main down conductor.
2. To shape each conductor correctly begin at the bonding

point and form the cable to the best transition back to the
feeder. From there you will establish the best position to fit
the earth kit to the feeder. Treat each earthing kit
separately.
The tower structure or
3. If using a Stainless Steel Angle Adaptor – this will provide climbing ladder are
flexibility to establishing a bonding point on the tower – the both commonly used
Angle Adaptor does not require you to find or drill a hole in for bonding the earth
jumper.
any structural members.
Angle Adaptors are the
most convenient
bonding method as this
Additional Earthing Kit:
avoids finding or
If a customer specifies additional earthing kit to be fitted, these drilling holes at height
would normally be positioned between the two kit installed at the in the tower.
top and bottom of the feeder.
Page 88
ODU Earthing
EACH ODU IS SEPARATELY

EARTHED – DO NOT JUMPER
BETWEEN ODU
1. SMOOTH JUMPER TRANSITION
2. SHORTEN THE JUMPER IF TOO LONG
3. SUPPORT EARTH JUMPER

WHERE NEEDED
4. BOND TO TOWER STRUCTURE.

CLAMP TYPE DEPENDENT ON
TOWER MEMBER PROFILE
RSSI
N-Type to IDU connection
EARTH TERMINAL
Applying the same principles to all cables
With All Cable Installations
Avoid leaving coils along

feeder cables
Avoid – kinking the cable
Avoid – cable loopbacks
Page 89
Weatherproofing
• Each Earthing Kit should be protected with a waterproof weather seal
• If the weather seals are not provided as part of the main Earthing Kit, they must be
ordered
• Each kit is provided with an installation instruction (or, Bulletin)
• Always follow the advice given in the instruction to achieve the best possible
installation
ODU to IDU connection
Page 90
IP-20G to RFU-C connection
The cable should have a maximum attenuation of 30 dB at 350 MHz.
TNC
N-type female
N-type male
TNC male
TNC females
N-type connector installation

http://www.youtube.com/watch
?v=cAV_xhP3FNA
http://www.youtube.com/watch
?v=Mo9LwdHe39M
Page 91
TNC connector
installation
instructions
http://www.youtube.co
m/watch?v=XfA0JVR
JSxU
Protecting the IF Connector for Split Mount
Make sure the vulcanized tape and PVC tape

overwrap extends right up to the ODU casing
and is hand moulded around the connector to
form a water tight joint
Fit a small cable tie at the top and

bottom of the weather kit to
prevent the PVC tape over wrap
from loosening
Also is possible to use cold

shrink medium instead of
tapes
Self sealing vulcanized tape The vulcanized tape must Failure to follow every detail of
weather kit should be be overwrapped with PVC the installation instructions will
applied to the connector at tape tied off at the top and result with water damage to the
the ODU to make it fully bottom with cable ties. connector and cable
water tight.
Page 92
Cable Clamping
IF Cable
Tower Cross Member
Avoid this method which is

When securing cables with cable
less secure and will cause
ties the method shown here can
unsightly bending of the
normally be achieved using a single
cable
tie.
This method will keep the cable
straight and provide the best
support
Cable Installation and Grounding

• For optical cables no grounding is required
• For Ethernet cables, the cable should be grounded to the antenna tower
every 50m using the kit CAT5E_gnd_kit.
• Procedure – see installation Guide
Page 93
Antenna Installation
RSSI Curve
1,9V
1,6V
1,3V
-30dBm -60dbm -90dBm
Page 94
Antenna Panning - Azimuth
Important to establish which are the side lobes
and what is the main beam
Position can be marked onto the column or

interface using a felt tipped pen
Receiving Antenna SIDE LOBE
Always Pan antenna

beyond each side lobe
AZIMUTH
MAIN BEAM
SIDE LOBE
For Azimuth panning it is important to establish the

strongest possible signal – but remember, further improvement
should be expected once elevation adjustment is carried out
Antenna Panning - Elevation

Determine from available data if the antenna direction
of shoot is above or below horizontal to ensure the
elevation is adjusted in the correct direction
With the main beam having already been established
it is not necessary to find the side lobes again
Receiving Antenna Once the best signal strength has been found using
elevation – minor azimuth panning can often
improve the signal strength further
SIDE LOBE
ELEVATION
HORIZONTAL
MAIN BEAM
Note:
SIDE LOBE
It should not always be expected to establish the strongest receive signal at
first attempt to align an antenna
Antenna may need to be panned several times before the optimum signal
strength is established
Page 95
Dual Polarized Antenna connection
To fit the Duel Polarized Waveguide
Interface
Note: There may be some variation in of the

Duel Polarized Waveguide Interface -
always refer to the installation Bulletin before
attempting to install this unit
Remove the two Waveguide Interface

securing screws.
Replace the Waveguide Interface with the

Dual Polarized Waveguide Interface.
Secure the Dual Polarized Waveguide

Interface to the antenna by means of two
screws M8.
Remount the two Waveguide Interface

securing screws.
Dual Polarized Antenna connection

DUEL POLARIZED FEEDHORN
WAVEGUIDE
Waveguide ports on feedhorn

clearly marked to show polarization
Page 96
RFU-C Installation
RFU-C waveguide flanges
Page 97
RFU-C direct mount configurations
1+0 direct
RFU-C and Antenna Interface Direct Mount Polarization
Page 98
RFU-C remote mount configurations
1+0 remote
RFU-C direct 1+1 mount configurations
1+1 direct
Page 99
RFU-C 1+1 Coupler Direct Mount Polarization
Vertical Polarization Horizontal Polarization
RFU-C remote mount configurations
1+1 remote
Page 100
Orthogonal Mode Transducer (OMT) Installation
Switch to the circular adaptor

(removing the
existing rectangular transition,
swapping the O-ring, and
replacing on the circular
transition).
OMT Installation Example
Page 101
RFU-C Mediation devices losses
Thank you
52
Page 102
First login
Ceragon Training Services

December, 2014 v3
Agenda
• CLI and Web login

• General commands
• Get IP address
• Set IP address
• Set to default
• Web Management
Page 103
Connecting to the Unit
CLI
Web/Telnet
Baud rate =
115200
Bits per Second – 115,200
Data Bits – 8
Parity – None
Stop Bits – 1
Flow Control - None
IP address = 192.168.1.1
Default Username/password is admin/admin
General commands
Press twice the TAB key for optional commands in actual directory
Use the TAB key to auto-complete a syntax
Use the arrow keys to navigate through recent commands
Question mark to list helpful commands
Page 104
Get IP address
CLI Command:
“platform management ip show ip-address”
Changing Management IP Address

• CLI Command:
“platform management ip set ipv4-address <IP Address> subnet <Mask>

gateway <default gateway>”
• Example
• Web
expand Platform branch, then Management branch and click on IP, set
accordingly and click Apply button
Page 105
Set to default
• CLI Command:
“platform management set-to-default”
Please note that IP address after Set to Factory Default will be not changed!!!
Other CLI commands

• For any CLI commands please follow our Web Manual
• Open Index html file

• Find out in Topics submenu required configuration
Page 106
Web Management
First Web login

Default IP address is 192.168.1.1 /24
Default Username/password is admin/admin
Page 107
Main View
Finding topic
Menu
Picture of
managed
element
Platform / Management / Unit Parameters
Page 108
Platform / Management / NTP Configuration
Platform / Management / Time Services
Page 109
Platform / Management / Interface Manager
Default status is
! DOWN ! Managing of all ports
Platform / Management / Inventory
Serial Number
important for
activation key
generating
Page 110
Platform / Management / Unit Info
Create Unit Information file, see

configuration in Backup chapter
Platform / Management / Reset
Provide software reboot
Page 111
Platform / Management / Set to Factory Default
Clear configuration database
IP address settings
Page 112
SNMP Parameters
Setting for NMS system
Trap Managers
Up to 4 Trap Managers
Page 113
V3 User
Setting for SNMP v3
Thank You
Page 114
Radio Link Parameters

December 2014 version 3
Agenda
• MRMC
• TX & RX Frequencies
• Link ID
• RSL
• MSE
• Current ACM Profile
Page 115
High and Low frequency station
Tx(f1)=11500 MHz Rx(f1)=11500 MHz

Full duplex
Local site Remote site
High station Low station
Rx(f1’)=11000 MHz Tx(f1’)=11000 MHz
High station means: Tx(f1) >Rx(f1’)
Low station means: Tx(f1’) < Rx(f1)
Radio Link Parameters

TSL RSL
IDU ODU )) ) ODU IDU
To Establish a radio link, we need configure following parameters:

1. MRMC – Modem scripts (ACM or fixed capacity, channel & modulation)
2. TX / RX frequencies – set on every radio
3. Link ID – must be the same on both ends
4. Max. TSL – Max. allowed Transmission Signal [dBm]
5. Unmute Transceiver – Transceiver is by default muted (is not transmitting)
-------------------------------------------------------------------------------------------------------
To verify a radio link, we need control following parameters:

1. RSL – Received Signal Level [dBm] – nominal input level is required
2. MSE- Mean Square Error [dB]
3. Current ACM profile
Page 116
MRMC – Multi Rate Multi Coding Profiles
Modulation RFU‐C RFU‐C Premium

QPSK Profile 0 Profile 0
8QAM Profile 1 Profile 1
256QAM (strong FEC) Profile 6 N/A
256QAM (weak FEC) Profile 7 Profile 6
512QAM N/A Profile 7
1024QAM (Strong FEC) N/A Profile 8
1024QAM (Light FEC) N/A Profile9
MRMC Scripts – 1st steep
Changing script automatically resets modem inside IP‐20G
Page 117
Radio Parameters settings
2nd step
4th step
5th step
3th step
LINK ID – Antenna Alignment Process

To avoid pointing the antenna to a wrong direction (when both links share the same
frequency), LINK ID can be used to alert when such action is take.
# 101
# 101
# 102
“Link ID
Mismatch”
# 101
“Link ID Mismatch”
Page 118
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”
Questions?
Page 119
Radio Link Setup Exercise
Thank You
Page 120
ACM – Adaptive Coding and Modulation
MSE – Mean Square Error

December 2014 version 3
Agenda
• Adaptive Coding and Modulation

• Using MSE with ACM
• What is MSE?
• Link Commissioning with MSE
• Triggering ACM with MSE
Page 121
Adaptive Coding and Modulation (ACM)
• In ACM mode, the radio will select the highest possible link capacity based on received signal quality.
• When the signal quality is degraded due to link fading or interference, the radio will change to a more robust
modulation and link capacity is consequently reduced.
• When signal quality improves, the modulation is automatically increased and link capacity is restored to the original
setting. The capacity changes are hitless (no bit errors introduced).
• During the period of reduced capacity, the traffic is prioritized based on Ethernet QoS - and TDM priority - settings.
• In case of congestion the Ethernet or TDM traffic with lowest priority is dropped. TDM capacity per modulation
state is configurable as part of the TDM priority setting.
High Priority
Traffic
8QAM
4QAM
1024QAM
1024QAM
2048QACM
512QAM
256QAM
128QAM
32QAM
LFEC
SFEC
64QAM
16QAM
Low Priority
Traffic
Hitless and Errorless switching
Page 122
Using MSE with ACM
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
Page 123
To simplify….
Imagine a production line where a machine needs to insert

one part into the other
Both devices must perfectly match
Let us assume the width has to be 10mm wide
We took a few of parts and measured them to see how

many can fit in….
The Errors Histogram

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

Page 124
The difference from Expected value…
Quantity
Error = 0 mm
Error = + 2 mm
Error = - 3 mm
Error = + 6 mm
Error = - 4 mm
width
To evaluate the inaccuracy (how sever the situation is) we

measure how much the errors differ from expected value
Giving bigger differences more weight than smaller

differences
Quantity
Error = 0 mm
+ 2 mm = 4
-3 mm = 9
- 4 mm = 16 + 6 mm = 36
width
We convert all errors to absolute values and then we square them
The squared values give bigger differences more weight than smaller differences,
resulting in a more powerful statistics tool:
16cm parts are 36 ”units” away than 2cm parts which are only 4 units away
Page 125
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
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
Page 126
MSE in digital modulation (Radios)
Let us use QPSK (4QAM)

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

2 possible states for Q signal
I = 4 possible states for the
combined signal
11 10 The graph shows the expected

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

expected values (constellation)
Q of the received signal (RSL)
01 00
The blue dots represent the
actual RSL
I
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
Page 127
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
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
Page 128
Commissioning with MSE in EMS
When you commission your

radio link, make sure your MSE
is small
Actual values may be read

-39dB to -41dB
Bigger values will result in loss

of signal
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
Page 129
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
Profile Mod MSE Down-Threshold MSE Up-Threshold
0 QPSK -18
1 8PSK -16 -19
2 16QAM -17 -23
3 32QAM -21 -26
4 64QAM -24 -29
5 128QAM -27 -32
6 256QAM -30 -34
7 512QAM -32 -37
8 1024 QAM SFEC -35 -38
9 1024 QAM WFEC -36 -41
10 2048QAM -39
Applicable for both 28/56MHz , 2048 QAM will be supported in future release
The values are typical and subject to change in relation to the frequency and RFU
type. For more details please contact your Ceragon representative
ACM & MSE: An example…

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 8 till MSE improves to -38dB:
ACM
Profile
Downgrade
-41 Downgrade
-38
-37
-34
Profile 10 Profile 9 Profile 8 Profile 7 Profile 6 Profile 5 Profile 4 Profile 3

2048 QAM 1024 QAM 1024 QAM 512 QAM 256 QAM 128 QAM 64 QAM 32 QAM
MSE
-39 -36 -35 -32 -30 -27 -24 -21
Page 130
ACM & MSE: An Example
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
‐41 ‐38
Profile 10 Profile 9 Profile 8
‐39 ‐36 ‐35 MSE
Thank You
Page 131
Page 132
Automatic Transmit Power Control - ATPC
November 2014, ver 3
Agenda
• Why ATPC?
• How does ATPC works?
• ATPC Vs. MTPC
• ATPC Configuration
Page 133
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
ATPC – Automatic Transmit Power Control

1. Enable ATPC on both sites
2. Set Input reference level (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 Output power to the min. possible level
5. Power reduction stops when RSL in remote receiver reaches Ref. input level
6. ATPC is strongly recommended with XPIC configuration
TSL Adjustments Monitored RSL
ATPC Radio Radio Radio

module Transceiver Receiver
‐ Ref. RSL
Feedback Signal RSL

Radio
Quality required
Receiver change
Site A
Check
Site B
Page 134
ATPC – Example when ATPC is OFF
FSL= -60 dB
Site A Site B
MTPC MTPC
TSL A = 30dBm TSL B = 30dBm

RSL A = ? RSL B = ?
RSL A = -30dBm (TSL B + FSL) RSL B = -30dBm (TSL A + FSL)
ATPC – Example when ATPC is ON (One site ATPC, second site MTPC)
FSL= -60 dB
Site A Site B
ATPC MTPC
IRLB (Input Ref. level on Site B) = -50dBm
TSL A = ? TSL B = 30dBm

RSL A = ? RSL B =?
TSL A = 10dBm (IRLB-FSL) RSL B = -50dBm (TSL A + FSL)

RSL A = -30dBm (TSL B + FSL)
You want -50dBm on Site B, so what is TXA in Site A?
Page 135
ATPC – Example when ATPC is ON (ATPC on both sites)
FSL= -60 dB
Site A Site B
ATPC ATPC
IRLB (Input Ref. level on Site B) = -50dBm IRLA (Input Ref. level on Site A) = -50dBm
TSL A = ? TSL B = ?
RSL A = ? RSL B = ?
TSL A = 10dBm (IRLB - FSL) TSL B = 10dBm (IRLA-FSL)

RSL A = -50dBm (TSLB + FSL) RSL B = -50dBm (TSL A + FSL)
ATPC – Example when ATPC is ON (ATPC on both sites), ATPC range
Max TSL is 30dBm

Max TSL is 30dBm
ATPC range is 20dB
ATPC range is 20dB
FSL= -60 dB
Site A Site B
ATPC ATPC
IRLB (Input Ref. level on Site B) = -60dBm IRLA (Input Ref. level on Site A) = -50dBm
TSL A = ? TSL B = ?
RSL A = ? RSL B = ?
TSL A = 10dBm (IRLB-FSL) TSL B = 10dBm (IRLA - FSL)

RSL A = -50dBm (TSL B + FSL) RSL B = -50dBm (TSL A + FSL)
RSL B is -50dBm because typical ATPC range for TX level is 20dB (depend on RFU type)!!!
It means that TSL A can’t be 0dBm because possible min is 10dBm (Max is 30dBm)
Page 136
ATPC Configuration
Thank You
10
Page 137
Page 138
IP-20G Licensing
October 2014
Version 4
Agenda
• Licensing in General
• Demo License
• CeraOS License concept
• IP-20 Licensing Scheme
• Licensed Features
Page 139
Licensing
• IP-20N offers a pay as-you-grow licensing concept in which
future capacity growth and additional functionality can be
enabled with Activation key.
• For purposes of licensing, each IP-20N chassis is considered
a distinct device, regardless of which cards are included in the
chassis. Each device contains a single Activation key.
• Licenses are divided into two categories:
• Per Carrier – The license is per carrier
• Per Device – The license is per device, regardless of the
number of carriers supported by the device.
• Ceragon provides a web-based License Management

System (LMS). The LMS enables authorized users to
generate Activation keys, which are generated per IDU serial
number.
• A 1+1 HSB configuration requires the same set of licenses for

both the active and the protected interfaces.
License Management System
Page 140
License generating
License is generated according to chassis SN
Mandatory Cards - IVM

• Single card for 1RU and 2RU chassis.
• 2 x E2PROM on single board (function as 2 separated cards).
• Installed at the back of the chassis
• Holds the chassis:
• License.
• Node MAC address (48 MACs per unit).
• Serial number for chassis
Page 141
DEMO License
• A demo license is available that enables all features for 60 days.
• The demo license expires 60 days from the time it was activated,
and the most recent valid license goes into effect.
• The 60-day period is only counted when the system is powered up.
10 days before the demo license expires, an alarm is raised
indicating to the user that the demo license is about to expire.
License violation
License violation yellow color screen has been implemented from sw. T7.9
Page 142
IP-20 Pricing Concept (Value Structure)
Hardware, Software & Licensed Features
CeraOS (Software)
Licensed Scalability Licensed Premium Functionality
• Radio capacity • Advanced radio configurations
• 2nd modem/core • Advanced QoS
activation (IP‐20G/C) • Ethernet OAM
• Additional GE user • TDM PW services
interfaces • Synchronization
• Additional CET‐Node • Network Resiliency
services/EVCs (L2) • Advanced Security
Licensed Mode ‐ CET‐Node
• CET services/EVCs (L2)
• 2x GE user interfaces
• Smart‐Pipe services (L1)
• 10M radio capacity Base‐line
• 1x GE user interface functionality
• Native TDM services
Hardware
• Product Models (e.g. IP‐20N, IP‐20G, IP‐20C, IP‐20LH)
• Assembly options (e.g. single/dual modem in IP‐20G)
• Add‐on modules (e.g. RMC in IP‐20N)
IP-20 Licensing Scheme

• Per Carrier • Per Node – Premium Functionality
• Scalability • QoS group
• Radio capacity • Enhanced Packet Buffer
• Advanced radio configurations • Frame Cut Through
• ACM • H-QoS
• XPIC • Sync group
• Multi-Carrier ABC • Sync-Unit
• IEEE-1588 TC
• MIMO
• IEEE-1588 OC
• Header De-duplication
• IEEE-1588 BC
• Redundancy/Resiliency group
• Per Node – scalability • Network Resiliency
• CET-Node mode/scalability • Main Card Redundancy - HA
• Edge (8 services/EVCs) • Ethernet OAM group
• Agg-Lvl-1 (64 services/EVCs) • Eth-OAM FM
• ETH-OAM PM
• Agg-Lvl-2 (1024 services/EVCs)
• TDM group
• General node scalability
• TDM PW
• 2nd
modem activation (IP-20G only)
• Security
• 2nd core activation (IP-20C only)
• Secure management
• GE user interfaces
Page 143
Licensed Features
License Name Description
Enables you to increase your system’s radio capacity in
gradual steps by upgrading your capacity license.
Without a capacity license, each carrier has a capacity
Radio Capacity License
of 10 Mbps. Licensed capacity is available from 50
Mbps to 500 Mbps. Each RMC card can be licensed for
a different capacity.
Enables the use of Adaptive Coding and Modulation
(ACM) scripts. A separate license is required per core.
IP‐20‐SL‐ACM
Enables Multi‐Carrier ABC.
IP‐20‐SL‐MC‐ABC
Enables the use of Header De‐Duplication, which can
IP‐20‐SL‐Header‐DeDuplication be configured to operate at L2 through L4.
Enables the use of Cross Polarization Interface
IP‐20‐SL‐XPIC Canceller (XPIC). A separate license is required for each
core in the XPIC pair.
Licensed Features
Enables the use of a TCC/LIC Ethernet traffic port in GE
mode (10/100/1000baseT or 1000baseX). An activation
key is required for each Ethernet traffic port that is used
on the device. An activation key can be installed
multiple times with dynamic allocation inside the unit
IP‐20‐SL‐GE‐Port to enable multiple GE ports.
Note: All Ethernet traffic ports are enabled in FE mode
(10/100baseT) by default without requiring any
activation key.
Enables the use of a second TCC in a 2RU chassis for
IP‐20‐SL‐Main‐Card‐Redundancy High Availability.
Page 144
Licensed Features
Enables Carrier Ethernet Transport (CET) and a number
of Ethernet services (EVCs), depending on the type of
CET Node license:
• Edge CET Node – Up to 8 EVCs.
• Aggregation Level 1 CET Node – Up to 64 EVCs.
• Aggregation Level 2 CET Node – Up to 1024 EVCs.
Edge CET Node
A CET Node license also enables the following:
• Network resiliency (MSTP/RSTP) for all services.
• Full QoS for all services including basic queue buffer
management (fixed queues buffer size limit, tail‐
drop only) and eight queues per port, no H‐QoS.
• LAG Support
•
Enables the following protocols for improving network
resiliency:
P‐20‐SL‐Network‐Resiliency
• G.8032
• TDM (PW) services 1:1/1+1 path protection
Licensed Features
Enables H‐QoS. This license is required to add service‐
IP‐20‐SL‐H‐QoSH‐QoS bundles with dedicated queues to interfaces. Without
this license, only the default eight queues per port are
supported. (Planned for future release)
Enables configurable (non‐default) queue buffer size
limit for Green and Yellow frames. Also enables WRED.
IP‐20‐SL‐Enh‐Packet‐Buffer
The default queue buffer size limit is 1Mbits for Green
frames and 0.5 Mbits for Yellow frames.
Enables the G.8262 synchronization unit. This license is
required in order to provide end‐to‐end synchronization
IP‐20‐SL‐Sync‐Unit
distribution on the physical layer. This license is also
required to use Synchronous Ethernet (SyncE).
Enables Frame Cut‐Through.
P‐20‐SL‐Frame‐Cut‐Through
Enables TDM pseudowire services on units with TDM
IP‐20‐SL‐TDM‐PW interfaces. Without this activation key, only native TDM
services are supported.
Page 145
Licensed Features
Enables secure management protocols (SSH, HTTPS,
P‐20‐SL‐Secure‐Management
SFTP, SNMPv3, and RADIUS).
Enables Connectivity Fault Management (FM) per
IP‐20‐SL‐Eth‐OAM‐FM
Y.1731/ 802.1ag and 802.3ah (CET mode only).
Enables performance monitoring pursuant to Y.1731
IP‐20‐SL‐Eth‐OAM‐PM
(CET mode only).
License
Page 146
License features available
Thank You
Page 147
Page 148
Service Model in IP-20
November 2014
Version 5
Agenda
• IP-20 Ethernet Capabilities
• Service Model in General
• What is a Service ?
• What is a Service point?
• Services in IP-20 Family & Services attributes
1. Point to Point Service
2. Multipoint Service
3. Management Service
• Service Point in IP-20 Family
1. Pipe Service Point
2. Service Access Point (SAP)
3. Service Network Point (SNP)
4. Management Service Point (MNG)
• Service Points classification and attributes
• Examples for Services and Service points
• Logical VS. Physical Port
Page 149
IP-20’s Ethernet Capabilities
• Up to 1024 services (1025 reserved for Management)
• Up to 32 service points per service (30 SPs for MNG service)
• All service types:
• Multipoint (E-LAN)
• Point-to-Point (E-Line)
• Point-to-Multipoint (E-Tree)
• Smart Pipe
• Management
• 128K MAC learning table per service - ability to limit MAC learning per
service
• Split horizon between service points
• Flexible transport and encapsulation via 802.1q, 802.1ad (Q-in-Q), and
MPLS-TP, with tag manipulation possible at egress
• High precision, flexible frame synchronization solution combining SyncE
and 1588v2
• Hierarchical QoS with 8K service level queues, deep buffering, hierarchical
scheduling via WFQ and Strict priority, and shaping at each level
IP-20’s Ethernet Capabilities

• Hierarchical two-rate three-Color policers
• Port based – Unicast, Multicast, Broadcast, Ethertype
• Service-based
• CoS-based
• Up to four link aggregation groups (LAG)
• Hashing based on L2, L3, MPLS, and L4
• Enhanced <50msec network level resiliency (G.8032) for ring/mesh support
• IP-20 is fully MEF-9 and MEF-14 certified for all Carrier Ethernet services.
Page 150
Service model in General
What is a Service?
• A virtual bridge, connecting two or more interfaces
• Bridge is a device that separates two or more network segments

within one logical network
• Interfaces are usually referred to physical ports but can also be logical
ports
Page 151
Service Model
2
Service #1
4 Service #2
Service points
Service points are logical entities attached to the interfaces that make up the
service. Service points define the movement of frames through the service.
Without service points, a service is simply a virtual bridge with no ingress or
egress interfaces.
Rails are second service point

towards the bridge
The Route is your first service point

towards the bridge
Page 152
What is a service point?
SP Service #1 SP
2
SP SP
4 Service #2
SP SP
Services in IP-20 Family
10
Page 153
IP-20 Services
IP20 supports the following services types:
1. Point-to-Point Service (P2P)

2. Multipoint Service (MP)
3. Management Service (MNG)
4. Point-to-Multipoint Service (E-Tree)
E-Tree services are planned for future release.
Point to Point Service (P2P)

• Point-to-point services are used to provide connectivity between two
interfaces of the network element.
• When traffic ingresses via one side of the service, it is immediately directed
to the other side according to ingress and egress tunneling rules.
• This type of service contains exactly two service points and does not require
MAC address-based learning or forwarding
1 4
PIPE PIPE
SAP SAP
2
Page 154
Multipoint Service (MP)
• Multipoint services are used to provide connectivity between two or more service points.
• When traffic ingresses via one service point, it is directed to one of the service points in the
service, other than the ingress service point, according to ingress and egress tunneling rules, and
based on the learning and forwarding mechanism.
• If the destination MAC address is not known by the learning and forwarding mechanism, the
arriving frame is flooded to all the other service points in the service except the ingress service
point.
1 4
SAP SNP
SAP SNP
Management Service (MNG)

• The management service is a multipoint service that connects the two local
management ports, the network element host CPU, and the traffic ports into a single
service. The service behavior is same as the Multipoint service behavior.
• The management service is pre-defined with Service ID 1025.
Management port
CPU
1
4
2 SAP SNP
1
Traffic ports
Service ID 1025
2
Page 155
Service Attributes
• Service ID - 1 - 1024
• Service Type – P2P, MP, MNG
• Service Admin Mode – Operational, Reserved
• EVC-ID - Ethernet Virtual Connection ID (End-to-end).
• EVC Description
• Maximum Dynamic MAC Address Learning per Service
• Static MAC Address Configuration
• CoS Mode & Default CoS
• xSTP Instance – The spanning tree instance ID (1-63)
• Split Horizon Group - (Enable/Disable)
IP-20 Service Points
16
Page 156
Service points
• SAP
• SNP
• Pipe Service Point
• Management Service Point
Proprietary and Confidential
Service Access Port SAP & Service Network Point SNP
Page 157
Service Access Port SAP & Service Network Point SNP
Management (MNG) Service Point
Only used for management services
Page 158
Pipe Service Points
Pipe Service Point – Used to create traffic connectivity between two

points in a port-based manner (Smart Pipe). In other words, all the
traffic from one port passes to the other port. Pipe service points are
used in Point-to-Point services
PIPE PIPE PIPE

SAP SAP SAP PIPE
SAP
Service points classification
22
Page 159
Service Point – Interface Types
Interface Type Types of Frames Applies to SP Type

Dot1q A single C‐VLAN is classified into the service All
point
S‐tag A single S‐VLAN is classified into the service SNP and MNG
point
Bundle‐C A set of C‐VLANs is classified into the service SAP
point
Bundle‐S A single S‐VLAN and a set of C‐VLAN are SAP
classified into the service point
All‐to‐One All C‐VLANs, S‐VLANs with TPID diff than the SAP
system one and untagged frames that enter
the interface are classified into the service
point
Q‐in‐Q A single S‐VLAN and C‐VLAN combination is SAP and MNG
classified into the service point
Service
Service Points
Page 160
Service
Service Point Types that can Co-Exist on the Same Interface
Service point Types per Service Type

Service point type
MNG SAP SNP Pipe
Service Type Management Yes No No No
Point-to-Point No Yes Yes Yes
Multipoint No Yes Yes No

MNG SP SAP SP SNP SP Pipe SP
MNG SP Only one MNG SP is Yes Yes Yes
allowed per interface.
SAP SP Yes Yes No No
SNP SP Yes No Yes No
PIPE SP Yes No No Only one Pipe SP is
allowed per interface.
Page 161
Example of dot1q services

• The classification to PtP1 and PtP2 is based
on one c‐vlan.
• PtP 1 uses same c‐vlan as the classification
at both ends
• PtP 2 uses different c‐vlan as the
classification at both ends.
• PtP1 and PtP2 uses the transport vlan
inside the network. The original c‐vlan is
not sent inside the network.
C‐Vlan
SAP3 10 SAP 3
ptp 1
C‐Vlan SAP1
10 SAP 1 C‐Vlan
20 SAP 2 120 SAP 4
SAP4
SAP2
ptp 2
Transport Vlan EVC
100 ptp1
SAP
200 ptp2 SNP
Page 162
Example of bundle services
on several c‐vlan’s.
inside the network. The original c‐vlan is
preserved and sent inside the network.
C‐Vlan
SAP3
10,11 SAP 3
ptp 1
C‐Vlan SAP1
10,11 SAP 1 C‐Vlan

20,21 SAP 2 20,21 SAP 4
SAP4
SAP2
ptp 2
Transport Vlan EVC
100 ptp1
SAP
200 ptp2 SNP
Example of Q-in-Q services

on a pair of c‐vlan and s‐vlan.
inside the network. The original c‐vlan and
s‐vlan is not sent inside the network.
S‐Vlan C‐Vlan
SAP3
230 10 SAP 3
ptp 1
SAP1
S‐Vlan C‐Vlan
SAP4 340 320 SAP 4

SAP2
S‐Vlan C‐Vlan ptp 2
230 10 SAP 1
240 20 SAP 2
Transport Vlan EVC
100 ptp1
SAP
200 ptp2 SNP
Page 163
Service points Attributes
31
Service Point Attributes

As described above, traffic ingresses and egresses the service via service
points. The service point attributes are divided into two types:
• Ingress Attributes – Define how frames are handled upon ingress, e.g.,
policing and MAC address learning.
• Egress Attributes – Define how frames are handled upon egress, e.g.,
preservation of the ingress CoS value upon egress, VLAN swapping.
Page 164
Service Point Attributes
General Ingress Egress
Service Point ID Learning Admin C‐VLAN CoS Preservation

Service Point Name Allow Flooding C‐VLAN Preservation
Service Point Type Allow Broadcast S‐VLAN CoS Preservation
Interface CoS Mode Marking Admin
Interface Type Default CoS Service Bundle ID
C‐VLAN Encapsulation
S‐VLAN Encapsulation
Service Point – General Attributes
General • Service Point ID – number for service point inside

the same service
• Service Point Name – The Name for service point
if is needed
Service Point ID • Service Point Type- SAP, SNP, MNG, PIPE
Service Point Name • Interface - The logical interface on which the
service point is located
Service Point Type
• Interface Type – Dot1q, S-Tag, Bundle-C, Bundle-
Interface S, All-to-One, Q-in-Q
Interface Type • C-Vlan Encapsulation - The C-VLAN classified
C‐VLAN Encapsulation into the service point
S‐VLAN Encapsulation • S-Vlan Encapsulation - The S-VLAN classified
into the service point
Page 165
Service Point – Ingress Attribute
• Learning Admin - Indicates whether MAC
address learning is enabled or disabled
Ingress
• Allow Flooding - Indicates whether incoming
frames with unknown MAC addresses are
forwarded to other service points via flooding
Learning Admin • Allow Broadcast - Indicates whether frames with
a broadcast destination MAC address are allowed
Allow Flooding to ingress the service via this service point
Allow Broadcast • CoS Mode - Indicates how the service point
CoS Mode handles the CoS of frames that pass through the
service point.
Default CoS
• Default CoS – The service point CoS. If the CoS
Mode is set to overwrite the CoS decision made at
the interface level, this is the CoS value assigned
to frames that ingress the service point.
Service Point – Egress Attribute

• C-Vlan CoS Preservation - Indicates whether the
original C-VLAN CoS value is preserved or
Egress restored for frames egressing from the service
point
• C-Vlan Preservation - Indicates whether the
original C-VLAN ID is preserved or restored for
C‐VLAN CoS Preservation
frames egressing from the service point
C‐VLAN Preservation • S-Vlan CoS Preservation - Indicates whether the
S‐VLAN CoS Preservation original S-VLAN CoS value is preserved or
Marking Admin restored for frames egressing from the service
point
Service Bundle ID
• Marking Admin - Indicates whether re-marking of
the outer VLAN (C-VLAN or S-VLAN) of tagged
frames that pass through the service point is
enabled
• Service Bundle ID - This can be used to assign
one of the available service bundles from the H-
QoS hierarchy queues to the service point
Page 166
Ethernet Service Points – GUI
General
Service Point ID
Service Point Name
Service Point Type
Interface
Interface Type
C‐VLAN Encapsulation
S‐VLAN Encapsulation
Ingress
Learning Admin
Allow Flooding
Allow Broadcast
CoS Mode
Default CoS
Egress
C‐VLAN CoS Preservation
C‐VLAN Preservation
S‐VLAN CoS Preservation
Marking Admin
Service Bundle ID
Logical Vs. Physical Interface
38
Page 167
Logical and physical interface
Service Demo
40
Page 168
The Setup
• IP-20N
IP-20G
• IP-20C/S/E
Creating the Service
Page 169
Attaching Service Points
Page 170
Questions?
Page 171
Thank You
Page 172
Quality of Service
December 2014
Version 6
Agenda
• Standard QoS VS. H-QoS
• QoS in General
• QoS in IP-20
• Classification
• Marker
• Bandwidth Profile
• Policing
• Queues Manager
• WRED
• Scheduler
• Shaper
Page 173
Hierarchical QoS (H-QoS) vs. Standard QoS
Standard QoS
• Differentiation between V
different traffic classes (CoS) Service 1
S
Voice
• Services within the same traffic V

S
Streaming Eth. Ethernet
class are treated as a single Service 2
V
D traffic Radio
aggregate with no isolation S D
Data
D
• Limited per-service visibility Service 3
and control
H-QoS
• Each service gets its own V
Service 1 S Service 1
personalized treatment D
• TDM-grade performance V
S
Ethernet
Service 2 Service 2
providing per-service full D
Radio
visibility and control V
Service 3 S Service 3
D
Backhaul Sharing – Fairness & Bursts Isolation

MSC/RNC/S-GW
Operator 1
Operator 1
Operator 2
Shared Backhaul
Shared Site
Shared Site
Operator 1 MSC/RNC/S-GW
Shared Site Operator 2
Operator 2
N >> 8
Operator 1
Standard
QoS
Operator 2 Same CoS
Operator 1
Same CoS HQoS
Operator 2
Page 174
Backhaul Sharing - Fairness & Bursts Isolation
MSC/RNC/S-GW
Operator 1
Operator 1
Operator 2
Shared Backhaul
Shared Site
Shared Site
Operator 1 MSC/RNC/S-GW
Shared Site Operator 2
Operator 2
Operator 1
7 6 5 4 3 2 1
Standard
Q1 3 2 1 7 6 5 4 3 2 1 3 2 1 7 6 5 4 3 2 1
3 2 1 QoS
Operator 2
Operator 1
7 6 5 4 3 2 1 Q1 7 6 5 4 3 2 1
7 6 5 4 3 3 2 2 1 1
HQoS
3 2 1
Q2 3 2 1
Operator 2
QoS in IP-20
Page 175
How it Works?
Ingress Port
Egress Port
Ethernet frame
V.ID = 100
P-Bit = 5
IP Packet
DSCP = 0
General Overview
Ingress Port
Egress Port
Marker Scheduler
Priority WFQ
Policers Queues
Shapers
WRED
Service
Ingress Egress
Page 176
Classification
Classification
• 3 Hierarchies
• Port (aka 1H)
• VLAN (aka 1.5H)
• Service Point (aka 2H)
• Service (aka 3H)
• Port level classification

• VLAN P-bits Service
• DSCP SP
• MPLS EXP bits
• Default classification
VLAN
Port
Page 177
Classification Hierarchies
Service #1
Calculated CoS =H3>H2>H1

Service H3
Port H1 SP H2
VLAN H1,5
Port VLAN SAP SNP
SAP SAP
Port level classification Service Points classification

1. VLAN P-bits 1. Preserve previous decision
2. DSCP 2. Default CoS
3. MPLS EXP bits Service classification
4. Default classification 1. Preserve previous decision
2. Default CoS
CoS Classification
Calculated CoS =H3>H2>H1

Port1 H1 VLAN H1,5
SP1 H2
Port 1 VLAN
SAP
Service H3 SNP
Port level classification

1. VLAN P-bits Service Points classification
2. DSCP 1. Preserve previous decision
3. MPLS EXP bits 2. Default CoS Service classification
4. Default classification 1. Preserve previous decision
2. Default CoS
SP2 H2
Port2 H1 VLAN H1,5
SAP SNP
Port 2 VLAN
Port level classification Service Points classification

1. VLAN P-bits 1. Preserve previous decision
2. DSCP 2. Default CoS
3. MPLS EXP bits
4. Default classification
Page 178
Classification example
Customer 1
Customer 2
4
Customer 3
Customer 3
Classification – 1H
Page 179
Classification – 1.5H
• VLAN CoS Override
Classification – 1.5H
• VLAN CoS Override for Bundle SPs
Page 180
• Service Point CoS Mode
• Service CoS Mode
Page 181
Policing
19
Ingress Policing
• We can configure ingress policing based on

two rates three colors token bucket (MEF 10.2 TrTCM).
• The token buckets order shall be as follow:
• Service-Point+CoS - service policing
• Service-Point - service policing
• Ethertype - port policing
• Frame type (unicast, multicast, broadcast) – port policing.
• There are 256 profiles
• There are 1024 policers.
CoS 1
Service-Point
Frame Type
Ethertype
CoS 2
CoS 3
Page 182
Meaning of Colors
Dropped
Non Guaranteed
Guaranteed
Bandwidth Profile (BWP)

Two Rate Three Color Marking Policer – Rates & Bursts
Committed Information Rate Excess Information Rate

The rate at which tokens fill the 1st bucket The rate at which tokens fill the 2nd bucket
Committed Burst Size Excess Burst Size

The size of the 1st bucket The size of the 2nd bucket
CIR & CBS defines the assured bandwidth and burst

EIR & EBS improves the network’s Goodput (best effort)
Page 183
Bandwidth Profile (BWP)
Two Rate Three Color Marking Policer – Modes Of Operation
Color Modes (CM) Coupling Flag (CF)

Color Blind – Frames are uncolored and are CF = 0 – the 2nd bucket is filled based on
marked following policer operation
EIR value only
Color Aware – Frames were marked before.
Yellow frames jump to 2nd bucket CF = 1 – 2nd bucket is filled based on EIR
and excess tokens not used in 1st bucket
Most Operators use CM & CF default values (CM = blind, CF = 0)
Defining Policer Profile
128000 bps
Page 184
Assign a Policer to a Port
Assign a Policer to an SP
Page 185
Queues Manager & WRED & Marker
27
Queues Manager
Service #1 Queue 0
CoS 0 SS
Queue 1
Service CoS 1 Queue 2

SS
SS
CoS 2
Queue 3
CoS 3 Queue 4
SS
SAP SNP
SAP SAP SS
CoS 4
Queue 5
SS
CoS 5
Queue 6
SS
CoS 6
Queue 7
CoS 7 SS
SS – Single Shaper
Page 186
WRED
• Weighted Random Early Detect
• Sliding window example
Maximum physical BW of the line
WRED
• IP-20 can hold 32 WRED profiles.
• For each queue (in L4)

we can attach one of the WRED profiles.
Page 187
Creating WRED Profile
Queues Manager with WRED
Service #1 Queue 0
CoS 0 WRED SS
Queue 1
Service CoS 1 WRED

Queue 2
SS
WRED SS
CoS 2
Queue 3
SAP
SAP
SNP
SAP CoS 3 WRED SS
Queue 4
WRED SS
CoS 4
Queue 5
WRED SS
CoS 5
Queue 6
WRED SS
CoS 6
Queue 7
CoS 7 WRED SS
Page 188
Creating WRED Profile
Marking
34
Page 189
“Painting” a Frame
CFI = 0, it is an Ethernet Frame, it means green color
CFI = 1, it is an Canonical format, it means yellow color
Marker
CoS Preservation Marking Result
IP‐20
Calculated
Enable Don’t Care 5 5
Cos = 3/G
IP‐20
Calculated
Disable Enable 5 3
Cos = 3/Y
IP‐20
Calculated
Disable Disable 5 3
Cos = 3/Y
Page 190
MARKER
Service #1 Queue 0
CoS 0 WRED MARKING

Queue 1
SS
Service SS
CoS 1 WRED MARKING
Queue 2
WRED MARKING
CoS 2 Queue 3
SS
SS
SAP
SAP
SNP
SAP CoS 3 WRED MARKING
Queue 4
CoS 4 WRED MARKING SS
Queue 5
Queue 6
Queue 7
Scheduling and Shaping
38
Page 191
Traffic Manager Example
1 8
2 9
1 3
3 10
Service #1
4 2 4 11
5 12
6 1 13
Service #2 3
7 2 14
Hierarchical QoS
MARKING
SP – Strict Priority Service Level Port Level

WFQ – Weighted Fair Queuing
CoS 0 WRED SS
CoS 1 WRED SS
WFQ
CoS 2 WRED SS
Dual Shaper
Service #1 CoS 3 WRED SS SP +

CoS 4 WRED SS WFQ
CoS 5 WRED SS
CoS 6 WRED SS
WFQ
Single Shaper
CoS 7 WRED SS
SP
CoS 0 WRED SS
WFQ
CoS 1 WRED SS
CoS 2 WRED SS
Dual Shaper
CoS 3 WRED SS SP +

Service #n
CoS 4 WRED SS WFQ 1st priority
2nd priority
WFQ
CoS 5 WRED SS
3rd priority
CoS 6 WRED SS 4th priority
CoS 7 WRED SS
CoS Queue Level (Within a service) Service Bundle Level Port Level
Page 192
Hierarchical QoS now in T7.9
MARKING
SP – Strict Priority Service Level Port Level
WFQ – Weighted Fair Queuing
CoS 0 WRED SS
CoS 1 WRED SS
WFQ
CoS 2 WRED SS
Dual Shaper
Service #1 CoS 3 WRED SS
CoS 4 WRED SS
CoS 5 WRED SS
CoS 6 WRED SS
WFQ
Single Shaper
CoS 7 WRED SS
SP
CoS 0 WRED SS
WFQ
CoS 1 WRED SS
CoS 2 WRED SS
Dual Shaper
CoS 3 WRED SS
Service #n
CoS 4 WRED SS
1st priority
2nd priority
WFQ
CoS 5 WRED SS
3rd priority
CoS 6 WRED SS 4th priority
CoS 7 WRED SS
CoS Queue Level (Within a service) Service Bundle Level Port Level
SP+WFQ Scheduling Example for one Service Bundle

CoS Level Service LevelPort Level
Queue 0
CoS 0 WRED
1st priority
Queue 1 2nd priority
CoS 1 WRED 3rd priority
4th priority
Queue 2 SP + WFQ
CoS 2 WRED
WFQ
Single Shaper
Queue 3
CoS 3 WRED
SP
Queue 4
WFQ
CoS 4 WRED
Queue 5
CoS 5 WRED
WFQ
Queue 6
CoS 6 WRED
Queue 7 Mixed scheduling

CoS 7 WRED • 4 strict priorities
• WFQ within same priority
8 Queues • Shaping per port/queue
Page 193
Scheduler – Priority and WFQ
• User shall can create up to 8 profiles of
priority/weight.
Class Of Priority Priority Weight Weight Service Name

Service when when when when
green yellow green yellow
CoS 7 4 4 20 20 Management (synch, PDU etc ...)
CoS 6 3 1 20 20 Real Time 1 (Voice small buffer)
CoS 5 3 1 20 20 Real Time 2 (Video large buffer)
CoS 4 2 1 20 20 Data Service 1
CoS 0 1 1 20 20 Best Effort
• The profile is attached on logical port. All the service bundle inherit
this configuration.
Creating a Shaper
PIR = CIR + EIR
Page 194
Assign a Shaper
Creating Priority Profile
Page 195
Creating Priority Profile
H-QoS Summary
MARKING
Service Bundle #1
Service Bundle #64
Policer level 1
Policer level 3 Policer level 2
Page 196
Standard QoS vs H-QoS - Summary
Capability Standard QoS Hierarchical QoS
Number of transmission
8 512
queues per port
Number of service bundles 1 (always service bundle id equal 1) 64
Per queue (two curves – for green traffic and Per queue (two curves – for green traffic and
WRED
for yellow traffic via the queue) for yellow traffic via the queue)
Shaping at queue level Single leaky bucket Single leaky bucket
Shaping at service bundle

Dual leaky bucket Dual leaky bucket
level
Single leaky bucket (this level is not relevant

Shaping at port level since it is recommended to use service bundle Single leaky bucket
level with dual leaky bucket)
Per queue priority (4 priorities). All service

Transmission queues priority Per queue priority (4 priorities). bundles for a specific port inherit the 8-
queues priority settings.
Queue level (between queues)
Weighted fair Queue (WFQ) Queue level (between queues) Service Bundle level (between service
bundles)
Marker Supported Supported
Queue level (8 queues) Queue level (512 queues)

Statistics Service bundle level (1 service bundle) Service bundle level (64 service bundles)
Port level Port level
WFQ on the service bundle level is planned for future release.

Thank You
Page 197
Page 198
IP- 20G XPIC Configuration
December 2014
Version 1
Agenda
• System Spectrum Utilization

• ACAP
• ACCP
• CCDP
• Co-channel System
• IP-20G & XPIC
• XPIC Recovery mechanism
• XPIC Settings
Page 199
System Spectrum Utilization
BW
V 1 3 5 7 9
ACAP (Adjacent Channel Alternating Pol.)
H
2 4 6 8 10
BW
V 1 2 3 4 5 6 7 8 9 10 ACCP (Adjacent Channel Common Pol.)

H
BW
V 1 2 3 4 5
CCDP (Co-Channel Dual Polarisation)
H
6 7 8 9 10
CCDP frequency plan
V 1 V 1
H H
2 2
Vertical and Horizontal Polarization are using the same frequency
Page 200
Co-channel Systems
• The XPIC improvement factor is typically 26 dB.

• Two channels are using the same frequency but different polarization
• RMC-B and XPIC script is required
• The XPIC mechanism utilizes the received signals from the V and H modems to extract the V and H signals
and cancel the cross polarization interference due to physical signal leakage between V and H polarizations.
• The H+v signal is the combination of the desired signal H (horizontal) and the interfering signal V (in lower
case, to denote that it is the interfering signal). The same happens with the vertical (V) signal reception=
V+h. The XPIC mechanism uses the received signals from both feeds and, manipulates them to produce the
desired data
• IP-20G’s XPIC reaches a BER of 10e-6 at a co-channel sensitivity of 5 dB. The improvement factor in an
XPIC system is defined as the SNR@threshold of 10e-6, with or without the XPIC mechanism.
Conditions for XPIC

• XPIC is enabled by selecting an XPIC script for each carrier.
• In order for XPIC to be operational, all the following conditions must be met:
• Communications with the RFU must be established by both radio
interfaces.
• RFU type must be the same for both carriers.
• The frequency of both radios must be equal.
• 1+1 HSB protection must not be enabled.
• The same script must be loaded for both carriers.
• The script must support XPIC
Page 201
RSL Vs. Threshold for system without CCDP
RSL (dBm) BER>10-6
-20
-30 Nominal Input Level
Fading Margin = 43dB
-73 Threshold level BER=10-6
BER>10-6 S/N=23dB for 128QAM (37 MHz)

-96 Receiver amplifies thermal noise
-99 K – Boltzmann constant

T – Temperature in Kelvin
Thermal Noise=10*log(k*T*B*1000) B – Bandwidth
Time (s)
RSL Vs. Threshold for CCDP system without XPIC
RSL (dBm)
BER>10-6
-20
-30 Nominal Input Level H
Fading Margin = 12dB

Threshold level because of interference without XPIC
-42 BER=10-6
BER>10-6
S/N=23dB for 128QAM (37 MHz)
-65 Interference level in H (interference from V,
separation between H & V with very good antenna is
35dB)
-73 Interference
Threshold level without interference BER=10-6
-96
-99
Time (s)
Page 202
RSL Vs. Threshold for CCDP system with XPIC
RSL (dBm)
BER>10-6
-20
-30 Nominal Input Level H
Fading Margin = 38 dB
BER>10-6
Interference level in H (interference from V, when
-65 XPIC is not enabled
XPIC will Threshold level when XPIC is ON

-68
“improve”
-73 Original Threshold level without CCDP and XPIC
interference S/N=23dB for 128QAM (37 MHz) configuration
for extra Interference level in H (interference from V, when
26dB XPIC is enabled
-91
Interference level
Time (s)
XPIC Recovery Mechanism
• The purpose of the XPIC recovery mechanism is to save the working link while
attempting to recover the faulty polarization.
• The mechanism works as follows:

• The indication that the recovery mechanism has been activated is a loss of
modem preamble lock, which takes place at SNR~10dB.
• The first action taken by the recovery mechanism is to cause the remote
transmitter of the faulty carrier to mute, thus eliminating the disturbing signal and
saving the working link.
• Following this, the mechanism attempts at intervals to recover the failed link. In
order to do so, it takes the following actions:
• The remote transmitter is un-muted for a brief period.
• The recovery mechanism probes the link to find out if it has recovered. If not,
it again mutes the remote transmitter.
• This action is repeated in exponentially larger intervals. This is meant to
quickly bring up both channels in case of a brief channel fade, without
seriously affecting the working link if the problem has been caused by a
hardware failure.
• The number of recovery attempts is user-configurable
Every such recovery attempt will cause a brief traffic hit in the working
link.
Page 203
MRMC selection
X – means XPIC script

N – Normal script
XPIC settings
Page 204
Thank you
13
Page 205
Page 206
Protection System Configuration
December 2014
Version 1
Agenda
• What is Protection?
• General Guidelines
• HSB Configuration in general – principals
• 1+1 HSB Configuration
Page 207
Different types of protections systems
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
Page 208
Hot standby in general
1
In case of ch1 failure, will be traffic
Ch1
Main Ch1
Main switched to Protection channel
1′
1
Protection Protection
1’
• HSB system is using same frequency for Main and Standby channel (f1 & f1’)
• HSB system is typically 1+1
• Protection channel is internally muted. Just in case Main channel failure will be Protection channel Unmuted.
• Space diversity with baseband switching is based on HSB system (selection of better input level)
• In Hot Standby mode only one transmitter is active, the other transmitter is standby. Both receivers are active
and hitless switching is performed if Space diversity was configured. The TX- and RX- switching at a terminal
normally operates independently, but they may be configured to operate together.
HSB Protection
• IP-20G offers radio redundancy via 1+1 HSB protection. 1+1 HSB protection provides
full protection in the event of interface, signal, or RFU failure
• The interfaces in a protected pair operate in active and standby mode. If there is a
failure in the active radio interface or RFU, the standby interface and RFU pair
switches to active mode
• Each carrier in a protected pair reports its status to the CPU. The CPU is responsible
for determining when a switchover takes place.
• In a 1+1 HSB configuration, the RFUs must be the same type and must have the
same configuration
Page 209
HSB Protection – Revertive mode
• In an HSB protection scheme, the active and standby radios are usually
connected to the antenna with a coupler.
• This causes a -6dB loss on the secondary path on each side of the link,
resulting in a 12dB increase in the total path loss for the link.
• This additional path loss will either reduce the link’s fade margin or increase the
power consumption of the Power Amplifier (PA) in order to compensate for the
additional path loss.
• The system monitors the availability of the primary path at all times. Whenever
the primary path is operational and available, without any alarms, but the
secondary path is active, the system initiates a revertive protection switch.
Every revertive protection switch is recorded as an event in the event log.
• Revertive time from Secondary radio back to Primary radio is 10 min
EACH PROTECTION SWITCH CAUSES TRAFFIC DISRUPTION!!!
Switchover Triggers
The following events trigger switchover for 1+1 HSB protection according to
their priority, with the highest priority triggers listed first.
1. Hardware module missing

2. Lockout
3. Force switch
4. Traffic failures
5. Manual switch
Page 210
ACM and 1+1HSB
• When ACM is activated together with 1+1 HSB protection, it is
essential to feed the active RFU via the main channel of the coupler
(lossless channel), and to feed the standby RFU via the secondary
channel of the coupler (-6db attenuated channel). This maximizes
system gain and optimizes ACM behavior for the following reasons:
• In the TX direction, the power will experience minimal attenuation.
• In the RX direction, the received signal will be minimally attenuated.
Thus, the receiver will be able to lock on a higher ACM profile
(according to what is dictated by the RF channel conditions).
• The following ACM behavior should be expected in a 1+1
configuration:
• In the TX direction, the Active TX will follow the remote Active RX ACM
requests (according to the remote Active Rx MSE performance).
• The Standby TX might have the same profile as the Active TX, or might
stay at the lowest profile (profile-0). That depends on whether the
Standby TX was able to follow the remote RX Active unit’s ACM
requests (only the active remote RX sends ACM request messages).
• In the RX direction, both the active and the standby carriers follow the
remote Active TX profile (which is the only active transmitter).
1+1 HSB Configuration
10
Page 211
1+1 HSB Configuration
• Select Member 1
• We support up to 4 Protection Groups
• 1+1 HSB – only for non ABC radio configuration

• 1+1 HSB SD – only for ABC radio configuration
ABC will be supported in future release
• Summary
• Select Member 2 • Submit
Copy to Mate
Configure first (Main) radio link (MRMC, Freq., Link ID)

1. Select first radio link for Primary radio location
2. Select Copy to mate source radio location (In this case 1st link)
3. Apply new setting
4. Click on the Copy to Mate button
Page 212
Thank You
Page 213
Page 214
Configuration Management &
Software Download

December 2014, ver4
Agenda
• Backup and Restore
• Software Download
• RFU Software Installation
• Unit Info
Page 215
Backup & Restore
Backup and Restore

• Backup and restore can be used for
• Restoring configuration upon unit replacement
• Duplicating configuration
• Three restore points
• Restore point are manually created
• Backup file is generated from a restore pointed
• Once a backup file is imported to a unit it can be restored
Page 216
Backup Process
Backup Configuration File Idea

1. Install FTP server – We recommend to use FileZilla Server (not Client)
2. Setup FileZilla Server parameters (Users, Shared Folders)
3. Synchronize Time via CLI
“platform management time-services utc set date-and-time 30-01-2014,15:07:58”
4. Setup communication parameters for IP20 unit with FTP Server
5. Create Configuration Backup inside IP20 unit
6. Export Configuration Backup to FTP server
Export
File
FTP IP address
Page 217
2. FTP Setup – FileZilla Settings
1. Install FileZilla Server and Run it
2. Create User in FileZilla Server
2. FTP Setup – FileZilla Settings

3. Create shared folder in FTP Server PC (C:\ Backups)
4. Setup all permissions for this folder in FTP Server
FTP SERVER PC
FileZilla settings in FTP SERVER PC
5. Check Firewall settings in FTP Server PC and if port 21 is used only with
FileZilla
Page 218
3. IP20G Configuration Management Settings
Setup Parameters for FTP Server Connection
Status for File transfer
Status for for Backup creation
User name and password

must be same as in FileZilla
Server
FTP Server IP address
Path in Server (This setup means that
file will be uploaded in C:\Backups)
Name.zip (.zip is MANDATORY)

!!!
Restore point selection
Time installation for future releases
4. Backup process
6. Check Export status
4. Check Status
1. Setup Configuration parameters

included Restore Point which will be
used for Configuration Backup inside
the system
2. Apply 5. Export 3. Backup
Page 219
Restore Process
Restore Configuration File Idea

1. Install FTP server (when is not already installed) – we recommend to use FileZilla
Server (Not Client)
5. Import Configuration Backup from FTP Server
6. Restore Configuration Backup
Import File
FTP IP address
Page 220
3. IP20 Configuration Management Settings
Setup Parameters for FTP Server Connection
Status for Backup creation

Server

Path in Server (Means that file will be downloaded
from Home FileZilla directory – in our case
C:\Backups)
!!! Name.zip (.zip is MANDATORY)

Restore point selection
Time installation for future releases
Restore process
4. Check Import status
6. Check Restore status
1. Setup Configurations parameters

included Restore point 1-3
2.Apply 3.Import 5 Restore
RESTORE CONFIGURATION WILL NOT CHANGE CURRENT IP ADDRESS !!!
Page 221
Config_Dump File
Software Download for IDU
16
Page 222
Software Download Idea for IDU
1. Before performing a software upgrade, it is important to verify that the system date
and time are correct.
2. Install FTP server (when is not already installed) – we recommend to use FileZilla
Server (Not Client)
6. UnZip software package for IP-20 to FTP Server shared folder
7. Download software from FTP Server
8. Install downloaded software Software
Download
• Although RFU software is included in the standard installation bundle, the current
software version is not automatically updated in the RFU when an installation is
performed.
• To upgrade the software in an RFU, you must perform the upgrade manually, per slot
IP-20 Software Download Settings

Server
Path in FTP Server (This setup means

that configuration files will be
downloaded from Home FileZilla
directory)
Page 223
Software process download
4. Check Download Status
6. Check Installation Status
1. Setup
Parameters
2. Apply 5. Install Downloaded Software

3. Download
Software Files
from FTP Server
RFU Software Installation
20
Page 224
RFU Software Installation
• Although RFU software is included in the standard installation bundle, the
current software version is not automatically updated in the RFU when an
installation is performed.
• To upgrade the software in an RFU, you must perform the upgrade manually, per
slot.
• This enables you to manage IDU and RFU software versions separately.
• In this version, you must use the Command Line Interface (CLI) to
upgrade RFU software.
RFU Software Installation Procedure

1. The following sequence of commands installs RFU-C software version 2.13 in the
RFU connected to slot 3.
root> platform software show rfu versions
2. The next step is to perform the update and install commands:

root> platform software update rfu version slot 3 radio-port 1
root> platform software install rfu version slot 3 radio-port 1
3. To check the status of an update or install operation, enter the following command:
root> platform software show rfu status
4. Once the installation is complete, the Install Status column should indicate installation
success and the In Progress column should indicate 100 (100%).
5.When the installation is complete, enter the show rfu versions command again to verify
that the new version has been properly installed in both the TCC and the RFU:
root> platform software show rfu versions
Page 225
Unit Information file
23
Unit Info
Status for Unit info creation

Server
Path in Server (This setup means that
!!! file will be uploaded in C:\Backups)

Name.zip (.zip is MANDATORY)
• Includes technical data about the unit and also backup files placed in restore points
• This file can be forwarded to customer support, at their request, to help in analyzing issues
that may occur
Page 226
Create and Transfer process
4. Check Status
6. Check Export status
1. Setup Configuration
parameters included Restore
Point which will be used for
Configuration Backup inside the
system
2. Apply 3. Create 5. Export
Thank You
Page 227
Page 228
Native TDM

November 2014 Version 3
Agenda
• Native TDM Services
• Hybrid Service Engine – TDM + Ethernet
• All-packet services example: Ethernet EVCs + TDM Pseudowire
• How to Setup Native TDM
• TDM Path Protection

2
Page 229
Native TDM Services
• IP-20G provides integrated support for transportation of TDM (E1) services
with integrated E1 and ch-STM-1 interfaces.
• Two types of TDM services are supported using the same hardware:
• Native TDM trails
• TDM Pseudowire services (enabling interoperability with third party
packet/PW equipment)
• IP-20G provides native TDM support, utilizing a cross-connect module to

support up to 512 TDM trails.
• The IP-20G Web EMS provides a simple and easy-to-use GUI that enables
users to provision end-to-end TDM trails. The Services Provisioning GUI
includes the following trail-creation end points:
• TDM interface
• Radio interface

3
Hybrid Services Engine – Ethernet + TDM

Services engine
TDM cross-connect (VCs)

E1 TDM
Ch-STM1
traffic
Hybrid
TDM
PW
Radio
Network processor (EVCs)
Packet
traffic
GE/FE
• Native TDM Services (VCs)

• Ethernet Services (EVCs)
• Ethernet switched (L2) services – E-Line (PtP), E-LAN (MPtMP)
• Ethernet port based (L1) services (“smart pipe”)
• TDM Pseudowire services – Unstructured (SAToP), Structured (CESoP)

4
Page 230
Hybrid services example: Ethernet EVCs + Native TDM
TDM cross-connect (VCs)
E1/
Port SAP
ch-STM1
Ethernet Services (EVCs)
User Port PtP Service

(UNI)
TDM
traffic
Hybrid
GE/FE Port SAP SNP
SAP SAP Packet Radio
traffic
MPtMP Service
User Port SAP SNP Network

(UNI) Port
GE/FE Port Port GE/FE
SAP SNP

5
All-packet services example: Ethernet EVCs + TDM Pseudowire

TDM PtP Service
PW
E1/DS1/
Port SAP
SAP SNP
SAP
ch-STM1/
OC3

(UNI)
S-VLAN =
200
GE/FE Port SAP SNP Packet Packet
SAP SAP traffic Radio
MPtMP Service

(UNI) Port
SAP SNP

6
Page 231
How to Setup Native TDM
Native TDM Configuration
VC‐1 VC‐2 VC‐3 VC‐4

VC‐9 VC‐10 VC‐11 VC‐12
VC‐13 VC‐14 VC‐15 VC‐n
E1#1-16 (or STM-1 VC)

Loop Timing
TDM
Network
8
Page 232
TDM Service Configuration 1
As first we have to create any Eth. service for Radio port, because we need specify
which type of traffic will be carry by Radio.
Create any service point which is connected to the radio port in Ethernet/Services …

9
TDM Service Configuration 2
1
2
3
1 – Select required TDM card

2 – Select required E1or VC
3 – Select Timing
Loop Timing – Timing is taken from incoming traffic.
Recovered Clock – Clock information is recovered on the egress path. Extra information may be located
in an RTP header that can be used to correct frequency offsets. Recovered Clock can provide very
accurate synchronization, but requires low PDV (Packer Delay Variation).
System Reference Clock – Trails are synchronized to the system reference clock.
Front Panel – Trails are synchronized from Front Panel synch. port.
Page 233
Native TDM Configuration
Select Required TDM Card and Timing
E1#1-1

11
TDM Service Configuration
Select VC for radio slot VC‐1 VC‐2 VC‐3 VC‐4

VC‐9 VC‐10 VC‐11 VC‐12
VC‐13 VC‐14 VC‐15 VC‐n
E1#1-1
Page 234
1 2
In remote end it needs to be set vice

versa according to drawing below
Selection Summary
Page 235
TDM Path Protection
15
TDM Path Protection

• TDM path protection enables the operator to define two separate network
paths for a single TDM service.
• Two different kinds of path protection are available, each suitable for a
different network topology:
• 1:1 and 1+1 TDM path protection is suitable for ring networks that consist
entirely of IP-20N and/or IP-20G elements with two end-point interfaces for
the TDM trail.
• 1+1 Dual Homing TDM path protection is suitable for networks in which the
IP-20N and/or IP-20G elements are set up as a chain connected to the third
party networks at two different sites.
• The ring is closed on one side by the IP-20N and/or IP-20G elements,
and on the other by third party equipment supporting standard SNCP.
• In this case, there are three end-point interfaces in the IP-20N and/or
IP-20G section of the network.
Page 236
1:1 TDM Path Protection
Active Backup
Path Path
• 1:1 TDM path protection enables the operator to define two separate network paths for a single
TDM trail.
• Each trail has the same TDM interface end points, but traffic flows to the destination via different
paths.
• Bandwidth is utilized only on the active path, freeing up resources on the standby path.
• For native TDM services TDM path protection is done by means of configuring active and backup
path at the TDM service end-points.
1+1 TDM Path Protection
Active Backup
Path Path
• 1:1 TDM path protection enables the operator to define two separate network paths for a single
TDM trail.
• Each trail has the same TDM interface end points, but traffic flows to the destination via different
paths.
• Bandwidth is utilized for both paths parallel.
• For native TDM services TDM path protection is done by means of configuring active and backup
path at the TDM service end-points.
Page 237
1+1 Dual Homing TDM Path Protection
• 1+1 TDM dual homing path protection is used for networks in which the IP-20 network elements are
set up as a chain connected to third party networks at two different sites, where one end-point is
located on an IP-20 unit and the other end-point is located on third-party equipment supporting
standard SNCP.
• As with 1:1 TDM path protection, the operator defines two separate network paths for a single TDM
trail. However, unlike path protection, traffic flows through both paths simultaneously, thereby
supporting standard SNCP in the third party equipment.
Configuration of Path Protection
20
Page 238
Configuration for 1:1 and 1+1 TDM Path Protection
1:1 or 1+1 TDM Protection
Active Backup
Path Bypass Bypass Path
configuration configuration
Trail ID 1 Trail ID 2
Radio Slot 1 E1#1 Radio Slot 2
VC-1 Slot 1 VC-1
Configuration 1:1 or 1+1 TDM Path Protection
1 2 3
or
4 5
Active Backup
Path Bypass configuration
Bypass configuration Path
Radio Slot 1 Radio Slot 2
E1#1
VC-1 VC-1
Slot 1
Page 239
TDM Service
Interface #1 Interface #2 Protection Interface
Configuration for 1+1 Dual homing Edge
1+1 Dual homing 1+1 Dual homing

network edge network edge
1+1 TDM Protection
Page 240
Thank You
Page 241
Page 242
TDM Pseudowire

July 2014 version 2
Agenda
• TDM over PSN
• TDM Pseudowire supported Standards
• General protocol
• TDM Structure and Transport Mode
• How to Configure Pseudowire Service without OAM
• How to Configure Pseudowire Service with OAM
• Synchronization
• Absolute mode
• Differential mode
• Adaptive mode
• Loop mode
Page 243
TDM over Packet Switch Network
TDM Network Packet Switch Network TDM Network
TDM TDM
Pseudowire PSN Pseudowire
PSN – Packet switch network
TDM Pseudowire supported Standards

• TDM Pseudowire supports the following standards:
• SAToP – RFC 4553
• CESoP – RFC 5086
• TDM Pseudowire is compliant with the following encapsulations:

• Ethernet Layer 2 (MEF-8)
• IP/UDP (IETF)
• MPLS (MFA8)
CESoP mode is planned for future release.

UDP/IP and MPLS are planned for future release.
Page 244
General Protocol Stack Reference Model
Emulated Service Emulated Service Emulated Service

(e.g. TDM, ATM) (e.g. TDM, ATM)
Payload Pseudowire Payload
Encapsulation Encapsulation
Demultiplexer Demultiplexer
PSN Tunnel PSN Tunnel PSN Tunnel
PSN & Physical PSN & Physical
Layers Layers
PSN
TDM structure and Transport Mode

Standards:
1. SAToP - Structure-Agnostic TDM over Packet

• Actually agnostic to the E1 framing / structure ,splitting channel into different
services can not be done, transfer full E1s as they are can be encapsulated
with either UDP/IP or Ethernet
2. CESoP - Circuit Emulation Services-over-Packet

• Can manipulate in DS0 timeslots channels, has a specific build for each E1
type.
• In order to know where the DS0 are, CESoP must understand the frame.
• Is planned for future release.
3. CESoP - CAS Circuit Emulation Services-over-Packet

• In addition to regular CESoP it has signaling CAS (which happen in a
separate timeslot).
• Is planned for future release.
Page 245
All-packet services example: Ethernet EVCs + TDM Pseudowire

TDM PtP Service
PW
E1/DS1/
Port SAP
SAP SNP
SAP
ch-STM1/
OC3

(UNI)
S-VLAN =
200
GE/FE Port SAP SNP Packet Packet
SAP SAP traffic Radio
MPtMP Service

(UNI) Port
SAP SNP
How to configure it?
Page 246
TDM Pseudowire configuration
TDM TDM
PSN
port port
PSN PSN PW
PW
Eth. Service PSN PW
Tunnel Tunnel
Tunnel
1. For PW configuration is PW license needed (Is not included in Demo license)

2. TDM Interfaces E1/DS1 Configuration
3. PW profile (Payload, Jitter buffer depth – we recommend to use default values)
4. PSN Tunnel (Ethernet, VLAN ID, Pbit, Destination Mac address, MAID)
5. PW service – (SAToP, Tunnel Type - Eth, select TDM Interface slot, PW Profile number
(PSN Tunnel ID, Clock, Source and Destination Tunnel Identifier)
6. Create Ethernet Services with the same VLANs as in PSN Tunnel Configuration
Pseudowire configuration without OAM
10
Page 247
IP-20 Pseudowire Configuration
TDM PW Configuration Eth Service
PSN Tunnel VLAN 10/Pbit7 with Destination Mac:xx:02 Configuration
VLAN10 PtP Service
VLAN10 VLAN10
PW Service ID1
E1/DS1/ Source Tunnel Identifier 1
Port /Destination Tunnel Identifier 2 SAP SNP
ch-STM1/ SAP SAP
OC3 PW Profile 1
MAC xx:01

PSN Tunnel VLAN 10/Pbit7 with Destination Mac:xx:01
Configuration
VLAN10 PtP Service
VLAN10 VLAN10
PW Service ID1
Port SAP SNP
ch-STM1/ /Destination Tunnel Identifier 1 SAP SAP
OC3 PW Profile 1
MAC xx:02
1. Check PW license
Page 248
E1/DS1/
Port
2. TDM Interface Configuration

ch-STM1/
OC3
1. Enable port
2. Select Timing – synchronization will be explained later
3. TDM Parameters
PW Profile 1
3. PW Profile
• We recommend to use default configuration
• This profile is possible to change when we operate with 3rd party equipment
• Payload Size - Displays the number of times E1 is sampled for each Ethernet packet.
• Jitter Buffer Depth - Displays the desired jitter buffer depth (from 1 to 32, in milliseconds). This is used to enable the
network to accommodate PSN-specific packet delay variation. The jitter buffer can be increased if the network
experiences a higher-than-normal level of jitter.
Page 249
4. PSN Tunnel
Local PW Mac address
1. Select Tunnel ID – e.g. 1

2. Tunnel Admin - Disable
3. Tunnel Type – e.g. Eth
4. Destination MAC address – Mac address of PW on remote site\ Pseudowire\Configuration and check MAC on remote end.
MAC address is not needed if OAM (CFM is used - In this case you can leave it empty). We are not using CFM in our case
so we have to add MAC manually.
5. Select VLAN ID for Tunnel – e.g. VLAN C-10
6. Tunnel Pbit – e.g. Pbit=7
7. Maintenance Association ID – 0 when OAM (CFM is not used)
8. Apply
9. Edit created PSN Tunnel ID 1 and change Tunnel Admin - Enable
PW Service
Source Tunnel Identifier 1
5. PW Service /Destination Tunnel Identifier 2
1. Service ID – e.g. 1
2. Admin State – Disable (You need create PW service itself, just after that you will be able to enable it)
3. Service Type – SAToP - we support SAToP in this software version only
4. Tunnel Type – Eth
5. TDM Interface – Select used TDM card – e.g. TDM slo3 port1 (port1 = E1#1)
6. PW Profile – we have to use same ID as in steep 3 - PW Profile (our case 1)
7. Tunnel ID – we have to use same ID as in steep 4 - PSN Tunnel (our case 1)
8. Clock Recovery – no - Indicates whether the service is used as a reference for clock recovery.
9. Source Tunnel Identifier – 1 on remote site configuration it will be 2
10. Destination Tunnel Identifier – 2 on remote site configuration it will be 1
11. Path Protection – no if path protection is not used
12. Apply
13. Edit created PW Service ID 1 and change admin status - Enable
Page 250
Where are we with actual configuration?
VLAN 10 PtP Service
VLAN10 VLAN10
PW Service ID1
ch-STM1/ SAP SAP
OC3 PW Profile 1
MAC xx:01

We have preconfigured only local PW service.
Configuration
PtP Service
Now we are going to create Ethernet service and connect it with PW
VLAN10
service
PW Service VLAN10
Port
Remember
ch-STM1/ that PSN Tunnel in our configuration
/Destination Tunnel Identifier 1
PW Profile 1
has C-VLANSAP
SAPID 10 SNP
SAP
OC3
MAC xx:02
6. Ethernet Service
1. Create P2P service with two SPs (MP service will be affected by MSTP)
2. In our case we would like to transport TDM via C-VLAN ID 10
Page 251
Where are we with actual configuration?
VLAN 10 PtP Service
VLAN10 VLAN10
PW Service ID1
ch-STM1/ SAP SAP
OC3 PW Profile 1
MAC xx:01

We configured only local PW service with Ethernet Service
Configuration
PtP Service
Try to configure remote site and run TDM traffic VLAN10
PW Service VLAN10
Port
Good
ch-STM1/luck ;) /Destination Tunnel Identifier 1
PW Profile 1
SAP
SAP SNP
SAP
OC3
MAC xx:02
Performance Monitoring
Page 252
Line Alarms
An example: Line alarms number 1040 = ( 10000010000 ) = 1024 + 16
It means that 1024 is Transceiver Loss of Multi-frame and 16 is Transceiver AIS alarm
Pseudowire configuration with OAM
22
Page 253
OAM Maintenance Domain
Maintenance Domain (MD)
• In Ethernet CFM, an MD is a management space for monitoring and administering of a network. An MD is

owned by a Maintenance Entity (ME). Figure shows different MDs, each owned by a single entity.
• A unique maintenance level from 0 to 7 is assigned to each domain. The larger the domain, the higher the
value. For instance, the customer domain in figure 1 would be assigned the highest value, 7, while the
operator domain would be assigned the lowest value, 0. The MDs are defined to have hierarchical
relationships with other domains. Domains cannot intersect, however, they can be touching &/or nested.
• Ethernet CFM exchanges messages and performs operations on a per-domain basis. For instance, in
figure, CFM running at Operator 1 level does not allow discovery of the network by Provider or Customer
level.
OAM Maintenance Point

Maintenance Point
• A Maintenance Point is a demarcation point for the CFM frames. It is an interface (physical port or
logical interface) that participates in an MD. A maintenance point filters the CFM frames by dropping
frames that do not belong in the correct MD. The maintenance points must be configured manually.
There are two types of maintenance points-
1. Maintenance Endpoint (MEP): MEPs initiate and terminate CFM messages. MEPs define the
boundary of an MD.
2. Maintenance Intermediate Point (MIP): MIPs receive CFM messages and respond to originating
MEPs. A MIP never initiates messages and does not expect any CFM messages.
Page 254
Maintenance Association (MA)
The following rules apply to CFM message processing:
• If the MD level of the CFM message is higher than the MD level of the MEP/MIP, the MEP/MIP transparently passes the CFM
message.
• If the MD level of the CFM message is lower than the MD level of the MEP/MIP, the MEP/MIP discards the CFM message.
• If the MD level of the CFM message is equal to the MD level of the MEP/MIP, the MEP/MIP processes the CFM message.
Depending on the type of CFM message, the MEP/MIP responds to, transports to or accepts the message.
IP-20 Pseudowire Configuration Maintenance

Domain ID 1
Maintenance
Association 1
C- VLAN 10
PtP Service
VLAN10 VLAN10
PW Service ID1
ch-STM1/ SAP SAP
OC3 PW Profile 1
MEP1
MAC xx:01

Configuration
PtP Service
MEP2
MAC xx:02 VLAN10 VLAN10
PW Service ID1
Port SAP SNP
ch-STM1/ /Destination Tunnel Identifier 1 SAP SAP
OC3 PW Profile 1
Page 255
1. Check PW license
2. Maintenance Domain
1. Maintenance ID 1
2. Domain Name
3. Level – recommend to use 7
Page 256
3. Maintenance Association
1. Maintenance association ID 1
2. Maintenance domain ID must be identical with step 2 =1
3. Local MEP ID =1 Remote MEP ID 2 (MAC addresses for TDM cards will be not needed. OAM will find
out correct MAC addresses
4. VLAN type – in our case C-VLAN 10
5. CCM Admin – Enable – when it will be disabled CFM will not find out remote MEP (remote MAC
address of TDM card)
4. Ethernet Service
1. Create P2P service with two SPs (MP service will be affected by MSTP)
2. In our case we would like to transport TDM via C-VLAN ID 10
Page 257
5. Check Maintenance Association
When OAM is not running or Ethernet service is not created on both ends,
system cannot identify remote MAC
When Maintenance domain, Maintenance Association, Ethernet service are

setup correctly on both ends , OAM will be able identify MAC address of remote
site
E1/DS1/
Port
6. TDM Interface Configuration

ch-STM1/
OC3
1. Enable port
2. Select Timing – synchronization will be explained later
3. TDM Parameters
Page 258
PW Profile 1
7. PW Profile
• We recommend to use default configuration

• This profile is possible to change when we operate with 3rd party equipment
• Payload Size - Displays the number of times E1 is sampled for each Ethernet packet.
• Jitter Buffer Depth - Displays the desired jitter buffer depth (from 1 to 32, in milliseconds). This is used to enable the
network to accommodate PSN-specific packet delay variation. The jitter buffer can be increased if the network
experiences a higher-than-normal level of jitter.
8. PSN Tunnel
PSN Tunnel VLAN 10/Pbit7
1. Select Tunnel ID – e.g. 1

2. Tunnel Admin - Disable
3. Tunnel Type – e.g. Eth
4. Destination MAC address – should stay empty because in background is running OAM
5. Select VLAN ID for Tunnel – VLAN C-10
6. Tunnel Pbit – e.g. Pbit=7
7. Maintenance Association ID – 1 identical with step 2
8. Apply
9. Edit created PSN Tunnel ID 1 and change Tunnel Admin - Enable
Page 259
PW Service
Source Tunnel Identifier 1
9. PW Service /Destination Tunnel Identifier 2
1. Service ID – e.g. 1
2. Admin State – Disable (You need create PW service itself, just after that you will be able to enable it)
3. Service Type – SAToP - we support SAToP in this software version only
4. Tunnel Type – Eth
5. TDM Interface – Select used TDM card – e.g. TDM slo3 port1 (port1 = E1#1)
6. PW Profile – we have to use same ID as in steep 7- PW Profile (our case 1)
7. Tunnel ID – we have to use same ID as in steep 8- PSN Tunnel (our case 1)
8. Clock Recovery – no - Indicates whether the service is used as a reference for clock recovery.
9. Source Tunnel Identifier – 1 on remote site configuration it will be 2
10. Destination Tunnel Identifier – 2 on remote site configuration it will be 1
11. Path Protection – no if path protection is not used
12. Apply
13. Edit created PW Service ID 1 and change admin status - Enable
Synchronization
Page 260
It is matter of synchronization
• When we talk about synchronization we always mean in the outgoing TDM
direction. The modes determine how the outgoing TDM signal’s clock is
generated
• 4 Clock modes
• Absolute – PW service takes the clock signal from any reference (using the
front panel) as GPS, 1588 etc.
• Differential – PW service is using time difference stamp inside PW

headers. This is the way how we could know difference between local and
far end in term of synchronization (supported in future releases).
• Adaptive - PW TDM port recovers the clock from the incoming PW packets
(supported T7.2)
• Loop – PW service is in loop mode (will be explained later)
Absolute clock
GPS for example - Clock coming from the front panel or from the
NativeSync mechanism
Sync
TDM
MUX
TDM
Pros:
• Accurate
• Doesn’t require any bandwidth MUX
Cons:
• You can say that GPS (or any other external clock) requires extra infrastructure.
•The entire network from end to end must support sync distribution
Page 261
Differential clock
TGPS TGPS
ᵟdelta
What is delta
between E1
and GPS ?
E1=TGPS േᵟdelta
E1
Pros:
• Accurate
• Differential clock allows transporting of E1s with different clocks (absolute does not)
Cons:
• Require GPS on each site and configure each of them
ACR (Adaptive Clock Recovery)
Local Remote
E1 E1
Pros:
• Does not require any addition clock (GPS, NativeSync BW)
• Can be used over non-Ceragon networks
Cons:
• Does not recover so fast as in case of RSTP re-convergence / Protection switches
• Lower performance than absolute clock
Page 262
Loop type
LOOP TYPE in General
Loop
E1
3th 3th
party Network
party
Generating clock Receiving clock
Loop mode is based on the assumption that the signal coming back should have the same clock as the
signal being injected into the network.
LOOP TYPE in IP-20G
IP-20 IP-20
3th E1 Network Any mode
party
Loop mode
The point in loop is to shorten as much as possible the path the originating clock goes through before it
is sent back.
Thank You
Page 263
Page 264
Troubleshooting

December 2014, ver 3
Agenda
• Faults and Alarms
• Performance monitoring
• RMON statistic
• Loopback
Page 265
Faults and Alarms
Faults
Current Alarms
Event Log
Page 266
Alarm Configuration
Performance Monitoring - Radio
Page 267
Radio Parameters
Profile Mod MSE Down-Threshold MSE Up-Threshold

0 QPSK -18
1 8PSK -16 -19
2 16QAM -17 -23
3 32QAM -21 -26
4 64QAM -24 -29
5 128QAM -27 -32
6 256QAM -30 -34
7 512QAM -32 -37
8 1024 QAM SFEC -35 -38
9 1024 QAM WFEC -36 -41
10 2048QAM -39
Applicable for both 28/56MHz , 2048 QAM will be supported in 7.9
The values are typical and subject to change in relation to the frequency and RFU
type. For more details please contact your Ceragon representative
Radio Parameters – Defected Blocks
Page 268
MRMC actual status
Signal Level
Page 269
MSE – Mean Square Error
MRMC
Page 270
Radio Thresholds
• Displays a table of every radio threshold settings
Radio Traffic - Capacity
• The Capacity PM Table page displays Radio Ethernet Capacity in Mbps for either radio for 15 minutes or 24 hours intervals
Page 271
Radio Traffic - Throughput
• The Throughput PM Table page displays Radio Ethernet Throughput in Mbps for either radio for 15 minutes or 24 hours intervals
Radio Traffic - Utilization
• The Utilization PM Table page displays Radio Ethernet Utilization for either radio for 15 minutes or 24 hours intervals
Page 272
Radio Traffic - Frame error rate
• The Frame error rate PM Table page displays Radio Frame error rate for either radio for 15 minutes or 24 hours intervals
Header Compression counters
Page 273
Performance Monitoring – Ethernet Services
ETH PM – RMON
Page 274
PM – RMON – Special Registers
RMON register / Counter Description
Undersize frames received Frames shorter than 64 bytes
Oversize frames received Frames longer than 2000 bytes
Total frames received with a length of more than 2000 bytes,
Jabber frames received
but with an invalid FCS
Total frames received with a length of less than 64
Fragments frames received
bytes, and an invalid FCS
Rx error frames received Total frames received with Phy‐error
Total frames received with CRC error, not countered in
FCS frames received
"Fragments", "Jabber" or "Rx error" counters
Pause frames received Number of flow‐control pause frames received
Troubleshooting with RMON: Oversized frames
Site A Site B
T T T A
Tagged Frames with frame

size > 2000 bytes
When ingress frames exceed the maximum frame size, RMON counter “Oversized frames received”
is updated accordingly
Page 275
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
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 MC CIR
rules
Page 276
Ethernet TX / RX PM - Enabling
• Enable Tx / RX Performance collection for specific Ethernet / Radio Port

• It will enable TX and RX Performance collection
Ethernet TX / RX PM
• Performance based on 15 min and 24 hours
Page 277
Ethernet TX / RX PM – View / Threshold window
Performance Monitoring – TDM Services
Page 278
TDM – Line Alarms
An example: Line alarms number 1040 = ( 10000010000 ) = 1024 + 16
It means that 1024 is Transceiver Loss of Multi-frame and 16 is Transceiver AIS alarm
TDM port PMs Table
Page 279
Loopbacks
RFU RF Loopback
IF LB
RFU RF LB
Page 280
TDM Loopback
Ethernet Loopback
• Select port and click to Loopback button
Page 281
Ethernet Loopback Setting
• Enable Swapping MAC addresses

• Enable admin status
Thank You
Page 282
Multiple Spanning Tree Protocol (MSTP)
November 2013
Version 2
Agenda
• STP – Spanning Tree Protocol
• How does STP work?
• MSTP
• Physical and Logical Topology
• MST Instance
• MST Region
• Region Boundary
• CST – Common Spanning Tree
• BPDU
• MSTP DEMO
• MSTI root
• Ports Role
• Ports Definition
• CIST
• Interoperation between two Regions
• How to configure MSTP
Page 283
STP – Spanning Tree Protocol
Network with Loops
SW3
SW1
SW2
When we will connect all switches together, we will create an Ethernet loop
Page 284
Ports in STP protocol
root
SW - Root Bridge is switch with the lowest Bridge ID
- Root port forward traffic to Root bridge

- Designated port forward traffic away from the Root and towards the leaves
- Non-Designated port - Blocked port which listen, no-talking
Bridge ID: x00-03
SW3
root
Bridge ID: x00-01 SW1
SW2 Bridge ID: x00-02
How does STP protocol work? IEEE 802.1D

Bridge ID : x00-05 SW3
Bridge ID: x00-02 SW2 SW4 Bridge ID: x00-04
root
Bridge ID: x00-03 SW1 SW5
SW5
Bridge ID: x00-01
1.Who is the Root Bridge?
2.Determine Root ports
3.Pair Root ports with Designated ports
4.Determine Designated Ports & Blocked Ports http://www.youtube.com/watch?v=iB7BxtZVy3c
Page 285
Where is the problem with STP?
SW3
SW2 SW4
1Gbps
1Gbps
Total 2Gbps
1Gbps root
SW1 SW5
SW5
Problem is a load balancing in your network (“capacity balance”). Why do not have doubled
capacity with usage different services?
This is the reason for using MSTP or G.8032 protocols as will be described in next slides
MSTP
Page 286
Physical and Logical Topology
SW3 SW3
= +
1Gbps 500Mbps
SW1 SW2 SW1 SW2
Physical Topology Logical Topology 1
+ SW3
+ SW3
500Mbps
SW1 SW2 SW1 SW2
Logical Topology 2 Logical Topology 3

VLANs 10, 20, 30 are VLANs 40, 50, 60 are
mapped to MSTP mapped to MSTP
SW3 Instance 1. Link Instance 1. Link
SW3 between SW1 &
between SW1 &
SW3 is blocked SW3 is blocked
SW1 SW2 SW1 SW2

The figure demonstrates six VLANs using two MSTP instances.
The question is: “What is the Instance?”
The Instance represents each logical topology. In our case we have two
Logical Topologies, it means two Instances
Page 287
MSTI – MST Instance
SW5
SW1
SW3
SW4
SW4
Physical
Logical SW2
REGION 2
topology
Topology
SW1 SW2
REGION 1 SW3
Instance 0 (IST – MSTI0) – is internal instance, designated to carry all STP-related information.
Instance 1 (MSTI1)(e.g. VLANs: 10, 20, 30)
Instance 2 (MSTI2)(e.g. VLANs: 40, 50)
Instance 3 (MSTI3)(e.g. VLANs: 60, 70, 80, 90)
MSTI - One of a number of Spanning Trees calculated by MSTP within an MST Region,
to provide a simply and fully connected active topology for frames classified as belonging
to a VLAN that is mapped to the MSTI by the MST Configuration Table used by the MST
Bridges of that MST Region.
MST Region
SW5
SW3 SW1
SW4
SW4
SW2
REGION 2
SW1 SW2
SW3
REGION 1
Each switch running MST in the network has a single MST configuration that consists of these three
attributes:
1. Configuration ID
2. An alphanumeric configuration name (32 bytes)
3. A configuration revision number (two bytes)
4. A 4096-element table that associates each of the potential 4096 VLANs supported on the chassis to a
given instance
In order to be part of a common MST region, a group of switches must share the same configuration attributes.
It is up to the network administrator to properly propagate the configuration throughout the region.
Page 288
MST Region Configuration Identifier
A parameter used to determine if a set of Bridges belongs to a single
region. Consists of several values:
• Configuration ID Format Selector – value of “0” indicates use of following
fields as defined in IEEE 802.1Q™-2003.
• Configuration Name – “A variable length test string encoded within a fixed
field of 32 octets”1, used to identify a MST region with a human readable
name.
• Revision Level – unsigned number in 2 octet field
• Configuration Digest – 16 field resulting from HMAC-MD5 encoding of the
MSTI column of a MSTI to VID table. “the MST Configuration Table is
considered to contain 4096 consecutive two octet elements, where each
element of the table (with the exception of the first and last) contains an
MSTID value encoded as a binary number, with the first octet being most
significant.”2
1 – IEEE Std 802.1Q™-2003 sub-clause 13.7

2 – IEEE Std 802.1Q™-2003 sub-clause 13.7
Region Boundary
SW5
SW3 SW1
SW4
SW4
SW2
REGION 2
SW1 SW2
SW3
REGION 1
Boundary Ports
• Boundary ports – are ports at the boundary of a region if the designated bridge on
its segment is in a different region.
• Between Regions is used standard Single STP protocol (CST)
BPDU – Bridge Protocol Data Unit CST – Common Spanning Tree
Page 289
Common Spanning Tree - CST
SW5
SW3 SW1
SW4
SW4
SW2
SW1 SW2
MST REGION 1 SW3
CST – Common Spanning Tree

CIST – IST+CST Common Instance
• Remember that MST must be able to interact with 802.1q based networks, a
bridged network only implements Single Spanning tree (Common Spanning Tree)
• The IST instance is simply an RSTP instance that extends the CST inside the MST
region.
BPDU – Bridge Protocol Data Unit CST – Common Spanning Tree
BPDU – Bridge Protocol Data Unit

Preamble SFD DA SA Length/Type Payload FCS
7 bytes 1 byte 6 bytes 6 bytes 2 bytes 46‐1500 bytes 6 bytes
Related to CIST Root
CIST Regional Root
Page 290
MSTP BPDU
SW3
SW1 PI MSTI1 MSTI2 MSTI3 SW2
Each switch only sends one BPDU, but each includes one MRecord per
MSTI present on the ports.
PI Protocol Information for the IST
CIST Root Bridges Election Process

• When a switch boots up, it declares itself as CIST Root and CIST Regional Root and announces this
fact in outgoing BPDUs. The switch will adjust its decision upon reception of better information and
continue advertising the best known CIST Root and CIST Regional Root on all internal ports. On the
boundary ports, the switch advertises only the CIST Root Bridge ID and CIST External Root Path Cost
thus hiding the details of the region’s internal topology.
• CIST External Root Path Cost is the cost to reach the CIST Root across the links connecting the
boundary ports – i.e. the inter-region links. When a BPDU is received on an internal port, this cost is not
changed. When a BPDU is received on a boundary port, this cost is adjusted based on the receiving
boundary port cost. In result, the CIST External Root Path Cost is propagated unmodified inside any
region.
• Only a boundary switch could be elected as the CIST Regional Root, and this is the switch with the
lowest cost to reach the CIST Root. If a boundary switch hears better CIST External Root Path cost
received on its internal link, it will relinquish its role of CIST Regional Root and start announcing the new
metric out of its boundary ports.
• Every boundary switch needs to properly block its boundary ports. If the switch is a CIST Regional Root,
it elects one of the boundary ports as the “CIST Root port” and blocks all other boundary ports. If a
boundary switch is not the CIST Regional Root, it will mark the boundary ports as CIST Designated or
Alternate. The boundary port on a non regional-root bridge becomes designated only if it has superior
information for the CIST Root: better External Root Path cost or if the costs are equal better CIST
Regional Root Bridge ID. This follows the normal rules of STP process.
• As a result of CIST construction, every region will have one switch having single port unblocked in the
direction of the CIST Root. This switch is the CIST Regional Root. All boundary switches will advertise
the region’s CIST Regional Root Bridge ID out of their non-blocking boundary ports. From the outside
perspective, the whole region will look like a single virtual bridge with the Bridge ID = CIST Regional Root
ID and single root port elected on the CIST Regional Root switch.
• The region that contains the CIST Root will have all boundary ports unblocked and marked as CIST
designated ports. Effectively the region would look like a virtual root bridge with the Bridge ID equal to
CIST Root and all ports being designated. Notice that the region with CIST Root has CIST Regional Root
equal to CIST Root as they share the same lowest bridge priority value across all regions.
Page 291
CIST Root Bridges Election Process
10
S3‐3 S3‐2
P50 P1
Region 3
10 10
S3‐1
CIST Regional
Root for P15
Region3
10 10
CIST Root and 10
CIST Regional 10
Root for
Region1
Region 1
10 10
S1‐1 S1‐3 S2‐1 S2‐3
P0 P200 CIST P20 P5
Regional Region 2
Root for
Region2
S1‐2 S2‐2
P100 P10
20
Conclusion from previous slide
Region 3
Virtual Bridge S3‐1
Priority=15
MASTER Ports
Region 1
Virtual Bridge
Priority=0
Region 2
S1‐1 S2‐1 Virtual Bridge
Priority =20
Page 292
What is necessary to understand
21

There are tree main problems with Ethernet that affect MSTP designs:
1. Unknown unicast flooding results in traffic surges under topology changes.
Those are either result of asymmetric routing or persistent topology
changes. Every topology change causes massive invalidation of MAC
address tables and unicast traffic flooding. This process is the result of
Ethernet topology unawareness – the bridges don’t know MAC addresses
location.
2. Broadcast and Multicast flooding. This is a separate problem as many core
protocols (ARP, IGP, PIM) rely on multicasting or broadcasting. Those
packets should be delivered to every node in a broadcast domain and under
intense load network could be congested at every point.
3. Spanning-Tree Convergence. MSTP uses RSTP procedure for STP re-
negotiation. Since it is based on distance-vector behavior, it is prone to
some convergence issues, such as counting to infinity (old information
circulation). This is especially noticeable in larger topologies with 10+
switches and under special conditions, such as failure of the root bridge.
Page 293
• Topology changes in MSTP are treated the same way as in RSTP. That is,
only non-edge links going to forwarding state will cause a topology change
and the switch detecting the change will flood this information through the
domain. However, single physical link may be forwarding for one MSTI and
blocking for another. Thus, a single physical change may have different
effect on MSTIs and the CIST. Topology changes in MSTIs are bounded to
a single region, while topology changes to the CIST propagate through all
regions. Every region treats the TC notification from another region as
“external” and applies them to CIST-associated ports only.
• A topology change to CST (the tree connecting the virtual bridges) will
affect all MSTIs in all regions and the CIST. This is due to the fact that new
link becoming forwarding between the virtual bridges may change all paths
in the topology and thus require massive MAC address re-learning. Thus,
from the standpoint of topology change, something happening to the CST
will have most massive impact of flooding in the set of interconnected
MSTP regions.
MSTP Demo
24
Page 294
Configuration MSTP regions
Config name: R1 What is necessary to configure for

Rev level:0 MSTP Regions:
R1 1/1
SW2 1. Configuration Name
2. Revision Level
3. Service to Instance mapping
1/2
Config name: R2 Default parameters are:

Rev level:0 1/2 1. Configuration name: R1
2. Revision Level: 0
SW1 3. No Service to Instance Mapping
R2 1/1
R3
1/1
Config name: R1
1/2 Rev level:65535
SW3
MSTI Root
MSTI Root Pri:28672

R1 1/1
In this case SW2 is MSTI Root
SW2
because he has the lowest Bridge
1/2 ID
1/2
Pri: SW1
32768
1/1
1/1 IST has a root bridge, elected based on the

SW3
1/2 lowest Bridge ID (Bridge Priority + MAC address
Pri:57344
Page 295
Port Role
root 1. Root Port – forward BPDUs

SW
The root port exists on non-root bridges and is the switch port with the
best path to the root bridge. Root ports forward traffic toward the root
RP RP bridge
SW1 SW2
root 2. Designated Port – forward BPDUs

SW
DP DP The designated port exists on root and non-root bridges.
• For root bridges, all switch ports are designated ports.
• For non-root bridges, a designated port is the switch port that
RP RP receives and forwards frames toward the root bridge as needed.
Only one designated port is allowed per segment.
SW1 SW2
DP
Port Role
root 3. Alternate Port – Receive BPUDs, not forward BPDUs

SW
DP DP
• Provide connectivity if other Bridges, Bridge Ports, or LANs
fail or are removed.
RP RP • Alternate port is blocking since better cost exist in topology
SW1 SW2
AP DP
root
SW 4. Backup Port - Receive BPUDs, not forward BPDUs
DP DP
• Provide connectivity if other Bridges, Bridge Ports, or LANs
fail or are removed.
RP RP
• Is a specific case of alternate port, when port is from the
same NE or LAN
SW1 SW2
AP DP BP
Page 296
Ports in Region
MSTI Root Pri:28672

1/1 Pri 128 Port decision is based on:
R1 DP SW2
1. Cost
Cost 20 000 2/1 Pri 128 1/2 Pri 64
DP DP 2. Priority
1/2 Pri 128 3. Port Number
RP
Pri: Cost 20 000 Cost 10 000
SW1
32768
1/1 Pri 128
DP ALT RP
2/1 Pri 128 1/2 Pri 128
Cost 20 000 RSTP Cost (802.1D‐2004 /
Data rate STP Cost (802.1D‐1998)
802.1w)
ALT SW3 250 5,000,000
1/1Pri 128 10 Mbit/s 100 2,000,000
16 Mbit/s 62 1,250,000
Pri:57344 100 Mbit/s 19 200,000
1 Gbit/s 4 20,000
10,0004 Mbit/s
2 Gbit/s 3
10 Gbit/s 2 2,000
CIST Configuration
R2
CIST Root Pri:4096

CIST Pri:8192 Cost 10 000 2/2 Pri 128 MSTI Pri:45056
MSTI Root Pri:286722/2 Pri 128
R1 1/1 Pri 128
MST DP
DP 2/3 Pri 128 2/3 Pri 128
ALT DP
2/1 Pri 128 1/2 Pri 64 Cost 20 000
Cost 20 000
DP DP
1/2 Pri 128 RP
CIST Pri:8192
MSTIPri:32768 Cost 20 000 Cost 20 000
1/1 Pri 128

For each bridge we define:
DP ALT RP
Cost 20 000 2/1 Pri 128 1/2 Pri 128 1. MSTI Priority
2. CIST Priority
ALT
1/1 Pri 128
CIST Pri:8192
MSTIPri:57344
Who has the lowest CIST Bridge ID from all regions is a
CIST Root Bridge
Page 297
Interoperation between R1 and R2 with instance 1
CIST Pri:8192 CIST Root Pri:4096

MSTI Root Pri:28672 MSTI Pri:45056 CIST Root Pri: 8192
2/2 Pri 128 Cost 20 000 2/2 Pri 64 MSTI Root Pri:28672
R1 1/1 Pri 128
MST DP
1/1 Pri 128 Cost 20 000 1/1 Pri 128
DP 2/3 Pri 128 2/3 Pri 128
RP DP
ALT DP DP 1/2 Pri 128
2/1 Pri 128 1/2 Pri 64 Cost 20 000
Cost 20 000 1/2 Pri 128
DP DP DP
1/2 Pri 128 RP
Cost 20 000
CIST Pri:8192 Cost 20 000
MSTIPri:32768 Cost 20 000 Cost 20 000
ALT 1/1 Pri 128

1/1 Pri 128
DP ALT RP RP
Cost 20 000 2/1 Pri 128 1/2 Pri 128
1/2 Pri 128
R2
ALT CIST Root Pri: 8192
1/1 Pri 128 MSTI Pri:57344
CIST Pri:8192
MSTIPri:32768
Legend:
Instance 1,
Different routes for different services Instance 2
CIST
CIST Root Pri:4096

MSTI Root Pri:28672/32768 Pri:45056/45056 MSTI Root
2/2 Pri 128 Cost 20 000 2/2 Pri 64
R1 1/1 Pri 128
MST/MST
DP/DP Pri:28672/57344
1/1 Pri 128 Cost 20 000 1/1 Pri 128
DP/RP 2/3 Pri 128 2/3 Pri 128
RP/DP DP/ALT
ALT/ALT DP/ DP 1/2 Pri 128
2/1 Pri 128 1/2 Pri 64 Cost 20 000
Cost 20 000 DP/RP 1/2 Pri 128
DP/DP DP/DP DP/RP
RP/DP
1/2 Pri 128
Cost 20 000
Pri:
32768/ MSTI Cost 20 000
Cost 20 000 Cost 20 000
Root4096
ALT/DP 1/1 Pri 128
1/1 Pri 128
DP/DP ALT/ALT RP/ALT RP/DP R2
Cost 20 000 2/1 Pri 128 1/2 Pri 128
1/2 Pri 128
Pri:57344/ MSTI Root28627

ALT/RP
1/1 Pri 128 EP/EP
Pri:57344/ 57344
EP/EP TESTER
Page 298
Demo topology with 3th party equipment which doesn’t support MSTP,
only RSTP
Legend:
* ‐changed
state
Instance 2,
Instance 3
CIST
R1 MSTI Root Pri:

24576/32768 MST
DP
CIST Root Pri:4096
Pri:45056/45056
MSTI Root
Pri:20480/57344
DP/RP 2/2 Pri 128 2/2 Pri 64 1/1 Pri 128
1/1 Pri 128
ALT DP RP/DP DP/RP
2/3 Pri 128 2/3 Pri 128 1/1 Pri 128
DP/DP DP/DP DP/RP DP

2/1 Pri 128 1/2 Pri 64 1/2 Pri 128
RP/DP 1/2 Pri 128
Pri:
1/2 Pri 128
R2
32768/
MSTI
Root28672 RP/DP ALT
1/1 Pri 128 1/4
DP/DP DP
1/1 Pri 128 ALT/ALT RP/ALT RP
2/1 Pri 128 1/2 Pri 128 1/2 Pri 128
1/3 CIST Pri:32768
Pri:57344/
ALT/RP MSTI Root:24576
1/1 Pri 128
Pri:57344/ 57344
TESTER
How to configure MSTP?
34
Page 299
Enabling and Disabling MSTP
• MSTP is enabled by default
Available commands
Disable MSTP
Enable MSTP
Number of Instances
• IP-20 can support from 1 to 16 MSTI on single unit. This does not include the CIST.
Page 300
Region Definition
For MSTP Regions is necessary setup:
1. Configuration Name
2. Revision Level
3. Service to Instance mapping (available via CLI)
Service ID
Bridge Priority for MSTI and CIST

Bridge MSTI Priority
Bridge CIST Priority
Page 301
MSTI Port - Cost & Priority Setting
CLI - MSTI Port Cost and Priority Settings
CLI -MSTI Port Cost and Priority Settings
CIST Port - Cost & Priority Setting
CLI - CIST Port Cost & Priority Settings
CLI -CIST Port Cost & Priority Settings
Page 302
Thank You
Page 303
Page 304
G.8032 – Ethernet Ring Protection Switching
ERPS
November 2014
Version 3
Agenda
• STP – Spanning Tree Protocol
• G.8032 in General
• G.8032 Principle
• How can we balance our network?
• What is the Instance?
• RPL – Ring Protection Link
• Recovery mechanism for G.8032
• Configuration of G.8032
• CLI Commands
• Web Interface for G.8032
Page 305
STP – Spanning Tree Protocol
Network with Loops
SW3
SW1
SW2
When we will connect all switches together, we will create an Ethernet loop
Page 306
Ports in STP protocol
root
SW - Root Bridge is switch with the lowest Bridge ID
- Root port forward traffic to Root bridge

- Designated port forward traffic away from the Root and towards the leaves
- Non Designated port - Blocked port which listen, no-talking
Bridge ID: x00-03
SW3
root
Bridge ID: x00-01 SW1
SW2 Bridge ID: x00-02
How does STP protocol work? IEEE 802.1D

Bridge ID : x00-05 SW3
Bridge ID: x00-02 SW2 SW4 Bridge ID: x00-04
root
Bridge ID: x00-03 SW1 SW5
SW5
Bridge ID: x00-01
1.Who is the Root Bridge?
2.Determine Root ports
3.Pair Root ports with Designated ports
4.Determine Designated Ports & Blocked Ports http://www.youtube.com/watch?v=iB7BxtZVy3c
Page 307
Where is the problem with STP?
SW3
SW2 SW4
1Gbps
1Gbps
Total 2Gbps
1Gbps root
SW1 SW5
SW5
Problem is a load balancing in your network (“capacity balance”). Why do not have doubled
capacity with usage different services?
This is the reason for using MSTP or G.8032 protocols as will be described in next slides
G.8032
Page 308
G.8032, General
• G.8032 is an ITU standard for Ethernet Ring Protection – ERP
• G.8032 Goals:
• Loop avoidance in every topology
• Topology is constructed out of rings with sub-rings
• Highly reliable and stable protection
• Provide protection switch time in less than 50ms for 16 nodes.
• Load Balancing
• In each instance, RPL may be different
• Sub Ring support (from T7.9)
• http://www.itu.int/rec/T-REC-G.8032-201003-S/en
G.8032, General
• ERPS, as defined in the G.8032 ITU standard, is currently the most
advanced ring protection protocol, providing convergence times of sub-
50ms.
• ERPS prevents loops in an Ethernet ring by guaranteeing that at any time,
traffic can flow on all except one link in the ring. This link is called the
Ring Protection Link (RPL).
• Under normal conditions, the RPL is blocked, i.e., not used for traffic. One
designated Ethernet Ring Node, the RPL Owner Node, is responsible for
blocking traffic at one end of the RPL.
• When an Ethernet ring failure occurs, the RPL Owner unblocks its end of
the RPL, allowing the RPL to be used for traffic.
• The other Ethernet Ring Node adjacent to the RPL, the RPL Neighbor
Node, may also participate in blocking or unblocking its end of the RPL. A
number of ERP instances (ERPIs) can be created on the same ring.
Page 309
G.8032 Principle
S1
RPL – Ring Protection Link

SW
S2 S3
SW
SW
Data link between S1 and S2

G.8032 Principle - Failure

S1

SW
S2 S3
SW
SW

Page 310
How can we load balance a network?
13
SW3 SW3
= +
1Gbps 500Mbps
SW1 SW2 SW1 SW2
Physical Topology Logical Topology 1
+ SW3
+ SW3
500Mbps
SW1 SW2 SW1 SW2
Page 311
VLANs 10, 20, 30 are VLANs 40, 50, 60 are
mapped to Instance mapped to Instance
SW3 1. Link between 1. Link between
SW3 SW1 & SW3 is
SW1 & SW3 is
blocked blocked
SW1 SW2 SW1 SW2

The figure demonstrates six VLANs using two instances.
The question is: “What is the Instance?”
The Instance represents each logical topology. In our case we have two
Logical Topologies, it means two Instances
Instance
SW3
SW4
Physical
Logical
topology
Topology
SW1 SW2
Instance 0 (IST – is default Instance, usually used for management, is not recommended to use it
for VLANs mapping)
Instance 1 (e.g. VLANs: 10, 20, 30)
Instance 2 (e.g. VLANs: 40, 50)
Instance 3 (e.g. VLANs: 60, 70, 80, 90)
Page 312
Ring Protection Links
17
RPLs for Instances

S1 RPL – Ring Protection Link
RPL for Instance 2 SW

RPL for Instance 1
S2 S3
SW
SW
Instance 1 (for example VLAN 10, 20, 30)

Instance 2 (for example VLAN 40, 50, 60)
Page 313
What will happen when failure disappear?
19
G.8032 Principle - Failure

S1

SW
S2 S3
SW
SW
WTR

Page 314
Ring Protection, R-APS Transmission
• A new R-APS message should be transmitted immediately when required
as an output action of ERPI state machine.
• If the R-APS information to be transmitted has been changed, a burst of
three R-APS messages shall be sent as quickly as possible. The interval
between them shall not be more than 3.3ms.
• R-APS messages other than the "event" message, continue to be
transmitted, after the first 3 messages, every five seconds.
• All R-APS messages should be transmitted on both ring ports
• R-APS channel Blocking
• traffic channel blocking  R-APS channel is blocking (except on sub-
rings without an R-APS virtual channel)
• When R-APS is blocked:
• R-APS messages received are not forwarded to the other port
• R-APS messages, locally generated should be transmitted over both ring
port
• R-APS messages received at each port are delivered to the ERP control
• R-APS – Ring – Automatic Protection Switching
R-APS PDU Format

• The R-APS PDU is part of the Y.1731 model.
• R-APS uses multicast MAC address of 01-19-A7-00-00-00 to 01-19-A7-00-00-FF (user config)
• The R-APS PDU uses the ERP service VLAN
• The R-APS PDU uses the Y.1731 Ether-Type of 0x8902
Field Value Description

1011 Signal Fail (SF)
0000 No Request (NR)
1101 Force Switch (FS) (V2 only)

Request/State
0111 Manual Switch (MS) (V2 only)
1001 Signal Degrade (SD) (V2 only)
1110 Event (V2/V1? only)
Other Reserved for future international standardization
Page 315
Ring Protection, Link Failure
Ring Protection, Failure recovery in revertive mode
Page 316
Ring Protection, Priority Logic
Ring Protection, State machine (sample)
Page 317
Configuration of G.8032
27
Let’s configure this Exercise
W
E
W E
Service ID 1 and VLAN 10
W E
W
E
RPL Port
E –East
W-West
Page 318
CLI Configuration for G.8032
29
Useful Commands 1
Available commands
Definition of Instance to EIRP and assignment of Service ID to Instance
For Example we would like to create Instance 1 were inside the instance 1 will be service with ID 1 (Service must be already created)
We have to defined also east and west service points inside a service
Service ID 1
W E
E SP SP
1 2
VLAN 10
W
Instance definition – Instance 0 is not recommended to use
Page 319
Useful Commands 2
How to check Instance to Service mapping?
Instance to service mapping
EIRP Status - (doesn’t matter where, in which node you will check it, because status is the
same in whole ring)
Useful Commands 3
Definition of RPL Owner
Changing of WTR (default value is 5min, minimum should be 1min)
Show all EIRP in your network
Show actual configuration in EIRP #
Page 320
WEB Interface for G.8032
33
First need to be created an Services
• When service is created and you are not able to create ERPI use CLI for Service
to Instance Mapping or WEB GUI
root> ethernet generalcfg instance-to-service-mapping set service sid 1 instance-id 1
root> ethernet generalcfg instance-to-service-mapping show service sid 1 to 10
Page 321
Service to Instance Mapping via web GUI
Web Interface
Page 322
Thank you
Page 323
Page 324
Synchronous Ethernet
December 2014
Version 1
Agenda
• Synchronization in General
• Jitter
• Synchronization Effect
• Concept of Synchronization in IP-20
• Implementation
• T3 Input & T4 output
• SSM and ESMC
• Sync E Clocks types
• Synchronization modes of operation
• Synchronization example
• IP-20G Synchronization Settings
Page 325
Synchronization
• Synchronization can be used to synchronize network elements by
feeding one node with a reference clock, and having other nodes
derive their clocks from that source
• Synchronization enables the receiving side of an interface to lock onto

the physical layer clock of the received signal, which was derived from
some reference clock source
Jitter
• One of the tasks of clock units CLU in TCC is to reduce jitter.
• Jitter period is the interval between two times of maximum effect (or minimum
effect) of a signal characteristic that varies regularly with time.
• Jitter frequency, the more commonly quoted figure, is its inverse.
• ITU-T G.810 classifies jitter frequencies below 10 Hz as wander and frequencies at
or above 10 Hz as jitter.
Page 326
Synchronization effects
• All problems in digital networks, including poor synchronization, are
manifested as errors.
• Degraded speech quality and audible clicks

• Degraded data traffic throughput
• Call setup, takedown, and management problems
• Corrupt or incomplete fax & email messages etc.
• Low speeds
• Freeze-frames and audio pops on video transmissions
• Call disconnects during mobile call hand-off
• Partial or complete traffic stoppage
Concept of Synchronization in IP-20G
Page 327
Synchronization in IP-20G
• Genesis sync mechanism based on CLU (Clock Unit)
• Each interface has it’ s own clock recovery mechanism
• The output clock selected based on quality and priority
• All slots sending clock to CLU
• We are able to select highest priority and
Select one for synch source
Implementation
Page 328
Sync in IP-20G – Implementation
• The clock input selection made by FPGA
• Clock output distributed to all interfaces in the system
• Each interface has option to switch from system clock to local oscillator.
T3/T4
Page 329
T3/T4 in TCC or LIC
• T3 input and T4 output are sharing the same physical connector
T3_IN_N 1
T3 (IN)
PPS – pulse per second T3_IN_P 2
1PPS_P 3
1PPS (Out) T4_OUT_N 4

T4 (Out)
T4_OUT_P 5
1PPS_N 6
PPS_IN_T3_ToD_P 7
1PPS (In) or ToD (Out)
PPS_IN_T3_ToD_N 8
T3 (IN) 2
T3 (In)
LIU T4 (Out) 2
T4 (Out)
Control
TCC
FPGA
1PPS_P
1PPS (out) RS-485
1PPS_N
ToD_1PPS_P
ToD (out) or 1PPS (in) RS-485
ToD_1PPS_N
T3/T4 sync support

• T3 input interface supports as synchronization input Framed E1/T1
and pure 2.048 and 1.544 Mhz clock
• T4 output interface supports as synchronization input Framed E1/T1

and pure 2.048 and 1.544 Mhz clock
Page 330
SSM and ESMC
13
SSM and ESMC
• Synchronization Status Messages (SSMs) are standard messages sent periodically
by each interface in order to inform of the quality of its outgoing signal
frequency across the link
Sync feature :
• The processing of received SSMs in order to determine the interface status
• Determining the information to be sent in each interface’s SSMs
• The format of the messages for each interface type
ESMC - Ethernet Synchronization Message Channel
Page 331
SSM timing
Genesis supports also timing SSM requirements :
• Switching quality from PRC to SSU in the same interface requires 200ms for SSM change
• In case of new SSM switchover it can take from 180ms up to 500ms (180+320ms)
SSM and ESMC Quality values
E1 Systems T1 Systems
Quality Value Quality Value
G.811* 0010 PRS * 0001
SSU‐A* 0100 Stratum 2 * 0111
SSU‐B* 1000 Transit Node * 0100
G.813/8262 1011 Stratum 3E * 1101
DO NOT USE 1111 Stratum 3 * 1010
SMC 1100
Unknown 0000
DO NOT USE 1111
Page 332
Sync E Clocks types
Sync E Clocks (ITU-T Rec. G.8262)

• ITU-T G.8262 defines Synchronous Ethernet clocks compatible with SDH
clocks. Synchronous Ethernet clocks, based on ITU-T G.813 clocks, are
defined in terms of accuracy, noise transfer, holdover performance, noise
tolerance, and noise generation
Page 333
Timing equipment
• Primary Reference Clocks (PRC)
The primary reference clock may be of two different types. The first uses a Caesium oscillator and the
second a Rubidium oscillator disciplined by timing from GPS receivers. The use of GPS as timing is
becoming more and more common. Although this leaves the control over the PRC to the United States
Department of Defence, is has become so widespread in use that the advantages (low cost) is more
important than this factor. Due to the lower cost of the PRC today, it is also common to implement
several PRCs in the network. This improves the timing source redundancy and improves timing quality.
• Synchronisation Supply Units (SSU)

The purpose of the SSU (Synchronous Supply Unit) is to filter the received timing signal and to
distribute it to all the equipment to be synchronised. The SSU also commonly incorporates an
oscillator which meets the G.812 requirement for free running quality. As an option GPS receiver may
further improve the free running quality.
• Synchronous Equipment Timing Source (SETS)

This is also sometimes referred to as Synchronous Equipment Clock (SEC).
Synchronization modes of operation
Page 334
Synchronization modes of operation
• Free running mode:
An operating condition of a clock, the output signal of which is strongly influenced by the oscillating
element and not controlled by servo phase-locking techniques. In this mode the clock has never had a
network reference input, or the clock has lost external reference and has no access to stored data,
that could be acquired from a previously connected external reference. Free-run begins when the
clock output no longer reflects the influence of a connected external reference, or transition from it.
Free-run terminates when the clock output has achieved lock to an external reference.
• Holdover mode:
An operating condition of a clock which has lost its controlling reference input and is using stored data,
acquired while in locked operation, to control its output. The stored data are used to control phase and
frequency variations, allowing the locked condition to be reproduced within specifications. Holdover
begins when the clock output no longer reflects the influence of a connected external reference, or
transition from it. Holdover terminates when the output of the clock reverts to locked mode condition.
• Ideal operation:
This category of operation reflects the performance of a clock under conditions in which there are no
impairments on the input reference timing signal.
• Locked mode:
An operating condition of a slave clock in which the output signal is controlled by an external input
reference such that the clock's output signal has the same long-term average frequency as the input
reference, and the time error function between output and input is bounded. Locked mode is the
expected mode of operation of a slave clock.
• Stressed operation:
This category of operation reflects the actual performance of a clock considering the impact of real
operating (stressed) conditions. Stressed conditions include the effects of jitter, protection switching
activity and the loss of the input reference timing signal.
Synchronization example, tandem

PRC
SSU
G.811
G.812
"G.811" "G.811" "G.811" "G.812"
A "Don't Use" B "Don't Use" C "G.812" D
PRC
SSU
G.811
G.812
"SETS" "SETS" "G.812"
A "SETS" B "Don't Use" C "G.812" D
PRC
SSU
G.811
G.812
"Don't Use" "Don't Use" "G.812"
"G.812" "G.812" "G.812"

A B C D
Page 335
IP-20G Synchronization Settings
Meaning of Sync source and Clock source (Outgoing clock)
Radio link
Radio is Outgoing clock (clock source)

Radio is Sync source
Sync or Eth is Sync

Eth is Outgoing
source
clock (clock source)
Traffic Traffic
Page 336
Sync Source Configuration
1. Select Interface which will be used as sync. Source

2. Select Quality of clock for this source (automatic means use SSM)
3. Select Priority, Lowest number means highest priority
Outgoing Clock Configuration
1. Edit Interface
2. Select outgoing clock source:
1. Local Clock - The interface uses its internal clock as its synchronization source.
2. System Clock - Default value. The interface uses the system clock as its synchronization source.
3. Source Interface - Reserved for future use.
4. Time Loop - Reserved for future use.
3. Select Radio channel 0-84 – is used only for interoperability with IP10. IP10 needs E1 inside radio
frame for synchronization with IP20N. IP20G use radio frame itself for synchronization and doesn’t
need any E1 inside radio frame. It means that between two IP20G units it needs to be set this
parameter = 0.
4. SSM messages – enable / disable
Page 337
Thank you
27
Page 338
Security Features
December 2014
Version 1
Agenda
• Security Purpose
• Ceragon’ s security Architecture
• Defense in Management Communication Channels
• User Management
• User Profiles
• User Parameters
• Security Log
Page 339
Security Purpose
• Maintain system availability and performance
• Preventing unwanted or unauthorized access
• Preventing attacks
Ceragon’s Security Architecture

• Defenses in Management Communication Channels
• Defenses in User and System Authentication Procedures
• Secure Communication Channels
• Security Log
Page 340
Defenses in Management Communication Channels
• Attack types addressed
• Tempering with management flows
• Management traffic analysis
• Unauthorized software installation
• Attacks on protocols (by providing secrecy and integrity to messages)
• Traffic interfaces eavesdropping (by making it harder to change
configuration)
• DoS through flooding
Defenses in User and System Authentication

Procedures
• User Configuration and User Profiles, based on the Role-Based
Access Control (RBAC) model
• Remote Authentication – FUTURE Release
• RADIUS – FUTURE Release
Page 341
Users Management
Users Profiles
• Up to 50 profiles can be created
• User’s profile defines the permitted actions a user can perform
• Actions are separated to groups as follows:
• Security
• Management
• Radio
• TDM
• Ethernet
• Synchronization
• Parameters maybe associated with more than one group

• For each parameter, required access level is defined (Advanced or
Normal)
Page 342
Users Profiles – Web GUI
Example – Import/Export Security Settings
Page 343
User’s Management Parameters
• General Parameters
• Number of failed logins to block user (3)
• Blocking time period (5)
• Unused account period blocking (None)
• Session timeout (10)
• Password Parameters (for the whole system)

• Enforce password strength (No)
• Password change for first login (Yes)
• Password aging (0)
Security Log
Page 344
Security Log
• File stores any parameters changes which are part of security group
and time changes
• The log size is 50K records and cyclic
• File is encrypted and digitally signed
Thank You
Page 345
Page 346
Link Layer Discovery Protocol LLDP
December 2014
Version 1
Agenda
• Generally about LLDP
• Using LLDP in IP-20
• LLDP configuration in IP-20
Page 347
Generally about LLDP
• LLDP is a vendor-neutral layer 2 protocol that can be used by a station attached to a
specific LAN segment to advertise its identity and capabilities and to receive identity
and capacity information from physically adjacent layer 2 peers
• IP-20’s LLDP implementation is based on the IEEE 802.1AB – 2009 standard
• LLDP provides automatic network connectivity discovery by means of a port identity
information exchange between each port and its peer
• The port exchanges information with its peer and advertises this information to the
NMS managing the unit
Using LLDP in IP-20

Enabling LLDP on IP-20 units enables the NMS to:
• Automatically detect the IP-20 unit neighboring the managed IP-20 unit, and
determine the connectivity state between the two units
• Automatically detect a third-party switch or router neighboring the managed

IP-20 unit, and determine the connectivity state between the IP-20 unit and
the switch or router
Page 348
LLDP configuration in IP-20
• It will enable Transmitting and Receiving LLDP Notifications via selected Ethernet port
• The same configuration has to be done on the peer port
Thank You
Page 349
Page 350
IP-20G Frame Cut-Through
December 2014
Version 1
Agenda
• Frame Cut-Through - Basic Operation
• Configuration
Page 351
Frame Cut-Through - Basic Operation
• Frame Cut-Through is a unique and innovative feature that ensures low latency for
delay-sensitive services, such as CES, VoIP, and control protocols
• With Frame Cut-Through, high-priority frames are pushed ahead of lower priority
frames, even if transmission of the lower priority frames has already begun
Frame Cut-Through
• Once the high priority frame has been transmitted, transmission of the lower priority
frame is resumed with no capacity loss and no re-transmission required
• This feature provides services that are sensitive to delay and delay variation, such as
VoIP, with true transparency to lower priority services, by enabling the transmission of
a high priority, low-delay traffic stream

• This provides operators with:
• Immunity to head-of-line blocking effects – key for transporting high-priority,
delay-sensitive traffic.
• Reduced delay-variation and maximum-delay over the link:

• Improved QoE for VoIP and other streaming applications.
• Expedited delivery of critical control frames.
With Frame Cut‐Through
Without Frame Cut‐ Through
Max Delay Max Delay
Propagation Delay
Page 352
• When enabled, Frame Cut-Through applies to all high priority frames, i.e.,
all frames that are classified to a CoS queue with 4th (highest) priority
Frame Cut-Through - Configuration
Page 353
Thank You
Page 354
Cascading port
December 2014
Version 1
Agenda
• Hybrid TDM + Eth Concept
• Configuration of Cascading port
Page 355
Hybrid (TDM + Eth) services over IP-20N ‘cascading port’
• Cascading interfaces can be configured on ports 3 and 4 of an Ethernet LIC.

• When operating in cascading mode, these interfaces can handle hybrid
Ethernet and Native TDM traffic, enabling operators to create links among
multiple IP-20 units in a node for multi-directional applications based on hybrid
Ethernet and Native or Pseudowire TDM services
Configuration – 1st Auto negotiation - OFF
Cascading ports
Page 356
Configuration – 2nd Cascading Port Configuration
Cascading ports
Configuration – 3rd Configure service
Create service point for Cascading Interface –

Management or Pipe service point
Page 357
Configuration – 4th Configure TDM Trail
Configure required TDM Trail by using cascading port
Configuration – 5th Configure Ethernet Service
Configure Ethernet Service where Cascading port will be one Service point with
specific Interface type and C & S-VLAN encapsulation
Page 358
Thank You
Page 359
Page 360
Automatic State Propagation
IP-20G
December 2014
Version 1
Agenda
• Automatic State Propagation in General
• Configuration
• Exercise
Page 361
Automatic State Propagation in General
• Automatic State Propagation (ASP) enables propagation of radio failures back to the Ethernet
port
• You can also configure ASP to close the Ethernet port based on a radio failure at the remote
carrier
• ASP improves the recovery performance of resiliency protocols
Radio LOF
Eth Port
Disabled
Need to find
alternative path
Configuration
• Controlled – will be disabled upon initiation of ASP

• Monitored – ASP will act upon detecting a failure indication on this interface
• The following events in the Monitored Interface trigger ASP:

• Radio LOF
• Radio Excessive BER
Page 362
Exercise Site A Site B
• Make a radio link, enable Eth#3, clear all alarms

• Enable ASP for ETH#3
Exercise
Site B
Site A
Site A
• Mute radio on the Site B
• See result on Site A

• Site A received LOF, based on ASP configuration, ETH#3 is disabled from Operational status
Page 363
Thank You
Page 364
Link Aggregation (IEEE 802.3ad)
December 2014
Version 3
Agenda
• Link Aggregation Introduction
• LAG Advantages
• LAG mechanism
Page 365
Introduction to Link Aggregation
IEEE Definition:
• Link Aggregation allows one or more links to be aggregated

together to form a Link Aggregation Group, such that a MAC
Client can treat the Link Aggregation Group as if it were a
single link
• The Link Aggregation Group is consisting of N parallel

instances of full duplex point-to-point links operating at the N
same data rate
• Traffic sent to the ports in such a group is distributed through a

load balancing function
Link Aggregation Groups (LAG)

Link aggregation (LAG) enables users to group several physical interfaces into
a single logical interface bound to a single MAC address. This logical interface
is known as a LAG group. Traffic sent to the interfaces in a LAG group is
distributed by means of a load balancing function. IP-20N uses a distribution
function of up to Layer 4 in order to generate the most efficient distribution
among the LAG physical ports, taking into account:
• MAC DA and MAC SA

• IP DA and IP SA
• C-VLAN
• S-VLAN
• Layer 3 Protocol Field
• UDP/TCP Source Port and Destination Port
• MPLS Label
Page 366
LAG
• LAG can be used to provide redundancy for Ethernet interfaces, both on the
same card (line protection) and on separate cards (line protection and
equipment protection). LAGs can also be used to provide redundancy for radio
links.
• LAG can also be used to aggregate several interfaces in order to create a wider
(aggregate) Ethernet link. For example, LAG can be used to create a 4 Gbps
channel.
• Up to four LAG groups can be created.
• LAG groups can include interfaces with the following constraints:
• Only physical interfaces (including radio interfaces), not logical interfaces,
can belong to a LAG group.
• Interfaces can only be added to the LAG group if no services or service
points are attached to the interface.
• Any classification rules defined for the interface are overridden by the
classification rules defined for the LAG group.
• When removing an interface from a LAG group, the removed interface is
assigned the default interface values.
• IP-20N enables users to select the LAG members without limitations, such as
interface speed and interface type. Proper configuration of a LAG group is the
responsibility of the user.
Advantages
Page 367
Benefits of using Link Aggregation
1. Increased aggregate bandwidth
Link Aggregation allows the establishment of full duplex point-to-point links

that have a higher aggregate bandwidth than the individual links that form the
aggregation.
The capacity of the multiple links is combined into one logical link.
100 Mbps
2. Improved Resiliency
In case of a failed link, remaining links take over utilization of new available BW
Traffic via LAG is distributed according to user’s policy – improved reliability
Page 368
3. Reduced Complexity & Administration
When multiple ports are allocated between two ETH switches, broadcast storms are
created due to physical loops. STP is required to eliminate loops by blocking the redundant
port.
When multiple ports are allocated between 2 Routers, Routing Protocols are required to
control traffic paths.
With LA – STP or routing protocols are not needed, therefore, less processing is involved.
STP requires blocking and

path cost calculations
4. Reduced Cost
Instead of utilizing an expensive GbE port(s) to transport 200Mbps –
>> we trunk N x FE ports
Page 369
5. Improved Network Efficiency / Security
For sites with limited IP address space that nevertheless require large amounts of
bandwidth, you need only one IP address for a large aggregation of interfaces.
For sites that need to hide the existence of internal interfaces, the IP address of
the aggregation hides its interfaces from external applications.
(These examples refer to using L2 topologies as well)
Multiple
Interfaces
Single
Interface
Customer Public
Network Network
LAG
Page 370
Thank You
Page 371
Page 372
Course Evaluation Form
Dear Customer!
Thank you for taking the time to complete the following course evaluation form. Your
commentary and feedbacks are of great importance to us as we analysis and investigate each
course and report. The information you provide will be used to help us improve the content of
the course and monitor the quality of our training program.
Thank You,
Oren Gerstner,
Training Director
Course details
Location
Course Name / ID
Start Date (d/m/year) End Date (d/m/year)
Instructor Name
Company / Customer
Please rate your satisfaction with the course from 1 to 5 (1 = poor and 5 = excellent):
Did the course meet your expectations? 1 2 3 4 5
Was the course well organized? 1 2 3 4 5
Training facility & Environment 1 2 3 4 5

Was the difficulty of the course in line
1 2 3 4 5
with your expectations?
The instructor was well prepared 1 2 3 4 5

Instructor’s level of knowledge 1 2 3 4 5
Instructor’s presentation skills 1 2 3 4 5
Instructor’s willingness to help 1 2 3 4 5
Audience was treated respectfully 1 2 3 4 5
Language was clear and understood 1 2 3 4 5
Course book 1 2 3 4 5
Level of practical exercises (when relevant) 1 2 3 4 5

Setup and lab functionality (when relevant) 1 2 3 4 5
Usefulness Level of practical exercises (when relevant) 1 2 3 4 5
Overall satisfaction from the training session 1 2 3 4 5
Your comments:
Course Evaluation Form Page 1 of 1

Page 373

Handbook - FibeAir IP-20G Advanced Training Course T7.9 Ver1 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Handbook - FibeAir IP-20G Advanced Training Course T7.9 Ver1 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Ceragon Course Handbook

FibeAir IP-20G Advanced Training Course

Visit our Customer Training Portal at training.ceragon.com or contact us at training@ceragon.com

Trainee Name: _________________

• Parameters affecting propagations:

2 Proprietary and Confidential

3 Proprietary and Confidential

Radio Relay Principles

• A Radio Link requires two end stations

4 Proprietary and Confidential

Tx(f1)=11500 MHz Rx(f1)=11500 MHz

Rx(f1’)=11000 MHz Tx(f1’)=11000 MHz

High station means: Tx(f1) >Rx(f1’)

Low station means: Tx(f1’) < Rx(f1)

5 Proprietary and Confidential

Standard frequency plan patterns

Reduced risk for overshoot

Tx Tx in upper part of band

6 Proprietary and Confidential

7 Proprietary and Confidential

Radio Principal Block Diagram

8 Proprietary and Confidential

c where c is the propagation velocity of electromagnetic

• Microwave – refers to very short waves (millimeters) and typically

9 Proprietary and Confidential

10 Proprietary and Confidential

11 Proprietary and Confidential

Parameters Affecting Propagation

13 Proprietary and Confidential

Parameters Affecting Propagation – Dispersion

• Low frequencies have longer wavelength and refract less

14 Proprietary and Confidential

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

16 Proprietary and Confidential

17 Proprietary and Confidential

Parameters Affecting Propagation – Duct

18 Proprietary and Confidential

Large rain drops become

19 Proprietary and Confidential

Parameters Affecting Propagation – Rain Fading

 V better than H (more immune to rain fading)

20 Proprietary and Confidential

Heavier rain >> Heavier Atten.

Higher FQ >> Higher Attenuation

21 Proprietary and Confidential

Parameters Affecting Propagation – Fresnel Zone

22 Proprietary and Confidential

23 Proprietary and Confidential

Example: First condition

24 Proprietary and Confidential

25 Proprietary and Confidential

RSSI Curve for RFU-C

-30dBm -60dbm -90dBm

26 Proprietary and Confidential

• Standard performance antennas (SP,LP)

27 Proprietary and Confidential

28 Proprietary and Confidential

29 Proprietary and Confidential

30 Proprietary and Confidential

• Performance requirements generally higher than Availability.

31 Proprietary and Confidential

AM - Amplitude modulation ASK – Amplitude Shift Keying

33 Proprietary and Confidential