FlexiPacket Microwave and

Tellabs 8630/8660
Interoperability

Solution Overview

Issue: 1 Issue date: August 2011

A25000-A1205-A008-01-76P1
 Solution Overview

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMEN-
TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT,
INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT
LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR
THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2011. All rights reserved.

f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the “Legal, Safety
and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit

Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-
anforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,
Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-
satzes.

2 A25000-A1205-A008-01-76P1
Issue: 1 Issue date: August 2011
Solution Overview

Table of Contents
This document has 24 pages.

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5 Waste electrical and electronic equipment (WEEE) . . . . . . . . . . . . . . . . 9
1.6 RoHS compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 FlexiPacket and Tellabs interoperability . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2 Products overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.1 FlexiPacket Microwave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.2 Tellabs 8630 / 8660 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3 Basic interoperability - scenarios and configurations. . . . . . . . . . . . . . . 13
2.3.1 Data plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.3.1.1 FPR/FPMR-Tellabs 8630/8660 IoT scenario . . . . . . . . . . . . . . . . . . . . . 14
2.3.1.2 FPR/FPMR-Tellabs 8630/8660-FM200/FPH800 IoT scenario . . . . . . . 15
2.3.2 Management plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.2.1 1+0 links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.2.2 1+1 links FPR/FPMR-Tellabs 8630/8660 IoT scenario . . . . . . . . . . . . . 17
2.3.2.3 1+1 links FPR/FPMR-Tellabs 8630/8660-FM200/FPH800 IoT scenario 18
2.3.3 CESoP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3.4 1+1 HSBY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3.5 Co-Channel and Diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.3.6 Synchronous Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

A25000-A1205-A008-01-76P1 3
Issue: 1 Issue date: August 2011
 Solution Overview

List of Figures
Figure 1 WEEE label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 2 Example of backhauling architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 3 FlexiPacket Microwave product suite . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 4 Tellabs 8630 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 5 Tellabs 8660 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 6 FPR/FPMR-Tellabs 8630/8660 IoT scenario . . . . . . . . . . . . . . . . . . . . . 14
Figure 7 FPR/FPMR-Tellabs 8630/8660-FM200/FPH800 IoT scenario . . . . . . . . 14
Figure 8 FPR-Tellabs 8630/8660 IoT: DCN configuration . . . . . . . . . . . . . . . . . . 17
Figure 9 FPR-Tellabs 8630/8660-FM200/FPH800 IoT: DCN configuration . . . . . 18
Figure 10 Link between Tellabs 8660 and FlexiPacket FirstMile 200 . . . . . . . . . . . 19
Figure 11 Protected links managed by the same devices. . . . . . . . . . . . . . . . . . . . 19
Figure 12 Protected links managed by different devices . . . . . . . . . . . . . . . . . . . . 20
Figure 13 Synchronous Ethernet interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 14 ESMC compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4 A25000-A1205-A008-01-76P1
Issue: 1 Issue date: August 2011
Solution Overview

List of Tables
Table 1 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Table 2 List of symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Table 3 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 4 Configuration vs. Functionalities compatibility matrix . . . . . . . . . . . . . . 16

A25000-A1205-A008-01-76P1 5
Issue: 1 Issue date: August 2011
 Solution Overview

6 A25000-A1205-A008-01-76P1
Issue: 1 Issue date: August 2011
Solution Overview Preface

1 Preface
This document describes interoperability scenarios between FlexiPacket Microwave
(FlexiPacket Radio, FlexiPacket MultiRadio, FlexiPacket FirstMile 200 / Hub 800) and
Tellabs routers (Tellabs 8630, Tellabs 8660).

1.1 Intended audience

This document is intended to engineers and technicians who design and configure the
Nokia Siemens Networks solutions. The reader is supposed to have a basic knowledge
of the products in scope of this document.

1.2 Structure of this document

The document is divided into the following main chapters:

Chapter Title Subject

Chapter 1 Preface Provides an introduction to the
document
Chapter 2 FlexiPacket and Tellabs Description of the solution
interoperability
Chapter 3 Acronyms and abbreviations Lists the acronyms and abbreviations
used in this document

Table 1 Structure of this document

1.3 Symbols and conventions

The following symbols and mark-up conventions are used in this document:

Representation Meaning

f DANGER! A safety message indicates a dangerous situation where

personal injury is possible.
f WARNING! The keywords denote hazard levels with the following meaning:
f CAUTION! DANGER! - Indicates a hazardous situation which, if not
avoided, will result in death or serious (irreversible) personal
injury.
WARNING! - Indicates a hazardous situation which, if not
avoided, could result in death or serious (irreversible) personal
injury.
CAUTION! - Indicates a hazardous situation which, if not
avoided, may result in minor or moderate (reversible) personal
injury.

w NOTICE: A property damage message indicates a hazard that may result

in equipment damage, data loss, traffic interruption, and so on.

Table 2 List of symbols and conventions

A25000-A1205-A008-01-76P1 7
Issue: 1 Issue date: August 2011
Preface Solution Overview

Representation Meaning

g A note provides important information related to the topic, for

example, not obvious exceptions to a rule or side effects.

t A tip provides additional information related to the topic which is

not essential in the context, but given for convenience.
Bold • All names of graphical user interface (GUI) objects, such as
windows, field names, buttons, and so on.
Example: Select the Full Screen check box and press OK.
• Terms and abbreviations which are linked to an entry in the
glossary and list of abbreviations respectively
• Important key words
Italic • Files, folders, and file system paths.
Example: /usr/etc/sbin/ftpd.exe
• Emphasized words
typewriter • Input to be typed in a command line or a GUI field.
Examples:
ping -t 192.168.0.1
Enter World in the Domain field.
• Output from a command, error messages, content of a status
line, and so on
• File content, such as program sources, scripts, logs, and
settings
<angle brackets> Placeholders, for example as part of a file name or field value.
Examples:
<picture name>.png or <ip address>:<port number>
[square brackets] A key to be pressed on a PC keyboard, for example [F11].
Keys to be pressed simultaneously are concatenated with a “+”
sign, for example [CTRL]+[ALT]+[DEL].
Keys to be pressed one after another are concatenated with
spaces, for example [ESC] [SPACE] [M].
> The greater than symbol “>” is used to concatenate a series of
GUI items in order to depict a GUI path. This is an abridged pre-
sentation of a procedure to be carried out in order to perform an
action or display a window or dialog box.
Examples:
A simple menu path: File > Save as ...
A more complex GUI path:
SURPASS TransNet window > Tools menu >
3R-Matrix Report command > 3R-Matrix Report dialog box

Table 2 List of symbols and conventions (Cont.)

8 A25000-A1205-A008-01-76P1
Issue: 1 Issue date: August 2011
Solution Overview Preface

Representation Meaning
x For convenience, card names are sometimes listed with a lower
(in card names) case x variable, in order to concisely represent multiple cards.
Example:
I01T40G-x (is to be interpreted as I01T40G-1 and I01T40G-2)

Table 2 List of symbols and conventions (Cont.)

Screenshots of the graphical user interface are examples only to illustrate principles.
This especially applies to a software version number visible in a screenshot.

1.4 History of changes

Issue Issue date Remarks

1 August 2011 1st version

Table 3 History of changes

1.5 Waste electrical and electronic equipment (WEEE)

All waste electrical and electronic products must be disposed of separately from the
municipal waste stream via designated collection facilities appointed by the government
or the local authorities. The WEEE label (see Figure 1) is applied to all such devices.

Figure 1 WEEE label

The correct disposal and separate collection of waste equipment will help prevent poten-
tial negative consequences for the environment and human health. It is a precondition
for reuse and recycling of used electrical and electronic equipment.
For more detailed information about disposal of such equipment, please contact Nokia
Siemens Networks.
The above statements are fully valid only for equipment installed in the countries of the
European Union and is covered by the directive 2002/96/EC. Countries outside the
European Union may have other regulations regarding the disposal of electrical and
electronic equipment.

1.6 RoHS compliance

FlexiPacket Radio complies with the European Union RoHS Directive 2002/95/EC on
the restriction of use of certain hazardous substances in electrical and electronic equip-
ment.

A25000-A1205-A008-01-76P1 9
Issue: 1 Issue date: August 2011
Preface Solution Overview

The directive applies to the use of lead, mercury, cadmium, hexavalent chromium, poly-
brominated biphenyls (PBB), and polybrominated diphenylethers (PBDE) in electrical
and electronic equipment put on the market after 1 July 2006.
Materials usage information on Nokia Siemens Networks Electronic Information
Products imported or sold in the People’s Republic of China
FlexiPacket Radio complies with the Chinese standard SJ/T 11364-2006 on the restric-
tion of the use of certain hazardous substances in electrical and electronic equipment.
The standard applies to the use of lead, mercury, cadmium, hexavalent chromium, poly-
brominated biphenyls (PBB), and polybrominated diphenyl ethers (PBDE) in electrical
and electronic equipment put on the market after 1 March 2007.

10 A25000-A1205-A008-01-76P1
Issue: 1 Issue date: August 2011
Solution Overview FlexiPacket and Tellabs interoperability

2 FlexiPacket and Tellabs interoperability

2.1 Overview
This document describes interoperability scenarios between Nokia Siemens Networks
(NSN) FlexiPacket Microwave and Tellabs routers, with focus on the following products:
• FlexiPacket Microwave family:
• FlexiPacket Radio
• FlexiPacket MultiRadio
• FlexiPacket FirstMile 200
• FlexiPacket Hub 800
• Tellabs:
• 8630
• 8660
A high level example of a typical network architecture, including FlexiPacket Microwave
and Tellabs, is shown in Figure 2.

Figure 2 Example of backhauling architecture

t A wide range of architectures can be designed with FlexiPacket Microwave and Tellabs,
including, but not limited to the setups described in this document. These setups
provides a number of building blocks which can be combined in a complete network
design.
The relevance of the setups included in the document is that they have been tested and
verified in Nokia Siemens Networks lab in order to assess:
• Functional interoperability between Tellabs and Nokia Siemens Networks devices
including:
• Interoperability between Tellabs equipment and NSN FlexiPacket ODU (Radio
and MultiRadio - FPR and FPMR in the following), in those configurations with
direct connection of ODU to Tellabs routers.
• Interoperability between Tellabs equipment and NSN switches (IDU - Indoor
Unit), namely, FlexiPacket FirstMile 200/Hub 800 (respectively FM200 and
FPH800 in the following).
• Proper behaviour of specific features developed in Tellabs devices to strengthen the
technical value of the joint Nokia Siemens Networks-Tellabs solution, such as:
• CESoP over UDP/IP application.

A25000-A1205-A008-01-76P1 11
Issue: 1 Issue date: August 2011
FlexiPacket and Tellabs interoperability Solution Overview

• NSN proprietary 1+1 Hot Stand-by radio protection mechanism implemented by

Tellabs equipment.

2.2 Products overview

2.2.1 FlexiPacket Microwave

Nokia Siemens Networks FlexiPacket Microwave is a new packet microwave system
designed to meet the requirements of evolved transport networks with the target of min-
imizing the operator Total Cost of Ownership (TCO). It joins together the benefits of an
advanced scalable microwave radio and of a real carrier grade Ethernet nodal solution.
FlexiPacket Microwave is the means of deploying a cost-effective microwave infra-struc-
ture for 2G, 3G, WiMAX and LTE backhaul, high speed wireless Internet networks, fixed
broadband access backhaul and private wireless networks.
FlexiPacket Microwave is the right solution to design advanced mobile backhaul
networks based on Ethernet transport. The solution is conceived both for pure packet
and TDM + Packet hybrid networks.

Figure 3 FlexiPacket Microwave product suite

For the detailed information of FlexiPacket Radio, FlexiPakcet MultiRadio, FlexiPacket
FirstMile 200, FlexiPacket Hub 800 please refer to related official Nokia Siemens
Networks product descriptions.

2.2.2 Tellabs 8630 / 8660

Readers can refer to Tellabs official documentation for a detailed description of Tellabs
devices.
This section highlights functionalities of Tellabs 8630/8660 involved into the IoT with
FlexiPacket products.
• Physical interface: among all line cards supported by the modular architecture of
Tellabs 8630/8660.
• following cards support CESoP/UDP/IP:
• 4 port channelized STM-1 IFM
• 1 port channelized STM-1 IFM
• 24 port chE1 Multiservice IFM
• Following cards supports 1+1 HSBY

12 A25000-A1205-A008-01-76P1
Issue: 1 Issue date: August 2011
Solution Overview FlexiPacket and Tellabs interoperability

• IFC2 interface card equipped with 8-port Ethernet 10/100/1000Base-TX R2

IFM
• Synchronous Ethernet: it is supported in a number of line cards. To the purpose of
IOT with FPMW note it is supported in the aforementioned 8 port Eth R2 IFM in both
TX and RX.
• TDM PseudoWire (PWE): it supports the standard IETF CESoP Pseudo Wire appli-
cations allowing to transport TDM E1/T1 traffic over packet networks; in detail, it
supports the MPLS-based encapsulation stack and the UDP/IP-based stack. The
latter is interoperable with FlexiPacket IDU.
• Nokia Siemens Networks proprietary 1+1 Hot Stand-By Protocol: this functionality
allows Tellabs equipment to handle protected FlexiPacket Radio-based microwave
radio links.

Figure 4 Tellabs 8630

Figure 5 Tellabs 8660

2.3 Basic interoperability - scenarios and configurations

2.3.1 Data plane

With regards to the data plane two interoperability scenarios are described:
• The interoperability between the FPR/FPMR and the Tellabs equipment
(8630/8660, refer to Figure 6);

A25000-A1205-A008-01-76P1 13
Issue: 1 Issue date: August 2011
FlexiPacket and Tellabs interoperability Solution Overview

Figure 6 FPR/FPMR-Tellabs 8630/8660 IoT scenario

• The interoperability between the FPR/FPMR, Tellabs equipment (8630/8660) and

NSN FlexiPacket Indoor Units, FlexiPacket FirstMile 200 and Hub 800 (respectively
FM200 and FPH800, refer to Figure 7).

Figure 7 FPR/FPMR-Tellabs 8630/8660-FM200/FPH800 IoT scenario

The main characteristics associated to these scenarios are described in the following
sections.

2.3.1.1 FPR/FPMR-Tellabs 8630/8660 IoT scenario

In this scenario the network, either IP or MPLS, is based on Tellabs 8630/8660 devices,
ODUs are used to connect Tellabs 8630/8660 with packet-based MW links. ODUs can
be used to interoperate with Tellabs 8630/8660 independently. They are used as IP or
MPLS routers. The interoperability is guaranteed according to the guidelines and
general rules described in the following.
Tellabs 8630/8660 Ethernet interfaces towards the ODUs are configured as Ethernet
trunk interfaces.
Different traffic frame formats can be transported over the radio link. In terms of quality
of service, this translates into the following guidelines:

14 A25000-A1205-A008-01-76P1
Issue: 1 Issue date: August 2011
Solution Overview FlexiPacket and Tellabs interoperability

• Single VLAN tagged Ethernet traffic which can be classified for QoS by FPR/FPMR
according to the PCP field of the VLAN tag.
• Untagged Ethernet traffic containing IP packets which can be classified for QoS by
FPR/FPMR according to the DSCP field.
• MPLS packets: for the MPLS traffic there are two possible options:
• MPLS traffic is VLAN tagged by Tellabs router before crossing the radio link. In
detail, Tellabs router tags MPLS traffic properly configuring the PCP field of the
tag according to the QoS that has to be reserved to the specific traffic classes (a
mapping between MPLS EXP filed and VLAN ID PCP filed can be configured
on), the PCP information will be used by FPR as classification criterion to apply
QoS.
• MPLS traffic is transmitted without VLAN and FlexiPacket ODU forward it trans-
parently across the radio link. This solution is not recommended with FPR, as
FPR QoS classification criteria would not be usable. On the contrary with Flexi-
Packet MultiRadio QoS classification based on MPLS EXP would be used. Such
EXP based classification will be supported in next releases of FPR too (refer to
official FlexiPacket roadmap).
• Untagged Ethernet traffic containing non-IP packets:
• In FPR, all the untagged traffic is served in the lowest priority queue. The lowest
priority queue should not be congested (this is obtained by a proper traffic load
planning with a related proper weights configuration on FPR queues) in order to
avoid that control plane traffic (Spanning Tree Protocols, ESMC protocols, etc.)
experience some packet losses.
• In FPMR, additional classification criteria (Ethertype, Source and Destination Ip
address, source and Destination MAC address) are supported, which allows to
map untagged traffic to the desired priority queue. Such additional classification
criteria will be supported in next releases of FPR too (refer to official FlexiPacket
roadmap).
With regards to the IP addressing plans, the following rules apply. Each VLAN domain
is associated to a single IP subnet; this means that each Tellabs 8630/8660 supports
different IP addresses, one for each VLAN domain, belonging to different subnets.

2.3.1.2 FPR/FPMR-Tellabs 8630/8660-FM200/FPH800 IoT scenario

In this scenario, the network is based on a mix of two different network technologies: the
IP/MPLS routing implemented by Tellabs 8630/8660 devices and the Carrier Ethernet
bridging implemented by the NSN IDUs.
This scenario describes how the two different technologies interoperate on the boundary
between the two domains; such boundary between the Tellabs 8630/8660 and the NSN
IDUs can consist on either a cable connecting directly the devices or on a radio link
handled by the ODUs. In both cases, the interoperability is guaranteed according to the
guidelines and general rules described in the following.
In this scenario the Tellabs 8630/8660 device is configured as IP/MPLS router; Tellabs
8630/8660 Ethernet interfaces towards the ODUs are configured as Ethernet trunk inter-
faces. The two domains, IP/MPLS and Carrier Ethernet are terminated on the Tellabs
8630/8660 device.
All traffic IP/MPLS traffic coming from the IP/MPLS domain is mapped on VLAN-based
Carrier Ethernet services and transmitted towards the NSN IDUs throughout either the
cable or the radio link. Across the radio link two different traffic frame formats can be

A25000-A1205-A008-01-76P1 15
Issue: 1 Issue date: August 2011
FlexiPacket and Tellabs interoperability Solution Overview

carried. The same QoS rules described in the previous paragraph can be used in this
scenario too.
The NSN IDUs interfaces towards the Tellabs 8630/8660 device can be configured
either as:
• UNI interface, or
• NNI interface.
Depending on how they are configured the different functionalities are available as
showed in Table 4.

NSN IDU port configuration Functionalities

[UNI / NNI] Single ODU 1+1 HSBY
UNI Yes No
NNI Yes Yes

Table 4 Configuration vs. Functionalities compatibility matrix

g In order to implement a 1+1 HSBY, link between Tellabs and NSN IDU, the
FM200/FPH800 ports have to be configured as NNI ports.

In order to guarantee interoperability in this scenario, the QoS aware routing functional-
ity has to be enabled. This functionality allows to perform the QoS mapping between the
DSCP and the couple [VLAN ID, PCP] fields.

2.3.2 Management plane

Configuration guidelines related to the management plane are described in this section
with reference to both local and remote management.
In case of local management:
• With regards to the management of Indoor Units: Tellabs 8630/8660 devices and
NSN IDUs can be accessed by the related management ports of the devices;
Tellabs 8630/8660 devices are managed via Command Line Interface (CLI); NSN
IDUs are managed via WebLCT.
• With regards to the management of ODUs: FPR/FPMR can be accessed from the
management port of the NSN IDUs or from a free Ethernet interface of any interface
card in Tellabs router; management traffic is routed and properly formatted (tagged)
towards the FPR/FPMR; FPR/FPMR is managed by its LCT.
In case of remote management different options exist depending on the link configura-
tion (1+0 or 1+1) and on whether the radio link is connected to Tellabs 8630/8660
devices at both the sides or not. These options are described in the following sections.
The IP addressing plans for DCN are shown as well.

2.3.2.1 1+0 links

FlexiPacket MW makes use of a management VLAN which is configured in all the
devices of the family. When using Tellabs in 1+0 links, a VLAN sub-interface is created
in the Tellabs interface towards FlexiPacket ODU. This allows to transport tagged VLAN
management traffic towards FlexiPacket ODU (and FlexiPacket IDU, in a mixed link:

16 A25000-A1205-A008-01-76P1
Issue: 1 Issue date: August 2011
Solution Overview FlexiPacket and Tellabs interoperability

Tellabs – FPR/FPMR – FPR/FPMR – NSN IDU). A VLAN p-bits value is configured over
this interface to ensure proper QoS to the management traffic.

2.3.2.2 1+1 links FPR/FPMR-Tellabs 8630/8660 IoT scenario

It is useful to describe the reachability from remote in terms of two sections:
• Firstly, the way to reach from the remote Network Management Station (NMS) the
Tellabs 8630/8660 device where the managed FPR is directly connected. This is
done by using the specific technology used by Tellabs 8630/8660 devices (IP
routing, IP/MPLS, MPLS-based PP-VPN, etc.).
• Secondly, the way to reach the FPR from the Tellabs 8630/8660 device where it is
directly connected.
The general plan for VLAN domains and IP addressing is represented in Figure 8. Five
subnets are defined, one subnet is associated to each FPR present in the link ; one
subnet is associated to the logical connection between the two Tellabs 8630/8660
devices. According to these planning the local FPRs are seen by the Tellabs 8630/8660
as directly connected whilst the remote ones are reachable through the remote Tellabs
8630/8660 device on the common logical subnet. As shown in the picture the VLAN IDs
of the different subnets associated to the different FPRs can be the same (VLAN 40 is
used in the picture example). This value must be different from that one of the subnet
associated to the logical link among the two Tellabs 8630/8660 devices. A routing
protocol has to be enabled in order to propagate information about the reach-ability of
the different subnets across the ring.

Figure 8 FPR-Tellabs 8630/8660 IoT: DCN configuration

Note that the management traffic has no reserved bandwidth but it is managed accord-
ing to the QoS criteria configured on the FPRs. It is recommended to reserve an high
priority treatment over the radio link so that the management channel is preserved in its
connectivity by potential congestion situations over the radio link itself.

A25000-A1205-A008-01-76P1 17
Issue: 1 Issue date: August 2011
FlexiPacket and Tellabs interoperability Solution Overview

2.3.2.3 1+1 links FPR/FPMR-Tellabs 8630/8660-FM200/FPH800 IoT scenario

In this scenario the solution depends on where the remote NMS is located and which is
the first Indoor Unit encountered along the path; we can distinguish among two cases:
• The first indoor unit is the Tellabs 8630/8660 device; in this case all the FPRs of the
link can be directly accessed by the Tellabs 8630/8660 device without passing
across the NSN IDUs; This is the most typical case.
• The first indoor unit is a NSN IDUs; the directly connected FPRs can be accessed
by the local NSN IDUs; the remote ones can be accessed by passing through the
remote Tellabs 8630/8660 device which performs routing towards them.
The general plan for VLAN domains and IP addressing is represented in Figure 9. Three
subnets are defined, two of which are associated to each FPR directly connected to the
Tellabs 8630/8660 device; one subnet is associated to the logical connection between
the Tellabs 8630/8660 device, the NSN IDUs and the connected FPRs. Note that the
NSN IDUs and the connected FPRs are placed in the same subnet since all these
devices are layer 2 VLAN Ethernet switches. According to these planning all the FPRs
are seen by the Tellabs 8630/8660 as directly connected; under the point of view of NSN
IDU the remote FPRs are reachable through the remote Tellabs 8630/8660 device on
the common logical subnet.

Figure 9 FPR-Tellabs 8630/8660-FM200/FPH800 IoT: DCN configuration

As shown in Figure 9 the VLAN IDs of the different subnets associated to the FPRs con-
nected to the Tellabs 8630/8660 can be the same (VLAN 40 is used in the picture exam-
ple). This value must be different from that one of the subnet associated to the logical
link among the Tellabs 8630/8660, the remote NSN IDU and related FPRs.
A special consideration has to be made on the management channel over the radio link
with FPR. This channel is an asymmetric channel: in one direction, from Tellabs
8630/8660 to NSN IDU, it has no reserved bandwidth, whilst in the opposite direction it
has reserved bandwidth (FPR R-channel). This implies that in the direction from Tellabs
8630/8660 towards NSN IDU management traffic is handled according to the QoS
criteria configured on the FPRs.

18 A25000-A1205-A008-01-76P1
Issue: 1 Issue date: August 2011
Solution Overview FlexiPacket and Tellabs interoperability

It is recommended to reserve an high priority treatment over the radio link so that the
management channel is preserved in its connectivity by potential congestion situations
over the radio link itself.

2.3.3 CESoP
Tellabs 8630/8660 supports two alternative protocol stacks for CESoP applications:
• CESoP over MPLS, which is not compatible with NSN IDUs; thus it cannot be used
in the interoperability scenarios with FM200/FPH800.
• CESoP over UDP/IP, which is compatible with NSN IDUs and which has to be used
in the interoperability scenarios with FM200/FPH800.
This functionality is compatible with that one implemented on NSN IDUs FM200 and
FPH800. This implies that TDM E1 flows can be emulated between two points of the
network with different equipment (CESoP over UDP/IP between Tellabs and FP IDU is
supported). For example NxE1 can be transported via CESoP over UDP/IP betweenTel-
labs 8660 and a FirstMile 200, as depicted in Figure 10. This interoperability has been
tested and validated by NSN.

Figure 10 Link between Tellabs 8660 and FlexiPacket FirstMile 200

2.3.4 1+1 HSBY

Tellabs 8630/8660 devices support the NSN proprietary protocol for 1+1 Hot Stand-by.
The 1+1 HSBY mechanism can be used in both in the FPR-Tellabs 8630/8660 interop-
erability scenario (Figure 11) and in the FM200/FPH800-Tellabs 8630/8660 scenario
(Figure 12).

Figure 11 Protected links managed by the same devices

A25000-A1205-A008-01-76P1 19
Issue: 1 Issue date: August 2011
FlexiPacket and Tellabs interoperability Solution Overview

Figure 12 Protected links managed by different devices

This section provides additional information about the implementation in Tellabs

8630/8660 devices.
The mechanism is implemented as an extension of the Tellabs proprietary Ethernet Link
Protection protocol; it is coherent with that one implemented on the NSN IDUs and it is
based on the replication, in TX direction, of protected traffic flows over the two Ethernet
connections towards the two FPRs in protection. The working and protection interfaces
where the FPRs in protection are connected are located on different IFMs and on differ-
ent IFCs; this allows has a double advantage:
• To protect against Tellabs 8630/8660 Indoor Unit pluggable cards failures.
• To avoid traffic interruption on the system during the software upgrade of Tellabs
8630/8660 devices.
There are no intermediate devices between Tellabs 8630/8660 and connected FPR
except optional power injector and Ethernet repeater.
FPRs are responsible for the coordination and the dynamics of the protection actions.
Tellabs 8630/8660 device only executes static replication and merging of the user plane
traffic and it provides CCM services for connection towards co-located protected FPRs.
The un-revertive behaviour is supported.
System is targeted to provide traffic restoration time shorter than 400 ms. In a protected
system, different frames are processed in different way:
• Data Plane traffic: the traffic which has to be transported over theradio link and
therefore protected - transparently; traffic is protected over the radio link by replicat-
ing traffic on working and protected interfaces on Tellabs 8630/8660 device. Related
VLANs are explicitly configured to the protected interface of Tellabs 8630/8660.
Untagged Traffic is by default replicated to working and protected interfaces.
• Management Plane: VLAN IDs associated to near-end FPRs are not protected and
dedicated VLANs are created on the working port for working FPR and on the pro-
tected port for the protected FPR (see chapter 2.3.2). The management traffic asso-
ciated to the remote FPRs is managed as data-plane traffic.
• Ethernet OAM Continuity Check Messages (CCM) is the traffic associated to the
protection mechanism traffic. Two flows exist:
• FPR-Tellabs 8630/8660 monitoring traffic: Ethernet-based OAM connectivity
between Tellabs 8630/8660 device and connected FPRs is monitored using
ETH OAM CCM with vendor specific TLVs. Two OAM CCM flows are defined,
one for each FPR; each runs over unprotected VLAN IDs; these VLAN IDs which
can be the same for the two different flows have to be explicitly configured on
both FPRs and Tellabs 8630/8660 devices; the time period associated to the
OAM CCM flow is 100 ms.

20 A25000-A1205-A008-01-76P1
Issue: 1 Issue date: August 2011
Solution Overview FlexiPacket and Tellabs interoperability

• FPR-FPR monitoring traffic: Ethernet-based OAM CCM connectivity between

two co-located FPRs is embedded into a dedicated VLAN ID and this flow is
bridged among working and protected interfaces. This VLAN ID is unprotected
and it is transparent for Tellabs 8630/8660 device, which guarantees connectiv-
ity among the co-located FPRs. This VLAN ID has to be explicitly configured on
both the FPRs and the Tellabs 8630/8660 device. Note that in Tellabs
8630/8660 terminology this VLAN ID is called VLAN bridging. The time period
associated to the OAM CCM flow is 100 ms.

2.3.5 Co-Channel and Diversity

The same Nokia Siemens Networks proprietary protocol for 1+1 HSBY is also used to
support additional configurations of FlexiPacket MultiRadio, namely:
• 1+1 Frequency Diversity
• 1+1 Space Diversity
• 2+0 Co-channel (XPIC) with Load balancing
• 2+0 Frequency Diversity with Load balancing
In other words, all configurations above are, from the perspective of the device the ODU
are connected to, equivalent. As a consequence, same setups (i.e. Tellabs-Tellabs and
Tellabs – NSN IDU) described in previous paragraph for 1+1 HSBY, can be extended to
other 1+1 and 2+0 configurations.
1+1 HSBY, 1+1 Frequency Diversity and 2+0 Frequency Diversity configurations have
been tested and validated in NSN laboratory.
Actually, 2+0 Load Balancing configurations are expecially interesting and are therefore
briefly described in the following. Load balancing operates on redundant radio links and
allows to:
• Maximize the throughput
• Optimize the resource utilization
The Load Balancing feature allows to double the net throughput over redundant radio
links.
Load Balancing feature is available on 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
Among the unique advantage of 2+0 NSN implementations are:

A25000-A1205-A008-01-76P1 21
Issue: 1 Issue date: August 2011
FlexiPacket and Tellabs interoperability Solution Overview

• Independency of the Indoor Units (IDUs) - No specific hardware/software feature to

support the feature in IDU/Routers. ODUs are responsible of load balancing
between the 2 links which acts as a single pipe from IDU perspective.
• Independency of the single radio link from each other: the two radio links are com-
pletely independent in terms of modulation.
Efficient load balancing via a proprietary protocol: The load balancing of traffic among
the two radio links is managed by a proprietary protocol which achieve 100% efficiency,
acting at physical layer, i.e. taking into account on real time the actual capacity of the 2
radio links and splitting the traffic accordingly with fine granularity.

2.3.6 Synchronous Ethernet

Synchronous Ethernet is supported by all devices of FlexiPacket Microwave as outlined
in chapter 2.2. Tellabs 8630/8660 can be synchronized / propagate synchronization by
means of Synchronous Ethernet.
Tellabs 8630/8660 have an internal timing generator compliant with both Synchronous
Equipment Clock (SEC) and Stratum 3, and can be configured to operate in one of these
modes:
• The holdover process by means of which Tellabs 8630/8660 devices learn the fre-
quency of the reference takes about 20 minutes; during this time the system is
anyway locked to the reference source;
• The Clock Selection Algorithm is based on up to five potential clock sources entries
selected based on priority, quality and error-free conditions;
• The Synchronization Status Messaging (SSM) protocol is supported and implanted
according to the standard.
In Figure 13 shows the typical scenario for Synchronous Ethernet application in the
context of a backhauling network based on Tellabs 86xx and FlexiPacket Microwave.

Figure 13 Synchronous Ethernet interoperability

Devices are statically configured as Master/Slave depending on the specific direction of
clock propagation. SSM messages are exchanged and processed between Tellabs
8630/8660 and FM200/H800; they are transparently carried across the radio link by the
FPR.
Figure 14 shows an example of the ESMC protocol handling and the consequent effects
on the clock propagation.

22 A25000-A1205-A008-01-76P1
Issue: 1 Issue date: August 2011
Solution Overview FlexiPacket and Tellabs interoperability

Figure 14 ESMC compatibility

When locked FM200 device can process the incoming messages from the Tellabs
8630/8660 device and to generate consistent messages forward (locked scenario in
Figure 14); in case of interruption of ESMC propagation across the radio link due to
failure or fading, FM200 device is capable to interpret the status and to take consequent
actions (entering into holdover mode and propagating ESMC messages with related
quality in the unlocked scenario depicted in Figure 14).

A25000-A1205-A008-01-76P1 23
Issue: 1 Issue date: August 2011
Acronyms and abbreviations Solution Overview

3 Acronyms and abbreviations

CCM Continuity Check Message

CES Circuit Emulation Service

CESoP CES over PSN

COS Class of Service

DSCP Differentiated Services Code Point

ESMC Ethernet Synchronization Messaging Channel

FPFM FlexiPacket FirstMile 200

FPR FlexiPacket Radio

HSBY Hot Standby

IETF Internet Engineering Task Force

LCT Local Craft Terminal

LTE Long Term Evolution

MWR Microwave Radio

MPLS Multi Protocol Label Switching

PCP Priority Code Point (p-bit)

PSN Packet Switched Network

PW Pseudo-wire

SSM Synchronization Status Message

TDM Time Division Multiplexing

VLAN Virtual Local Area Network

24 A25000-A1205-A008-01-76P1
Issue: 1 Issue date: August 2011