ALCplus2 Plus2e - User Manual PDF
ALCplus2 Plus2e - User Manual PDF
User manual
MN.00224.E - 018
The information contained in this handbook is subject to change without notice.
Property of Siae Microelettronica S.p.A. All rights reserved according to the law and according to the inter-
national regulations. No part of this document may be reproduced or transmitted in any form or by any
means, electronic or mechanical, without written permission from Siae Microelettronica S.p.A.
Unless otherwise specified, reference to a Company, name, data and address produced on the screen dis-
played is purely indicative aiming at illustrating the use of the product.
MS-DOS®, MS Windows® are trademarks of Microsoft Corporation.
HP®, HP OpenView NNM and HP–UX are Hewlett Packard Company registered trademarks.
UNIX is a UNIX System Laboratories registered trademark.
Oracle® is a Oracle Corporation registered trademark.
Linux term is a trademark registered by Linus Torvalds, the original author of the Linux operating system.
Linux is freely distributed according the GNU General Public License (GPL).
Other products cited here in are constructor registered trademarks.
Contents
Section 1.
USER GUIDE 13
Section 2.
DESCRIPTIONS AND SPECIFICATION 21
4 ABBREVIATION LIST................................................................................................21
4.1 ABBREVIATION LIST .........................................................................................21
MN.00224.E - 018 1
5.8 MANAGEMENT ..................................................................................................28
5.8.1 Hardware platform ..................................................................................28
5.8.2 Management ports ..................................................................................28
5.8.2.1 MNGT/1 and MNGT/2 ................................................................29
5.8.2.2 RS232 ....................................................................................29
5.8.2.3 LCT USB .................................................................................29
5.8.3 Protocols ...............................................................................................29
2 MN.00224.E - 018
7.1.4.3 Adaptive code modulation .........................................................52
7.1.4.4 Power supply ...........................................................................54
7.1.4.5 Telemetry IDU/ODU..................................................................54
7.2 LOOPS ............................................................................................................54
7.2.1 Tributary ...............................................................................................54
7.2.2 IDU loop ................................................................................................55
MN.00224.E - 018 3
9.6.7 4X(1+0) with XPIC, circulator, two CCDP channels ......................................87
9.6.8 8X(1+0) with XPIC and multicirculator .......................................................88
9.6.9 MULTICIRCULATOR FREQUENCY RESTRICTIONS .........................................89
9.7 SYNCHRONIZATION ..........................................................................................91
9.8 ALCPLUS2E NODE.............................................................................................92
9.8.1 Expansion from 2 to 3 IDUs......................................................................93
9.8.2 Reduction from 3 to 2 IDUs ......................................................................94
9.9 SWITCH FOR ETHERNET PORTS ..........................................................................94
9.10 LAG - LINK AGGREGATION ................................................................................99
9.10.1 Line Trunking .........................................................................................99
9.10.2 Radio Link Trunking .............................................................................. 100
9.11 LINE PROTECTION THROUGH DISTRIBUTED ELP ................................................. 101
9.12 ETHERNET OAM (OPERATION ADMINISTRATION AND MAINTENANCE) ................... 101
9.12.1 Service Layer OAM ................................................................................ 101
9.12.2 OAM Example with ALCplus2e................................................................. 103
9.13 ALCPLUS2E FIRMWARE UPDATES...................................................................... 103
9.13.1 Firmware release 1.3.1 .......................................................................... 103
9.13.2 Firmware release 1.4.0 .......................................................................... 105
9.13.3 Firmware release 1.5.0 .......................................................................... 106
9.13.4 Firmware release 1.5.1 .......................................................................... 106
9.13.5 Firmware release 1.6.0 .......................................................................... 106
9.13.6 Firmware release 1.7.0 .......................................................................... 108
9.13.7 Firmware release 1.7.2 .......................................................................... 109
9.14 FIRMWARE UPDATES FOR ALCPLUS2E 1+1 XPIC ................................................. 110
9.14.1 Firmware release 1.0.1 .......................................................................... 110
9.14.2 Firmware release 1.2.0 .......................................................................... 110
9.14.3 Firmware release 1.2.2 .......................................................................... 111
9.14.4 Firmware release 1.2.3 .......................................................................... 111
9.14.5 Firmware release 1.3.0 .......................................................................... 111
Section 3.
INSTALLATION 125
4 MN.00224.E - 018
11.2 GENERAL....................................................................................................... 126
11.3 MECHANICAL INSTALLATION............................................................................ 126
11.3.1 IDU..................................................................................................... 126
11.3.2 IDU installation..................................................................................... 126
11.4 ELECTRICAL WIRING....................................................................................... 126
11.5 OPTICAL CONNECTORS ................................................................................... 128
11.6 CONNECTIONS TO THE SUPPLY MAINS .............................................................. 128
11.7 IDU-ODU INTERCONNECTION CABLE................................................................. 128
11.7.1 Electrical characteristics......................................................................... 128
11.7.2 Connectors .......................................................................................... 128
11.7.3 Max length........................................................................................... 128
11.7.4 Suggested cable ................................................................................... 128
11.8 GROUNDING CONNECTION .............................................................................. 129
11.9 IDU-ODU CABLE GROUNDING KIT INSTALLATION ............................................... 129
11.9.1 Grounding kit K09283F (for RG8 or 1/8” cable) ......................................... 129
11.9.2 Grounding kit ICD00072F (for any cable with shield) ................................. 130
11.10 SURGE AND LIGHTNING PROTECTION ............................................................... 131
14 ALCplus2E CONNECTORS........................................................................................142
14.1 IDU FRONT PANEL .......................................................................................... 142
14.2 ALCPLUS2E 1+0 (GAI0178), 2+0/1+1 (GAI0175), 2+0/XPIC (GAI0172) ................ 142
14.3 ALCPLUS2E 18E1 2XSTM1 NODAL (GAI0176), 2+0/1+1 (GAI0173),
2+0/XPIC (GAI0170) ...................................................................................... 143
14.4 ALCPLUS2E 34E1 2XSTM1 1+0 (GAI0177), 2+0/1+1 (GAI0174),
2+0/XPIC (GAI 0171) ..................................................................................... 144
16 INSTALLATION ONTO THE POLE OF THE ODU WITH SEPARATED ANTENNA ...........146
16.1 INSTALLATION KIT ......................................................................................... 146
16.2 REQUIRED TOOLS FOR MOUNTING (NOT SUPPLIED) ........................................... 147
16.3 INSTALLATION PROCEDURE ............................................................................. 147
MN.00224.E - 018 5
16.4 GROUNDING .................................................................................................. 149
18 INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED ANTENNA .........177
18.1 FOREWORD ................................................................................................... 177
18.2 INSTALLATION KIT ......................................................................................... 177
18.3 REQUIRED TOOLS FOR MOUNTING (NOT SUPPLIED) ........................................... 178
18.4 INSTALLATION PROCEDURE ............................................................................. 178
18.4.1 Installation onto the pole of the support system and the antenna ................ 178
18.4.2 Installation of ODU................................................................................ 179
18.4.3 ODU installation.................................................................................... 180
18.5 ANTENNA AIMING........................................................................................... 180
18.6 COMPATIBILITY .............................................................................................. 180
18.7 GROUNDING .................................................................................................. 181
6 MN.00224.E - 018
20.7.1 Installation of the centring rings over the OMT .......................................... 213
20.7.2 Installation of the fast lock 1+0 ODU support ........................................... 213
20.7.3 Installation over the pole of the assembled structure: antenna, OMT and
pole support system .............................................................................. 213
20.7.4 Installation of the fast lock ODUs over the OMT......................................... 214
20.7.5 Antenna aiming .................................................................................... 214
20.7.6 ODU grounding..................................................................................... 214
21 INSTALLATION ONTO THE POLE OF THE ODU WITH RFS INTEGRATED ANTENNA...218
21.1 FOREWORD ................................................................................................... 218
21.2 INSTALLATION KIT ......................................................................................... 218
21.3 REQUIRED TOOLS FOR MOUNTING (NOT SUPPLIED) ........................................... 219
21.4 INSTALLATION PROCEDURE ............................................................................. 219
21.5 1+0 MOUNTING PROCEDURES ......................................................................... 220
21.5.1 Setting antenna polarization ................................................................... 220
21.5.2 Installation of the centring ring on the antenna ......................................... 220
21.5.3 Installation of 1+0 ODU support ............................................................. 220
21.5.4 Installation onto the pole of the assembled structure ................................. 220
21.5.5 Installation of ODU (on 1+0 support)....................................................... 220
21.5.6 Antenna aiming .................................................................................... 221
21.5.7 ODU grounding..................................................................................... 221
21.6 1+1 MOUNTING PROCEDURES ......................................................................... 221
21.6.1 Installation of Hybrid ............................................................................. 221
21.6.2 Installation of ODUs (on hybrid for 1+1 version) ....................................... 222
22 INSTALLATION ONTO THE POLE OF ODU ASN/ASNK WITH STANDARD LOCK ........233
22.1 ODU COUPLING KIT ........................................................................................ 233
22.1.1 ODU AS ............................................................................................... 233
22.1.2 ODU ASN/ASNK .................................................................................... 233
22.1.2.1 Fast lock coupling kit .............................................................. 233
22.1.2.2 Standard coupling kit .............................................................. 233
22.2 INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED ANTENNA ........... 234
22.2.1 ODU AS and ODU ASN/ASNK (Fast Lock) ................................................. 234
22.2.2 ODU ASN/ASNK (Standard Lock)............................................................. 234
22.2.2.1 1+0 ODU .............................................................................. 234
22.2.2.2 1+1 ODU .............................................................................. 235
22.3 INSTALLATION ONTO THE POLE OF THE ODU WITH SEPARATED ANTENNA............. 236
22.3.1 ODU AS, ASN and ASNK (Fast Lock) ........................................................ 236
22.3.2 ODU ASN and ASNK (Standard Lock) ....................................................... 236
22.3.2.1 1+0 ODU .............................................................................. 237
22.3.2.2 1+1 ODU .............................................................................. 237
22.3.2.3 Waveguide towards the antenna............................................... 239
23 INSTALLATION ONTO THE POLE OF 8+0 ODU WITH SEPARATED ANTENNA ...........247
23.1 GENERALS ..................................................................................................... 247
23.2 N+0.............................................................................................................. 247
MN.00224.E - 018 7
Section 4.
LINE-UP 259
8 MN.00224.E - 018
29 EXAMPLE OF ALCplus2 NODE EXPANSION..............................................................316
29.1 INTRODUCTION.............................................................................................. 316
29.2 PRECONDITIONS ............................................................................................ 316
29.3 NBUS AND INTRA-NODE GE CABLING RULES ..................................................... 318
29.4 NODE EXPANSION FROM N TO N+K ELEMENTS................................................... 319
29.4.1 Step 1 ................................................................................................. 319
29.4.2 Step 2 ................................................................................................. 319
29.4.3 Step 3 (traffic affecting)......................................................................... 319
29.4.4 Step 4 ................................................................................................. 320
29.4.5 Step 5 (traffic affecting)......................................................................... 320
29.5 NODE REDUCTION FROM N+K TO N ELEMENTS .................................................. 321
29.5.1 Step 1 (traffic affecting)......................................................................... 321
29.5.2 Step 2 ................................................................................................. 321
29.5.3 Step 3 (traffic affecting)......................................................................... 321
29.5.4 Step 4 ................................................................................................. 321
Section 5.
COMMISSIONING REPORT 339
MN.00224.E - 018 9
36.1.4 Network addresses (DCN) ...................................................................... 341
36.2 SITE INSPECTION ........................................................................................... 343
36.3 COMMISSIONING CHECKS ............................................................................... 344
36.4 COMMISSIONING MEASURES ........................................................................... 347
36.4.1 Tributary connections stability ................................................................ 347
36.4.2 Link Fade Margin .................................................................................. 348
36.4.3 Loops and maintenance ......................................................................... 349
36.5 ETHERNET TEST ............................................................................................. 351
36.5.1 Link Residual BER test ........................................................................... 353
36.6 FINAL CHECK LIST.......................................................................................... 354
36.7 FINAL REPORT ............................................................................................... 355
36.7.1 Link activation date ............................................................................... 355
36.7.2 Certificate ............................................................................................ 356
Section 6.
MAINTENANCE 357
10 MN.00224.E - 018
Section 7.
PROGRAMMING AND SUPERVISION 375
Section 8.
COMPOSITION 379
Section 9.
LISTS AND SERVICES 413
45 ASSISTANCE SERVICE............................................................................................423
MN.00224.E - 018 11
12 MN.00224.E - 018
Section 1.
USER GUIDE
1 DECLARATION OF CONFORMITY
complies with the essential requirements of article 3 of the R&TTE Directive (1999/5/EC) and therefore is
marked CE.
- EN 301 489–4 V.1.3.1 (2002–8): “Electromagnetic compatibility and radio spectrum Matters (ERM);
Electromagnetic Compatibility (EMC) standard for radio equipment and services; Part 4. Specific con-
ditions for fixed radio links and ancillary equipment and services”
- ETSI EN 301 751 V.1.1. (2002–12): “Fixed Radio Systems; Point–to point equipment and antennas;
generic harmonized standard for point–to–point digital fixed radio systems and antennas covering the
essential requirements under article 3.2 of the 1999/5/EC Directive”.
MN.00224.E - 018 13
2 FIRST AID FOR ELECTRICAL SHOCK AND SAFETY
RULES
Do not touch the bare hands until the circuit has been opened. pen the circuit by switching off the line
switches. If that is not possible protect yourself with dry material and free the patient from the con-
ductor.
It is important to start mouth respiration at once and to call a doctor immediately. suggested procedure
for mouth to mouth respiration method is described in the Tab.1.
This treatment should be used after the patient has regained consciousness. It can also be employed while
artificial respiration is being applied (in this case there should be at least two persons present).
Warning
14 MN.00224.E - 018
Tab.1 - Artificial respiration
Lay the patient on his back with his arms parallel to the body.
If the patient is laying on an inclined plane, make sure that his
1 stomach is slightly lower than his chest. Open the patients
mouth and check that there is no foreign matter in mouth (den-
tures, chewing gum, etc.).
Kneel beside the patient level with his head. Put an hand under
the patient’s head and one under his neck.
Shift the hand from the patient’s neck to his chin and his
mouth, the index along his jawbone, and keep the other fingers
closed together.
With your thumb between the patient’s chin and mouth keep
his lips together and blow into his nasal cavities
When the equipment units are provided with the plate, shown in Fig.1, it means that they contain compo-
nents electrostatic charge sensitive.
MN.00224.E - 018 15
Fig.1 - Components electrostatic charge sensitive indication
In order to prevent the units from being damaged while handling, it is advisable to wear an elasticized band
(Fig.2) around the wrist ground connected through coiled cord (Fig.3).
This device has Class I LASER modules: it is not required to have a laser warning label or other laser state-
ment (IEC 60825-1).
16 MN.00224.E - 018
2.3 CORRECT DISPOSAL OF THIS PRODUCT (WASTE ELECTRICAL &
ELECTRONIC EQUIPMENT)
(Applicable in the European Union and other European countries with separate collection systems). This
marking of Fig.4 shown on the product or its literature, indicates that it should not be disposed with other
household wastes at the end of its working life. To prevent possible harm to the environment or human
health from uncontrolled waste disposal, please separate this from other types of wastes and recycle it
responsibly to promote the sustainable reuse of material resources. Household users should contact either
the retailer where they purchased this product, or their local government office, for details of where and
how they can take this item for environmentally safe recycling. Business users should contact their supplier
and check the terms and conditions of the purchase contract. This product should not be mixed with other
commercial wastes for disposal.
CAUTION: Risk of explosion if battery is replaced by an incorrect type. Dispose of used batteries
according to law.
MN.00224.E - 018 17
3 PURPOSE AND STRUCTURE OF THE MANUAL
The purpose of this manual consists in providing the user with information which permit to operate and
maintain the ALS radio family.
Warning: This manual does not include information relevant to the SCT/LCT management program win-
dows and relevant application. They will provided by the program itself as help-on line.
The following knowledge and skills are required to operate the equipment:
• a basic understanding of microwave transmission
The manual is subdivided into sections each of them developing a specific topic entitling the section.
Each section consists of a set of chapters, enlarging the main subject master.
It provides the information about the main safety rules and expounds the purpose and the structure of the
manual.
It traces the broad line of equipment operation and lists the main technical characteristics of the whole
equipment and units it consists of.
18 MN.00224.E - 018
Section 3 – Installation
The mechanical installation procedures are herein set down as well as the user electrical connections.
Section 4 – Line–Up
Line–up procedures are described as well as checks to be carried out for the equipment correct operation.
The list of the instruments to be used and their characteristics are also set down.
This section describes how to prepare a commissioning report regarding the installation of a link
Section 6 – Maintenance
In this section a description of alarms is given in order to help operators to perform equipment mainte-
nance and troubleshooting.
The ALS radio family is programmed and supervised using different software tools. Some of them are al-
ready available, some other will be available in the future.
This section lists the tools implemented and indicates if descriptions are already available.
Each description of software tools is supplied in a separated manual.
Section 8 – Composition
Position, part numbers of the components the equipment consist of, are shown in this section.
This section contains the lists of figures and tables and the assistance service information.
MN.00224.E - 018 19
20 MN.00224.E - 018
Section 2.
DESCRIPTIONS AND
SPECIFICATION
4 ABBREVIATION LIST
- AF Assured Forwarding
- AL Access Link
- BB Baseband
- E1 2 Mbit/s
MN.00224.E - 018 21
- IDU Indoor Unit
- IF Intermediate Frequency
- LC Lucent Connector
- MA Maintenance Association
- MD Maintenance Domain
- NE Network Element
22 MN.00224.E - 018
5 SYSTEM PRESENTATION
5.1 RECOMMENDATION
• EN 300 019 environmental characteristics (Operation class 3.2 for IDU and class 4.1 for ODU; stor-
age: class 1.2; transport: class 2.3)
The ALS “plus2 family” is the new packet radio link from SIAE. These packet radio links are split mount
equipment made up of:
• an indoor unit called IDU for 19” rack mounting that interfaces tributaries and supervises the full
equipment
• an outdoor unit called ODU for pole or wall mounting with RF circuitry and antenna flange.
MN.00224.E - 018 23
5.3.1 LIM
The LIM interfaces the in (out) E1 streams and Ethernet traffic and, through a multiplexing (demultiplex-
ing) and bit insertion (bit extraction) process, supplies (receives) the aggregate signal to the modulator
(from the demodulator). In addition the LIM performs the digital processing of the QAM modulator.
Moreover the module duplicates the main signals at the Tx side and performs the changeover at the Rx
side in the 1+1 version.
5.3.2 RIM
• the IF section of the programmable modemodulator (8 available profiles: 4QAM, 4QAM strong,
8PSK, 16QAM, 32QAM, 64QAM, 128QAM, 256QAM)
• the power supply unit that processes the battery voltage to supply power to the IDU circuits and
send the battery voltage towards the ODU
• the cable interface for the bidirectional communication between IDU and ODU via interconnecting
cable
• thanks to ACM (Adaptive Code Modulation) actual modulation can be automatically changed accord-
ing to available S/N.
5.3.3 Controller
• interfaces the service signals as 1x9600 bit/s or 2x4800 bit/s, 64 kbit/s, 2 Mbit/s (details are given
in the system technical specification)
• contains the equipment software that permits to control and to manage all the equipment function-
ality through a main controller and associated peripherals distributed within IDU and ODU
• interfaces the SCT/LCT management system through Ethernet, RS232 and USB ports
• receive external alarms and route them to relay contact along with the internal alarms generated
by the equipment.
24 MN.00224.E - 018
The compact IDU are made by a single board.
The line interfaces contain the tributary connectors and, by means of processes of multiplexing/demulti-
plexing and of bit insertion/extraction, provide/receive the aggregate signal to/from the modulator/de-
modulator. The line interfaces realize the digital processing for the QAM modulator and, in 1+1
configuration, duplicate the main signals on the transmission side and execute the switch on the reception
side.
The interfaces to the ODU contain the interface of the cable for the bidirectional communication between
ODU and IDU, and implement the IF section of the mo-demodulator. The power supply units of the IDU
process the battery voltage and supply power to the circuits of IDU and ODU. The controller section of the
radio contains the interfaces of the service channels, stores the firmware of the IDU, interfaces the SIAE
management systems through dedicated supervision ports and forwards external and internal alarms to
the relay contacts.
MN.00224.E - 018 25
ALCplus2e 1+1 XPIC 4GE 2xE1 See Fig.18
The Compact IDU and EPP (Enhanced Packet Processing) are made of a single board and expansions like
34E1 2xSTM1 or 18E1 2xSTM1 NODAL.
The line interface contain the tributary connectors and, by means of processes of multiplexing/demulti-
plexing and of bit insertion/extraction, provide/receive the aggregate signal to/from the modulator/de-
modulator. The line interfaces realize the digital processing for the QAM modulator and, in 1+1
configuration, duplicate the main signals on the transmission side and execute the switch on the reception
side.
The interfaces to the ODU contain the interface of the cable for the bidirectional communication between
ODU and IDU, and implement the IF section of the mo-demodulator. The power supply units of the IDU
process the battery voltage and supply power to the circuits of IDU and ODU.
The controller section of the radio contains the interfaces to internal circuits, stores the firmware of the
IDU, interfaces the SIAE management systems through dedicated supervision ports and forwards external
and internal alarms to the relay contacts.
CCDP, with XPIC technology, in ALCplus2e IDU doubles the capacity of radio link, a clear advantage to the
network operator at the dense frequency bands.
CCDP operation provides two parallel radio streams in the same RF channel with orthogonal polarizations,
thus doubling the radio hop total capacity. Separate and independent signals are transmitted, over the
same RF channel using a single antenna with a double polarization feeder. However, despite of the orthog-
onality of the two signals, some interference between the signals almost inevitably occurs, due to imperfect
antenna isolation and channel degradation.
Each polarization demodulator path receives a large signal from the orthogonal polarization, causing cross-
polarization interference. XPIC systems cancels this interference in order to demodulate both vertical and
horizontal signal successfully. In XPIC technology, each polarization path receives both the polar and the
cross-polar interference.
In ALCplus2e XPIC, the XPIC circuitry and ACM engine gives to the network operator high capacity and
high availability.
26 MN.00224.E - 018
ALCplus2e 1+1 4GE 18E1 See Fig.18
Hw
PWE3 1+0 EPP ALCplus2e 1+0 4GE 18E1 PWE3 See Fig.15
ready
Hw
PWE3 2+0/1+1 EPP ALCplus2e 2+0/1+1 4GE 18E1 EPP PWE3 See Fig.15
ready
Hw
PWE3 2+0 EPP ALFCplus2e 2+0 XPIC 4GE 18E1 EPP PWE3 See Fig.15
ready
Hw
STM1 bulk
PWE3 1+0 EPP ALCplus2e 1+0 4GE 34E1 2xSTM1 EPP PWE3 See Fig.16
transmission
ready
Hw
STM1 bulk ALCplus2e 2+0/1+1 4GE 34E1 2xSTM1 EPP
PWE3 2+0/1+1 EPP See Fig.16
transmission PWE3
ready
Hw
STM1 bulk ALCplus2E 2+0 XPIC 4GE 34E1 2xSTM1 EPP
PWE3 2+0 EPP See Fig.16
transmission PWE3
ready
Some IDUs with updated hardware permit STM-1 bulk transmission and are PWE3 ready.
5.6 N+0
The ALCplus2e radio links can be combined together up to 4 ODU connected to a multicirculator to feed
vertical antenna port and other 4 ODU connected to another multicirculator to feed horizontal antenna port.
The result is a radio link with eight streams 8+0 with XPIC. This is at 7GHz and channel bandwidth of
28MHz. See Fig.21.
5.7 ODU
The ODU unit contains IF and RF circuits that permits to transmit and receive the signals relevant the user
traffic, the management and the telemetry and it is connected with its IDU unit through a single cable.
The ODU employs four different passband filters with the following bandwidth: 7, 14, 28 and 56 MHz. A 40
MHz bandwidth is available in some RF band only (ASN6U, ASN11). The ODU unit is available in three dif-
ferent versions: AS (only from hardware version 003), ASN and ASNK.
MN.00224.E - 018 27
The configuration of the ODU can be 1+0 or 1+1 with integrated or separated antenna. In 1+1 configura-
tion the antenna coupling is performed through a balanced or an unbalanced hybrid system (branching
unit).
For ALCplus2e 8+0 configuration is also available. This configuration is performed through a multicirculator
for each polarization.
5.8 MANAGEMENT
ALplus2/ALCplus2/ALCplus2e equipment can be locally and remotely controlled via an internal dedicated
application software called WebLCT through Internet Browser and LAN connection. A serial/USB connection
can be used through the WebLCT console, an application that can be downloaded from SIAE site (http://
www.siaemic.com)
It provides a friendly graphic interface complying with current standard use of keyboard, mouse, windows
and so on.
The hardware platform used by SCT/LCT is based on personal computer having at least following charac-
teristics:
• 1GB RAM
The SCT/LCT program is connected to the equipment via the following communication ports:
• LCT (USB)
• Embedded Overhead Channel (EOC) embedded into a 16 kbit/s or 4x16 kbit/s time slot of one of
the 2 Mbit/s tributary signals
• In band management through traffic LAN (separated VLAN required)
28 MN.00224.E - 018
5.8.2.1 MNGT/1 and MNGT/2
• Connector RJ45
5.8.2.2 RS232
• Protocol PPP
5.8.3 Protocols
SNMP along with IP or OSI protocol stacks are used to reach and manage the equipment operation.
1 2 3 ON 48V
SPEED
PoE
ACT FAIL
LINK
+
1 2 3 ON 48V
SPEED
PoE
ACT FAIL
LINK
+
SW TEST
LCT RS232 USER IN/OUT MNGT/1 MNGT/2 CH1 CH2 2Mb/s
-
2
M 3.15A
250VAC 48VDC
MNGT LAN 3 LAN 4 NURG URG
1 LCT
SW
+
MN.00224.E - 018 29
YELLOW SPEED LAN 2 LAN 4 Trib. B
2 2
M 3.15A
250VAC
MNGT 48VDC
LAN 3 LAN 4 NURG URG
1 LCT 1 2 1
SW
+
GREEN LINK LAN 1 LAN 3 Trib. A SD USER IN/OUT TEST ON -
Fig.8 - ALCplus2 1+1 and ALCplus2e E1 2+0/1+1 and ALCplus2e 2E1 XPIC 2+0
2
M 3.15A
250VAC 48VDC
MNGT LAN 3 LAN 4 NURG URG
1 LCT
SW
+
GREEN LINK LAN 1 LAN 3 Trib. A SD USER IN/OUT TEST ON -
2 2
M 3.15A
250VAC
MNGT 48VDC
LAN 3 LAN 4 NURG URG
1 LCT 1 2 1
SW
+
GREEN LINK LAN 1 LAN 3 Trib. A SD USER IN/OUT TEST ON -
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16 Trib. 17-24 Trib. 25-32
1 2
2
ON M 3.15A 48V
MNGT LAN 3 LAN 4 250V
NURG URG
1 LCT
SW
-
+
GREEN LINK LAN 1 LAN 3 Trib. A SD USER IN/OUT TEST ON
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16 Trib. 17-24 Trib. 25-32
1 2 2
2
ON M 3.15A
MNGT 48V
LAN 3 LAN 4 NURG URG 250V
1 LCT 1 2 1
SW
-
+
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16
1 2 1 2
2
M 3.15A
ON 250VAC 48VDC
MNGT NBUS
LAN 3 LAN 4 NURG URG
1 LCT
SW
+
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16
1 2 1 2
2 2
M 3.15A
ON 250VAC
MNGT NBUS 48VDC
LAN 3 LAN 4 NURG URG
1 LCT 1 2 1
SW
+
30 MN.00224.E - 018
YELLOW SPEED LAN 2 LAN 4 Trib. B
2 M 3.15A
250V 48V
MNGT LAN 3 LAN 4 NURG URG
1
LCT
R SW
+
GREEN LINK LAN 1 LAN 3 Trib. A USER IN/OUT TEST ON -
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16 Trib. 17-24 Trib. 25-32
1 2
2
ON M 3.15A 48V
MNGT LAN 3 LAN 4 250V
NURG URG
1
LCT
R SW
+
GREEN LINK LAN 1 LAN 3 Trib. A USER IN/OUT TEST ON -
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16
1 2 1 2
2 M 3.15A
ON 250V 48V
MNGT NBUS
LAN 3 LAN 4 NURG URG
1
LCT
R SW
-
+
GREEN LINK LAN 1 LAN 3 Trib. A USER IN/OUT TEST ON
2
2 M 3.15A
250V
MNGT 1 2 48V
LAN 3 LAN 4 NURG URG
1 1
LCT
R SW
+
GREEN LINK LAN 1 LAN 3 Trib. A USER IN/OUT TEST ON -
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16 Trib. 17-24 Trib. 25-32
1 2 2
2
ON M 3.15A 48V
MNGT LAN 3 LAN 4 1 2 250V
NURG URG
1 1
LCT
R SW
+
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16
1 2 1 2
2
2 M 3.15A
ON 250V
MNGT NBUS 48V
LAN 3 LAN 4 1 2 NURG URG
1 1
LCT
R SW
+
MN.00224.E - 018 31
Fig.21 - N+0
32 MN.00224.E - 018
6 TECHNICAL SPECIFICATIONS
In the following paragraphs are listed only the main characteristics of an IDU typology.
- 3 Ethernet ports: 2 RJ45, electrical (LAN1 and LAN2) and 2 SFP, optical (LAN1 and LAN3). LAN1
can be set electrical or optical.
• ALCplus2, max transmitted capacity 341 Mbit/s. Traffic options can vary depending on IDU version:
- 4 Ethernet ports: 4 RJ45, electrical (LAN1, LAN2, LAN3 and LAN4) and 2 SFP, optical (LAN3 and
LAN4). LAN3 and LAN4 can be set electrical or optical
- 2 BUS for traffic connections with other ALCplus2 IDUs (same version).
• ALCplus2e, max transmitted capacity 682 Mbit/s, 341 Mbit/s, per carrier (IDU 2+0/XPIC). Traffic
options can vary depending on IDU version:
- 2 BUS for traffic connections with other ALCplus2e IDUs (same version, TBA).
Input side
MN.00224.E - 018 33
• Rated level 2.37 Vp/75 Ohm or 3 Vp/120 Ohm
Output side
Input side
Output side
The STM1 interface can be specialised for different applications, by simply equipping the STM1 interface
with the appropriate pluggable optical or electrical transceiver. Optical interface has LC connectors. Electric
interface has 1.0/2.3 connectors. The characteristics of all the possible optical interfaces are summarised
in Tab.4.
34 MN.00224.E - 018
Tab.4 - Optical interface characteristics
Minimum
Launched Operating Distance
Interface Ref. sensitivity Transceiver Fibre
power (dBm) wavelength (km)
(dBm)
I-1 ANSI -14 ... -20 -28 1263 - 1360 Laser MultiMode Up to 2
The LIM is provided with Automatic Laser Shutdown as prescribed by ITU-T G.664 Recommendation.
Operating wave-
Interface Ref. Link budget Fibre Distance
length nm
MN.00224.E - 018 35
Tab.6 - Guaranteed Ethernet Throughput (Mbit/s) for ALplus2/ALCplus2/ALCplus2e
(Ethernet only)
36 MN.00224.E - 018
Tab.7 - Estimated Ethernet throughput
4QAMs 57 49
4QAM 69 60
8PSK 100 86
MN.00224.E - 018 37
4QAMs 0.475 0.492 0.526 0.595 0.735 0.867 3.136
User output
User input
- Equivalent circuit recognized as a closed contact 200 Ohm resist. (max) referred to -6V (min)
ALplus2 only.
• E1: configurable as Extra E1-1 or Extra E1-2 (connector name is “2 Mbit/s wayside” but is “in band”.
38 MN.00224.E - 018
6.1.3.1 E1 (Connector name is 2 Mbit/s wayside)
Input side
Output side
• Connector RJ45
MN.00224.E - 018 39
• Equipment side contradirectional
• Connector RJ45
• Connector RJ45
• Connector RJ45
• Equalization 24 taps
• Correction LDPC
40 MN.00224.E - 018
6.1.5 1+1 switching criteria
Rx switch
Rx switch is hitless and the system has built in capabilities of minimizing errors during the detection time.
Branch 1 is preferential and the system switches to branch 2 only when branch 1 is error affected. The
switching facility provides automatic synchronization of the two incoming streams up to:
Levels Definition
Tx switch is not hitless. Maximum outage due to the Tx switching (sum of the maximum automatic change-
over + Rx IDU re-synchronisation time), with ACM (Adaptive Code and Modulation) activated, is shown in
Tab.10.
• Interconnection with ODU unit single coaxial cable for both Tx and Rx
MN.00224.E - 018 41
6.2 POWER SUPPLY AND CONSUMPTION
In this paragraphs are listed the following three characteristics: the max current (IMAX) at the power con-
nector of the IDU alone, the max current (IMAX) at the power connector of the IDU with the complete equip-
ment (IDU 1+1 and relevant 2 ODUs) and the consumption of the IDU alone. The consumption of the
complete equipment is described inside the ODU attachment (one for each frequency) with high precision,
at this point we have considered the ODU with the higher consumption (about 25W) among all the avail-
able.
N.B. The consumption of the complete equipment is described inside the ODU attachment (one for each
frequency).
42 MN.00224.E - 018
Tab.12 - IMAX
ALCplus2 1+0 exp 16E1 0.88A (@40.8 Vdc) 1.5A (@40.8 Vdc)
ALCplus2 1+0 exp nodal 0.91A (@40.8 Vdc) 1.52A (@40.8 Vdc)
ALCplus2 1+1 exp 16E1 1A (@40.8 Vdc) 2.23A (@40.8 Vdc)
ALCplus2 1+1 exp nodal 1.1A (@40.8 Vdc) 2.33A (@40.8 Vdc)
ALCplus2e 1+0 18E1 2xSTM-1 nodal 1.42A (@40.8 Vdc) 2A (@40.8 Vdc)
ALCplus2e 2+0/1+1 34E1 2xSTM-1 1.54A (@40.8 Vdc) 2.75A (@40.8 Vdc)
ALCplus2e 2+0/1+1 18E1 2xSTM-1 1.54A (@40.8 Vdc) 2.75A (@40.8 Vdc)
ALCplus2e 2+0 2E1 XPIC 1.45A (@40.8 Vdc) 2.1A (@40.8 Vdc)
ALCplus2E 2+0 34E1 2xSTM-1 1.64A (@40.8 Vdc) 2.85A (@40.8 Vdc)
ALCplus2e 2+0 18E1 2xSTM-1 nodal 1.64A (@40.8 Vdc) 2.85A (@40.8 Vdc)
6.2.4 Fuses
Power supply circuits are protected against overcurrent with fuses on supply line:
• ALplus2 there is an internal soldering fuse on the RIM PCB behind front panel
- Nominal current 3A
- Type timed
MN.00224.E - 018 43
6.3 ODU CHARACTERISTICS
• Max RF level in Rx for BER 10-3 see attachment relevant to ODU frequency
• Additional Tx and Rx losses for 1+1 version see attachment relevant to ODU frequency
6.4.1 Dimensions
6.4.2 Weight
44 MN.00224.E - 018
6.4.3 Environmental condition
MN.00224.E - 018 45
7 ALPLUS2 IDU DESCRIPTION
7.1 CONFIGURATION
• Controller
• LIM
In Fig.24 you can find the block diagram of ALplus2 with 16E1, version 1+0 and 1+1 configuration. In
Fig.25 you can find the block diagram of Alplus2 with 16E1, 2x(1+0) configuration.
7.1.2 Controller
- USB port
- RS232 asynchronous used for SCT/NMS connection (using PPP protocol and baud rate speed up
to 57600)
- RS232 asynchronous used for connecting further NEs (using PPP protocol and baud rate speed
up to 57600)
- EOC embedded within the packet radio frame for connection to the remote NEs
• WEB LCT interface can be used with EOC capacity equal or bigger than 64 kbit/s
• log-in: the main controller manages the equipment or network login/logout by setting and then con-
trolling the user ID and relevant password
46 MN.00224.E - 018
• alarm monitoring: acquisition, filtering and correlation of the alarms gathered logger and alarm
sending to the connected managers: SCT/LCT - NMS5UX. Management of the alarm LEDs on the
LIM front panel.
• user in and alarm out management: it receives external alarms and route them to relay contacts
along with the internal alarms generated by the equipment
• download: firmware, Web Lct and configuration file can be downloaded. Download activity is based
on FTP protocol.
The controller offers an electrical interface to the following three service channel:
Service signals connected to the controller modules are sent to the LIM module for MUX/DEMUX process-
ing.
7.1.2.2 Firmware
Equipment software permits to control and manage all the equipment functionality and it is distributed on
two hardware levels: main controller and ODU peripheral controllers.
Firmware can be updated through the Web Lct and it is stored in two different memory banks: one con-
taining the running firmware and the other the stand-by firmware. This permits to download a new firm-
ware release to the stand by bank without cutting the traffic. Bank switch enables the new release to be
used.
The Web Lct allows the configuration and the management of the local equipment. When the remote one
is configured properly, the whole radio link can be managed.
Web Lct runs on Internet Explorer and Firefox with Flash player plug-in. WLC is a utility to connect to
ALplus2 with USB cable.
WLC and Flash player plug-in for IE and Firefox can be downloaded from the site www.siaemic.com after
registration.
On Controller front panel are present four LEDs to summarize the terminal status:
Always on Controller front panel are present two Ethernet ports for management, MNGT1 and MNGT2,
whose LEDs are:
MN.00224.E - 018 47
• during the boot with Ethernet cable inserted:
- green LED = ON
On the Controller board is present a slot, not accessible from the external, for the insertion of a memory
card. The memory card allows the upload/download of the equipment configuration and the equipment
firmware
7.1.3 LIM
• multiplexing and demultiplexing (MUX/DEMUX process) of traffic (tributaries and Ethernet frames)
• aggregation of the multiplexed signals along with services through a Bit Insertion circuit and vice-
versa. The aggregate frame contains:
- the EOC signals for supervision message propagation towards the remote equipment
• duplication of the digital processed signals to supply two RIMs in 1+1 configuration.
From the two RIMs the LIM receives I and Q analogue signals then digital converted for the following pro-
cessing:
• clock recovery
• differential decoding
• parallel to serial conversion to recover the aggregate signal at the receive side.
48 MN.00224.E - 018
The aggregate signal is then sent to a frame alignment circuit and CRC analysis and then to the error cor-
rector. The errors uncorrected by the FEC are properly counted to achieve:
• radio performances.
Inside LIM is present an Ethernet switch with 3 external ports (electrical 1000BaseT or optical 1000BaseX)
and one internal. Only port 1 is present with both kind of interface, the port 2 is electrical and port 3 optical.
The external interfaces (3 operational on 4 presents) are placed on the front panel. Internal port is repre-
sented by the local radio stream where through native Ethernet transport is connected with the remote
equipment.
• Ethernet port LEDs
• Speed
- one blinking = 10BaseT
- two blinking = 100BaseT
- three blinking = 1000BaseT
• LINK/ACT
- on = link up, no activity
- off = link down
- blinking = activity.
Switch function
LIM can operate like a switch between two or more separated LANs with the following advantages:
• to keep separated the traffic into two LANs towards MAC filtering to get a total traffic greater than
the traffic in a single LAN.
The switch realised into LIM/Ethernet module is transparent (IEEE 802.1d and 802.q) into the same Vlan
described by VLAN Configuration Table.
It works at data link level, Layer 2 of OSI pile, and leave untouched Layer 3 and it takes care to send traffic
from a local LAN to another one (Local and Remote).
The operation is the following: when a LAN port receives a MAC frame, on the basis of destination address,
it decides which LAN to send it:
• if destination address is a known address (towards address learning procedure) and is present into
local address table, the frame is sent only on destination LAN (MAC switching)
• otherwise the frame is sent to all ports with the same VLAN ID (flooding).
Full duplex mode can be activated into 10/100BaseT interfaces manually or with autonegotiation.
100BaseFx operates always into full duplex mode.
MN.00224.E - 018 49
Link Loss Forwarding
Link Loss Forwarding (LLF) is an alarm status of Ethernet interface. LLF can be enabled or disabled.
If LLF is enabled, any linkdown alarm will generate the alarm status of Ethernet interface blocking any
transmission to it. LLF can be enabled for each ports at front panel.
With LLF enabled the equipment connected (routers, switches so on) can be notified that radio link is not
available and can temporarily re-route the traffic.
MDI/MDIX cross-over
The Ethernet electrical interface into FEM module can be defined by WebLCT as MDI or MDIX to cross-over
between pairs so that external cross-over cable is not required.
VLAN functionality
LIM Ethernet module works with IEEE 802.1q and 802.1p tag. Tag is made up with:
• 1 fixed bit
• 12 bits VLAN identifier (VLAN ID) according with 802.1q.
Switch cross-connections are based on Vlan Configuration Table where input and output ports or only out-
put ports should be defined for any used VID. Vlan ID (VID) has a range from 1 to 4095.
Refer to Fig.22.
STM-1 frame generation requires that it is synchronised to a SDH network.
Into ALplus2 a synchronisation circuit, called SETS, gets the synchronisation signal from the following dif-
ferent sources:
• radio
• STM1
• tributary A/WST
• tributary B
• tributary n
• Lan3
• Lan4
• Internal source
As shown in Fig.22 the clocks extracted from the sources are sent to a selection circuit that chooses one
of the signals depending on the control sent by a selection logic.
This latter acts on the base of alarm roots (LOS-loss of input signal, LTI-loss of timing input, LOF-loss of
frame), on the base of assigned priority and manual forcing.
The selected clock drives an oscillator through a PLL circuit. The oscillator will generate the required syn-
chronisation for the STM-1 frame generation. If no input signals are available the internal oscillator source
is used for the local restart.
50 MN.00224.E - 018
Radio
Trib A
Trib B/n Synchronisation
Source
for
STM-1 selector
STM-1 interface
Lan3
Lan4
LOS
Logic circuit
LTI
for
Priority Control clock
Manual Forcing synchronisation
On LIM front panel are present two LEDs to describe the following aspect:
7.1.4 RIM
• power supply
• telemetry IDU/ODU.
MN.00224.E - 018 51
7.1.4.1 Modulator
Signals from LIM are connected to a programmable modulator. It consists of the following circuits:
The obtained 330 MHz QAM modulated carrier is then sent to the cable interface for connection with ODU.
7.1.4.2 Demodulator
At the receive side, from the cable interface, the 140 MHz QAM modulated carrier is sent to the QAM de-
modulator passing through a cable equalizer circuit.
The QAM demodulator within the RIM converts the signal to be sent to the digital part of the demodulator
within the LIM.
ACM profiles
In ALplus2/ALplus2 radio family uses Adaptive Code and Modulation (ACM) in order to employ the correct
modulation profile depending on the Rx signal quality.
• 4QAM strong
• 4QAM
• 8PSK
• 16QAM
• 32QAM
• 64QAM
• 128QAM
• 256QAM.
• 7 MHz
• 14 MHz
• 28 MHz
• 56 MHz.
ACM switching
The usage of the previous modulation profiles in a fixed channel bandwidth results in a variable capacity.
The criteria defining the necessity of an ACM switching, upshift or downshift, is the Rx S/N ratio.
• Upshift - When there is an increase of received S/N, within the same Channel Spacing, the modu-
lation complexity is increased in the direction from 4QAM strong to 256QAM increasing the spectral
efficiency
52 MN.00224.E - 018
• Downshift - When there is a decrease of received S/N, within the same Channel Spacing, the mod-
ulation is reduced in the direction from 256QAM to 4QAM strong reducing the spectral efficiency,
In order to configure properly the radio link using ACM facility, an optimization must be found between
max traffic during good propagation conditions and max availability during bad propagation conditions. To
obtain this purpose the ACM in ALplus2/ALCplus2 family can be configured via software setting the follow-
ing parameters: ACM setting and Tx Power mode.
ACM setting
The ACM can vary modulation profiles between two extremes defined by the operator through software
configuration: Upper Modulation and Lower Modulation.
• Upper modulation - When propagation into the given radio channel is in the better condition (high
Rx S/N), the radio link is working at the maximum throughput defined at Upper Modulation: the
highest modulation profile that ACM can employ
• Lower modulation - When propagation into the given radio channel is in the worst condition (low
Rx S/N), the radio link is working at the minimum throughput, defined at Lower Modulation: the
lowest modulation profile that ACM can employ
Tx power mode
Tx power mode can be set as Constant Peak or Constant Average (constant bolometer measurement).
• Constant Peak - Tx power is at maximum at 4QAM and at 256QAM is reduced (typical 4.5 dB) so
the RF Tx amplifier can operate in better linear conditions.
The Tx Power mode is set depending on the modulation license of the user and depending on the Lower
Modulation that has been set.
For example:
In case of a 4QAM licence, all the other modulations must remain into the 4QAM mask. In this condition
Tx power must be Constant Peak (Tx Power Constant Peak Mode = Enable): max Tx power at 4QAM and
reduced power at all the other modulations.
In case of a 16QAM licence (or higher complexity) and Lower Modulation is set at 4QAM, the emitted spec-
trum must remain into the emitted spectrum defined for 16QAM even if the equipment is transmitting at
4QAM. In this case Tx power must be Constant Average (Tx Power Constant Peak Mode = Disable): Tx
power is always the same at any modulation and typically is the Upper Modulation's power. As an alterna-
tive the Lower Modulation can be set at 16QAM so Tx power Constant Peak can be activated.
With Constant Average Tx power (Tx Power Constant Peak Mode = Disable), the Tx power at 4QAM and
any other modulation is the same of Upper Modulation, so if Upper Modulation is 256QAM the output power
at any modulation is the same of 256QAM which is 4.5 dB less than 4QAM. The result is that enabling
256QAM is a big advantage for traffic but less link budget margin at 4QAM.
E1 priority
One is Permanent E1 equal to High Priority E1 that will never be interrupted during modulation downshift.
Downshift modulation will be limited to the minimum to obtain the selected Permanent E1.
The second group is Extra E1 equal to Low Priority, these tributaries will be interrupted progressively during
modulation downshift. They will start to be cut from the highest e.g. tributaries 16th or 32nd up to the first.
In Tab.13 it is reported the priority of tributaries, the lowest will be cut first.
Ethernet traffic
Once defined the bandwidth, Permanent E1 and Extra E1 at any modulation the amount of Ethernet ca-
pacity is the total radio capacity minus the Permanent + Extra E1 at any modulation.
MN.00224.E - 018 53
Tab.13 - E1 priority
The -48 V battery voltage feeds the IDU and ODU circuitry. The service voltage for the IDU feeding are
achieved through a DC/DC converter for +3.6 V generation and a step down circuit for -5 V.
Both voltages are protected against overvoltages and overcurrents. The same battery running through the
interconnection cable gives the power to the ODU.
The dialogue IDU/ODU is made-up by the main controller and associated peripherals within the ODU. Con-
trols for ODU management and alarm reporting is performed making use of a bidirectional 388 kbit/s
framed signals.
The transport along the interconnecting cable is carried out via two FSK modulated carriers:
7.2 LOOPS
To control the IDU correct operation a set of local and remote loops are made available. The commands
are forwarded by the WebLCT/NMS program. Loop block diagram is shown by Fig.23.
7.2.1 Tributary
Each input tributary is routed directly to the tributary output upon receiving the command. The Tx line
transmission is still on.
54 MN.00224.E - 018
Tributary remote loop
Each tributary directed towards the Rx output line is routed back to the Tx line. The Rx line is still on.
This kind of loop permits to check the full IDU operation. When activated, the modulator output is connect-
ed to demodulator input.
The loop is assured by converting the frequency of the modulator from 330 MHz to 140 MHz.
MN.00224.E - 018 55
56
LIM RIM
330
DEMUX BE
Trib. OUT 140
IDU loop
140 MHz
from ODU
MN.00224.E - 018
10/100BaseT
LAN1 Ethernet
1000BaseT
packet switch
10/100/1000BaseT
LAN2 Port A
1000BaseSX,LX
LAN3
Permanent E1 Radio
up to 60E1 1+0
1+1
E1
cross-connect
STM-1 MSP
Extra E1
up to 19E1
16E1
WST
Up to 80E1
Fig.24 - ALplus2 with 16E1, 1+0 and 1+1 version, block diagram
MN.00224.E - 018 57
Ethernet
10/100BaseT packet switch Port A
LAN1
1000BaseT
10/100/1000BaseT
LAN2
Port B
1000BaseSX,LX
LAN3
Permanent E1 Radio A
up to 60E1
1+0
E1
cross-connect
Extra E1
STM1 MSP up to 19E1
16E1
E1 WST
Permanent E1 Radio B
up to 60E1 1+0
- Permanent = High Priority
- Extra = Low Priority
Extra E1
up to 19E1
58 MN.00224.E - 018
8 ALCPLUS2 IDU DESCRIPTION
8.1 CONFIGURATION
• Controller
• LIM
Please refer to chapter 7 ALplus2 IDU DESCRIPTION for any information relevant to functionalities of the
listed circuits.
Inside IDU is present an Ethernet switch with 4 external ports (electrical 1000BaseT or optical 1000BaseX)
and one internal. Port 3 and Port 4 have both interfaces, Port 1 and Port 2 are electrical only.
The external interfaces (4operational on 6 present) are placed on the front panel. Internal port is repre-
sented by the local radio stream where, through native Ethernet transport, is connected with the remote
equipment.
For Ethernet switch functionalities, please refer to chapter 7 ALplus2 IDU DESCRIPTION.
MN.00224.E - 018 59
8.2 SYNCHRONIZATION
Refer to Fig.52.
Into ALplus2e a synchronisation circuit, called SETS, gets the synchronisation signal from the following dif-
ferent sources:
• radio A
• radio B
• STM1(1)
• STM1 (2)
• tributary A/B
• tributary A/B as T3
• tributary nE1
• node1
• node2
As shown in Fig.52 the clocks extracted from the sources are sent to a selection circuit that chooses one
of the signals depending on the control sent by a selection logic.
This latter acts on the base of alarm roots (LOS-loss of input signal, LTI-loss of timing input, LOF-loss of
frame), on the base of assigned priority and manual forcing.
The selected clock drives an oscillator through a PLL circuit. The oscillator will generate the required inter-
nal synchronisation signal T0.
Trib A or B selected as T3 can be the source of T4 signal (2MHz) for other equipment like for example into
nodal structure.
If no input signals are available the internal oscillator source is used for the local restart of STM1 genera-
tion.
On the front panel a protected slot for the insertion of a memory card is present.
The memory card allows the upload/download of the equipment configuration and the equipment firmware.
60 MN.00224.E - 018
8.4 ALC BLOCK DIAGRAMS
On Fig.31, Fig.32, Fig.33 and Fig.34 you can find block diagrams of ALCplus2 with 32E1 expansion, with
16E1 expansion and NBUS, with 16E1 expansion and without any expansion.
A node can be made up of max 8 subracks of ALCplus2 IDU so that we can have:
• up to 8 x 16E1 = 128E1
On the front panel of ALCplus2 there are two “NBUS” ports (1 and 2) which must be connected to the other
IDU subrack as in Fig.35 for E1 traffic and Ethernet traffic.
For Ethernet traffic Lan1 and Lan2 must be connected as in Fig.35 Lan1 and Lan2 connection can be made
with normal Lan cables CAT5e/CAT6.
NBUS connection among the IDUs are made by cables of CAT7 quality, only by proprietary SIAE cable to
insert into the NBUS connectors (1 and 2) on the front panel. See Tab.15 for cable length and SIAE code.
For any IDU into WebLCT it is necessary to define how many IDU are into the Node from 2 to 8.
In case of Not Protected mode, all the 126 E1’s of the NBUS are used to connect a subrack to the others
for a total amount of 252 E1 connections available on NBUSes from one IDU.
In case of Protected mode, the unused connections, are used as protection of the connections between the
other IDUs; for example 63 E1’s are used between Node1 and Node2 and the other 63 E1’s are used as
protection of the connections between the other nodes, the connections used as protection pass into others
IDUs as passthrough without any need to be programmed.
The troubles in the connections between the NBUS buses are identified by alarms.
In case of protected modality, if the cable carrying the traffic is broken, an alarm is issued on the relevant
NBUS port, the equipment software switches the traffic on the other operating NBUS cable.
With SCT/LCT program it is possible to configure a Node made up of some Nodals so into the window of
Node Manager it is possible to program only one big Crossconnect matrix for E1 and only one Ethernet
switch for all Lan traffic.
The software hides all NBUS connection for E1 and Lan connection from an IDU to others IDUs, so to op-
erate on one big Crossconnection matrix and one big Ethernet switch.
For any IDU the Node Manager shows for E1s 16E1, STM1 E1s, radio permanent E1, radio extra E1 and for
Ethernet Lan3, Lan4, radio port Port A.
The Nodal equipment with SDH STM1 interface is a Regenerator Section Termination (RST) and a Multiplex
Section Termination (MST) therefore it generates the STM-1 frame and has an internal synchronization cir-
cuit SETS. The synchronization of the Node can be distributed on the NBUS.
The ALCplus2 subracks must be synchronised together via NBUS or other interface.
MN.00224.E - 018 61
For each Nodal subrack, the STM-1 interface can be duplicated (1+1 MSP) for the possible protection of
cable. The switching criteria in Rx are:
• Unequipped
• LOS
• LOF
• MSAIS
• TIM
• B2 excessive BER
• B2 degraded BER.
Suppose that the nodals 1 and 2 already exist and that you must add the nodal 3.
Disconnect the cable between NBUS1 nodal2 and NBUS2 nodal1, the traffic is automatically switched to
the other cable, if necessary.
Disconnect the cable between LAN1 nodal2 and LAN2 nodal1, the traffic is automatically switched to the
other cable, if necessary.
By WebLCT or SCT/LCT, re-program the nodal1 and nodal2 as node with 3 items.
By WebLCT or SCT/LCT, re-program the nodal3 as nodal3, protected and define the node with 3 items.
Connect the NBUS1 of the nodal2 with NBUS2 of nodal3, connect the NBUS1 of the nodal3 with NBUS2 of
the nodal1 as in Fig.35.
Connect the LAN1 of the nodal2 with LAN2 of nodal3, connect the LAN1 of the nodal3 with LAN2 of the
nodal1 as in Fig.35.
By SCT/LCT, with Nodal ALCplus2 Manager, Nodal Configuration add nodal3 IP address.
Program the interested cross-connections and Ethernet switch connections with external interfaces of
nodal3, Node Manager will take care of connections on NBUSes and LAN1, 2.
The same procedure can be used even if the added node is different from nodal3.
Suppose that the nodals 1, 2 and 3 already exist and that the nodal 3 must be removed.
By SCT/LCT, with Nodal ALCplus2 Manager, delete all the cross-connections to the external interfaces of
nodal3.
The same procedure can be used even if the deleted nodal is different from nodal3.
62 MN.00224.E - 018
8.6 LAG - LINK AGGREGATION
Link Aggregation (LAG) is a feature available on SIAE ALCplus2 equipment that allows assigning up to four
physical links to one logical link (trunk) that functions as a single, higher-speed link.
In SIAE equipment LAG is named Trunking and two different implementations are possible:
Radio Trunking is available only when the Nodal Ethernet functionality is enabled.
The nodal Ethernet configuration can be deployed on all the ALCplus2 IDU models.
More details about this implementation will be provided in next paragraph 8.5 ALCplus2 NODE.
Line Trunking is available on the ALCplus2 IDU. SIAE ALCplus2 support IEEE 802.3ad LACP (Link Aggrega-
tion Control Protocol). See Fig.26.
LACP allows a network device to negotiate an automatic bundling of links by sending LACP packets to the
peer (directly connected device that also implements LACP). In addition to the increased capacity of the
logical link, LACP provides additional advantages:
• failover detection when a link fails, allowing for a trunk reconfiguration in order to avoid systematic
packet loss (after the reconfiguration the packets will be lost only if the throughput exceed the trunk
capacity).
• it introduces an agreement between the two LACP peers before to start data transmission over the
trunk. This prevent anomalous behaviour in case of cabling or configuration mistakes.
LACP works by sending frames (LACPDUs) over the links belonging to the trunk. Also the equipment de-
ployed on the other end of the trunk will send LACP frames over the same links: this enables the two units
to establish the trunk. LACP can be configured two modes: active or passive. In active mode it will always
send frames along the configured links. SIAE ALCplus2 implements an "active" LACP.
MN.00224.E - 018 63
Each IDU allows to define up to 4 different trunks on its LAN interfaces. A Line Trunk can aggregate up to
4 LAN interfaces with the following restrictions:
• all the LAN interfaces must be defined with the same speed (either 10, 100 or 1000 Mbit/s).
• all the interfaces must belong to the same IDU, even if the IDU is deployed in Nodal Ethernet con-
figuration.
When a Trunk is defined on SIAE ALCplus2, the end-to-end traffic is transmitted over all the aggregated
lines. As a results, the overall capacity of the trunk can be theoretically equal to the number of aggregated
lines multiplied by the capacity of a single line. In the example of Fig.27, four 100Mbs connection are
grouped into the same trunk, carrying all the capacity in transit from a radio link to another. In this con-
figuration, the theoretical maximum capacity that can transit on this trunk is 400 Mbit/s.
Line
trunking
The packets carried by the trunk are assigned to each line depending on their Source MAC (SA) and Des-
tination MAC (DA) Addresses (MAC hashing).
A possible problem that could occur when Link Aggregation protocols are used is a change in the transmis-
sion order of packets belonging to the same logical session. The MAC hashing method prevents such a
problem: the traffic transmitted from one host to another one in the network (fixed SA and DA) is always
sent over the same physical line of the trunk, avoiding any order change.
If a line of the trunk fails (for example due to a cable disconnection), the LACP protocol automatically re-
configure the trunk group into a lower order trunk. So doing, the traffic that before was carried over the
failed line, now will be re-distributed over one of the remaining trunk lines, ensuring continuity to the traffic
transmission. The typical LAG reconfiguration time in case of a LAN cable failure is below 1 second.
Radio Link Trunking is a feature available on SIAE ALCplus2 equipment when deployed in Nodal Ethernet
configuration.
This feature allows to bundle up to 4 radio links to increase the capacity of an Ethernet connection between
two radio sites (see Fig.28).
64 MN.00224.E - 018
LAN4 LAN4
LAN3 LAN3
ALCplus2 ALCplus2
Node 1 Node 1
LAN2 LAN2
LAN1 LAN1
LAN4 LAN4
LAN3 LAN3
ALCplus2 ALCplus2
Node 2 Node 2
LAN2 LAN2
LAN1 LAN1
LAN4 LAN4
LAN3 LAN3
ALCplus2 ALCplus2
Node 3 Node 3
LAN2 LAN2
LAN1 LAN1
LAN4 LAN4
LAN3 LAN3
ALCplus2 ALCplus2
Node 4 Node 4
LAN2 LAN2
LAN1 LAN1
Radio
trunking
SITE A SITE B
Each Nodal Ethernet stack can belongs to one Radio Trunk. Each IDU of the trunk sends over the air only
a portion of the traffic, according to the same hashing rule used for the line trunking (see paragraph 8.6.1
Line Trunking). The traffic received from the radio trunk is sent towards the IDU where is located the out-
going interface according to standard MAC learning/switching mechanisms.
Resiliency between the radio links aggregated into the trunk is managed by means of a proprietary proto-
col. If a radio link of the trunk fails (due to fading or equipment failure), this protocol automatically recon-
figure the trunk group into a lower order trunk. In this way, the traffic that before was carried over the
failed link, now will be re-distributed over one of the remaining trunk lines, ensuring continuity to the traffic
transmission. The typical Radio Trunk reconfiguration time is about 600msec.
It is important to note that also if it could be possible to aggregate up to four 340Mbit/s radio links (by
using 56 MHz frequency channel with 256 QAM modulation), the maximum capacity that can be carried
over the radio link cannot exceed 1Gbit/s in each direction of transmission (referring to Fig.28, from Site
A to Site B and vice-versa).
Regarding multicast/broadcast, the total traffic entering the stack (sum of the packets entering from LAN3/
LAN4 interfaces and from the radio ports) cannot exceed 1Gbit/s. This because also the traffic received
from the radio trunk is flooded towards all the IDUs belonging to the Nodal Ethernet stack (MAC learning
cannot be performed over multicast packets).
MN.00224.E - 018 65
8.7 LINE PROTECTION THROUGH DISTRIBUTED ELP
ELP (Ethernet Line Protection) is a feature available on ALCplus2 IDU that allows to protect a GE interface
against cable failure or accidental disconnection. With ELP it is possible to connect an ALCplus2 IDU to an-
other network element by using two GE interfaces. Both interfaces are active but just one is enabled to
forward and receive traffic (forwarding state), while the other does not allow any traffic to pass (blocking
state). If the forwarding interface goes down, the other one passes to the forwarding state. The typical
switching time is around 1.5 sec. This feature does not imply the use of any protocol, but is simply based
on the status of the physical interfaces. As a consequence, no particular protocol support is required on
the connected equipment: it is simply required to enable the two GE interfaces.
When the Nodal Ethernet configuration is used, ELP can be used to protect the traffic of two GE interfaces
belonging to two different IDUs of the stack. In this way the traffic can be protected against IDU failure,
in addition to the cable protection.
This feature is particularly useful when the Nodal stack is connected to an external equipment like a core
router (see the example of the following Fig.29).
LAN4
LAN3
ALCplus2
Node 2
LAN2
LAN1
LAN4
LAN3
ALCplus2
Node 3
LAN2
LAN1
Core router
LAN4
ELP
protection LAN3
ALCplus2
Node 4
LAN2
LAN1
It is recommended to disable any Spanning Tree protocol on the external equipment: this could cause long-
er traffic recovery times.
66 MN.00224.E - 018
8.8 ETHERNET OAM (OPERATION ADMINISTRATION AND MAINTE-
NANCE)
As native Ethernet is originally designed for LAN (local Area Network), OAM is not included into the native
Ethernet network equipment. In order to provide a carrier grade service, the OAM protocol can be used in
any point-to-point Ethernet link (made up of a single radio link or many radio links). The aim of this pro-
tocol is to check and monitor the functionality of the service that the provider guarantees on the network.
The Service Layer OAM fully monitors a customer End-to-End Ethernet Service. Two main standards cover
this topic, the IEEE 802.1ag and ITU-T Y.1731.
The IEEE 802.1ag provides CFM (Connectivity Fault Management) useful for detecting, isolating and re-
porting connectivity faults. The ITU-T Y.1731 Standard comprehends the CFM plus some additional fea-
tures, like RDI (Remote Defect Indicator) that allows to report back to the start of the chain the Alarm
message.
SIAE ALCplus2 supports CFM according to both standards ITU-T Y.1731 and 802.1ag.
The IEEE 802.1ag and the ITU-T Y.1731 are End-to-End service, i.e. provides the tools to monitor the
Ethernet Service regardless of the layers, Network Path and operators. Since the spectrum of application
can include many applications a more hierarchical structure is needed.
The Standards define:
• Maintenance Domains (MD): these specify the Domains of operators, users and service providers.
Levels from 0 to 7 are possible depending on the type of service to be monitored. Customer Domain
is the higher which includes both ends of the Ethernet service (from one End user to the other End
user), Standard Default values for Customer Domain are 7, 6 and 5. Service Provider Domains
should have a MD lower than the Customer Domain since include the whole network except the End
Users. Standard default values for Provider Domains are 3 and 4. Operator Domains are lower than
Service Provider Domains since just a part of the network is included. Standard Default values for
operator domains are 0, 1 and 2. A domain is transparent to all messages with higher priority while
blocking all lower priority messages. Fig.30 shows the hierarchical structure of Maintenance Do-
mains.
MN.00224.E - 018 67
CE PE PE CE
Access Operator 1 Operator 2 Access
Network Core Network Core Network Network
High Level
Low Level
MEP MIP MIP MEP
Operator 2
At each end of the Maintenance Domain two MEPs (Maintenance End Point) will be specified. One MEP is
local, the other one is in the remote equipment. The MEPs are "markers" that defines the end of a domain
and are in charge of originating OAM frames.
In a domain also MIPs (Maintenance Intermediate Points) can be specified. The MIPs are passive check-
points. The MEPs and MIPs configuration are discussed in details in the following points. The choice of the
domain that is the Domain Label (name) is left to the user. Particular attention must be paid to use exactly
the same MD label (and level) in each equipment where the MD is specified, i.e. different equipment with
same value of MD domain but different MD labels (or levels) belongs to different Domains.
• A Maintenance Association (MA) is one association which correlates the VLAN to the MD in which
the MEPs and MIPs have to be defined.
When a specified traffic needs to be monitored, then it is necessary to relay the VLAN to a Domain
and to the corresponding MEPs or MIPs through the MA. Before creating the Maintenance Associa-
tion, the VLAN, either SVLAN (Service VLAN Tag o Stacked VLAN Tag) or C-VLAN, has to be specified
in the VLAN Table. In each SIAE equipment it is possible to set up to 32 different MA. Particular
attention must be paid to use the same MA label in each equipment where the MA is specified, i.e.
different MA labels on the same VLAN correspond to different MA associations.
68 MN.00224.E - 018
• At the Edge of a MD there are MEPs (Maintenance End Points) and in the middle there could be MIPs
(Maintenance Intermediate Points). MEPs are the units in charge of managing the CFM to correctly
monitor the status of the Ethernet service provided. MIPs are passive check-points that answer to
polling coming from MEPs. MEPs will forward OAM messages coming from higher domains and will
discard OAM messages generated from lower domains.
Each interface can be configured as MEP, Port A interface (radio interface) included. Once chosen
the interface, depending on the network topology, the direction of the MEP has to be specified. Two
Directions are possible, MEP "up" and MEP "Down". With MEP "Down" configured the OAM PDUs are
sent from the interface in the direction outside the equipment, i.e. the OAM PDUs are sent from the
interface on the cable toward next equipment. With MEP "Up" configured the OAM PDUs are sent
from the interface toward the inside of the equipment and will follow the VLAN table previously con-
figured. MEPs are distinguished from each other through a MEP ID, therefore MEPs belonging to
same MA must have different MEP Ids. In order to configure a MIP the MA has to be enabled on the
equipment. Up to 32 MIPs or MEPs can be configured on each equipment.
The protocols belonging to the Connectivity Fault Management implemented in SIAE equipment are follow-
ing listed:
• Continuity Check Protocol: this protocol enables the sending of a periodic message (like a Heartbeat
message) which enables the other MEPs deployed in the network to distinguish the status of a vir-
tual connection. This message can only be originated by a MEP. Time between messages is adjust-
able with 1s, 10s, 1min, 10min. These messages do not trigger any automatic reply from the
destination entity.
• LoopBack Protocol: it resembles an IP PING message; once this message is sent (e.g. MEP1 sends
a Loopback Message to MEP2). MEP2 replies to MEP1 confirming therefore the status of the connec-
tion. This is done to check the status of the connection between the MEP originating the message
and the MEP/MIP to which the message is addressed. This message can only be originated from one
MEP and can be addressed to both MEPs or MIPs. ALCplus2: The number of Loopback Messages in
ALCplus2 equipment is adjustable from 1 to 5 consecutive Loopbacks. In each equipment, it is pos-
sible for each MEP to check the presence of other MEPs in the same MA. This is done through the
"Remote MEP" application which allows this acknowledgement and distinguishes the other MEP
through means of MEP IDs and MAC address.
• Link Trace Protocol: This protocol sends a message similar to the LoopBack protocol. Every equip-
ment that is reached by this message will answer to the sender providing its own MAC Address. In
this way the sender is able to understand of which equipment the MA is composed. E.g. a MEP sends
the Link Trace Message to another MEP belonging to the same Maintenance Association. The MIPs
that are eventually deployed in the middle of the path will forward this message and answer to the
initiating MEP with their own MAC Address. By doing so the initiating MEP knows the OAM-devices
deployed in the path and their order.
• Remote Defect Indicator: This Feature allows a MEP, in presence of a fault or a defect, to send a
RDI to inform the other MEPs, belonging to the same MA, of the presence of this Defect. The ad-
vantages of this procedure are to avoid multiple Alarms created by the same cause and to be able
to check the status of other Remote MEPs. This RDI information is reported in the Continuity Check
Message. ALCplus2: This feature is present in ALCplus2 equipment and the presence of this alarm
can be checked as well in the Remote MEPs screen on the equipment.
As an example, let's consider a network where a sequence of 8 SIAE ALCplus2 Radio links is deployed. In
this case a Maintenance Domain, a VLAN and a Maintenance Association have to be defined. The VLAN car-
rying the traffic must be present in the VLAN table of each equipment.
Two MEPs at the end of the chains and a variable number of MIPs in the middle has to be defined with
Continuity Check Message (CCM) enabled.
In case of defect or Ethernet problem, the Continuity Check Message will result in an "Inactive" status trig-
gering one Alarm.
By logging on one MEP it is sufficient to configure the Loopback message and Link Trace Message correctly
detects the location of the Bottleneck or defect related to this traffic. If More than one VLAN is present then
more than one MA has to be defined.
MN.00224.E - 018 69
8.8.3 Reset Switch
Reset Switch button forces factory default values into switch but this is true only at next restart.
The purpose of these two selection is dividing the MAC table into some independents parts named FID (For-
warding Indication Database).
In this chapter are described the new features available in an ALCplus2 with new firmware releases. Only
the main releases are considered (....the firmware releases with new features).
Every firmware release is included in a System Version and is supplied with the right WebLCT version.
FW update procedure
1. FW_Boot E82101
2. FW_appl N90634
3. WEBLCT N96106
All the files are in a compressed container called System Version v.XX.YY.ZZ.
If ODU needs a firmware update, it must be done after there three.
The MAC address in the MAC Address Table can be managed also in this way:
• MAC Learning on Vid basis: MAC address table can be managed depending on Vid
• MAC on port basis: MAC address table can be managed depending on port
70 MN.00224.E - 018
• Half duplex 10M
• Auto-Speed-Dplx (the speed is set automatically during the handshake of the interfaces)
Now is available a new manual operation in the radio management: the Tx side of the radio can be turned
off with or without the timeout checking.
New values are available in each LAN port to limit the input throughput (PIRL - Port based Ingress Rate
Limiting).
Now LAN port3 and LAN port4 can be used in equipment synchronization without considering the interface
kind: the syncE management is available with optical and with electrical interface.
MN.00224.E - 018 71
SOH-STM1 Transport
Now the SOH of a STM1 stream can be transmitted: the SOH transport is made up by a permanent TDM,
one for STM1-1 and another for STM1-2.
A proper symbol is present in the cross connection matrix for this kind of usage.
The SSM management (quality status of a synch source) is available on the following sources:
• STM1
• Nodal Bus
• E1
• Lan Port
SSM allows:
• the presence of two synch sources to all the network elements, a primary and a secondary source
in case of a primary failure
Radio E1 type
The E1 streams carried through the radio link can be set as framed or not framed.
In case of “Framed” setting, the TU-AIS alarms can be used for VC12 management.
The management ports can be set in secure mode: only traffic with the Vid pointed out can be managed.
In each LAN port, up to three different limits can be set for the following kind of traffic and/or a combination
of them: Unicast, Unknown Unicast, Unknown Multicast, Broadcast, ARP.
SSM Management
72 MN.00224.E - 018
CWDM SFP modules
This release increases the range of CWDM SFP modules that can be used in the IDU.
This feature allows limiting the egress throughput of the ALCplus2e LAN interfaces, by properly exploiting
the buffer of this port.
The egress shaping rate can be configured with the following values:
• if Egress Rate < 1Mbit/s: 64kbit/s, 128 kbit/s, 256 kbit/s, 512 kbit/s
• if Egress Rate > 1 Mbit/s & Egress Rate <10 Mbit/s: values with granularity of 1 Mbit/s
• if Egress Rate > 10 Mbit/s (up to 1 Gbit/s): values with granularity of 10 Mbit/s.
In this way each Ethernet port has separate limits for input and output throughput.
In some cases, the radio link failure can be unidirectional, for example when the local equipment has an
Rx signal failure but the remote Rx signal is OK (i.e. unidirectional radio fail due to failure of a transmitter).
However, also in these cases there can be the need to shutdown the link in both directions even if there is
only a unidirectional link failure.
Using the bidirectional LLF feature, in case of LLF in the local equipment, the local equipment can notify
this LLF status to the remote equipment, shutting down the link on both directions.
The following buffer configuration are available on the 8 output queues of the radio port:
• each queue is configurable from 128 kbit to 128 Mbit (see the below screenshot of the queue con-
figuration)
• every radio port has a total available buffer of 184 Mbit (23 Mbyte), so the sum of the 8 output
queue lengths of a single radio port does not have to exceed this value.
MN.00224.E - 018 73
10/100BaseT
LAN1 Ethernet
1000BaseT
packet switch
10/100/1000BaseT
LAN2 Port A
10/100/1000BaseT
LAN3 1000BaseT,SX,LX
10/100/1000BaseT
LAN4 1000BaseSX,LX
Radio
Permanent E1
1+0
up to 60E1
1+1
E1
cross-connect
32E1
2E1
Up to 80E1
Fig.31 - ALCplus2 with 32E1 expansion, STM-1, 1+0 and 1+1 version, block diagram
74 MN.00224.E - 018
10/100BaseT
LAN1 Ethernet
1000BaseT
packet switch
10/100/1000BaseT
LAN2 Port A
10/100/1000BaseT
LAN3 1000BaseT,SX,LX
10/100/1000BaseT
LAN4 1000BaseSX,LX
Radio
Permanent E1
1+0
up to 60E1
1+1
E1
cross-connect
STM-1 MSP
Extra E1
16E1 up to 19E1
NBUS1
NBUS2
2E1
Up to 80E1
Fig.32 - ALCplus2 with 16E1 expansion, STM1, NBUS, 1+0 and 1+1 version, block diagram
MN.00224.E - 018 75
10/100BaseT
LAN1 Ethernet
1000BaseT
packet switch
10/100/1000BaseT
LAN2 Port A
10/100/1000BaseT
LAN3 1000BaseT,SX,LX
10/100/1000BaseT
LAN4 1000BaseSX,LX
Radio
1+0
1+1
2E1
Fig.33 - ALCplus2 with 2E1, 1+0 and 1+1 version, block diagram
10/100BaseT
LAN1 Ethernet
1000BaseT
packet switch
10/100/1000BaseT
LAN2 Port A
10/100/1000BaseT
LAN3 1000BaseT,SX,LX
10/100/1000BaseT
LAN4 1000BaseSX,LX
16E1 Radio
1+0
1+1
2E1
Fig.34 - ALCplus2 with 16E1, 1+0 and 1+1 version, block diagram
76 MN.00224.E - 018
1 2 NBUS
STM1
16E1 up to 80E1
E1 CrossConnect
Nodal 1
Ethernet Switch
LAN3
LAN4 up to 340 Mbit/s
LAN 1 2
1 2 NBUS
STM1
16E1 up to 80E1
E1 CrossConnect
Nodal 2
Ethernet Switch
LAN3
LAN4 up to 340 Mbit/s
LAN 1 2
1 2 NBUS
STM1
16E1 up to 80E1
E1 CrossConnect
up to Nodal 8
Ethernet Switch
LAN3
LAN4 up to 340 Mbit/s
LAN 1 2
MN.00224.E - 018 77
9 ALCPLUS2E IDU DESCRIPTION
9.1 CONFIGURATION
• 1+0
• 1+1
• 1+0 XPIC
• 1+1 XPIC
• 2x (1+0)
• N+0 XPIC
• Controller
• LIM
Please refer to chapters 7 ALplus2 IDU DESCRIPTION and 8 ALCplus2 IDU DESCRIPTION for any informa-
tion relevant to functionalities of the listed circuits.
On Fig.55 you can find block a diagram of ALCplus2e with 32E1 expansion.
78 MN.00224.E - 018
9.2.1 ADAPTIVE CODE MODULATION - ACM PROFILES
In ALplus2e radio family uses Adaptive Code and Modulation (ACM) in order to employ the correct modu-
lation profile depending on the Rx signal quality. Available ACM profiles are the following:
• 4QAM strong
• 4QAM
• 8PSK
• 16QAM
• 32QAM
• 64QAM
• 128QAM
• 256QAM.
• 14 MHz
• 28 MHz
• 40 MHz
• 56 MHz.
The frequency reuse makes use of an XPIC circuit (Cross Polar Interference Canceller) and allows the co-
existence of two radio bearer transmission on the same RF channel. Each radio bearer carries an individual
radio frame up to 341 Mbit/s.
The system consists of two fully independent transceivers, and a cross-polarized antenna with polarization
H connected to one transceiver and polarization V connected to the other transceiver.
The initial co-channel interference is featured by the antenna cross polar discrimination factor (example
29 dB). This value may be not sufficient for frequency reuse system making use of modulations 32QAM
After all, it may be impaired by the propagation condition giving rise to a BER degradation. To get a suitable
discrimination value, an adaptive canceller, based on a fully numeric adaptive coefficient filter, must be
used.
As shown in Fig.58 the received signals at the IF receiver outputs are processed by the demodulator placed
on the copolar branch as well as by the canceller annexed to the demodulator processing the signals from
the cross polar polarization. This process operates in baseband time domain.
An adaptive equalizer minimizes the intersymbolic interference within the copolar demodulator whereas a
circuit similar to the equalizer, processes the signal on the cross route.
Such a signal, summed with the one available at the equalizer output permits the cancelling of the inter-
ference contained in the copolar signal. XPIC circuit is used into configuration 1+0 XPIC and 1+1 XPIC.
IDU-ODU coaxial cable to ODU for vertical polarization and ODU for horizontal polarization should not differ
more than 1.5 meters in length.
MN.00224.E - 018 79
9.4 XPIC 1+1 CONFIGURATION
The XPIC 1+1 configuration is made up of two ALCplus2e IDU with XPIC and 4ODU connected as in Fig.56.
• one IDU is defined Master, the other is defined Reserve, while one of them is Active the other is
Stand-by
• LAN protection with ring connection within LAN1 Master with LAN2 Reserve and LAN1 Reserve with
LAN1 Master
• TDM protection with Nodal Bus, NBUS1 Master with NBUS2 Reserve and NBUS1 Reserve with
NBUS2 Master.
The Active IDU has Tx and Rx on and it is communicating bidirectionally with remote end. The stand-by
IDU has Tx off. The following user interfaces are available:
• STM1
- 4x(1+0), the four STM1s (two on Master and two on Reserve) are independent
or
• no E1 port is available.
A max number 160 (2x80) VC12s are available via radio. Nodal bus from Master and Reserve can carry a
max of 126xVC12s.
The Active IDU is using completely the Radios, the Stand-by IDU has the two Radios in Tx off. HW failure
activate protection switch. Radio traffic is moved on new Active IDU. Switching from one IDU to the other
is traffic affecting.
The four STM1 available on front panel of IDU Master and IDU Reserve can get the traffic from Master Radio
1A and 2A or from Reserve Radio 1A and 2A depending on which IDU is Active: Master or Reserve.
Connection from Radio (Active IDU) to Active IDU STM1 ports is done through cross connection matrix.
Connection from Radio (Active IDU) to Stand-by IDU STM1 ports is done through Active cross connection
matrix, NBUS1, 2, and Stand-by cross connection matrix. Some Ethernet Enchanced features are not avail-
able:
• Not available: Priority management is the same for all LAN ports
• Not available: MPLS priority to SVLAN priority. MPLS priority to CVLAN priority is available
80 MN.00224.E - 018
9.4.1 XPIC 1+1 management
Master and Reserve IDUs have two different IP address shown to the user with WebLCT.
MNGT1 is connected with MNGT2 with a Lan cable. The two local IP address and remote IP Address are in
the same subnet. Local to remote connection of management channel is in Bridge mode.
Synchronization Setup Protocol (SSP) is on only into Active IDUs. Into Standby IDUs the SSP is off.
The 2x(1+0) Est West configuration is made up of one IDU and 2 ODUs connected as in Fig.57.
One ODU to an antenna directed to Est, one ODU connected to an antenna directed to West.
The following interfaces are available:
• 2xSTM1
• 4x1Gbit Ethernet
Cross connection is possible among STM1s, 16E1, radio side E1s. At receiving end the IDU receives E1s
from two ODUs East and West and decides which is going to use on the basis of alarms.
Ethernet traffic may arrive from East or West, switching between the two sides can be done with rapid
spanning tree protocol, activated on both radio ports.
A selective E1 subset defined into WebLCT can be routed, for protection purposes, to both radio directions
Vertical and Horizontal or Est and West.
With 1+0 XPIC configuration the ALCplu2e on the other side receives the two E1s and decides which one
to select on the basis of alarms.
With 2x(1+0) Est West configuration, if the equipment is part of a loop, the equipment is receiving the
two E1s and on the basis of alarms decides which incoming E1 to select.
MN.00224.E - 018 81
9.6 N+0 CONFIGURATION
The ALCplus2e can be configured with a number of ODU depending on frequency arrangement.
The following frequency arrangement definitions will be used. See Fig.36, Fig.37 and Fig.38.
9.6.2 GENERALS
ALCplus2e high capacity radio links N+0 are available in some configurations:
82 MN.00224.E - 018
• 2x(1+0) with hybrid coupler, two channels adjacent or not adjacent
• 2x(1+0) with circulator, two channels adjacent or not adjacent, low losses, narrow band ODU
• 4x(1+0) with XPIC, hybrid coupler, two not adjacent channels or two CCDP adjacent channels
• 4x(1+0) with XPIC, circulator, two not adjacent channels or two CCDP adjacent channels, low loss-
es, narrow band ODU
For maximum Ethernet throughput, depending on channel bandwidth, modulation, frame size and proto-
cols, please refer to relevant paragraph in this manual
MN.00224.E - 018 83
The solutions ALCplus2e 2x(1+0) with frequency reuse (XPIC) have the following characteristics:
• XPIC,
• Channel bandwidth: 14MHz, 28MHz, 40MHz, 56 MHz Horizontal and Vertical polarization
• No branching loss
84 MN.00224.E - 018
The solutions ALCplus2e 2x(1+0) with hybrid coupler two channels, adjacent and not adjacent, have the
following characteristics:
• No XPIC,
• Channel bandwidth: 14MHz, 28MHz, 40MHz, 56 MHz Horizontal and Vertical polarization
MN.00224.E - 018 85
The solutions ALCplus2e 2x(1+0) with circulator two channels not adjacent (ACAP) or two channels adja-
cent (ACCP), have the following characteristics:
• No XPIC,
• ODU:
- AS 28MHz single channel ACAP at 7, 13, 15 GHz, and AS 40MHz single channel ACAP 6U, 11 GHz
- High power ASN7HP 28MHz single channel ACCP, 7,1-7,4 and 7,4-7,7 GHz, other frequencies
available on request
9.6.6 4X(1+0) with XPIC and hybrid coupler two CCDP channels
86 MN.00224.E - 018
The solutions ALCplus2e 4x(1+0) with XPIC and hybrid coupler two not adjacent channels or CCDP adja-
cent channels have the following characteristics:
• XPIC,
• channel bandwidth: 14MHz, 28MHz, 40MHz, 56 MHz Horizontal and Vertical polarization
MN.00224.E - 018 87
The solutions ALCplus2e 4x(1+0) with XPIC, circulator coupler, two not adjacent channels or CCDP adja-
cent channels have the following characteristics:
• XPIC,
• ODU:
- AS 28MHz single channel, two not adjacent channels at 7, 13, 15 GHz, and AS 40MHz single
channel, two not adjacent at 6U, 11 GHz
- High power ASN7HP 28MHz single channel, CCDP, 7,1-7,4 and 7,4-7,7 GHz, other frequencies
available on request
ƒ1 ƒ2 ƒ4
28 28
88 MN.00224.E - 018
Fig.50 - 8x(1+0) with XPIC and multicirculator
The solutions ALCplus2e 8x(1+0) with XPIC, Multicirculators and 4 adjacent CCDP channels have the fol-
lowing characteristics:
• XPIC,
• ODU:
- High power ASN7HP 28MHz single channel CCDP, 7,1-7,4 and 7,4-7,7 GHz, other frequencies
available on request
See Fig.51.
MN.00224.E - 018 89
2 1
3 4
It is possible to select 4 frequency low or high . But the following limitation apply:
90 MN.00224.E - 018
Tab.14
CH 1,2,3,4 CH 2,3,4,5
7L band 7L band
9.7 SYNCHRONIZATION
Refer to Fig.52.
STM-1 frame generation requires that it is synchronised to a SDH network.
Into ALplus2e a synchronisation circuit, called SETS, gets the synchronisation signal from the following dif-
ferent sources:
• radio A
• radio B
• STM1(1)
• STM1 (2)
• tributary A/B
• tributary A/B as T3
• tributary nE1
• node1
• node2
• Internal source
As shown in Fig.52 the clocks extracted from the sources are sent to a selection circuit that chooses one
of the signals depending on the control sent by a selection logic.
This latter acts on the base of alarm roots (LOS-loss of input signal, LTI-loss of timing input, LOF-loss of
frame), on the base of assigned priority and manual forcing.
The selected clock drives an oscillator through a PLL circuit. The oscillator will generate the required inter-
nal synchronisation signal T0.
Trib A or B selected as T3 can be the source of T4 signal (2MHz) for other equipment like for example into
nodal structure.
If no input signals are available the internal oscillator source is used for the local restart of STM1 genera-
tion.
Synchronization quality is connected to synchronization source (SSM).
ALCplus2e manages quality information (synchronization status message SSM) from the following sources:
MN.00224.E - 018 91
• E1: tribA or triB for one 2Mbit/s within the 16 E1 available; quality info uses a spare bit of G.704
time slot 0 frame B.
• Ethernet (ITU G.8264): a dedicated slow protocol transfers quality info (second FW release)
Local Remote
SETS SETS
NBUS
STM-1 NBUS
LAN3, 4 STM-1
TRIB A= LAN3, 4
2MHz/2Mbit TRIB A=2MHz/2Mbit
TRIB B=2Mbit
TRIB B=2Mbit
TRIB 1-16=2Mbit TRIB 1-16=2Mbit
A node can be made up of max 8 subracks of ALCplus2e IDU so that we can have:
• up to 8 x 16E1 = 128E1
On the front panel of ALCplus2e there are two “NBUS” ports (1 and 2) which must be connected to the
other IDU subrack as in Fig.35 for E1 traffic and Ethernet traffic.
For Ethernet traffic Lan1 and Lan2 must be connected as in Fig.35 Lan1 and Lan2 connection can be made
with normal Lan cables CAT5e/CAT6.
NBUS connection among the IDUs are made by cables of CAT7 quality, only by proprietary SIAE cable to
insert into the NBUS connectors (1 and 2) on the front panel. See Tab.15 for cable length and SIAE code.
For any IDU into WebLCT it is necessary to define how many IDU are into the Node from 2 to 8. Into We-
bLCT each IDU must be defined as node number 1, 2...8.
92 MN.00224.E - 018
NBUS can operate in Protected mode or in Not Protected mode. Each NBUS carries 126 E1’s.
In case of Not Protected mode, all the 126 E1’s of the NBUS are used to connect a subrack to the others
for a total amount of 252 E1 connections available on NBUSes from one IDU.
In case of Protected mode, the unused connections, are used as protection of the connections between the
other IDUs; for example 63 E1’s are used between Node1 and Node2 and the other 63 E1’s are used as
protection of the connections between the other nodes, the connections used as protection pass into others
IDUs as passthrough without any need to be programmed. The troubles in the connections between the
NBUS buses are identified by alarms.
In case of protected modality, if the cable carrying the traffic is broken, an alarm is issued on the relevant
NBUS port, the equipment software switches the traffic on the other operating NBUS cable.
With SCT/LCT program it is possible to configure a Node made up of some Nodals so into the window of
Node Manager it is possible to program only one big Crossconnect matrix for E1 and only one Ethernet
switch for all Lan traffic.
The software hides all NBUS connection for E1 and Lan connection from an IDU to others IDUs, so to op-
erate on one big Crossconnection matrix and one big Ethernet switch.
For any IDU the Node Manager shows for E1s 16E1, STM1 E1s, radio permanent E1, radio extra E1 and for
Ethernet Lan3, Lan4, radio port Port A.
The Nodal equipment with SDH STM1 interface is a Regenerator Section Termination (RST) and a Multiplex
Section Termination (MST) therefore it generates the STM-1 frame and has an internal synchronization cir-
cuit SETS. The synchronization of the Node can be distributed on the NBUS.
The IDUs subracks must be synchronised together via NBUS or other interface.
For each Nodal subrack, the STM-1 interface can be duplicated (1+1 MSP) for the possible protection of
cable. The switching criteria in Rx are:
• Unequipped
• LOS
• LOF
• MSAIS
• TIM
• B2 excessive BER
• B2 degraded BER.
Suppose that the nodals 1 and 2 already exist and that you must add the nodal 3.
Disconnect the cable between NBUS1 nodal2 and NBUS2 nodal1, the traffic is automatically switched to
the other cable, if necessary.
Disconnect the cable between LAN1 nodal2 and LAN2 nodal1, the traffic is automatically switched to the
other cable, if necessary.
By WebLCT or SCT/LCT, re-program the nodal1 and nodal2 as node with 3 items.
By WebLCT or SCT/LCT, re-program the nodal3 as nodal3, protected and define the node with 3 items.
Connect the NBUS1 of the nodal2 with NBUS2 of nodal3, connect the NBUS1 of the nodal3 with NBUS2 of
the nodal1 as in Fig.35.
Connect the LAN1 of the nodal2 with LAN2 of nodal3, connect the LAN1 of the nodal3 with LAN2 of the
nodal1 as in Fig.35. By SCT/LCT, with Nodal ALCplus2 Manager, Nodal Configuration add nodal3 IP ad-
dress.
Program the interested cross-connections and Ethernet switch connections with external interfaces of
nodal3, Node Manager will take care of connections on NBUSes and LAN1, 2.
The same procedure can be used even if the added node is different from nodal3.
MN.00224.E - 018 93
9.8.2 Reduction from 3 to 2 IDUs
Suppose that the nodals 1, 2 and 3 already exist and that the nodal 3 must be removed.
By SCT/LCT, with ALCplus2/ALCplus2e Node Manager, delete all the cross-connections to the external in-
terfaces of nodal3.
The same procedure can be used even if the deleted nodal is different from nodal3.
Into WebLCT Configurator, Ethernet switch can be set as Enhanced = Absent, in this case the ALCplus2e
Ethernet functionalities are fully compatible to ALCplus2. With Enhanced = Present selection new Ethernet
fiunctionalities are present and are described in the following.
The external interfaces (4 operational on 6 present) are placed on the front panel. Internal port is repre-
sented by the local radio stream where, through native Ethernet transport, is connected with the remote
equipment.
Inside IDU is present an Ethernet switch with 4 external ports (electrical 1000BaseT or optical 1000BaseX)
and up two internal ports. Port 3 and Port 4 have both interfaces, Port 1 and Port 2 are electrical only.
The internal ports are represented by the local radio stream where through native Ethernet transport is
connected with the remote equipment. There is one internal port for 1+0 and 1+1 radio configuration.
In XPIC and in 2x(1+0) link configurations, two settings are available regarding the internal port:
• dual pipe - two internal ports (port A and port B), one for each polarization/direction
For Ethernet switch functionalities, please refer to chapter 8 ALCplus2 IDU DESCRIPTION.
• monitoring on service type (outer or inner VLAN TAG) counters based on CVLAN or SVLAN (second
FW release)
• QinQ selective VLAN based selective VLAN + priority based, port based
• 8 queues scheduler on Radio Port, with priority managed on all 8 queues, it is possible to select
whenever queue is full:
- Queue Drop: the queue is deleted, over a defined threshold all packets in the queue are discard-
ed to limit latency time on traffic within this queue
- RED (Random Early Discard) random automatic discard of packets, over a defined threshold
there is a defined high percentage of discarded, only for incoming packets to a port without CIR
(that is all packets have same priority)
- WRED (Waited Random Early Discard) random automatic discard of packets, over a defined
threshold there is a defined high percentage of discarded, only for incoming packets (green or
yellow coloured) to a port with CIR
• frame fragmentation: packets exiting on radio port are fragmented to reduce Latency Time Jitter
• CIR/EIR/Max rate management, at the input of any physical Lan port for the packets exiting from
radio port it is possible to define: CIR Committed Information Rate (minimum guaranteed rate),
94 MN.00224.E - 018
Excessive Information Rate (maximum bit rate if bandwidth is available) Max Rate (maximum bit
rate, rate control) for any Lan port, for any CVLAN, for any SVLAN
• OAM 802.1ag
LINK CONCATENATION
Link Concatenation is a feature available on SIAE ALCplus2e equipment that allows assigning up to two
physical links to one logical link that functions as a single, higher-speed link.
Link Concatenation works aggregating two radio interfaces (single pipe). With XPIC it aggregates radio
traffic from Vertical polarization and radio traffic from horizontal polarization. Traffic speed on the two po-
larization can be different.
Algorithm of packets distribution on the two radios are statistically and proportional to traffic capacity giv-
ing the maximum throughput from the two radios.
Warning: if the two radio interfaces carry a too unbalanced Ethernet traffic, the combined Ethernet traffic
may be blocked.
On radio side it is possible to enable the Packet Fragmentation at 256 or 512 bytes. Smaller packets give
the benefit of lower delay variation (jitter) on the other packets maybe at higher priority.
EPP
Enhanced Packet Processing (EPP) is the possibility to compress the fixed field into the packets. Up to 68
byte of headers can be affected by compression algorithm giving a higher benefit to small packets.
VLAN REWRITING
In the direction from Lan ports to Radio ports the Vid of tagged packets can be rewritten according the
maps defined into WebLCT.
With Fallback, Traffic Treatment=Transparent Port to Port Transport, Provider=Disable we can make a ta-
ble with: Input CVLAN Vid to Output CVLAN Vid
With Fallback, Traffic Treatment=Transparent Port to Port Transport, Provider=Enable C_Vid Based we can
make a table with: Input CVLAN Vid to Output CVLAN Vid and output SVLAN Vid
With Fallback, Traffic Treatment=Transparent Port to Port Transport, Provider=Enable C_Vid Priority we
can make a table with: Input CVLAN Vid and Input priority to Output SVLAN Vid.
In the direction from Lan ports to Radio ports MPLS packets are analysed in their Exp (Experimental) 3 bits
and sent into one of the 8 queues available to radio.
A programmable map into WebLCT defines for each value of Exp bits which queue (from 0 to 7 Max priority)
the packet will enter.
Another programmable map into WebLCT defines for each value of Exp bits which value of 802.1p priority
bit will be written into the Vlan Tag.
MN.00224.E - 018 95
CIR/EIR RATE MANAGEMENT / INPUT FILTER POLICY (e.g. LAN1)
Some definitions:
• CF Coupling Flag
Committed Information Rate (CIR): The bandwidth that the service provider guarantees to the cus-
tomer, regardless of network conditions.
Excess Information Rate (EIR): The bandwidth allowance for “best effort” delivery, for which service
performance is not guaranteed and traffic may be dropped if the network is congested.
The combination of CIR and EIR rates is typically referred to as PIR, or Peak Information Rate, which
represents the total burstable bandwidth sold to the customer.
Committed Burst Size (CBS): The maximum size, expressed in bytes, of a burst of back-to-back Ether-
net frames for guaranteed delivery.
Excess Burst Size (EBS): The maximum size of a burst of back-to-back Ethernet frames permitted into
the network without performance guarantees. EBS frames may be queued or discarded if bandwidth is not
available.
According to MEF 10.2 (Metro Ethernet Forum) specifications, the “bandwidth profile” service attribute (In-
put Filter Policing), which includes some or all of the above categories, can be defined per UNI, per EVC or
per CoS identifier (CoS ID; EVC.CoS). For any given frame, however, only one such model can apply. The
service provider meets the bandwidth guarantees by reserving appropriate network resources and employ-
ing a two-rate/three-colour (trTCM) rate-limitation methodology as part of its traffic engineering policy to
ensure compliance by user traffic.
For any port it is possible to add a Input Filter Policy table with this selections:
• Disable
96 MN.00224.E - 018
• Secure: two selections 1) EVC S_Vid/C_Vid Based: applied to a SVLAN S_Vid and a CVLAN C_Vid
with CIR, EIR, CBS and EBS; Cf disable is ok. 2) COS S_Vid/C_Vid + Priority Based: applied to a
SVLAN S_Vid and CVLAN C_Vid with priority range, CIR, EIR, CBS and EBS; Cf disable is ok.
Into ALCplus2e there is a total of 64 instances of Input Filter Policing for all the four ports into any radio
port.
Into same port same CVID can be reused but with different priority.
In the direction from Lan ports to Radio ports. Priority Management is dependant on the status of 802.1q
Management> 802.1q settings:
• Disable: you can select only Uni Port Based with CIR, EIR, CBS and EBS; Cf disable is ok.
• Fallback: two selections 1) EVC C_Vid Based: applied to a CVLAN C_Vid with CIR, EIR, CBS and
EBS; Cf disable is ok. 2) COS C_Vid + Priority Based: applied to a CVLAN C_Vid with priority range,
CIR, EIR, CBS and EBS; Cf disable is ok.
• Secure (C_Vid Filtering): five selections 1) Port Default: priority defined by Default port Priority, all
packets entering this port have the same priority; 2) Native 802.1p (C_Vid): priority defined by
802.1p field in the CVLAN C_Vid; 3) Native TOS/DSCP: priority defined by Level 3 IP TOS/DSCP; 4)
Native MPLS: priority defined by MPLS Exp bits; 5) 802.1p(C_PCP) rewrite with MPLS: priority de-
fined by PriorityLan to Radio > MPLS to 802.1p Rewrite (tab) map translation.
• Secure (S_Vid Filtering, Provider=on): six selections 1) Port Default: priority defined by Default port
Priority, all packets entering this port have the same priority; 2) Native 802.1p (S_Vid): priority
defined by 802.1p field in the SVLAN S_Vid; 3) Native TOS/DSCP: priority defined by Level 3 IP
TOS/DSCP; 4) Native MPLS: priority defined by MPLS Exp bits; 5) 802.1p(C_PCP) rewrite (of CV-
LAN) with MPLS: priority defined by PriorityLan to Radio > MPLS to 802.1p Rewrite (tab) map trans-
lation; 6) 802.1p(S_PCP) rewrite (of SVLAN) with MPLS: priority defined by PriorityLan to Radio >
MPLS to 802.1p Rewrite (tab) map translation.
Direction from Lan ports to Radio ports. Here you can select the input 802.1q: Disable, Fallback, Secure
mode.
You can select the Traffic Treatment with two possibilities: 1) Transparent Port to Port Transport; 2) Trans-
parent Bridge Port Based.
1. Transparent Port to Port Transport : this is a setting for a simple application with 4 segragated con-
nections Lan1 to remote Lan1, Lan2 to remote Lan2, Lan3 to remote Lan3, Lan4 to remote Lan4
with tagged and untagged traffic; some settings are needed locally and remote. Via radio (PortA)
the QinQ is used. From this configuration it is possible to add VLAN tags into Vlan Configuration
Table, prioritizing and OAM.
2. Transparent Bridge Port Based: this is a setting to create connections from radio port to Lan1,2,3,4
and from Lan1,2,3,4 to radio port.
With Provider> Enable C_Vid Based: into a tagged packet it is possible to rewrite from a defined Input
C_Vid to a defined Output C_Vid and add an Output S_Vid (a Service Vlan Identifier).
With Provider> Enable C_Vid + Priority: into a tagged packet, with a defined Input C_Vid and a defined
Input Priority it is possible to add an Output S_Vid (a Service Vlan Identifier).
A packet that locally is entering untagged, can be tagged on remote radio, with “Untag to Tag” checked.
MN.00224.E - 018 97
Queue Management Lan to Radio (e.g. Port A Enh.)
On radio Port A (and PortB if configured as 2x(1+0)) there are 8 Queues. Queue 8 has maximum priority.
For each queue length 128/256/512/1024 Kbit can be defined. Small queues have lower delay. Larger
queues have few drops.
Starting from lower priority queue, it is possible to use WFQ (Wait Fair Queue) exit policy. WFQ counts the
number of transmitted packets. For each Queue set as WFQ the queue priority can be defined changing
Weight value.
• Queue: if queue is full, all packets in the queue are dropped; packets are too old to be useful, so
all packets in the queue are dropped to reduce time delay at minimum;
See Fig.53.
• RED (Random Early Drop): no packet are dropped until Average Queue Occupation % reaches
Smin(G, Green), packets are dropped randomly until a percentage of Pmax and an Occupation %
of Smax(G) limits are reached, all packets are dropped over an Occupation % higher than Smax(G);
• RED Gentle (Enable): no packets are dropped until Average Queue Occupation % reaches Smin(G,
Green); with Average Queue Occupation % higher than Smin(G) and lower than Smax(G), packets
are dropped randomly with a percentage defined by the straight line between Smin(G)/0 and
Smax(G)/Pmax(G); with Average Queue Occupation % higher than Smax(G) the percentage of ran-
domly dropped packets is defined by the straight line between Smax(G)/Pmax(G) and Sgentle(G)/
100% ;
• WRED (Weighted Random Early Drop): Weighted RED is a two line RED; one line for Green packets,
one line for Yellow packets; Green and Yellow are defined by CIR and EIR into Input Filtering Policy
(Lan1,2,3,4);
no green packet is dropped until Average Queue Occupation % reaches Smin(G, Green);
no yellow packet is dropped until Average Queue Occupation % reaches Smin (Y, Yellow);
with Average Queue Occupation % higher than Smin(G) and lower than Smax(G) green packets are
dropped randomly with a percentage defined by the straight line between Smin(G)/0 and Smax(G)/
Pmax(G);
with Average Queue Occupation % higher than Smin(Y) and lower than Smax(Y) yellow packets are
dropped randomly with a percentage defined by the straight line between Smin(Y)/0 and Smax(Y)/
Pmax(Y);
all green packets are dropped over an Occupation % higher than Smax(G);
all packets are dropped over an Occupation % higher than Smax(Y);
98 MN.00224.E - 018
• WRED Gentle (Enable): Weighted RED is a two line RED; one line for Green packets, one line for
Yellow packets; Green and Yellow are defined by CIR and EIR into Input Filtering Policy
(Lan1,2,3,4);
for Green packets no packet is dropped until Average Queue Occupation % reaches Smin(G);
with Average Queue Occupation % higher than Smin(G) and lower than Smax(G) green packets are
dropped randomly with a percentage defined by the straight line between Smin(G)/0 and Smax(G)/
Pmax(G);
with Average Queue Occupation % higher than Smax(G), the percentage of dropped green packets
is defined by the straight line between Smax(G)/Pmax(G) and Sgentle(G)/100%;
for Yellow packets no packet is dropped until Average Queue Occupation % reaches Smin(Y);
with Average Queue Occupation % higher than Smin(Y) and lower than Smax(Y) green packets are
dropped randomly with a percentage defined by the straight line between Smin(Y)/0 and Smax(Y)/
Pmax(Y);
with Average Queue Occupation % higher than Smax(Y), the percentage of dropped green packets
is defined by the straight line between Smax(Y)/Pmax(Y) and Sgentle(Y)/100%;
WRED and WRED Gentle are very efficient to get the most from the radio link available traffic avoiding the
“stop and go” beavior (SAW trend) typical of congested TCP/IP traffic.
Warning: RED and WRED impact only TCP/IP traffic, not UDP traffic.
Link Aggregation (LAG) is a feature available on ALCplus2e equipment that allows assigning up to four
physical links to one logical link (trunk) that functions as a single, higher-speed link. In ALCplus2e LAG is
named Trunking and two different implementations are possible:
• Line trunking: it works by aggregating LAN interfaces.
Radio Trunking is available only when the Nodal Ethernet functionality is enabled. The nodal Ethernet con-
figuration can be deployed on all the ALCplus2e IDU models.
Line Trunking is available on the ALCplus2e IDU. ALCplus2e support IEEE 802.3ad LACP (Link Aggregation
Control Protocol). See Fig.54.
MN.00224.E - 018 99
LACP allows a network device to negotiate an automatic bundling of links by sending LACP packets to the
peer (directly connected device that also implements LACP). In addition to the increased capacity of the
logical link, LACP provides additional advantages:
• failover detection when a link fails, allowing for a trunk reconfiguration in order to avoid systematic
packet loss (after the reconfiguration the packets will be lost only if the throughput exceed the trunk
capacity).
• it introduces an agreement between the two LACP peers before to start data transmission over the
trunk. This prevent anomalous behaviour in case of cabling or configuration mistakes.
LACP works by sending frames (LACPDUs) over the links belonging to the trunk. Also the equipment de-
ployed on the other end of the trunk will send LACP frames over the same links: this enables the two units
to establish the trunk. LACP can be configured two modes: active or passive. In active mode it will always
send frames along the configured links. ALCplus2e implements an "active" LACP.
Each IDU allows to define up to 4 different trunks on its LAN interfaces. A Line Trunk can aggregate up to
4 LAN interfaces with the following restrictions:
• all the LAN interfaces must be defined with the same speed (either 10, 100 or 1000 Mbit/s).
• all the interfaces must belong to the same IDU, even if the IDU is deployed in Nodal Ethernet con-
figuration.
When a Trunk is defined on ALCplus2e, the end-to-end traffic is transmitted over all the aggregated lines.
As a results, the overall capacity of the trunk can be theoretically equal to the number of aggregated lines
multiplied by the capacity of a single line. In the example of Fig.27, four 100Mbs connection are grouped
into the same trunk, carrying all the capacity in transit from a radio link to another. In this configuration,
the theoretical maximum capacity that can transit on this trunk is 400 Mbit/s.
The packets carried by the trunk are assigned to each line depending on their Source MAC (SA) and Des-
tination MAC (DA) Addresses (MAC hashing).
A possible problem that could occur when Link Aggregation protocols are used is a change in the transmis-
sion order of packets belonging to the same logical session. The MAC hashing method prevents such a
problem: the traffic transmitted from one host to another one in the network (fixed SA and DA) is always
sent over the same physical line of the trunk, avoiding any order change.
If a line of the trunk fails (for example due to a cable disconnection), the LACP protocol automatically re-
configure the trunk group into a lower order trunk. So doing, the traffic that before was carried over the
failed line, now will be re-distributed over one of the remaining trunk lines, ensuring continuity to the traffic
transmission. The typical LAG reconfiguration time in case of a LAN cable failure is below 1 second.
Radio Link Trunking is a feature available on ALCplus2e equipment when deployed in Nodal Ethernet con-
figuration.
This feature allows to bundle up to 4 radio links to increase the capacity of an Ethernet connection between
two radio sites (see Fig.28).
Each Nodal Ethernet stack can belongs to one Radio Trunk. Each IDU of the trunk sends over the air only
a portion of the traffic, according to the same hashing rule used for the line trunking (see paragraph 8.6.1
Line Trunking). The traffic received from the radio trunk is sent towards the IDU where is located the out-
going interface according to standard MAC learning/switching mechanisms.
Resiliency between the radio links aggregated into the trunk is managed by means of a proprietary proto-
col. If a radio link of the trunk fails (due to fading or equipment failure), this protocol automatically recon-
figure the trunk group into a lower order trunk. In this way, the traffic that before was carried over the
failed link, now will be re-distributed over one of the remaining trunk lines, ensuring continuity to the traffic
transmission. The typical Radio Trunk reconfiguration time is about 600msec.
It is important to note that also if it could be possible to aggregate up to four 340Mbit/s radio links (by
using 56 MHz frequency channel with 256 QAM modulation), the maximum capacity that can be carried
over the radio link cannot exceed 1Gbit/s in each direction of transmission (referring to Fig.28, from Site
A to Site B and vice-versa).
ELP (Ethernet Line Protection) is a feature available on ALCplus2e IDU that allows to protect a GE interface
against cable failure or accidental disconnection. With ELP it is possible to connect an ALCplus2e IDU to
another network element by using two GE interfaces. Both interfaces are active but just one is enabled to
forward and receive traffic (forwarding state), while the other does not allow any traffic to pass (blocking
state). If the forwarding interface goes down, the other one passes to the forwarding state. The typical
switching time is around 1.5 sec. This feature does not imply the use of any protocol, but is simply based
on the status of the physical interfaces. As a consequence, no particular protocol support is required on
the connected equipment: it is simply required to enable the two GE interfaces.
When the Nodal Ethernet configuration is used, ELP can be used to protect the traffic of two GE interfaces
belonging to two different IDUs of the stack. In this way the traffic can be protected against IDU failure,
in addition to the cable protection.
This feature is particularly useful when the Nodal stack is connected to an external equipment like a core
router (see the example of the following Fig.29).
It is recommended to disable any Spanning Tree protocol on the external equipment: this could cause long-
er traffic recovery times.
As native Ethernet is originally designed for LAN (local Area Network), OAM is not included into the native
Ethernet network equipment. In order to provide a carrier grade service, the OAM protocol can be used in
any point-to-point Ethernet link (made up of a single radio link or many radio links). The aim of this pro-
tocol is to check and monitor the functionality of the service that the provider guarantees on the network.
The Service Layer OAM fully monitors a customer End-to-End Ethernet Service. Two main standards cover
this topic, the IEEE 802.1ag and ITU-T Y.1731.
The IEEE 802.1ag provides CFM (Connectivity Fault Management) useful for detecting, isolating and re-
porting connectivity faults. The ITU-T Y.1731 Standard comprehends the CFM plus some additional fea-
tures, like RDI (Remote Defect Indicator) that allows to report back to the start of the chain the Alarm
message.
ALCplus2e supports CFM according to both standards ITU-T Y.1731 and 802.1ag.
The IEEE 802.1ag and the ITU-T Y.1731 are End-to-End service, i.e. provides the tools to monitor the
Ethernet Service regardless of the layers, Network Path and operators. Since the spectrum of application
can include many applications a more hierarchical structure is needed.
• Maintenance Domains (MD): these specify the Domains of operators, users and service providers.
Levels from 0 to 7 are possible depending on the type of service to be monitored. Customer Domain
is the higher which includes both ends of the Ethernet service (from one End user to the other End
user), Standard Default values for Customer Domain are 7, 6 and 5. Service Provider Domains
should have a MD lower than the Customer Domain since include the whole network except the End
Users. Standard default values for Provider Domains are 3 and 4. Operator Domains are lower than
Service Provider Domains since just a part of the network is included. Standard Default values for
operator domains are 0, 1 and 2. A domain is transparent to all messages with higher priority while
blocking all lower priority messages. Fig.30 shows the hierarchical structure of Maintenance Do-
mains.
At each end of the Maintenance Domain two MEPs (Maintenance End Point) will be specified. One MEP is
local, the other one is in the remote equipment. The MEPs are "markers" that defines the end of a domain
and are in charge of originating OAM frames.
In a domain also MIPs (Maintenance Intermediate Points) can be specified. The MIPs are passive check-
points. The MEPs and MIPs configuration are discussed in details in the following points. The choice of the
domain that is the Domain Label (name) is left to the user. Particular attention must be paid to use exactly
the same MD label (and level) in each equipment where the MD is specified, i.e. different equipment with
same value of MD domain but different MD labels (or levels) belongs to different Domains.
• A Maintenance Association (MA) is one association which correlates the VLAN to the MD in which
the MEPs and MIPs have to be defined.
When a specified traffic needs to be monitored, then it is necessary to relay the VLAN to a Domain
and to the corresponding MEPs or MIPs through the MA. Before creating the Maintenance Associa-
tion, the VLAN, either SVLAN (Service VLAN Tag o Stacked VLAN Tag) or C-VLAN, has to be specified
in the VLAN Table. In each SIAE equipment it is possible to set up to 32 different MA. Particular
attention must be paid to use the same MA label in each equipment where the MA is specified, i.e.
different MA labels on the same VLAN correspond to different MA associations.
• At the Edge of a MD there are MEPs (Maintenance End Points) and in the middle there could be MIPs
(Maintenance Intermediate Points). MEPs are the units in charge of managing the CFM to correctly
monitor the status of the Ethernet service provided. MIPs are passive check-points that answer to
polling coming from MEPs. MEPs will forward OAM messages coming from higher domains and will
discard OAM messages generated from lower domains.
Each interface can be configured as MEP, Port A interface (radio interface) included. Once chosen
the interface, depending on the network topology, the direction of the MEP has to be specified. Two
Directions are possible, MEP "up" and MEP "Down". With MEP "Down" configured the OAM PDUs are
sent from the interface in the direction outside the equipment, i.e. the OAM PDUs are sent from the
interface on the cable toward next equipment. With MEP "Up" configured the OAM PDUs are sent
from the interface toward the inside of the equipment and will follow the VLAN table previously con-
figured. MEPs are distinguished from each other through a MEP ID, therefore MEPs belonging to
same MA must have different MEP Ids. In order to configure a MIP the MA has to be enabled on the
equipment. Up to 32 MIPs or MEPs can be configured on each equipment.
The protocols belonging to the Connectivity Fault Management implemented in SIAE equipment are follow-
ing listed:
• Continuity Check Protocol: this protocol enables the sending of a periodic message (like a Heartbeat
message) which enables the other MEPs deployed in the network to distinguish the status of a vir-
tual connection. This message can only be originated by a MEP. Time between messages is adjust-
able with 1s, 10s, 1min, 10min. These messages do not trigger any automatic reply from the
destination entity.
• LoopBack Protocol: it resembles an IP PING message; once this message is sent (e.g. MEP1 sends
a Loopback Message to MEP2). MEP2 replies to MEP1 confirming therefore the status of the connec-
tion. This is done to check the status of the connection between the MEP originating the message
and the MEP/MIP to which the message is addressed. This message can only be originated from one
MEP and can be addressed to both MEPs or MIPs. ALCplus2e: The number of Loopback Messages in
ALCplus2e is adjustable from 1 to 5 consecutive Loopbacks. In each equipment, it is possible for
each MEP to check the presence of other MEPs in the same MA. This is done through the "Remote
MEP" application which allows this acknowledgement and distinguishes the other MEP through
means of MEP IDs and MAC address.
• Link Trace Protocol: This protocol sends a message similar to the LoopBack protocol. Every equip-
ment that is reached by this message will answer to the sender providing its own MAC Address. In
this way the sender is able to understand of which equipment the MA is composed. E.g. a MEP sends
the Link Trace Message to another MEP belonging to the same Maintenance Association. The MIPs
• Remote Defect Indicator: This Feature allows a MEP, in presence of a fault or a defect, to send a
RDI to inform the other MEPs, belonging to the same MA, of the presence of this Defect. The ad-
vantages of this procedure are to avoid multiple Alarms created by the same cause and to be able
to check the status of other Remote MEPs. This RDI information is reported in the Continuity Check
Message. ALCplus2e: This feature is present in ALCplus2e equipment and the presence of this alarm
can be checked as well in the Remote MEPs screen on the equipment.
As an example, let's consider a network where a sequence of 8 SIAE ALCplus2e Radio links is deployed. In
this case a Maintenance Domain, a VLAN and a Maintenance Association have to be defined. The VLAN car-
rying the traffic must be present in the VLAN table of each equipment.
Two MEPs at the end of the chains and a variable number of MIPs in the middle has to be defined with
Continuity Check Message (CCM) enabled.
In case of defect or Ethernet problem, the Continuity Check Message will result in an "Inactive" status trig-
gering one Alarm.
By logging on one MEP it is sufficient to configure the Loopback message and Link Trace Message correctly
detects the location of the Bottleneck or defect related to this traffic. If More than one VLAN is present then
more than one MA has to be defined.
In this chapter are described the new features available with new firmware releases.
Every firmware release is included in a System Version and is supplied with the right WebLCT version.
FW update procedure
1. FW_Boot E82103
2. FW_appl N90656
3. WEBLCT N96109
All the files are in a compressed container called System Version v.XX.YY.ZZ.
When SyncE is not available in all transmission chain, the synchronization protocol IEEE 1588v2 can be
used: this synchronization protocol allows distributing the CK through the network by means of protocol
packets.
The IEEE1588v2 is based on time stamps sent from a Master Clock Source to one or more Slave.
In one link both sides can be elected as Master but not at the same time : if one side is Master, the other
is Slave.
Enabling IEEE 1588 Pass Through an extra queue with maximum priority is generated. The transit delay
on radio link at different modulation is fixed. Jitter on 1588 packets is reduced activating packet fragmen-
tation.
The acknowledgement of the 1588 Frames in ALCplus2e can be done depending on different sections of
the header with different filtering options, listed below, that are mutually exclusive. It is possible to con-
figure:
• UDP based PTP Filtering (destination Port) - Default Configuration: the 1588 Frames are filtered
based on the Destination port (319 or 320 depending on the type of 1588 frames)
• Ethernet based PTP Filtering: The 1588 frames are filtered based on the Ethertype (Ox88F7)
• C-TAG based PTP Filtering: The 1588 frames are filtered amongst all the traffic marked with a pre-
cise C-Tag.
• S-TAG based PTP Filtering: The 1588 frames are filtered amongst all the traffic marked with a pre-
cise S-Tag.
• C-TAG+S-TAG based PTP Filtering: The 1588 frames are filtered amongst all the traffic marked with
a precise Combination of C-Tag and S-Tag.
By enabling this "Pass Through" on 1588 Frames, the equipment automatically enables the "Ethernet
Frames Fragmentation" to 256 Bytes.
RMON
RMON (Remote Monitoring) is a standard whose function is providing a set of services of statistics count,
monitoring and alarm report with reference to the activity of a LAN network.
SIAE NMS systems collect periodically RMON data and store it into the network database.
The RMON implementation in SIAE Network Elements is classified into two groups:
1. RMON - Statistics
2. RMON - History
From Firmware release 1.3.1, RMON is available also on VLAN basis and Priority basis and can be shown
into SIAE NMS software.
FADE MARGIN
After installation of radio link and before assign traffic to it, it is possible to test and compare the "calcu-
lated" fade margin from link budget with "real fade margin verified" supplied as result after the fade margin
test.
This result can be printed and used as a benchmark of the quality of the installation.
In case of 1+1 configuration the test is applied on all the four ODU. Each of the four TX are attenuated one
by one reaching the threshold at opposite RX side (both radios) so measuring the link fade margin.
Into LAN1, 2, 3, 4 ports in the 802.1q Management card, when the 802.1q setting is set "Disabled", the
Service Tag can be defined by the user for each port of the switch.
ALCplus2e is now compatible with new SFP modules: 1000BaseLX 40Km and 80 Km. Optical plugin mod-
ules must be supplied by SIAE.
In each of the four LAN port the autonegotiation can be limited up to 10 Mbps, 100 Mbps, 1 Gbps.
From this firmware release it is available the header compression for packets with Ethernet over MPLS over
Ethernet.
From this firmware release it is available the management of SSM, Synchronization Status Messages.
SSM allows:
• the presence of two synch sources to all the network elements, a primary and a secondary source
in case of a primary failure
SSM can be enabled on all the LAN ports in order to distribute the Quality of the clock, according Rec.
G.8264/Y.1364.
VLAN on Management port 1 and on Management port 2 can be defined independently. Management ports
can communicate, without VLAN, with/without VLAN, only with VLAN.
For Lan ports the PIRL (Port Ingress Rate Limiter) can be defined for Broadcast, Unknown Multicast, Un-
known Unicast, Unicast, ARP packets.
SSH security
New IDUs with updated hardware allow new features that are available with firmware release 1.5.0
• HW PWE3 ready
STM-1 bulk transmission is possible with compatible HW (see detailed IDU part number into IDU compo-
sition chapter at the end of the manual)
STM-1 transmission is possible only with channel bandwidth of 56 MHz, 40 MHz, 28 MHz.
HW PWE3 ready
PWE3 (Pseudowire Emulation Edge to Edge) is a protocol to transfer a point to point TDM connection via
Ethernet network.
PWE3 will be possible only with compatible HW (see detailed IDU part number into IDU composition chapter
at the end of the manual).
ACM setting
This release increases the range of CWDM SFP modules that can be used in the IDU.
Ethernet Ring Protection Switching, or ERPS, (ITU-T G.8032 Rec.) provides sub-50ms protection and
recovery switching for Ethernet traffic in a ring topology and at the same time ensuring that there are no
loops formed at the Ethernet layer.
SNMP-V3 management
SNMPv3 defines a secure versione of SNMP and facilitates remote configuration of the SNMP entities.
This features allows activating an additional ACM power mode named “Ramp to max Power”. If no atten-
uation is applied to the link (i.e. RTPC=0), the “Ramp to Max. Power” mode has the same behaviour of
the “Ramp to Ref. Modulation” mode. Both the power modes automatically set the equipment transmitted
power according to the active modulation, as follows:
• from Upper Modulation to Reference Modulation: the Tx power increases according to the active
modulation
• from Reference Modulation to Lower Modulation: the Tx power keeps constant in order to comply
with the Reference modulation mask.
If the equipment transmitted power is limited by means of a fixed attenuation (i.e. RTPC>0), the “Ramp
to Max. Power” mode allows the equipment to reach for each modulation the maximum “allowed” power
(i.e. the highest value between the maximum Tx power of the modulation and the maximum equipment
power set by the user).
The following buffer configurations are available on the 8 output queues of the radio port:
• each queue is configurable from 128 kbit to 128 Mbit (see the below screenshot of the queue con-
figuration)
• every radio port has a total available buffer of 184 Mbit (23 Mbyte), so the sum of the 8 output
queues lengths of a single radio port does not have to exceed this value.
In addition to the Ethernet Counters per Port, it is possible to set on the Radio port the RMON counters per
Service (Vlan) or Priority (Queues). Differently from the previous RMON counters, the Service and Priority
counters can be activated for the following variables.
• Octets Tx: total number of octets of data (including those in bad packets) transmitted.
• Octets Rx: total numbers of octets of data (including those in bad packets) received by the interface.
• DropEvents: total number of events (frames) in which packets were dropped by the interface due
to lack of resources.
The Service and Priority RMON can be activated and collected from NMS (Network Management System).
The Service and Priority RMON are based on the Advanced Ethernet Counters present on the equipment
and configurable on site. This means that on site it is possible to activate the Advanced Ethernet Counters
but not the Service and Priority RMON.
In any case the NMS has higher priority in respect to the configuration inserted by WebLCT.
This means that the local operator can enable and read the active measure, but when the configuration of
these RMON is done through NMS, the local operator can only read the values of the Advanced Ethernet
Counters.
It is not possible to enable the RMON for Priority and, in the same equipment, the RMON per Vlan.
• the maximum number of RMON (Priority) that can be enabled are limited to 8, i.e. the number of
the queues available in ALCplus2e equipment.
• if traffic with different priorities are listed in the same queue, the Priority RMON will work with one
Probe on the Queue. I.e. the traffic in the same Queue is seen as “Same Priority Traffic” and the
Priority RMON counts the frames belonging to the Queue.
In other words, with Priority RMON there is a probe for each queue (8 queues in ALCplus2e). Each probe
counts the variables listed above (Octets Tx, Pkts Tx, Octets Rx, Pkts Rx and Drop Events).
These counters will be available only with the Minimum Polling Policy of 15 min.
Service RMON: it allows the equipment to track the variables listed above depending on the Service (Vlan
Tag). This type of RMON can be set only on the Radio interface.
Each equipment can be set to collect RMON up to 32 Services (Vlan Tag) and only on Customer Tag. These
counters will be available only with the Minimum Polling Policy of 15 min.
This feature allows adding/removing a Tag on the Q3 ports (MNGT1 and MNGT2) by configuring the MNGT
ports in Secure Mode while in the past it was only possible to enable the VLAN Tagging in Fallback mode
on MNGT ports.
The Q3 ports could be set in Secure mode (“Enable Secure”) with specifying the VLAN ID the Ethernet traf-
fic has to be tagged by.
This feature allows limiting the egress throughput of the ALCplus2e LAN interfaces, by properly exploiting
the buffer of this port.
The egress shaping rate can be configured with the following values:
• if Egress Rate < 1Mbit/s: 64kbit/s, 128 kbit/s, 256 kbit/s, 512 kbit/s
• if Egress Rate > 1 Mbit/s & Egress Rate <10 Mbit/s: values with granularity of 1 Mbit/s
• if Egress Rate > 10 Mbit/s (up to 1 Gbit/s): values with granularity of 10 Mbit/s.
In this way each Ethernet port has separate limits for input and output throughput.
In some cases, the radio link failure can be unidirectional, for example when the local equipment has an
Rx signal failure but the remote Rx signal is OK (i.e. unidirectional radio fail due to failure of a transmitter).
However, also in these cases there can be the need to shutdown the link in both directions even if there is
only a unidirectional link failure.
Using the bidirectional LLF feature, in case of LLF in the local equipment, the local equipment can notify
this LLF status to the remote equipment, shutting down the link on both directions.
This feature allows a secure HTTP connection with WebLCT, in addition to the already existing HTTP con-
nection.
• HTTP/HTTPS protocols have been implemented in an exclusive way, so that, when a user is con-
nected using HTTPS, HTTP requests will be redirected in HTTPS and vice versa. So, when the user
connects to the IP address of the equipment by means of a Web browser, it is automatically con-
nected through HTTP or HTTPS depending on the WebLCT security configuration
• C.A. Certificate and SSL Certificate provide the encryption keys for the secure connection. These
certificates can be uploaded on the equipment through Certificate Upload Manager on WebLCT.
• The user can switch to HTTPS only if the SSL certificates have been uploaded on the equipment.
In order to switch the WebLCT to HTTPS, the following steps have to be followed:
3. Re-load the equipment web page and make a new HTTPS login.
Management of the following feature keys: Ethernet header compression, G.8032, STM1-bulk, secu-
rity package.
From this fw release the following functionalities can be enabled by means of a specific SIAE feature key.
EVC S-Vid Based (Bandwidth Profile per S_VID): a different profile is defined for different Service VLANs.
Up to 64 VLAN can be managed with different profiles.
COS S_Vid + Internal Priority (Bandwidth Profiles per S_VID+CoS): a different profile is defined for dif-
ferent couples S_VID+priority queue (up to 64 different cases can be managed). In this case the priority
queue from 0 to 7 (i.e. internal switch priority) is considered by the rate limiting algorithm and indepen-
dently from the enabled QoS management (e.g. IEEE 802.1p, IPv4 ToS/DSCP, IPv6 TC/DSCOP).
Possibility to define two different rules inside the switch, port to port, to forward the
incoming frames: destination address + VID basis (bridge scenario) or VID basis
(pipe scenario).
This new feature allows the user to set the MAC forwarding rule od each LAN interface (i.e. LAN1, LAN2,
LAN3 and LAN4). Two different forwarding rules are available:
Destination Address + VID Basis: packets are forwarded on the basis of their destination MAC address and
VLAN ID. This is most commonly deployed rule (I.e. default setting).
VID Basis: packets are forwarded on the basis of their VLANID. The destination MAC address is NOT con-
sidered in this case. This rule is used only in some specific cases.
All the management packets sent towards MNGT1 and MNGT2 ports and towards radio EOC have priority
1 (802.1p)
In the following are described the new features available in ALCplus2e 1+1 XPIC with new firmware releas-
es. Only the main releases are considered (....the firmware releases with new features).
Every firmware release is included in a System Version and is supplied with the right WebLCT version.
The MAC address in the MAC address Table can be managed also in this way
• MAC Learning on Vid Basis: MAC address table can be managed depending on Vid
• MAC on port basis: MAC address table can be managed depending on port.
• Auto-Speed-Dplx (the speed is set automatically during the handshake of the interfaces).
Bandwidth available
10E1 expansion
IDU with expansion 16E1 an relevant cross-connection matrix can be managed and used.
The SSM management (quality status of a synch source) is available on the following sources:
• STM-1
• Nodal Bus
SSM allows:
• the presence of two synch sources to all the network elements, a primary and a secondary source
in case of a primary failure
OAM
The Service Layer OAM fully monitors a customer End-to-End Ethernet Service. Two main standards cover
this topic, the IEEE 802.1ag and ITU-T Y.1731.
The IEEE 802.1ag provides CFM (Connectivity Fault Management) useful for detecting, isolating and re-
porting connectivity faults. The ITU-T Y.1731 Standard comprehends the CFM plus some additional fea-
tures like RDI (Remote Defect Indicator) that allows to report back to the start of the chain the Alarm
message.
SIAE ALCplus2e supports CFM according to both standards ITU-T Y.1731 and 802.1ag.
The IEEE 802.1ag and the ITU-T Y.1731 are End-to-End service, i.e. provides the tools to monitor the
Ethernet Service regardless of the layers, Network Path and operators.
SSM can be enabled on all the LAN ports in order to distribute the Quality of the clock, according rec.
G.8264/Y.1364.
New values are available in each LAN port to limit the input throughput (PIRL - Port based Ingress Rate
Limiting).
up to 32E1
NBUS1
NBUS2
Trib A/B
Port A
LAN1 Switch
LAN2
LAN3
LAN4
Slave
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16
1 2 1 2
2
2 M 3.15A
ON 250V
MNGT NBUS 48V
LAN 3 LAN 4 1 2 NURG URG
1 1
LCT
R SW
+
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16 Trib. 17-24 Trib. 25-32
1 2 2
2
ON M 3.15A 48V
MNGT LAN 3 LAN 4 1 2 250V
NURG URG
1 1
LCT
R SW
+
GREEN LINK LAN 1 LAN 3 Trib. A USER IN/OUT TEST ON -
XPIC
XPIC
The ODU (refer to Fig.59) consists of a two shell aluminium mechanical structure, one shell housing all the
ODU circuits, the other forming the covering plate.
• one “N” type connector for IF cable interfacing IDU and ODU
• one “BNC” connector for connection to a multimeter with the purpose to measure the received field
strength
The 1+1 configuration consists of two ODUs mechanically secured to a structure housing the hybrid circu-
lator or branching unit for the connection towards the antenna.
10.1.1 AS ODU
The AS ODU is shown in Fig.59 (single ODU) and in Fig.60 (1+1 ODU with branching unit). Electrical and
mechanical characteristics are listed in a separate addendum relevant to ODU frequency.
The ASN ODU is shown in Fig.59 (single ODU) and in Fig.60 (1+1 ODU with branching unit). Electrical and
mechanical characteristics are listed in a separate addendum relevant to ODU frequency.
The ASNK ODU is shown in Fig.60 (single ODU with F15 GHz) and in Fig.61 (single ODU with F15 GHz).
Electrical and mechanical characteristics are listed in a separate addendum relevant to ODU frequency.
• cable interface
• power supply
• Tx section
• Rx section
The cable interface permits to interface the IF cable interconnecting IDU to ODU and viceversa.
It receives/transmits the following signals:
The 17.5 MHz and 5.5 MHz FSK modulated carriers, carry the telemetry channel. This latter consists of two
388 kbit/s streams one from IDU to ODU with the information to manage the ODU (RF power, RF frequen-
cy, capacity, etc...) while the other, from ODU to IDU, sends back to IDU measurements and alarms of the
ODU. The ODU management is made by a µP.
The battery voltage is dropped from the IF cable interface and then sent to a DC/DC converter to generate
three stabilized output voltages to be distributed to the ODU circuitry.
10.5 TX SECTION
The 330 MHz QAM modulated carrier from the cable interface (see chapter 10.3 IF CABLE INTERFACE) is
forwarded to a mixer passing through a cable equalizer for cable loss compensation up to 40 dB at 330
MHz. The mixer and the following bandpass filter give rise to a second IF Tx carrier the frequency of which
depends on the go/return frequency value. The mixer is of SHP type.
The power at the MMIC output can be manually attenuated by 40 dB, 1 dB step (20dB, 1dB step for ASN
or 30dB, 1dB step for ASNK).
The automatic adjustment is performed making use of an ATPC (see paragraph 10.5.1 ATPC operation for
details). The regulated output power is kept constant against amplifier stage gain variation by a feedback
including the AGC.
Before reaching the antenna side the RF signal at the output of MMIC passes through the following circuits:
A particular setting of Tx and Rx RF oscillators allows to obtain a RF Loop, managed by Controller module.
The particular way used to perform the RF loop avoids the necessity to switch off the remote Transmitter.
RF Loop is available in AS ODU only.
The ATPC regulates the RF output power of the local transmitter depending on the value of the RF level at
the remote terminal. This value has to be preset from the local terminal as threshold high and low. The
difference between the two thresholds must be equal or higher than 3 dB.
As soon as the received level crosses the preset threshold level low (see Fig.65) due to the increase of the
hop attenuation, a microP at the received side of the remote terminal sends back to the local terminal a
control to increase the transmitted power. The maximum ATPC range is 40 dB (only in ASN and ASNK).
If the hop attenuation decreases and the threshold high is crossed then the control sent by the microP
causes the output power to decrease.
The maximum ATPC range is 40dB for AS ODU (20dB in ASN ODU, 30dB in ASNK ODU).
10.6 RX SECTION
The RF signal from the Rx passband filter is sent to a low noise amplifier that improves the receiver sen-
sitivity. The following down–converter translates the RF frequency to approximately 765 MHz. The conver-
sion mixer is SSB type. The sideband selection is given through a µP control.
A second down converter generates the 140 MHz IF carrier to be sent to the demodulator within the IDU.
The level of the IF carrier is kept constant to –5 dBm thank to the IF amplifier stages, AGC controlled,
distributed in the IF chain.
Between two amplifiers a passband filter assures the required selectivity to the receiver. The filter is SAW
type and the bandwidth depends on the transmitted capacity.
The two ODUs are coupled to the antenna side via a balanced or unbalanced hybrid in case of 1+1 hot
stand-by.
The two ODUs are coupled to the antenna side via a circulator in case of 1+1 frequency diversity.
1+1 Tx switching occurs in the 1+1 hot stand–by 1 antenna or 2 antennas versions as shown in Fig.63 and
Fig.64.
The transmitter switchover is controlled by Processor and the attenuation of the stand-by transmitter is
at least 50 dB.
O-ring
ODU side flange
ASN version
ASNK version (for frequency ≤ 15 GHz)
"N"
"BNC"
Ground bolt
AS version
AS version
x
N type 330
Cable MHz Cable IF Tx
interface equaliz. T
MMIC
140 LNA
MHz
variable 140
µP bandwidth MHz
(capacity Rx LO
depending)
AGC
µP
MN.00224.E - 018
Tx side
SW control
Rx side
Antenna
side
Tx side
SW control
Rx side
Tx side
SW control
First
antenna
Rx side
Tx side
SW control
Second
antenna
Rx side
Local Remote
Tx Rx
Thresh High
PTx actuation PRx recording
Thresh Low level
μP μP
PTx control
Transmission
Rx Tx
of PTx control
Local PTx
dBm
PTx max.
40 dB (ODU AS)
20 dB (ODU ASN)
ATPC range
PTx min.
The equipment is a split mount (indoor-outdoor) radio link system operating in the frequency ranges 4, 6,
7, 8, 13, 15, 18, 23, 25, 28 and 38 GHz, for low, medium and high transport capacity (from 4 up to 622
Mbit/s), designed to establish LAN-LAN connections and PDH/SDH access. For the details related to the
actual used frequency band refer to the label on the equipment.
The system is provided with an integral antenna; however, in case its antenna is not used, it should be
connected to an antenna conforming to the requirements of ETSI EN 302 217-4-2 for the relevant frequen-
cy band.
• Baseband (indoor)
Warning: Class 2 radio equipment subject to Authorisation of use. The equipment can operate only at the
frequencies authorised by the relevant National Authority.
Warning: The deployment and use of this equipment shall be made in agreement with the national regu-
lation for the Protection from Exposure to Electromagnetic Field.
Warning: The symbol indicates that, within the European Union, the product is subject to separate
collection at the product end-of-life. Do not dispose of these products as unsorted municipal waste. For
more information, please contact the relevant supplier for verifying the procedure of correct disposal.
The equipment consists of IDU and ODU(s) units and is mechanically made up of a wired 19” subrack (IDU)
and a weather proof metallic container (ODU). The two units are shipped together in an appropriate card-
board box.
After unpacking, mechanical installation takes place followed by electrical connections as described in the
following paragraphs.
The installation phases of the whole system are described in the following paragraphs and it must be done
only by service person suitably trained.
11.3.1 IDU
On their sides the subracks making up the several IDU versions are provided with two holes for the M6
screws fastening the subracks to a rack or to a 19” mechanical structure. The front of the IDU mechanical
structure is provided with the holes at the sides. This permits to fasten the subrack to a 19” rack by means
of 4 M6 screws.
ALPlus2 - To avoid overtemperature problems the free space below and above an IDU must be 22 mm
(1/2RU) minimum.
The electrical wiring must be done using appropriate cables thus assuring the equipment responds to the
electromagnetic compatibility standards.
The cable terminates to flying connectors which have to be connected to the corresponding connectors on
the equipment front.
Position and pin–out of the equipment connectors are available in this section.
Tab.15 shows the characteristics of the cables to be used and the flying connector types.
a. Select the correct size and type of cable for any installation case according to specific
length.
b. Power cable operative temperature 60°C.
c. Max length 2.5 m.
In case of necessity of optical connectors, please use the optical plug-in modules supplied by SIAE. Ask
SIAE Microelettronica for different modules.
During the final installation, the IDU must be protected by a magneto-thermal switch (not supplied with
the equipment), whose characteristics must comply with the laws in force in one's country.
The disconnection from the supply mains is made disconnecting the connector SUB-D 3W3 from the IDU.
- Return loss (connectors included) better than 22 dB (from 100 MHz to 400 MHz)
- Shielding effectiveness 90 dB
11.7.2 Connectors
With the 1/4” cable, the max length is 300m for all modulation profile.
With 1/8” cable, any length that respects max 24dB at 330 MHz and a Max total DC resistance of 4 Ohm.
RG8 or 1/4” cable on any coaxial cable that respect the previous electrical characteristics.
Fig.66 and annexed legend show how to perform the grounding connections.
Indoor 3 4
3 4
ODU
unit
1 5
7 IDU 2
unit
(+) (-)
6
Station Local
ground ground
ground
rack
Legend
1. IDU grounding point, copper faston type. The cross section area of the cable used must be ³ 4 sq.
mm. The Faston is available on the IDU both sides.
2. ODU grounding M6 bolt copper faston type. The cross section area of the cable used must be ³ 16
sq. mm (V60052)
3. IDU–ODU interconnection cable type Celflex CUH 1/4” or RG8 cable terminated with N–type male
connectors at both sides.
4. Grounding kit type Cabel Metal or similar to connect the shield of interconnection cable.
5. Matching cable (tail) terminated with SMA male and N female connectors.
6. Battery grounding point of IDU to be connected to earth by means of a cable with a section area
2.5 sq. mm. Length 10 m.
7. Grounding cords connected to a real earth internal of station. The cross section area of the cable
must be 16 sq. mm
• grounding kit
• a short tape (to define the part of the jacket to remove from the cable)
In order to install the grounding kit, follow the instructions supplied with the kit itself and position the kit
in the proper points along the IDU-ODU cable (position and number of the points can vary depending on
local rules and/or customer request).
After grounding kit installation, it is necessary to seal it. Please, use two kinds of tape in the following or-
der:
• apply the first (of two) layer of sealing tape overlapping the IDU-ODU cable jacket by 3 cm on each
ends. The layer must cover 3cm of cable before the grounding clamp, the clamp itself and 3 cm
after the clamp.
The grounding bolt (opposite to the grounding clamp of the kit) must remain without sealing.
Fig.67
2. insert one end of the tin copper tube of 3 mm of diameter in the relevant hole over the plate copper
bar of the grounding kit
4. put the plate copper bar over the shield of the cable and tie firmly the plate to the cable using the
tin copper tube. When the tin copper tube is over, wedge its end inside a notch of the plate in order
to fix it
5. apply two layers of vinyl mastic self amalgamating waterproof tape overlapping the IDU-ODU cable
jacket by 3 cm on each ends as in Fig.68. Every wrapping must overlap the previous.
6. Apply two layers of black PVC UV proof tape overlapping the waterproof tape layers as in Fig.68.
Every wrapping must overlap the previous.
The grounding bolt (opposite to the grounding clamp of the kit) must remain without sealing.
Characteristics
The front panel of the ALplus2 modular IDU is made up by the front panels of the modules LIM, RIM and
Controller. See Fig.69.
Electrical port 1 and port 2 can be configured MDI or MDIX via WebLCT.
• Trib 9-16, 75 Ohm and 120 Ohm E1 in/out 50 pin SCSI female
(Tab.17 for 75Ohm and Tab.18
for 120Ohm)
E1, 75 Ohm and 120 Ohm interfaces are present in the same connector (different pins).
• Connector for 50 Ohm interconnection to ODU SMA (max tightening torque = 0.5 Nm)
Port MNGT/1 and port MNGT/2 set MDI or MDIX status automatically.
Ethernet Power
IDU-ODU
Port 1 Port 2 Port 3 2xSTM-1 16E1 cable supply
1 2 3 ON 48V
SPEED
PoE
ACT FAIL
LINK
+
10-100-1000 BaseT/100-1000 BaseX 1 STM1 2 Trib: 1-8 Trib: 9-16
-
LINK LINK IDU ODU 48V
ACT ACT WAY
SIDE
+
REM TEST
LCT RS232 USER IN/OUT MNGT/1 MNGT/2 CH1 CH2 2Mb/s -
Function
Pin RJ45
10/100BaseT 1000BaseT
4 nc BI_DD+
5 nc BI_DD-
7 nc BI_DC+
8 nc BI_DC-
Pin 75 Ohm
48 Ground A
50 Ground A
47 Ground A
45 Ground A
42 Ground A
43 Ground A
40 Ground A
39 Ground A
36 Ground B
37 Ground B
34 Ground B
33 Ground B
29 Ground B
31 Ground B
28 Ground B
26 Ground B
Note: Join pin 44 with ground A pins, join pin 32 with ground B pins.
25 1
.........................
.........................
50 26
44 Ground A
44 Ground A
44 Ground A
44 Ground A
44 Ground A
44 Ground A
44 Ground A
44 Ground A
32 Ground B
32 Ground B
32 Ground B
32 Ground B
32 Ground B
32 Ground B
32 Ground B
2 Tributary 8/16output
32 Ground B
25 1
.........................
.........................
50 26
Pin Description
1 DCD (IN)
2 RD (IN)
3 TD (OUT)
4 DTR (OUT)
5 GND
6 Not connected
7 RTS (OUT)
8 CTS (IN)
9 Not connected
Pin Description
5 User input 01
6 User input 02
7 User input 03
8 User input 04
9 Ground
Tab.21 - MNGT/1 and MNGT/2 100BaseT connector pin-out for 10/100BaseT Ethernet connec-
tion (RJ45)
Pin Description
1 Tx+
2 Tx-
3 Rx+
4 --
5 --
6 Rx-
7 --
8 --
Tab.22 - CH2 connector pin-out for 64 kbit/s channel - V.11 interface (RJ45)
Pin Description
1 D-V11-Tx
2 D+V11-Tx
3 C-V11-Tx
4 C+V11-Tx
5 D-V11-Rx
6 D+V11-Rx
7 C-V11-Rx
8 C+V11-Rx
Pin Description
3 GND
7 GND
The front panel of the ALCplus2 IDU is made up by various connectors depending on IDU version: in the
following type of connectors and relevant pin-out are listed. On the body of each IDU there is the ground
connection: 6.3mm male (Faston).
In Fig.7 and Fig.8 are shown the 1+0 and 1+1 version. The following connectors are available:
• MNGT1, 2 management
Port MNGT 1, 2 set MDI or MDIX status automatically RJ45 (Tab.21)
3 GND
7 GND
1 C relay contact
2 NO relay contact
3 User Input 01
4 User Input 02
5 Ground
6 Do not use
7 NC relay contact
8 Not connected
9 Do not use
In Fig.9 and Fig.10 are shown the 1+0 and 1+1 version. The following connectors are presents:
• MNGT1, 2 management
Port MNGT 1, 2 set MDI or MDIX status automatically RJ45 (Tab.21)
In Fig.13 and Fig.14 are shown the 1+0 and 1+1 version. The following connectors are present:
• MNGT1, 2 management
Port MNGT 1, 2 set MDI or MDIX status automatically RJ45 (Tab.21)
• STM-1 1, 2 in/out
SFP can be I.1, S1.1, L1.1, L1.2, electrical coaxial 1.0/2.3 SFP
In Fig.11 and Fig.12 are shown the 1+0 and 1+1 version. The following connectors are present:
• MNGT1, 2 management
Port MNGT 1, 2 set MDI or MDIX status automatically RJ45 (Tab.21)
• STM-1 1, 2 in/out
SFP can be I.1, S1.1, L1.1, L1.2, electrical coaxial 1.0/2.3 SFP
The front panel of the ALCplus2e IDU is made up by various connectors depending on IDU version: in the
following type of connectors and relevant pin-out are listed. On the body of each IDU there is the ground
connection: 6.3mm male (Faston).
In Fig.7 and Fig.8 are shown the 1+0 and 1+1 version. The following connectors are available:
• MNGT1, 2 management
Port MNGT 1, 2 set MDI or MDIX status automatically RJ45 (Tab.21)
3 GND
7 GND
1 C relay contact
2 NO relay contact
3 User Input 01
4 User Input 02
5 Ground
6 Do not use
7 NC relay contact
8 Not connected
9 Do not use
In Fig.13 and Fig.14 are shown the 1+0 and 1+1 version. The following connectors are present:
• MNGT1, 2 management
Port MNGT 1, 2 set MDI or MDIX status automatically RJ45 (Tab.21)
• STM-1 1, 2 in/out
SFP can be I.1, S1.1, L1.1, L1.2, electrical coaxial 1.0/2.3 SFP
In Fig.11 and Fig.12 are shown the 1+0 and 1+1 version. The following connectors are present:
• MNGT1, 2 management
Port MNGT 1, 2 set MDI or MDIX status automatically RJ45 (Tab.21)
• STM-1 1, 2 in/out
SFP can be I.1, S1.1, L1.1, L1.2, electrical coaxial 1.0/2.3 SFP
The ALS with frequency reuse is double carrier systems with one carrier on vertical path and one carrier
on horizontal path. One carrier can have a radio frame up to 341 Mbit/s for a total of 682 Mbit/s.
For frequency reuse systems to assume the achievement of guaranteed performances of XPIC functional-
ities some cares shall be taken for IDU-ODU cabling. ALS XPIC systems use IDU ALCplus2e; ODU can be
AS or ASN or ASNK version in accordance with necessity.
15.2 CHARACTERISTICS
15.2.1 Antennas
15.2.2 RF channel
RF channel shall be the same for vertical polarization path and horizontal polarization path.
15.2.3 ATPC
• cable from RT1A to IDU-ODU SMA connector 1 and cable from RT1B to IDU-ODU SMA connector 2
shall have the same length with the following tolerance:
Installation changes regarding the kind of ODU RF flange that can be fast locking or standard.
Following installation kits are supplied with the equipment depending on different versions:
• 1+0 version
- supporting plate plus 60–114 mm pole fixing bracket and relevant nuts and bolts (see Fig.73)
- adapting tools and relevant bolts and nuts for 219 mm pole (see Fig.74)
- connection to the antenna with flexible wave guide and possible use of a rigid elbow (optional)
(see Fig.75)
• 1+1 version
- antisliding strip (see Fig.72)
- supporting plate plus pole fixing bracket and relevant nuts and bolts (see Fig.73)
- adapting tools and relevant bolts and nuts for 219 mm pole (see Fig.74)
Warning: in order to avoid damages to flexible waveguides, don’t fold or twist them more than values spec-
ified as limit in installation instructions of the waveguide supplier.
In case of flexible wave guide use, Tab.30 shows the maximum bending radius.
Warning: if screwing operation concerns more than one screw or bolt, tighten subsequently everyone and
its opposite, step by step.
• Version 1+0: installation onto the pole of the support plate by Band-it
3
• Version 1+1: installation onto the pole of the supporting plate
• ODU grounding
Fig.72 – Mount antislide strip around the pole. The position of the plastic blocks depends on the position
of the supporting plate (see next step)
Fig.73 – Adhere the supporting plate to the antisliding strip plastic blocks and then secure it to the pole
through the fixing bracket for 60–114 mm pole (see Fig.73). Bolts and nuts are available on the supporting
plate. Tightening torque must be 32 Nm.
Warning: As shown in Fig.74 an adapting kit must be used for the 219 mm pole. It consists of an additional
plate to enlarge the standard supporting plate dimension and relevant U–bolt for 219 mm pole fixing.
Fig.75 – Fix the flexible waveguide to the antenna side flange. Four fixing screws are available the dimen-
sions of which depend on the waveguide type. Tighten progressively and alternatively the four screws with
the following torque:
Fig.75 – Fix the antenna side flange to the support with ODU fast locking mechanism. The flange can be
mounted horizontally (as shown in Fig.75) or vertically as function of convenience.
Fig.76 – Fix the support with ODU fast locking mechanism to the supporting plate making use of available
bolts and nuts. Fig.76 shows the possible positions. Tightening torque must be 18 Nm.
In case of 1+0 ODU installation, a Band-it pole mounting kit can be used: through slots (see Fig.77) on
the supporting plate two metallic bands secure the plate on the pole. Band characteristics are:
• thickness 0.76 mm
• width 19 mm.
Fig.72 – Mount antislide strip around the pole. The position of the plastic blocks depends on the position
of the supporting plate (see next step)
Fig.73 – Position the supporting plate to the antisliding strip plastic blocks and then secure it to the pole
through the fixing bracket for 60–114 mm pole (see Fig.73). Bolts and nuts are available on the supporting
plate kit. Tightening torque must be 32 Nm.
Fig.78 – Secure the hybrid with ODU fast locking mechanism to the supporting plate using bolt and nuts
available on the support plate. Tightening torque must be 18 Nm.
Remove the plastic cover from the hybrid flange sides.
Warning: Do not remove the foil from the hybrid flange sides.
Fig.78 – Fix the flexible waveguide to the antenna side flange. Four fixing screws are available the dimen-
sions of which depend on the waveguide type. Tighten progressively and alternatively the four screws with
the following torque:
Warning: It is advisable to shape the waveguide flexible trunk, connecting ODU flange with antenna flange
as shown in Fig.81. This avoids possible condensate to be channelled towards the ODU flange.
1. Remove the plastic cover from the ODU flange side. Apply seal and lubricant grease Dow Corning 4
to the O–ring of Fig.80.
Warning: Do not remove the foil from the flange.
2. Bring the ODU with the two hands and position the ODU handle at the bottom side.
3. Position the ODU body close to the support with ODU fast locking mechanism and align ODU side
flange (see Fig.80) to antenna side flange (see Fig.75 – 1+0 version) or hybrid side flange (see
Fig.78 – 1+1 version).
Note: For 1+0 version the ODU can assume positions of Fig.79 depending on the polarisation.
4. With respect to the flange alignment, turn the ODU body approx. 30° anti–clockwise and then insert
the ODU body into the support and search for alignment between reference tooth on the support
(see Fig.75 – 1+0 version or Fig.78 – 1+1 version) and ODU body reference tooth (see detail Fig.80)
5. When alignment is achieved, turn the ODU body clockwise until “clack” is heard and the ODU rota-
tion stops.
6. Secure ODU body on the support by tightening bolts (1) (see Fig.75 – 1+0 version or Fig.78 – 1+1
version). Tightening torque must be 6 Nm.
Final assembly of 1+1 version is shown in Fig.81. A parasol mounting is optionally possible.
Bending radius with- Bending radius with- Bending radius with Bending radius with
out rebending out rebending rebending rebending
Frequency
mm (inch) mm (inch) mm (inch) mm (inch)
E-plane a H-plane b E-plane a. H-plane b.
6 GHz or 7 GHz
200 (7,9) 500 (19,8) 300 (11,9) 600 (23,7)
low
7 GHz high 200 (7,9) 500 (19,8) 250 (9,9) 600 (23,7)
a. Bending E-plane
Rmin/E
Bending E-plane
(short side of the section)
b. Bending H-plane
Rmin/H
Bending H-plane
(long side of the section)
Supporting plate
Use 15 mm wrench
(32Nm torque)
Reference tooth
Reference tooth
1
1
Position of antenna
side flange
1. 13 mm wrench
6 Nm torque
B C
Fig.76 - Possible positions of the support with ODU fast locking mechanism
Optional vawe
guide
RT1 RT2
Fig.79 - Position of the ODU body depending on the polarisation for 1+0. For 1+1 the polarisa-
tion is always vertical: handle at the left side.
O-ring
ODU side flange
ASN version
"N"
Ground bolt
AS version
AS version
4
5
ASN version
AS version
Washer
Screw M5x25
Screw M4x8
Screw M4x18
Spring
Washer
O-Ring
Hybrid 6 GHz
(balanced or
unbalanced)
The installation of AS, ASN or ASNK ODU is the same. Installation changes regarding the kind of ODU RF
flange that can be fast locking or standard.
Following installation kits are supplied with the equipment depending on different versions:
• 1+0 version
- wall supporting plate with additional contact surface extension plates (see Fig.85)
- connection to the antenna with flexible wave guide and possible use of a rigid elbow (optional)
(see Fig.86)
• 1+1 version
- supporting plate with additional contact surface extension tools (see Fig.85)
- connection to the antenna with flexible wave guide and possible use of a rigid elbow (optional)
(see Fig.86)
In case of flexible wave guide use, Tab.33 shows the maximum bending radius.
Warning: if screwing operation concerns more than one screw or bolt, tighten subsequently everyone and
its opposite, step by step.
• ODU grounding.
Fig.85 – Fix on the supporting plate the two supplied extension plates to increase the wall contact surface.
Fig.85 – Secure the supporting plate on the wall using the more suitable screws.
Use the expansion plug suitable to the wall. Test the installed bracket with a load of 50kg. No deformation
should be noted.
Fig.86 – Fix the flexible waveguide to the antenna side flange. Four fixing screws are available the dimen-
sions of which depend on the waveguide type. Tighten progressively and alternatively the four screws with
the following torque:
Fig.86 – Fix the antenna side flange to the support with ODU fast locking mechanism. The flange can be
mounted horizontally (as shown in Fig.86) or vertically as function of convenience.
Fig.87 – Fix the support with ODU fast locking mechanism to the supporting plate making use of available
bolts and nuts. Fig.87 shows three possible positions. Tightening torque must be 18 Nm.
Fig.85 – Fix on the supporting plate the two supplied extension plates to increase the wall contact surface.
Fig.85 – Secure the supporting plate on the wall using the more suitable screws.
Warning: Use the expansion plug suitable to the wall. Test the installed bracket with a load of 50kg. No
deformation should be noted.
Fig.88 – Secure the hybrid with ODU fast locking mechanism to the supporting plate using bolt and nuts
available on the support plate. Tightening torque must be 18 Nm.
Remove the plastic cover from the hybrid flange sides.
Warning: Do not remove the foil from the hybrid flange sides.
Fig.88 – Fix the flexible waveguide to the antenna side flange. Four fixing screws are available the dimen-
sions of which depend on the waveguide type. Tighten progressively and alternatively the four screws with
the following torque:
Warning: It is advisable to shape the waveguide flexible trunk, connecting ODU flange with antenna flange
as shown in Fig.91 This avoids possible condensate to be channelled towards the ODU flange.
1. Remove the plastic cover from the ODU flange side. Apply seal and lubricant grease Dow Corning 4
to the O–ring of Fig.90.
Warning: Do not remove the foil from the flange.
2. Bring the ODU with the two hands and position the ODU handle at the bottom side.
3. Position the ODU body close to the support with ODU fast locking mechanism and align ODU side
flange (see Fig.90) to antenna side flange (see Fig.86 – 1+0 version) or hybrid side flange (see
Fig.88 – 1+1 version).
Note: For 1+0 version the ODU can assume positions of Fig.89 depending on the polarisation.
4. With respect to the flange alignment, turn the ODU body approx. 30° anti–clockwise and then insert
the ODU body into the support and search for alignment between reference tooth on the support
(see Fig.86 – 1+0 version or Fig.88 – 1+1 version) and ODU body reference tooth (see detail Fig.90)
5. When alignment is achieved, turn the ODU body clockwise until “clack” is heard and the ODU rota-
tion stops.
6. Secure ODU body on the support by tightening bolts (1) (see Fig.86 – 1+0 version or Fig.88 – 1+1
version). Tightening torque must be 6 Nm.
Final assembly of 1+1 version is shown in Fig.91. A parasol mounting is optionally possible.
Bending radius with- Bending radius with- Bending radius with Bending radius with
out rebending out rebending rebending rebending
Frequency
mm (inch) mm (inch) mm (inch) mm (inch)
E-plane a H-plane b E-plane a. H-plane b.
6 GHz or 7 GHz
200 (7,9) 500 (19,8) 300 (11,9) 600 (23,7)
low
7 GHz high 200 (7,9) 500 (19,8) 250 (9,9) 600 (23,7)
a. Bending E-plane
Rmin/E
Bending E-plane
(short side of the section)
b. Bending H-plane
Rmin/H
Bending H-plane
(long side of the section)
Supporting plate
Reference tooth
Reference tooth
1
1
13 mm wrench
6 Nm torque
Position of antenna
side flange
Optional wave
guide
RT1 RT2
Fig.89 - Position of the ODU body depending on the polarisation for 1+0. For 1+1 the polarisa-
tion is always vertical: handle at the left side.
O-ring
ODU side flange
ASN version
"N"
"BNC"
AS version
ASN version
AS version
4
5
ASN version
AS version
1. Bolt
2. Spring washer
3. Flat washer
5. Flat washer
Washer
Screw M5x25
Screw M4x8
Screw M4x18
Spring
Washer
O-Ring
Hybrid 6 GHz
(balanced or
unbalanced)
18.1 FOREWORD
The installation onto the pole of the ODU with integrated antenna concerns both 1+0 and 1+1 versions.
Installation changes regarding the kind of ODU RF flange that can be fast locking or standard.
Following installation kits are supplied with the equipment depending on different versions:
1+0 version
1+1 version
Warning: if screwing operation concerns more than one screw or bolt, tighten subsequently everyone and
its opposite, step by step.
1+0 version
4. antenna aiming
5. ODU grounding
1+1 version
5. antenna aiming
6. ODU grounding.
18.4.1 Installation onto the pole of the support system and the antenna
Fig.95 – Set the antenna in such a position as to be able to operate on its rear side. Locate the five threaded
holes around antenna flange. Mount centring ring onto antenna flange and tight it with 3 calibrated bolts.
Caution: centring ring should be mounted so that the screws do not stick out.
Define if the antenna will be mounted with vertical or horizontal polarization. Check that free drain holes
stay at bottom side. Mount bolt type M10x30, in position A leaving it loose of 2 cm approx. With horizontal
polarization mount bolt type M10x30 in position D, leaving it loose of 2 cm approx.
Fig.96 – Mount antislide strip onto the pole. Place blocks as in Fig.96 following antenna aiming direction.
Tighten the strip with screwdriver.
Fig.97 – Mount pole supporting system with relevant pole fixing brackets following antenna aiming direc-
tion as indicated by arrow. Antislide strip should result at the centre of supporting plate. Supporting system
Fig.100 – Rotate the antenna body until the remainder three antenna holes coincide with the three support
holes. Secure the antenna to the support by tightening the relevant passing through bolts.
1+0 version
1. Apply seal and lubricant grease Dow Corning 4 to the O–ring (4) of Fig.103 by protecting finger
hands with gloves.
2. Bring the ODU with the two hands and position the ODU handle at the bottom side. The ODU handle
can assume position of Fig.101 depending on the polarization.
3. Position the ODU body near the support system and align ODU side flange to antenna side flange
(see Fig.102). With respect to the flange alignment, turn the ODU body approx. 30° anti–clockwise
and then insert the ODU body into the support and search for alignment between reference tooth
on the support (see Fig.102) and ODU body reference tooth (see detail of Fig.103).
4. When alignment is achieved, turn the ODU body clockwise until “clack” is heard and the ODU rota-
tion stops.
Fig.104 and Fig.105 show ODU housing final position for vertical and horizontal polarization respec-
tively.
5. Secure ODU body on the support system by tightening bolts (1) of Fig.102.
1+1 version
Fig.106 – Apply seal and lubricant grease Dow Corning 4 to O–rings (1). Insert O–rings (1) and (6) into
twist polarization disk (2).
Vertical polarization
Fix the disk on hybrid flange placing marker (4), on disk, close to V mark.
Horizontal polarization
Fix the disk on hybrid flange placing reference (4), on disk, close to H mark.
In 13 GHz and 15 GHz ODUs the polarization disk is fixed to the hybrid flange by means of 3 screws as
shown in Fig.107.
Caution: Twist disk has two planes. Take care of position marker (4) on twist disk. The position of marker
(4) plane should be in contact to hybrid like in figure. Tighten progressively and alternatively screws (7)
with the same number of spring washers (8) with the following torque:
Fig.108 – Fix hybrid to support system with four bolts (1) taking care of RT1/RT2 position shown by labels
of Fig.108. Tighten progressively and alternatively four bolts (1).
1. Apply seal and lubricant grease Dow Corning 4 to the O–ring (4) of the Fig.103 by protecting finger
hands with gloves.
2. Bring the ODU with the two hands and position the ODU handle at the bottom side. For 1+0 the
ODU can assume position of Fig.101 depending on the polarisation. For 1+1 the handle ODU posi-
tion is always placed at the right side (horizontal polarization).
3. Position the ODU body near the support system and align ODU side flange to antenna side flange
(see Fig.102). With respect to the flange alignment, turn the ODU body approx. 30° anti–clockwise
and then insert the ODU body into the support and search for alignment between reference tooth
on the support (see Fig.102) and ODU body reference tooth (see detail of Fig.103).
4. When alignment is achieved, turn the ODU body clockwise until “clack” is heard and the ODU rota-
tion stops.
Fig.104 and Fig.105 show ODU housing final position for vertical and horizontal polarization respec-
tively for 1+0 version.
Fig.109 shows ODU housing final position for 1+1 version.
5. Secure ODU body on the support system by tightening bolts (1) of Fig.102.
Antenna aiming for 1+0 version and 1+1 version is the same. The antenna aiming devices allow to perform
the following adjustments with respect to the starting aiming position:
- Horizontal ± 15° operating on the nut (3) shown in Fig.110, only after having loosen
the nuts (7), (8), (9), (10) of Fig.111.
- vertical ± 15° operating on vertical adjustment worm screw (2) shown in Fig.110
only after having loosen nuts (1), (2), (11) of Fig.111 and (4) and (5) of
Fig.110.
For adjustment from 0° to +30° extract nut (1) Fig.111 and position it in
hole (4), extract nut (2) Fig.111 and position it in hole (6). Operate on
vertical adjustment worm screw (2) after having loosen nuts (1), (2), (11) of
Fig.111 and (4) of Fig.110.
For adjustment from 0° to –30° extract nut (1) of Fig.111 and position it in
hole (3), extract nut (2) of Fig.111 and position it in hole (5). Operate on
vertical adjustment worm screw (2) after having loosen nuts (1), (2), (11) of
Fig.111 and (4) of Fig.110.
For vertical adjustment some markers, every 10°, are available on support.
The bigger marker gives 0° starting aiming position. Once the optimum aiming
position is obtained, tighten firmly the four nuts (1), (2), (11) of Fig.111 and
(4) and (5) of Fig.110 for vertical adjustment and the four nuts (7), (8), (9),
(10) of Fig.111 for horizontal adjustment. Tighten with 15 mm wrench and
32 Nm torque.
18.6 COMPATIBILITY
The pole installation kit of the ODU unit in 1+0 and 1+1 configuration is compatible with integrated antenna
complying with SIAE standard with measures 0.2 m, 0.4 m, 0.6 m, 0.8 m of diameter.
See Fig.112.
On ODU grounding can be connected with the available bolt spring washer and flat washers as shown. Cou-
pling torque for the grounding bolt is 9.5 Nm.
A D D C
B C A B
3 mm allen key 2
2,5 Nm torque
A
1
C
1. Antenna
3. Centring ring
1. Steel belt
2. Plastic blocks
15 mm wrench
32 Nm torque 3
3 3
2. Tooth
3. Bolt
1. Tooth
Fig.99 - Hole E
A D
15 mm wrench
32 Nm torque
A, B, C, D Bolt slots
Vertical Horizontal
Fig.101 -Position of the ODU handle depending on the polarisation for 1+0. For 1+1 the polari-
sation is always horizontal. Handle at the right side.
H
H
1
1
H
H
H
H
1
H: Reference tooth
Fig.102 - Support system for ODU housing and reference tooth in evidence
O-ring
ODU side flange
ASN version
"N"
"BNC"
AS version
5
30
5
30
2
4
6
1. O–ring
2. Polarization twist disk
6. O–ring
7. Allen screws
8. Spring washer
Vertical polarization
RT1
2
1
RT2
13 mm wrench
18 Nm torque
1. Bolts
2. Spring washer
AS version
1. Marker
2. Vertical adjustment
3. Horizontal adjustment
4. Bolt
5. Fixing nut
7
4 11 1 8
3
10
9 15 mm wrench
6 32 Nm torque
5 2
15 mm wrench
32 Nm torque
4
5
ASN version
AS version
1. Bolt
2. Spring washer
3. Flat washer
5. Flat washer
19.1 FOREWORD
The description concerns pole mounting of ODU, in 1+0 and 1+1 version, using following installation kits:
Differences regard the dimensions and the presence of the centring ring (see Fig.113):
Installation changes regarding the kind of ODU RF flange that can be fast locking or standard.
Following installation kits are supplied with the equipment depending on different versions.
1+0 version
- pole support system plus antenna (already assembled) and pole fixing brackets
1+1 version
- pole support system plus antenna (already assembled) and pole fixing brackets
• N.2 17 mm spanner.
Warning: if screwing operation concerns more than one screw or bolt, tighten subsequently everyone and
its opposite, step by step.
1+0 version
1. antenna polarization
5. installation of ODU
6. antenna aiming
7. ODU grounding
1+1 version
1. antenna polarization
5. installation of hybrid
6. installation of ODUs
7. antenna aiming
8. ODU grounding.
Fig.113 – Set the antenna in such a position to operate on its rear side. Locate the four M3 Allen screws
around the antenna flange. Unscrew them (use 2.5 mm Allen wrench) and position the antenna flange ac-
cording on: horizontal wave guide –> vertical polarization, vertical wave guide –> horizontal polariza-
tion. Screw again the four Allen screws (torque = 1 Nm).
Fig.113 – Set the antenna in such a position to operate on its rear side. Locate the three holes around the
antenna flange. Mount the centring ring onto antenna flange and tight it with the 3 Allen screws M4 (use
3mm Allen wrench, torque 2 = Nm).
Fig.113 – Mount the support onto assembled structure (pole support system plus antenna) using the four
M8 Allen screws (use 6 mm Allen wrench, torque 18 = Nm). Two of the four screws, diagonally opposed,
must be mounted with the two bushes around.
Fig.113 – Mount the assembled structure on the pole using the two pole fixing brackets and the four M10
screws (use 17 mm spanner, torque = 13 Nm); the heads of the screws are inserted on the antenna side,
the four nuts and the springs between nut and brackets are inserted on bracket side.
Fig.114 – Apply seal and lubricant grease Dow Corning 4 on the O–ring by protecting fingers with gloves.
Fig.115 – Bring the ODU with the two hands and position the ODU handle at the bottom side. The handle
can assume the positions shown in the figure depending on the polarization. Position the ODU body near
the support and align the wave guide of the ODU to the Wave guide of the antenna: respect to the position
of wave guide alignment, turn the ODU body approx. 30° counter–clockwise into the support and search
for matching between reference tooth on the support (see Fig.116) and reference tooth on the ODU body.
Fig.117 – When alignment of the references teeth is achieved, turn the ODU body clockwise until rotation
is stopped. In figure are shown ODU final position for both polarizations.
Fig.116 – When ODU positioning is over, secure ODU body on the support by tightening bolts (use 13mm
spanner, torque = 6Nm).
Antenna aiming procedure for 1+0 version or 1+1 version is the same.
Horizontal aiming: ±5° operating on the 17 mm nut shown in Fig.118 with a 17 mm spanner, only after
having loosen the two 17 mm nut on the pivot.
Vertical aiming: ±20° operating on the 13 mm nut shown in Fig.118 with a 13 mm spanner, only after
having loosen the three 13 mm nut on the pole support.
Once optimum position is obtained, tighten firmly all the nuts previously loosen.
as shown in Fig.119.
In further page are explained all the mounting step not already discussed in paragraph “19.5 1+0
MOUNTING PROCEDURES”.
Fig.120 – The polarization disk must be always fixed on hybrid flange. Apply seal and lubricant grease Dow
Corning 4 on the O–rings by protecting fingers with gloves. Bring the polarization twist disk with the posi-
tion marker down. Insert the O–ring into polarization twist disk.
Vertical polarization: fix the twist disk on hybrid flange placing the marker of the disk towards V mark.
Horizontal polarization: fix the twist disk on hybrid flange placing the marker of the disk towards H mark.
In 13 GHz and 15 GHz ODUs the polarization disk is fixed to the hybrid flange by means of 3 screws as
shown in Fig.121.
Tighten progressively and alternatively the screws and the spring washer with following torque:
Fig.122 – Fix hybrid body to 1+0 support with four M8 bolts (use 13 mm spanner, torque = 18 Nm), tighten
progressively and alternatively the bolts.
Fig.114 – Apply seal and lubricant grease Dow Corning 4 to the O–ring by protecting fingers with gloves.
Fig.115 – Bring the ODU with the two hands and position the ODU handle at the bottom side. The handle
can assume the positions shown in the figure depending on the polarization. Position the ODU body near
the support and align the wave guide of the ODU to the wave guide of the hybrid: respect to the position
of wave guide alignment, turn the ODU body approx. 30° counter–clockwise and then insert the ODU body
into the support. For 1+1 system the handle of the ODU is always positioned on the right. The polarization
twist disk on the hybrid matches the antenna polarization.
Fig.123 – When alignment of the reference teeth is achieved, turn the ODU body clockwise until the rota-
tion stops. In figure are shown ODUs final position.
Fig.116 – When ODU positioning is over, secure ODU body on the support by tightening bolts (use 17 mm
spanner, torque = 6 Nm).
Warning: Internal codes (e.g. installation items, antennas, PCB) are here reported only as example. The
Manufacturer reserves the right to change them without any previous advice.
Four 13mm
screws
Centring ring
(not present in V32309)
1+0 support
Two bushes
O-ring
ODU wave guide
"N"
"BNC"
Vertical Horizontal
Fig.115 - Position of the ODU handle depending on the polarisation for 1+0. For 1+1 the polar-
isation is always horizontal. Handle at the right side.
1
5
4 4
1
2
3
1. 6 mm Allen screw
Vertical aiming:
13mm block screws
Pole support
4
5
ASN version
AS version
1. Bolt
2. Spring washer
3. Flat washer
5. Flat washer
2
4
6
1. O–ring
2. Polarization twist disk
6. O–ring
7. Allen screws
8. Spring washer
Vertical polarization
AS version
20.1 FOREWORD
The installation onto the pole of the ODU with integrated dual polarization antenna concerns 2+0 ODU
(with/without XPIC) and purpose of this chapter is to describe how to install ODUs over an orthomode
transducer (OMT) to achieve a double polarization microwave link.
Dual polarization antenna, orthomode transducer and pole support assembly are supplied by different sup-
pliers.
Depending on supplier and antenna dimension the final assembled structure can vary.
An example in Fig.124.
• Pole support system with antenna and orthomode transducer (from various suppliers)
• 2 standard lock ODUs with O-rings and accessories for ground connection and with standard lock
flange.
• Pole support system with antenna and orthomode transducer (from various suppliers)
• 2 Fast lock ODUs with O-rings and accessories for ground connection and with fastlock flange
• 1x 3 mm Allen wrench
• 1x 6 mm Allen wrench
• 1x 13 mm spanner
• 2x 17 mm spanner
Warning: if screwing operation concerns more than one screw or bolt, tighten subsequently everyone and
its opposite, step by step.
Two installation procedures are available depending the ODU mounting flange.
1. Installation of the 2 centring rings on the two lateral flanges of the orthomode transducer
2. Installation over the pole of the assembled structure: antenna with orthomode and pole support
system
3. Installation of standard lock ODUs
4. Antenna aiming
5. ODU grounding
1. Installation of the 2 centring rings on the two lateral flanges of the orthomode transducer
3. Installation over the pole of the assembled structure: antenna with orthomode and pole support
system
5. Antenna aiming
6. ODU grounding
Two centring rings must be mounted over the two lateral flanges of the OMT (see Fig.125).
• Set the OMT in such a position to operate on its lateral side flange.
• Locate the three holes around the flange and mount the first centring ring onto this flange and
tight it with the 3 Allen screws M4 (use 3mm Allen wrench, torque 2 = Nm).
• Repeat the procedure on the flange on opposite side of the OMT in order to mount the second cen-
tring ring.
See the instructions included in the antenna box (instructions vary depending on antenna vendor).
Two ODUs must be mounted using four 25mm bolts for each one.
• Add lubricant paste, e.g. MOLYKOTE P-40, on threads of four 25mm M10 bolts (M10). The sliding
surfaces should be cleaned. The paste should then be applied with a suitable brush, rag or grease
gun. It should not be mixed with grease or oils. Chemical protective gloves should be used.
• Screw partially these four 25mm M10 bolts in the relevant four holes around the OMT lateral flange:
each bolt should be tightened to have the square head out of the hole of about 13-14mm (the thick-
ness of hook), use 15mm spanner
• Apply seal and lubricant grease DOW CORNING 4 to the O-ring, protecting hands with gloves, and
insert in the proper track on the ODU flange
• Position the ODU vertically near the four bolts on the OMT lateral flange and align the ODU to match
the polarization of the OMT flange itself.
• After the right position has been found, rotate 30° counter clockwise the ODU and approach the
ODU to the OMT flange in order to have the four slots of the Standard Lock cross between the four
bolts
• Rotate 30° clockwise the ODU to hook each slots on the relevant bolt
• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15mm spanner,
torque=46mm)
• Optional: sun cover kit - Insert the sun cover and tie one of its bottom holes to the ODU handle by
means of the black plastic strip included in the sun cover kit
• Now the ODU is ready to be connected to the IDU-ODU cable and to the grounding cable.
Repeat this procedure for the second ODU on the opposite side of the OMT.
For horizontal and vertical aiming see the instructions included in the antenna box (instructions vary de-
pending on antenna vendor). Remember to tighten firmly all the nuts previously loosen.
For polarization adjustment see the instructions included in the antenna box (instructions vary depending
on antenna vendor). Remember to tighten firmly all the nuts previously loosen.
as shown in Fig.119.
Two centring rings must be mounted over the two lateral flanges of the OMT (see Fig.125).
• Set the OMT in such a position to operate on its lateral side flange.
• Locate the three holes around the flange and mount the first centring ring onto this flange and
tight it with the 3 Allen screws M4 (use 3mm Allen wrench, torque 2 = Nm).
• Repeat the procedure on the flange on opposite side of the OMT in order to mount the second cen-
tring ring.
See Fig.126. The orientation of the ODU support is the one that allows the mounting of the support over
the OMT. The fast lock ODU can be mounted inserted inside the ODU support in two different orientations
just to match the OMT wave guide flange.
• Mount the support onto OMT lateral flange using the four M8 Allen screws (1 in Fig.126). Use 6 mm
Allen wrench, torque 18 = Nm.
• Two of the four screws, diagonally opposed, must be mounted with the two bushes (2 in Fig.126).
around
See the instructions included in the antenna box (instructions vary depending on antenna vendor).
• In each fast lock ODUs apply seal and lubricant grease DOW CORNING 4 on the groove of the O-
ring by protecting hands with gloves.
• Bring the ODU with the two hands and position the ODU handle at the bottom side.
• Position the ODU body near the support and align the wave guide of the ODU to the wave guide of
the OMT flange.
• Respect to the position of wave guide alignment, turn the ODU body approx. 30° counter-clockwise
into the support and search for matching between reference tooth (4 or 5 in Fig.126, point the one
that allows the two waveguides matching) on the support and reference tooth on the ODU body.
• When alignment of the references teeth is achieved, turn the ODU body clockwise until rotation is
stopped and secure ODU body on the support by tightening bolts (3 in Fig.126). Use 13mm spanner,
torque = 6Nm.
Repeat this procedure for the second ODU on the opposite side of the OMT.
For horizontal and vertical aiming see the instructions included in the antenna box (instructions vary de-
pending on antenna vendor). Remember to tighten firmly all the nuts previously loosen.
For polarization adjustment see the instructions included in the antenna box (instructions vary depending
on antenna vendor). Remember to tighten firmly all the nuts previously loosen.
as shown in Fig.119.
Centering ring
3
1
1
5
4 4
1
2
3
4. Reference point
5. Reference point
O-ring
ODU ASN/ASNK
Eyelet terminal
Grounding bolt
AS version
21.1 FOREWORD
The installation onto the pole of the ODU with integrated antenna concerns both 1+0 and 1+1 version.
Installation changes regarding the kind of ODU RF flange that can be fast locking or standard.
Following installation kits are supplied with the equipment depending on different versions.
1+0 version
- pole support system plus antenna (already assembled) and pole fixing brackets
1+1 version
- pole support system plus antenna (already assembled) and pole fixing brackets
- 1+0 ODU support
• N.2 17 mm spanner.
Warning: if screwing operation concerns more than one screw or bolt, tighten subsequently everyone and
its opposite, step by step.
1+0 version
1. antenna polarization
5. installation of ODU
6. antenna aiming
7. ODU grounding
1+1 version
1. antenna polarization
2. installation of the centring ring on the antenna
5. installation of hybrid
6. installation of ODUs
7. antenna aiming
8. ODU grounding.
Fig.113 – Set the antenna in such a position to operate on its rear side. Locate the four M3 Allen screws
around the antenna flange. Unscrew them (use 2.5 mm Allen wrench) and position the antenna flange ac-
cording on: horizontal wave guide –> vertical polarization, vertical wave guide –> horizontal polariza-
tion. Screw again the four Allen screws (torque = 1 Nm).
Fig.113 – Set the antenna in such a position to operate on its rear side. Locate the three holes around the
antenna flange. Mount the centring ring onto antenna flange and tight it with the 3 Allen screws M4 (use
3mm Allen wrench, torque 2 = Nm).
Fig.113 – Mount the support onto assembled structure (pole support system plus antenna) using the four
M8 Allen screws (use 6 mm Allen wrench, torque 18 = Nm). Two of the four screws, diagonally opposed,
must be mounted with the two bushes around.
Fig.113 – Mount the assembled structure on the pole using the two pole fixing brackets and the four M10
screws (use 17 mm spanner, torque = 13 Nm); the heads of the screws are inserted on the antenna side,
the four nuts and the springs between nut and brackets are inserted on bracket side.
Fig.114 – Apply seal and lubricant grease Dow Corning 4 on the O–ring by protecting fingers with gloves.
Fig.115 – Bring the ODU with the two hands and position the ODU handle at the bottom side. The handle
can assume the positions shown in the figure depending on the polarization. Position the ODU body near
the support and align the wave guide of the ODU to the Wave guide of the antenna: respect to the position
of wave guide alignment, turn the ODU body approx. 30° counter–clockwise into the support and search
for matching between reference tooth on the support (see Fig.116) and reference tooth on the ODU body.
Fig.117 – When alignment of the references teeth is achieved, turn the ODU body clockwise until rotation
is stopped. In figure are shown ODU final position for both polarizations.
Fig.116 – When ODU positioning is over, secure ODU body on the support by tightening bolts (use 13mm
spanner, torque = 6Nm).
Antenna aiming procedure for 1+0 version or 1+1 version is the same.
Horizontal aiming: ±5° operating on the 17 mm nut shown in Fig.118 with a 17 mm spanner, only after
having loosen the two 17 mm nut on the pivot.
Vertical aiming: ±20° operating on the 13 mm nut shown in Fig.118 with a 13 mm spanner, only after
having loosen the three 13 mm nut on the pole support.
Once optimum position is obtained, tighten firmly all the nuts previously loosen.
as shown in Fig.119.
In further page are explained all the mounting step not already discussed in paragraph “19.5 1+0
MOUNTING PROCEDURES”.
Fig.120 – The polarization disk must be always fixed on hybrid flange. Apply seal and lubricant grease Dow
Corning 4 on the O–rings by protecting fingers with gloves. Bring the polarization twist disk with the posi-
tion marker down. Insert the O–ring into polarization twist disk.
Vertical polarization: fix the twist disk on hybrid flange placing the marker of the disk towards V mark.
Horizontal polarization: fix the twist disk on hybrid flange placing the marker of the disk towards H mark.
In 13 GHz and 15 GHz ODUs the polarization disk is fixed to the hybrid flange by means of 3 screws as
shown in Fig.121.
Tighten progressively and alternatively the screws and the spring washer with following torque:
Fig.122 – Fix hybrid body to 1+0 support with four M8 bolts (use 13 mm spanner, torque = 18 Nm), tighten
progressively and alternatively the bolts.
Fig.114 – Apply seal and lubricant grease Dow Corning 4 to the O–ring by protecting fingers with gloves.
Fig.115 – Bring the ODU with the two hands and position the ODU handle at the bottom side. The handle
can assume the positions shown in the figure depending on the polarization. Position the ODU body near
the support and align the wave guide of the ODU to the wave guide of the hybrid: respect to the position
of wave guide alignment, turn the ODU body approx. 30° counter–clockwise and then insert the ODU body
into the support. For 1+1 system the handle of the ODU is always positioned on the right. The polarization
twist disk on the hybrid matches the antenna polarization.
Fig.123 – When alignment of the reference teeth is achieved, turn the ODU body clockwise until the rota-
tion stops. In figure are shown ODUs final position.
Fig.116 – When ODU positioning is over, secure ODU body on the support by tightening bolts (use 17 mm
spanner, torque = 6 Nm).
WARNING: Internal codes (e.g. installation items, antennas, PCB) are here reported only as example. The
Manufacturer reserves the right to change them without any previous advice.
1+0 support
O-ring
ODU wave guide
"N"
"BNC"
Vertical Horizontal
Fig.131 - Position of the ODU handle depending on the polarisation for 1+0. For 1+1 the polar-
isation is always horizontal. Handle at the right side.
1
4
3 3
1
Vertical aiming
2
1
Horizontal aiming
4
5
ASN version
AS version
1. Bolt
2. Spring washer
3. Flat washer
5. Flat washer
2
4
6
1. O–ring
2. Polarization twist disk
6. O–ring
7. Allen screws
8. Spring washer
Vertical polarization
ASN version
Two versions of ODU can be connected to ALplus2/ALCplus2 IDU: ODU AS and ODU ASN/ASNK. Both ver-
sions need to be completed with a coupling kit to be connected to the mechanical structure for the instal-
lation.
22.1.1 ODU AS
ODU AS is factory assembled with a “Fast Lock” coupling kit (see Fig.140); for the installation it needs O-
ring and grounding bolt only.
ODU ASN/ASNK can mount two different coupling kits in order to obtain a Fast Lock ASN/ASNK or a Stand-
ard ASN/ASNK. After having mounted the proper coupling kit the ODU needs O-ring and grounding bolt.
The Fast Lock coupling kit is the same used in ODU AS and so after kit, O-ring and grounding bolt assembly,
the ASN/ASNK Fast Lock can be installed in the same way of ODU AS.
See Fig.141 - Put the Fast Lock coupling kit on the ODU.
Align the four holes of the coupling kit with the four nut screws on the ODU. Insert and tighten the four
screws.
The standard coupling kit is mounted on ASN/ASNK ODU by means of four screws.
The installation of ODUs with Fast Lock coupling kit is described in previous chapters.
• M10 bolts
Install the antenna using the antenna installation guide (specific for each antenna) inside the antenna box
provided by antenna producer. Keep attention to the polarization of the antenna feeder depending on re-
quested polarization.
After the antenna is installed onto the pole, the ODU must be installed, see Fig.143.
• Position the three holes circular flange (1) on the antenna flange and align the three holes on the
circular flange with the three relevant holes on the antenna flange
• Insert and tighten the three 3mm M4 Allen screws (2) using a 3mm Allen wrench (torque = 2 Nm)
• Add lubricant paste, e.g. MOLYKOTE P-40, on threads of four 25mm bolts (3). The sliding surfaces
should be cleaned. The paste should then be applied with a suitable brush, rag or grease gun. It
should not be mixed with grease or oils. Chemical protective gloves should be worn where repeated
or prolonged contact can occur.
• Apply seal and lubricant grease Dow Corning 4 to the O-ring, protecting fingers with gloves, and
insert in the proper track on the ODU flange
• Position the ODU (5) vertically near the four bolts on the antenna flange and align the ODU to match
the polarization of the antenna feeder:
- vertical polarization: the handle (6) of the ODU is at the bottom left corner
- horizontal polarization: the handle (6) of the ODU is at the bottom right corner
• After the right position has been found, rotate 30° counter clockwise the ODU and approach the
ODU to the antenna flange in order to have the four slots of the Standard Lock cross between the
four bolts
• Rotate 30° clockwise the ODU to hook each slots on the relevant bolt
• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15mm spanner,
torque=46mm)
• Optional: sun cover kit - Insert the sun cover and tie one of its bottom holes to the ODU handle by
means of the black plastic strip included in the sun cover kit
• The ODU is ready to be connected to the IDU-ODU cable and to the grounding cable.
Install The antenna using the antenna installation guide (specific for each antenna) inside the antenna box
by antenna producer. Keep attention to the polarization of the antenna feeder depending on requested po-
larization.
After the antenna is installed onto the pole, follow the procedure below, see Fig.144.
• Position the three holes circular flange (1) on the antenna flange and align the holes on the circular
flange with the relevant holes on the antenna flange
• Insert and tighten the three 3mm M4 Allen screws (2) using a 3mm Allen wrench (torque = 2mm)
• Prepare the polarization disk (see Fig.145) with the two O-rings: seal and lubricant grease Dow
Corning 4 must be applied to the O-ring, protecting fingers with gloves; each O-ring must be insert-
ed in the proper track on each surface of the disk
• Mount always (with vertical and with horizontal polarization) the polarization disk on the hybrid
flange (antenna side) as shown in Fig.145 and tighten the four screws (only three screws in 13 GHz
and 15 GHz hybrid). The polarization disk must br oriented depending on requested polarization by
antenna feeder (position V or H as shown in Fig.145. Torque values as in 22.3.2.2.
• Mount the hybrid on the back of the antenna by means of four M10 bolts (4) (torque = 46 Nm)
• Add lubricant paste, e.g. MOLYKOTE P-40, on threads of four 25mm bolts (3). The sliding surfaces
should be cleaned. The paste should then be applied with a suitable brush, rag or grease gun. It
should not be mixed with grease or oils. Chemical protective gloves should be worn where repeated
or prolonged contact can occur.
• Screw partially four M10 bolts (4) on the hybrid flange (ODU side): each bolt should be tightened
to have the square head out of the hole of about 13-14 mm, use 15 mm spanner
• Position the ODU (5) vertically near the four bolts on the antenna flange and align the ODU to match
the polarization of the antenna feeder: horizontal polarization must be used, the handle (6) of the
ODU is at the bottom right corner
• After the right position has been found, rotate 30° counter clockwise the ODU and approach the
ODU to the antenna flange in order to have the four slots (7) of the Standard Lock cross between
the four bolts on the hybrid
• Rotate 30° clockwise the ODU to hook each slots on the relevant bolt
• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15 mm spanner, torque
= 46Nm)
• Optional: sun cover kit - Insert the sun cover and tie one of its bottom holes to the ODU handle by
means of the black plastic strip included in the sun cover kit
• Now the ODU is ready to be connected to the IDU-ODU cable and to the grounding cable
• Repeat for the other ODU on the other side
• Optional: sun cover kit. Insert the sun cover and tie one of its bottom holes to the ODU handle by
means of the black plastic strip included in the sun cover kit
• Now the ODU is ready to be connected to the IDU-ODU cable and to the grounding cable.
The installation of ODUs with Fast Lock coupling kit is described in previous chapters.
• Supporting plate, fixing bracket with M10 130mm bolts (with washer, spring and nut)
• Supporting plate, fixing bracket with M10 130mm bolts (with washer, spring and nut)
See Fig.146.
• Position the supporting plate (1) on the pole and fix the rear bracket (2) to it by means of the four
130 mm M10 bolt (3) with relevant washers, springs and nuts (use 15mm spanner, torque =
46Nm).
• Fix the antenna side flange (4) with the proper screws (in Fig.146 the antenna flange is shown in
two different positions depending on the polarization), the screw holes side is the side where the
waveguide must be installed.
• Add lubricant paste, e.g. MOLYKOTE P-40, on threads of four 25mm bolts (3). The sliding surfaces
should be cleaned. The paste should then be applied with a suitable brush, rag or grease gun. It
should not be mixed with grease or oils. Chemical protective gloves should be worn where repeated
or prolonged contact can occur.
• On the supporting plate, on the opposite side respect to the antenna flange just mounted, insert in
holes (5) on the supporting plate the four 25mm M10 bolts (3): screw them partially, each bolt
should be tightened to have the square head out of the hole of about 13-14 mm (the thickness of
hook (4), use 15mm spanner).
• Apply seal and lubricant grease Dow Corning 4 to the O-ring, protecting fingers with gloves, and
insert it in the proper track on the ODU flange.
• Position the ODU vertically near the four bolts on the supporting plate and align the ODU to match
the polarization of the antenna flange:
- vertical polarization: the handle of the ODU is at the bottom left corner
- horizontal polarization: the handle of the ODU is at the bottom right corner
• After the right position has been found, rotate 30° counter clockwise the ODU and approach the
ODU to the supporting plate in order to have the four slots of the Standard Lock cross between the
four bolts
• Rotate 30° clockwise the ODU to hook each slots on the relevant bolt
• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15 mm spanner, torque
=46 Nm).
See Fig.147.
• Position the supporting plate (1) on the pole and fix the rear bracket (2) to it by means of the four
130 mm M10 bolt (3) with relevant washers, springs and nuts (use 15 mm spanner, torque = 46
Nm)
• Mount the hybrid (4) on the back of the antenna by means of four 25 mm M10 bolts (5) (use 15
mm spanner with torque = 46 Nm) in the holes (6).
Mounting each ODU on the hybrid:
• Add lubricant paste, e.g. MOLYKOTE P-40, on threads of four 25mm bolts (3). The sliding surfaces
should be cleaned. The paste should then be applied with a suitable brush, rag or grease gun. It
should not be mixed with grease or oils. Chemical protective gloves should be worn where repeated
or prolonged contact can occur.
• Screw partially four 25 mm M10 bolts positioning them in the holes (7) on the hybrid flange (ODU
side): each bolt should be tightened to have the square head out of the hole of about 13-14 mm,
use 15 mm spanner
• Apply seal and lubricant grease Dow Corning 4 to the O-ring, protecting fingers with gloves, and
insert in the proper track on the ODU flange
• After the right position has been found, rotate 30° counter clockwise the ODU and approach it to
the antenna flange in order to have the four slots of the Standard Lock cross between the four bolts
on the hybrid
• Rotate 30° clockwise the ODU to hook each slots on the relevant bolt
• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15 mm spanner, torque
= 46 Nm)
• Optional: sun cover kit - insert the sun cover and tie one of its bottom holes to the ODU handle by
means of the black plastic strip included in the sun cover kit
• Now the ODU is ready to be connected to the IDU-ODU cable and to the grounding cable
After having installed the ODU in 1+0 configuration or in 1+1 configuration, the waveguide towards the
antenna must be installed.
• 1+0: the waveguide must be fixed to the antenna flange on the supporting plate of the ODU. In
case of flexible waveguides, an excessive folding can damage the waveguide, see Tab.38 for details.
• 1+1: the waveguide must be fixed to the hybrid. In case of flexible waveguides, an excessive folding
can damage the waveguide, see Tab.38 for details.
Bending radius with- Bending radius with- Bending radius with Bending radius with
out rebending out rebending rebending rebending
Frequency
mm (inch) mm (inch) mm (inch) mm (inch)
E-plane a H-plane b E-plane a. H-plane b.
6 GHz or 7 GHz
200 (7,9) 500 (19,8) 300 (11,9) 600 (23,7)
low
7 GHz high 200 (7,9) 500 (19,8) 250 (9,9) 600 (23,7)
a. Bending E-plane
Rmin/E
Bending E-plane
(short side of the section)
b. Bending H-plane
Rmin/H
Bending H-plane
(long side of the section)
ODU AS
Eyelet terminal
Grounding bolt
Screws
O-ring
ODU ASN
Eyelet terminal
Coupling torque for the grounding bolt is 9.5 Nm
Grounding bolt
O-ring
ODU ASN
Eyelet terminal
Grounding bolt
4
M10
2 (Torque 2Nm)
7
3
4
6
1
114-60
3
5
2
23.1 GENERALS
To install the ODUs of 8+0 system you need the following components:
The 8 IDU-ODU coax cables plus tail must have the same length with a tolerance of 1.5 m.
23.2 N+0
See Fig.148.
• Position the supporting plate (1) on the pole and fix the rear bracket (2) to it by means of the four
130 mm M10 bolt (3) with relevant washers, springs and nuts (use 15 mm spanner, torque = 46
Nm)
See Fig.149.
• Mount the multichannel support (4) on the back of the supporting plate (1) by means of four 25
mm M10 bolts (5) (use 15 mm spanner with torque = 46 Nm) in the holes (6).
• Add lubricant paste, e.g. MOLYKOTE P-40, on threads of four 25mm M10 bolts (8). The sliding sur-
face should be cleaned. The paste should then be applied with a suitable brush, rag or grease gun.
It should not be mixed with grease or oils. Chemical protective gloves should be worn where re-
peated or prolonged contact can occur. Screw partially four 25 mm M10 bolts (8) positioning them
in the holes (7) on the multichannel support (ODU side): each bolt should be tightened to have the
square head out of the hole of about 13-14 mm, use 15 mm spanner (9)
See Fig.151.
• Apply silicon grease e.g. DOW CORNING 4 to the O-ring (10) and insert in the proper track on the
ODU flange
• After the right position has been found, rotate 30° counter clockwise the ODU and approach it to
the antenna flange in order to have the four slots of the Standard Lock cross between the four bolts
on the hybrid
• Rotate 30° clockwise the ODU to hook each slots on the relevant bolt
• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15 mm spanner, torque
= 46 Nm)
• Optional: sun cover kit - insert the sun cover and tie one of its bottom holes to the ODU handle by
means of the black plastic strip included in the sun cover kit
• Now the ODU is ready to be connected to the IDU-ODU cable and to the grounding cable
See Fig.153.
After having installed the ODU in 8+0 configuration, the waveguides towards the antenna must be in-
stalled. The waveguides must be fixed to the antenna flange and on the two multichannel support. An ex-
cessive folding can damage the waveguide, see Tab.39 for details.
See Fig.152.
On optional kit V60366 must be installed onto Multichannel support port where ODU are not installed be-
cause of maintenance or because of N+0 less than 8+0 (e.g. 7+0).
Bending radius with- Bending radius with- Bending radius with Bending radius with
out rebending out rebending rebending rebending
Frequency
mm (inch) mm (inch) mm (inch) mm (inch)
E-plane a H-plane b E-plane a. H-plane b.
6 GHz or 7 GHz
200 (7,9) 500 (19,8) 300 (11,9) 600 (23,7)
low
7 GHz high 200 (7,9) 500 (19,8) 250 (9,9) 600 (23,7)
a. Bending E-plane
Rmin/E
Bending E-plane
(short side of the section)
b. Bending H-plane
Rmin/H
Bending H-plane
(long side of the section)
3
2
Slot 2
Slot 4
10
Slot 3
636
350
1264
Ø 1310
300
599
R482
Ø 114 315
433
839
Ø 1262
R1291
100
105
• equipment switch–on
• check measurements.
In order to have the link working properly, in the local and remote equipment the same parameters have
to be set:
• system layout (1+0, 1+1 hot stand-by, 1+1 frequency diversity.....) (Equipment - Configuration)
• ACM Engine (Equipment - Modulation&Capacity): during Line-up “ACM Engine” must be disable
You can download Web Lct Console program and Flash Player from http://www.siaemic.com.
Proceed as follows:
The relationship between AGC voltage and received field is shown by Fig.156.
The received field level has a tolerance of ±4 dB in the full temperature range.
A factory default address is assigned to each network element that must normally be reconfigurated on
site following the network administrator rules.
For this purpose it is required to connect the PC, where the WEB LCT program has been installed, to the
network interfaces: this has to be done via USB cable or Ethernet cable.
Warning: the checks that follow require the knowledge of the program use.
Run the program and perform the connection to equipment by choosing from menu “Option” the connec-
tion made via USB cable.
• IP Address: select Port Configuration. Enter the required port addresses in the available communi-
cation ports.
• Routing Table and Default Gateway: select Routing table: add the routes and default gateway if nec-
essary.
Warning: the routing policy depends on the routing type: static IP/OSPF/IS–IS. The relevant routing
rules must be normally given by network administrator.
• Remote Element Table: select Remote Element Table. Add station name. Add local equipment IP
address, add remote equipment IP address selecting Remote Link.
• Agent IP Address: select Equipment Properties. Assign the address in accordance to the address of
Ethernet port.
4 If the connection is made via USB cable, the IP address is automatically achieved.
Here are listed few observation to follow during the address/netmask setup:
1. PPP connection (RS232 and LCT ports) - PC address can be selected among:
b. broadcast address -1
c. a given address.
For a correct management, solutions b) and c) must be different than Ethernet port address.
2. PPP connection (RS232 and LCT ports) - if Unnumbered is used, the netmask relevant RS232 and
LCT ports must be equal or wider than the Ethernet port netmask
3. PPP connection (RS232 and LCT ports) - never assign network addresses to RS232 or LCT ports
(check that they are hosts).
It is advisable to perform the following measurements to check the correct operation of the radio hop:
• transmitted power
• received power
• RF frequency
• S/N measurement
- on top of the window Tx/Rx power and frequency values are displayed. In case of Tx power and
frequency setup proceed to Branch 1/2 and Power/Frequencies submenus.
• S/N measurement
- Run WLC program and then perform the connection to the equipment you want to check.
- Perform the S/N measurement and check that values comply with the requirements.
In order to enable the ACM features in the radio links, the following parameters must be set on both ends
just to have the same configuration.
ACM parameters can be set in WEB LCT in Modulation and Capacity card in the window.
ACM engine
• Upper modulation: when propagation, into the given radio channel is in the better condition (high
Rx S/N), the radio link is working at the maximum throughput defined at Upper Modulation: the
highest modulation profile that ACM can employ
• Lower modulation: when propagation into the given radio channel is in the worst condition (low Rx
S/N), the radio link is working at the minimum throughput, defined at Lower Modulation: the lowest
modulation profile that ACM can employ
When more then one ACM profile (different FEC redundancy) is available at the selected reference modu-
lation (i.e.: 4QAM and 4QAM strong), the maximum throughput profile will be automatically selected (i.e.:
4QAM).
When more than one ACM profile (different FEC redundancy) is available at the selected lower modulation
(i.e: 4QAM and 4QAM strong), the minimum throughput profile will be automatically included (i.e.: 4QAM
strong).
When more than ACM profile (different FEC redundancy) is available at the selected upper modulation (i.e.:
4QAM and 4QAM strong), the maximum throughput profile will be automatically included (i.e.: 4QAM).
• Enabled - The Tx power is the maximum allowed in each modulation profile (only if “reference mod-
ulation” is equal to “lower modulation”)
• Disabled - The link uses the same Tx power in each profile (Tx power is the Tx power at “upper
modulation”)
• Reference modulation, with ACM enabled, or used modulation, with ACM disabled
Permanent TDM
Extra TDM
Number of TDM (E1 streams) transmitted besides the permanent TDM, in each ACM profile. In case of Extra
TDM usage, in the Extra TDM Priority card is present the list of which extra TDMs are transmitted.
2,625
2,25
1,875
1,5
1,125
0,75
0 dBm
The parameters necessary to define the management of the radio link are set via WEBLCT through a web
browser (IE, Firefox, Chrome,…) with a page opened at the unit address
• via Ethernet cable to port MNGT 1 or 2 (out of band management, factory default mode). Default
addresses are 172.20.255.15 or 172.20.254.14, netmask is 255.255.255.0. PC and connected unit
must be in the same subnet
• via Ethernet cable to port LAN1,2,3 or 4 (in band management). PC and connected unit must be in
the same subnet
• via USB cable and WEB LCT Console to port LCT. This connection needs no address.
The necessary parameters, in local side and remote side, in order to manage the radio link are the follow-
ing:
• Agent IP Address, equal to Ethernet port Address (Equipment Properties window, General Info card)
• Radio IP Address (Port Configuration and ACL window, Radio card see Fig.158). Push “IP Unnum-
bered” button if the IDU needs only one address: the Ethernet port address. This parameter needs
a double step confirm: set the proper address/netmask push Apply and confirm, push Store and
confirm. This port is available in Out of Band management only
• Remote Element List: the IDU has a list with the local IDU Agent IP (declared Managed By SCT) and
remote IDU Agent IP (declared Remote Link) contained in a folder (Station)
In Out of Band the management channel is separated from traffic and, on radio side, is in a specific OOB
channel (or EOC – Embedded Operating Channel, 128Kb)
Ethernet port MNGT 1 and/or MNGT 2 can be set in the following modes (MNGT VLan Tagging field, see
Fig.157):
• Enable Secure- the port accepts tagged input only (the VLAN tag is set in “VLan ID”, 0 not accepted)
The Radio PPP Mode can be set in three different modes (see Fig.158):
• Client - If local and remote units are in different subnet, Client must be set on both sides
• Server - EOC channel is off. If local and remote units are both managed through Ethernet port,
Server must be set on both sides
• Bridge - If local and remote units are in the same subnet, Bridge must be set on both sides
Management channel is separated by traffic by means of a dedicated VLAN (In Band Management field in
Fig.157).
This mode can be used in a radio link with local and remote units in the same subnet.
• mark all the LAN ports involved in the passage of the management VLAN (LAN 1, 2, 3, 4 or the radio
port A)
• set the VLAN ID used for management VLAN. This VLAN is created automatically and cannot be used
by traffic or other
• the ports involved in In Band management must be set in Fallback (via WEBLCT, Base Band, LAN 1
or 2 or 3 or 4 or Port A, 802.1Q card and 802.1q Setting field)
Example: management network is connected to local unit with port LAN1 and through the radio arrives to
remote unit. The ports to be selected for the in band are the following:
The selection of the traffic ports (LAN 1, 2, 3, 4, port A) for In Band management disables the OOB (128
Kb EOC channel) through the radio towards the remote unit but leaves enabled the ports MNGT 1 and 2
that can be used for the Out of Band access of local unit only.
A group of IDUs, or more radio links, can be managed in Out of Band or In Band mode.
• all the units are in the same subnet: the Radio PPP Mode of each Radio port must be set in Bridge.
Management is transmitted through the 128Kb OOB (or EOC) channel.
• in each radio link the local unit (closer to management PC) and the remote unit are in different sub-
net: the Radio PPP Mode of each Radio port (local and remote) must be set in Client. From the first
unit closer to the PC up to the penultimate, the Routing tables must be configured in order to allow
the management to arrive to the last IDU, while the opposite direction is available using properly
the Default Gateway of each unit. Management is transmitted through the 128Kb OOB (or EOC)
channel.
Exactly as in the single radio link, unit by unit, using the WEBLCT in Port Configuration & ACM, Ethernet
card, In Band Management field (see Fig.157):
• select all the ports involved in the passage of management VLAN (LAN 1, 2, 3, 4 and Port A)
• set the VLAN ID used for management VLAN. This VLAN is created automatically and cannot be used
by traffic or other
• set the ports involved in In Band management in Fallback (via WEBLCT, Base Band, LAN 1 or 2 or
3 or 4 or Port A, 802.1Q card and 802.1q Setting field)
24.3.2 Node
A Node is a group of IDUs, up to 8, connected together by means of LAN1 and LAN2 ports, if the Node
involves Ethernet traffic, and/or NB connectors, if the node involves E1 transmission from an IDU to an-
other of the same node.
Node management can be obtained in Out of Band or In Band mode, in any case all the IDUs of the node
must be in the same subnet.
All the IDUs are connected together by means of a cascade of Ethernet cables between ports MNGT 1 and
2: port MNGT 1 is connected to port MNGT 2 of the adjacent IDU and so on. The port MNGT 1 of the last
IDU of the node remains not used while the port MNGT 2 port of the first IDU is connected to management
PC/network.
All the IDUs are connected together by means of ports LAN 1 and LAN 2: ports LAN 2 of an IDU is connected
to port LAN 1 of the adjacent IDU. The port LAN 1 of the last IDU must be connected to port LAN 2 of the
first IDU. The Ethernet loop is avoided by means of an internal protection protocol.
In each IDU (see Fig.157) in Ethernet card, In Band Management field, the following operations must be
performed:
• select ports LAN 1 and LAN 2 and, if the IDU has a remote unit (the eventual remote unit must be
in the same subnet), port A also (and, in remote unit, the remote port A).
• set the ports involved in In Band management in Fallback (via WEBLCT, Base Band, LAN 1 and 2
and Port A, 802.1Q card and 802.1q Setting field)
The node is connected to management network/PC by means of the remaining ports LAN 3 or LAN 4 (also
this port must be selected) or MNGT 1 or 2.
25.1 SCOPE
This chapter describes the procedure to back up the full equipment configuration. This permits to recover
the original equipment configuration in case of faulty CONTROLLER module replacement with spare.
Foreword: it is advisable to backup the configuration after the first installation. Proceed as follows:
1. Select “Equipment Configuration Wizard” from menu “Tools”; “Equipment Configuration Wi-
zard” window will be displayed.
2. Select “Upload” and then “Backup Full Equipment Configuration”; “Template Selection” win-
dow will be displayed.
3. Select the correct equipment template (in case of uncorrected choice the backup will be aborted).
4. Press OK and then select the equipment to be uploaded from “Upload Configuration File” window.
5. Press OK and then edit the file name from “Save backup as” window.
6. Press Save; “Equipment Configuration Wizard: Complete Backup” window will appear.
The window shows dynamically the backup procedure. If everything is OK, at the end of the upload
will appear the word “done” showing the procedure success.
7. Press OK to finish.
Once the spare controller has been installed, or every time you need the primitive configuration, proceed
as follows:
1. Select “Equipment Configuration Wizard” from menu “Tools”. “Equipment Configuration Wizard”
window will be displayed.
2. Select “Download” and than “Restore Full Equipment Configuration” from Equipment Configu-
ration Wizard. “Select Backup File” window will be displayed.
3. Select the wanted backup file with extension .bku and then press Open. “Download Configuration
File” window will be displayed.
5. Press OK to finish.
Foreword: it is advisable to backup the configuration after the first installation. Proceed as follows:
2. in the field “Backup File name” write the name of the configuration file you are going to upload in
the PC, complete with the full path of its folder
3. push Backup. The status of the backup procedure is shown in the “Operation Status” field.
Once the spare Controller has been installed or every time the saved configuration is necessary, proceed
as follow:
2. select “Browse local system” in order to locate the configuration file you need and push Open when
it has been found
3. Push Restore. The status of the backup procedure is shown in the “operation Status” field. During
Restore operation the equipment creates a backup configuration, you can come back to this config-
uration at the end of the restore pushing Revert.
A SD card slot is available on the ALplus2 Controller module (on the board) or on the front panel of
ALCplus2.
Using a SD memory card is possible to perform an auto restore of Configuration and of Equipment Firmware
every time a mismatch between running ones and saved occurs.
5. select Execute
6. remove SD
This paragraph deals with line-up of ALplus2 LIM Ethernet and ALCplus2/ALCplus2e IDU with details of WEB
LCT program related only to Ethernet application.
Main difference is the number of LAN ports: three in ALplus2 and four in ALCplus2/ALCplus2e, moreover
in ALplus2 the LAN2 port can manage POE functionality besides in ALCplus2/ALCplus2e Sync Signal can be
taken from LAN ports also (see relevant paragraph).
Assuming that the radio link is already in service, with correct frequency, output power and correct antenna
alignment, the line up procedure for two different kinds of connection set up of a radio link ALplus2,
equipped with LIM module with Ethernet ports, is hereafter described:
• Local Lan-1 port to remote Lan-1 port connection Lan per port, see Fig.159
• from 3 ports to 3 ports connections and segregated traffic for Untagged Traffic, see Fig.167
• from 3 ports to 3 ports connections and segregated traffic for Tagged and Untagged Traffic, see
Fig.177.
Settings here below are intended to be done both into local and remote radio equipment. The software to
be used to configure the equipment is WEB LCT. In the following chapter the figures used as example can
differ in the position of main commands depending on WEB LCT release.
switch switch
Lan-2 AL AL Lan-2
radio radio
Lan-3 Lan-3
Nx2 Nx2
Mbit/s Mbit/s
Local Remote
The first example is local Lan1 port to remote Lan1 port transparent connection for tagged and untagged
traffic please refer to Fig.159.
ACM Engine, Upper Modulation, Lower Modulation, Permanent Traffic and extra TDM Capacity at any mod-
ulation must be the same local and remote.
The throughput at any modulation with 28 MHz bandwidth is shown in Fig.161 with View Current Config
button of Fig.160.
See Fig.162 for general settings of the switch. All the used ports must be Enabled, so enable Lan-1 and
Internal Port A, see Fig.163.
Please notice the MAC Address Aging Time reduced, only for this test at 15 sec.
The other ports should be disabled. The correct cable crossover arrangement must be selected too (see
Fig.163). Enable LLF, if needed, only at the end of link line up.
Switch connections are done with Lan per port selections. Referring to Fig.164, incoming traffic at Lan-1
exits at internal Port A and as in Fig.165 and in Fig.166 incoming traffic at internal Port A exits at Lan-1
port. This connection are done for all Untagged packets and all Tagged packets with Vlan Id not described
into Vlan Configuration Table.
If Vlan Configuration Table is blank all Tagged traffic follows the rules of Lan per port.
• "Disable 802.1q": no check of Virtual Lan tag is done and all packets follow Lan per port settings
• "Fallback": if Tagged packets have their Vlan Id into Vlan Configuration Table they follow the con-
nection described into the table, otherwise they follow the Lan per port settings as Untagged pack-
ets
• "Secure": no Untagged packet transits; only Tagged packets with Vlan Id listed into the table can
transit.
For all previous configuration "Disable 802.1" should be selected. With Egress Mode as Unmodified the out-
going packets at Lan-1 port exit Untagged or Tagged exactly as they were Untagged or Tagged at the in-
coming port.
switch switch
Lan-2 AL AL Lan-2
radio radio
Lan-3 Lan-3
Nx2 Nx2
Mbit/s Mbit/s
Local Remote
In this example 3 local port must communicate with corresponding 3 remote ports. All the ports share the
same radio channel but traffic originated and directed to Lan1 should be kept separated from traffic from
Lan2 and Lan3 and viceversa.
Lan-2 and Lan-3 have the same requirements. Please refer to Fig.167.
ACM Engine, Upper Modulation, Lower Modulation, Permanent Traffic and extra TDM Capacity at any mod-
ulation must be the same local and remote.
So with 4QAMstrong modulation the Ethernet capacity is 20 Mbit/s and with 256QAM modulation the Ether-
net capacity is 140 Mbit/s.
See Fig.170 for Switch general settings of the switch. All the used ports must be Enabled, so enable Lan-
1, Lan-2, Lan-3 and Internal Port, see Fig.171.
Please notice the MAC Address Aging Time reduced, only for this test, at 15 sec. The correct cable crossover
arrangement must be selected too (see Fig.171). Enable LLF if needed only at the end of link line up.
If Vlan Configuration Table is blank all Tagged traffic follows the rules of Lan per port.
• "Disable 802.1q": no check of Virtual Lan tag is made and all packets follow Lan per port settings
• "Fallback": if Tagged packets have their Vlan Id into Vlan Configuration Table they follow the con-
nection described into the table, otherwise they follow the Lan per port settings as Untagged pack-
ets
• "Secure": no Untagged packet transits; only Tagged packets with Vlan Id listed into the table can
transit.
Each port of the switch must be associated with a different Default VLAN ID, Lan-1 with Default VID 4001,
Lan-2 with Default VID 4002, Lan-3 with Default VID 4003, for Lan-1 see Fig.171 and Fig.172.
Untagged packets coming at physical ports are tagged on common radio channel but tagged with different
Vlans. At receiving end packets are distributed at their ports and untagged.
Vlan Configuration Table will be defined in order to group traffic from Lan-1, Lan-2, Lan-3 to Port A.
switch switch
Lan-2 AL AL Lan-2
radio radio
Lan-3 Lan-3
Nx2 Nx2
Mbit/s Mbit/s
Local Remote
Fig.177 - 3 ports to3 ports connections with segregated Tagged and Untagged traffic
In this example 3 local port must communicate with corresponding 3 remote ports. All the ports share the
same radio channel but traffic originated and directed to Lan1 should be kept separated from traffic from
Lan2 and Lan3 and viceversa.
Lan-1 to Lan-1, connection must transfer tagged and untagged packets. Lan-2 and Lan-3 have the same
requirements. Please refer to Fig.177.
ACM Engine, Upper Modulation, Lower Modulation, Permanent Traffic and extra TDM Capacity at any mod-
ulation must be the same local and remote.
The throughput at any modulation with 28 MHz bandwidth is shown in Fig.179 with View Current Config
button of Fig.178.
See Fig.180 for Switch general settings of the switch. All the used ports must be Enabled, so enable Lan-
1, Lan-2, Lan-3 and internal Port A, see Fig.163.
For already Tagged traffic we need to add a second Vlan Tag to the packets creating the Vlan of Vlan into
radio channel, so we need a Max packet size of 2048.
27.1 TOOLS
The following procedure can be done with SCT/LCT or with Web LCT and similar windows.
27.2 PROCEDURE
2. Clear the Stored Routing Table on remote equipment and add new lines to it
3. Set the new Agent and restart remote equipment
5. Prepare Subnetwork on local equipment, capture the remote equipment and send it the new sub-
network
Configuration
Configure:
If you have other port to configure ex. PPP RS232 - 2Mbit/s EOC etc. configure it with IP and netmask
Select menu Equipment -> Configuration Setup -> Stored Routing Table
Add new routine lines (relevant the new addresses configuration) pushing the Add button.
When the Stored Routing Table is complete, push Apply and then Save.
Select menu Equipment -> Properties. Set new Agent (equal to Ethernet port address).
Push Restart and then Confirm.
After the restart, the Remote Equipment disappears from SCT display.
Configure the local equipment with the same procedure seen before. Then restart the local equipment.
To see both local and remote equipment the new subnetwork (station and equipment) must be prepared.
When the remote equipment appears in Actual Configuration, prepare again the network configuration you
have set before (or select the local equipment, push Retrieve) and send the configuration to remote equip-
ment.
28.1 OVERVIEW
The following paragraph deals with the activation of the Node with Nodal IDU unit with details of the SCT/
LCT program relevant to the functionalities offered by the cross-connection matrix and Ethernet switch in
relation to the achievable connections.
Supposing that the radio links are already commissioned, the following items are described:
• ethernet switch.
The connections among the IDUs in the node are the following:
• connections for E1: Nbus cables are used (connectors NBUS1 and NBUS2 are involved)
• connections for Ethernet: Ethernet cables are used (ports LAN1 and LAN2 are involved).
Remember that in a node for Ethernet Traffic can be used port 3 and port 4 only because port LAN1 and
LAN2 are used for nodal connections.
IDU1
LAN1 LAN2 NB1 NB2
IDU2
LAN1 LAN2 NB1 NB2
Max 8
IDU3
LAN1 LAN2 NB1 NB2
IDU8
LAN1 LAN2 NB1 NB2 LAN1 and LAN2 are used for cabling
The operations to enable the functionalities offered by the internal cross-connection matrix and Ethernet
switch are the following:
• run the software SCT, select tools and Subnetwork Configuration Wizard
• insert all the Nodal IDU present into the Node, all these Nodals must be reachable and connected
• configure the Node with Station name, Node name, define is Nodal cables are Protected or Not
Protected
• configure the Node indicating the number of IDU setting the Node for E1 TDM traffic, Number of
TDM Elem.
• configure the Node indicating the number of IDU setting the Node for E1 TDM traffic, Number of
ETH Elem.
• insert the IP number of the IDU setting the Node and press Apply Config button
• to run the software WebLCT, open Equipment Menu, TDM Tributaries, E1 and select the type
of used tributary
• to enable the E1 and/or STM-1 tributaries (transport of 63 E1 each) involved by the cross-connec-
tion
• in case of STM-1 streams, configure the parameters VC4 (Label - TUG Structure) and any VC12 (La-
bel: Asynchronous) and the synchronization parameters (WebLCT, Equipment Menu, Synchro-
nisation).
The operations to configure a cross-connection can be done IDU by IDU into WebLCT or easier into the
Nodal ALCplus2 Manager:
• run the software SCT, open Network, Nodal ALCplus2 Manager and press Cross-connection
- tributary - radio: cross-connection between the tributaries available on the front side of IDUs
(E1, STM-1, IDU1 to IDU8) and the tributaries available on the radio link, IDU1 to 8 Radio Extra
E1 and Permanent E1
- tributary - tributary: cross-connection between the tributaries available on the front side of IDUs
(E1, STM-1, IDU1 to 8).
• select the type of tributary to use on the front side of the IDU: the relevant E1 streams will be dis-
played in the window together with the number of E1 streams relevant to the radio link
• select which radio link you want to use in cross-connection (up to eight available)
• move the symbol of the E1 stream (the number corresponds to the physical position in the connec-
tor of the IDU) by dragging and dropping from a type of tributary to the position to use in the radio
frame, see Fig.200.
• the tributaries in the radio frame (link direction A or others) can be involved in a tributary loop to-
wards the corresponding remote radio by means of a double click on the relevant box that points
out the position in the frame, see Fig.201
• the tributaries on radio side can transit directly from a radio link to the other without need to pass
from the tributaries on matrix side: by means of drag’n’drop, a box relevant to an E1 on radio side
is moved from a link to the other link. The two involved links must be selected in the fields 1st Radio
and 2nd Radio. A pass- through (transit) cross-connection is so executed: see Fig.202
• select the two types of tributary (1st tributary and 2nd tributary) on the front side of the IDUs mod-
ule to use as ends: the relevant E1 streams will be displayed in the top and bottom part of the win-
dow
This type of cross-connection includes even those relevant to the transport of E1 streams from a nodal IDU
to another one belonging to the same node.
For Ethernet connections the Nodals are as one big switch with two Lan ports and a radio Ethernet port for
any IDU.
Connections between the IDU are not shown into SCT but are programmed automatically by SCT in order
to create the big switch.
Setting of the Ethernet switch is performed through Nodal ALCplus2 Manager which then programs any
Nodal part of the switch.
All settings of Ethernet switches part of the Node can be done directly into Nodal ALCplus2 Manager.
29.1 INTRODUCTION
The goal of this chapter is to define a procedure to add one (or more) ALCplus2 IDU to an existing node of
similar IDUs, carrying live traffic. This procedure is applicable to the following IDUs:
• GAI0162
• GAI0163
equipped with system versions 01.01.xx.
In the following paragraphs some screenshots are provided, related to a 3-IDU node expanded to a 4-IDU
node, as an example. The example can be easily applied to a N-IDU node (i.e. a node composed by a num-
ber of IDUs equal to N) expanded to N+K-IDU node: the 3 to 4 IDU case corresponds to the N=3 K=1 case.
This procedure does not provide specific guidance about the GEthernet traffic: with this respect the node
expansion shall be treated as an usual case of interconnection between Ethernet Switches, implementing
Rapid Spanning Tree Protocol.
Attention: this procedure covers also the case when you want to withdraw one (or more) IDU from the
node.
29.2 PRECONDITIONS
The SCT distribution to be used to perform this task shall be 4.6.8 or greater.
All the IDUs are reachable by the PC running the SCT/Web browser. All the operations performed via SCT/
WebLCT shall be done logged as 'System' into the relevant equipment.
The existing node is composed by IDUs configured as "AlcPlus2 (Protected)". See hereafter the screenshots
relevant to an example.
• …
• …
• …
• …
29.4.1 Step 1
Install the K new IDUs in the same rack where the existing node is installed (or in an adjacent rack, pro-
vided that the NBUS cables length is compatible with the installation). Do not connect the N-BUS cables
to the new IDUs.
Configure the new IDUs as "AlcPlus2 (Protected)", with the following parameters:
• Nodes Id: from N+1 to N+K, depending on the IDU position inside the node
29.4.2 Step 2
Interconnect the new IDUs with the nodal bus, as per rule in 29.2 PRECONDITIONS. Do not connect the
new IDUs to the existing IDUs.
Alarms will appear: some possibly related to E1 traffic (depending on the existing interconnections) and at
least two one related to the nodal bus interruption. The E1 related alarms will disappear as soon as the
protection on the N-BUS will take place. The N-BUS related alarms will remain. See screenshots hereafter
as an example.
29.4.4 Step 4
Change configuration of IDU 1 and IDU N, modifying the 'number of nodes' parameter from N to N+K.
Change configuration of IDUs from number 2 to number N-1, modifying the 'number of nodes' parameter
from N to N+K.
Connect the N-BUS from IDU N to IDU N+1 as per rule in paragraph 29.2 PRECONDITIONS. Connect the
N-BUS from IDU N+K to IDU 1, as per rule in paragraph 29.2 PRECONDITIONS.
Depending on the number and kind of interconnections among the IDUs, there will be errors and/or AIS
on some of the E1, due to the traffic protection intervention on the N-BUS. The typical duration of the traffic
interruption, measured at E1 level, is around 1s.
Basically this procedure consists in reverting the steps done to expand the node.
Disconnect the N-BUS from IDU N to IDU N+1 and from IDU N+K to IDU 1.
Depending on the number and kind of interconnections among the IDUs, there will be errors and/or AIS
on some of the E1, due to the traffic protection intervention on the N-BUS. The typical duration of the traffic
interruption, measured at E1 level, is around 1s.
The N-BUS related alarms shall appear in IDU 1, IDU N, IDU N+1 and IDU N+K.
29.5.2 Step 2
Change configuration of IDU 1 and IDU N, modifying the 'number of nodes' parameter from N+K to N.
Change configuration of IDUs number 2 to number N-1, modifying the 'number of nodes' parameter from
N+K to N.
Connect the N-BUS from IDU N to IDU 1, as per rule in paragraph 29.2 PRECONDITIONS.
Depending on the number and kind of interconnections among the IDUs, there will be errors and/or AIS
on some of the E1, due to the traffic protection intervention on the N-BUS. The typical duration of the traffic
interruption, measured at E1 level, is around 1s.
At the end of a transitional period the N-BUS related alarms shall disappear.
29.5.4 Step 4
This mode is available only for equipment belonging to an ALCplus2 node and interconnected by nodal Bus
Ethernet. The radio Trunking mode allows aggregating some radio streams of a nodal system.
To insert a radio port of a switch in the Trunk, it is necessary to enable the radio Trunking mode for this
port (Enable-Trunk1). In this mode, up to 4 radio ports can be aggregated.
The use of the radio Trunking mode is alternative to the use of the Spanning Tree protocol.
30.1.1 To verify the status of the internal port in relation to the trunking
mode
Operations available only if the equipment belongs to an ALCplus2 node and is interconnected to the other
node elements by the nodal Bus Ethernet.
1. Select the Equipment Menu > Base Band > Port A command. The Port A contextual area opens.
2. Bring in front of page the STP/Trunking tab. The tab points out the status of the port in relation to
the Trunking modality or to the Spanning Tree protocol.
Fig.219 reports an example of the tab when the Trunking modality is active.
If the STP protocol is enabled the parameter Trunk is automatically forced to the value Disable. To modify
the value, it is first necessary to disable the Spanning Tree protocol. STP Parameters relevant to the Span-
ning Tree protocol.
Operations available only if the equipment belongs to an ALCplus2 node and is interconnected to other el-
ements of the node through nodal Bus Ethernet. The Trunking modality cannot be enabled when the Span-
ning Tree protocol is enabled.
• Select the Equipment Menu > Base Band > Port A command. The Port A contextual area opens.
• Bring in front of page the STP/Trunking tab. The Trunk parameter points out the enabling status of
the Trunking mode for the selected port (see Fig.219).
This mode is available for a connection between IDU and ODU and from a node to other node connected
via Lan ports.
1. Select the Equipment Menu > Base Band > LAN 1, LAN 2, LAN 3 or LAN 4 command.
Parameter:
• Status. Status of the port as regards the LACP (Link Aggregation Control Protocol):
• Partner Id. MAC Address of the remote equipment located at the other end of the Ethernet connec-
tion (remote switch).
Value:
• Enable-Trunk2. Trunking mode enabled. The considered LAN port is aggregated to the equipment
LAN ports, whose considered parameter has value Enable-Trunk2.
• Enable-Trunk3. Trunking mode enabled. The considered LAN port is aggregated to the equipment
LAN ports, whose considered parameter has value Enable-Trunk3.
• Enable-Trunk4. Trunking mode enabled. The considered LAN port is aggregated to the equipment
LAN ports, whose considered parameter has value Enable-Trunk4.
It is possible to aggregate up to 4 LAN ports for each group (Trunk). Another example is to aggregate two
Lans on Trunk1 and other two Lans on Trunk2. Send Trunk1 to one IDU and Trunk2 to a second IDU.
All the Lan port belonging to a group (Trunk) must have the same speed.
If the equipment belongs to an ALCplus2 node and it is interconnected to other elements of the node
through nodal Bus Ethernet, this operation is available for the external ports LAN3 and LAN4.
Please, first read paragraph “8.8 ETHERNET OAM (Operation Administration and Maintenance)”.
Do the same on remote equipment. Now it is possible to verify the status of connection with Remote MEP
(Rmep), or send a Loop back Message (Lbm) or send a Link trace Message (Ltm)
32.1 FM DOMAIN
In details it is possible:
The name or the level of an OAM domain associated to an equipment cannot be modified. In order to modify
one or both the parameters, it is necessary to remove the current domain and to define a new one.
• Select the Equipment Menu > Maintenance > OAM-FM Domain command.
The OAM-FM Domain contextual area opens where the name and level of the OAM domain of the equipment
are displayed Fig.221.
• Select the Equipment Menu > Maintenance > OAM-FM Domain command. The OAM-FM Do-
main contextual area opens (see Fig.221).
• Into the Domain box, type the OAM domain name of the equipment (alphanumeric string with min-
imum 1 and maximum 45 characters).
• Move the cursor Level over a number between 0 and 7 according to the priority level you wish to
assign to the OAM domain (0: lowest priority, 7: highest priority).
• Press Create.
This command is available only if an OAM domain has been defined for the equipment (see Fig.221).
The OAM-FM MA/MEP command manages the maintenance points of the OAM domain of the equipment.
To verify the status of the VLANs as regards the OAM Ethernet protocol
• Select the Equipment Menu > Maintenance > OAM-FM MA/MEP command.
The OAM-FM MA/MEP contextual area opens, pointing out the status of the VLANs in relation to the OAM
Ethernet protocol.
Every VLAN is represented by a rectangle whose characteristics are described here below see Fig.223.
Status of the port as regards the transit of packets with VLan ID equal to that of the VLAN:
• ----, the port is not enabled to the transit of the packets with VLan ID equal to that of the virtual
Lan, other possible settings are: Untag, Tagged, Unmodif.
Push-buttons:
The availability of the push-buttons depends on the status of the selected VLAN.
If a MA or a MEP is associated to the VLAN, only the Unbind push-button will be available.
In Fig.222 the arrow shows direction of messages, in this case the messages are sent into the equipment
at Lan 3 port. Further details can be found into Help on-line of WebLct for ALCplus2.
The Ethernet Line Protection (ELP) is a function which allows implementing a protection at physical level
(Level 2) between two or more LAN external ports.
When the user enables the Ethernet line protection, even the management of the ELP switch is enabled.
The switch operates in automatic mode: the equipment executes the switch when the LOS alarm is present
on the LAN port in service. When the alarm clears, the controller does not execute the switch again.
The Ethernet line protection is implemented by means of proprietary protocol. As consequence, the ELP
switch is managed without considering alarms or settings executed on the equipment on the other side of
the LAN connection.
In ALCplus2 equipment, the line Ethernet protection can be enabled at equipment level or at node level.
This last chance is available and meaningful only for the equipment belonging to an ALCplus2 node and
which are interconnected to other node elements through the nodal Bus Ethernet.
The port with highest priority (that is lowest number) is selected. The port with lowest cost is selected
(ports with same speed, as the protected two, have same cost).
Access Control List (ACL) permits to define a list of IP address allowed to control the equipment.
Before activating Enable please create the list of allowed IP address, see Fig.225.
After creating a correct list of allowed IP address it is possible to Enable the ACL, see Fig.226.
Warning: with no address into the list and Enable active no computer can access the equipment via Lan.
With USB cable it is always possible to access the equipment.
ACL is effective only on local equipment, remote equipment reached by routing are not affected by local
ACL.
Local Remote
SETS SETS
NBUS
STM -1
NBUS
LAN3 , 4
STM-1
TRIBA =
2MHz/2Mbit LAN3 , 4
Examples:
1. Synchronisation is coming from Lan3 local (working at 14 Gbit) and it is exiting from Lan3 on remote
radio
2. Synchronisation is coming from E1 tributary 1 and it is exiting from E1 tributary 1 on remote radio.
The starting point is that local SETS circuit is synchronised by an external source which may be one of the
sources shown in the picture so also Lan3 or Tributary 1. Sources can be one or many with different pri-
ority.
Synchronization signal is transmitted from local radio to remote radio via radio frame timing.
Remote SETS is synchronised by incoming radio frame generated by local SETS that is with SDH quality.
All local signals are generated by SETS and will have the same frequency precision and stability.
See Fig.228.
With WebLct go to Configurator -> Sync Enable -> Enable, press Apply and Confirm. Now into Equipment
Menu a new item Synchronization is available.
See Fig.229 into Synchronization the system is synchronised from Internal Source.
See Fig.230, now select TE-Lan3 and select Enabled with priority 1 which is the maximum.
See Fig.231, now if Lan3 is connected to a Lan port working at 1Gbit, the SETS is synchronised by Lan 3.
But Lan 3 Interface must be programmed as Slave and external Lan port must be programmed as Master
(for Gbit clock).
Now if local radio is receiving a correct signal, the SETS is synchronized by Lan 3 as in Fig.232
Now if remote radio is receiving a correct signal the SETS is synchronized by radio as in Fig.234.
See Fig.235.
E1 tributary N is used as a signal transfer and a synchronization source for external equipment into remote
site.
Local SETS is synchronised by E1 Trib. 1. Remote radio SETS is synchronised by receiving radio frame.
We must Enable E1 Retiming so the E1 Trib. 1 at remote site can be used by external equipment as an
SDH synchronism source as in Fig.236.
Fig.229
Fig.231
Fig.233
Local Remote
SETS SETS
Modem
TRIB1 Modem
Memory TRIB1
E1Trib1 used as 2Mbit timing source on remote for external equipment, needs
E1 retiming = Enabled on remote
Fig.235 - E1 retiming
This chapter describes how to prepare a commissioning report regarding the installation of a link.
This report helps an installation team in the check of all the steps performed during the job.
36.1.1 Documentation
The site is installed and commissioned according to the following documentation set:
The site must be installed and commissioned according to the Link document.
Checked
Item DESCRIPTION OK NOT OK
36.1.3 Configurations
Equipment Modulation/Bandwidth
XPIC East-West
Elevation
Polarization (H / V)
Link ID
User Input 1
User Input 2
User Output 1
Agent IP address . . . .
Ethernet IP Address . . . .
IP Net Mask . . . .
IP Net Mask . . . .
Radio 1 IP Address . . . .
IP Net Mask . . . .
Radio 2 IP Address . . . .
IP Net Mask . . . .
Default Gateway . . . .
Interface
ADDRESSES
Agent IP address . . . .
IP Address . . . .
Ethernet
IP Net Mask . . . .
IP Address . . . .
LCT PPP
IP Net Mask . . . .
IP Address . . . .
IP Net Mask . . . .
IP over OSI
EOC radio User Network Bridge
Default Gataway . . . .
Interface
Comments:
Executed by:
Note: The purpose of this inspection is to be sure that the site is ready for the commissioning of the Radio
Link.
Checked
Item DESCRIPTION OK NOT OK
Structure for the support of the ODU unit correctly installed and ori-
3
ented to the required direction
Panel for antenna cable ingress drilled and provided with gaskets for
6
tin passage
Notes:
___________________________________________________________________________________
___________________________________________________________________________________
Comments:
Executed by:
Checked
Item DESCRIPTION OK NOT OK
1 Equipment setup
3.5 DCN cables and/or inserted terminations (if used, otherwise present)
Enabled Disabled
Trib A Priority:_____
4.2 STM-1 MST mode None 1+0 1+1 MSP 1+1 MSP no ALS
5 Radio parameters
TX1 (MHz):
5.1 Set TX and RX frequencies Branch 1
RX1 (MHz):
TX2 (MHz):
5.2 Set TX and RX frequencies Branch 2 (1)
RX2 (MHz):
6 ATPC
Branch 1 MHz/QAM
7.1 Reference Bandwidth and Modulation
Branch 2a MHz/QAM
Enabled
7.2 ACM engine
Disabled
4QAM-st
4QAM
8PSK
32QAM
64QAM
128QAM
256QAM
9 RX quality Link
11 General settings
Comments:
Executed by:
Fig.237
Connect an E1 Transmission analyser to the DDF and check NO ERRORS or ALARMS for each E1 tributaries.
Connect all Ethernet tributaries to the router/switch and check NO ALARMS (i.e LAN LOS) for each ETH
tributaries.
Checked
Item DESCRIPTION OK NOT OK
Check NO ERRORS or ALARMS for each E1, STM-1 and ETH tributaries.
1
Check mechanical stability of the connections.
E1 TRIBUTARY 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
ERRORS / ALARMS
E1 TRIBUTARY 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
ERRORS / ALARMS
E1 TRIBUTARY A B
ERRORS / ALARMS
STM-1 1 2
ERRORS / ALARMS
ETH TRIBUTARY 1 2 3 4
ALARMS
Comments:
Executed by:
Fig.238
Disable the ACM Engine and set the modulation scheme in compliance with the reference modulation by
project.
SIAE Microelettronica radio systems have an embedded PTX manual attenuation (up to 20dB for the ODU
Universal ASN/ASNK, using the automatic Fade Margin procedure by webLCT, and up to 40 for the ODU
Advanced AS-03) in order to attenuate via SW the transmit power and therefore the received field in the
opposite station. If the TX internal attenuation is not enough to verify the Link Fade Margin, there are two
solutions:
• insert a fixed or variable attenuator between the ODU and the antenna (recommended solution).
• verify the Link Fade Margin in the maximum modulation available, only if the Link project report
include all parameters about this modulation (Calculated Fade Margin, RX threshold, etc.).
DESCRIPTION
Comments:
Executed by:
Fig.239
Fig.240
Enable tributary PPI 1 and connect a PDH analyser (Tx, Rx) on the local NE tributary E1#1. Set E1#1 to
"Line Loop On".
Fig.241
Enable tributary E1#1 (on local and remote NE) and connect a PDH analyser (Tx, Rx) on the local NE trib-
utary E1#1. Set on Remote NE E1#1 to "Remote LoopOn".
Fig.242
Enable tributary PPI 1 (on local and remote NE) and connect a PDH analyser (Tx, Rx) on the local NE trib-
utary E1#1 (PPI 1).
Fig.243
RF Loop
Enable tributary PPI 1 (on local and remote NE) and connect a PDH analyser (Tx, Rx) on the local NE trib-
utary E1#1 (PPI 1).
Comments:
Executed by:
IDU Settings
To verify the Ethernet performances set both equipment following this table:
PORT PARAMETERS
Interface
Port Rate Control M/S Autoneg Master/Slave Flow Control Cable crossover Mac Learning Speed/Duplex
Connect the PC as shown in the following figure and set IP Ethernet Address in the same subnetwork of
the MNGT/1 IP Ethernet of the remote terminal.
Connect, by means of a CAT5 cable, LAN1 port to MNGT/1 IP Ethernet port of the remote terminal.
A ping test between the PC and the MNG/1 port of the remote terminal, connecting them directly through
a CAT-5E cable, is required.
Fig.244
RESULT
OK NOT OK
PING test
Comments:
Executed by:
Fig.245
Checked
Item DESCRIPTION OK NOT OK
3 Link Residual BER via internal PRBS test set (by Web LCT)
3.2 Protected system 1+1: measure >12 hours on Branch 1 (manual switch)
NO ERRORS
Comments:
Executed by:
Checked
Item ALARM CABLING (IF REQUIRED) OK NOT OK
Check of the functionality of the alarm cabling forcing the error condition on
7
the equipment
Checked
Item DESCRIPTION OK Not OK
1 Completed equipment
Comments:
Executed by:
DATE
Item DESCRIPTION
dd/mm/yyyy
Notes:
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
This certificates that the equipment listed below with the respective order/s has passed the Final Test.
Order number
Equipment Type:
www.siaemic.com
37.1 GENERAL
In these pages a description of alarms is given in order to help operators to perform equipment trouble-
shooting.
37.2 TROUBLESHOOTING
• traffic is interrupted
• Rx signal quality and/or Rx signal level are lower than the expected
By means of alarms, historical alarms and “Performance monitoring” the operator can imagine the cause
of the problem. By means of loops, causes can be confirmed and a solution can be applied.
• Green: Power on
• red URG Critical and Major alarms (traffic down, IDU reachability, hardware faulty)
• red NURG minor and earning alarms (traffic, quality and configuration problems)
• yellow TEST manual operation active (loops and commands that can cut the link).
• in alarm histories of local and remote side, the same situation is present or not
• any recent operations or commands have been performed over the link, or not
• the link has been without problems for a long time or the link is a “problematic” one
• BER tester (advisable but not mandatory because ALCplus2e has a software one built-in)
Warning: If power supply alarms are present, these must be faced at first. If test LED is ON, check if any
manual operations that can cut the traffic are present or not.
WEBLCT
• status of alarms
• performance monitoring in the last 48h (Rx quality, modulation profile, Rx power)
• configuration
NMS5LX/NMS5UX
• status of alarms
• configuration
Warning: refer to proper software manuals for information relevant to these items.
• Tx - This line starts in IDU and arrives at ODU output flange: when a situation of more alarms is
occurring, the most significative alarm of them is the lower in Tx direction, all the others are prob-
ably caused by this
• Rx - This line starts in ODU RF flange and arrive at IDU: when a situation of more alarms is occur-
ring, the most significative alarm is the higher in Rx direction, all the others after are probably
caused by this.
Examples
1. “Radio 1A RT VCO Fail” alarm in the ODU gives alarm also in IDU (Rx dir.) ->Demodulator Fail alarm
2. An antenna input < -80dBm -> Rx Power Low -> Demodulator Fail alarm -> Rx Quality warning and
Rx Quality alarm.
ODU ODU
Rx
Cable Most significant alarm Cable
Tx
IDU IDU
Alarms are divided in groups depending on functionality or hardware module that has the failure or the
problem described by the alarm itself.
• most common scenarios with the problem that has generated them
- severity
• quality problems: cause that generates the problem (rain or interferences). An easy example of
troubleshooting using Performance monitoring.
Rx quality low
IDI E1-G.704 Line side AIS AIS in the E1 (line side) for EOC Check E1 status/E1 generator side
IDU E1 - G.704 Internal side AIS AIS in the E1 (radio side) for EOC Check E1 status/E1 generator side
RADIO - Local-Remote Term Set- Local and Remote units have dif- Check Mod-Capc.-E1perm-
up Mismatch ferent config E1extra setting
One Plus One IDU Active Status IDU status in 1+1 XPIC config only
One Plus One Configuration Mis- Wrong IDU status in 1+1 XPIC
Check configuration
match config only
Remote Xpic Procedure: Tx- In remote unit there’s a TxOff Check the rem Rx with TxOff: Rx
<...>Off caused by FMP active problems
Ethernet Compr./Fragm. Config Local and Remote have different Check compression and fragmen-
Mismatch compr/fragm setting tation setting
One Plus One Preferential IDU is Working IDU is not the preferen-
Check twin IDU alarms
not active tial
PPS signal in slave IDU has drift Chcek 1588 configuration or port
IEEE 1588 PTP PPS Unlock
problems status
PWE3: Local TDM Down channel The Ethernet port relevant local E1 Check and solve Ethernet port
<...> in uplink is alarmed problems
PWE3: Remote TDM Down channel The Ethernet port relevant remote Check and solve Ethernet port
<...> E1 in uplink is alarmed problems
PWE3: Local PSN Down channel The Ethernet port relevant local E1 Check and solve Ethernet port
<...> in downlink is alarmed problems
PWE3: Remote PSN Down channel The Ethernet port relevant remote Check and solve Ethernet port
<...> E1 in downlink is alarmed problems
a.
E1 LOS IDU E1 - G.704 Internal side Fail
a.
E1 LOS Comminc EOC (E1/Stm1) Data Link
Fan Temperature
IDU <...> Link Loss For- Check LAN status (in local and re-
Link Loss Forwarding in indicated port
warding mote unit)
IDU Board Trib. <...> Loss of Signal in E1 (Inversion a. of the E1 enabled without sign./E1 disa-
Signal Loss a LOS) bled with sign.
IDU BRANCH-<...> Modulator not working/low quality or no IDU loop: if alarm is still active
Modulator Fail input substitute IDU
Local IDU Alarm Synthesis Alarms in local IDU Check local IDU status
a. LOS: LOS inversion OFF - LOS is ON when E1 is enabled with no signal entering
LOS inversion ON - LOS is ON when E1 is enabled with no signal entering and when E1
is disabled with signal entering.
Fan Temperature
Node NB <...> MS AIS MSAIS in NBUS frame payload Substitute the IDU
Examples:
1. Node composed by a minimum of 2 and maximum of 8 elements interconnected only by TDM nodal
BUS
4. Node composed by 8 elements interconnected by Ethernet nodal Bus and 2 elements interconnected
by TDM nodal bus
5. Node composed by 8 elements interconnected by TDM nodal bus and 2 elements interconnected by
Ethernet nodal bus.
Only these five configurations are correct. Any mistake causes following alarms:
PRBS is not receiving the expected pat- Check radio link/no loop active/re-
IDU PRBS Fail
tern mote PRBS off
Warning: Radio group alarms are relevant to the WHOLE RADIO LINK, not relevant to a specific module
only.
In this group are present alarms coming from PSU failure or from:
• Tx direction - none
• Rx direction - alarms in previous module (IDU-ODU cable, ODU) or external failure (bad propagation
or remote alarmed or no remote).
Observation
If Cable Open and Cable Short alarms are active at the same time, it means that the IDU is connected to
a weak battery that is not able to give enough voltage and enough current (also Power Supply alarm is
active).
RT Problem Solution
BRANCH <...> Rx IF Out No Rx IF from the ODU ODU in failure -> replace ODU
BRANCH <...> XPIC Fail A polarization in a XPIC link is down Check radio branches alarms
a. Attenuation in Tx, performed by operator and/or by ATPC, doesn’t affect Tx Power alarm.
In this group are present alarms coming from ODU failure or from:
IDU Stm1 <...> Ms Ais AIS in input MSOH Check equipment line side
IDU Stm1 <...> Ms Rdi RDI in input MSOH Check equipment line side
IDU Sets Free Running Equipment in Free running status Check the selected source input
IDU Sets Holdover Equipment in Holdover status Check the selected source input
IDU Sets <...> LTI Alarm LTI: LOS of timing input (no sync source) Check the selected source
• TDM traffic: an internal PRBS generator van be used to transmit a signal that, by means of IF/RF
loops, can be measured (presence and quality)
• Ethernet traffic: two points in the same VLAN can generate packets (CCM messages) one towards
the other. If the MEPs (Maintenance End Point) are situated one in local unit and the other in remote
unit, the Ethernet transmission (ports, setting and radio link) can be tested.
37.7.1 PRBS
The result of a PRBS test where the PRBS generator receives back the same signal is transmitting (by
means of a loop), is to have the PRBS alarm off (named Sync Loss Alarm in PRBS window).
Pay attention that the alarm off (test ok) during the test
and the test off situation (test not active) have the same
colour (grey) in Synch Loss Alarm box.
Fig.247
In the same domain (NAME and level), in the same VLAN, MEPs can send each other CCM. In order to test
a VLAN between local and remote, two MEPs (one in local unit and the other in the remote one) are nec-
essary to:
• create MEP in local and in the remote unit in the same VLAN (MEPs names must be different)
CCM direction
• Port 1, 2, 3, 4
• Radio port
Fig.248
37.8 LOOPS
- IF loop (ETH not squelched) -> E1 streams + Ethernet signal are looped
3. RF loop - Tx RF signal is looped back towards IDU just before antenna flange
- IF loop (ETH not squelched) -> E1 streams + Ethernet signal are looped
• In case of 1+1 link, the branch under investigation must be forced active (Tx and Rx) by means of
the Radio Switch commands
- without test signal - if alarms of the branch disappear, circuits are OK.
If RF loop gives positive results on both branches, IDU, cables and ODUs are OK (the local station is OK)
and eventual problems are given by propagation or in other side.
Present alarms:
In order to understand why quality alarms are present, RxPwr performance window must be used (in NMS,
WebLCT, SCT).
Local status
Rx levels are low.... and before? From RxPWR table it is possible to see that in the
last 15min record Rx level is <-80dBm but in previous records Rx levelwas higher.
From the situation the reason of quality problem is rain (...f>10Ghz).
If the two alarms are present during a high Rx level period (Rx level >-50dBm) the
quality fall should be caused by interference.Investigate about.
If the problem suggests rain or other weather related fading condition and
it matches the prevailing weather conditions, do not perform any further
action until the situation gets better.
Fig.249
This problem is revealed by low Rx level (how much lower depends on the severity of tropospheric phe-
nomena) and consequent low quality in Rx signal, in both directions of the link.
Rain, multipath fading, rain drop depolarization and diffraction cause Reduced capacity notification alarm,
Rx Power low, Rx Quality warning, Rx quality alarm, Telemetry fail.
• F>10 GHz the fading is given by rain (for F>30 GHz rain is a serious problem)
When propagation problems occur, the link performance will be restored as the weather gets back to nor-
mal and if problems persist (Rx level remain different from normal) the reason must be searched in wrong
antenna disalignment (probably caused by strong wind or snow/ice).
Radio link affected by interference has quality problems in one direction only (possible alarms are Rx Qual-
ity warning, Rx Quality alarm, Telemetry fail increasing the interference severity). Rx level in the interfered
site is not reduced by interference.
When these symptoms occur check if new radio links have been installed in close areas (higher the fre-
quency, smaller the search radius).
In any case interference can be confirmed by a spectrum analyser through a multi-angle investigation per-
formed at antenna side.
38.1 GENERAL
• NMS5–UX Network Management. It is used for the remote control of an entire network consisted of
different SIAE equipment including radio equipment.
For details refer to relevant documentation. SCT/LCT documentation is available as help on–line.
38.2 WEBLCT
Equipment can be locally controlled by an embedded Web Server, the WEB LCT, and an http browser run-
ning on PC.
It is also available a software named SCT that can manage sub networks of SIAE Network Elements.
The hardware platform used by SCT is based on Personal Computer with at least the following character-
istics:
The operator can check the status the equipment through an "Alarm Display Panel" that is automatically
updated by the system.
Alarm records are stored by the equipment in an history log together with all information which could be
of interest for the user, among which:
• alarm description
The operator can access the history log using different filters.
Equipment Configuration
The configuration parameters the operator can update from the WebLCT are:
• Channel bandwidth
• ACM profiles
• RF channel
• ATPC enable/disable
• ATPC Rx thresholds
• RTPC
• Synchronisation parameters
• Alarm enable
• Alarm severity
Equipment Maintenance
The main maintenance parameters that the operator can update from the WebLCT are:
• transmitter enable/disable
• carrier only
• PRBS
The following figure shows the loops that can be set from the WEBLCT, for any IDU configuration.
5 Line loops can be done for E1, STM-1 and Ethernet interfaces. Internal loops can be done for E1 and
STM-1 interfaces.
IDU ODU
Fig.250 - Loop
Software management
A new firmware or a new WEBLCT release can be downloaded from the WEBLCT itself. Actual software re-
lease is reported to the operator.
Performance management
G828, Rx Power, Tx Power and ACM counters are calculated both on radio side and line side
All counters are available on 15 minutes basis and daily, the WEBLCT collects 16 blocks of 15 minutes coun-
ters showing in this way the history of 4 hours.
The user can Start and Stop the Performance Monitoring function.
The user can define a threshold for each counter, when the threshold is crossed an alarm is set by the
equipment, the performance alarm severity can be set by the operator.
Fig.251 reports all the Termination points for the performance monitoring supported by ALplus2.
G828 Radio 1
G828 - 2 Mbit/s Rx&Tx
radio side Power Radio 1
ODU1
G828 - B1 STM-1
G.829 B2 & M1 STM-1 IDU
Line side
Rx&Tx
G828 - 2 Mbit/s ODU2 Power Radio 2
line side
G828 Radio 2
In addition to what shown in the figure above, the following performance monitoring features are available:
• RMON for Ethernet port statistics, both on tributary and radio side
• ACM performance monitoring counters
The WEBLCT Administrator creates and manages a set of user accounts, the security information (Pass-
word and User profile) is used for identification, authentication purpose.
Two operator levels are enabled depending on the profile assigned to the operator:
39.1 GENERAL
• 1RU 1+1
• 1RU 2+0
All the units consist of plug-in modules as LIM/RIM/Controller that can individually be replaced.
Module part number, hardware layout and equipment composition are subject to change without notice.
Every version is identified by a specific part number shown on a label (see Fig.254) attached on IDU, top
left side. Important power supply informations are also written.
2 A AL equipment
3 I Indoor installation
The IDU consists of LIM/RIM/CONTROLLER modules. Each module is identified through internal label indi-
cating the relevant P/N.
- LIM
- RIM
- CONTROLLER.
1 2 3 ON 48V
SPEED
PoE
ACT FAIL
LINK
+
1 2 3 ON 48V
SPEED
PoE
ACT FAIL
LINK
+
REM TEST
LCT RS232 USER IN/OUT MNGT/1 MNGT/2 CH1 CH2 2Mb/s
-
40.1 GENERAL
The ALCplus2 IDU is available in many versions depending on he kind and the number of user connections
and facilities. The versions are listed in the following chapter and are offered in two different configuration:
• 1RU 1+0
• 1RU 1+1.
• All of them consist of a single unit.
• Unit part number, hardware layout and equipment composition are subject to change without no-
tice.
Every version is identified by a specific part number shown on a label (seeFig.254) attached on IDU, top
left side. Important power supply informations are also written.
2
M 3.15A
250VAC 48VDC
MNGT LAN 3 LAN 4 NURG URG
1 LCT
SW
+
2 2
M 3.15A
250VAC
MNGT 48VDC
LAN 3 LAN 4 NURG URG
1 LCT 1 2 1
SW
+
2
M 3.15A
250VAC 48VDC
MNGT LAN 3 LAN 4 NURG URG
1 LCT
SW
+
GREEN LINK LAN 1 LAN 3 Trib. A SD USER IN/OUT TEST ON -
2 2
M 3.15A
250VAC
MNGT 48VDC
LAN 3 LAN 4 NURG URG
1 LCT 1 2 1
SW
+
GREEN LINK LAN 1 LAN 3 Trib. A SD USER IN/OUT TEST ON -
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16 Trib. 17-24 Trib. 25-32
1 2
2
ON M 3.15A 48V
MNGT LAN 3 LAN 4 250V
NURG URG
1 LCT
SW
-
+
GREEN LINK LAN 1 LAN 3 Trib. A SD USER IN/OUT TEST ON
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16 Trib. 17-24 Trib. 25-32
1 2 2
2
ON M 3.15A
MNGT 48V
LAN 3 LAN 4 NURG URG 250V
1 LCT 1 2 1
SW
-
+
GREEN LINK LAN 1 LAN 3 Trib. A SD USER IN/OUT TEST ON
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16
1 2 1 2
2
M 3.15A
ON 250VAC 48VDC
MNGT NBUS
LAN 3 LAN 4 NURG URG
1 LCT
SW
+
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16
1 2 1 2
2 2
M 3.15A
ON 250VAC
MNGT NBUS 48VDC
LAN 3 LAN 4 NURG URG
1 LCT 1 2 1
SW
+
41.1 GENERAL
The ALCplus2e IDU is available in many versions depending on he kind and the number of user connections
and facilities.
The versions are listed in the following chapter and are offered in two different configuration:
• 1RU 1+0
• 1RU 1+1.
• Unit part number, hardware layout and equipment composition are subject to change without no-
tice.
Every version is identified by a specific part number shown on a label (seeFig.254) attached on IDU, top
left side. Important power supply informations are also written.
EPP ALCplus2e 1+0 4GE 34xE1 2xSTM1 EPP GAI0188 See Fig.264
ALCplus2e 1+0 4GE 18xE1 2xSTM1 NODAL EPP GAI0187 See Fig.265
ALCplus2e 2+0 or 1+0 XPIC 4GE 34xE1 2xSTM1 GAI0171 See Fig.267
EPP ALCplus2e 1+0 4GE 34E1 2xSTM1 EPP GAI0211 See Fig.264
EPP ALCplus2e 1+1 4GE 34E1 2xSTM1 EPP GAI0207 See Fig.267
Hw
PWE3 1+0 EPP ALCplus2e 1+0 4GE 18E1 PWE3 GAI0198 See Fig.269
ready
Hw
PWE3 2+0/1+1 EPP ALCplus2e 2+0/1+1 4GE 18E1 EPP PWE3 GAI0199 See Fig.269
ready
Hw
PWE3 2+0 EPP ALFCplus2e 2+0 XPIC 4GE 18E1 EPP PWE3 GAI0200 See Fig.269
ready
Hw
STM1 bulk
PWE3 1+0 EPP ALCplus2e 1+0 4GE 34E1 2xSTM1 EPP PWE3 GAI0201 See Fig.264
transmission
ready
Hw
STM1 bulk ALCplus2e 2+0/1+1 4GE 34E1 2xSTM1 EPP
PWE3 2+0/1+1 EPP GAI0202 See Fig.264
transmission PWE3
ready
Hw
STM1 bulk ALCplus2E 2+0 XPIC 4GE 34E1 2xSTM1 EPP
PWE3 2+0 EPP GAI0203 See Fig.264
transmission PWE3
ready
2 M 3.15A
250V 48V
MNGT LAN 3 LAN 4 NURG URG
1
LCT
R SW
+
GREEN LINK LAN 1 LAN 3 Trib. A USER IN/OUT TEST ON -
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16 Trib. 17-24 Trib. 25-32
1 2
2
ON M 3.15A 48V
MNGT LAN 3 LAN 4 250V
NURG URG
1
LCT
R SW
+
GREEN LINK LAN 1 LAN 3 Trib. A USER IN/OUT TEST ON -
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16
1 2 1 2
2 M 3.15A
ON 250V 48V
MNGT NBUS
LAN 3 LAN 4 NURG URG
1
LCT
R SW
+
GREEN LINK LAN 1 LAN 3 Trib. A USER IN/OUT TEST ON -
2
2 M 3.15A
250V
MNGT 1 2 48V
LAN 3 LAN 4 NURG URG
1 1
LCT
R SW
+
GREEN LINK LAN 1 LAN 3 Trib. A USER IN/OUT TEST ON -
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16 Trib. 17-24 Trib. 25-32
1 2 2
2
ON M 3.15A 48V
MNGT LAN 3 LAN 4 1 2 250V
NURG URG
1 1
LCT
R SW
+
YELLOW SPEED LAN 2 LAN 4 STM1 Trib. B Trib. 1-8 Trib. 9-16
1 2 1 2
2
2 M 3.15A
ON 250V
MNGT NBUS 48V
LAN 3 LAN 4 1 2 NURG URG
1 1
LCT
R SW
+
2
2
M 3.15A 48V
MNGT LAN 3 LAN 4 1 2 250V
NURG URG
1 1
LCT
R SW
-
+
42.1 GENERAL
The ODU consists of a mechanical structure that houses all the transceiver circuitry. In 1+1 HSB version
the connection to the antenna is performed through a passive hybrid.
Both transceiver and hybrid are offered in different versions depending on the operating bands, the anten-
na configuration etc...
A label (see Fig.270) attached on the ODU structure shows the most significant parameters as go/return
frequency value, subband, operating band and part number.
Part number identifies the ODU type. ODU description in the following tables shows frequency, go-return,
channel and capacity if specified.
For example:
Part number, hardware layout and equipment composition are subject to change without notice.
43 LIST OF FIGURES
Fig.8 - ALCplus2 1+1 and ALCplus2e E1 2+0/1+1 and ALCplus2e 2E1 XPIC 2+0.................... 30
Fig.21 - N+0................................................................................................................. 32
Fig.32 - ALCplus2 with 16E1 expansion, STM1, NBUS, 1+0 and 1+1 version, block diagram .... 75
Fig.33 - ALCplus2 with 2E1, 1+0 and 1+1 version, block diagram ........................................ 76
Fig.34 - ALCplus2 with 16E1, 1+0 and 1+1 version, block diagram ...................................... 76
Fig.60 - Final 1+1 assembly with AS, ASN or ASNK ODU .................................................. 120
Fig.76 - Possible positions of the support with ODU fast locking mechanism ........................ 154
Fig.78 - Installation onto the pole of the supporting plate ................................................. 156
Fig.79 - Position of the ODU body depending on the polarisation for 1+0. For 1+1 the polarisation
is always vertical: handle at the left side. ........................................................................ 157
Fig.80 - ODU body reference tooth ................................................................................ 158
Fig.89 - Position of the ODU body depending on the polarisation for 1+0. For 1+1 the polarisation
is always vertical: handle at the left side. ........................................................................ 171
Fig.101 -Position of the ODU handle depending on the polarisation for 1+0. For 1+1 the polarisation
is always horizontal. Handle at the right side.................................................................... 185
Fig.102 - Support system for ODU housing and reference tooth in evidence ........................ 186
Fig.104 - ODU housing final position for vertical polarization ............................................. 188
Fig.105 - ODU housing final position for horizontal polarization .......................................... 188
Fig.107 - Polarization disk fixing (only for 13GHz and 15 GHz)........................................... 190
Fig.117 - ODU housing final position for both polarization ................................................. 203
Fig.118 - Antenna aiming ............................................................................................. 204
Fig.124 - Assembled structure (DP antenna, OMT, mounting system) ................................. 214
Fig.131 - Position of the ODU handle depending on the polarisation for 1+0. For 1+1 the polarisa-
tion is always horizontal. Handle at the right side. ............................................................ 224
Fig.132 - 1+0 support.................................................................................................. 225
Fig.133 - ODU housing final position for both polarization ................................................. 226
Fig.137 - Polarization disk fixing (only for 13 GHz and 15 GHz).......................................... 230
Fig.148 - 1+1 ASN support kit (60-114) code V60100-01 ................................................. 250
Fig.159 - Local Lan-1 port to remote Lan-1 port connection .............................................. 270
Fig.177 - 3 ports to3 ports connections with segregated Tagged and Untagged traffic ........... 280
Tab.5 - Ethernet optical interfaces characteristics, SFP and LLC connectors ............................35
Tab.8 - Guaranteed Ethernet Latency (ms) for ALplus2/ALCplus2/ALCplus2e (Ethernet only) ....37
Tab.14 ..........................................................................................................................91
Tab.21 - MNGT/1 and MNGT/2 100BaseT connector pin-out for 10/100BaseT Ethernet connection
(RJ45) .........................................................................................................................137
Tab.22 - CH2 connector pin-out for 64 kbit/s channel - V.11 interface (RJ45) ....................... 137
For more information, refer to the section relevant to the technical support on the Internet site of the com-
pany manufacturing the product.