Академический Документы
Профессиональный Документы
Культура Документы
User manual
MN.00356.E - 003
The information contained in this handbook is subject to change without notice.
Property of Siae Microelettronica. All rights reserved according to the law and according to the international
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 7
Section 2.
DESCRIPTIONS AND SPECIFICATION 13
MN.00356.E - 003 1
5.6.1 SINGLE ODU ..........................................................................................20
5.6.2 Dual ODUs and SP antenna ......................................................................20
5.6.3 Dual ODUs, 2 hybrid and DP antenna.........................................................21
5.6.4 Dual ODUs and DP antenna ......................................................................21
5.7 RADIO FUNCTIONALITIES ..................................................................................22
5.7.1 ACM ......................................................................................................23
5.7.2 RF band/High Power versions ...................................................................24
5.8 ETHERNET FUNCTIONALITIES ............................................................................24
5.8.1 Ingress port rate limiting (Storm control) ...................................................25
5.8.2 Ingress VLAN manipulation ......................................................................25
5.8.3 Service Instance mapping ........................................................................25
5.8.4 Classification criteria ...............................................................................26
5.8.5 Ingress Filter Policing ..............................................................................26
5.8.6 Queues and Congestion avoidance methods ...............................................27
5.8.7 Scheduling .............................................................................................27
5.8.8 Egress Shaping.......................................................................................28
5.8.9 Egress Manipulation ................................................................................28
5.9 SECURITY........................................................................................................28
5.10 MANAGEMENT ..................................................................................................29
5.11 LICENSE KEY ...................................................................................................29
Section 3.
INSTALLATION 39
2 MN.00356.E - 003
7.12.1 M12 connector........................................................................................53
7.12.2 RJ45 connector.......................................................................................58
7.13 ACCESSORIES FOR INSTALLATION .....................................................................59
7.13.1 Installation procedure of optical junction ....................................................62
7.13.2 Installation procedure of Rosenberger outdoor enclosure..............................62
Section 4.
LINE-UP 65
MN.00356.E - 003 3
11.9 OPTIMIZING ANTENNA ALIGNMENT WITH RX MEASUREMENT ................................82
Section 5.
MAINTENANCE 99
13 ALARMS ...................................................................................................................99
13.1 GENERAL.........................................................................................................99
13.2 ALARMS SYSTEM ..............................................................................................99
13.2.1 LED status ........................................................................................... 100
13.2.2 Alarm group ......................................................................................... 100
4 MN.00356.E - 003
14.3.5 Radio link affected by fading................................................................... 106
14.3.6 Radio link affected by interference .......................................................... 106
Section 6.
PROGRAMMING AND SUPERVISION 107
Section 7.
COMPOSITION 111
Section 8.
EQUIPMENT CHARACTERISTICS 113
17 INTRODUCTION .....................................................................................................113
17.1 GENERALS ..................................................................................................... 113
17.2 THROUGHPUT ................................................................................................ 114
17.3 ACM SHIFTING THRESHOLDS ........................................................................... 114
MN.00356.E - 003 5
19 ALFOplus2 18 GHZ CHARACTERISTICS...................................................................127
19.1 FOREWORD ................................................................................................... 127
19.2 AVAILABLE FREQUENCIES ............................................................................... 127
19.2.1 Transmitter characteristics ..................................................................... 130
19.2.2 Receiver characteristics ......................................................................... 131
19.3 RADIO FLANGE............................................................................................... 132
19.4 POWER SUPPLY AND CONSUMPTION ................................................................. 132
Section 9.
LISTS AND SERVICES 147
24 ASSISTANCE SERVICE............................................................................................153
6 MN.00356.E - 003
Section 1.
USER GUIDE
1 DECLARATION OF CONFORMITY
SIAE MICROELETTRONICA
Via Buonarroti, 21 - Cologno (MI) - Italy
DECLARES
THAT THE PRODUCT
complies with the essential requirements of article 3 of the R&TTE Directive (1999/05/EC)
and therefore is marked:
The equipment makes use of non-harmonized frequency bands. Following the requirements
of the R&TTE Directive (article 12) and the relevant decision of the EC, in term of classifica-
tion of Radio Equipment and Telecommunications Terminal Equipment and associated iden-
tifiers, the transmitting equipment shall carry the 'class 2' identifier:
MN.00356.E - 003 7
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 resuscitation at once and to call a doctor immediately. suggested procedure
for mouth to mouth resuscitation 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
8 MN.00356.E - 003
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.00356.E - 003 9
Fig.1 - Components electrostatic charge sensitive indication
In order to prevent the units from being damaged while handling, it is advisable to wear an elasticised 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).
10 MN.00356.E - 003
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.00356.E - 003 11
3 PURPOSE AND STRUCTURE OF THE MANUAL
The purpose of this manual consists in providing for the user information which permit to operate and
maintain the ALFOplus radio equipment.
Warning: This manual does not include information relevant to the SCT/WebLCT management program
windows 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 describes a general overview of the typical applications and in particular of the whole radio equipment.
Section 3 – Installation
The mechanical installation procedures are herein set down as well as the user electrical connections.
12 MN.00356.E - 003
Section 2.
DESCRIPTIONS AND
SPECIFICATION
4 LIST OF ACRONYMS
- ETH Ethernet
- FEC Forward Error Correction
- NE Network Element
MN.00356.E - 003 13
- QoS Quality of Service
14 MN.00356.E - 003
5 SYSTEM PRESENTATION
5.1 GENERAL
This document contains the description of features and capability of ALFOplus2 equipment.
ALFOplus2 (see Fig.5) is a Full Outdoor microwave radio that houses, within a unique unit, two complete
TX/RX radio channels (RF Multi-core definition) to double the radio capacity and includes a complete Carrier
Ethernet features set. With 4096QAM Modulators, Ethernet Header compression, MIMO ready architecture
and 2x112MHz canalization capability, ALFOplus2 set the new standard in point to point Microwave sys-
tems.
The ALFOplus2 must be used in RAL areas (Restricted Access Location) where an equipotent bonding has
been applied. The ODU unit has a supplementary specific connector for a permanent connection to ground-
ing point intended to be installed by technical staff only.
Fig.5 - ALFOplus2
5.2 CHARACTERISTICS
This document contains the description of features and capability of ALFOplus2 equipment.
Dual Carrier ALFOplus2 is the first SIAE MICROELETTRONICA point to point microwave device capable of
providing, in a unique solution, highest modulation schemes and software defined architecture in a highly
integrated design.
ALFOplus2 flexibility makes it suitable perfectly to all the last generation network requirements fitting per-
fectly in Macrocell Backhaul, C-RAN CPRI transport, Macro-site Aggregations scenarios.
MN.00356.E - 003 15
5.3 APPLICATIONS
ALFOplus2 is the ideal solution in urban environments for all carrier-class applications in which the typical
requirements are Ethernet connections:
ALFOplus2 doesn’t need any indoor unit and the power supply can be provided directly by POE through the
data cable or through a dedicated auxiliary port.
• 2xGbE Electrical ports (1Gbps line rate): LAN3 and LAN4 (with PoE)
• 2xGbE Optical interfaces (1Gbps or 2.5Gbps line rate): LAN1 and LAN2.
Interconnection ports are present for communication between two ALFOplus2 when 2+2/4+0 configura-
tions are implemented.
Auxiliary connectors are in place for Direct Power supply feeder, Local Access and RSSI indication.
In case of protected configurations one traffic port is used as signaling interconnection interface.
The increased number of application segments demands for a spread of microwave technologies in order
to address each of the segments in an effective and efficient way.
This scenario brings to a higher complexity in microwave portfolio challenging for the consistency of the
overall network solution and streamlined roadmap.
16 MN.00356.E - 003
SIAE MICROELETTRONICA answer is based on the adoption Unified Product Architecture, a common Ether-
net hardware and software platform through all new generation products based on two main building
blocks:
• Ethernet Core unit based on powerful switching gear featuring 46Gbps switch fabric capacity, high
performance dual-core CPU and embedded IEEE1588v2 processor for advanced synchronization ca-
pability.
• SM-OS software, based on carrier-grade field proven highly interoperable protocol stack provides
complete MPLS services set and compliancy to CE2.0.
ALFOplus2 has been developed with this concept in mind: Unified Hardware and Software platform archi-
tecture
ALFOplus2 mechanical structure is made up by a main body and three possible additional antenna-interface
modules, lodged in the reserved bay (see Fig.7).
The antenna-interface module is specialized in accordance with the required application (see Fig.8):
• OMT module: it contains an OMT element that combines the two antenna ports of the main body in
a unique antenna port for H/V integrated operations (Antenna Flange is circular)
• HYB module: it contains a HYB element that combines the two antenna ports of the main body to a
unique antenna port for frequency diversity operations (Antenna Flange is circular)
• PASSTHROUGHT module: it exposes both antenna ports (Antenna Flanges are rectangular).
MN.00356.E - 003 17
5.5.1 Single ALFOplus2
Single ALFOplus2 RF-Dual core solution allows the following configurations (See Tab.2):
• 2+0 CP (Co-polar)
Interface Circular
Single waveguide Dual waveguide
Radio module waveguide
configurations
Integrated Integrated Not integrated External
OMT
Dual flange
Hybrid X X
OMT X
Dual flange X
Hybrid
OMT X
Dual flange X
Hybrid
Two ALFOplus2 RF-Dual core solutions allows the following configurations (see Tab.3 and Tab.4):
• 2+2 CP Protected (HSTBY or FD)
• 4+0 CP unprotected
• 4+0 AP unprotected
Tab.3 - Dual ALFOplus2 in 2+0 configurations (purpose, interface module, used antenna)
Dual ALFOplus2
Antenna type
2+0 operations
Interface
Circular Dual
module Single waveguide
Radio waveguide waveguide
configurations
Integrated Integrated Not integrated External
OMT
2+2 CP
HSBY or protected SW 2 ports
Hybrid X
18 MN.00356.E - 003
Dual ALFOplus2
Antenna type
2+0 operations
Interface
Circular Dual
module Single waveguide
Radio waveguide waveguide
configurations
Integrated Integrated Not integrated External
2+2 AP OMT
HSBY or protected SW
2 ports X
Hybrid
Hybrid
OMT
2+2 CP
protected FD 2 ports
Hybrid X
2+2 AP OMT
protected FD
2 ports X
Hybrid
Hybrid
Tab.4 - Dual ALFOplus2 in 4+0 configurations (purpose, interface modules, used antenna)
Dual units
Antenna type
4+0 operations
Interface
Circular Dual
module Single waveguide
Radio waveguide waveguide
configurations
Integrated Integrated Not integrated External
Hybrid
OMT
4+0 CP
unprotected 2 ports
Hybrid X
4+0 AP OMT
unprotected SW
2 ports X
Hybrid
Hybrid
MN.00356.E - 003 19
5.6 ANTENNAS AND EXTERNAL BRANCHING
The previous Link configuration can be pointed out depending antenna and eventual external branching.
The following configuration can be obtained by a single polarization antenna: 1+0, 2+0 CP.
The following configuration can be obtained with a double polarization antenna: 2+0 AP, 2+0 XPIC.
See Fig.8.
H 2+0 XPIC
H 2+0, AP
H H
2+0 CP or 1+0
The following configurations can be obtained by a single polarization antenna, integrated or not, as in Fig.9:
2+2 CP SW/HSBY prot, 2+2 CP FD prot, 4+0 CP.
HYB
HYB
HYB
20 MN.00356.E - 003
5.6.3 Dual ODUs, 2 hybrid and DP antenna
The following configurations can be obtained by a DP antenna, not integrated, and 2 hybrids as in Fig.10:
2+2 AP SW/HSBY prot, 2+2 XPIC SW/HSBY prot, 2+2 XPIC FD prot, 4+0 XPIC.
H
HYB
HYB
V
The following configurations can be obtained by a not integrated DP antenna as in Fig.11: 2+2 AP FD prot,
4+0 AP.
MN.00356.E - 003 21
H
HYB
HYB
V
• ATPC
• link ID
22 MN.00356.E - 003
• InBand/OutOfBand management
5.7.1 ACM
SIAE MICROELETTRONICA implements MSE based Adaptive Coding and Modulation in all channel band-
widths.
Multiple ACM profiles are available for automatic changes in accordance with the link conditions and select-
ed parameters (highest modulation, lowest modulation, masks, power mode etc.). ACM together with QoS
fits perfectly with modern networks requirements in order to ensure the high priority traffic to be never
dropped even in the worst conditions.
ACM includes modulation schemes starting from 4QAM to 4096QAM. Additional sets of ACM profile are in-
cluded differentiating between two different FEC rate codes maximizing throughput, system gain and link
availability with the same constellation type, just changing on-fly the ratio between payload bits and pro-
tection bits in the FEC ratios. This unique set of profiles allows achieve –at the same time– higher capacity
in good propagation conditions and really higher signal strength in tough propagation conditions.
ACM feature is available in all the configurations (1+0/1+1/2+0/4+0 and XPIC). Note that ACM works in-
dependently for uplink and downlink and it is able to protect against fading up to 100dB per second.
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 can be configured via software.
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 the worst channel in the worst
condition (low Rx S/N), the radio link is working at the minimum throughput, defined at Lower Mod-
ulation: the lowest modulation profile that ACM can employ.
The Automatic Transmission Power Control (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 Low Level threshold due to the increase of the hop atten-
uation, a microprocessor (μP) sends back to the local terminal a control to increase the transmitted power.
A good set of the thresholds is to put the ATPC Low Level threshold higher than the downshift threshold of
the highest modulation scheme of the ACM; this way, the ATPC start to work before than the downshift.
The behaviour of the system is to try to increase the PTx and so the System Gain, before than being forced
to reduce capacity due to modulation downgrade.
Resuming, the correct setting of the thresholds is when the two windows, the ATPC one and the ACM one,
are not overlapped.
MN.00356.E - 003 23
5.7.2 RF band/High Power versions
ALFOplus2 is available in several RF band with various Tx/Rx spacing and two Tx Power profiles, standard
and High Power.
• Standard power:
- 18 GHz
- 23 GHz
- 25 GHz
- 28 GHz
- 38 GHz
- 42 GHz
• High power:
- 6/7/8 GHz
- 11 GHz
- 13/15 GHz.
ALFOplus2 is compliant with MEF9 for service functionality and MEF14 for service performance and can be
used to implement standardized Ethernet services such as E-Line, E-LAN and E-Tree providing quality of
service (QoS), scalability and reliability. Each service could be created in transparent mode or in virtual
mode sharing radio link resources between different services managing VLAN 802.1q tags.
• Configurable MTU
• MAC learning/aging
24 MN.00356.E - 003
• MAB: MW adaptive bandwidth by OAM message support (feature jointly developed with Cisco)
Storm control limits the maximum amount of traffic that can be accepted at the input of the switch LAN
ports: it’s possible to apply, for each LAN port, a rate limiter (PIRL set as active for each relevant LAN in-
terface) to a combination of incoming traffic types (independently from the VLAN ID and priority level).
These traffic types are:
• BROADCAST Frames
• MULTICAST
Once the mapping has been performed, all the incoming traffic has been associated to a specific EVC. This
means that the VLAN tag associated to the Carrier Ethernet service is appended to each frame and it is
used across the entire Carrier Ethernet network for delivering the frame towards the destination. This tag
is called S-tag.
S- tag is removed before the frame is delivered across the UNI to the external equipment on the other end
of the connection.
Before appending the VLAN tag associated to the service, the VLAN manipulation function allows modifying
the format of the incoming frames.
The VID can be rewritten on the basis of the following criteria:
• S-tag remapping
• C-tag remapping
Mapping functionality allows associating to all incoming traffic a specific VLAN ID identifying the Ethernet
Virtual Connection (EVC).
• ingress user port: all traffic from the port is mapped on the same unique EVC;
• user VLAN ID: all traffic associated to one or more CE VLAN ID is mapped on the same EVC.
Available services:
• service multiplexing
• all-to-one bundling.
MN.00356.E - 003 25
5.8.4 Classification criteria
QoS refers to the ability of a network device to provide improved services to selected network traffic over
various underlying technologies, including Ethernet and wireless LANs.
In particular, QoS feature provides an improved and more predictable network services, as follows (see
Fig.12):
• ingress port
ALFOPLUS2 allows limiting the ingress traffic rate on the basis of:
• UNI Port Based (Bandwidth profile per UNI port): a different profile is defined for each LAN port
(VLAN ID and priority are not considered in this case by the rate limiting algorithm)
• EVC Based (Bandwidth Profile per C_VID): a different profile is defined for different VLANs (priority
is not considered in this case by the rate limiting algorithm).
• COS Based (Bandwidth Profile per CoS): a different profile is defined for each priority queue from
0 to 7 (i.e. internal switch priority). In this case, the Customer and Service VLAN IDs are not con-
sidered by the rate limiting algorithm and independently from the enabled QoS management
• C-TAG + C-PCP Based: (Bandwidth Profile per C_VID + CoS): a different profile is defined for dif-
ferent couples VLAN+priority queue
• S-TAG + S-PCP based: (Bandwidth Profile per S_VID+S-PCP): a different profile is defined for dif-
ferent couples Service VLANs – S.
26 MN.00356.E - 003
• S-TAG + C-TAG: (Bandwidth Profiles per S_VID+CoS): a different profile is defined for different
couples S_VID+priority queue (up to 64 different cases can be managed).
Up to 64 Ingress Filtering Policy resources can be defined and each bandwidth profile defined on the basis
either of LAN port, VLAN or VLAN+priority consumes 1 of such resources.
In order to define the bandwidth profile, the following parameters must be configured:
• CIR (Committed Information Rate): it is the admitted ingress rate (“green” colored), with values
between 0 Kbit/s and 1 Gbit/s.
• CBS (Committed Burst Rate): it is the maximum size of the token bucket of the green packets, with
values between 0 byte and 256 Kbyte.
• EIR (Excess Information Rate): it is maximum ingress rate eventually admitted (“yellow” colored),
with values between 0Kbit/s and 1Gbit/s.
• EBS (Excess Burst Rate): it is the maximum size of the token bucket of the yellow packets, with
values between 0 byte and 256 Kbyte.
When the queues are full there is a congestion situation, this means that the resources are not enough to
serve all the packets and some of them must be dropped.
The choice of the dropping policy has different effects on the network. In case of congestion, the TCP/IP
protocol reduces the transmitting windows and therefore the amount of traffic transmitted. The TCP/IP pro-
tocol increases the transmitting window very slowly to allow the network to solve the congestion issues.
Congestion Avoidance is a protocol that permits to discard some frames before congestion occurs.
Supported mechanisms are:
• Tail Drop.
5.8.7 Scheduling
Once the priority is assigned, the traffic in the queues is then emptied by means of either Strict Priority or
Weight Round Robin algorithms:
• WRR - the available bandwidth is shared among the different priorities with configurable weights
It is also possible to configure at the same time some queues as Strict Priority and the remaining as WRR.
ALFOPLUS2 ethernet switch supports 8 queues per port with configurable depth.
MN.00356.E - 003 27
Fig.13
Egress Shaping is used to control rate of traffic sent on network interface. traffic lower than or equal to the
specified rate is sent, traffic that exceeds the rate is dropped or delayed. Rate limiting is performed by
policing (discarding excess packets), queuing (delaying packets in transit) or congestion control (manipu-
lating the protocol’s congestion mechanism).
The rate limiting which allows shaping traffic inserted inside the network is also implemented per egress
port or per queue.
The egress manipulation function allows modifying the format of the outcoming frames.
The egress VLAN can be removed on the basis of the following criteria:
• Port Based
5.9 SECURITY
• SNMP V3
28 MN.00356.E - 003
5.10 MANAGEMENT
ALFOplus2 unit can be monitored via GE interfaces and via serial connector.
Unit management level is in line with all the other SIAE MICROELETTRONICA products:
• configurations via SNMP v.1/v.2/v.3 datagram
• WebLCT usage
Through WEBLCT a feature key can be sent to the unit and the relevant functionalities can be unlocked.
MN.00356.E - 003 29
6 TECHNICAL SPECIFICATION
In Section 8. DESCRIPTIONS AND SPECIFICATION more details regarding the available ALFOplus2 version
depending on RF frequency.
ALFOplus2 implements an adaptive modulation algorithm to improve the system gain when the quality of
the received signal become insufficient to guarantee an error free link.
Adaptive modulation guarantees error free and hitless unidirectional downshifts with fading speed up to 30
dB/s. Ethernet frames aren’t lost in case of upshift and downshift events.
The ACM shifting thresholds are shown in Tab.20, Tab.21, Tab.22 and Tab.23.
The line interfaces (LAN1 and LAN2 GE with PoE facilities, LAN3 and LAN4 optical up to 2.5Gbps) are con-
nected to an embedded Ethernet switch. Ethernet traffic is forwarded to the radio interface through 2x 2.5
Gbps port, one for radio branch (BB, IF and RF unit). Network synchronism can be acquired and provided
by each Ethernet switch port.
30 MN.00356.E - 003
Main DC/DC,
Power
Aux DC/DC
Radio1
LAN4
Split/combine
I/Q
Protecon
(Packet Process) TX/RX
MD-Ch1
TXmod
Framer
HC
channel1
POE
QoS
Frag
LAN3 RXdem IF
OL1
module
Ant.
Radio2
LAN2 RF-unit2
Split/combine
I/Q
Protecon
TXmod
Framer
MD-Ch2
TX/RX
HC
Frag
QoS
LAN1 channel2
RXdem IF
OL2
µP
Tab.5 - Latency
Channel size (MHz) 4QAM 16QAM 32QAM 64QAM 128QAM 256QAM 512QAM 1K QAM 2K QAM 4K QAM
14 1.023 0.776 0.680 0.641 0.608 0.614 0.603 0.577 0.575 0.567
20 0.747 0.570 0.528 0.487 0.472 0.451 0.437 0.438 0.437 0.433
28 0.507 0.382 0.348 0.329 0.326 0.323 0.310 0.309 0.299 0.297
30 0.493 0.407 0.352 0.338 0.322 0.310 0.307 0.299 0.302 0.295
40 0.388 0.292 0.263 0.265 0.247 0.240 0.238 0.233 0.238 0.233
50 0.416 0.344 0.336 0.318 0.309 0.306 0.306 0.299 0.299 0.297
MN.00356.E - 003 31
56 0.384 0.315 0.297 0.283 0.278 0.276 0.272 0.272 0.269 0.266
60 0.378 0.297 0.289 0.281 0.271 0.269 0.263 0.262 0.262 0.259
80 0.282 0.246 0.234 0.224 0.221 0.215 0.213 0.211 0.210 0.208
112 0.217 0.185 0.181 0.177 0.172 0.169 0.169 0.168 0.167 0.166
Channel size (MHz) 4QAM 16QAM 32QAM 64QAM 128QAM 256QAM 512QAM 1K QAM 2K QAM 4K QAM
14 1.052 0.751 0.718 0.672 0.637 0.612 0.583 0.593 0.573 0.573
20 0.778 0.577 0.550 0.497 0.471 0.453 0.451 0.450 0.440 0.427
28 0.548 0.373 0.359 0.347 0.325 0.322 0.309 0.312 0.310 0.306
30 0.542 0.381 0.372 0.336 0.322 0.312 0.309 0.302 0.301 0.297
40 0.401 0.293 0.282 0.260 0.251 0.246 0.235 0.237 0.237 0.231
50 0.436 0.352 0.334 0.328 0.312 0.309 0.302 0.301 0.298 0.300
56 0.387 0.311 0.299 0.289 0.282 0.275 0.272 0.268 0.268 0.268
60 0.386 0.303 0.293 0.283 0.272 0.268 0.267 0.264 0.261 0.257
80 0.289 0.241 0.235 0.225 0.219 0.218 0.213 0.213 0.212 0.211
112 0.225 0.185 0.182 0.176 0.175 0.171 0.169 0.169 0.168 0.167
Channel size (MHz) 4QAM 16QAM 32QAM 64QAM 128QAM 256QAM 512QAM 1K QAM 2K QAM 4K QAM
14 1.158 0.801 0.703 0.653 0.658 0.610 0.613 0.602 0.587 0.580
20 0.859 0.586 0.555 0.528 0.471 0.481 0.464 0.453 0.446 0.436
28 0.521 0.392 0.385 0.359 0.337 0.323 0.316 0.319 0.317 0.308
30 0.526 0.392 0.380 0.349 0.326 0.324 0.320 0.315 0.309 0.306
40 0.406 0.307 0.285 0.263 0.260 0.254 0.248 0.240 0.235 0.240
50 0.425 0.356 0.340 0.334 0.325 0.311 0.309 0.305 0.304 0.300
56 0.394 0.319 0.306 0.295 0.284 0.279 0.277 0.272 0.274 0.271
60 0.387 0.314 0.293 0.285 0.278 0.273 0.267 0.267 0.265 0.262
80 0.310 0.252 0.240 0.228 0.222 0.219 0.218 0.216 0.216 0.214
112 0.231 0.196 0.186 0.181 0.176 0.174 0.172 0.170 0.170 0.169
Channel size (MHz) 4QAM 16QAM 32QAM 64QAM 128QAM 256QAM 512QAM 1K QAM 2K QAM 4K QAM
14 1.188 0.818 0.735 0.695 0.643 0.634 0.617 0.602 0.606 0.601
20 0.834 0.629 0.579 0.517 0.498 0.483 0.469 0.463 0.456 0.450
28 0.623 0.419 0.400 0.372 0.344 0.349 0.334 0.317 0.329 0.315
30 0.598 0.445 0.387 0.358 0.353 0.332 0.333 0.317 0.313 0.315
40 0.458 0.330 0.304 0.273 0.267 0.264 0.249 0.246 0.245 0.246
50 0.462 0.372 0.352 0.339 0.329 0.318 0.319 0.313 0.307 0.308
56 0.427 0.337 0.314 0.302 0.294 0.284 0.287 0.282 0.281 0.276
60 0.387 0.323 0.309 0.288 0.286 0.280 0.278 0.272 0.272 0.266
32 MN.00356.E - 003
80 0.326 0.255 0.247 0.233 0.231 0.226 0.222 0.219 0.219 0.218
112 0.241 0.205 0.190 0.187 0.182 0.179 0.176 0.175 0.174 0.173
Channel size (MHz) 4QAM 16QAM 32QAM 64QAM 128QAM 256QAM 512QAM 1K QAM 2K QAM 4K QAM
14 1.522 0.982 0.897 0.771 0.728 0.711 0.666 0.687 0.643 0.639
20 1.061 0.732 0.659 0.593 0.574 0.523 0.508 0.510 0.490 0.485
28 0.718 0.480 0.445 0.416 0.384 0.380 0.353 0.350 0.347 0.336
30 0.727 0.478 0.430 0.398 0.371 0.360 0.360 0.348 0.343 0.338
40 0.572 0.375 0.345 0.318 0.289 0.282 0.278 0.268 0.270 0.259
50 0.548 0.410 0.379 0.371 0.352 0.344 0.331 0.325 0.326 0.323
56 0.503 0.358 0.352 0.321 0.314 0.304 0.297 0.298 0.291 0.289
60 0.464 0.354 0.343 0.311 0.301 0.293 0.291 0.286 0.287 0.283
80 0.356 0.285 0.269 0.249 0.248 0.237 0.235 0.231 0.232 0.228
112 0.271 0.225 0.207 0.201 0.192 0.188 0.186 0.184 0.182 0.182
Channel size (MHz) 4QAM 16QAM 32QAM 64QAM 128QAM 256QAM 512QAM 1K QAM 2K QAM 4K QAM
14 1.584 0.998 0.910 0.815 0.766 0.715 0.703 0.675 0.682 0.666
20 1.119 0.746 0.684 0.607 0.597 0.559 0.532 0.522 0.516 0.501
28 0.773 0.523 0.455 0.440 0.401 0.393 0.364 0.355 0.360 0.352
30 0.763 0.536 0.474 0.429 0.404 0.386 0.372 0.360 0.356 0.344
40 0.560 0.395 0.346 0.325 0.301 0.295 0.286 0.279 0.276 0.269
50 0.570 0.429 0.398 0.370 0.360 0.351 0.343 0.339 0.333 0.330
56 0.481 0.382 0.353 0.332 0.319 0.314 0.310 0.302 0.299 0.296
60 0.479 0.376 0.339 0.325 0.311 0.304 0.298 0.294 0.293 0.285
80 0.380 0.298 0.279 0.260 0.250 0.246 0.241 0.238 0.236 0.233
112 0.286 0.228 0.215 0.203 0.198 0.193 0.191 0.188 0.187 0.186
Channel size (MHz) 4QAM 16QAM 32QAM 64QAM 128QAM 256QAM 512QAM 1K QAM 2K QAM 4K QAM
14 1.650 1.071 0.962 0.856 0.794 0.734 0.709 0.710 0.686 0.677
20 1.253 0.808 0.724 0.658 0.575 0.570 0.563 0.532 0.520 0.519
28 0.816 0.559 0.486 0.449 0.420 0.402 0.384 0.365 0.370 0.535
30 0.827 0.544 0.482 0.439 0.398 0.394 0.375 0.370 0.366 0.352
40 0.593 0.397 0.379 0.333 0.315 0.305 0.288 0.285 0.279 0.273
50 0.587 0.437 0.412 0.380 0.369 0.355 0.346 0.342 0.338 0.336
56 0.505 0.391 0.373 0.339 0.330 0.318 0.314 0.310 0.305 0.301
60 0.519 0.380 0.347 0.333 0.322 0.310 0.306 0.299 0.297 0.292
80 0.397 0.298 0.282 0.265 0.260 0.252 0.248 0.243 0.241 0.237
112 0.301 0.237 0.222 0.212 0.202 0.199 0.196 0.193 0.191 0.190
MN.00356.E - 003 33
One way delay (msec) Physical modes (4000 bytes)
Channel size (MHz) 4QAM 16QAM 32QAM 64QAM 128QAM 256QAM 512QAM 1K QAM 2K QAM 4K QAM
14 2.789 1.609 1.394 1.239 1.101 1.021 0.960 0.922 0.904 0.869
20 2.102 1.206 1.038 0.909 0.831 0.770 0.728 0.712 0.691 0.667
28 1.435 0.844 0.723 0.633 0.568 0.552 0.518 0.487 0.476 0.461
30 1.350 0.818 0.701 0.614 0.575 0.527 0.504 0.478 0.470 0.462
40 0.995 0.618 0.533 0.472 0.431 0.413 0.390 0.376 0.376 0.356
50 0.908 0.618 0.547 0.495 0.469 0.448 0.435 0.419 0.416 0.405
56 0.822 0.537 0.486 0.442 0.422 0.403 0.385 0.375 0.373 0.362
60 0.806 0.521 0.485 0.435 0.407 0.385 0.377 0.363 0.363 0.352
80 0.605 0.419 0.376 0.347 0.330 0.313 0.307 0.297 0.296 0.288
112 0.449 0.327 0.295 0.273 0.258 0.250 0.243 0.237 0.234 0.230
Channel size (MHz) 4QAM 16QAM 32QAM 64QAM 128QAM 256QAM 512QAM 1K QAM 2K QAM 4K QAM
14 4.968 2.721 2.284 1.901 1.676 1.535 1.443 1.376 1.317 1.235
20 3.653 2.039 1.698 1.434 1.295 1.162 1.100 1.035 1.001 0.957
28 2.460 1.359 1.153 1.005 0.872 0.815 0.765 0.710 0.704 0.662
30 2.401 1.367 1.137 0.988 0.857 0.793 0.750 0.700 0.688 0.664
40 1.775 1.015 0.873 0.747 0.673 0.614 0.581 0.549 0.534 0.510
50 1.549 0.936 0.819 0.724 0.656 0.618 0.588 0.559 0.550 0.533
56 1.344 0.827 0.733 0.638 0.585 0.549 0.525 0.504 0.496 0.480
60 1.304 0.802 0.709 0.616 0.569 0.533 0.508 0.490 0.483 0.463
80 0.995 0.642 0.557 0.497 0.456 0.431 0.412 0.399 0.393 0.380
112 0.729 0.484 0.429 0.386 0.357 0.339 0.329 0.317 0.312 0.304
34 MN.00356.E - 003
Gigabit 2.5 Gbps
Connector type LC
6.3 LOOPS
To check the correct operation a set of local and remote loops are made available. The commands are for-
warded by the WebLCT program. The loop is a manual operation that can be activated for a timeout period
specified by operator (0-172800sec.). The available loop facilities are:
• loopback on Ethernet LAN PORT (1)
• I/Q loop: activation command of I/Q loop operates on both branch; RF transmission is squelched
(3).
Main DC/DC,
Power Aux DC/DC
POE
LAN4
Eth. Switch 2 I/Q TX/RX
(Packet Process)
Protection
Split/combine
MD-Ch1
TXmod
Framer
channel1
Frag
QoS
POE
HC
LAN3 RXdem IF
OL1
module
TRX
Ant.
3
LAN2
Radio2
RF-unit2
I/Q
TX/RX
Protection
MD-Ch2
TXmod
Frag
QoS
Framer
channel2
HC
LAN1
RXdem IF
OL2
1
µP
MN.00356.E - 003 35
6.4 POWER SUPPLY AND CABLE
Power supply can be provided at the 48V port and at the electrical Ethernet ports (in case of PoE).
11 GHz HP 90 80 72
RF 15 GHz 70 60 54
a. An adapter is required
36 MN.00356.E - 003
GND
Fig.16
MN.00356.E - 003 37
6.6 SURGE AND LIGHTNING PROTECTION
- Environmental conditions and environmental tests ETSI EN 300 019 Class 4.1
38 MN.00356.E - 003
Section 3.
INSTALLATION
7 INSTALLATION OF ALFOPLUS2
The installation, maintenance or removal of antenna systems requires qualified, experienced personnel.
SIAE installation instructions have been written for such personnel.
Antenna system should be inspected once a year by qualified personnel to verify proper installation, main-
tenance and condition of equipment.
SIAE disclaims any liability or responsibility for the results of improper or unsafe installation practices.
ALFOplus2 equipment is a full-outdoor IP Ethernet radio link system operating in various band frequency
RF bands coverage up to 42 GHz for transport capacity up to 2036 Mbit/s, designed to establish LAN-LAN
connections.
For the details related to the actual used frequency band refer to the label on the equipment.
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.
MN.00356.E - 003 39
7.2 GENERAL
- use of filters on the power supply input circuits against noise propagating on the power supply
wires
• during the installation phase
The installation phases of the whole system are described in the following paragraphs and it must be done
only by service person suitably trained.
Remember that the whole radio link can work only if ODUs chosen for local and remote side have equal
sub-band and different SSB (H and L).
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.
During the final installation, protect the ALFOplus2 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 48V connector M12 5Pin from the ODU
or disconnecting the LAN PoE cable.
The typical magneto thermal switch has characteristics at least 48 Vdc @12A with overcurrent relay class
“C” or “K” tripping curve.
Seal the M12 connector when it isn’t used, in order to avoid the removal of the cover without tools.
40 MN.00356.E - 003
7.5 GROUNDING CONNECTION
Fig.17 and annexed legend show how to perform the grounding connections.
The ODU must be connected to ground with the available grounding bolt M08303 and eyelet terminal
M06614, making reference to details of Fig.16.
Indoor 7
4 3 4
ODU
unit
1
Ethernet
6 2
equipment
(IDU)
(+) (-)
5
Station Local
ground ground
Chassis
ground rack
Legend
1. Ethernet Switch chassis grounding point. The cross section area of the cable used must be 4 sq.
mm.
2. ODU (ALFOplus2) grounding M6 bolt copper faston type. The cross section area of the cable used
must be 16 sq. mm
5. 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.
6. Grounding cords connected to a real earth internal of station. The cross section area of the cable
must be 16 sq. mm
The kit IDC00072F can be used for both IF cable and Ethernet cable.
MN.00356.E - 003 41
Tab.9 - Mounting Instructions
Description
42 MN.00356.E - 003
7.6 REQUIRED TOOLS FOR MOUNTING (NOT SUPPLIED)
• ODU assembling: the proper antenna interface module is installed over the ALFOplus2
- Dual output flanges - installation of the supporting plate and of the ODU over it
• ODU grounding.
Various version of antenna interface modules are available (each of them with proper screws included).
For every frequency three versions are available: OMT, Balanced Hybrid and Dual Flange (polarization can
be set).
The antenna interface adapter is shown in Fig.18 and the ALFOplus2 cavity in Fig.19.
The antenna interface module assembling procedure is the following (see Fig.18 and Fig.19):
• insert the antenna interface adapter in the proper cavity of the ALFOplus2
• move the module slightly to match the correct positioning of the protruding ODU gasket in the
adapter peripheral groove
• insert the screws in the following order: 1 and 2 (and check again the correct positioning) and tight-
en them, 3 and 4 and tighten and at last 5, 6, 7 and 8. Tighten and check all of them.
MN.00356.E - 003 43
Groove for
ODU gasket
Fig.18 – Antenna adapter module (left: external side - right: internal side)
Protruding
ODU gasket
44 MN.00356.E - 003
7.9 ODU INSTALLATION – SINGLE RECTANGULAR OUTPUT FLANGE
In this case the standard mounting flange (Z21823) is used (see Fig.20).
Use centring ring and relevant screws and the 4 M10 bolts to install the mounting flange on the ALFOplus2.
M10 screws
Z21823 flange
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:
• 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 as in Fig.21.
• 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 M10 bolts (3). The sliding sur-
faces 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 the four M10 bolts (3) on the antenna back
plate: each bolt should be tightened to have the square head out of the hole of about 13-14mm
(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 in the proper track on the ODU flange
• position the ODU vertically near the four bolts on the antenna flange and align the ODU to match
the polarization of the antenna feeder.
• 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
MN.00356.E - 003 45
• 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).
Only for OMT ALFOplus2 the mounting flange is the Z22011 with closed slot in upper position according to
the position of the pole (see Fig.22).
Use centring ring and relevant screws and the 4 M10 bolts to install the mounting flange on the ALFOplus2.
46 MN.00356.E - 003
Z22011 flange
M10 screws
Install the antenna using the antenna installation guide (specific for each antenna) inside the antenna box
provided by antenna producer. Keep attention to the position of the antenna feeder depending on request-
ed setting.
After the antenna is installed onto the pole, the ODU must be installed:
• 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 as in Fig.23.
• 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 M10 bolts (3). The sliding sur-
faces 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 the three M10 bolts (3) on the antenna back
plate: each bolt should be tightened to have the square head out of the hole of about 13-14mm
(the thickness of hook (4), use 15mm spanner). The last bolt will be inserted in the closed slot.
• 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 vertically near the three bolts on the antenna flange and align the ODU to match
the antenna feeder.
• 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 slots of the Standard Lock cross between the 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)
• now insert the last bolt in the closed bolt (the upper) and tighten it.
MN.00356.E - 003 47
Fig.23 – Installation of OMT flange ALFOplus2 over the antenna
• install the antisliding strip 1 and the plastic blocks 2 onto the pole
• hang the tooth of the supporting plate 3 onto the plastic blocks: two possibilities depending if the
rectangular opening must be on the left (see Fig.24) or on the right (see in Fig.26 and Fig.27) re-
spect the pole.
• secure the plate to the pole with the two fixing bracket for 60–114 mm pole (see Fig.24). Bolts and
nuts are available on the supporting plate kit. Use the four screws 5 and items 6, 7, 8, 9. Tightening
torque must be 32 Nm.
• install the ALFOplus2 (see Fig.25) on the supporting plate using the six bolts M10 (shorter than the
four screws 5) through the six mounting holes (see Fig.26). When all the bolts are positioned, tight-
en them (use 15mm spanner, torque=46mm)
• from the two RF flanges of ALFOplus2 two wave guides are necessary to connect them to the an-
tennas as in Fig.27.
48 MN.00356.E - 003
Tooth
ALFOplus2
mounting holes
MN.00356.E - 003 49
ALFOplus2
mounting holes
50 MN.00356.E - 003
Fig.26 - Installation of dual flanges ALFOplus2
MN.00356.E - 003 51
Fig.27 - Dual flanges ALFOplus2 with waveguides connected to the two RF flanges
52 MN.00356.E - 003
7.12 USER CONNECTORS
ALFOplus2 provides 2xM12 5pin connector and 4 Ethernet ports as shown in Fig.36.
• 2 LAN SFP (1 Gbps or 2.5 Gbps) Optic Rosenberger connectors: LAN1 and LAN2
• 2 LAN RJ45 (1 Gbps) Electric Rosenberger connectors, with surge arrester: LAN3 and LAN4.
Warning: If cable is not inserted, close the port with relevant cap to ensure waterproofing.
There are 2 separated M12 5 pin straight circular connector for different applications:
• 48V port
• MNGT port.
• F03594 cable for laboratory use only (see Fig.28) dedicated for 48V port only
• F03616 maintenance cable (remove it after commissioning pointing) (see Fig.29) dedicated for
MNGT port only
• F03622 console cable (remove it after use) (see Fig.30) dedicated for 48V port only
48V port
• Used as a port for the secondary power supply source 48Vdc, when the power over Ethernet injector
through the data LAN cable is not available or it is possible use with both power source (PoE and
48V ports).
• If necessary, console port pins are present (see Tab.10). Use cables F03594 or F03622 and a hy-
perterminal session (params: 115000, 8, N, 1) to access and login.
Pinout Description
3 Rx_Console
4 Tx_Console
5 GND_Console
Shield Ground
MNGT port
Pinout in Tab.11.
• It is a dedicated port used for local management only (fast Ethernet 100BaseT) also called On-
SMNGT (On-Site Management)
MN.00356.E - 003 53
• The interface has lightning protection.
Pinout Description
1 TXP
2 RXP
3 TXN
4 RXN
5 Vpointing (+)
54 MN.00356.E - 003
Fig.28 - F03594 cable for lab use only
MN.00356.E - 003 55
Fig.29 - F03616 maintenance cable (to remove after commission pointing)
56 MN.00356.E - 003
Fig.30 - F03622 console cable (remove it after use)
MN.00356.E - 003 57
7.12.2 RJ45 connector
The electrical RJ45 connection to ALFOplus2 is guaranteed only with coded connector. Part to be assembled
(see Tab.12).
Please be aware that modifying Ethernet cables improperly may cause loss of network connectivity. Please
follow colours of wiring.
58 MN.00356.E - 003
Assignment T568A T568B
Pin
1000Base-T Colour wire Colour wire
MN.00356.E - 003 59
Tab.14 - Accessories for installation
60 MN.00356.E - 003
SIAE code Descriptions View
MN.00356.E - 003 61
7.13.1 Installation procedure of optical junction
Components
Fig.34 - Components
The kit P20101 Rosenberger outdoor enclosure is an universal outdoor connector used for LC fiber and RJ45
LAN cable. Follow the graphical passages in Fig.35 for fiber assembly, the same procedure can be used for
RJ45 LAN outdoor cable.
62 MN.00356.E - 003
Fig.35 - P20101 assembly procedure
MN.00356.E - 003 63
64 MN.00356.E - 003
Section 4.
LINE-UP
8 LINE-UP OF ALFOPLUS2
8.1 GENERAL
• connection procedure
• equipment configuration (through PC software)
All the parameters set on local unit must be set on remote one also. Local and remote units must be in the
same subnet.
This is a list of procedures for a fast and “basic” line-up to be performed after a correct installation.
8.2 SWITCH ON
• antenna presence - check the connection between ODU output flange and antenna.
MN.00356.E - 003 65
8.3 ALARM LED CHECK
On the front panel of ODU unit there are two LEDs dedicated to show unit alarms. Further information about
alarms can be found onto the Section 5. MAINTENANCE.
ALFOplus2 line-up can be done via MNGT (Gi 0/4) port using WEBLCT or Hyperterminal and via console
port using Hyperterminal only. LAN1 and LAN2 are disabled by default.
The factory default IP addresses are 172.20.254.14/16 ODU L and 172.20.255.15/16 ODU H.
The max number of users connected to the same radio at the same time is:
• CLI sessions = 7
• WebLCT users = 4.
To antenna/wave guide
See also connection to paragraph 8.4.1 WEBLCT via MNGT port (cable F03616).
See also connection to paragraph 8.4.2 CLI session via MNGT or console port.
66 MN.00356.E - 003
• write unit default IP address
• set host address: the radio IP address, Port number= 23, connection using: TCP/IP (Winsock)
• open Hyperterminal and, in the window Connection Description, write the name/icon for the con-
nection
• set serial COM speed=115200bps, data bits=8, parity=none, stop bit=1 and flow control=none
• click on OK button
MN.00356.E - 003 67
• type show nvram to know the actual IP address
68 MN.00356.E - 003
9 BRIDGE MODE (WEBLCT AND CLI)
V ia W E B LC T
V ia C LI
Command Purpose
SM-OS# c t; bridge-mode customer #Enable Customer Bridge (802.1q)
SM-OS# c t; bridge-mode provider-core #Enable Provider Bridge (802.1ad)
SM-OS# c t; bridge-mode provider-edge # Enable Provider Edge Bridge
MN.00356.E - 003 69
10 MANAGEMENT: OUT OF BAND/IN BAND
10.1 GENERAL
• Out of Band (factory default) – Traffic and management use separate ports (This is a simulated Out
of Band: a dedicated VLAN, the VLAN1, is used)
• In Band – Traffic and management use the same ports with management in a defined and specific
VLAN not used by traffic
- Management ports – LAN1, LAN2, LAN3, LAN4 and MNGT (VLAN127 in the example).
LAN1 Gi 0/7
Optical 1/2.5G
LAN2 Gi 0/9
Optical 1/2.5G
MNGT Gi 0/4
Electrical 100M
This is the default configuration but, just in case, it can be created again:
• WEBLCT
- Address
- Agent IP Address
70 MN.00356.E - 003
- Remote Element List
- Restart
• CLI
- MNGT VLAN creation (Vid=1), IP address, Agent IP Address and default gateway.
For the Out of band example, involved ports are: MNGT, LAN2 and TRX. Among them MNGT and LAN2 are
untagged.
• select Static VLANs card and click Add: Static VLAN Configuration window is open
• set VLAN ID, VLAN name, Member Ports (MNGT gi0/4, LAN2 gi0/9, Radio gi0/3), Untagged Ports
(MNGT gi0/4, LAN2 gi0/9) and Ether Type used (0x8100)
In WEBLCT select Base Band menu, DCN and MNGT Port Configuration.
• Set IP Address, Net Mask, Default Gateway and VLAN ID (Default OoB Vid =1)
MN.00356.E - 003 71
10.2.3 Out of band: Setting the Agent IP (WEBLCT)
72 MN.00356.E - 003
Fig.44 - Remote element list
• Equipment menu
• Main - Equipment properties, in General Info
10.2.6 Out of band: IP Address, MNGT VLAN, Agent IP and Default Gate-
way (CLI)
This is the CLI script for the setup of Out of Band Management. Add the script after SM-OS#.
#Customer bridge
ct
bridge-mode customer
#set MTU=2048byte
#set VLAN 1
vlan 1
exit
default ip vlan id 1
MN.00356.E - 003 73
default gateway route 192.168.79.1
exit
end
reload.
For the In Band example, the ports involved are: MNGT, LAN1, LAN2 and TRX. MNGT is untagged.
WEBLCT
• Restart
CLI
MNGT VLAN creation, MNGT (gi0/4) IP address and Agent IP Address, InBand Vid and default gateway.
• Select Static VLANs card and click Add: Static VLAN Configuration window is open
• Set VLAN ID (Vid=127), VLAN name, Member Ports, Untagged Ports (among the previous) and
Ether Type used
• Click Apply and confirm
74 MN.00356.E - 003
Fig.45 - VLAN 127 creation
In WEBLCT select Base Band menu, DCN and MNGT Port Configuration.
• Set IP Address, Net Mask, Default Gateway and mngt VLAN ID (in example Vid =127)
• If MNGT port address and MNGT VLAN have been already set, it’s time to restart the ALFOplus2:
click System Restart and confirm.
MN.00356.E - 003 75
Fig.47 - Agent IP setting
In WebLCT at position:
• Equipment menu
76 MN.00356.E - 003
10.3.6 In band: IP Address, MNGT VLAN, Agent IP and Default Gateway
(CLI)
This is the CLI script for the setup of In Band Management. Add the script after SM-OS#.
#Customer bridge
ct
bridge-mode customer
#Set MTU=2048byte
exit
exit
end
reload.
MN.00356.E - 003 77
11 RADIO LINK LINE-UP
11.1 GENERAL
• radio configurator
• link ID setting
• frequency setting
If the Link configuration present in Current Radio Configuration card is correct, go to next paragraph if not
delete it.
• Proceed as in fig. NEW LINK. In Select Link Type menu select the desired configuration and, in Avail-
able Radio list, the Radio to use (one in case of 1+0, 2 in case of 2+0 XPIC). Push Done.
78 MN.00356.E - 003
Fig.48- New link
- set Bandwidth: 14, 20, 28, 30, 40, 50, 56, 60, 80 or 112 MHz
- set Ref Modul ...that is the used one: 4, 16, 32, 64, 128, 256, 512, 1024, 2048 or 4096QAM
- click Apply and Confirm
• ACM Engine Enabled (modul. Profile varies between lower and upper depending on S/N in Rx)
- set Bandwidth, Reference Modulation, Lower and Upper Profiles (see previous case for details)
In ACM table is listed the Ethernet capacity relevant to the Active Modulation.
MN.00356.E - 003 79
11.4 MODULATION & CAPACITY PARAMETERS
• Modulation profiles 4, 16, 32, 64, 128, 256, 512, 1024, 2048 and 4096QAM
4QAM and 16QAM have the strong version also; the modulation is the
same but the payload in the strong case is lower because of a bigger over-
head (stronger protection code).
• ACM Engine Enabled adaptive modulation (between Lower and Upper profiles):
11.5 LINK ID
• set the value used as Link ID between 1 and 255, 0=parameter not used and not checked
• ...set the same Link ID value on remote unit. In case of Link ID mismatch (the unit receives a signal
with a Link ID different from the expected one) the alarm LinkID is active.
• in Dplx Freq. menu select the desired value (Dplx freq. Is the Tx/Rx spacing) and push Apply and
Confirm
• in Tx Freq. menu select the desired Tx Freq. value in MHz (Local Tx Freq. = Rem Rx Freq.)
80 MN.00356.E - 003
• in field Measurements Resolution select the resolution of Tx and Rx power reading
No manual operations must be active on the radio.
Note: On remote IDU Tx and Rx frequencies are the opposite respect the local.
• in Ptx slide select the value in dBm for the Tx power (30 dB range)
In WEBLCT select Radio menu, Radio Branch, select ODU Powers card:
MN.00356.E - 003 81
• in Tx Power Control select Automatic, ATPC is active
• in Ptx slide set the value in dBm for the Max Tx power (30 dB range)
• in ATPC Regulation set the dynamics of ATPC (from 30dB to 1dB), if max Regulation is required,
flag the ATPC Full Range (up to 30dB of attenuation)
• in ATPC Thresholds on Local PRx set the two thresholds to define the desired Rx power obtained
through remote side Tx power regulation (min.gap=3dB, advised=5dB)
Note: the difference between low ATPC threshold and upper modulation downshift threshold must be bigger
than 10dB.
There is no alarm if Rx Power is out from the range defined by ATPC thresholds.
When the whole radio link is on, antenna alignment can be optimised. Antenna alignment optimization is
performed depending on the Rx signal power at local and remote equipment and evaluating both local and
remote S/N value maximizing them. There are two possibilities to see the Rx signal power level:
• relevant branch 1(A) through a voltmeter connected to MNGT port on the ODU (F03616 cable - see
Fig.29).
In order to get the Rx signal power level via software, connect the PC to ALFOplus2 and start the WebLCT.
Into WebLCT is shown in the top status bar (Rx1A= -value dBm) see Fig.44:
82 MN.00356.E - 003
If you’re using a voltmeter the Rx signal power level is available on the MNGT port of ODU, the measure-
ment can be performed with a proper cable (see Fig.29). Following this last procedure, the voltage you’re
reading with the voltmeter is proportional to Rx power level, refer to Tab.15.
Error [dB] @
Received Signal [dBm] Signal Output [V] Error [dB] @25°C
-33°C ÷ +65°C
-20 3 ±2 ±4
-30 2.5 ±2 ±4
-40 2 ±2 ±4
-50 1.5 ±2 ±4
-60 1 ±2 ±4
-70 0.5 ±2 ±4
-80 0 ±2 ±4
It is the most important item to optimise the antenna alignment, but in a situation of interference Rx level
can be good, BER acceptable but S/N margin low. This means that when Rx fields will decrease then BER
will increase fast. The situation can be easily shown with WebLCT software looking at Signal Quality level.
Into WebLCT Software select:
• Equipment menu
• Maintenance
The best antenna alignment gives the higher Rx signal power level with the higher S/N ratio (see Fig.54).
MN.00356.E - 003 83
12 ETHERNET TRAFFIC CONFIGURATION
12.1 GENERAL
Some examples of traffic port configuration are suggested in the following paragraphs using two ports only,
LAN1 and LAN2 on local and remote unit.
Other ports can be used following the same procedures here shown.
Three main configurations “pipe” are suggested depending on traffic kind and Bridge mode:
• CB for untagged traffic and known C-tagged traffic
Suggested configurations are with In Band management where both the LAN1 and LAN2 ports are used for
traffic and management.
In case of Out of Band management only LAN1 port can be used for traffic and so in the following examples
all the commands referred to LAN2 port (second pipe) have to be avoided.
84 MN.00356.E - 003
12.2 CB EXAMPLE
Units in Customer Bridge mode: the transmitted traffic is untagged and/or known C-tagged.
U ntag g ed traffic
C -tag g ed ≠ Vid10, Vid 20
OK D ropped
Know n C -tag g ed (VID and p) C 10-p2
S -tag g ed traffic
Def VID=101
Def VID=101
DEF p=6
DEF p=6
A A
C 101-p6
A
C 10-p2
B C 10-p2
B
CBP
1 CBP
C 10-p2 1
B
TRX TRX
C 102-p6
CBP
2 C 2
CBP
C CB C 20-p2
C
D CB
C 20-p2
D
C 20-p2
D
Def VID=102
Def VID=102
DEF p=6
DEF p=6
Fig.55 - Configuration for untagged and known C-tagged traffic in Customer Bridge mode
• WEBLCT
• CLI.
• Port Settings.
- MDI/MDIX Auto
MN.00356.E - 003 85
- Bridge Port Type Customer Bridge
• set VLAN ID, VLAN name, Member Ports, Untagged Ports (among the previous) and Ether Type
used, Click Apply and confirm
• now the new VLAN can be used for traffic
86 MN.00356.E - 003
Fig.58 - CB Port setting
This is the script for the setting of traffic configuration described in Fig.55.
SM-OS# c t
SM-OS(config-vlan)# ports gigabitethernet 0/3 gigabitethernet 0/7 untagged gigabitethernet 0/7 name
Vlan101
SM-OS(config-vlan)# exit
SM-OS(config-if)# shutdown; switchport pvid 101; switchport priority default 6; switchport ingress-filter;
mtu 2048; negotiation; no shutdown
SM-OS(config-if)# exit
SM-OS(config)# vlan 10
SM-OS(config-vlan)# exit
SM-OS(config-vlan)# ports gigabitethernet 0/3 gigabitethernet 0/9 untagged gigabitethernet 0/9 name
Vlan102
SM-OS(config-vlan)# exit
SM-OS(config)# interface gigabitethernet 0/9
SM-OS(config-if)# shutdown; switchport pvid 102; switchport priority default 6; switchport ingress-filter;
mtu 2048; negotiation; no shutdown
SM-OS(config-if)# exit
SM-OS(config)# vlan 20
SM-OS(config-vlan)# exit
MN.00356.E - 003 87
SM-OS(config)# interface gigabitethernet 0/3
SM-OS(config-if)# shutdown; switchport ingress-filter; mtu 2048; no negotiation; speed 2500; no shut-
down
SM-OS(config-if)# exit
Units in Provider Core Bridge mode (Provider Bridge 802.1ad): the transmitted traffic is known S-tagged
only.
S 101-p6
S -tag g ed ≠ Vid101, Vid 102
S 101- p6
A S 101- p6
A
S 101-p6 C 10-p2 S 101-p6 C 10-p2
B S 101- p6
A B
PNP 1 PNP
1
S 101-p6 C 10-p2
TRX B
TRX
PNP PNP
2 S 102- p6
C 2
S 102- p6
C PCB
S 102- p6
C
S 102-p6 C 20-p2
PCB
S 102-p6 C 20-p2
D
D S 102-p6 C 20-p2
D
Fig.59 - Configuration for known S-tagged traffic in Provider Core Bridge mode
• WEBLCT
• CLI.
Using the WEBLCT with the units in Provider Core Bridge mode:
• Port Status
88 MN.00356.E - 003
• set the following parameters:
- MDI/MDIX auto
• select Static VLANs card and click Add: Static VLAN Configuration window is open
• set VLAN ID, VLAN name, Member Ports and Ether Type used, Click Apply and confirm
MN.00356.E - 003 89
Fig.62 - PB Port setting
This is the script for the setting of traffic configuration described in Fig.59.
SM-OS# c t
SM-OS(config)# bridge-mode provider-core
SM-OS(config-vlan)# exit
SM-OS(config-if)# exit
SM-OS(config-vlan)# exit
SM-OS(config-if)# shutdown; switchport ingress-filter; mtu 2048; no negotiation; speed 2500; no shut-
down
SM-OS(config-if)# exit
90 MN.00356.E - 003
12.3 PEB EXAMPLE
Units in Provider Edge Bridge mode. The transmitted traffic is untagged and/or unknown C-tagged.
U ntag g ed traffic
OK S -tag g ed traffic D ropped
C
U nk now n C -tag g ed (VID and p) 10 -p2
A A
S 101-p6
C 10-p2
B A C 10-p2
B
CNP 1
1 CNP
S 101-p6 C 10-p2
B
R
R
CNP
S 102-p6 CNP
2 C 2
C PEB
C
PEB
S 102-p6 C 20-p2
C 20-p2 D D C 20-p2
D
Def VID=102 Def VID=102
DEF p=6 DEF p=6
Fig.63 - Configuration for untagged and unknown C-tagged traffic in Provider Edge Bridge mode
This traffic configuration can be set via:
• WEBLCT
• CLI.
See following paragraphs.
Using the WEBLCT with the units in Provider Edge Bridge mode:
• Port Status
• Port Settings.
MN.00356.E - 003 91
- Auto Neg. selected or not
- MDI/MDIX Auto
• select Static VLANs card and click Add: Static VLAN Configuration window is open
• set VLAN ID, VLAN name, Member Ports, Untagged Ports (among the previous) and Ether Type
(0x88A8), Click Apply and confirm
92 MN.00356.E - 003
Fig.66 - PEB Port setting
This is the script for the setting of traffic configuration described in Fig.63.
SM-OS# c t
SM-OS(config-vlan)# ports gigabitethernet 0/3 gigabitethernet 0/7 untagged gigabitethernet 0/7 name
Vlan101
SM-OS(config-vlan)# exit
SM-OS(config)# interface gigabitethernet 0/7
SM-OS(config-if)# exit
SM-OS(config-vlan)# exit
SM-OS(config-if)# exit
SM-OS(config)# interface gigabitethernet 0/3
SM-OS(config-if)# shutdown; switchport ingress-filter; mtu 2048; no negotiation; speed 2500; no shut-
down
SM-OS(config-if)# exit.
MN.00356.E - 003 93
12.4 COMMISSIONING MEASURES FOR ETHERNET TRAFFIC
Verify with the appropriate Ethernet analyser the Ethernet performances of equipment before commission-
ing of the link.
After checking commissioning measures it is mandatory to fill “SIAE commissioning report” and send it to
SIAE database, ready to be checked when necessary.
These reports are very important for SIAE and for the customer because they certify the conformity of SIAE
link.
Firmware can be updated using the software WebLCT Console. There are two different memory benches:
one containing the running firmware and the other the stand-by firmware. This permits to download a new
firmware release to the stand-by bench without cutting the traffic
Use “Bench Switch” to activate the bench in stand-by (SW restart will be performed).
12.5.1 Scope
Scope of this paragraph is to provide a procedure that describes, step by step, how to perform the software
upgrade of ALFOplus2 equipment. Downloading time depends on connection used between PC and
ALFOplus2.
Boot download
1. Unzip files E82xxx XXX.zip in a suitable directory of the PC used to performed the upgrade.
- using WebLCT select Software Info&Maint (see Fig.67) from Equipment Menu and press
Upgrade (see Fig.68)
4. Select the file E82xxx.dwl (boot firmware) from the directory boot_ e82xxx_xxyyzz
6. Start the download and confirm by clicking on the window that pops-up.
7. At the end of the boot firmware download, the equipment Controller will automatically restart. Wait
for the restart to be completed.
94 MN.00356.E - 003
System Version Download
1. Unzip files N50052 XXX.zip in a suitable directory of the PC used to performed the upgrade.
- using WebLCT select Software Info&Maint (see Fig.67) from Equipment Menu and press
Upgrade (see Fig.68)
4. Select the file N50052.dwl (system version) from the directory bin
6. Start the download and confirm by clicking on the window that pops-up
7. At the end of the system version download, to activate the new system version a bench switch is
required: click on Bench switch confirm by clicking on the window that pops-up.
Warning: The bench switch affects Ethernet traffic during device re-configuration.
WebLCT Download
2. In Equipment menu - Software Info&Maint - WebLCT - Upload Manager press Browse and
select the file “N96126_XXYYZZ”
4. After the update it is recommended to clear temporary internet files, cookies and history of the used
browser.
MN.00356.E - 003 95
Fig.68 - Upgrade software
12.6.1 Scope
Backup Configuration
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.
Restore Configuration
Once the spare Controller has been installed or every time the saved configuration is necessary, proceed
as follow:
2. In the field Restore file name write the name of the configuration file you are going to download in
the ODU, complete with the full path of its folder
96 MN.00356.E - 003
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 (see Fig.69).
MN.00356.E - 003 97
98 MN.00356.E - 003
Section 5.
MAINTENANCE
13 ALARMS
13.1 GENERAL
In this document a description of alarms is present, in order to help operators to perform equipment trou-
bleshooting.
• through LEDs
• through WebLCT
For each part of the units, groups of alarms are defined. These alarms can be independent or interdepend-
ent with each other, according to the real causes that generated them.
Alarms are divided into 4 severity levels according to the effects that an alarm might cause to the regular
operation of the unit detecting it. Levels are prioritised as follows:
• minor (yellow): failure neither urgent, high residual functionality, not urgent alarm
Critical and Major alarms indicate impossibility of executing a service, hence the faulty units needs to be
serviced. Minor level represents the not urgent alarms which do not prejudice service continuity. Warning
level indicates malfunctions that might be locally removed without having to replace the unit. Alarm sever-
ity can be modified or masked in “Alarm severity configuration” via WebLCT by the operator.
MN.00356.E - 003 99
13.2.1 LED status
Radio B Radio A
• Red on internal failure (Unit fail, Modulator fail, PTX fail, VCO fail)
• Red blinking (both LEDs) external alarm (LAN LOS, no distinction if Radio A or B).
In order to obtain LEDs status stability, a minute is necessary to pass the boot.
Alarms are divided in groups to refer to a particular functionality and are characterized by programmable
severity. Alarms, with group and a short description, are listed into Tab.16.
In the following you can find a class list and the item they describe:
COMMON Equip Manual Operation At least one manual operation active Warning
ETH LAN Eth Lan Phy Link Loss Loss of Ethernet signal Major
Radio Rx Power Low Alarm Rx power below the fixed threshold Major
RADIO
Capacity is reduced because the working
Radio Reduced Capacity Warning
profile is nit the upper one
Radio Invalid Frequency Alarm Set Wrong frequency on radio link Major
Radio Equip Ber Sync Loss Alarm BER/Sync loss on received radio signal Warning
Unit Unit Not Responding Alarm No response from the unit Major
14.1 GENERAL
In the following pages are listed all the procedures necessary to ALFOplus2 maintenance.
When corrective maintenance is necessary, a troubleshooting procedure helps the operator to identify the
unit to replace.
14.2 MAINTENANCE
Periodical checks serve to detect correct radio performance without the presence of any alarm condition.
Corrective maintenance takes place as soon as one or more alarm conditions are in existence. Operation
sequence to be carried out is shown in “Troubleshooting” paragraph.
Routine maintenance consists in a series of checks aiming to verify the correct operating mode.
• Rx field (value measured must comply with that resulting from hop calculation)
How these operations are carried out is specified in “Line–up” section or, more widely, in ALFOplus2 man-
ual.
Troubleshooting purpose is to locate the faulty unit and replace it with a spare after having verified that
the cause of faulty is not external to the equipment.
14.3 TROUBLESHOOTING
• 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.
• 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
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 file
NMS5LX/NMS5UX
• status of alarms
• configuration file
• loops and manual operation.
Warning: refer to proper software manuals for information relevant to these items.
• Rx - This line starts in RF flange and arrive at the LAN interfaces: when a situation of more alarms
is occurring, the most significative alarm is the higher in Rx direction, all the others after are prob-
ably caused by this.
Examples
1. Radio 1A RT VCO Fail alarm in the ODU causes alarms also in IF circuits (Rx dir.) ->Demodulator
Fail alarm
2. An antenna input < -80dBm can cause the sequence of alarms: Rx Power Low -> Demodulator Fail
alarm -> Rx Quality warning and Rx Quality alarm…all of them can be caused by a Tx failure on
remote unit.
Present alarms:
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 over its surface).
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).
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.
15.1 GENERAL
ALFOplus2 is programmed and supervised using CLI, WebLCT or NMS5UX/LX. These software are fully de-
scribed in separated manuals.
15.2 SUPERVISION
The description of management plane is differentiated on the base of the possible product interconnections
and applications.
In ALFOplus2 the ports that can participate to the management plane are the following:
• MGMT: On site management port (OnSMng). FE for local access connection only.
Basically the management plane can be shared with the data plane (In band management) or supported
via dedicated and independent channel (Out of Band). Moreover it could be managed at L2 or L3 level.
In the following the supported schemes are listed, on the base of configuration and management scheme
is intended to be supported independently from the Data Plane configurations (Customer Bridge mode or
Provider Bridge mode).
Warning: Only MNGT and TRX ports are enabled by default. All the other interfaces (LAN1, LAN2, LAN3 and
LAN4) are disabled.
In general the management plane can be configured using CLI (see separated software manual). In par-
ticular, for management purpose, the LAN interfaces can be configured as follow:
• Local Access Only - LAN is dedicated to the management and it allows to reach the local CPU only
• In Band - LAN is configured to transport both management and data: management is differentiated
by dedicated VLan
• Drop Node - LAN is dedicated to the management and it is possible to access to both local CPU and
the rest of the network.
These management configurations are shown in the following paragraphs in examples where only LAN1
and LAN2 are employed but all the ports can be used with the limit of the bitrate allowed by the media
(LAN1 and LAN2 are optical with bitrate 2.5Gbps and LAN3 and LAN4 are electrical with bitrate 1Gbps).
In this configuration the management plane transport is shared with the data plane (see Fig.72). The dif-
ferentiation is obtained by managing different VLANs. A VLAN dedicated to the management shall be de-
fined (VLANmng) and configured by the user.
• Define which ports participate to the VLANmng and the port connectivity scheme to obtain the de-
sired reachability (local only or also remote)
• In particular it shall be possible to dedicate a LAN to the management only (in this case untagged
management frames at this interface shall be supported, see "Drop Node" configuration)
µP µP
data
1 1
VIDMng
TRX TRX
2 2
Switch Switch
MNGT MNGT
mng
Fig.72 - Example of InBand management, LAN1 with local and remote visibility
data
1 1
VIDMng
mng
TRX TRX
2 2
Switch Switch
MNGT MNGT
mng
Fig.73 - In band Management example, LAN2 port is dedicated to the management and accesses
to local CPU only
Restrictions in selection could be present in case of incompatible LAN configurations at physical layer or
data plane (for example, if two LANs are in ELP or LAG the management is InBand).
The MNGT port is dedicated to the management for "On-Site" use only. This access mode is expected to
be used during first installation or replacement cases, for example to configure the system, check system
status, recover NE configurations.
µP µP
1 1
VIDonSMng
TRX TRX
2 VIDMng 2
15.2.4 Address
The unit uses a single IP address associated at the management port of controller and a single "default
gateway".
The “Console access” is available in 48V port through serial port (F03594 or F03622 cable) via Hyperter-
minal (115200bps,n,8,1):
Some Ethernet configurations may require further settings and executed by CLI commands (i.e.: manage-
ment VLAN, bridge mode change, ...).
CLI commands can be sent locally or remotely line by line in a Hyperterminal session.
The script file are an alternative way to perform commands, respect to access the system from local con-
sole connector.
ALFOplus2 allows to execute on microprocessor flash a script previously loaded without command inter-
ruption.
Script procedure:
• start and configure a TFTP server (suggested TFTP32 for Windows or tftpd on Linux/Unix)
• load the script (e.g.: script.txt) to microprocessor non volatile memory via TFTP with command
SM-OS# copy tftp://server_ip/script.txt flash:script.txt
• the script must be in UNIX/OSX textual format (using i.e. “Notepad plus plus”)
• the file name must not contain special characters, including _ or -.
16.1 GENERAL
There are several versions of ALFOplus2, each of them with different hardware characteristics. If one of
these is inserted improperly in local and remote side, radio link doesn’t work.
Following statements:
• the ODU must be assembled with proper antenna adapter module. See Tab.18 for the code relevant
frequency and characteristics.
• you must have 2 ODUs, the first working in the lower selected subband and the second one working
in the correspondent higher subband; e.g. 1L-1H, 2H-2L, etc....
Unit 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 attached on ODU.
Other information such as power consumption, allowed configuration, feature key, system version, part
number P/N and serial number S/N are also written.
Frequency
Antenna adapter module
11 18 23 25 28
17 INTRODUCTION
17.1 GENERALS
In this chapter are listed all the characteristics of ALFOplus2, common to all the versions and relevant the
various frequencies.
• throughput
• quality and SNR
Frequency by frequency:
• frequency range
• Tx characteristics
• power consumption
• RF flange
• Tx power.
Tab.19 - Net Radio Throughput in Mbit/s versus channel bandwidth for ALFOplus2 equipment
(1+0 configuration)
In this paragraph are present the ACM upshift and downshift thresholds depending on the bandwidth.
16SQAM 12.8 17 21
16QAM 14 18.5 23
32QAM 17.6 21 26
64QAM 20.7 24 29
BW=14MHz
128QAM 24.2 27 32
4096QAM
4SQAM 6.9 15
4QAM 8.4 13 19
16SQAM 12.9 17 20.5
16QAM 14 18.5 23
32QAM 17.6 21 26
64QAM 20.7 24 29
BW=28MHz
128QAM 24.4 27 32
1024QAM 34.4 37 40
4SQAM 6.6 15
4QAM 8.4 13 19
32QAM 16.9 21 26
64QAM 20 24 28.3
BW=56MHz
128QAM 23.3 26.3 31.5
1024QAM 33.3 36 39
4SQAM 6.6 -- 15
4QAM 8.4 13 19
64QAM 20 24 28.2
BW=112MHz
128QAM 23.1 26.2 31.2
256QAM 26.4 29.2 34.2
4096QAM 38 40.8
18.1 FOREWORD
• This device has been verified as per FCC 47 CFR part 101 and has been found to meet its relevant
requirements.
• This device complies with part 15 of the FCC Rules. Operation is subject to the following two condi-
tions:
Changes or modifications not expressly approved by the party responsible for compliance could void the
user’s authority to operate the equipment.
The frequency carrier limits are given in Tab.27, Tab.28, Tab.29 and Tab.30.
Tab.25 - Net Radio Throughput in Mbit/s versus channel bandwidth for ALFOplus2 equipment
(1+0 configuration)
FREQUENCY RANGE: 10700 ÷ 11700 MHz - CEPT T/R 12-06 and ITU-R F.387-10-
GO-RETURN: 490 MHz - 180 MHz RF Filter Tuning Range
SUB BAND 1
SUB BAND 2
SUB BAND 3
FREQUENCY RANGE: 10700 ÷ 11700 MHz - CEPT T/R 12-06 and ITU-R F.387-10 - GO-RETURN: 530 MHz
- 180 MHz RF Filter Tuning Range
SUB BAND 1
SUB BAND 2
SUB BAND 3
FREQUENCY RANGE: 10700 ÷ 11700 MHz - FCC CFR Title 47 Part 101
Go-Return: 490 MHz - 180 MHz RF Filter Tuning Range
SUB BAND 1
SUB BAND 2
SUB BAND 3
FREQUENCY RANGE: 10700 ÷ 11700 MHz - FCC CFR Title 47 Part 101
Go-Return: 500 MHz - 30 MHz RF filter tuning range
SUB BAND 1
40 - - - -
80 - - - -
SUB BAND 3
40 - - - -
80 - - - -
4QAMs 29 27
4QAM 29 27
16QAMs 26 24
16QAM 26 24
32QAM 26 24
64QAM 25 23
±2 dB
128QAM 25 23
256QAM 24 22
512QAM 24 22
1024QAM 23 21
2048QAM 23 21
4096QAM 23 21
- Transmit power with ACM Hybrid Mode: the ACM profiles above the
reference modulation transmit in Peak Constant
Mode (i.e. each modulation transmits the output
- Muting attenuation 60 dB
- Typical receiver sensitivities (dBm) 2dB better (lower) than guaranteed receiver
sensitivities
- Maximum input level for BER 10-6 -21dBm for modulations below 64QAM
-22dBm for modulations below 64QAM/128QAM
-23dBm for modulations below 256QAM/512QAM
-24dBm for modulations equal or higher than
1024QAM
- Radio WG flange type UBR 220 (ODU configuration with hybrid and
flange kit)
UBR 220 (ODU configuration Dual Flange and
flange kit)
C 255 (ODU configuration with OMT)
80.0 90.0
19.1 FOREWORD
• ITU-R F.595 and CEPT Rec T/R 12-03 for RF channel arrangement
• EN 300 019 Climatic Characteristics (operation: class 4.1 for ODU; storage: class 1.2; transport:
class 2.3)
- Channel bandwidth 14, 20, 28, 30, 40, 50, 56 and 112 MHz
FREQUENCY RANGE: 17700 ÷ 18140 MHz paired with 19260 - 19700 MHz
Go-return: 1560 MHz - ITU-R F.595 - Annex 7
FCC CFR Title 47 Part 101
The frequency carrier limits are given in Tab.36, Tab.37 and Tab.38.
Tab.36 - 17700 - 19700 MHz band - ITU-R F.595 - Annex 7 - Go-Return 1010 MHz - Frequency
carrier limits
SUB BAND 1
SUB BAND 2
SUB BAND 3
a. The actual channel bandwidth is compliant with a channel spacing of 7, 13.75, 27.5 and 55 MHz re-
spectively.
Tab.37 - 17700 - 18140 MHz paired with 19260 - 19700 MHz band - ITU-R F.595 - Annex 7 -
Go-return 1560 MHz - Frequency carrier limits
FREQUENCY RANGE: 17700 - 18140 MHz paired with 19260 - 19700 MHz - ITU-R F.595 - Annex 7
Go-return: 1560 MHz - 440 MHz RF Filter Tuning Range
SUB BAND 1
a. The actual channel bandwidth is compliant with a channel spacing of 7, 13.75, 27.5 and 55 MHz re-
spectively.
Tab.38 - 17700 - 18140 MHz paired with 19260 - 19700 MHz band - FCC CFR Title 47 Part 101 -
Go-return 1560 MHz - Frequency carrier limits
FREQUENCY RANGE: 17700 - 19700 MHz - FCC CFR Title 47 Part 101
Go-return: 1560 MHz - 440 MHz RF Filter Tuning Range
SUB BAND 1
a. The actual channel bandwidth is compliant with a channel spacing of 7, 13.75, 27.5 and 55 MHz re-
spectively.
- Transmit power with ACM Hybrid Mode: the ACM profiles above the
reference modulation transmit in Peak Constant
Mode (i.e. each modulation transmits the output
power indicated in the table above). Below the
reference modulation the Mean Constant Mode is
followed. RTPC attenuation is applied to Tx power
of lower modulation; higher modulations can
transmit at their maximum power if they do not
overcome the power transmitted at lower
modulation.
4QAMs 23 21
4QAM 23 21
16QAMs 21 19
16QAM 21 19
32QAM 21 19
64QAM 19 17
±2 dB
128QAM 19 17
256QAM 18 16
512QAM 18 16
1024QAM 17 15
2048QAM 17 15
4096QAM 17 15
- Typical receiver sensitivities (dBm) 2dB better (lower) than guaranteed receiver
sensitivities
- Maximum input level for BER 10-6 -21 dBm for modulations below 64QAM
-22 dBm for modulations equal or higher than
64QAM
- Radio WG flange type UBR 220 (ODU configuration with hybrid and
flange kit)
UBR 220 (ODU configuration Dual Flange and
flange kit)
C 165 (ODU configuration with OMT)
60.0 70.0
20.1 FOREWORD
• ITU-R F.637-3 and CEPT Rec T/R 13-02 for RF channel arrangement
• EN 300 019 Climatic Characteristics (operation: class 4.1 for ODU; storage: class 1.2; transport:
class 2.3)
- Channel bandwidth 14, 20, 28, 30, 40, 50, 56 and 112 MHz
3 4096QAM modulation scheme is not available with 14MHz and 20MHz channel bandwidth.
The frequency carrier limits are given in Tab.44, Tab.45, Tab.46 and Tab.47.
Tab.44 - 22000 - 23600 MHz band - ITU-R F.637-3 - Annex 3 and CEPT T/R 13-02 -
Go-Return 1008 MHz - Frequency carrier limits
FREQUENCY RANGE: 22000 - 23600 MHz - GO-RETURN: 1008 MHz - ITU-R F.637-3 - Annex 3 and
CEPT T/R 13-02 - 336 MHz RF Filter Tuning Range
SUB BAND 1
SUB BAND 2
Tab.45 - 21200 - 23600 MHz band - ITU-R F.637-3 - Annex 1 - Go-return 1232 MHz -
Frequency carrier limits
FREQUENCY RANGE: 21200 - 23600 MHz - GO-RETURN: 1232 MHz - ITU-R F.637-3 - Annex 1
SUB BAND 1
SUB BAND 2
SUB BAND 3
Tab.46 - 21200 - 23600 MHz band - ITU-R F.637-3 - Annex 4 - Go-return 1200 MHz -
Frequency carrier limits
FREQUENCY RANGE: 21200 - 23600 MHz - GO-RETURN: 1200 MHz - ITU-R F.637-3 - Annex 4
SUB BAND 1
SUB BAND 2
SUB BAND 3
Tab.47 - 21200 - 23600 MHz band - FCC CFR Title 47 Part 101 - Go-return 1200 MHz - Frequency
carrier limits
FREQUENCY RANGE: 21200 - 23600 MHz - GO-RETURN: 1200 MHz - FCC CFR Title 47 Part 101 -
405.5-400-403.5 MHz RF Filter tuning range
SUB BAND 1
SUB BAND 2
SUB BAND 2
- Transmit power with ACM Hybrid Mode: the ACM profiles above the
reference modulation transmit in Peak Constant
Mode (i.e. each modulation transmits the output
power indicated in the table above). Below the
reference modulation the Mean Constant Mode is
followed. RTPC attenuation is applied to Tx power
of lower modulation; higher modulations can
transmit at their maximum power if they do not
overcome the power transmitted at lower
modulation.
4QAMs 23 21
4QAM 23 21
16QAMs 21 19
16QAM 21 19
32QAM 21 19
64QAM 19 17
±2 dB
128QAM 19 17
256QAM 18 16
512QAM 18 16
1024QAM 17 15
2048QAM 17 15
4096QAM 17 15
- Typical receiver sensitivities (dBm) 2dB better (lower) than guaranteed receiver
sensitivities
- Maximum input level for BER 10-6 -21 dBm for modulations below 64QAM
-22 dBm for modulations equal or higher than
64QAM
- Radio WG flange type UBR 220 (ODU configuration with hybrid and
flange kit)
UBR 220 (ODU configuration Dual Flange and
flange kit)
C 220 (ODU configuration with OMT)
60.0 70.0
21.1 FOREWORD
• ITU-R F.748-3 and CEPT Rec T/R 13-02 for RF channel arrangement
• EN 300 019 Climatic Characteristics (operation: class 4.1 for ODU; storage: class 1.2; transport:
class 2.3)
Tab.53 - 24.5 - 26.5 GHz - Go-Return 1008 MHz - Frequency carrier limits
FREQUENCY RANGE: 24.5 ÷ 26.5 GHz - GO-RETURN: 1008 MHz - 448 MHz RF Filter Tuning Range
SUB BAND 1
SUB BAND 2
- Transmit power with ACM Hybrid Mode: the ACM profiles above the
reference modulation transmit in Peak Constant
Mode (i.e. each modulation transmits the output
power indicated in the table above). Below the
reference modulation the Mean Constant Mode is
followed. RTPC attenuation is applied to Tx power
of lower modulation; higher modulations can
transmit at their maximum power if they do not
overcome the power transmitted at lower
modulation.
4QAMs 22 20
4QAM 22 20
16QAMs 20 18
16QAM 20 18
32QAM 20 18
64QAM 18 16
±2 dB
128QAM 18 16
256QAM 17 15
512QAM 17 15
1024QAM 16 14
2048QAM 16 14
4096QAM 16 14
- Typical receiver sensitivities (dBm) 2dB better (lower) than guaranteed receiver
sensitivities
- Radio WG flange type UBR 220 (ODU configuration with hybrid and
flange kit)
UBR 220 (ODU configuration Dual Flange and
flange kit)
C 255 (ODU configuration with OMT)
60.0 70.0
22 LIST OF FIGURES
Fig.9 - Configuration with an external hybrid and a SP antenna, integrated or not .................. 20
Fig.10 - Configuration with 2 external hybrids and a not integrated DP antenna ..................... 21
Fig.13 .......................................................................................................................... 28
Fig.16 .......................................................................................................................... 37
Fig.18 – Antenna adapter module (left: external side - right: internal side) ........................... 44
Fig.27 - Dual flanges ALFOplus2 with waveguides connected to the two RF flanges................. 52
Fig.29 - F03616 maintenance cable (to remove after commission pointing) ........................... 56
Fig.55 - Configuration for untagged and known C-tagged traffic in Customer Bridge mode ...... 85
Fig.59 - Configuration for known S-tagged traffic in Provider Core Bridge mode ..................... 88
Fig.60 - PB Port status ................................................................................................... 89
Fig.63 - Configuration for untagged and unknown C-tagged traffic in Provider Edge Bridge mode .
91
Fig.72 - Example of InBand management, LAN1 with local and remote visibility ................... 108
Fig.73 - In band Management example, LAN2 port is dedicated to the management and accesses
to local CPU only .......................................................................................................... 109
Fig.74 - Management traffic to/from On-Site Management port (1+0 case) ......................... 109
Tab.2 - Single ALFOplus2 configurations (purpose, interface module, used antenna) ...............18
Tab.3 - Dual ALFOplus2 in 2+0 configurations (purpose, interface module, used antenna)........18
Tab.4 - Dual ALFOplus2 in 4+0 configurations (purpose, interface modules, used antenna) ......19
Tab.5 - Latency..............................................................................................................31
Tab.19 - Net Radio Throughput in Mbit/s versus channel bandwidth for ALFOplus2 equipment (1+0
configuration) ............................................................................................................... 114
Tab.25 - Net Radio Throughput in Mbit/s versus channel bandwidth for ALFOplus2 equipment (1+0
configuration) ............................................................................................................... 118
Tab.26 - Filter sub-bands for ALFOplus2 11GHz ................................................................ 118
Tab.27 - 10700 MHz - 11700 MHz band - CEPT T/R 12-06 and ITU-R F.387-10 -
Go-return 490 MHz - 180 MHz RF Frequency carrier limits .................................................. 120
Tab.28 - 10700 MHz - 11700 MHz band - CEPT T/R 12-06 and ITU-R F.387-10 -
Go-return 530 MHz - Frequency carrier limits .................................................................... 121
Tab.29 - 10700 MHz - 11700 MHz band - FCC CFR Title 47 Part 101 - Go-Return 490 MHz -
Frequency carrier limits.................................................................................................. 122
Tab.30 - 10700 MHz - 11700 MHz band - FCC CFR Title 47 Part 101 - Go-Return 500 MHz - Fre-
quency carrier limits ...................................................................................................... 123
Tab.36 - 17700 - 19700 MHz band - ITU-R F.595 - Annex 7 - Go-Return 1010 MHz - Frequency
carrier limits .................................................................................................................128
Tab.37 - 17700 - 18140 MHz paired with 19260 - 19700 MHz band - ITU-R F.595 - Annex 7 -
Go-return 1560 MHz - Frequency carrier limits .................................................................. 129
Tab.38 - 17700 - 18140 MHz paired with 19260 - 19700 MHz band - FCC CFR Title 47 Part 101 -
Go-return 1560 MHz - Frequency carrier limits .................................................................. 129
Tab.44 - 22000 - 23600 MHz band - ITU-R F.637-3 - Annex 3 and CEPT T/R 13-02 -
Go-Return 1008 MHz - Frequency carrier limits ................................................................. 134
Tab.45 - 21200 - 23600 MHz band - ITU-R F.637-3 - Annex 1 - Go-return 1232 MHz -
Frequency carrier limits.................................................................................................. 135
Tab.46 - 21200 - 23600 MHz band - ITU-R F.637-3 - Annex 4 - Go-return 1200 MHz -
Frequency carrier limits.................................................................................................. 135
Tab.47 - 21200 - 23600 MHz band - FCC CFR Title 47 Part 101 - Go-return 1200 MHz - Frequency
carrier limits .................................................................................................................136