flexipacket multi radio 2.4 commission

FlexiPacket MultiRadioRel. 2.4

Commission

A25000-A1600-B030-01-76P1

Issue: 1 Issue date: October 2011

2 A25000-A1600-B030-01-76P1Issue: 1 Issue date: October 2011

Commission

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

A25000-A1600-B030-01-76P1Issue: 1 Issue date: October 2011

3

Commission

Table of ContentsThis document has 92 pages.

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.4 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.5 Waste electrical and electronic equipment (WEEE) . . . . . . . . . . . . . . . 111.6 RoHS compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.7 Safety instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.7.1 RF Energy Health Hazard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.7.2 Protection against Lightning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.7.3 Protection from RF Burns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.7.4 Warning – Turn off all power before servicing . . . . . . . . . . . . . . . . . . . . 14

2 Test instrument list and measurement accessories. . . . . . . . . . . . . . . . 152.1 Tools and Test Instruments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2 Typical test bench overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3 System configuration and line-up phase . . . . . . . . . . . . . . . . . . . . . . . . 183.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2 Installation Check summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.1 FlexiPacket MultiRadio configuration summary . . . . . . . . . . . . . . . . . . . 193.2.2 Antennas alignment (both FlexiPacket MultiRadios) . . . . . . . . . . . . . . . 193.2.3 Line-Up and commissioning (both stations). . . . . . . . . . . . . . . . . . . . . . 193.3 Installation checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3.1 Outdoor installation check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3.1.1 Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3.1.2 Flexible waveguide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.3.1.3 Elliptical waveguide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.3.1.4 Mounting kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.3.1.5 FlexiPacket MultiRadio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.3.2 Indoor-Outdoor cable installation visual checking . . . . . . . . . . . . . . . . . 26

4 Requirements for WebLCT PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

5 PC connection to the FlexiPacket MultiRadio . . . . . . . . . . . . . . . . . . . . 30

6 Equipment configuration (station A). . . . . . . . . . . . . . . . . . . . . . . . . . . . 316.1 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336.1.1 Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356.1.1.1 Synchronization parameter overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 366.1.1.2 Synchronization configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386.1.2 Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416.1.2.1 CCM area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416.1.2.2 Link Protection Group area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426.2 GbE - Physical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446.3 GbE - Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476.4 Radio - BB/Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71


Commission

6.5 Radio - RF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736.6 Station A correct operation check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766.7 IP address assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776.8 Date & Time configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.8.1 Manual setting of date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.8.2 Synchronization of the NE via Time Server SNTP (Time server Setting)836.9 Before leaving terminal station A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846.9.1 Alarms status check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

7 Equipment configuration (station B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

8 Antenna alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

9 System commissioning and testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899.1 Link connectivity check (using the remote loopback) . . . . . . . . . . . . . . . 899.2 Interferences evaluation check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91


5

Commission

List of FiguresFigure 1 WEEE label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 2 General layout for the link test (1+0 - case 1) . . . . . . . . . . . . . . . . . . . . 16Figure 3 General layout for the link test (1+0 - case 2) . . . . . . . . . . . . . . . . . . . . 16Figure 4 General layout for the link test (1+1 - case 3) . . . . . . . . . . . . . . . . . . . . 17Figure 5 Example of 0.3m (1ft) XD antenna (Low profile version shown) . . . . . . 21Figure 6 Example of 0.6m (2ft) XD antenna (Low profile version shown) . . . . . . 21Figure 7 Example of XD Antenna 0,3 and 0,6 mt Polarization Identification on Horn

Feeder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Figure 8 Overview 1+0 Not Integrated Mounting . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 9 Outdoor overview for 1+1 Integrated Mounting . . . . . . . . . . . . . . . . . . . 25Figure 10 Outdoor overview for 1+1 Not Integrated Mounting. . . . . . . . . . . . . . . . 25Figure 11 Fixing of Indoor-Outdoor cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 12 Indoor-Outdoor cable, Grounding connection (IDU cable). . . . . . . . . . . 27Figure 13 Indoor-Outdoor cable, Grounding connection (ODU cable). . . . . . . . . . 28Figure 14 Open NE screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 15 FlexiPacket MultiRadio - Main view . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Figure 16 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 17 Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Figure 18 Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 19 Port Quality level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 20 Clock source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 21 Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Figure 22 GbE - Physical (1+0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 23 GbE - Physical (1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 24 Switch configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Figure 25 Forwarding area configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 26 Static MAC Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 27 Add in MAC Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 28 Static MAC Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 29 Special frame handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 30 VLAN Support area configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 31 Default VLAN Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 32 VLAN Id Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 33 VLAN Table with one VLAN Id. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 34 VLAN DB Table example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 35 VLAN Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Figure 36 E1 Priorization area configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 37 Filtering Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 38 Filtering Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Figure 39 Traffic Service configuration table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 40 Header Compression Service configuration table . . . . . . . . . . . . . . . . . 58Figure 41 HC rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Figure 42 Port Configuration area configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 62Figure 43 VLAN priority table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Figure 44 VLAN priority modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Figure 45 Modified VLAN priority table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63


Commission

Figure 46 802.1p Priority Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Figure 47 802.1p priority table modify. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Figure 48 Diffserv priority table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Figure 49 Diffserv priority modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Figure 50 L2/L3 address criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Figure 51 L2/L3 address criteria add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Figure 52 MPLS label table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Figure 53 MPLS label modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Figure 54 Ether Type table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Figure 55 Ether Type add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Figure 56 Scheduling area configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Figure 57 Scheduling dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Figure 58 Jumbo frame management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Figure 59 BB/Modem Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Figure 60 Profiles Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Figure 61 RF Configuration (ATPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Figure 62 RF Configuration (RTPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Figure 63 BB/Modem Configuration: service state selection . . . . . . . . . . . . . . . . . 74Figure 64 Tx RF frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Figure 65 RTPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Figure 66 ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Figure 67 Continuous Wave Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Figure 68 HW Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Figure 69 Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Figure 70 IP Setting Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Figure 71 Physical Topology discovery via LLDP . . . . . . . . . . . . . . . . . . . . . . . . . . 81Figure 72 Manual setting of date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Figure 73 Synchronization of NE via Time Server SNTP . . . . . . . . . . . . . . . . . . . . 83Figure 74 Alarms menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Figure 75 Example BNC Connection on FlexiPacket MultiRadio . . . . . . . . . . . . . . 87Figure 76 Standard antenna pointing for 1 antenna system . . . . . . . . . . . . . . . . . . 87Figure 77 Antennas aim for 2 antenna system in Hot Stand By configuration . . . . 88Figure 78 Antennas aim for 2 antenna system in Frequency Diversity configuration .

88Figure 79 Link connectivity test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Figure 80 Measurements menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Figure 81 Remote squelch command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92


7

Commission

List of TablesTable 1 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 2 List of symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Table 3 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Table 4 Test Instruments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Table 5 Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Table 6 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Table 7 Flexible waveguide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Table 8 IP addresses scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Table 9 FlexiPacket MultiRadio configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 30Table 10 System configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Table 11 CCM use summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Table 12 FlexiPacket MultiRadio Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Table 13 ODUs roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Table 14 IP addressing scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Table 15 Available parameters for DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78


Commission


9

Commission Preface

1 PrefaceThis document provides a guideline for placing into service a FlexiPacket MultiRadio link.

1.1 Intended audienceThis document is intended to the commissioning technicians in charge to commission a FlexiPacket MultiRadio link.

1.2 Structure of this documentThe document is divided into the following main chapters:

1.3 Symbols and conventionsThe following symbols and mark-up conventions are used in this document:

Chapter Title Subject

Chapter 1 Preface Provides an introduction to the document and the safety instructions

Chapter 2 Test instrument list and mea-surement accessories

Provides the list of the Test instruments and accessories to be used during the commissioning

Chapter 3 System configuration and line-up phase

Provides the list of the checks to be done before starting the commissioning

Chapter 4 Requirements for WebLCT PC Provides the instructions to install the WebLCT on the PC

Chapter 5 PC connection to the Flexi-Packet MultiRadio

Provides the instructions to connect the WebLCT to the FlexiPacket MultiRadio

Chapter 6 Equipment configuration (station A)

Provides the operations to be done to configure the FlexiPacket MultiRadio in station A

Chapter 7 Equipment configuration (station B)

Provides the operations to be done to configure the FlexiPacket MultiRadio in station B

Chapter 8 Antenna alignment Provides the instruction to correctly align the antenna

Chapter 9 System commissioning and testing

Provides the operations to be done to check the properly working operation of the radio link between station A and station B

Table 1 Structure of this document


CommissionPreface

Representation Meaning

fDANGER!

fWARNING!

fCAUTION!

A safety message indicates a dangerous situation where personal injury is possible.

The keywords denote hazard levels with the following meaning:

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.

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.1Enter 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>

Table 2 List of symbols and conventions


11

Commission Preface

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

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.

[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:> Nokia Siemens Networks TransNet window > File menu > Change Password command > Change Password dialog box

x(in card names)

For convenience, card names are sometimes listed with a lower case x variable, in order to concisely represent multiple cards.

Example:

I01T40G-x (is to be interpreted as I01T40G-1 and I01T40G-2)

Representation Meaning

Table 2 List of symbols and conventions (Cont.)

Issue Issue date Remarks

1 October 2011 1st version

Table 3 History of changes


CommissionPreface

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 complianceFlexiPacket MultiRadio complies with the European Union RoHS Directive 2002/95/EC on the restriction of use of certain hazardous substances in electrical and electronic equipment.

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 ChinaFlexiPacket MultiRadio complies with the Chinese standard SJ/T 11364-2006 on the restriction of the use of certain hazardous substances in electrical and electronic equip-ment. The standard applies to the use of lead, mercury, cadmium, hexavalent chro-mium, polybrominated biphenyls (PBB), and polybrominated diphenyl ethers (PBDE) in electrical and electronic equipment put on the market after 1 March 2007.

1.7 Safety instructionsIn this paragraph are indicated all the safety rules and the precautionary measures to follow while carrying out operations on the equipment in order to prevent injuries to per-sonnel and/or damages to the equipment components.

t PLEASE READ THESE SAFETY PRECAUTIONS!


13

Commission Preface

1.7.1 RF Energy Health Hazard

This symbol indicates a risk of personal injury due to radio frequency exposure.

The radio equipment described in this guide uses radio frequency transmitters.

No one shall be allowed to come in the close proximity of the antenna's front while the transmitter is operating. The antenna will be professionally installed on the outdoor per-manent fix-mounted structures in order to keep it separate from any other antenna and from everybody else.

f WARNING!RF Energy Exposure Limits and Applicable Rules for 6-38 GHz. It is recommended that for each radio equipment deployment site the radio equipment operator refers to the RF exposure rules and precaution for each frequency band and to all other applicable rules and precautions with respect to transmitters, facilities, and operations that may affect the environment due to the RF emissions.Appropriate warning signs must be properly placed and affixed at the equipment site and access entries.

1.7.2 Protection against Lightning

Article 810 of the US National Electric Department of Energy Handbook 1996 specifies that radio and television lead-in cables must have adequate surge protection at or near the point of entry to the building. The code specifies that any shielded cable from an external antenna must have the shield directly connected to a 10 AWG wire that connects to the building ground electrode.

Do not turn on power before reading product documentation. This device has a -48 VDC direct current input.

1.7.3 Protection from RF BurnsIt is dangerous to stare into or stand in front of an active antenna aperture. Do not stand in front of or look into an antenna without first ensuring that the associated transmitter or transmitters are switched off. Do not stare into the waveguide port of an ODU (if appli-cable) when the radio is active.


CommissionPreface

1.7.4 Warning – Turn off all power before servicing

f WARNING!Turn off all power before servicing.


15

Commission Test instrument list and measurement accessories

2 Test instrument list and measurement acces-sories

2.1 Tools and Test Instruments

Test Instruments Notes

Personal Computer / Laptop (Minimum HW Requirements)(Suggested Qty 2)

• CPU Pentium 4 or higher • 256 Mbyte RAM minimum (Suggested 512) • Color monitor with resolution of 1024x768 at least • Video card with minimum resolution of 1024x768 • 10 Gbyte Hard-disk minimum • CD-ROM drive • Mouse • Ethernet network card (RJ45 interface)

Personal Computer / Laptop (SW Requirements)

• Microsoft Windows XP Professional / Microsoft Windows Vista / Microsoft Windows 7

• Optional browser: recommended Microsoft Internet Explorer 8.0 (Note: The browser is optional because the WebLCT can start also from the command line via Java Web Start (javaws http://<ip address> or javaws http://<ip address>/public/application.jnlp)

• Java Runtime Environment (Version 1.6.0_10 or latest version is preferred) (Note: Check that the Java cache is enabled and clean).

Multimeter Suggested Analog or Digital Multimeter

Table 4 Test Instruments

Accessories Notes

ETH Cat 5e cable type RJ45 Straight and Cross type both end cabled (all wire)

Cable for antenna alignment BNC / Banana (must be build in Field)

Table 5 Accessories

Tools Notes

RJ45 Connectors Crimping Tool (suggested)

Technical Tools bag

Table 6 Tools


CommissionTest instrument list and measurement accessories

2.2 Typical test bench overviewCase 1 (1+0): P+E solution (only 1 cable)

Figure 2 General layout for the link test (1+0 - case 1)

Case 2 (1+0): 2-cable solution



17

Commission Test instrument list and measurement accessories

Case 3 (1+1)



CommissionSystem configuration and line-up phase

3 System configuration and line-up phase

3.1 RequirementsThe technicians responsible for the commissioning of the equipment must have the fol-lowing basic requirements:

• ETH main concept system know-how • Microwave Radio Link system know-how • FlexiPacket MultiRadio equipment radio basic know-how • Basic PC know-how • Skill to use FlexiPacket MultiRadio software management • Mechanical installation know-how (antennas, rack, waveguide, cabling, etc.)

If the technician is not familiar with the FlexiPacket MultiRadio system, it is suggested that he reads the product documentation.

Before switching ON the equipment verify that all the installation items have been properly installed.

In order to operate and configure the FlexiPacket MultiRadio it is important to follow the phases step by step.

Assuming that the link is made up of a Station A and of a Station B, the operations shall begin on Station A and the other station will be OFF.

For each station it is suggested to proceed in the manner stated below.

3.2 Installation Check summaryOutdoor installation

• Antenna assembling and Positioning • Antenna Fixing • Antenna Polarization • Flexible waveguide (or elliptical WG) fixing • If applicable fix and assemble the Mounting Kit • Properly assemble the FlexiPacket MultiRadio to the antenna or mounting Kit • FlexiPacket MultiRadio Grounding Connections • Indoor-Outdoor cable properly assembled • Indoor-Outdoor cable Grounding connection

Indoor-Outdoor cable installation (1 cable or 2 cables according to the implemented Power Supply solution)

• Indoor-Outdoor Cable length (refer to the system specification in the PD manual) • Indoor-Outdoor cable connections • Indoor-Outdoor cable properly assembled • Indoor-Outdoor cable properly fixed

Acceptance tests are performed to ensure that proper installation procedures detailed in the installation manual have been applied.

t Report any problems to the installation group in order to solve the problem before System Switching On or Line-Up and Commissioning.


19

Commission System configuration and line-up phase

3.2.1 FlexiPacket MultiRadio configuration summary • Check the DC Power voltage and related Pin Out connection. • Switch ON the DC Power Breakers. • Connect the PC to the FlexiPacket MultiRadio. • Log-In into the FlexiPacket MultiRadio. • Configure the equipment. • Set the basic IP address. • Set the NE date and time. • Repeat all the above steps on the opposite FlexiPacket MultiRadio.

3.2.2 Antennas alignment (both FlexiPacket MultiRadios) • Set the Frequency channel as project specification. • Set the ATPC to disabled mode on both FlexiPacket MultiRadios. • Same modulation scheme in both stations • On both FlexiPacket MultiRadios set the Tx Power configuration as per project spec-

ification. If not specified, set the Max. Power • Only in 1+1 configuration: on the protection setting force the working path on the

main FlexiPacket MultiRadio • Start with the Alignment phase • Only in 1+1 configuration: on the protection setting configure the system to auto-

matic mode • After alignment check the RF Rx Power value (using the PC) and verify that the

value complies with that of project specification.

3.2.3 Line-Up and commissioning (both stations) • Taking as reference the relevant commissioning test sheets, proceed to register the

configuration data and all Local and Link Line-up tests.



3.3 Installation checksThis phase is fundamental for all the other technical activities.

It is a statistical data, where most of the field problems or link troubles are caused by a wrong mechanical installation of all the parts making up the system.

Installation check must be sub-divided into two fundamental groups:

• Outdoor installation (section 3.3.1) • Indoor-Outdoor cable installation (section 3.3.2)

3.3.1 Outdoor installation checkUse all the necessary safety devices for working at certain altitudes. Verify that all the outdoor components making up the system have been properly assembled, installed and cabled.

The following are the typical outdoor components making up the systems:

• Antenna • Flexible waveguide (if applicable) • Elliptical waveguide (if applicable) • Mounting Kit (if applicable) • FlexiPacket MultiRadio and related Grounding Connections

3.3.1.1 AntennaFollowing the assembling instructions supplied by the antennas supplier, check that all the mechanical assembling components have been properly assembled and fixed.

Verify that the antennas have already been oriented in the direction of the remote station (refer to the project specification; to check the antenna Azimuth value pay attention if using the compass to verify the antenna pointing).

t The compass reader placed near a metal structure (in particular on the TLC structure) is subjected to errors introduced by magnetic effects. It is suggested to aim the antenna by using external reference point (mountain, building, tree etc.).Use the compass (not near the tower structure) to identify the reference point.Note that the value measured with the compass refers to the magnetic coordinates (Magnetic North), but most of the project refers to the geographic coordinates (True North). Slight differences are possible.

Check that the output polarization agrees with the project specification.

Normally horn feeder fixing and antennas have a reference mark to identify the polariza-tion.

In the case of dual polarization horn feeder a label or mark (also described in the antenna assembling instructions) identifies the H or V polarization.

Depending on the antenna diameter, type and supplier, verify (if necessary) the instal-lation of the wind bracket and check (if applicable) if this component has been properly installed. Note that the wind bracket needs to be fixed on a separate mount pole in order to maintain a proper angle between the antenna and the bracket fixing point.

FlexiPacket MultiRadio is compatible with the XD antennas.


21


XD antenna

Figure 5 Example of 0.3m (1ft) XD antenna (Low profile version shown)

Figure 6 Example of 0.6m (2ft) XD antenna (Low profile version shown)



Figure 7 Example of XD Antenna 0,3 and 0,6 mt Polarization Identification on Horn Feeder

t For the compatibility with the FlexiHopper antennas a special adapter (to be installed on the FlexiPacket MultiRadio) is available (refer to the “HW Install” document).


23


3.3.1.2 Flexible waveguideThis chapter is applicable if the connection of FlexiPacket MultiRadio (fixed to the proper mounting kit support) is through a flexible waveguide supplied with the system

Check that they have been properly installed, in particular:

• Appropriate length, based on antenna diameter and distance (typically 0.6 m or 1 m).

• No close bending or anomalous torsion (note that normally the flexible waveguide supplied is also twistable).

• Check that the flange termination has been properly fixed by using the correct screws to the antenna and Mounting support; • in case of doubt disconnect them from the antenna and mounting support and

check the installation of the O-ring between the flanges. • Check that the waveguide-fixing bracket (supplied with the flexible wave-guide) has

been properly installed. The system needs 1 fixing bracket for WG of up to 0.6 m, and 2 fixing brackets for WF of up to 1 m.

Flexible Wave-guide

Supplied Fixing Kits

Scheme Installation Hints

60 cm One : Pole Fixing Set

1.The Clamp must be installed as close as possible to the middle of the Flex. (30cm), this in accordance with structural boundaries.

2.The Flexible Waveguide must be installed according to its mechanical specifications as: Maximum twist and minimum bend radius (E/H Plane)

100 cm Two : Pole Fixing Sets

1.The two Clamps must be installed with (33cm) spacings this in accor-dance with structural boundaries.

2.The Flexible Waveguide must be installed according to its mechanical specifications as: Maximum twist and minimum bend radius (E/H Plane)

Table 7 Flexible waveguide



3.3.1.3 Elliptical waveguideThis chapter is applicable if the connection of FlexiPacket MultiRadio (fixed to the proper mounting kit support) is through an elliptical waveguide supplied with the system.

Check that they have been properly installed, in particular:

• Appropriate length, based on antenna diameter and distance. • No close bending or anomalous torsion. • Check that the flange termination connector has been properly fixed by using the

correct screws to the antenna and Mounting support; • in case of doubt disconnect them from the antenna and mounting support and

check the installation of the O-ring between the flanges.

3.3.1.4 Mounting kitThe mounting kit is used in case of installation with independent antenna.

Check if the FlexiPacket MultiRadio mounting kit has been properly assembled and fixed to the pole.

Check that the position of this component does not introduce an anomalous torsion on the flexible waveguide.

Refer to the installation description to verify if the mounting kit model installed is like the model reported in the project specification.

In 1+1/2+0 it is also fundamental to verify the positioning of the FlexiPacket MultiRadio installed on the mounting support.

Figure 8 Overview 1+0 Not Integrated Mounting

For 1+1 system a label affixed on the mounting identifies the positioning of the Main channel and the Stand-by Channel.


25


Figure 9 Outdoor overview for 1+1 Integrated Mounting

Figure 10 Outdoor overview for 1+1 Not Integrated Mounting



3.3.1.5 FlexiPacket MultiRadioCheck that the FlexiPacket MultiRadio installed covers the proper frequency band as specified on the project (check the P/N and extension number on the FlexiPacket Multi-Radio label and check the relevant P/N reported in the technical description).

Verify the proper positioning of the mounting kit and related connection with the Indoor-Outdoor cable.

Verify that the cover cup of the BNC connector (used for antenna aiming phase) is properly closed.

Check if the antenna (or mounting support) has been properly fixed (refer to the descrip-tion given in the technical description or in the Installation description).

Check that the grounding connection tail, starting from the FlexiPacket MultiRadio, is properly connected to a good grounding distribution point.

3.3.2 Indoor-Outdoor cable installation visual checkingVerify that the cable lenght is less than the maximun recommended lenght.

t The FlexiPacket MultiRadio can be connected to the Indoor Device by using:

• 2 cables (1 cable for the Ethernet interface to be connected to the Ethernet connec-tor and 1 cable for the Power Supply to be connected to the PS connector);

• 1 cable only to be connected to the Ethernet connector, if the Power+Ethernet solution has been used. In this case the Power Injector must be installed or the Flex-iPacket MultiRadio must be connected to an Ethernet powered port of the Indoor device.

Verify if the cable is properly tied, if all connectors are properly assembled and installed in the right position.

• Ethernet cable: Amphenol (Outdoor side) and RJ45 (Indoor side) • PSU cable (if required): Amphenol (Outdoor side).

On the outdoor connector, verify that the shrink sleeve is properly assembled and fixed on the connector body.

Other PVC and water proofing material is optional material; the connectors need no other particular protection.

Verify that the cable is properly fixed and tied to the support ladder (indoor and outdoor). The distance suggested between each fixing point is defined in the installation docu-ments.

In any case refer to the following table:

If the cable is tie-fixed, it is suggested to fix the ties in a cross mode, in order to prevent the cable from sliding or falling off.

External Ethernet cable cat5e 24 AWG

External PSU cable 13 AWG

Recommended Maximum Tie (or Clamp) spacing: 0.3 m


27


Figure 11 Fixing of Indoor-Outdoor cable

Check that the cable path from the FlexiPacket MultiRadio is not under stress or subject to an anomalous torsion.

Check that the grounding connection of the Indoor-Outdoor cable is properly connected before the building/shelter entrance to an appropriate Grounding distribution plate.

Note that two grounding kits per cable are supplied with the system (one additional kit per cable is supplied each 30 m cable lenght after the first 40 m). In any case refer to the customer and project specification.

Figure 12 Indoor-Outdoor cable, Grounding connection (IDU cable)



Figure 13 Indoor-Outdoor cable, Grounding connection (ODU cable)


29

Commission Requirements for WebLCT PC

4 Requirements for WebLCT PCRefer to Table 4 Test Instruments on page 15.


CommissionPC connection to the FlexiPacket MultiRadio

5 PC connection to the FlexiPacket MultiRadio • Connect the Ethernet interface of the PC to the FlexiPacket MultiRadio depending

on the test bench scenario (refer to para. 2.2 on page 16). • FlexiPacket MultiRadio has two IP addresses:

• For the default configuration, the IP address of the PC needs to be 192.168.255.x, where x (between 4 and 253) provides an available IP address.

• If no DCN Planning configuration is available (or Stand alone Link) it is suggested to configure on the equipment the following IP addresses (refer to para. 6.7 to set these parameters).

Consequently the PC must be set with an IP address belonging to the same IP Subnet.

Before opening the PC it is suggested to verify the connectivity between the PC and the Equipment. To check apply a ping command from the Windows DOS Prompt.

IP Default IP address

IPpublic (configurable) 0.0.0.0

IPdefault (fixed) 192.168.255.3

Table 8 IP addresses scheme

FlexiPacket MultiRadio Configuration Description

Station A Station B

IP Address (1+0) 10.10.10.16 10.10.10.18

IP Addresses (1+1) 10.10.10.16

10.10.10.17

10.10.10.18

10.10.10.19

IP Netmask 255.255.255.0 255.255.255.0

DHCP Client Disabled Disabled

Table 9 FlexiPacket MultiRadio configuration


31

Commission Equipment configuration (station A)

6 Equipment configuration (station A)This chapter gives all the information to configure the main parameters of the NE in order to implement the commissioning.

t In case of 1+1 configuration configure first the Main FlexiPacket MultiRadio and then the Protection FlexiPacket MultiRadio.

Steps

1 Open the Web browser:

2 Enter http:\\192.168.255.3 (default IP address)

t From a single PC it is possible to open at least 16 WebLCT instances at the same time in order to configure at least 16 FlexiPacket MultiRadios.

3 The Java authentication screen opens.

Figure 14 Open NE screen

4 Enter:

• User name: admin • Password: sysmanager

t After the first launch you can install a shortcut into the desktop through the Java Control Panel.

5 The NE main view is presented.


CommissionEquipment configuration (station A)

Figure 15 FlexiPacket MultiRadio - Main view

The left-hand part of the window contains a tree structure organized in folders, which represent the main functionalities. In turn, each main functionality is divided into functions, according to the above structure. The Commission, included in Status and Config > Equipment, comprises:

• System Configuration • Operation Administration & Maintenance • Gbe: Physical • Gbe: Switch • Radio: BB Modem • Radio: RF • Networking • Date & Time


33


6.1 System Configuration

Figure 16 System Configuration

The dialog box is divided into System Type, System and Configure areas.

System Type areaSteps

1 In the System Type area click on the Change System Type button. The following screen opens.

2 Select the System Type and the Cables (one or two) to be used to interconnect the FlexiPacket MultiRadios to the Indoor Device. The supported configurations are shown in Table 10.



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

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

• HW Protection mode 3 (Standalone): for interoperability with a generic L2 Bridge which implements Learning, Forwarding and Filtering.

3 Select the Mode: CCM based or Standalone, as explained in the previous table. The mode can be changed only in configurations with 2 cables.

4 Only for 2+0 XPIC System Type select the Polarization to be associated to the FlexiPacket MultiRadio: horizontal polarization or vertical polarization.

5 Enter the P-CCM VID: specific VID for each Protection Group (from 16 to 49).

Configuration HW protection

Mode (Note 1)

ETSI supported

system type

NAM supported

system type

1+0 - x x

1+0 Ring - x x

1+1 Hot Stand-by - 2 cables CCM based x x

Standalone x -

1+1 Hot Stand-by - single cable - x -

1+1 FD - 2 cables CCM based x x

1+1 SD - 2 cables CCM based x -

2+0 FD - 2 cables CCM based x x

2+0 XPIC - 2 cables CCM based x x

Standalone x -

2+0 XPIC - single cable - x -

Table 10 System configurations


35


System areaSteps

1 Four comment fields are provided for Customer convenience: Name/Con-tact/Location/User Data.

2 Field Powered by can take one of the following values:

• Info Not Used: No information in the field • External PS: Power supply on the dedicated cable • Midspan-injector: Power supply coming from the Power Injector • Switch-pse: Power + Ethernet from the Indoor Device

This field is only for user information.

Configure areaSteps

1 Click on the Synchronization button to configure the synchronization parameters (refer to paragraph 6.1.1).

2 Click on the Protection button in case of 1+1 System Types to configure the protec-tion parameters (refer to paragraph 6.1.2).

6.1.1 SynchronizationClicking on the Synchronization button (in the Configure area of the System Config-uration menu) the Synchronization menu opens.

Figure 17 Synchronization

The menu has 2 tab-panels:

• In Use Configuration • Local Status



6.1.1.1 Synchronization parameter overviewDifferent parameters have to be configured:

• Operation Mode: to configure the direction of clock propagation; three options are available: • No clock transfer: the system is not configured to carry synchronization infor-

mation (Free Run); • Fixed Clock Transfer: the direction of the synchronization propagation is stati-

cally configured (by means of Source Port item in the Synchronization menu); it is not changed run-time based on quality or priority;

• Priority Based Clock Transfer: the direction of clock propagation is determined on the basis of the source priority: the source with the highest priority is the one selected as a source port.

• GbE source type: to declare if the characteristics of GbE interface are compliant to Synchronous Ethernet quality; to allow this interface to be selected as synchroniza-tion source this option MUST be flagged.

• Source for synch propagation: to select the source port. The effect depends on the selected direction of clock propagation: in particular, in case of : • No Clock Transfer: it has no effect; • Fixed Clock Transfer: it indicates the fixed clock source; • Priority based Clock Transfer: it indicates the preferred source clock (highest

priority). • SSM management: to enable//disable the management of SSM messages; two

options are available: • Disabled: it foresees the following behavior:

• The FlexiPacket MultiRadio does not handle the received SSM messages and it discards them;

• The FlexiPacket MultiRadio does not generate the SSM messages; • Enabled: The SSM messages are taken into account for determining the quality

associated to a synchronization source. This option has to be selected also in case of the quality of a source is forced by means of the clock source table in the synchronization menu.

t The Local capabilities field (menu GbE > Physical) must be set to 1000Base-T Full Duplex for the selection as synchronization source.

t The Synchronization via Synchronous Ethernet requires the configuration of the QoS capabilities for the proper management of the SSM messages. This configuration must be done in GbE > Switch menu.

Several parameters have to be configured: the first one is the classification criteria for the identification of the SSM messages. The criterion according to which they are clas-sified can be either:

• Ether-Type: the option has to be flagged; the value is 8809 (showed in this example)Or

• Destination MAC address: the value is 01-80-C2-00-00-02

In the EtherType Priority Add menu two parameters have to be configured:

• EtherType value (8809);


37


• Priority Value, which has to be set equal to a priority associated to a non-congestion subject WFQ queue.

t SSM management (Quality Level)The Sync source quality levels are transmitted via SSM messages. The SSM contains the quality level of the transmitting clock, and hence represents a unidirectional channel between the Sync control in the transmitter NE and that of the receiver NE.

The quality criterion can be disabled (enabled / disabled modes) upon configuration, that is quality level shall not be considered in order to choose the sync source.

In the disabled mode, the selection is based on the criteria of enabling / alarm / priority. Furthermore, no SSM messages shall be transmitted from the Sync interfaces, and possible received SSM messages shall be ignored. Finally, in this mode, lack of received SSMs is not considered a fault condition of the Sync source.

In the enabled mode, among all the available sources, the one with highest quality is selected. Only Sync sources with received quality level higher than QL-DNU are quali-fied for the system clock selection. A received signal carrying a SSM with QL-DNU must not be used for synchronization because a timing loop situation could result if it is used.

To protect against possible failure, the lack of the messages for a 5 second period is considered to be a failure condition. That Sync source is then subject to a wait-to-restore period (see below).

Upon reception of an event SSM, the QL state is changed to the new QL value, and the information timer is reset.

The transmitted SSMs contain the quality level of the selected source (and, as men-tioned, QL-DNU in case of free-running); however, in order to avoid timing loops, the system transmits from some interfaces the QL-DNU quality level instead of the system clock quality level.

More in detail, the system must always transmit an SSM with QL-DNU from the interface which is used as the actual synchronization source for the NE clock; the system must always transmit an SSM with QL-DNU from the 1000Base-T GbE interface if it is slave-clock; the other cases of QL-DNU insertion depend on the configured system type and are detailed within the relevant subsections.



6.1.1.2 Synchronization configuration

Steps

1 Click on the Modify button in the In Use Configuration tab-panel.

Figure 18 Modify

2 Select the Operation mode: No Clock Transfer/Fixed Based Clock Trasfer/Priority Base Clock Transfer.

3 Select in the GbE source type “Synchronous” to propagate the synch.

4 Select in the Source for synch propagation field the source to be used to lock the system clock:

1. “GbE”: the clock extracted from the Ethernet interface to the IDU;2. “Radio”: the clock extracted from the received radio data IDU;3. “ODU-ODU”: the clock extracted from the data received from the other co-

located ODU (only in Configurations with two FlexiPacket MultiRadios).

5 Select the SSM management (Synchronous Status Message): enabled/disabled.

6 If the SSM management has been enabled, the Port quality level area appear.


39


Figure 19 Port Quality level

If the ports, as default, are in “Auto”, the clock recovered from the in use sync source is transported on the ports. On the port currently in use as sync source is written “Don’t use” (qlDUS).

By clicking on Modify it is possible to force the quality level for each port.

7 In the Local Status tab-panel in the Clock source area a summary of the current synchronization is shown.



Figure 20 Clock source

8 In the Local Synchronization status area the following information is given:

• ODU synch status: the source to which the synch is locked; • Sync switch counter: number of the sync switches occurred from the last reset; • SSM missing check box: it is automatically flagged in case of loss of the SSM.


41


6.1.2 ProtectionClicking on the Protection button (in the Configure area of the System Configuration menu) the below menu opens.

Figure 21 Protection

This menu is divided in two areas:

• CCM (paragraph 6.1.2.1 on page 41) • Link Protection Group (paragraph 6.1.2.2 on page 42)

6.1.2.1 CCM areaThe CCM area is a read-only area showing the configuration and the status of the CCM.

Column VID shows the ID assigned to each CCM (Continuity Check Message):

• IDU (E-CCM): embedded in the IDU • Protection (P-CCM): this ID must be unique for each LPG connected to the same

IDU. It must be assigned when the System Type is assigned (refer to the System Configuration menu)

• ODU-ODU (A-CCM): this ID is fixed to 50 and it is the same for each LPG.

Table 11 shows the summary of the CCM in the different System Types.



t Legenda:ns = not supported / not present

x = supported/present

- = not applicable

x (only if activated) = supported if the relevant configuration is enabled.

6.1.2.2 Link Protection Group areaThis area allows to configure the role and the other parameters depending on the System Type as shown in Table 12.

System Type HW protection

Mode

ODU Role IDU (E-CCM)

ODU-ODU (A-CCM)

Protection (P-CCM)

1+0 Chain - x x (only if activated) ns ns

1+0 Ring - x x (only if activated) x ns

1+1 SD/FD 2 cables

2+0 FD/XPIC 2 cables

2+0 XPIC Ring 2 cables

CCM based Don’t Care x x x

Standalone Don’t Care ns x x

1+1 HSBY 2 cables CCM based Don’t Care x ns x

Standalone Don’t Care ns x x

1+1 HSBY 1 cable - Main ns x ns

Protection x (only if activated) x ns

2+0 XPIC 1 cable - Main x (only if activated) x ns

Protection ns x ns

Table 11 CCM use summary

System Type HW protection

Mode

Role/Status Interfaces

GbE Radio ODU-ODU

1+0 Chain - x x x inactive

1+0 Ring - x x x x

1+1 SD/FD 2 cables2+0 FD/XPIC 2 cables2+0 XPIC Ring 2 cables

CCM based Active Master/Active Slave x x x

Standalone Active Master/Active Slave x x x

1+1 HSBY 2 cables CCM based Active/Standby x x inactive

Standalone Active/Standby x x x

2+0 XPIC 1 cable

1+1 HSBY 1 cable

- Active Master x x x

Active Slave inactive x x

Table 12 FlexiPacket MultiRadio Interfaces


43


The terminology used to identify the role and the status of the ODUs among the various System types is summarized in Table 13.

Main/Protection and Active/Standby: the first couple (it is a configuration) gives the priority of the ODU (useful when the revertive mode of operation is selected), while the second couple (it is a status) gives the actual role played.

Master/Slave configuration defines the priority of the ODU (useful when the revertive mode of operation is selected in the system types with two IDU-ODU cables), while the Active-Master/Active-Slave couple refers to the actual role played, which can change according to the status of the ODUs.

Steps

1 Set the Switching mode: revertive or unrevertive (available only with 1+1 HSB)

2 Set the Suspend interval: select the suitable time interval. Default: 160 sec. The Suspend interval is the time interval during which the controller is in freezing state. During this time the stand-by FlexiPacket MultiRadio receives no message from the active FlexiPacket MultiRadio, except the Suspend Interval message, which disables the switching for the time configured in the Suspend Interval.

3 Set the ODU role: depending on the configured System Type as shown in Table 12.

t The Force Down command acts on the protection group, causing a switching operation.

t The Rx Clock Switch field must be used to force the Rx switch in case of 1+1 FD or 1+1 SD.

Role Status

Main / Protection Active / Standby

Master / Slave Active-Master / Active-Slave

Table 13 ODUs roles



6.2 GbE - PhysicalFrom the left-side tree select GbE > Physical.

Figure 22 GbE - Physical (1+0)

Figure 23 GbE - Physical (1+1)


45


Steps

1 Verify that the Operational Status in the Ethernet area is up.

2 Set the MDI/MDI-X Autosensing field: automatic (default), manMDI and manMDIX. If set to Automatic the Ethernet cable to be connected to the FlexiPacket MultiRadio can be straigh or cross.

3 Set the Autonegotiation Protocol field: Enabled (default), Disabled.

If set to Enabled the bit rate and the operation type is automatically set by the Ethernet interface.

t In the Local Capabilities field, from the selection subwindow, select the desired value. The selected value is shown in Enabled Capabilities. It is possible to enter the max. capabilities to be negotiated.

4 For the 1000 BaseT interface the Autonegotiation Protocol must be always enabled. Use the default settings for the Master/Slave Selection field.

t To change the selection (Master or Slave) in the Synchronization screen the Settings must be Freerun (refer to par. 6.1.1).

5 The Flow Control field can be set to:

• Asymmetric Pause • Symmetric Pause • Asymmetric & Symmetric Pause • No Pause

6 Configure the Fast link down feature, if required.

When disabled, the link down is reported following IEEE standard after 750ms. When enabled, the notification is sent after the timeout defined in the Fast link down timing field.

7 Configure the Interface Shutdown on Radio Link feature (if required).

This features is available only with the System Types 1+0 and 1+0 Ring.

The user can enable/disable the feature and set its related configurable parameters:

• Interface Down Time:It is the time after which the Ethernet interface is turned on again.Range: [1…30]Default value: 6 secs. Step: 1 sec.

• Wait to Restore Time:It is the time that must elapse before enabling the radio port of the switch after the air-loss condition has ended.Range: [30...300]Default value: 60 secs. Step: 10 secs.

t This feature (available only in 1+0) speeds up the reconfiguration of the FlexiPacket MultiRadio-based rings beyond the possibilities of the standard xSTP protocol.

In a scenario defined by ring topology managed by RSTP, the FlexiPacket MultiRa-dio is requested to signal to the IDU, that runs the RSTP, a loss of connectivity on the radio interface by shutting down the GbE interface.



The IDU reacts instantly, i.e. not waiting for the timeout defined in the protocol, to such event (Ethernet link-down) by re-routing the data traffic towards the other direc-tion in the ring.

The behavior is:

• Upon detection of air-loss condition, the Ethernet interface of the GbE port is shut down, so that a link loss is detected at the other side of the Ethernet con-nection.

• The radio port of the switch is disabled (in order to avoid unidirectional link after the connection with the IDU has been restored) and the MAC forwarding table of the bridge is flushed.

• After a configurable timeout has elapsed the Ethernet interface is turned on again (to allow local management).

• The radio port of the switch is restored after the air-loss alarm is off only when a wait-to-restore time has elapsed.

8 Press pushbutton Reset to restart the physical interface.


47


6.3 GbE - SwitchFrom the left-side tree select GbE > Switch.

Figure 24 Switch configure

In the screen seven areas are present, which have to be configured:

1. Forwarding area2. VLAN Support area3. E1 Prioritization area4. Header Compression5. Priority Settings6. Scheduling7. Jumbo frame management



1) Forwarding area configuration

Figure 25 Forwarding area configuration

Steps

1 Change the Ageing Time, if needed. Default value: 300 sec.

2 Define a Static MAC table, if required, by clicking on Static MAC DB. The next screen opens.

Figure 26 Static MAC Table

3 Click on Add. The next screen opens.

Figure 27 Add in MAC Table

4 Enter the Destination MAC Address and select the Interface Type (Local Port/Radio Port/Micro Port).


49


t The internal L2 switch has 3 ports. One port (Local Port) is connected to the Ethernet interface; another port (Radio Port) is connected to the Modem and the last port (Micro Port) is connected to the internal microprocessor.

By selecting “Radio Port” the frame with the specified MAC destination address is always forwarded from the Local Port or from the Micro Port to the Radio Port.

By selecting “Local Port” the frame with the specified MAC destination address is always forwarded from the Radio Port or from the Micro Port to the Local Port.

By selecting “Micro Port” the frame with the specified MAC destination address is forwarded from the Radio Port or from the Local Port to the Micro Port.

5 Click on OK. The next screen opens with the MAC address previously inserted.

Figure 28 Static MAC Table

6 Check the Special Frame Handling table. No changes can be done.



Figure 29 Special frame handling

The Table is the default table with default MAC Address and default Mode where:

• filtered (the frame is discarded) • flooded (the frame is sent to all the ports) • management (the frame is sent to the microprocessor) • normal traffic (the frame transits between the local Ethernet port and the radio

port)

t By clicking on Clear All MAC DB Entries the MAC Table is cleared.

t By clicking on View MAC DB Entries the MAC Table (autolearning and static) can be exported in an xml file.


51


2) VLAN Support area configuration

Figure 30 VLAN Support area configuration

Steps:

1 Click the VLAN Table button.

2 The VLAN Table screen opens.

The VLAN table will include all the VLAN Ids which will be managed in the Priority Setting area. (All the other VLAN IDs will transit without any priority association).

Figure 31 Default VLAN Table

3 Click on Add and insert the VLAN ID with the relevant Description.

Figure 32 VLAN Id Add

4 Press OK.

5 The VLAN DB Table will include the VLAN ID previously configured.



Figure 33 VLAN Table with one VLAN Id

6 Repeat steps 3 to 4 to insert the other VLAN Ids. Max. number of rows: 4095.

7 In the next figure an example is given with 4 rows.

Figure 34 VLAN DB Table example


53


t How to delete a row in the VLAN table

Steps

a Select the row to be deleted.

Figure 35 VLAN Delete

b Click Delete.

c Click Close.

8 Put a check mark on the VLAN Filtering box to allow only to the VLAN IDs written in the VLAN table to enter the switch. All the other VLAN will be dropped at the input of the switch.



3) E1 Priorization area configuration (Modulation driven service add/drop feature)

Figure 36 E1 Priorization area configuration

The services can be filtered according to the following criteria:

• VID only • PCP (Priority Code Point) only • A combination of VID and PCP

Steps

1 In the ACM Threshold field, select the Modulation scheme. Below this threshold, in the ACM engine some services, selected in the Filtering Scheme field, will be dropped.

2 Select in the Service Filtering Mode field the filter criteria: VID only, PCP only, VID and PCP.

3 Press the Filtering Scheme button and select the services to be dropped. The fol-lowing screen opens.

Figure 37 Filtering Scheme

4 Select a row and click on Modify. The following screen opens.


55


Figure 38 Filtering Scheme

5 Change the Filtering Mode previously assigned.

6 Click on OK.



4) Header Compression

t New packet networks are going towards very high bit rates, e.g. 1 Gbit/s and above, whereas the capacity over the FlexiPacket MultiRadio is limited to few hundreds Mbit/s. In many services and applications, payload of the packets is almost of the same size or even smaller than the header. Over the end-to-end connection, comprised of multiple hops, these protocol headers are extremely important but over just one link (hop-to-hop) these headers serve no useful purpose. It is possible to compress those headers, pro-viding in many cases significant savings, and thus save the bandwidth and use the radio resource efficiently. Header compression also provides other important benefits, such as reduction in packet loss and improved interactive response time.

In brief, header compression is the process of compressing excess protocol headers before transmitting them on a link and uncompressing them to their original state on reception at the other end of the link. It is possible to compress the protocol headers due to the redundancy in header fields of the same packet as well as consecutive packets of the same packet stream.

t FlexiPacket MultiRadio proprietary Header Compression Service is based on the concept of compression rules associated to a specific traffic service. Each compres-sion rule is unambiguously defined and identifies the amount of bytes that can be removed from the packet. Up to 1024 compression rules can be defined; some rules are predefined (up to 511) and ready to be selected, while the others will be defined, on field, by the operator.

At the same time, the traffic service must be identified by means of MAC addresses or VLAN ID and/or VLAN priority, when the frames are VLAN tagged. Up to 64 traffic services can be defined simultaneously.

When MAC Address criterion has been enabled, the traffic service can be identified according to the following criteria:

• MAC Destination Address only • MAC Source Address only • Both MAC Addresses

When MAC Destination Address only is selected the user can enter the MAC Desti-nation Address that will be compressed, irrespective of the MAC Source Address value.

When MAC Source Address only is selected the user can enter the MAC Source Address that will be compressed, irrespective of the MAC Destination Address value.

When Both Addresses is selected the user can enter both MAC Destination Address and MAC Source Address that will be compressed.

When VLAN criterion has been enabled, the traffic service can be identified according to the following criteria:

• VLAN ID (VID) only • VLAN Priority (Priority Code Point - PCP) only • A combination of VID and PCP

When VID only is selected the user can enter the list of VIDs that will be compressed, irrespective of the PCP value.

When PCP only is selected the user can enter the list of PCPs that will be compressed, irrespective of the VID value.


57


When VID and PCP is chosen, the user can enter the couples of VIDs and PCP values that will be compressed. In this modality, it is possible to add or remove specific couples of VIDs and PCPs from the traffic service data base at any time.

Figure 39 Traffic Service configuration table

At any time the user can configure, enable, and disable whatever traffic service definition rule. It shall be also possible to retrieve the current configuration of the defined traffic services, even when the compression is disabled. All the configurations are stored in a permanent storage device.

Compresion rulesUp to 1024 compression rules are available. Some rules are predefined and ready to be selected, while others will be defined, on field, by the operator. Each compression rule must identify the amount of byte that can be removed from the packet.

The Header compression rules are identified according to the following criteria:

• Predefined (up to 512 rules - numbered from 0 to 511) • User Defined (up to 512 rules - numbered from 512 to 1023)

In both cases a list containing the indication of every byte that must be suppressed are provided. Only the first 128 bytes starting from MAC destination address can be sup-pressed.

When header compression rules have been identified and at least one header compres-sion rule has been enabled, it is possible to define the Header Compression Service configuration table.

At any time the user can configure, enable, and disable the functionality of service based header compression. It is also possible to retrieve the current configuration of the defined services, even when the compression is disabled. All the configurations are stored in a permanent storage device.

Each Header Compression Service is compound of one traffic service together with a series of 8 compression rules.

The following objects are provided for configuration:



• Header Compression Service: it identifies unambiguously the Header Compres-sion Service.

• Service Enable: it enables the Header Compression Service. • Traffic Service: it identifies unambiguously the traffic service involved in the Header

Compression Service • Associated compression rules: it represents a list of 8 compression rules that

must be applied to the identified traffic service. The rules can be both Predefined and User defined.

Figure 40 Header Compression Service configuration table

Procedure to set the Header Compression.

t First the Header Compression rules must be configured and then to each Ethernet service (if required) a specific rules must be associated.

A) Header Compression rulesThe Header Compression rules allow to define which bytes have to be compressed over the radio link

• The user can select a set of predefined rules for the most common services (CESoP, SAToP, etc.)

• The user can create a personalized HC rule by selecting which bytes to be com-pressed

Up to the first 128 byte of the packet header can be compressed.


59


Steps

1 Click on the HC rules button in the Header Compression area. The following screen opens.

Figure 41 HC rules

2 Select the rules to be modified by displaying the range from 513 up to 1024 in the Show rules field in the bottom.

3 Click on Modify.

This window allows to configure a new personalized rule. A rule is characterized by an identification name and the list of bytes starting from the first byte of the Ethernet frame (Destination Address) which have to be compressed.

4 Enter the Name of the rule.

5 Tick the Enable check box.



6 Tick the check boxes of the bytes to be cancelled in the Rule List area (from byte#1 to byte#128).

B) Rules association to a specific Ethernet ServiceThe Header Compression classification criteria allow to classify the incoming traffic as belonging to a specific flow to be compressed.

Each compressed flow is identified by two-byte compression header.

The compression produces effects if the number of suppressed bytes is greater than 2.

Steps

1 Click on the HC table button.

The HC Table lists all the packet flows subject to compression. By means of the Add button it is possible to configure a new compressed flow.

2 Click on Add. The Header Compression Add dialog box opens.


61


3 Tick the Service Enable check box.

4 Enter the service description.

5 Select the Mapping Criteria. The following criteria are available:

• Destination MAC address • Source MAC address • Source and Destination MAC address • VID only • PCP only • VID and PCP

6 Enter a specific MAC address or VLAN ID or PCP or VLAN ID+PCP according to the Mapping criterion selected in step 5.

7 In the Rule# area select the rule to be associated (multiple selection can be done).

8 Click on OK.



5) Priority Settings

Figure 42 Port Configuration area configuration

• Enable the suitable settings (multiple selection can be done) (VLAN ID/802.1p/IPv4/IPv6/L2-L3 address criteria/MPLS label/Ether Type) by putting a check mark in the relevant check box.The first matching is done with VLAN ID (if enabled), the second one with 802.1p (if enabled) and so on. The last matching is with Ether Type (if enabled).

• According to the enabled setting click on the relevant button.

VLAN Priority Settings

t In the VLAN Id Priority table are listed all the VLAN IDs that have been inserted previ-ously in the VLAN Table in the VLAN Support area.

Steps:

1 Click on VLAN Priority Settings. The next screen opens. The default priority is “No priority”, corresponding to queue 0.

Figure 43 VLAN priority table


63


2 Select the VLAN Id to be modified and click on Modify (VLAN ID 77 in the example).

Figure 44 VLAN priority modify

3 Change the Priority (from 0 to 7) and click OK.

Figure 45 Modified VLAN priority table

4 Repeat steps 2 to 3 to modify the priority of the other VLAN Ids.



802.1p Priority settings

Steps:

1 Click on 802.1p button. The next screen opens. The default priority is 0 (lowest pri-ority)

Figure 46 802.1p Priority Table

2 Click on Modify.

3 Select for each Tag the Priority (from 0 to 7) to be modified and click on OK.

Figure 47 802.1p priority table modify


65


IPv4/IPv6 Priority settingsSteps:

1 Click on IPv4/IPv6 button. The next screen opens. The default priority is 0 (lowest priority).

Figure 48 Diffserv priority table

2 Select one row and click on Modify.

3 Modify the value (from 0 to 7) and click on OK.

Figure 49 Diffserv priority modify

4 Repeat the previous steps to modify the other priorities.



L2/L3 address criteriaSteps:

1 Click on L2/L3 address criteria button. The next screen opens.

Figure 50 L2/L3 address criteria

2 Click on Add.

3 Enter the Address type, the address and the relevant priority (from 0 to 7) and click on OK.

Figure 51 L2/L3 address criteria add

t Different Address types can be selected:

• Destination MAC address • Source MAC address • Destination IPv4 address • Source IPv4 address • Destination IPv6 address • Source IPv6 address

t MAC address is the L2 address.

IPv4 or IPv6 is the L3 address.


67


MPLS labelSteps:

1 Click on MPLS label button. The next screen opens. The default priority is 0 (lowest priority). The MPLS label is a combination of 3 bits, called “Exp Bits” (from 0 to 7).

Figure 52 MPLS label table

2 Select the row relevant to the MPLS label to be managed, tick on the Enable check box and click on Modify.

3 Modify the value (from 0 to 7) and click on OK.

Figure 53 MPLS label modify



Ether typeSteps:

1 Click on Ether Type button. The next screen opens.

Figure 54 Ether Type table

2 Click on Add.

3 Enter the Ether Type value, the Priority (from 0 to 7) and click on OK.

Figure 55 Ether Type add


69


6) Scheduling area configuration

Figure 56 Scheduling area configuration

Steps

1 Press the Scheduling button. The following screen opens.

Figure 57 Scheduling dialog box

2 By clicking on the Strict priority queues field in the General Settings area one of the following selections can be done for the Strict Priority.



t Queue 7 is the highest priority queue.

Queue 0 is the lowest priority queue.

t The queues, not involved in the Strict Priority algorithm, will be available for the WFQ algorithm.

For each WFQ queue assign the relevant weight by selecting the queue on the Queues list on the left-side and by inserting the weight in the WFQ weight field.

t The Rate limiting and Exceed action check boxes are not implemented in the curent release.

t The Random Early Detection (RED) feature has not been implemented in the current release.

7) Jumbo frame management

Figure 58 Jumbo frame management

Steps

1 Enable, if required, the management of the Jumbo frames (up to 10240 bytes).


71


6.4 Radio - BB/ModemFrom the left-hand side tree select Radio > BB-Modem.

Figure 59 BB/Modem Configuration

To change the parameters click on the Modify button. The following screen opens.

Steps

1 Select the Standard mode according to the market: etsi or ansi.

2 Select the Channel bandwidth.



3 Select the Profile Criteria: "Standard profile" or "High Performance profile". In the latter case the LDPC (more robust) coding is used.

4 Select the ACM TX: adaptive or static.

5 If the Static Modulation has to be used, enter in the relevant Tx Static Profile field the Modulation scheme to be used:

• QPSK • 16 QAM • 32 QAM • 64 QAM • 128 QAM • 256 QAM

t In Rx side the Modulation scheme automatically changes according to the Modula-tion scheme used in Tx side in the remote equipment.

6 If the Adaptive Modulation has to be used, enter the Lowest Tx Profile and the Highest Tx Profile.

t In Rx side the Modulation scheme automatically changes according to the Modula-tion scheme used in Tx side in the remote equipment.

7 Click OK to confirm the new parameters.

t By clicking on Profiles Details the following read-only screen opens.

Figure 60 Profiles Details

This screen shows the modulation schemes selected for the Adaptive Modulation, the max. Tx power for each modulation scheme and the switching thresholds (based on the S/MSE) from one modulation scheme to another one.


73


6.5 Radio - RFFrom the left-hand side tree select Radio > RF.

Figure 61 RF Configuration (ATPC)

Figure 62 RF Configuration (RTPC)



Steps

1 Click on Service State field. The Input dialog box appears.

Figure 63 BB/Modem Configuration: service state selection

2 Tick up and click on OK.

3 Enter the Tx RF frequency (in kHz) in the Tx Value field or Rx RF frequency (in kHz) in the Rx Value field (250 kHz steps). The dual RF frequency (Rx or Tx) is automat-ically calculated according to the selected frequency and the frequency shifter.

Figure 64 Tx RF frequency

4 If the ATPC is not used, enter the Tx Power value (RTPC).

Figure 65 RTPC

5 Enable the ATPC, if required, and enter the relevant parameters.

Figure 66 ATPC


75


6 The Continuous Wave Test is only for maintenance and test purposes. With this test the RF Transmitter emits an unmodulated carrier.

Figure 67 Continuous Wave Test

7 By clicking on HW Parameters button the following screen opens.

Figure 68 HW Inventory

This screen is read-only and shows the remote inventory of the FlexiPacket Mul-tiRadio.



6.6 Station A correct operation checkCheck the correct operation of the station by using the RF loopback.

t The loopback cannot be performed in 1+1 configuration.

Steps

• When the time for the RF loopback is over, click on the pushbutton View Result. • File TestLoopResult.xml opens. If during the loopback no error occurred, station

A works properly: In Bad Octets counter must be zero, In Octets counter must be equal to the Out Octets counter and both must be in the In Good Octets counter.

t The report file can be exported by clicking on the button Export XML.


77


6.7 IP address assignmentFlexiPacket MultiRadio has two IP addresses.

t The IP default address is always available. By using this address the NE is always reachable from the Ethernet interface (not from the Radio side).

t The Management VLAN is used only with the IP public address.

FlexiPacket MultiRadio supports a DHCP client in order to automatically retrieve IPpub-lic, subnet mask and default gateway parameter settings. DHCP client can be enabled / disabled; DHCP client is default-set to enabled.

It is assumed that only one DHCP server is present in the LAN, so that the response to the broadcast DHCP discovery is unique.

With DHCP client disabled, the IP address, subnet mask and default gateway can be manually configured by using the Admin user privileges.

IP Reference Scenario

IPpublic Used for remote or local management operations

IPdefault Used to access the ODU locally without knowing the IPpublic or IPpri-vate. It is a fixed address.

Table 14 IP addressing scheme



Steps:

1 From the left-side tree select Status and Config > Equipment > Networking.

2 Select the IP Settings tab-panel.

Figure 69 Networking

3 Click on IP Setting Mode field. The following Input dialog box opens.

Figure 70 IP Setting Mode

4 Tick check box Obtain an IP address Automatically, if the DHCP Client has to be used, otherwise tick check box Use the Manual IP Settings and click on OK.

Configurable parameters Default configuration

DHCP enabling Enabled

IPpublic address 0.0.0.0

Subnet mask 255.255.255.0

Default gateway 0.0.0.0

Secondary gateway 0.0.0.0

Table 15 Available parameters for DHCP


79


5 In the Manual IP Settings area click on Modify. In the Input dialog box enter the IP parameters according to the DCN plan.

6 If the IP Setting Mode is Obtain an IP address automatically, the DHCP Setting area is available. In this area set:

• Discovery Message IntervalTime interval (ms) for discovery messages issued before the client received the first reply. Range is 0 - 2,147,483,647 and default value is 125.

• Lease TimeRequested lease time option to be used with DHCP Discover or DHCP Request messages. Range is 0 - 2,147,483,647 and default value is 24.

• DHCP RestartDHCP protocol restart command. Any value set greater than 0 causes the IP address to be renewed.

7 Enter the parameters of the default Gateway by clicking on Modify. The default Gateway could be a Router, if FlexiPacket MultiRadio is connected to a router.

8 Enter the IP address of the Secondary default Gateway, if any.

9 In the Management VLAN Management tab-panel enter the VLAN id to be used for the “In Band” management and the relevant Priority (VPRI from 0 to 7).



10 In the LLDP tab-panel you can activate (if required) the Physical Topology Discov-ery.

11 The LLDP protocol (Link Layer Discovery Protocol) can be enabled on the Giga Ethernet port and on the Radio port to discover the neighbouring NEs connected to these ports.

The enabling can be:

• txOnly: the information is only transmitted to the neighbour, but nothing is read in Rx side;

• rxOnly: the information is received from the neighbour, but nothing is transmit-ted;

• txAndrx: the information is send and received.

12 In the Tx Message Rate and Time To Leave Multiplier fields keep the default values.

13 Press LLDP Information button to show the list of the neighbouring NEs.


81


14 Press the Static Information button to insert manually the neighbour NEs which do not have the LLDP feature. Click on Add and insert the NE parameters.

t The LLDP protocol is used to allow the NMS to build the physical topology of the network under its supervision. In order to obtain a complete picture of the network controlled, the underlying assumption is that all the Network Elements in the con-trolled network support the LLDP protocol. An example is shown in figure below, where the NMS is able to build a draw of the physical connections between the Network Elements by inspecting the information stored in the MIBs.

Figure 71 Physical Topology discovery via LLDP



15 In case of configuration with 2 FlexiPacket MultiRadios with single cable, assign the IP address of the colocated ODU in menu Operation, Administration and Main-tenance >tab-panel Colocated ODU Config.


83


6.8 Date & Time configurationThe date and time have a particular importance during the execution and the analysis of the measurements and recordings on the equipment.

The date and time configuration can now be executed only in case of login with admin-istrator privileges and of proprietary synchronization.

6.8.1 Manual setting of date and time

Steps

1 Select menu Status & Config > Data & Time.

2 In the “Manual Settings” area press Host Time button; the PC date and time will synchronize the FlexiPacket MultiRadio.

Figure 72 Manual setting of date and time

3 As an alternative in the “Manual Setting” area the time can be manually selected.

6.8.2 Synchronization of the NE via Time Server SNTP (Time server Setting)It is possible to synchronize the clock of the NE to the time reference provided by a SNTP Time Server reachable via IP network.

The Time Server distributes the GMT time, which can be adjusted depending on its own time zone and of the daylight saving time.

Selecting Time Server Configuration command in the Time Settings menu opens the Time Server IP Address window , where it is possible to enable and configure the SNTP synchronization

The default value of the address IP of the Time Server (0.0.0.0) causes the disabling of the SNTP synchronization.

Figure 73 Synchronization of NE via Time Server SNTP

Steps

1 Insert the IP address of the SNTP Time Server in the IP address field.



2 Select the offset to correct the GMT time in the Time Zone field. The possible offset values go from GMT-12 to GMT+13.

3 To correct the time reference of the SNTP synchronization (addition of the GMT time received by the Time Server and the possible correction due to the time zone) according to the daylight saving time, select the Daylight saving time check-box.

6.9 Before leaving terminal station AIn order to prepare the system configuration for the antenna adjustment phase (align-ment) set the Tx Power data with the ATPC Disable mode with the Maximum power transmission and disable the Adaptive Modulation (if configured).

Disconnect the PC and move to the opposite station.

t After the antenna alignment reconfigure the ATPC and the Adaptive Modulation as the project requirements.

6.9.1 Alarms status checkAt the end of the configuration of the parameters and before to leave the terminal station verify that no particular alarms are active except the Radio (with related indication) and the alarm related to the Ethernet interface.

Selecting the Alarms menu the following screen opens.

Figure 74 Alarms menu


85

Commission Equipment configuration (station B)

7 Equipment configuration (station B)Repeat all the steps done for station A in section 6.


CommissionAntenna alignment

8 Antenna alignmentBefore starting with the alignment phase, verify the ATPC and the Adaptive Modula-tion in both terminal stations are disabled.

t After the antenna alignment reconfigure the ATPC and the Adaptive Modulation as the project requirements.

Verify also that the Transmission power is configured with the maximum output power.

The Nominal setting values depend on the frequency range. Apply this setting in both stations.

By properly using the safety device and observing the security rules, climb near the FlexiPacket MultiRadio and connect the Multimeter on the main FlexiPacket MultiRadio to the BNC connector.

t It is not compulsory but for antenna pointing it is suggested to use an analog multimeter.

The multimeter must be connected in DC voltage measure.

Start with the antenna adjustment following the indication reported in the installation manual of the antenna supplier.

t Take care that the antennas alignment procedure is not a single station activities, but require a synchronizing tasks between Installation Team on both terminal stations.The alignment operations must be possible only after that all above system configuration and controlling are done also on the remote terminal station. For the mechanical antennas adjustment points, refer to the installation documentation supplied by the antennas sup-plier.

A general alignment procedure is available on request.

After the alignment verify on both terminal station and for all RF channels, that the Received power level agrees with the project specification. (See the RSL value on the Status Bar of the Web Interface).

t The update and refresh time of RSL value on Status Bar are slow, don't use only this Item for the antennas adjustment phase, but it is suggested to use the multimeter on BNC ODU port and refer to the Maximal Voltage value received. Afterwards read the RSL value.

t For RSL, consider a Prx read value tolerance of about ±3 dB.


87

Commission Antenna alignment

Figure 75 Example BNC Connection on FlexiPacket MultiRadio

The alignment steps and antennas pointing mode depend on the system type and project specifications.

See the examples below.

t In 1+1 configuration it is reccommended to force the active channel on the ODU with the Main role in both Sites and get the relevant RSL reference values (only for antenna adjustment operations) from the Main ODUs. This operation must be done because typ-ically the 1+1 hot standby system uses an unbalanced coupler and RSL on the protec-tion ODU should be lower than the main ODU.

After the antennas adjustment operation to be reconfigure all in automatically mode.

Figure 76 Standard antenna pointing for 1 antenna system


CommissionAntenna alignment

Figure 77 Antennas aim for 2 antenna system in Hot Stand By configuration

Figure 78 Antennas aim for 2 antenna system in Frequency Diversity configuration


89

Commission System commissioning and testing

9 System commissioning and testing

9.1 Link connectivity check (using the remote loopback)

Figure 79 Link connectivity test

t In case of 1+1 configuration no loopback is available.

To check the link connectivity ping the remote station.

Steps

1 Connect the LCT to Station A, as shown in Figure 79.

t The complete sequence to create a loopback is shown in para. 6.6 on page 76.


CommissionSystem commissioning and testing

2 Enter Station B: Create the following loopback:

• Interface: GbE Port • Test Type: Link Test Remote Payload (RL3) • Time Out: more than 60 sec.

t The complete sequence to create a loopback is shown in para. 6.6 on page 76.

3 Enter Station A: Create the following loopback:

• Interface: Micro Port • Test Type: Link Test Starting Point (LsRL3) • Time Out: 60 sec.

4 Enter Station B: Activate the loop

5 Enter Station A: Activate the loop

6 During the loop activation time the NE is not reachable.

7 When the time is over click on pushbutton View Result. File TestLoopResult.xml opens.

8 If during the loopback no error occurred, the link works properly: In Bad Octets counter must be zero, In Octets counter must be equal to the Out Octets counter and both must be in the In Good Octets counter.


91

Commission System commissioning and testing

9.2 Interferences evaluation checkAfter the frequency setting and power setting, before starting with the Alignment phase or remote station configuration phase (considering the remote station in Power OFF condition), check the Prx value to evaluate the presence of any interfering signal from other MW Links.

The operator can measure the value of the power received by the FlexiPacket MultiRa-dio installed in the system by means of the Measurements > RF & Other menu, where the measurement of the reception power is displayed.

Check that all the Rx power values are less than -94 dBm (or in any case with the appro-priate fade margin written in the RF Network Plan).

Figure 80 Measurements menu

If the link is already operational (but not in service), it is possible to set the Remote Tx amplifier to OFF (squelching activation) for a settable timing (the time necessary to read a local Rx Power, about 60 second). This command is also suitable, if any operator is present in the remote station.

By using the WebLCT enter the remote NE and activate the Timed Tx Squelch as shown in the next figure.

Insert an appropriate Squelch Time (example 60 seconds) and activate the command.

On the local station check the Prx value.


CommissionSystem commissioning and testing

Steps

Figure 81 Remote squelch command

flexipacket multi radio 2.4 commission

Documents