04 Ft48994en04gla0 Conf & Prot

Configurations and Protections
Contents
1
FlexiPacket MultiRadio System (FPMR) Configurations in Full Packet
Mode
1.1
System configurations in Full Packet Mode
2
FlexiPacket MultiRadio: Some installation examples
3
FlexiPacket FirstMile 200 Protection Methods
3.1
CES linear Protection (2.0EP1)
3.2
G.8031 Ethernet Protection Switching (FM200 R2.5)
3.3
Link Aggregation Group (LAG)
3.4
RSTP/MSTP
4
FlexiPacket HUB 800 Protection Methods
4.1
4.2
G.8031 Ethernet Protection Switching (2.0EP1)
4.3
Link Aggregation Grouping
4.4
RSTP/MSTP
4.5
STM-1 Multiplex Section Protection
FT48994EN04GLA0
2012 Nokia Siemens Networks
1
3
4
29
41
42
43
44
45
47
48
49
51
52
53
FT48994EN04GLA0
FlexiPacket MultiRadio System (FPMR)

Configurations in Full Packet Mode
FT48994EN04GLA0
1.1
System configurations in Full Packet Mode
FlexiPacket MultiRadio Software Release 2.5 is available with the configurations

listed in Fig. 1.
Nokia Siemens Networks
Fig. 1 System Configurations in software release 2.5
1.1.1
1+ 0 Configuration
FlexiPacket MultiRadio in 1+0 Configuration is reported in Fig. 25 showing the

installation with Integrated Antenna and in Fig. 26 showing the independent antenna
configuration.
WARNING
Integrated mounting (single or dual polarized) is possible up to an antenna
diameter =< 180 cm. For bigger antennas diameter it's necessary to use the
separated mounting.
FT48994EN04GLA0
1.1.2
1+0 Ring
The 1+0 Ring System Type is a 1+0 configuration with the facility to protect the
synchronization in the ring.
This system type must be used to implement the Ring Protection: two FlexiPacket
MultiRadios, interconnected through the ODU-ODU cable, configured as 1+0 Ring,
are connected to the Indoor Device, as shown in Fig. 2.
In this configuration the ring is made up of all FlexiPacket MultiRadios (the ring does
not include any IDU).
The synchronization is managed by the FlexiPacket MultiRadios.
The ODU-ODU cable carries the synchronization only.
Fig. 2 1+0 Ring Configuration
FT48994EN04GLA0
1.1.3
1+1 Hot Standby with Two Cables
In order to provide resilience against hardware failures, FlexiPacket MultiRadio

supports a 1+1 Hot Stand-by protection scheme with two cables (Fig. 3).
In the 1+1 Hot Standby system, the ODUs use the same RF channel.
The HotStandby protection can be supported using 2 different mechanisms:
CCM based (continuity check messages): It is based on customized L2 OAM

protocol according to 802.3ag standard involving the IDU and the ODUs. This
protocol is implemented in all IDU that are part of FlexiPacket Microwave solution.
The exchange of particular frames between IDU and ODUs univocally identifies
any single fault making ODU switching and making IDU redirecting data traffic
from one ODU to the other one.
Protection assure less then 50ms switching time in worst case. The duplication
capability is available on the HUB NNI ports only, so the IDU ports connected to each
ODU of the protection scheme shall be configured as NNI.
In addition, the two ports shall be full duplex and with the same speed. When the
working radio fails, IDU switches the traffic on the standby ODU which is concurrently
activated.
FT48994EN04GLA0
ODU master
f1
In normal conditions, only the master

ODU transmits; both RF receivers are
receiving
ODU slave
Link Protection Group (LPG)

HUB
A-Series/ FM200/ HUB800

ODU master
f1
In case Master ODU fails, the Slave

ODU becomes master, and the signal is
restored through the second IDU-ODU
cable. Switching time is ~50ms.
ODU slave
HUB
f1
Fig. 3 1+1 Hot Standby
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
FT48994EN04GLA0
. Nokia
. .Siemens
. .Networks
. .
2012
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1.1.3.1
CCM Mechanism: How it works
The working FlexiPacket MultiRadio periodically sends Continuity Check messages

to both the FPHub and the Stand-By FlexiPacket Radio.
The FPHub forwards the data traffic towards the working FlexiPacket MultiRadio until
it periodically receives these Continuity Check messages.
If Continuity Check messages from working FlexiPacket MultiRadio are not received
anymore, the FPHub flushes its own L2 tables and enables forwarding towards the
other port.
The Stand-by FlexiPacket MultiRadio remains switched OFF (both in Tx and Rx) until
it periodically receives Continuity check messages from the working FlexiPacket
MultiRadio. If Continuity Check messages are not received for 3 Times by the Standby FlexiPacket Radio, it will become working for both the Tx and the Rx chain.
ODU 1
CPU
Keep
alive
IDU
Port Odd
CPU
switch
Working
switch
Keep
alive E-CCM
Port Even
E-CCM
ODU 2
P-CCM
switch
Standby
CPU
Fig. 4 ECC Signals
FT48994EN04GLA0
1.1.4
1+1 Hot Standby with Single cable
In the single cable system type the protection ODU is connected via Ethernet
interface to the IDU or to a generic Indoor device.
The two Outdoor Units are connected via ODU-ODU cable.
In normal operation the protection ODU has the Transmitter turned off.
The Main ODU is active in both TX/RX directions.
When a failure occurs on the Main ODU, the Protection ODU removes the squelch
and starts to protect the radio link This system type does not protect in case of cable
or Protection ODU failure.
The protection of the system is revertive, that is, when the faulty unit is replaced,
rebecomes Main.
WARNING
Please note that Main ODU needs to be powered separately.
Main
f0
Main
ODU-ODU Cable
Protection
Protection
f0
traffic
Fig. 5 1+1 Hot Standby - single cable
FT48994EN04GLA0
1.1.5
1+1 frequency diversity with two cables
Frequency Diversity protection is implemented transmitting the same traffic flow over
two frequency channels (Fig. 6).
The two ODU (in both sides of the link) are directly connected by means of the ODUODU cable.
The Master ODU receiver selects the received signals on the basis of their estimated
noise level.
The master ODU is defined as the ODU that receives the traffic from IDU in normal
working conditions; secondary ODU receives the traffic from master ODU.
In normal working operation the traffic from the IDU is sent to the main ODU which
then reroutes it to the second ODU via direct ODU-ODU connection.
ACM is synchronized between the two channels.
ODU master
f1
f1
ODU-ODU cable
f2
f2
ODU slave

HUB
The two Outdoor Units are connected by means of the ODUODU cable
In normal conditions, each ODU is connected to the IDU via
its own IDU-ODU cable. Only IDU-ODU cable connected to
the Master ODU transports the payload to be transmitted
over the radio and to be provided in RX direction to the IDU.
The same payload is transmitted over two different
frequencies
The Rx signal is selected inside the Master ODU and
directed to the IDU
Fig. 6 1+1 Frequency Diversity (1)
10
FT48994EN04GLA0
In case of radio fading, the ODU group assures the hitless restoration of the traffic.
Payload is not affected.
In case Master ODU fails, the Slave ODU becomes master, and the signal is restored
through the second IDU-ODU cable
Radio fading
ODU master
f1
ODU-ODU cable
f2
ODU slave
In case of radio fading, the ODU group

assures the hitless restoration of the traffic.
HUB

ODU master
ODU fail
IDU-ODU cable
f1
f2
In case Master ODU fails, the Slave ODU

becomes master, and the signal is restored
ODU slave
HUB
Fig. 7 1+1 Frequency Diversity (2)
WARNING
1+1 Frequency Diversity is available with one or two antennas
FT48994EN04GLA0
11
1.1.6
FPMR 2+0 Load Sharing with two cables
In 2+0 load sharing (Radio link aggregation) configuration, the traffic is transmitted
over two radio channels (Fig. 8).
The radio link aggregation function ensures that the traffic coming from the IDU port
is shared among the two radio channels.
WARNING
2+0 Load sharing is the possibility to increase the transported capacity of a
radio link splitting the data traffic in two channels with 2+0 configuration. The
two channels have two different frequencies f1 and f2 (Fig. 8).
ACM works independently among the two radio links.
High priority traffic is preserved; low priority traffic is discarded when the RF pipes
reduce.
The main ODU is defined as the ODU that receives the traffic from IDU in normal
working conditions; secondary ODU receives the traffic from master ODU.
In normal working operation the traffic from the IDU is sent to the master ODU which
then splits it and reroutes part of it to the second ODU via direct ODU-ODU
connection
ODU master
f1
ODU-ODU cable
f1
f2
f2
ODU slave

HUB
Master ODU splits the traffic among the two RF

channels, taking into account also different ACM levels
The traffic of the two RF pipes is carried over one
cable (IDU-ODU), in normal operations.
In normal operation traffic comes from the master
ODU
Fig. 8 2+0 Load Sharing (1)
12
FT48994EN04GLA0
WARNING
The two ODUs configured in the Protection Group must be interconnected by
means of the ODU-ODU interconnection cable.
The master ODU algorithm splits the traffic among the two RF Channels considering
the size of each pipe. The master ODU "scheduler and congestion avoidance
mechanism" ensures that the high priority traffic is kept when the two pipes reduce
their sizes due to ACM intervention.
In case of master ODU HW failure, the IDU reroute the traffic over the secondary
ODU.
In case of Secondary ODU failure, the main ODU interrupts the traffic flow to and
from the secondary ODU.
The ODU QoS algorithm preserves 50% of the traffic (high priority traffic).
ODU fail
ODU master
IDU-ODU cable
f1
f2
In case Master ODU fails, the Slave ODU

becomes master, and the signal is restored
ODU slave
HUB
Fig. 9 2+0 Load Sharing (2)
FT48994EN04GLA0
13
1.1.7
FPMR 2+0 XPIC Load Sharing with two cables
The 2+0 load sharing (radio link aggregation ) configuration can be also implemented
using XPIC (Fig. 10).
In this case, the master ODU performs also XPIC operations to reduce the crosspolar interference.
WARNING
2+0 XPIC Load sharing is the possibility to increase the transported capacity of
a radio link splitting the data traffic in two channels with 2+0 configuration. The
frequency of the two channels is the same but two different polarizations
(Horizontal and Vertical) are used.
f0H
f0v
Master ODU splits
the traffic among
the two RF
channels, taking
into account also
different ACM levels
XPIC is performed in
the main ODU,
Phase shift
information among
the RF channels are
exchanged through
ODU-ODU
connection
f0H
f0V
LPG
HUB
The traffic of the

two RF pipes is
carried over one
cable, in normal
operations
LPG
HUB
Fig. 10 FPMR 2+0 XPIC Load Sharing
WARNING
XPIC is always implemented with one antenna dual polarization.
WARNING
The two ODUs configured in the Protection Group must be interconnected by
means of the ODU-ODU interconnection cable
14
FT48994EN04GLA0
1.1.8
FPMR 2+0 XPIC Load Sharing with Single Cable
The system is similar to the 2+0 XPIC, with the difference that only one cable is
connected to the IDU.
As in the others 2+0 systems, the ODUs are connected via ODU-ODU cable.
In case of HW failure, only the failure of the ODU that is not connected to the IDU is
protected.
Half of the capacity is saved on the remaining polarization (H/V), according to QoS
criteria.
WARNING
Please note that Main ODU needs to be powered separately.
WARNING
This system type provides load sharing but does not protect in case of cable or
protection ODU failure.
Main
f0H
*
ODU-ODU Cable
f0v
Protection
f0v
traffic
Fig. 11 2+0 XPIC (single cable)
FT48994EN04GLA0
15
1.1.9
Further considerations about 2+0 Load Balancing
Load Balancing feature is available with two system types:

2+0 Frequency Diversity (2+0 FD)
Normal conditions:
Total Net Throughput = (Net Throughput link 1) + (Net Throughput link
2)
Protection:
Hardware Failure
Fading
2+0 Cross-Polarization (2+0 XPIC)
Normal conditions:
Total Net Throughput = (Net Throughput link 1) + (Net Throughput link
2)
Frequency Optimization
Protection:
Hardware Failure
Polarized interference
The Load Balancing feature makes the FlexiPacket MultiRadio unique in the market
for the following characteristics:
1) Independency of the Indoor Units (IDUs)
No hardware/software upgrade in IDUs for supporting the feature
The processing associated to the feature is completely handled by the FPMR

in an automatic manner (single pipe between the IDUs)
The IDU only implements a single LPG
2) Independency of the single radio link from each other
The two radio links are completely independent in terms of modulation.
3) Efficient proprietary protocol
16
The load balancing of traffic among the two radio links is managed by a
proprietary protocol, which allows for a complete usage of link net throughput
(no inefficiency due to overhead as for LACP in LAG, no hashing mechanisms
involved)
FT48994EN04GLA0
According to the type of license (which fixes the maximum capacity to be transmitted
by the FlexiPacket MultiRadio) and the available capacity over air (depending on the
channel bandwidth and the modulation scheme) two different traffic protection modes
are available:
2+0 maximum throughput
In normal conditions each ODU transmits half of the payload of a 2+0 link
In case of failure, the second ODU is configured (bandwidth) to be able in to

preserve the total payload of the 2+0 link
2+0 minimum bandwidth
In normal conditions each ODU transmits half of the payload of the 2+0 link
In case of failure of one ODU, the second ODU is configured (bandwidth) to

preserve half of the total payload of the 2+0 link
1.1.9.1
2+0 maximum throughput examples
Example 1
Fig. 12 Example1
Both ODUs have a 200 Mps license and are set to ACM between min 16 QAM and
max 256 QAM. In normal condition each ODU transmits 100 Mbs with 256 QAM (200
Mps in total).
In case of failure of one ODU, the other ODU, working again with the 256 QAM,
increases the total amount of throughput up to 200 Mbps. The link is not affected.
FT48994EN04GLA0
17
Example 2
Fig. 13 Example2
In case of ACM switching on Secondary ODU, Main ODU takes the part of the traffic
that is not transmitted on the Slave ODU.
Total amount of transmitted traffic is not affected and the behavior is hitless.
18
FT48994EN04GLA0
1.1.9.2
2+0 minimum bandwidth examples
Example 1
Fig. 142+0 minimum bandwidth Example1

In normal conditions both ODU transmit at 256 QAM.

In case of failure, half of the payload is saved on one ODU. The ODU QoS algorithm
preserves the high priority traffic.
FT48994EN04GLA0
19
Example 2
Fig. 15 2+0 minimum bandwidth Example2

In case of ACM switching on Secondary ODU, Main ODU and Secondary ODU save
the payload according to QoS.
Total amount of transmitted traffic is reduced (depending on minimum modulation
level set for ACM) and the behavior is hitless for high priority traffic.
1.1.9.3
Comparison with the HSBY system type
Both 2+0 modes, thanks to the possibility to directly integrate the two ODUs on one
Dual Pol. Antenna, does not introduce HSBY (balanced/unbalanced) losses, and
provide protection to fading (with load sharing) and hw failures.
20
FT48994EN04GLA0
1.1.10
1+1 Space diversity with two cables
Space Diversity protection is implemented receiving the same traffic flow over two
different antennas (Fig. 16).
The Main ODU receiver selects the received signals on the basis of their estimated
noise level.
The Main ODU (Master) is defined as the ODU that receives the traffic from IDU in
normal working conditions.
Secondary ODU (Slave) receives the traffic from primary ODU.
In normal working operation the traffic from the IDU is sent to the master ODU which
transmits it over air.
On receiver side the secondary ODU transmits the traffic to the main ODU via direct
ODU-ODU connection.
ODU master
f1
f1
ODU-ODU cable
ODU slave
f1

HUB
The two Outdoor Units are connected via the ODU-ODU

cable
In normal conditions, only the master ODU transmits.
In RX direction both receivers are active
The Rx signal is selected inside the Master ODU and
directed to the IDU
Fig. 16 Space Diversity (1)
FT48994EN04GLA0
21
In case of radio fading, the ODU group assures the hitless restoration of the traffic.
In case Master ODU fails, the Slave ODU becomes master, transmitting on the same
frequency, and the signal is restored through the second IDU-ODU cable
Radio fading
ODU master
f1
ODU-ODU cable
ODU slave
f1
In case of radio fading, the ODU group

assures the hitless restoration of the
traffic. Payload is not affected.
HUB
ODU fail
ODU master
ODU-ODU cable
f1
ODU slave
In case Master ODU fails, the Slave

ODU becomes master, and the signal
is restored through the second IDUODU cable.
HUB
Fig. 17 Space Diversity (2)
22
FT48994EN04GLA0
1+1 Space Diversity Summary is reported in Fig. 18
The 1+1 Space Diversity operates on two radio links and it is characterized
by:
Single transmission frequency fo
Single Active Transmitter for each direction
Two Active Receivers for each direction
Two antennas for each site
Acting Master
TX: ON
RX: ON
Main ray
Main
Acting Slave
TX: OFF
RX ON
Acting Master
TX: ON
RX: ON
ra y
h ra
ipat
Mult
y
Acting Slave
TX: OFF
RX: ON
Interference
Fig. 18 1+1 Space Diversity Summary
FT48994EN04GLA0
23
1.1.11
2+2 XPIC on one Dual Pol Antenna
This system type is 2+0 XPIC with full HSBy protection by a second couple of ODUs
in stand-by (see Fig. 19).
If a fault happens, the traffic is completely switched to the stand-by couple of ODUs.
This means that at every time either the Main or the Protection pair of ODUs is
active.
V main
H
V
H
XPIC conn.
V prot
H main
V
Dual pol.
Working
group
Stand
by
group
Balanced coupler
antenna
Waveguide
XPIC conn.
LPG
H prot
Fig. 19 2+2 XPIC (1)
WARNING
2x Power cables for Hmain and H prot. ODUs are necessary
24
FT48994EN04GLA0
1.1.12
2x2 XPIC on two Dual Pol Antennas (integrated)
This system type is 2+0 XPIC with full HSBy protection by a second couple of ODUs
in stand-by using two Dual Pol Antennas (see Fig. 20).
V main
H
V
Working
group
XPIC conn.
H
H main
V prot
Standby
group
XPIC conn.
LPG
H prot
Fig. 20 2+2 XPIC (2)
WARNING
2x Power cables for Hmain and H prot. ODUs are necessary
FT48994EN04GLA0
25
1.1.13
Compatibilities with Indoor Units
FPMR compatibilities with Indoor Units are listed in Fig. 21.
Fig. 21 Compatibilities with Indoor Units
26
FT48994EN04GLA0
1.1.14
System Integrated inside FlexiBTS: 1+1 HSBY standalone
This protection mode is applicable to BTS but in general can be used with generic
L2 devices.
The BTS (or L2 device, or IDU) is supposed to be basically unaware of the
presence of a protected radio link (1+1 HSBY).
The decision about which ODU is active at a given moment is taken
autonomously by the ODUs according to the configurations (Main/Protection and
Revertive/Unrevertive) and the status of the ODU.
The mechanism is based on CCM messages exchanges between the two ODUs.
The ODUs are connected via ODU-ODU cable.
In case of HW fault the protection ODU becomes main and starts
transmitting/receiving. The correspondant cable carries the traffic from IDU/BTS to
ODU.
3G BTS
ETH
ETH
Giga
Ethernet
traffic
Fig. 22 HotStandby Stand-alone
FT48994EN04GLA0
27
1.1.15
System Integrated inside FlexiBTS: 2+0 XPIC
This protection mode is based on the same principle described for 1+1 HSBY
The BTS (or L2 device, or IDU) is supposed to be basically unaware of the presence
of a protected radio link (2+0 XPIC w/ load sharing).
Both the ODUs are active at the same time. Only one cable carries the payload to the
main ODU. The second cable is for protection purposes.
The mechanism is based on CCM messages exchanges between the two ODUs.
The ODUs are connected via ODU-ODU cable.
f0H
f0v
3G BTS
ETH
ETH
Giga
Ethernet
traffic
Fig. 23 2+0 XPIC with FlexiBTS

28
FT48994EN04GLA0
FlexiPacket MultiRadio: Some installation

examples
Some installation schemes are reported in the following figures as examples.
WARNING
For complete information about installation, please, refer yourself to the
FlexiPacket MultiRadio Field Installation and Commissioning training
documentation.
FlexiPacket Radio is available with 2 different antenna interfaces:
XD mechanical compatibility
FH mechanical compatibility
For the compatibility with the FlexiHopper antennas a special adapter (to be installed
on the FlexiPacket MultiRadio) is available (Fig. 24).
Fig. 24 Adapter for FlexiHopper antenna
FlexiPacket antennas are sized: 20, 30, 60, 80, 100, 120 and 180cm.
WARNING
The following schemes are referred to the XD mechanical compatibility
WARNING
Integrated Antenna mounting (single or dual polarized) is possible up to an
antenna diameter =< 180 cm. For bigger antennas diameter it's necessary to
use the separated mounting.
FT48994EN04GLA0
29
Fig. 25 1+0 system with integrated antenna
30
FT48994EN04GLA0
Fig. 26 1+0 system with independent antenna
FT48994EN04GLA0
31
Fig. 27 Hot Stand-by/1+1 FD (co-polar) system with integrated antenna
32
FT48994EN04GLA0
Fig. 28 1+1 Hot Stand-by/1+1 FD (co-polar) system with independent antenna
FT48994EN04GLA0
33
New back-to-back frames are available from 6GHz to 42GHz in both variants
(balanced/unbalanced)
Fig. 29 New back-to-back frames

34
FT48994EN04GLA0
Fig. 30 1+1 FD (cross-polar) system with independent antenna
FT48994EN04GLA0
35
Fig. 31 1+1 FD SD system with integrated antenna
36
FT48994EN04GLA0
Fig. 32 2+0 XPIC/2+0 FD (cross-polar) system with independent antenna (Full Packet Mode)
FT48994EN04GLA0
37
Fig. 33 2+2 XPIC configuration (with 1 Antenna with coupler)
38
FT48994EN04GLA0
Siemens Networks
Fig. 34 2+2 XPIC configuration (with 2 Antennas)
FT48994EN04GLA0
39
40
FT48994EN04GLA0
FlexiPacket FirstMile 200 Protection

Methods
FT48994EN04GLA0
41
3.1
This protection protects Circuit Emulation (CES) services.

Its a E2E protection mechanism.
Its typically used in MW rings but it can be used in any topology.
Principle: a protected service has a working and a protection path
Fault detection based on CES monitoring of traffic.
CES is constant rate service loss of traffic frames provides an indication of loss of
connectivity.
Switching time <50ms
The Uni-direction failure protection will be added in the future release.
Operator can issue commands to make CES traffic switching to working path or
Protection path.
FM200
R2.0EP1
E1
2G
Fig. 35 FM200 CES Linear Protection
42
FT48994EN04GLA0
3.2
G.8031 Ethernet Protection Switching (FM200

R2.5)
This protection scheme is according to ITU-T G.8031.

It is a E2E protection mechanism.
Principle: a protected service has a working and a protection path.
The End points exchange CCM to monitor the status of the path.
Switching time depends on number of services.
FPH800: Sub100 ms with 8 services - up to 80 protected services with sub400ms
protection.
Typical used in rings but it can be used in any topology.
Eth
Fig. 36 FM200 G8031 Ethernet Protection Switching
WARNING
FM200 R2.5 is not currently available
FT48994EN04GLA0
43
3.3
Link Aggregation Group (LAG)
Link aggregation grouping allows multiple links to be aggregated together to form a

Link Aggregation Group (LAG).
A MAC client treats the LAG as if it is a single logical link. For bridge functionality, the
LAG is considered as a single bridge port. LAG consists of N parallel full duplex
point-to-point links.
LAG provides the following main functionality:
Increased bandwidth: the capacity of multiple links is combined into one logical
link.
Linearly incremental bandwidth
Increased availability: a failure in one of the links will result in the traffic being
redistributed among the other active member links.
Load sharing
Rapid configuration and reconfiguration
WARNING
Only six Ethernet ports on the front panel can be configured for LAG
44
FT48994EN04GLA0
3.4
RSTP/MSTP
Rapid/Multiple Spanning Tree protocol is supported in FM200 to provide a loop-free

redundant network topology, preventing the network from broadcast storm.
FM200 supports up to 8 MSTIs.
FT48994EN04GLA0
45
46
FT48994EN04GLA0
FlexiPacket HUB 800 Protection Methods
FT48994EN04GLA0
47
4.1
This protection protects Circuit Emulation (CES) services.

It is typically used in MW rings but it can be used in any topology.
Principle: a protected service has a working and a protection path
Fault detection based on CES monitoring of traffic.
CES is constant rate service loss of traffic frames provides an indication of loss of
connectivity.
Switching time <50ms
FPH 800
R2.0EP1
E1
2G
Fig. 37 HUB800 CES Linear Protection
48
FT48994EN04GLA0
4.2
G.8031 Ethernet Protection Switching (2.0EP1)
This protection scheme is according to ITU-T G.8031.

Principle: a protected service has a working and a protection path.
The End points exchange CCM to monitor the status of the path.
Following features are supported in FPH800 R2.0 EP1 linear protection:
FPH800 R2.0 EP1 supports 80 protected services which can ensure less than
400ms switch-over time upon a failure on the path of these services. For only
1 service failed, the protection time is less than 50ms; For all services failed at
the same time, the protection time is less than 400ms
Both revertive switch mode and non-revertive mode are supported. In revertive
mode, when the working path is repaired, traffic will switch back to working
path after WTR (Wait to Restore) time expires. In non-revertive mode, when
the working path is repaired, traffic will still stay at protection path. Revertive
mode is the default mode.
Following end to end commands are supported

Lockout of protection - This command prevents a working signal from
being selected from the protection transport entity. This effectively
disables the protection group.
Force switch normal traffic signal-to-protection - Forces normal traffic
signal to be selected from the protection transport entity when there is
no failure on protection path.
Manual switch normal traffic signal-to-protection - In the absence of a
failure of a working and a protection transport entity, forces normal
traffic signal to be selected from the protection transport entity.
Clear - Clears the active near end Lockout of Protection, Forced Switch,
Manual Switch, and WTR state.
Hold off timer.

-
Range of the hold off timer is 0 to 10 seconds in steps of 100 ms. The default
value for hold off time is 0.
FT48994EN04GLA0
49
Eth
Fig. 38 HUB800 G.8031 Ethernet Protection Switching
works
50
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
FT48994EN04GLA0
. . . . . . .
. . . . . . .
. . . . . . .
4.3
Link Aggregation Grouping
Link aggregation grouping allows multiple links to be aggregated together to form a

Link Aggregation Group (LAG).
A MAC client treats the LAG as if it is a single logical link. For bridge functionality, the
LAG is considered as a single bridge port. LAG consists of N parallel full duplex
point-to-point links.
LAG provides the following main functionality:
Increased bandwidth: the capacity of multiple links is combined into one logical
link.
Linearly incremental bandwidth
Increased availability : a failure in one of the links will result in the traffic being
redistributed among the other active member links.
Load sharing
Rapid configuration and reconfiguration
WARNING
Only six Ethernet ports on the front panel can be configured for LAG
FT48994EN04GLA0
51
4.4
RSTP/MSTP
Rapid/Multiple Spanning Tree protocol is supported in FPH800 to provide a loop-free

redundant network topology, preventing the network from broadcast storm.
FPH800 supports up to 16 MSTIs.
52
FT48994EN04GLA0
4.5
STM-1 Multiplex Section Protection
MSP is supported to protect STM-1 ports from link failures, e.g., fiber broken.
In release 2.0, for the two STM-1 ports available on mainboard, 1 + 1 unidirectional
MSP is supported, and it is fixed to non-revertive mode.
The traffic behavior of MSP is "source side bridges, sink side selects" (see Fig. 43).
The quality criteria to trigger sink end section includes Signal Failure (SF) and Signal
Degrade (SD).
Fig. 39 FPH 800 STM-1 MSP protection
FT48994EN04GLA0
53
54
FT48994EN04GLA0

04 Ft48994en04gla0 Conf &amp; Prot

Hochgeladen von

Dokumentinformationen

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

04 Ft48994en04gla0 Conf &amp; Prot

Hochgeladen von

Copyright:

Verfügbare Formate

Configurations and Protections

Configurations and Protections

Configurations and Protections

Configurations and Protections

FlexiPacket MultiRadio System (FPMR)

Configurations and Protections

System configurations in Full Packet Mode

FlexiPacket MultiRadio Software Release 2.5 is available with the configurations

Nokia Siemens Networks

Fig. 1 System Configurations in software release 2.5

FlexiPacket MultiRadio in 1+0 Configuration is reported in Fig. 25 showing the

Configurations and Protections

Fig. 2 1+0 Ring Configuration

Nokia Siemens Networks

Configurations and Protections

1+1 Hot Standby with Two Cables

In order to provide resilience against hardware failures, FlexiPacket MultiRadio

CCM based (continuity check messages): It is based on customized L2 OAM

Configurations and Protections

In normal conditions, only the master

Link Protection Group (LPG)

A-Series/ FM200/ HUB800

In case Master ODU fails, the Slave

A-Series/ FM200/ HUB800

Fig. 3 1+1 Hot Standby

Configurations and Protections

CCM Mechanism: How it works

The working FlexiPacket MultiRadio periodically sends Continuity Check messages

Fig. 4 ECC Signals

Configurations and Protections

1+1 Hot Standby with Single cable

Fig. 5 1+1 Hot Standby - single cable

Nokia Siemens Networks

Configurations and Protections

1+1 frequency diversity with two cables

Link Protection Group (LPG)

A-Series/ FM200/ HUB800

Fig. 6 1+1 Frequency Diversity (1)

Configurations and Protections

In case of radio fading, the ODU group

A-Series/ FM200/ HUB800

In case Master ODU fails, the Slave ODU

A-Series/ FM200/ HUB800

Fig. 7 1+1 Frequency Diversity (2)

Configurations and Protections

FPMR 2+0 Load Sharing with two cables

Link Protection Group (LPG)

A-Series/ FM200/ HUB800

Master ODU splits the traffic among the two RF

Fig. 8 2+0 Load Sharing (1)

Configurations and Protections

In case Master ODU fails, the Slave ODU

A-Series/ FM200/ HUB800

Fig. 9 2+0 Load Sharing (2)

Configurations and Protections

FPMR 2+0 XPIC Load Sharing with two cables

A-Series/ FM200/ HUB800

The traffic of the

A-Series/ FM200/ HUB800

Fig. 10 FPMR 2+0 XPIC Load Sharing

Configurations and Protections

FPMR 2+0 XPIC Load Sharing with Single Cable

Fig. 11 2+0 XPIC (single cable)

Nokia Siemens Networks

04 Ft48994en04gla0 Conf & Prot

04 Ft48994en04gla0 Conf & Prot