006. configuration & protection.pdf

39
Configurations and Protections FT48928EN03GLA0 © 2012 Nokia Siemens Networks 1 Content 1 FlexiPacket MultiRadio System (FPMR) Configurations in Full Packet Mode 3 1.1 System configurations in Full Packet Mode 3 2 FlexiPacket MultiRadio: Some installation examples 27 3 FlexiPacket FirstMile 200 Protection Methods 37 3.1 CES linear Protection (2.0EP1) 38 3.2 G.8031 Ethernet Protection Switching (FM200 R2.5) 39 3.3 Link Aggregation Group (LAG) 40 3.4 RSTP/MSTP 40 4 FlexiPacket HUB 800 Protection Methods 41 4.1 CES linear Protection (2.0EP1) 41 4.2 G.8031 Ethernet Protection Switching (2.0EP1) 42 4.3 Link Aggregation Grouping 44 4.4 RSTP/MSTP 44 4.5 STM-1 Multiplex Section Protection 45 Configurations and Protections

Upload: ismailttl

Post on 19-Dec-2015

47 views

Category:

Documents


6 download

TRANSCRIPT

Page 1: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 1

Content

1 FlexiPacket MultiRadio System (FPMR) Configurations in Full Packet Mode 3

1.1 System configurations in Full Packet Mode 3

2 FlexiPacket MultiRadio: Some installation examples 27

3 FlexiPacket FirstMile 200 Protection Methods 37

3.1 CES linear Protection (2.0EP1) 38

3.2 G.8031 Ethernet Protection Switching (FM200 R2.5) 39

3.3 Link Aggregation Group (LAG) 40

3.4 RSTP/MSTP 40

4 FlexiPacket HUB 800 Protection Methods 41

4.1 CES linear Protection (2.0EP1) 41

4.2 G.8031 Ethernet Protection Switching (2.0EP1) 42

4.3 Link Aggregation Grouping 44

4.4 RSTP/MSTP 44

4.5 STM-1 Multiplex Section Protection 45

Configurations and Protections

Page 2: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 3

1 FlexiPacket MultiRadio System (FPMR) Configurations in Full Packet Mode

1.1 System configurations in Full Packet Mode

FlexiPacket MultiRadio Software Release 2.4 is available with the configurations listed in Fig. 1.

© Nokia Siemens Networks

FPMR

R2.4

Fig. 1 System Configurations

Page 3: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 4

Note 1 - In order to provide resilience against hardware failures FlexiPacket MultiRadio supports two different behaviours according to the type of IDU which the FlexiPacket MultiRadio is connected to:

HW Protection mode 1 (CCM based): for interoperability with IDUs, which support the protection mechanism (Ax200 and FirstMile).

HW Protection mode 3 (Standalone): for interoperability with a generic L2 Bridge which supports the normal behavior specified in IEEE 802.1D (i.e. Learning, Forwarding, Filtering, and xSTP) and in 802.1Q (VLAN tagging).

Note 2 - The IDU is unaware of the presence of a protected radio link (1+1 HSBY) and the functioning of the system entirely relies upon MAC address bridging.

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 alarms (both HW failure and link loss alarms).

No explicit notification of the active link is sent to the IDU.

The IDU sends the traffic to the ODU according to the learning algorithm.

This mode of operation requires the presence of the ODU-ODU cable for the dialog between the 2 ODUs.

Note 3 - One ODU acts as Master and the other one as Slave.

All the traffic from the IDU is sent on the cable of the Master ODU, which is in charge to split the traffic over its radio channel and over the radio channel of the Slave ODU (through the ODU-ODU cable).

In case of failure of the Master ODU the Slave ODU becomes active and the traffic from IDU transits on the cable of the Slave.

1.1.1 1+ 0 Configuration

FlexiPacket MultiRadio in 1+0 Configuration is reported in Fig. 23 showing the installation with Integrated Antenna and in Fig. 24 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.

Page 4: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 5

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.

© Nokia Siemens Networks

Fig. 2 1+0 Ring Configuration

Page 5: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 6

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.

Page 6: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 7

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ODU master

ODU slave

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.

f1

•In normal conditions, only the master

ODU transmits; both RF receivers are

receiving

ODU master

ODU slave

f1

A-Series/ FM200/ HUB800

HUB

A-Series/ FM200/ HUB800

HUB

Link Protection Group (LPG)

Fig. 3 1+1 Hot Standby

Page 7: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 8

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 Stand-by FlexiPacket Radio, it will become working for both the Tx and the Rx chain.

IDU

ODU 1

CPU

switch

ODU 2

switch

CPU

switchCPU

Port Odd E-CCM

E-CCM

Port Even

P-CCM

Keep

alive

Keep

alive

Working

Standby

Fig. 4 ECC Signals

Page 8: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 9

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.

© Nokia Siemens Networks

Main

Protection

f0 Main

Protectionf0

traffic

ODU-ODU Cable

Fig. 5 1+1 Hot Standby - single cable

Page 9: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 10

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

f1 f2

ODU master

ODU slave

f1

f2

•The two Outdoor Units are connected by means of the ODU-

ODU 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

ODU-ODU cable

A-Series/ FM200/ HUB800

HUB

Link Protection Group (LPG)

Fig. 6 1+1 Frequency Diversity (1)

Page 10: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 11

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

ODU master

ODU slave

f1

f2•In case of radio fading, the ODU group

assures the hitless restoration of the traffic.

Payload is not affected.

ODU-ODU cable

Radio fading

ODU master

ODU slave

f1

f2IDU-ODU cable

ODU fail

•In case Master ODU fails, the Slave ODU

becomes master, and the signal is restored

through the second IDU-ODU cable

A-Series/ FM200/ HUB800

HUB

A-Series/ FM200/ HUB800

HUB

Fig. 7 1+1 Frequency Diversity (2)

WARNING 1+1 Frequency Diversity is available with one or two antennas

Page 11: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 12

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

f1 f2ODU master

ODU slave

f1

f2

•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

ODU-ODU cable

A-Series/ FM200/ HUB800

HUB

Link Protection Group (LPG)

Fig. 8 2+0 Load Sharing (1)

Page 12: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 13

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 master

ODU slave

f1

f2IDU-ODU cable

ODU fail

•In case Master ODU fails, the Slave ODU

becomes master, and the signal is restored

through the second IDU-ODU cable

A-Series/ FM200/ HUB800

HUB

Fig. 9 2+0 Load Sharing (2)

Page 13: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 14

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 cross-polar 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.

LPG

f0V

f0H

The traffic of the

two RF pipes is

carried over one

cable, in normal

operations

Master ODU splits

the traffic among

the two RF

channels, taking

into account also

different ACM levels

LPG

XPIC is performed in

the main ODU,

Phase shift

information among

the RF channels are

exchanged through

ODU-ODU

connection

f0H

f0v

A-Series/ FM200/ HUB800

HUB

A-Series/ FM200/ HUB800

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

Page 14: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 15

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.

© Nokia Siemens Networks

f0H

f0vf0v

traffic

Main

Protection

*ODU-ODU Cable

Fig. 11 2+0 XPIC (single cable)

Page 15: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 16

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

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

Page 16: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 17

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

© Nokia Siemens Networks

Fig. 12

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.

Page 17: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 18

Example 2

© Nokia Siemens Networks

Fig. 13

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 behaviour is hitless.

Page 18: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 19

1.1.9.2 2+0 “minimum bandwidth” examples

Example 1

© Nokia Siemens Networks

Fig. 14

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.

Page 19: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 20

Example 2

© Nokia Siemens Networks

Fig. 15

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.

Page 20: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 21

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

ODU slave

f1

f1

•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

ODU-ODU cable

f1

A-Series/ FM200/ HUB800

HUB

Link Protection Group (LPG)

Fig. 16 Space Diversity (1)

Page 21: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 22

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, transmitting on the same frequency, and the signal is restored through the second IDU-ODU cable

ODU master

ODU slave

f1

f1

ODU-ODU cable •In case of radio fading, the ODU group

assures the hitless restoration of the

traffic. Payload is not affected.

ODU master

ODU slave

f1ODU-ODU cable•In case Master ODU fails, the Slave

ODU becomes master, and the signal

is restored through the second IDU-

ODU cable.

Radio fading

ODU fail

A-Series/ FM200/ HUB800

HUB

A-Series/ FM200/ HUB800

HUB

Fig. 17 Space Diversity (2)

Page 22: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 23

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

Acting Slave

TX: OFF

RX ON

Acting Slave

TX: OFF

RX: ON

Acting Master

TX: ON

RX: ONMain ray

Main ray

Interference

Multipath ray

Fig. 18 1+1 Space Diversity Summary

Page 23: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 24

1.1.11 Mixed link compatibility

In the present release the allowed mixed-link configurations are listed in Fig. 19 ("C" boxes).

© Nokia Siemens Networks

Fig. 19 Mixed link compatibility

Page 24: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 25

1.1.12 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.

© Nokia Siemens Networks

3G BTSGiga

EthernetETH

ETH

traffic

Fig. 20 HotStandby Stand-alone

Page 25: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 26

1.1.13 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.

© Nokia Siemens Networks

3G BTS

Giga

EthernetETH

ETH

f0H

f0v

traffic

Fig. 21 2+0 XPIC with FlexiBTS

Page 26: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 27

2 FlexiPacket MultiRadio: Some installation examples

Page 27: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 28

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. 22).

Fig. 22 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.

In this chapter, figures with the green border are for "Full packet and Hybrid mode", figures with the blue border are for "Full Packet Mode" only and figures with the orange border are for the "Hybrid Mode" only.

Page 28: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 29

Fig. 23 1+0 system with integrated antenna

Page 29: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 30

Fig. 24 1+0 system with independent antenna

Page 30: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 31

Fig. 25 Hot Stand-by/1+1 FD (co-polar) system with integrated antenna

Page 31: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 32

Fig. 26 1+1 Hot Stand-by/1+1 FD (co-polar) system with independent antenna

Page 32: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 33

Fig. 27 1+1 FD (cross-polar) system with independent antenna

Page 33: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 34

Fig. 28 1+1 FD SD system with integrated antenna

Page 34: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 35

Fig. 29 2+0 XPIC/2+0 FD (cross-polar) system with independent antenna (Full Packet Mode)

Page 35: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 37

3 FlexiPacket FirstMile 200 Protection Methods

Page 36: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 40

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

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.

Page 37: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 41

4 FlexiPacket HUB 800 Protection Methods

4.1 CES linear Protection (2.0EP1)

This protection protects Circuit Emulation (CES) services.

It’s a E2E protection mechanism.

It’s 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

© Nokia Siemens Networks

2G

E1

FPH 800 R2.0EP1

Fig. 32 HUB800 CES Linear Protection

Page 38: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 44

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

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.

Page 39: 006. Configuration & Protection.pdf

Configurations and Protections

FT48928EN03GLA0

© 2012 Nokia Siemens Networks 45

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. 34 FPH 800 STM-1 MSP protection