10 ft4282aen02gla0 configurations

Configurations

FT4282AEN02GLA0 © 2010 Nokia Siemens Networks

1

Contents 1 FlexiPacket Radio System Configurations 3 1.1 System configurations 3

Configurations

Configurations

FT4282AEN02GLA0

© 2010 Nokia Siemens Networks 2

Configurations


3

1 FlexiPacket Radio System Configurations 1.1 System configurations The equipment is available with the configurations listed in Fig. 1.

Installation schemes are reported in Fig. 2, Fig. 3, Fig. 4 and Fig. 5.

WARNING Pictures are based to XD ODUs type and XD antennas type. For FH overview refer to same principle used for FlexiHopper.

Fig. 1 System configurations

Note 1: The type of waveguide connection between the ODU and the antenna can be either flexible or elliptical.

FlexiPacket Microwave 1+1 Hot Stand-by is available from the SVR 1.2

Configurations

FT4282AEN02GLA0


1+0 System with Integrated Antenna

Fig. 2 1+0 System with Integrated Antenna

Configurations


5

1+0 System with Independent Antenna

Fig. 3 1+0 System with Independent Antenna

Configurations

FT4282AEN02GLA0


1+1 Hot Stand-by system with integrated antenna

FlexiPacket Hub or FlexiPacked First Mile

Fig. 4 1+1 Hot Stand-by system with integrated antenna

WARNING for 1+1 HSBY protection of FlexiPacket only FlexiPacket First Mile or FlexiPacket Hub can be used.

1+1 is available from the SVR 1.2

Configurations


7

1+1 Hot Stand-by system with independent antenna

FlexiPacket Hub or FlexiPacked First Mile

Fig. 5 1+1 Hot Stand-by system with independent antenna

WARNING for 1+1 HSBY protection of FlexiPacket only FlexiPacket First Mile or FlexiPacket Hub can be used.

FlexiPacket Microwave 1+1 Hot Stand-by will be available with the SVR 1.2

Configurations

FT4282AEN02GLA0


1.1.1 1+1 Hot Stand-by In order to provide resilience against hardware failures, FPR ODU shall support a 1+1 Hot Stand-by protection scheme.

When connected to a single A2200 IDU equipped with 2 copper interface cards, up to 15 ports are available for the ODUs.

Therefore it is possible to install up to 7 pairs of protecting ODUs. The two ports connected to the redundancy pair of ODUs must have different number parity (one port number shall be odd and the other one even).

WARNING two odd number ports or two even ports are not allowed to be the interfaces connected to the protecting ODUs.

When both Ethernet IFCs are plugged, it is advisable to install a pair of main and protecting ODUs on two ports belonging to different cards. The different number parity shall be always guaranteed.

Mixed configurations, i.e. some ODUs with system type 1+1 and some with system type 1+0, are also possible as reported in Fig. 6; the restrictions are the number of free ports on the IDU and, for 1+1, the port number parity.

The 1+1 HSBY protection scenario involves a single A2200 IDU and a pair of FPR ODUs.

In the protection scheme 1+1 ODUs, the IDU has to duplicate the traffic (data plane) to both protected ODUs.

In this way the traffic is not affected by any ODU failure.

Configurations


9

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

The duplication capability is available on NNI ports only, so the IDU ports connected to each ODU of the protection scheme shall be configured as NNI as reported in

Fig. 6.

In addition, the two ports shall be full duplex and with the same speed.

NNI NNI

A-2200A-2200A-2200

1+1

NNI NNI

Fig. 6

Configurations

FT4282AEN02GLA0


The protection scheme mainly relies upon the Continuity Check protocol defined in IEEE 802.1ag-2007.

For the sake of clarity, the basic terminology adopted in the aforementioned reference is reported below:

• Maintenance Domain (MD): is a domain (or a part of domain) for which faults in connectivity are to be managed

- a domain is a network (or a part of a network) capable of offering connectivity to systems outside the domain;

• Maintenance Association (MA): is an association of elements configured to verify the integrity of a specific service

- a MA is identified by a Short MA name

- a MA is composed of Maintenance Association End Points (MEPS), capable of performing connectivity verification

• Continuity Check Message (CCM): a multicast message transmitted by the MEP and received by the other MEPs within the same MA for connectivity verification.

IDU and ODUs play the role of MEPs in this scenario. The messages used for handling the protection are illustrated in Figure Fig. 7:

• P-CCM: ODU to ODU in a protecting ODU pair

• E-CCM: IDU to ODU

The Continuity Check Message provides a means to detect connectivity failures in a Maintenance Association.

In our scenario, three MAs per protected radio link are defined (and consequently 3 CCM sessions are present):

• MA ODU 1 – ODU 2 (associated to a P-CCM session)

• MA IDU – ODU 1 (associated to a E-CCM session)

• MA IDU – ODU 2 (associated to a E-CCM session)

the CCM is carried in a multicast frame.

WARNING a pool of 50 VID are reserved for Control Plane (E-CCM and P-CCM)

Each MEP (IDU and ODUs) is configured to periodically transmit a CCM.

A connectivity failure is then defined as either:

• Inability of a MEP to receive 3 consecutive CCMs from the other MEP in its MA

• Reception by a MEP of an incorrect CCM.

The transmitting MEP sets the Remote Defect Indication (RDI) to "1" if it doesn’t receive CCMs from the other configured MEP.

Configurations


11

How it works The working FlexiPacket Radio 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 Radio until it periodically receives these Continuity Check messages. If Continuity Check messages from working FlexiPacket Radio are not received anymore, the FPHub flushes its own L2 tables and enables forwarding towards the other port.

The Stand-by FlexiPacket Radio remains switched OFF (both in Tx and Rx) until it periodically receives Continuity check messages from the working FlexiPacket Radio. 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-CCMPort Even

P-CCM

Keepalive

Keepalive

Working

Standby

Fig. 7 ECC Signals

Configurations

FT4282AEN02GLA0


10 ft4282aen02gla0 configurations

Documents