Professional Documents
Culture Documents
User Manual - V10 - AGS20
User Manual - V10 - AGS20
User manual
MN.00329.E - 010
The information contained in this handbook is subject to change without notice.
Property of Siae Microelettronica S.p.A. All rights reserved according to the law and according to the inter-
national regulations. No part of this document may be reproduced or transmitted in any form or by any
means, electronic or mechanical, without written permission from Siae Microelettronica S.p.A.
Unless otherwise specified, reference to a Company, name, data and address produced on the screen dis-
played is purely indicative aiming at illustrating the use of the product.
MS-DOS®, MS Windows® are trademarks of Microsoft Corporation.
HP®, HP OpenView NNM and HP–UX are Hewlett Packard Company registered trademarks.
UNIX is a UNIX System Laboratories registered trademark.
Oracle® is a Oracle Corporation registered trademark.
Linux term is a trademark registered by Linus Torvalds, the original author of the Linux operating system.
Linux is freely distributed according the GNU General Public License (GPL).
Other products cited here in are constructor registered trademarks.
Contents
Section 1.
USER GUIDE 11
Section 2.
DESCRIPTIONS AND SPECIFICATION 19
MN.00329.E - 010 1
5.4.4 1+1 frequency diversity...........................................................................27
5.4.5 1+1 frequency and space diversity ............................................................28
5.4.6 2+0 single pipe with L1 aggregation ..........................................................28
5.4.7 2+0 single pipe with L1 aggregation in XPIC ...............................................28
5.4.8 AGS-20 multiple direction ........................................................................28
5.4.9 Radio link configurations with AGS20 Single IF interface...............................29
5.4.10 Radio link configurations with AGS20 Dual IF interface .................................29
5.4.10.1 Port clusters configuration .........................................................29
5.4.10.2 Dual IF system configurations ....................................................30
5.4.11 Radio link configurations with AGS20 Quad IF interface ................................32
5.4.11.1 Quad IF: Port clusters configurations ..........................................32
5.4.11.2 Quad IF: system configurations ..................................................33
5.5 ETHERNET SWITCH...........................................................................................41
5.5.1 Ethernet interfaces..................................................................................42
5.5.2 Traffic treatment.....................................................................................43
5.6 DATA PLANE ....................................................................................................43
5.6.1 Ethernet features ....................................................................................43
5.6.1.1 Auto-negotiation ......................................................................43
5.6.1.2 MDI/MDI-X ..............................................................................43
5.6.1.3 Ingress Filtering .......................................................................44
5.6.1.4 MTU .......................................................................................44
5.6.1.5 Storm Control ..........................................................................44
5.6.1.6 MAC Learning Rules ..................................................................44
5.6.1.7 MAC Forwarding Rules ..............................................................45
5.6.2 VLAN Forwarding ....................................................................................45
5.6.2.1 IEEE 802.1q ............................................................................45
5.6.2.2 VLAN Stacking - QinQ ...............................................................46
5.6.2.3 VLAN Threatment .....................................................................46
5.6.2.4 Service Instance Mapping Criteria...............................................47
5.6.2.5 Ingress Manipulation.................................................................48
5.6.3 QoS Management ...................................................................................48
5.6.3.1 Classification with Priority Map ...................................................49
5.6.3.2 Classification with Class Map......................................................50
5.6.4 Policing .................................................................................................51
5.6.4.1 Metering .................................................................................51
5.6.4.2 Policy Map ...............................................................................52
5.6.5 Congestion Avoidance..............................................................................52
5.6.6 Output queues........................................................................................53
5.6.7 Scheduling method .................................................................................55
5.6.8 Egress Shaping.......................................................................................56
5.6.9 Egress Manipulation ................................................................................56
5.6.10 Packet Header Compression .....................................................................56
5.6.11 PWE3 ....................................................................................................58
5.6.11.1 Encapsulation ..........................................................................58
5.6.11.2 PWE3 in Customer Bridge mode .................................................59
5.6.11.3 PWE3 in Provider Edge Bridge mode ...........................................59
5.7 CONTROL PLANE ..............................................................................................60
5.7.1 ELP .......................................................................................................60
5.7.2 Link Aggregation.....................................................................................60
5.7.2.1 Layer 1 radio link aggregation ....................................................61
5.7.2.2 LACP ......................................................................................61
5.7.2.3 Static LAG ...............................................................................62
5.7.3 LLF .......................................................................................................62
2 MN.00329.E - 010
5.7.3.1 Bidirectional LLF.......................................................................62
5.7.3.2 Parameters in Bidirectional LLF...................................................63
5.7.4 STP and RSTP.........................................................................................64
5.7.4.1 BPDU......................................................................................64
5.7.4.2 Root Bridge election .................................................................65
5.7.4.3 Root Port Election.....................................................................65
5.7.4.4 Designated Port Election............................................................65
5.7.4.5 Alternate Port ..........................................................................65
5.7.4.6 STP/RSTP Configurability...........................................................65
5.8 SYNCHRONIZATION ..........................................................................................66
5.8.1 Sources .................................................................................................66
5.8.2 Output ..................................................................................................67
5.8.3 Priority ..................................................................................................67
5.8.4 Quality and SSM .....................................................................................68
5.8.5 Source settings.......................................................................................68
5.8.6 Ethernet Interfaces .................................................................................69
5.9 ETHERNET MAINTENANCE..................................................................................69
5.9.1 OAM......................................................................................................69
5.9.2 RMON ...................................................................................................71
5.9.2.1 Ethernet Statistics ....................................................................71
5.9.2.2 RMON Counters in each interface................................................71
5.9.2.3 Ethernet Services Statistics .......................................................72
5.10 PROGRAMMABILITY ..........................................................................................73
5.10.1 Software................................................................................................74
5.11 AVAILABLE VERSIONS.......................................................................................74
5.11.1 AGS-20 switch........................................................................................75
5.11.2 AGS-20 Single IF ....................................................................................75
5.11.3 AGS-20 Single IF/16E1 ............................................................................76
5.11.4 AGS-20 Dual IF ......................................................................................76
5.11.5 AGS-20 Dual IF/16E1 ..............................................................................77
5.11.6 AGS-20 Quad ETH...................................................................................77
5.11.7 AGS-20 Quad ETH/16E1 ..........................................................................77
5.11.8 AGS-20 PP Single IF/16E1........................................................................78
5.11.9 AGS-20 Dual IF/16E1 + 2STM1 + Nodal.....................................................78
5.11.10AGS-20 Single IF/16E1 + 2STM1 + Nodal .................................................79
5.11.11AGS-20 Quad Eth/16E1 + 2STM1 + Nodal.................................................79
5.11.12AGS-20 PP Single IF/16E1 + 2STM1 + Nodal .............................................80
5.11.13AGS-20 Quad IF ....................................................................................80
5.11.14AGS-20 Quad IF/16E1 ............................................................................81
5.11.15AGS-20 Quad IF/16E1 + 2STM1+ Nodal....................................................81
5.12 SUPPORTED ODUS............................................................................................81
5.13 SUPPORTED FULL ODUS ....................................................................................82
MN.00329.E - 010 3
6.1.1.7 DRI (Connector LAN C, LAN D) ...................................................86
6.1.1.8 COMBO (Connector LAN A, LAN B) ..............................................86
6.1.2 Service interfaces ...................................................................................86
6.1.2.1 LCT ........................................................................................86
6.1.2.2 Alarm .....................................................................................87
6.1.2.3 Console...................................................................................87
6.1.2.4 SYNC (SYNC-1 interface)...........................................................87
6.1.2.5 ToD (SYNC-2 interface) .............................................................87
6.1.2.6 1PPS (SYNC-3 interface) ...........................................................87
6.1.3 Optical indications...................................................................................87
6.1.3.1 System LEDs ...........................................................................87
6.1.3.2 Ethernet interface activity .........................................................88
6.1.3.3 PoE LEDs ................................................................................88
6.1.4 Modulation, bandwidth and relevant capacity ..............................................88
6.1.5 Power supply, consumption and max current absorption...............................91
6.1.6 PoE - Power over Ethernet .......................................................................91
6.1.6.1 PoE characteristics ...................................................................91
6.1.6.2 PoE settings ............................................................................92
6.1.7 IDU general characteristics.......................................................................92
6.1.7.1 Dimensions .............................................................................92
6.1.7.2 Weight....................................................................................92
6.1.7.3 Environment conditions .............................................................92
6.2 AVAILABLE ODUS AND FULL ODUS .....................................................................93
6.2.1 ODUs ....................................................................................................93
6.2.2 Full ODUs ..............................................................................................93
6.3 ODUS, DESCRIPTION AND TECHNICAL CHARACTERISTICS.....................................93
6.3.1 ODU description......................................................................................93
6.3.1.1 ODU versions...........................................................................93
6.3.1.2 Description ..............................................................................94
6.3.1.3 IF cable interface .....................................................................94
6.3.1.4 Power supply ...........................................................................94
6.3.1.5 Tx section ...............................................................................94
6.3.1.6 Rx section ...............................................................................95
6.3.1.7 1+1 Tx system .......................................................................95
6.3.1.8 Full ODUs, description and technical characteristics..................... 101
Section 3.
INSTALLATION 103
4 MN.00329.E - 010
7.7 IDU-ODU INTERCONNECTION CABLE................................................................. 106
7.7.1 Electrical characteristics......................................................................... 106
7.7.2 Connectors .......................................................................................... 106
7.7.3 Max length........................................................................................... 106
7.7.4 Suggested cable ................................................................................... 106
7.7.5 IF cables in XPIC radio link ..................................................................... 106
7.8 GROUNDING CONNECTION .............................................................................. 107
7.9 IDU-ODU CABLE GROUNDING KIT INSTALLATION ............................................... 107
7.9.1 Grounding kit K09283F (for RG8 or 1/8” cable) ......................................... 107
7.9.2 Grounding kit ICD00072F (for any cable with shield) ................................. 108
7.10 SURGE AND LIGHTNING PROTECTION ............................................................... 109
8 CONNECTORS .........................................................................................................111
8.1 CONNECTORS ................................................................................................ 111
MN.00329.E - 010 5
10.7.5 Antenna aiming .................................................................................... 133
10.7.6 ODU grounding..................................................................................... 133
11 INSTALLATION ONTO THE POLE OF THE ODU WITH RFS INTEGRATED ANTENNA...136
11.1 FOREWORD ................................................................................................... 136
11.2 INSTALLATION KIT ......................................................................................... 136
11.3 REQUIRED TOOLS FOR MOUNTING (NOT SUPPLIED) ........................................... 136
11.4 INSTALLATION PROCEDURE ............................................................................. 137
11.5 1+0 MOUNTING PROCEDURES ......................................................................... 137
11.5.1 Setting antenna polarization ................................................................... 137
11.5.2 Installation of the centring ring on the antenna ......................................... 138
11.5.3 Installation of 1+0 ODU support ............................................................. 138
11.5.4 Installation onto the pole of the assembled structure ................................. 138
11.5.5 Installation of ODU (on 1+0 support)....................................................... 138
11.5.6 Antenna aiming .................................................................................... 138
11.5.7 ODU grounding..................................................................................... 139
11.6 1+1 MOUNTING PROCEDURES ......................................................................... 139
11.6.1 Installation of Hybrid ............................................................................. 139
11.6.2 Installation of ODUs (on hybrid for 1+1 version) ....................................... 139
12 INSTALLATION ONTO THE POLE OF ODU ASN/ASNK WITH STANDARD LOCK ........150
12.1 ODU COUPLING KIT ........................................................................................ 150
12.1.1 ODU ASN/ASNK .................................................................................... 150
12.1.1.1 Fast lock coupling kit .............................................................. 150
12.1.1.2 Standard coupling kit .............................................................. 150
12.2 INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED ANTENNA ........... 151
12.2.1 ODU ASN/ASNK (Fast Lock) ................................................................... 151
12.2.2 ODU ASN/ASNK (Standard Lock)............................................................. 151
12.2.2.1 1+0 ODU .............................................................................. 151
12.2.2.2 1+1 ODU .............................................................................. 152
12.3 INSTALLATION ONTO THE POLE OF THE ODU WITH SEPARATED ANTENNA............. 153
12.3.1 ODU ASN/ASNK (Fast Lock) ................................................................... 153
12.3.2 ODU ASN/ASNK (Standard Lock)............................................................. 153
12.3.2.1 1+0 ODU .............................................................................. 154
12.3.2.2 1+1 ODU .............................................................................. 154
12.3.2.3 Waveguide towards the antenna............................................... 156
Section 4.
LINE-UP 165
14 LINE–UP OF AGS-20...............................................................................................165
14.1 GENERAL....................................................................................................... 165
14.2 SWITCH ON ................................................................................................... 166
14.3 ALARM LED CHECK ......................................................................................... 166
14.4 CONNECTION TO EQUIPMENT .......................................................................... 166
14.4.1 Connection to LCT or LAN3 port .............................................................. 166
6 MN.00329.E - 010
14.4.2 Connection using WLC ........................................................................... 167
14.4.3 CLI session using Hyperterminal (or a similar software) ............................. 167
14.5 RADIO LINK CONFIGURATION .......................................................................... 167
14.6 EQUIPMENT CONFIGURATION .......................................................................... 167
14.6.1 IP address setting ................................................................................. 168
14.6.2 Bandwidth, modulation, TDM and Link ID setting....................................... 168
14.6.3 Tx frequency setting.............................................................................. 168
14.6.4 Tx power setting ................................................................................... 169
14.6.5 Equipment ID and Agent IP setting.......................................................... 169
14.6.6 Routing Table setting............................................................................. 169
14.6.7 Remote Element Table........................................................................... 169
14.7 ANTENNA ALIGNMENT AND RX POWER .............................................................. 170
14.7.1 ODU ASN and ODU ASNK ....................................................................... 170
14.7.2 Full ODU .............................................................................................. 170
Section 5.
MAINTENANCE 171
15 ALARMS .................................................................................................................171
15.1 ALARM SYSTEM .............................................................................................. 171
15.1.1 LED status ........................................................................................... 172
15.1.2 Alarm group ......................................................................................... 172
MN.00329.E - 010 7
16.5.2.7 FMP Reset Procedure .............................................................. 188
16.5.2.8 XPIC Manual Operation ........................................................... 188
16.5.2.9 Interaction between other Maintenance command and XIPC FMP .. 189
16.6 MAN.OP. E CONSEQUENTIAL ACTION FOR 1+1 XPIC HS/FD ................................. 189
16.6.1 Introduction ......................................................................................... 189
16.6.2 TX OFF ................................................................................................ 190
16.6.2.1 Hot Stand-by configuration: TX OFF .......................................... 190
16.6.2.2 Frequency Diversity configuration: TX OFF ................................. 190
16.6.3 Carrier Only ......................................................................................... 190
16.6.4 RT PSU OFF.......................................................................................... 191
16.6.4.1 1+1 HOT STBY configuration: RT PSU OFF ................................. 191
16.6.4.2 Configuration Frequency diversity: RT PS OFF ............................ 191
16.6.5 IF Loop................................................................................................ 192
16.6.5.1 System Configuration Hot-STBY: IF loop.................................... 192
16.6.5.2 System configuration Frequency Diversity: IF Loop ..................... 193
16.6.6 RF Loop ............................................................................................... 194
16.6.6.1 System Configuration Hot-STBY: RF Loop .................................. 194
16.6.6.2 System Configuration Frequency Diversity: RF Loop .................... 194
Section 6.
PROGRAMMING AND SUPERVISION 197
Section 7.
COMPOSITION 203
8 MN.00329.E - 010
Section 8.
LISTS AND SERVICES 215
23 ASSISTANCE SERVICE............................................................................................221
MN.00329.E - 010 9
10 MN.00329.E - 010
Section 1.
USER GUIDE
1 DECLARATION OF CONFORMITY
SIAE MICROELETTRONICA
Via Buonarroti, 21 - Cologno (MI) - Italy
DECLARES
THAT THE PRODUCT
MN.00329.E - 010 11
2 FIRST AID FOR ELECTRICAL SHOCK AND SAFETY
RULES
Do not touch the bare hands until the circuit has been opened. pen the circuit by switching off the line
switches. If that is not possible protect yourself with dry material and free the patient from the con-
ductor.
It is important to start mouth respiration at once and to call a doctor immediately. suggested procedure
for mouth to mouth respiration method is described in the Tab.1.
This treatment should be used after the patient has regained consciousness. It can also be employed while
artificial respiration is being applied (in this case there should be at least two persons present).
Warning
12 MN.00329.E - 010
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
MN.00329.E - 010 13
2.2 SAFETY RULES
When the equipment units are provided with the plate, shown in Fig.1, it means that they contain compo-
nents electrostatic charge sensitive.
In order to prevent the units from being damaged while handling, it is advisable to wear an elasticized band
(Fig.2) around the wrist ground connected through coiled cord (Fig.3).
This device has Class I LASER modules: it is not required to have a laser warning label or other laser state-
ment (IEC 60825-1).
14 MN.00329.E - 010
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.00329.E - 010 15
3 PURPOSE AND STRUCTURE OF THE MANUAL
The purpose of this manual consists in providing the user with information which permit to operate and
maintain the AGS-20 radio family.
Warning: This manual does not include information relevant to the 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 traces the broad line of equipment operation and lists the main technical characteristics of the whole
equipment and units it consists of.
16 MN.00329.E - 010
Section 3 – Installation
The mechanical installation procedures are herein set down as well as the user electrical connections.
Section 4 – Line–Up
Line–up procedures are described as well as checks to be carried out for the equipment correct operation.
The list of the instruments to be used and their characteristics are also set down.
Section 5 – Maintenance
In this section a description of alarms is given in order to help operators to perform equipment mainte-
nance and troubleshooting.
The AGS-20 radio family is programmed and supervised using different software tools. Some of them are
already available, some other will be available in the future.
This section lists the tools implemented and indicates if descriptions are already available.
Section 7 – Composition
Position, part numbers of the components the equipment consist of, are shown in this section.
This section contains the lists of figures and tables and the assistance service information.
MN.00329.E - 010 17
18 MN.00329.E - 010
Section 2.
DESCRIPTIONS AND
SPECIFICATION
- BW Bandwidth
- CBPDU Configuration BPDU
MN.00329.E - 010 19
- E1 European Plesiochronous Transport Module level-1
- ETH Ethernet
- GE Gigabit Ethernet
- MA Maintenance Association
- MD Maintenance Domain
- MNG Management
- MW Microwaves
20 MN.00329.E - 010
- N.C. Not Connected
- NE Network Element
- PWR Power
- QL Quality
- QoS Quality of Service
- SW Software
- tbc to be confirmed
- tbd to be defined
MN.00329.E - 010 21
- UART Universal Asynchronous Receiver-Transmitter
- µP Microprocessor.
22 MN.00329.E - 010
5 SYSTEM PRESENTATION
5.1 GENERAL
AGS-20 is a split microwave radio system for Ethernet transport made up by one IDU and up to 4 ODUs.
The AGS-20 IDU has various sub-units within a 1RU indoor equipment that is made up by a complete range
of interfaces (Gigabit/Fast Ethernet, E1, STM-1) towards both IF compatible SIAE ODU and Ethernet com-
patible Full-ODU (up to ten interfaces can be equipped in a 1RU IDU allowing reaching up to ten different
directions).
Higher level of connectivity is provided by supporting IDU stackability for nodal configuration, addressing
demand for higher number of radio directions, GE and TDM interfaces.
The AGS-20 IDU must be used in RAL areas (Restricted Access Location) where an equipotent bonding has
been applied. The IDU unit has a supplementary specific connector for a permanent connection to the
grounding point intended to be installed by service persons only.
5.2 APPLICATIONS
AGS-20 can be configured as an Indoor Unit for split mount radio: AGS-20 brings superior packet capabil-
ities, certified to comply with LTE transport requirements.
Still it supports TDM traffic, both native and pseudowire, to allow easy network evolution from pure TDM
to pure IP:
• 2G/3G/4G Cellular Network backhauling infrastructure
• WiMAX Backhauling
AGS-20 is an Universal Microwave Aggregation Platform addressing the need for carrier-class multi-tech-
nology traffic aggregation.
Based on high performance Carrier Ethernet 2.0 engine (MPLS ready), the platform enables convergence
of the major microwave application segments:
MN.00329.E - 010 23
All outdoor radio aggregator
Radio Access migration towards full packet technology is boosting demand for Full Outdoor microwave
equipment. AGS-20 enables this move by providing:
AGS-20 set a new industry benchmark in split mount microwave by featuring the following capabilities:
Small cell layer is expected to increase number of transport connections of x10 factor compared to Macro-
cell backhaul layer. Such network evolution demands for data traffic aggregation capability and some man-
agement intelligence in the network nodes to avoid flood of management traffic and prevent overwhelming
complexity towards central NMS.
AGS-20 (EasyCell Gateway) acts as small-cell cluster aggregator and manager providing the following fea-
tures:
• Connectivity towards EasyCell small form factor radios
• Gateway functionality between small cell backhauling radios and NMS: configuration, monitoring
and management at cluster level
5.2.1 Functionalities
• Hitless Rlag
• Flexible QoS definition based on VLAN, IPv4, IPv6, MPLS exp bits
24 MN.00329.E - 010
• Flow Based Ingress Policing (CIR & EIR definition)
• Egress shaping
• Jumbo Frames
AGS20 split mount radio system can support multiple configurations depending on the following charac-
teristics:
• hardware protection
In addition the AGS-20 can be connected to SIAE Full outdoor equipment through all the available LAN
interfaces, supporting multiple radio directions.
AGS-20 is able to simultaneously manage N radio links outgoing from the available IF interfaces. In case
the N links are parallel (i.e. deployed between the same two sites) the Ethernet capacity can be aggregated
in order to increase the capacity of the Ethernet connection.
In this case the Link Aggregation mechanism is not based on MAC hashing, but on a more efficient Layer
1 distribution of the traffic over the two radio channels. The traffic received from the line interfaces, after
the L2 Ethernet switch processing, is fragmented and labeled with proprietary protocols. The additional la-
beling is used to keep trace of the original order of the fragments before to send it over the radio. On the
receiver side the fragments are recomposed with the original order. In this way the correct packet order
is preserved, independently from the frequency channel over which each packet has been sent.
The fragments are sent over the air in order to balance the load between the N frequency channels. The
balancing mechanism is able to take into account also the imbalance in the available capacity on the N
radio links (for example, in the case an ACM modulation down-switch occurs only on one radio branch).
The final result is that the traffic is balanced over the N radio channels on the basis of the available capacity
and independently from any other packet characteristics (source or destination MAC address etc...). Resil-
iency between the aggregated radio links is inherently provided by the balancing mechanisms (if one radio
channel becomes unavailable all the traffic will be sent on the other channels).
The maximum capacity that can be aggregated is relevant to N times the maximum channel available on
AGS-20. However, due to the additional fragment labeling used by the protocol there is a slight loss in
terms of available capacity over the radio link. This loss is dependent from the Ethernet packet length.
MN.00329.E - 010 25
5.3.2 Hitless RLag
Hitless RLag consists in making a “hitless" management (removal and reintroduction) of concatenated ODU
(ASN/ASNK) from Physical LAG according to current ACM profile.
Hitless Physical
Level Aggregation Up to 4 ODU
in case of IDU Quad-IF
Fig.5
The hitless PLA management behaves in this way:
• continuously checks every link degradation in order to remove a bad quality link in advance from
LAG (link status estimator)
• if necessary removes the degrades link from PLA.
The Link Status Estimator uses a new profile in the ACM range: the Hitless profile (= Lower profile +1).
Every time in Rx the S/N of a radio link of the group goes under the Removal threshold, that radio link
leaves the hitless PLA and every time the S/N overtakes the Reintroduction threshold that radio link enters
again in the group. Removal and the reintroduction are performed without errors.
Fig.6
26 MN.00329.E - 010
5.4 BRIEF RADIO LINK DESCRIPTION
5.4.1 1+0
Description:
• no HW or diversity protection
Description:
• ODU HW protection
• single radio direction
Description:
• ODU HW protection
Description:
• ODU HW protection
MN.00329.E - 010 27
5.4.5 1+1 frequency and space diversity
Description:
• ODU HW protection
Description:
• 2 RF channels
• no HW protection
In this configuration a single Ethernet logical channel with double capacity is available on the radio obtained
by means of layer 1 link aggregation of the 2 physical radio channels.
Description:
In this configuration a single Ethernet logical channel with double capacity is available on the radio obtained
by means of layer 1 link aggregation of the 2 physical radio channels.
Description:
• no HW or diversity protection
• multiple radio directions can be managed through IF interfaces (one per each IF)
28 MN.00329.E - 010
5.4.9 Radio link configurations with AGS20 Single IF interface
• N.C. stands for Not Connected and it means that the interface is unused.
• SINGLE stands for single not protected connection. It can be realized with 1+0 radio configuration.
1+0
f1
f
In this HW configuration 2 IF interfaces are available. Fig.8, Fig.9 and Fig.10 show the available port clus-
ters for each specific radio configuration.
Protection cluster 1:
ODU-A; ODU-B
(2+0)XPIC cluster 1:
ODU-A; ODU-B
MN.00329.E - 010 29
(2+0) FD cluster 1:
ODU-A; ODU-B
System configuration is compound of 3 configurations related to the 2 IF ports and, when necessary, up
to 1 cluster identification (ports<->cluster association). Supported port configurations are:
• N.C. stands for Not Connected and it means that the interface is unused.
• SINGLE stands for single not protected connection. It can be realized with 1+0 radio configuration.
• PROTECTION stands for protected connection. It can be realized with one of the following radio con-
figurations:
- 1+1 HSB
- 1+1 SD (not displayed in the system configuration table because in practice it is a 1+1 HSB with
space diversity antenna installation)
- 1+1 FD.
• SHARING or RLAG stands for the Physical Layer Aggregation of more than one radio channels in
order to set up a single radio bundle. It can be realized with one of the following radio configura-
tions:
30 MN.00329.E - 010
1+0
1+0
f1 f2
f
1+1 f
f1 f2
MN.00329.E - 010 31
CCDP solution
f1
ACAP solution
f1 f2
2+0
f
ACCP solution
f1 f2
In order to support protection for XPIC configuration a specific interconnection between modem chips must
be provided. Fig.14, Fig.15, Fig.16, Fig.17, Fig.18 and Fig.19 show the available port clusters for each spe-
cific radio configuration.
Protection cluster 2:
Protection cluster 1:
ODU-B; ODU-D
ODU-A; ODU-C
(2+0)XPIC cluster 2:
(2+0)XPIC cluster 1:
ODU-C; ODU-D
ODU-A; ODU-B
32 MN.00329.E - 010
(2+0) FD cluster 1: (2+0) FD cluster 3: (2+0) FD cluster 2:
ODU-A; ODU-B ODU-A; ODU-C ODU-C; ODU-D
Fig.17 - (1+1) XPIC protection: all IF ports are part of the cluster
(4+0) FD cluster:
4 IF ports
System configuration is compound of 4 configurations related to the 4 IF ports and, when necessary, up
to 2 clusters identification (ports<->cluster association).
• N.C. stands for Not Connected and it means that the interface is unused.
• SINGLE stands for single not protected connection. It can be realized with 1+0 radio configuration.
• PROTECTION stands for protected connection. It can be realized with one of the following radio con-
figurations:
- 1+1 HSB
MN.00329.E - 010 33
- 1+1 SD (not displayed in the system configuration table because in practise it is a 1+1 HSB with
space diversity antenna installation)
- 1+1 FD.
• SHARING or RLAG stands for the Physical Layer Aggregation of more than one radio channels in
order to set up a single radio bundle. It can be realized with one of the following radio configura-
tions:
• XPIC PROTECTION stands for protected connection of two (2+0) XPIC radio bundle. It can be real-
ized with the following radio configuration:
- 1+1 XPIC (3 possible protection sub-types: HSB; SD (not displayed in the system configuration
table because in practise it is a 1+1 HSB with space diversity antenna installation) and FD)
34 MN.00329.E - 010
Tab.7 - Quad IF: system configurations table
Port
Min SYV ODU-A ODU-B ODU-C ODU-D
configuration
1 1.6.0 (1+1) HSB cluster 1 (1+0) or N.C. (1+1) HSB cluster 1 (1+0) or N.C.
3 1.6.0 (2+0) RLAG-FD cluster 1 (2+0) RLAG-FD cluster 1 (1+0) or N.C. (1+0) or N.C.
4 1.6.0 (2+0) RLAG-XPIC cluster 1 (2+0) RLAG-XPIC cluster 1 (1+0) or N.C. (1+0) or N.C.
8 1.6.0 (2+0) RLAG-FD cluster 3 (1+0) or N.C. (2+0) RLAG-FD cluster 3 (1+0) or N.C.
9 1.6.0 (1+0) or N.C. (1+1) HSB cluster 2 (1+0) or N.C. (1+1) HSB cluster 2
11 1.6.0 (2+0) RLAG-FD cluster 3 (1+1) HSB cluster 2 (2+0) RLAG-FD cluster 3 (1+1) HSB cluster 2
12 1.6.0 (2+0) RLAG-FD cluster 3 (1+1) FD cluster 2 (2+0) RLAG-FD cluster 3 (1+1) FD cluster 2
13 1.6.0 (1+1) HSB cluster 1 (1+1) FD cluster 2 (1+1) HSB cluster 1 (1+1) FD cluster 2
14 1.6.0 (1+1) FD cluster 1 (1+1) HSB cluster 2 (1+1) FD cluster 1 (1+1) HSB cluster 2
15 1.6.0 (1+1) HSB cluster 1 (1+1) HSB cluster 2 (1+1) HSB cluster 1 (1+1) HSB cluster 2
17 1.6.0 (2+0) RLAG-FD cluster 1 (2+0) RLAG-FD cluster 1 (2+0) RLAG-XPIC cluster 2 (2+0) RLAG-XPIC cluster 2
18 1.6.0 (2+0) RLAG-XPIC cluster 1 (2+0) RLAG-XPIC cluster 1 (2+0) RLAG-FD cluster 2 (2+0) RLAG-FD cluster 2
19 1.6.0 (2+0) RLAG-FD cluster 1 (2+0) RLAG-FD cluster 1 (2+0) RLAG-FD cluster 2 (2+0) RLAG-FD cluster 2
20 1.6.0 (2+0) RLAG-XPIC cluster 1 (2+0) RLAG-XPIC cluster 1 (2+0) RLAG-XPIC cluster 2 (2+0) RLAG-XPIC cluster 2
Port
Min SYV ODU-A ODU-B ODU-C ODU-D
configuration
MN.00329.E - 010 35
1+0 1+0
1+0 1+0
f1 f2 f3 f4
f
Port
Min SYV ODU-A ODU-B ODU-C ODU-D
configuration
1 1.6.0 (1+1) HSB cluster 1 (1+0) or N.C. (1+1) HSB cluster 1 (1+0) or N.C
9 1.6.0 (1+0) or N.C. (1+1) HSB cluster 2 (1+0) or N.C. (1+1) HSB cluster 2
1+1 f
f1 f2
36 MN.00329.E - 010
Hot Standby solution
f1
1+1 f
f1 f2
Port
Min SYV ODU-A ODU-B ODU-C ODU-D
configuration
MN.00329.E - 010 37
CCDP solution
f1
ACAP solution
f1 f2
2+0
f
ACCP solution
f1 f2
3+0
ACCP solution
f1 f2 f3
38 MN.00329.E - 010
CCDP solution
f1 f2
ACAP solution
f1 f2 f3 f4
4+0
ACCP solution
f1 f2 f3 f4
ACAP solution
f1 f2
2+0
f
ACCP solution
f1 f2
Port
Min SYV ODU-A ODU-B ODU-C ODU-D
configuration
11 1.6.0 (2+0) RLAG-FD cluster 3 (1+1) HSB cluster 2 (2+0) RLAG-FD cluster 3 (1+1) HSB cluster 2
12 1.6.0 (2+0) RLAG-FD cluster 3 (1+1) FD cluster 2 (2+0) RLAG-FD cluster 3 (1+1) FD cluster 2
MN.00329.E - 010 39
2+0
Hot Standby solution
f1
ACAP solution
1+1 f
f1 f2
f1 f2
ACCP solution
f
f1 f2
Fig.27 - Port config 11 and 12: (2+0) cluster 3 & (1+1) cluster 2
Port
Min SYV ODU-A ODU-B ODU-C ODU-D
configuration
13 1.6.0 (1+1) HSB cluster 1 (1+1) FD cluster 2 (1+1) HSB cluster 1 (1+1) FD cluster 2
14 1.6.0 (1+1) FD cluster 1 (1+1) HSB cluster 2 (1+1) FD cluster 1 (1+1) HSB cluster 2
15 1.6.0 (1+1) HSB cluster 1 (1+1) HSB cluster 2 (1+1) HSB cluster 1 (1+1) HSB cluster 2
1+1
Hot Standby solution Hot Standby solution
f1 f1
f 1+1 f
f f
Fig.28 - Port config from 13 to 16: (1+1) cluster 1 & (1+1) cluster 2
Port
Min SYV ODU-A ODU-B ODU-C ODU-D
configuration
17 1.6.0 (2+0) RLAG-FD cluster 1 (2+0) RLAG-FD cluster 1 (2+0) RLAG-XPIC cluster 2 (2+0) RLAG-XPIC cluster 2
18 1.6.0 (2+0) RLAG-XPIC cluster 1 (2+0) RLAG-XPIC cluster 1 (2+0) RLAG-FD cluster 2 (2+0) RLAG-FD cluster 2
19 1.6.0 (2+0) RLAG-FD cluster 1 (2+0) RLAG-FD cluster 1 (2+0) RLAG-FD cluster 2 (2+0) RLAG-FD cluster 2
20 1.6.0 (2+0) RLAG-XPIC cluster 1 (2+0) RLAG-XPIC cluster 1 (2+0) RLAG-XPIC cluster 2 (2+0) RLAG-XPIC cluster 2
40 MN.00329.E - 010
CCDP solution
f1
CCDP solution
f1 f
2+0
f
ACAP solution
f1 f2
ACAP solution
2+0
f1 f2 f
f
ACCP solution
ACCP solution f1 f2
f1
f
f2
Fig.29 - Port config from 17 to 20: (2+0) cluster 1 & (2+0) cluster 2
Port
Min SYV ODU-A ODU-B ODU-C ODU-D
configuration
1+1 XPIC f
The AGS-20 hardware layout is a single motherboard connected to a single Internal Ethernet Switch, used
to route data traffic and protocols’ traffic of the control plane and for DCN connectivity.
MN.00329.E - 010 41
5.5.1 Ethernet interfaces
In Tab.15 are listed the technical parameters of the switch and in Fig.31 is represented the Ethernet block
diagram.
Up to 4 interfaces (Eth/IF)
depending on Hw version
42 MN.00329.E - 010
5.5.2 Traffic treatment
With reference to 802.1ad, the switch can be set through WEBLCT or CLI in predefined configurations:
• Customer Bridge (default mode): in this mode the L2 Ethernet switch is a 802.1q aware component.
There is interoperability with customer devices that are not able to manage S-VLANs, as they are
not 802.1ad aware: only C-VLAN modality is used. Moreover, in this mode the transport over the
radio link is more efficient since a double tag is not added.
• Provider Bridge: in this mode the L2 Ethernet switch is a 802.1ad aware component. The switch
operates with S-VLAN frames, forwarding the packets accordingly. Further, in accordance with MEF
requirements (basically MEF 10.2 and MEF 6.1) each EVC is identified using a S-tag, added by the
equipment at UNI ports (at Customer Edge) or received at NNI ports (at Provider Edge). If C-VLANs
are also involved a further classification is necessary as in Tab.16
In the next paragraphs are listed the Ethernet features offered by the switch of AGS-20.
5.6.1.1 Auto-negotiation
Auto-negotiation standards are regarding speed from 10BaseT to 1000BaseT, Full Duplex.
In addition, for 1000BaseT, auto-negotiation determines the master/slave configuration between the PHYs
at the ends of the link, necessary to establish the source of the timing control of each SETS.
Auto-negotiation is not necessary for optical interface ports with speed of 1Gbps or 2.5Gbps both Full Du-
plex.
5.6.1.2 MDI/MDI-X
For Electrical interfaces only, available values are MDI, MDI-X and Auto mode.
MN.00329.E - 010 43
5.6.1.3 Ingress Filtering
In each interface, it is possible to specify which frame types are accepted or denied.
The Ingress Filtering criteria are based on the following configurable parameters:
- tagged only: the port accepts only the Tagged packets. Untagged and Priority Tagged packets
are rejected
- untagged and Priority Tagged: the port accepts only the Untagged and Priority Tagged packets.
Tagged packets are rejected
Note: in case the port is configured as Customer Edge Port or Customer Network Port the only option avail-
able is “Untagged and Priority Tagged”.
• Ingress Filtering
- enabled: the port accepts, in input, only packets with VLAN ID contained in VLAN table and the
input port must be member of this VLAN, otherwise the packet is discarded
- disabled: the port does not execute any check and all the packets are accepted
5.6.1.4 MTU
MTU correspond to the maximum dimension (in byte) of the data field accepted by the interface without
the bytes of Ethernet header and CRC (frame size between <46-12266> in Byte (Jumbo Frames).
The feature limits the maximum amount of traffic that can be accepted at the input of the switch LAN ports.
This is, for each LAN port, a rate limiter (PIRL set as active for each relevant LAN interface) to the incoming
Ethernet data traffic relevant to a combination of the three following traffic types (independently from the
VLAN ID and priority level):
• BROADCAST
• MULTICAST unknown, multicast packets with destination MAC addresses not present in the MAC ta-
ble
• UNICAST unknown, unicast packets with destination MAC addresses not present in the MAC table
The configuration of the storm control can be done by means of a CLI script.
The MAC learning mechanism operates on VLAN ID basis: the incoming packet is associated to a VLAN (de-
termined by Outer-VLAN tag from 1 to 4094 or assigned as Port VID) and the forwarding is allowed only
among ports configured as belonging to the same VLAN of the packet. Between the ports belonging to the
same VLAN the actual recipient port is then determined on the base of the packet destination MAC address.
44 MN.00329.E - 010
The Learning process in VLAN independent: the information learned by a VLAN is not used by other VLAN’s
to forward their frames.
The MAC Learning mode has to be activated configuring the Ethernet switch “Basic Settings” as follows (i.e.
“Global MAC Learning Status” set as “Enable”, default option). This option is common to all port of the
switch.
Note: up to 100 MAC per VLAN can be registered in the MAC table and up to 4K VLAN-ID are supported.
Note: disabling the MAC Learning does NOT allow to have the monitoring on the MAC addresses received
by LAN ports.
Special treatment of specific control protocols frames (LACP, RSTP, etc.) or multicast addresses, as defined
in MEF, is supported. In particular it is possible to:
The unit can decide if the BPDUs of control protocols have to be processed and consequently managed by
the equipment that actively participates in protocols mechanisms (peered), simply transported through the
switch without any change (tunneled), or merely terminated because of security or policy reasons (dis-
carded).
The frames of the following protocols can be managed by the AGS-20 switch:
• Dot1x
• LACP
• STP
• GVRP
• GMRP
• IGMP
L2 forwarding function establishes the egress port for each incoming frames, on the base of its MAC ad-
dress and/or VLAN ID. Consequently, the MAC forwarding rule of each LAN interface is the following:
• MAC Destination Address + VID Basis: the incoming packet is associated to a VLAN (determined by
Outer-VLAN tag or assigned as Port VID). Within the ports belonging to the same VLAN, the egress
port is then determined on the base of the frame MAC destination address
• VID Basis: if the MAC learning option is disabled, the forwarding is performed among all ports con-
figured as belonging to the VLAN of the packets, without checking the MAC address
Multicast and Broadcast packets are handled in the same way, i.e. forwarded to all enabled ports. Flooding
of not-unicast and unknown unicast frames is performed toward all the ports that are members of frame’s
VLAN domain, excluding the port the frame is received from.
AGS-20 switch works always in a VLAN aware bridge mode in which the equipment is able to manage
VLANs, recognizing, inserting and removing VLAN tags in Ethernet frames. In this sense the switch is com-
pliant with standard IEEE 802.1q and 802.1ad (QinQ).
VLAN forwarding can be configured in two different ways, depending on incoming frames:
MN.00329.E - 010 45
• Based on port (“Port Default VLAN”), where the membership of the VLAN is related to a local port
attribute, regardless the packet content. This means that the membership of the VLAN is based on
the port on which traffic is received and on the frame type
• Based on IEEE 802.1q TAG (“VLAN Configuration”), where the member of the VLAN is defined by
the VLAN ID (VLAN identifier) TAG content
“Port Default VLAN” and “VLAN Configuration” are not mutually exclusive but can be used both at the same
time.
The additional tag is defined in the standard IEEE802.1ad. VLAN stacking differentiates the traffic at dif-
ferent levels when the packets must cross networks managed by different entities (e.g. provider).
When VLAN stacking is used, one or more additional VLAN tag are added to already tagged frames: the
first VLAN tag is usually named C-VLAN, while the second VLAN tag is named S-VLAN.
The possible operations that can be performed with VLANs on the AGS-20 are strictly connected to the
switch and ports configuration set on the equipment. These possible actions can be described accordingly
to the standard 802.1ad network architecture depending on switch bridge mode.
1. Customer Bridge, the switch receives and elaborates untagged or C-tagged packets and VLAN type
registered in the VLAN table is C-VLAN. Port kind is Customer Port only.
The Customer Port (CP) performs the following actions:
- Tag ingress untagged packets with C-tag, creating C-VLAN to forward them to the egress port
- Untag C-tag packets at egress; in this case the action “untagged” has to be specified in the script
- Receive already C-tagged packets and forward them to the egress port according to existing
VLAN table; if the C-tag is not present in the VLAN table the packet is dropped
2. Provider Edge Bridge, the switch manages untagged, C-tagged and S-tagged packets. VLAN type
registered in the VLAN table is S-VLAN. Three types of port are available: Customer Edge Port, Cu-
stomer Network Port and Provider Network Port.
The Customer Edge Port (CEP) performs the following actions:
- Create a PtoP connection between two ports of the switch through an EVC, mapping an ingress
C-tagged packet to an S-tagged packet one-to-one emulating the virtual communication betwe-
en the two internal ports CNP and PEP
The Customer Network Port (CNP) performs the following actions:
- Receive C-tagged packets and add a S-tag at ingress, creating a S-VLAN; port type has to be
“port-based”; in this case the difference from the CEP is that all the incoming packets will be S-
tagged with the same VLAN value
- Remove the S-tag at egress to render the Customer traffic as it was at the ingress part of the
Provider network; in this case the action “untagged” has to be specified in the script (this is the
only available option)
The Provider Network Port (PNP) performs the following actions:
- Receive already S-tagged packets and forward them to the egress port
In Customer Bridge and in Provider Edge Bridge a default port VLAN ID has to be set on the “port-
based” interfaces. The PVID represents the VLAN ID that is to be assigned to:
- untagged frames
- C-tag frames in case the switch is in Provider Bridge Mode, as the frame is considered as untag-
ged (no S-tag)
46 MN.00329.E - 010
The PVID is used for port based VLAN type membership classification (ID between 1 and 4094,
default = 1).
3. Provider Core Bridge, the switch manages S-tagged packets and VLAN type registered in the VLAN
table is S-VLAN. Port kind is Provider Network Port only.
The Provider Network Port (PNP) performs the following action:
- Receive already S-tagged packets and forward them to the egress port
In WEB LCT is present a static VLANs management area where it is possible modify and create VLANs (per
port).
During the creation of a static VLAN, one port of the Switch is assigned to a specific VLAN, so that the
device connected to that port automatically becomes member of the assigned VLAN.
VLAN creation can be also performed through CLI script, in accordance with 802.1ad and S-VLAN aware
configuration or with MEF specifications, creating a virtual circuit between two or more ports of the switch,
defining the proper network interfaces and mapping the incoming C-tagged frames into an S-tagged frame.
In this logical block the incoming packet is analyzed to match the desired criteria for the association to an
EVC, identified by a C or S-VLAN (therefore the assignment of a transport C-tag or S-tag), and for the
assignment to an Internal Priority level.
Mapping functionality (at UNI port) allows associating to all incoming traffic a specific VLAN ID, identifying
the Ethernet Virtual Connection (EVC). Depending on the switch operation mode, different parameters can
be considered in this classification process:
1. In Customer Bridge the “EVC” is identified by a Carrier Ethernet VLAN ID that is inserted on the
frame at the ingress port according to the following criteria:
- Untagged or Priority tagged frames: they are associated by default to the CE VLAN identified by
the port VID (default VID associated to the port); the other C-tag fields are the following:
- Costumer EtherType: fixed to 0x8100
- C-PCP management of port VID:
- Assigned by user
- Remapping of DSCP
- Incoming tagged: they are be treated on the base of rules configured for the VLAN correspond-
ing to the C-VID of the frames
2. In Provider Bridge the EVC is identified by an S-tag. Configurable mapping rules are (per each UNI-
port):
- Ingress User Port: all traffic from the port is mapped on the same unique EVC
- User C-VLAN ID: all traffic associated to one or more VLAN ID (C-tag) is mapped on the same
EVC
Traffic that doesn’t match any mapping criteria is discarded or associated with a default EVC.
Multiplexing functionality are supported: various EVC (S-tag) per port. S-Tag fields are determined as be-
low:
- S-tag EtherType: it is configurable by the user (default is 0x88a8). The configured value is used
to
- Detect the S-tagged frames
- Define the S-tag type to be added
- S-PCP:
- Assigned by user
- Copy (or in general “Remapping”) of C-tag-PCP
MN.00329.E - 010 47
5.6.2.5 Ingress Manipulation
- VLAN rewriting: it identifies the possibility to map an S-VLAN ID received at ingress port in an-
other S-VLAN ID; it works in a bidirectional way
- Port mirroring: the switch sends a copy of all network frames seen on one port to another port,
where the packet can be analyzed
- Port Isolation: the switch forwards all frames received from a port to another specific port, re-
gardless of VLAN ID or destination MAC address. In the example below, port <LAN1> forwards
frames just to <RADIO> port, <LAN2> forwards frames just to <RADIO> port as well and <RA-
DIO> port forwards frames just to <LAN1> and <LAN2>
- Loopback: in order to create a loop of traffic incoming on an interface and outgoing from the
same interface, for example for management purposes, it is possible to set a loopback on a LAN
port
QoS features available on Ethernet LAN and radio ports are summarized in Fig.32.
48 MN.00329.E - 010
Fig.32 – QoS block diagram
Each port can independently analyze the incoming frame and decide its internal priority (queue) based on
the following criteria:
• Layer 2 802.1p QoS, using the 3 bits of the C-PCP or S-PCP in the tag 802.1q (depending on the
bridge mode)
• Layer 3 IPv4 and IPv6, using the 6 bits of the ToS (DSCP)
MN.00329.E - 010 49
• the input priority value (InPriority)
As default Layer 2 PCP 802.1p is enable on each port, with a 8-level default priority-map (from 0 to 7).
The default 802.1p map, see Fig.33, cannot be removed but only modified.
In order to prevent unwanted traffic or actions an admission control lists (ACL) is available, allowing the
ingress of data that respect defined criteria:
• up to 16 source or destination static MAC addresses per port (logical in case of LAG)
• port based
50 MN.00329.E - 010
• C-VLAN for incoming double S-Tagged frames in provider bridge mode
• C-VLAN + C-PCP for incoming double S-Tagged frames in provider bridge mode
• S-VLAN + S-PCP for incoming double S-Tagged frames in provider bridge mode
• C-VLAN + S-VLAN for incoming double S-Tagged frames in provider bridge mode
After frames classification performed by ACL list, the internal priority definition of the frame for the queuing
procedure passes through a Class-map, used to create class of service: the class is defined by a numeric
index and based on ingress criteria of the previous L2 ACL.
A class-map matches a single Class with a single Layer 2 ACL and creates the correspondence with a single
internal priority value.
8 different Class-map are defined as default: class-map 1 to 8 match the priority-map 1 to 8 with the con-
sequent internal priority level. Default class-map cannot be removed but can be modified.
5.6.4 Policing
Traffic policing, also known as rate limiting, defines a bandwidth profile (BWP) depending on the Service
Level Specification that has been agreed upon by the Subscriber and the Service Provider.
Specifically, this phase defines a set of traffic rate limits and performs actions on traffic that is not con-
formed to the configured limits.
• CIR (Committed Information Rate): it defines the average traffic rate that a subscriber is allowed
to use, with guaranteed performances in terms of attributes for the associated service (“green”
colored)
• EIR (Excess Information Rate): it is the additional bit-rate that the subscriber can use as long as
there is no congestion (“yellow” colored)
• PIR (Peak Information Rate): it is the maximum average sending rate, i.e. CIR+EIR, beyond which
the traffic is discarded (“red colored”)
• CBS (Committed Burst Size): this value defines the maximum amount of contiguous packets that a
customer is allowed to send in a single burst
• EBS (Excess Burst Size): this value defines the extra amount of contiguous packets that occasion-
ally a customer is allowed to send, in condition of no congestion
5.6.4.1 Metering
The bandwidth profile rates are enforced through a meter algorithm which is commonly implemented as a
token bucket algorithm. The MEF has defined a two rate three color marker (trTCM) algorithm which marks
packets based on two rates and two burst sizes, guaranteeing only the transmission of the smaller one,
and implemented via two token buckets.
Basing on the ingress filtering policies, it is possible to assign different bandwidth profiles (i.e. CIR/EIR and
CBS/EBS profiles) to the incoming Ethernet services, defining specific CIR/EIR parameters basing on:
• the specific operator (e.g. in case the microwave network is shared between two or more operators)
• the destination terminal (e.g. each NodeB can have a specific CIR/EIR profile).
The bandwidth profile classifies the service frames into 3 "colors", each denoting a certain compliance lev-
el:
MN.00329.E - 010 51
• yellow – Frames exceeding the CIR/CBS but are within the EIR/EBS. These frames are delivered as
"best effort". The equipment may drop some or all of these frames based on congestion conditions
in the network (available yellow tokens)
• red – Frames not conforming to the bandwidth profile are dropped, either because the rate exceeds
the sum of CIR and EIR or because there are insufficient yellow tokens to admit a frame that is
within EIR/EBS
SIAE switch is color blind: the packets are considered green upon entering the metering process and are
marked as yellow or red if the traffic class exceeds the correspondent bandwidth limits.
• red packets (i.e. the ones exceeding the CIR+EIR rate) are automatically discarded. In other words,
the rate obtained with the sum of CIR + EIR is the maximum rate allowed to be transmitted
Notes: the bandwidth profile parameters are defined in kbps and they do not consider changes of BW due
to ACM.
The switch allows to define a meter and to apply it to a class through the definition of a Policy-map, match-
ing a single class with a single meter.
The metering session establishes the behaviour for green, yellow and red frames.
Actions over yellow frames (exceed-action) or red frames (violate-action) can be:
• for yellow frames can optionally change the PCP. In Customer bridge it modifies C-PCP, in Provider
Bridge (edge/core) it modifies S-PCP. This commands is optional and acts after the traffic is queued
and scheduled, that means original PCP is used to schedule incoming traffic
• discards the red frames. This command is not optional and must be specified.
Congestion Avoidance methods permit to discard some frames before congestion occurs.
The dropping policy depends also on the type of traffic and it can have different effects on the network.
The following dropping policies can be adopted:
• Tail: when the queue is 100% full, all the arriving packets are dropped (default configuration)
• Red (Random Early Discard): before the queue is full some incoming packets are dropped randomly,
regardless if the frames are marked yellow or green. An example of RED curve is shown in Figure
X5.
- per each queue a dropping curve is defined by specifying the following “RED” parameters:
- minimum queue threshold (Smin)
- maximum queue threshold (Smax)
- max probability (Pmax)
- the arriving packet is directly queued only if the average queue size is < Smin
- depending on the packet drop probability (Pmax) the packet is either dropped or queued if the
average queue size is between Smin and Smax
- the packet is automatically dropped if the average queue size is > Smax
• WRED (Weighted Random Early Discard): Two Red curves are used, one for green traffic and one
for yellow (two groups of Smin,Smax and Pmax are used).
For each kind of traffic (identified by its drop profile) different dropping parameters can then be defined:
52 MN.00329.E - 010
In case of WRED congestion template, the equipment OS can manage up to 4 different traffic drop profiles
for template: green/yellow for TCP and green/yellow for not-TCP traffic; red frames are automatically
dropped by the Policer, so no thresholds are defined:
• min-threshold: min average threshold for the random detect algorithm (in byte 1-13107200)
• max-threshold: max average threshold for the random detect algorithm (in byte 1-13107200)
• gain: exponential weight for determining the average queue size (1-15)
• drop-threshold-type byte: defines the working mode in byte for min and max threshold.
In general, congestion avoidance behavior can be modified for each output queues of each interface. The
same queue template (identified by a numeric index) can be applied to more queues on more than one
interfaces.
At least 8 queues per port are present and each queue is associated to a priority value.
There is the possibility to configure the queue parameters through ad hoc configurations, available in WEB
LCT interface. Different type of queue settings can be selected and activated, with a consequent restart
of the machine.
This configuration is then applied to all the ports (IF and LAN interfaces), with the only difference between
line ports and radio ports that can have different configurations.
The following are the available type of queue configurations with the values of the related parameters:
MN.00329.E - 010 53
• full dynamic memory see Tab.17
• priority based memory allocation (1 radio port and 2 radio port) see Tab.18 and Tab.19
• uniform memory allocation (1 radio port and 2 radio ports) see Tab.20 and Tab.21
54 MN.00329.E - 010
Radio ports reserved memory [Mbyte] 4
Once the priority is assigned, the traffic in the queues is then emptied by means of specific algorithms:
• Strict Priority: the highest priority queue is served until it is empty, then the next and so on
• D-WRR (Weighted Round Robin): serves a number of packets for each not empty queue, based on
byte and not on frames, according to its weight ? number = mean packet size * Wi / (W1 + W2 +
... + Wn) A weight from 1 to 127 can be set
Note: D-WRR scheduler doesn’t care of queue priority to define their weight. It means that high pri-
ority queue can have less weight than a low priority queue
• Mixed strict priority & D-WRR: user can select which curves are to be served as Strict Priority or
WFQ/D-WRR. Once a mixed strict-priority + D-WRR scheduler is applied to an interface, traffic of
its highest queue in strict-priority is served before than the other queues in D-WRR, according to
their weight. To configure a mixed scheduler, a D-WRR scheduler must be created; then define
queues in strict priority (served before) assigning weight 0, while for the other queues in D-WRR
assign a weight from 1 to 127.
MN.00329.E - 010 55
5.6.8 Egress Shaping
This feature manages output shaping for constant and bursting traffic out of a port, limiting the egress
throughput defining a rate limiter on it.
Differently from the input filtering policy, the packets are not discarded when the egress rate is reached,
but buffered and released with the selected output rate. The shaping process retains excess packets in the
buffer of the port and then schedules the excess for later transmission over increments of time. The result
of traffic shaping is a smoothed packet output rate.
The shaper is configured with a shaper template, two different parameters can be configured to drive the
rate limiter:
• rate-value: defines the maximum output rate for constant traffic in kbit/s
Output rate limiter acts after the traffic is queued, so scheduling is done according to defined output band-
width. No rate-limiter is defined as a default value and the burst-value is an optional one: if it is not spec-
ified all bursting traffic is totally shaped at set rate-value, avoiding any output bursting traffic.
Additionally, the switch manages output shaping per each queue as well, by defining and applying a shap-
er.
Once a new shaper template is defined, two parameters can be configured for the rate limiter:
• CIR: defines the guaranteed reserved output bandwidth for the queue in kbit/s
• PIR: defines the exceed traffic available for the queue in kbit/s. PIR value includes also CIR value.
No parameters are specified for burst behaviour: in case of bursting traffic, it is totally shaped at CIR/PIR
value and no burst are transmitted out of the queue.
There are also some restrictions on the shaper template applications. For example one queue can match
a single shape-template, while the latter can be applied to more queues of more interfaces. A shaper tem-
plate can also be removed, assigning the shaper–template 0 to all the queues that used that own shaper.
Once the shaper isn’t applied to any queues, it can be removed from the switch. Besides, if a scheduler
parameter is changed on a queue, the shaper-template on that queue is removed.
Per each port it’s possible to define the packet format to egress. In particular the actions that can be con-
figured are:
Packets belonging to the same stream have up to 90% the same header (IP and MAC addresses, TAG
Ethernet, MPLS labels, etc.). Packet Header Compression allows eliminating locally the static fields of the
packet header, transmitting over the radio link proprietary labels (Context Label) in place of these long and
repetitive header fields and reconstructing them at the output of the remote terminal.
The set of "static" information of all the packets belonging to the same flow and retained in the compres-
sion/decompression module is defined as the context of the compression.
Hop-by-hop Header Compression has the basic idea to store at both ends of a radio link all the information
that are repeated identically in all the packets belonging to the same data flow and transmit only the var-
iable fields with good gains in throughput in case of long communication streams with a great number of
packets (for example, real-time communication).
56 MN.00329.E - 010
It is necessary to support a lot of streams at the same time in order to maximize the gain permitting to
have on the MW link a higher capacity reserved for payload, increasing the total throughput of the system.
In the switch a unique level Header Compression is set, in which it’s not necessary to specify what protocols
are supported but just if the compressor is enabled or disabled (completely bypassed).
The compression function will operate in the direction from LAN to Radio, while the decompression function
will operate in the opposite direction.
On the WEB LCT platform is available the contextual area of the Header Compression functionality for the
Ethernet packets in output from the LAN ports to the radio.
The lower part of the contextual area displays protocols and modes supported by the Parser of Header
Compression functionality as in Fig.36.
The parameter “Context Depth” indicates the total size of the Ethernet header the user wishes to compress.
The number of available contexts (i.e. the number of streams which can be managed at the same time on
the same radio link) changes inversely to the selected context depth:
• Always IPv4/IPv6
The compressor considers the most outer header of the packet as Ethernet.
- S-TAG with not standard Ethertype (0x9100, 0x9200, 0x9300 or a configurable Ethertype value)
- 802.1ah (MAC-in-MAC or PBB) is not supported
• MPLS
• Pseudo-Wire "MPLS-Like"
• Control Word
MN.00329.E - 010 57
• Ethernet-over-MPLS (EoMPLS)
5.6.11 PWE3
The transmission of TDM channels over Packed switched Networks (PSN) can be emulated by Pseudo-Wire
Emulation Edge to Edge (PWE3).
Using the PWE3 feature on AGS-20, we have to take into account of the following maximum capabilities:
- the VLAN ID used for PWE3 cannot be used for other services
• E1 Payload Size
• Clock Recovery Type (it can insert the fixed RTP header)
• Stack CES Type (depending on the transport type)
For instance with a Payload Size of 256 bytes and without insertion of RTP header, the bandwidth values
spent to carry out a 2Mbit/s are:
• 2320 Kbit/s for MEF8 (overhead of 30 bytes)
5.6.11.1 Encapsulation
PWE3 has an encapsulation process called "Structure Agnostic TDM over Packet" (SAToP, see RFC4553).
This process places a Pseudo-Wire Control Word in front of the TDM data, plus, if set, an optional fixed RTP
header for differential Clock Recovery.
The PW Control Word allows:
• differentiation between PSN and attachment circuit problems as causes for emulated service outage
For PWE3 purposes the equipment has to operate in Customer Bridge or in Provider Edge Bridge modalities.
A specific fixed port is used as PWE3 port, depending on the HW version of the Core Expansion Sub-Unit:
58 MN.00329.E - 010
• for ARI-2 and DRI-4 IDU versions ODU D
Note: once the PWE3 is enabled, the corresponding port is blocked and reserved for its transportation, i.e.
it cannot be used to forward normal traffic.
The PWE3 feature must be enabled under the related menu (see Figure 80) in the WEB LCT interface.
The PWE3 VLAN has to be created in the VLAN table, assigning at least the PWE3 port as member interface.
In the PWE3 menu, the user has to create the Bundle that carries the PWE3 channels using the following
parameters:
• destination MAC address: the PWE3 source MAC address of the last NE of the chain
• encapsulation: PSN type over which the PW is transported. Three types of PSN are supported:
- MPLS
- IP (IPv4-UDP or IPv6-UDP)
• C-VLAN tag.
Then, based on the selected type of encapsulation, different additional parameters has to be set:
• if IPv4-UDP is set fills in UDP destination port, destination IP address and source IP address in ver-
sion 4 syntax
• if IPv6-UDP is set fills in UDP destination port, destination IP address and source IP address in ver-
sion 6 syntax.
After the bundle is created, the user has to add the channels the bundle is going to carry; each channel
corresponds to a tributary E1.
To create the PWE3 point-to-point circuit the user has to keep in mind the following assumptions:
• Mef8 Bundle: source and destination have the same ECID
• MPLS Bundle: source and destination have the same MPLS inner label
• IPv4 – UDP Bundle: for each E1 in the bundle, a different Source Port has to be selected; mind that
the selected couples of UDP Source and Destination Ports must be the same between the source
and destination devices
• IPv6 – UDP Bundle: for each E1 in the bundle, a different Source Port has to be selected; mind that
the selected couples of UDP Source and Destination Ports must be the same between the source
and destination devices.
In case of a Provider Edge Bridge configuration of the switch two kind of port can be used as PWE3 port:
• Customer Edge Port: it is necessary to set an EVC with a specific S-VLAN tag on this port for the
transport of the PWE3 circuit, configure the bundle with a C-VLAN tag and create the mapping be-
tween this C-VLAN and the S-VLAN
• Customer Network Port: after the creation of the EVC with S-VLAN on the port, any C-VLAN can be
used to configure the bundle, as all the C-VLANs reaching this port will be carried with that EVC.
Then the configuration steps are the same as in the Customer Bridge case described in the previous par-
agraph.
MN.00329.E - 010 59
5.7 CONTROL PLANE
In this chapter are described all the AGS-20 features belonging to the Control Plane. Some of these fea-
tures are commonly deployed in Ethernet switches and routers for traffic control (e.g. RSTP, etc…), while
other features are microwave specific implementations that allow the interaction between the radio channel
and the AGS-20 embedded Ethernet switch (e.g. LLF, LACP, RSTP, etc…).
In the following paragraphs it is described the SIAE implementation of these features and some application
examples.
5.7.1 ELP
ELP (Ethernet Line Protection) is a proprietary feature that protects a LAN interface against cable failure
or accidental disconnection.
It allows connecting the unit to another network element by using two LAN interfaces, configuring one port
in active status and the other in standby status, realizing a protection between two Ethernet interfaces.
When the user enables the LAG, the system automatically enables the management of the ELP switch
among the ports. The switch operates in automatic mode, i.e. the equipment actuates the switch between
the two ports when an alarm LOS is received on the LAN currently in service.
This feature requires to enable and configure the protection between two LAN interfaces, nothing else.
ELP configuration is exactly the same of LACP aggregation, except for the indication that the bundle is a
LAG for protection with the tick of the ELP checkbox in the Port Channel Basic Settings window in LA Man-
ager of WEBLCT.
Two LAN ports must be added to the logical bundle in the New Aggregation window in LA Manager of WE-
BLCT.
Note: in Provider switch mode, the ELP can be implemented only among ports of Provider Network type
60 MN.00329.E - 010
• Layer 1 Aggregation available at IF radio ports for 2x(1+0) Single Pipe configuration
• Layer 2 Link Aggregation Control Protocol (LACP) available at LAN ports for nodal configurations
• Layer 2 Link Aggregation in manual configuration, a static LAG in which the LACP protocol is deac-
tivated.
In 2+0 Single Pipe configurations, AGS-20 is able to simultaneously manage two 1+0 radio links outgoing
from the two available IF interfaces. In case the two links are parallel (i.e. deployed between the same two
sites) the Ethernet capacity can be aggregated in order to double the capacity of the single 1+0 Ethernet
connection.
In this case the Link Aggregation mechanism is not based on MAC hashing, but on a more efficient Layer
1 distribution of the traffic over the two radio channels. The traffic received from the line interfaces, after
the L2 Ethernet switch processing, is fragmented and labeled with proprietary protocols a and recomposed
at remote side.
The fragments are sent over the air in order to balance the load between the two radio channels. The bal-
ancing mechanism is able to take into account also the down-switch due to ACM modulation on one radio
branch only.
The final result is that the traffic is balanced over the two radio channels on the basis of the available ca-
pacity and independently from any other packet characteristics (source or destination MAC address etc...).
Resiliency between the aggregated radio links is inherently provided by the balancing mechanisms (if one
radio channel becomes unavailable all the traffic will be sent on the other channel).
The maximum capacity that can be aggregated is relevant to two times the maximum channel available
on AGS-20. However, the additional fragment labeling (additional overhead) gives a lower capacity.
Depending on frame length, the lost percentage due to increased overhead is:
Note: in case the L1 LAG is enabled between the two IF interfaces (ODU A and ODU B) in the switch settings
just one interface is available and configurable, i.e. ODU A port.
5.7.2.2 LACP
LACP (Link Aggregation Control Protocol) allows aggregating multiple Ethernet parallel connections into a
single logical Ethernet connection. The main purpose of this protocol is to provide a single aggregated ca-
pacity that is the sum of the “n” parallel links capacities.
Link Aggregation (LAG) is implemented as a dynamic LAG: this kind of link aggregation consider a mutual
exchange of BPDUs frames between the two devices involved in the LAG mechanism, to communicate and
align each other on the active/standby links forming the logical bundle.
The result is that some individual Gigabit Ethernet links are bundled into a single link, aggregating multiple
device ports. This port group act as a single logical port for high-bandwidth connections between two net-
work devices.
So all the LACP links are bundled to provide an increased capacity, however, at the same time, they provide
traffic redundancy as well, in case one of the links fails: if a physical link within the group fails, the traffic
previously carried over the failed link is then transferred and spread on the remaining ones; when the link
is recovered, it is automatically re-included in the LAG group.
Besides, it is possible to create protected configuration with a bundle of N interfaces in which N-1 ports are
active and the remaining one is in standby. In this case when a failure happens on one cable, the standby
port becomes active, preserving the number of physical active cables forming the logical bundle. For set-
ting this configuration the minimum number of active ports has to be equal to 2 (N+1 with N≥2).
LACP Rules:
• the selected ports must have a homogeneous configuration, i.e. the same transmission speed, the
same transmission mode (Full-Duplex) and the same MTU.
MN.00329.E - 010 61
• hashing: all the packets carried by the trunk are assigned to each physical channel depending on
the values of different parameters:
- VLAN ID
- ethertype
On SIAE AGS-20 is also possible to configure a static LAG between two or more LAN interfaces. This kind
of LAG is a L2 aggregation that does not implement the LACP protocol, so there is not a mutual exchange
of BPDUs frames between the two devices involved in the LAG mechanism.
Besides, in case of one of the links involved in the bundle fails, it provides traffic redundancy balancing the
traffic load across all the active links.
This type of LAG can be created in the same way of LACP LAG, except for the mode of aggregation that
has to be set as “Manual” during the creation of the new aggregation.
Note: it is important that on the two devices involved in the link aggregation, the same mechanism has to
be configured, i.e. static or dynamic.
5.7.3 LLF
LLF (Link Loss Forwarding) is a feature that forces a local LAN in a LOS state in case of radio failure or
remote LAN failure. It consists in a controlled shout-down of the Ethernet link thanks to the propagation
of a Ethernet link failure condition.
The aim of this feature is to inform an external device (i.e. customer switch/router) about the radio link
failure. When the switch/router receives the LOS signal on the LAN interface connected to the AGS-20, it
can take the proper counter actions, for example switching the traffic to the backup path.
The LLF can be configured on each LAN interface (not on radio port) and the main applications are the
following:
In some cases, the radio link failure can be unidirectional, for example when the local equipment has an
Rx LOS but the remote receiver is OK (i.e. unidirectional radio failure due to a malfunction on the remote
transmitter). However, there could be the need to shut down the link in both directions even if there is only
a unidirectional link failure.
Using the bidirectional LLF feature in case of a fault of LAN or Radio in the local equipment, the latter can
notify this LLF status to the remote equipment through a telemetry LOS alarm. Then the remote equipment
shuts down the associated LAN ports so that the link failure is communicated in both directions.
62 MN.00329.E - 010
5.7.3.2 Parameters in Bidirectional LLF
• Alarm to Circuit: indicates the possibility to propagate the LOS of a LAN port or receive the LOS
from the local radio on the correspondent circuit, provided that this circuit has been created and
configured on the “Mapped circuit on current port selection” area (see below); it manages the uni-
directional LLF
• Delay Time: indicates the hysteresis value (in seconds) for the LLF functionality in reception. The
alarm received from the radio direction (IDU BRANCH... Demodulator Fail Alarm, RADIO... Link Id
Alarm) must persist for “delay time” seconds before the equipment disables the corresponding LAN
port. In the same way, if the LAN port is disabled by LLF functionality, the radio alarm must be
cleared on the radio for “delay time” seconds before the equipment enables the considered LAN port
• Protection Mode: this option take sense in case of Ethernet link aggregation in which the user has
anyway to create two circuits, one associated to each aggregated radio direction. The LLF is acti-
vated depending on the status of the aggregated links:
- disable: the failure of just one of the links triggers the LLF activation (logic OR between the ag-
gregated links)
- enable: the failure of both links triggers the LLF activation (logic AND between the aggregated
links).
In the “Mapped circuit on current port selection” area is possible to create several circuits associated to the
LAN port selected in the area above. As in Fig.40, the circuit is mainly identified by the following parame-
ters:
• link ID: from #1 to #4; it represent a specific radio interface (depending on HW version of the AGS-
20, with one or more available IF interfaces)
• LOS to Circuit: it indicates the possibility to propagate a LOS alarm of the local LAN port or local Rx
to the remote equipment
• LOS Insertion Mode: it indicates the possibility, if more ports belong to the same circuit, to propa-
gate a LOS alarm into the circuit toward the remote equipment in case just one port is in LOS con-
dition or all the ports of the circuit are in LOS condition
For the correct configuration of the bidirectional LLF functionality for a radio connection, local and remote
LANs have to be associated to the same circuit ID.
MN.00329.E - 010 63
Fig.40 – Select the circuit that manages the LLF protected LAN port
While STP can take 30 to 50 seconds to respond to a network topology change, RSTP (IEEE 802.1d-2004)
is typically able to respond to changes within 3 × Hello times (default: 3 times 2 seconds) or within a few
milliseconds of a physical link failure. For this reason RSTP has actually replaced the STP in the most mod-
ern Ethernet networks, adding new bridge port roles in order to speed convergence following a link failure:
• root - A forwarding port that is the best port to the root bridge
• designated - A forwarding port for every LAN segment
• alternate - An alternate path to the root bridge. This path is different than using the root port
• backup - A backup/redundant path to a segment where another bridge port is already connected
• disabled - Not strictly part of RSTP, a network administrator can manually disable a port.
The number of states a port can be in (RSTP switch port states) are three instead of STP's original five:
5.7.4.1 BPDU
All switches with RSTP enabled generate and process data messages called Bridge Protocol Data Units (BP-
DUs). The exchange of BPDUs allows the switches to identify redundant paths and, by using the Rapid
Spanning Tree algorithm, to ensure that there is no loop path in the network identifying and blocking re-
dundant links.
• RSTP enables BPDU messages among switches to agree upon the Root Bridge Election
• once the root bridge is elected, every switch manages one port to communicate with the root bridge.
Therefore Root Port Election takes place on every network switch.
• finally, Designated Port Election takes place in order to have only one active path towards every
network segment.
64 MN.00329.E - 010
5.7.4.2 Root Bridge election
Through the BPDU the switches compare Root Bridge ID and Sender Bridge ID (six byte MAC address head-
er and a two byte Bridge Priority header). The switch with the smallest Bridge Priority is automatically
elected as the Root Bridge. If Bridge Priority is the same on all switches then the switch with the smaller
MAC address is elected as the Root Bridge.
Once the Root Bridge is elected, every not-root switch has to select a root port with the best path towards
the Root Bridge. The Root Port is determined by the Root Path Cost field in each BPDU (four bytes) accord-
ing to this process:
• path cost is based on the port bandwidth: the higher the bandwidth, the lower the path cost across
the specific port
• path cost is added to the root path cost field of each received BPDU. Root switch has root path cost
of zero for all its ports
• on every not-root switch the port with the lowest resulting root path cost is finally elected as the
Root Port.
The final step is the election of one Designated Port on each network segment.
The election of the Designated Port is based on the Root Path Cost: the chosen port is that with the lowest
cost and if two or more ports have the same, the switch with the lower Sender Bridge ID wins and has the
segment Designated Port.
Any port which is not a Root Port or a Designated Port is an Alternate Port.
This port moves into the Blocking State, (it cannot receive nor transmit frames) ensuring that the network
is loop-free.
• priority: field for the Root Bridge election. The switch with the smallest Priority is elected Root
Bridge
• Max Age: it controls the maximum period before a bridge port saves its configuration BPDU infor-
mation. 20 seconds by default, tunable between 6 and 40 s
• Hello Time: it is the period between each BPDU sent on a port. 2 seconds (s) by default, tunable
between 1 and 10 s
• Forward Delay: it is the period spent in the listening and learning state. 15 sec by default, tunable
between 4 and 30 s. For example, when a bridge receives a BPDU with the “Topology Change” flag
bit set, it reduces its bridging-table aging time to “forward delay” seconds.
To complete the configuration of RSTP, these parameter in the “Port Settings” card of WEBLCT must be set:
• Port Role: automatic role of the port, configured by the protocol operation itself
MN.00329.E - 010 65
• Port Priority: port priority settable from 1 to 15, used to define the port status in case of equal path
cost
• RSTP Status: activation status (“Enable” or “Disable”) of the port within the protocol operation con-
text (not related to the switch basic operation)
• Path Cost: cost of the link outgoing from that port, used to define the port status (i.e. Root, Desig-
nated or Alternate).
• type of failure: for example a LAN disconnection is detected faster because it automatically gener-
ates a LOS alarm. For the same reason, in case of radio failure, it is recommended to enable the
LLF protocol
• RSTP configuration settings as Hello Time, Forward Delay and Max Age.
5.8 SYNCHRONIZATION
Different approaches can be done to carry the synch signal in existing networks:
• exploit TDM circuits if they are kept in the network while starting carrying Ethernet traffic (valid
when the network is deployed with hybrid native TDM/Eth approach)
• use Synchronous Ethernet, by synchronizing the Ethernet line CK to a reference one. In this way,
the Ethernet connections are converted to synchronized lines. In this case the precision of the CK
recovered in the peripheral site is guaranteed by the fact that the CK is transferred at physical level,
like in TDM networks
• rely on packet protocols to rebuild the CK in the peripheral nodes. The most popular protocol is IEEE
1588v2, which rely on timestamps sent over Ethernet frames. In this case the accuracy of the re-
built CK could be affected by the traffic conditions and could particularly suffer in case of too high
packet jitter or packet losses.
The use of physical layer techniques allows the best performances in terms of the frequency precision of
the recovered CK: this should always be the preferred solution for frequency synchronization transport.
The SETS identify the input and output types of interfaces by the following codes:
• TE, represents an Ethernet interface (LAN) used as input CK (TE SyncE A, TE SyncE B)
• T3, represents a 2MHz signal or a 2Mbit/s signal not carrying traffic as input interface
5.8.1 Sources
- 2MHz: in this configuration the port can be used to get the CK signal from a 2MHz sync source
- 2 Mbit/s: this is an E1 signal not carrying traffic that can be used to get the CK from a G.704
framed E1, without transmitting it on air and so without wasting radio capacity. The correspond-
ent E1 frame transmitted by the interface is a framed E1 (according to ITU-T G.704) with AIS
• T2 E1, One of the E1 Tributaries of the E1 SCSI interface (max of 16 E1s depending on hardware
version)
66 MN.00329.E - 010
• Radio Interface (ODU/LANx): It is very important to keep in mind that all the radio interfaces are
seen as independent sources at the receiver SETS; this means that in a 1+1 protection configuration
both radio channel can be a sync source, if enabled by the user. When SSM is enabled, the main
and protection channels have the same clock quality at the receiver; so the choice of the clock
source by the SETS is performed basing on the priority
• GbE Interface (with SyncE): two of the available LAN ports could be chosen as the sources of syn-
chronization, selecting them under “TE SyncE A” and “TE SyncE B” entry list in the T0 TAB of the
equipment WEBLCT. In order to receive the synch. signal (and SSM if enabled) the GbE interface
has to be set as “Slave”
5.8.2 Output
Once the SIAE equipment is synchronized, the clock signal has to be passed toward external equipment
through different interfaces:
• E1: In order to modify the output timing of the E1 stream the user has to enable the “Retiming”
option for each E1 If the “Retiming” option is not enable, the E1s pass through the MW without any
synch. modification remaining with its original CK
• T3-SYNC: this interface is configurable as 2 Mbit/s or 2 MHz channel, always locked to the SETS
- 2MHz: in this configuration the port can be used to provide a 2MHz CK to an external equipment
• GbE Interfaces: the Tx CK of the GbE lines is locked to the SETS. When the GbE interfaces are elec-
trical interfaces, the port role must be set as “Master”. Once the synchronization is enabled, all the
LAN interfaces are locked onto the SETS and the synchronization signal is provided onto all the LAN
interfaces.
5.8.3 Priority
Each synch source can be enable or disable, being available or not in the selection process. If no sync
source is enabled, the clock of the system will work as “free running”, locked to the internal oscillator and
marked with a SEC quality level.
WARNING: if all the sources are disabled, the synchronization management is disabled.
A priority method is used to define the preferred source: nine priority levels are assigned to each synchro-
nization source and are used in case two or more sources have the same quality (with SSM protocol ena-
bled).
Priority 1 corresponds to the maximum value, while the priority 9 corresponds to the minimum value.
The unit changes synch source if one of the following events occur:
• the synch source is not physically available (the cable is not stuck in the interface port or the re-
ceived signal is under the receiver minimum threshold)
• the difference between the source frequency and the internal reference source (25MHz STRATUM
3e) is greater than ± 7 ppm.
Once one of these events occurs, the IDU will switch the source of synchronization to the second according
with priority list. If also the second source listed will be unplugged or out of maximum range then the IDU
will switch to the third source and so on.
WARNING: if two sources have the same quality and priority, the SETS will choose in a random way.
MN.00329.E - 010 67
5.8.4 Quality and SSM
The unit supports the SSM protocol to forward the quality of the synchronization sources and to manage
their classification (ITU-T G.781 and ITU-T G.8264). As the SSM transmits the quality of the transmitting
source, it represents a unidirectional channel between tx CK and rx CK.
According to SSM, the classification of clock quality, from better to worse, is:
• PRC: Primary Reference Clock – Best quality clock reachable (Cesium Clock)
• DNU: Do not Use – This signal informs the receiver to do not use this clock.
• QL-disabled mode: the sync source selection is based on the sequence enabling / alarm / priority.
No SSM messages are transmitted and possible SSM messages received are ignored. Furthermore,
lack of these messages will not be considered as a fault condition.
• QL-enabled mode: the sync source selection is performed among the available sources with a qual-
ity level higher than DNU, basing on the classification previously described; a received signal with
DNU quality is not be used. To protect against possible failures, the lack of SSM messages from a
sync source for more than a 5 second period is detected as a failure condition and that source passes
in a wait-to-restore period. After an event of SSM message, this source quality state is restored with
the new quality level contained in the message and the timer is restored.
In addition is possible to force the quality of an enabled source; in this case possible SSM messages from
this source are ignored, a lack of messages is not considered as a failure condition and no SSM messages
are sent from that port.
Unless the user forces the input/output CK quality, the output quality is the same as the input quality.
With SSM enabled, the unit selects the synch source with the following criteria:
• among same quality sources, the one with the highest priority is selected
• in any case, if a DNU quality is received on the highest priority source, this latter is discarded and
the equipment selects an alternative source.
The quality of the synchronism has to be enabled for each unit and can be transported on the following
interfaces:
• forced switch: the operator forces the SETS to lock to a predetermined source (even if the cable is
unplugged or the sync signal experiences a poor quality)
• preferential switch: the selected source is preferential respect the other enabled. Without alarms or
forced sources, it is used as the generator of synchronism. In any case the quality is the main pa-
rameter of choice.
With SSM enabled, the unit selects a synch source with the quality available. If the 2 MHz signal is the only
source available, the unit uses the internal clock instead of a source without quality.
68 MN.00329.E - 010
This can be avoided by overwriting the Rx quality in input of the 2 MHz cable. Same approach can be used
in case a source of synchronization does not support SSM.
First of all, the SSM can be enabled on all the LAN interfaces.
When the SSM is not active, in order to properly propagate the clock signal through the Ethernet electrical
interface, it is necessary to set correctly the master/slave option as the SyncE transmission has to be uni-
directional, while it’s not needed for the optical interface, as the transmission is anyway unidirectional on
each fiber.
In this case, and in general for all the LAN interfaces not selected as sync sources in “T0” TAB, the role of
the GbE ports has to be set as Master/Slave (sync direction manually selected) Auto (sync direction auto-
negotiated).
This because the master interface transmits the clock to the slave interface and, in case the direction of
propagation of the clock has to be changed (line failure, insufficient quality, etc.), the master/slave assign-
ment has to be re-negotiated with a consequent loss of traffic. In fact, this re-negotiation implies an inter-
ruption of the traffic indicatively from 2.5 to 3 seconds.
This is not necessary for the two possible LAN interfaces selected as TE Sync A and B: in fact, in this case,
the role is automatically set as “Auto”, or as “Slave” if the T0 signal is locked to this source.
All the Ethernet interfaces are locked on the SETS, regardless which LAN interfaces are set as sources of
synchronization. Nevertheless the “Overwrite RX Quality” and “Overwrite TX Quality” can be applied only
on the LAN interfaces used as sources of synchronization.
The Service Layer OAM fully monitors a customer End-to-End Ethernet Service, i.e. CFM (Connectivity Fault
Management) useful for detecting, isolating and reporting connectivity faults.
Administration and Maintenance (OAM) standards are designed to simplify the management of Carrier
Ethernet services with end-to-end service visibility, fault isolation, reporting and continuous performance
monitoring. As specified in the IEEE 802.1ag standard, these capabilities enable providers to manage
Ethernet services regardless of the network path, topology, operators or network layer that carries the traf-
fic between service endpoints.
5.9.1 OAM
Through CLI interface, OAM configuration is available on all Ethernet interfaces, regardless of their physical
port connection.
• Maintenance Domains (MD): these specify the Domains of operators, customers and service pro-
viders. Eight MEG Levels are and roles are:
- Customer Domain is the higher and includes both ends of the Ethernet service (three MEG Lev-
els: 7, 6, and 5)
- Service Provider Domains should have a MD lower than the Customer since include the whole
network except the End Users Provider role (two MEG Levels: 4 and 3)
- Operator Domains are lower than Service Provider Domains since just a part of the network is
included (three MEG Levels: 2, 1, and 0).
MN.00329.E - 010 69
SIAE unit: up to 32 Maintenance Domains can be specified on a single device and each MD has to
be identified by a different VLAN. At each end of a Maintenance Domain two MEPs (Maintenance End
Point) will be specified. The MEPs are “markers” that define the end of a domain and are in charge
of originating OAM frames. In a domain also MIPs (Maintenance Intermediate Points) can be spec-
ified. The MIPs are passive check-points.
• Maintenance Association (MA): association which correlates the VLAN to the MD with MEPs and MIPs
When a specified traffic needs to be monitored, it is necessary to associate the VLAN to a Domain
and so to the corresponding MEPs or MIPs. This is done through the Maintenance Association. Before
creating the MA, the VLAN, either S-VLAN or C-VLAN, has to be specified in the VLAN Table. On each
SIAE unit it is possible to set up to 32 different MA. A MA is associated with more than one VLAN
but different MAs cannot share one VLAN in a single Maintenance Domain
• MEPs (Maintenance End Points): MEPs monitor the status of the Ethernet service provided. MEPs
mark the end point of a MD and are capable of initiating and terminating OAM frames for fault man-
agement and performance monitoring. MEPs forwards OAM messages coming from higher domains
and stops OAM messages from lower domains
• MIPs (Maintenance Intermediate Points). MIPs are passive intermediate check-points that answer
to polling coming from MEPs. A MIP does not initiate OAM frames.
SIAE unit: each Ethernet interface can have a MEP. Once chosen the interface, the direction of the MEP has
to be specified:
• MEP Inward, entering the switch. With MEP Inward configured, the OAM PDUs are sent from the
interface toward the inside of the equipment and will follow the VLAN table
• MEP Outward, outgoing from the switch. With MEP Outward, the OAM PDUs are sent from the in-
terface in the direction outside the equipment (OAM PDUs are sent thorough the cable toward next
equipment)
• MEP ID: MEPs belonging to same MA must have different MEP IDs. In order to configure a MIP, the
MA has to be enabled on the equipment. Up to 32 MIPs or MEPs can be configured on each equip-
ment, as per SIAE recommendation.
Note: up to 1 MEP can be installed on the same port at the same level, either MEP Inward or not. This
means that 2 domains at the same level cannot exist on the same port.
Some protocols belonging to the CFM implemented in SIAE equipment, as listed here:
• Continuity Check Protocol: each MEP transmit periodically a CC message with its ID and MA and
tracks the CCMs received from other MEPs. Pulse period: 1s, 10s, 1min, 10min.
• Loopback Protocol: it is an “answer request” to another MEP/MIP or multicast. On LBM reception,
MEPs/MIPs validate the received LBM and send back a Loopback Reply to the sender. This is done
to check the status of the connection between sender and destination.
SIAE units: the number of Loopback Messages is adjustable from 1 to 8192 consecutive Loopbacks.
• Remote MEP: Each MEP can check the presence of other MEPs in the same MA through means of
MEP IDs and MAC address of the interface correspondent to the MEP itself. The LBM can be used for
the following applications:
- to verify bi-directional connectivity of a MEP with a MIP or a peer MEP (both unicast and multicast
LBM)
• errored ccm received: the MEP is receiving invalid CCMs (RMEP ID unattended, CCM interval differ-
ent)
• remote CCM defect: the MEP is not receiving CCMs from some other MEP in its Remote MEP list
• mac status defect: the last CCM received from remote MEP indicated that the transmitting MEP’s
associated MAC is reporting an error status via the Port Status TLV
• remote defect indication: the last CCM received from remote MEP contains a RDI.
70 MN.00329.E - 010
The trap messages of the first four alarms are active by default option, while the trap of the last alarm has
to be activated from CLI interface.
5.9.2 RMON
RMON (Remote Monitoring) is a standard whose function is monitoring the activity of a LAN network.
SIAE equipment support RMONv1, first MIB, as defined in RFC2819. This MIB contains real-time LAN sta-
tistics e.g. utilization, collisions and CRC errors. These counters are managed locally into the radio equip-
ment and are defined independently for each port of the device (both LAN and Radio interfaces). SIAE NMS
systems collect periodically this data and store it into the network database.
• RMON - Ethernet Port Statistics: these data counters are collected in real time by the Network
Equipment. These data are stored in the network equipment itself
• RMON - History: collection of data counters from the network equipment. After a periodical polling
to the network element, the NMS collects all the data and these data are seen as the RMON History.
RMON statistics are represented by counters collected for each port of the device, stored in the equipment.
This mechanism of monitoring requires the creation of a Ethernet Statistic in the “Settings” area of RMON
on WEB LCT, to enable the collection of the available metrics on the interface or service. This collection can
be viewed as a punctual measure in the “Ethernet Statistics” area.
Based on the Ethernet statistics, one or more Ethernet History can be then created, to collect a number of
samples configurable by the user and store them in the equipment memory.
The following are the important settings for the Ethernet history configuration:
• Buckets Requested: number of sampling events registered by the RMON on the equipment, based
on the “Interval” and “Data Source” configured by the user; when the end of the buckets is reached
the process restarts cyclically, replacing the first measured entry with the new ones.
• Persistence: enable the possibility to export the registered measures on a file through an FTP client;
the file is created when the user make the request to the equipment.
• Interval (s): data collection has a configurable sampling period:
- 60, 300, 600, 900, 1800, 3600 s, (persistence of the results is enabled).
• if the sampling interval is equal or greater than 300 s two files will be created:
- one with a number of samples equal to the bucket size and related to the previous day
- one with a number of samples equal to the bucket size and related to the current day
• if the sampling interval is less than 300 s one single file will be created, with a number of measures
equal to the double of the bucket size, independently from when the measures have been recorded.
• DropEvents: total number of frames received by the port dropped by the output interface due to
lack of resources. For example, LAN 1 “Rx Dropped Events” measures the frames received by LAN
1 that have NOT been transmitted on the output interface (e.g. Radio port) due to lack of resources
• Octets Rx: total number of octets of data (including those in bad packets) received by the interface
MN.00329.E - 010 71
• Pkts Rx: total number of packets (including bad packets, broadcast packets, and multicast packets)
received
• BroadcastPkts Rx: total number of good received packets that were directed to the broadcast ad-
dress
• MulticastPkts Rx: total number of good received packets that were directed to a multicast address
• UndersizePkts Rx: total number of packets received that were less than 64 octets long (excluding
framing bits, but including FCS octets) and were otherwise well formed
• OversizePkts Rx: total number of packets received that were longer than 1518 octets (excluding
framing bits, but including FCS octets) and were otherwise well formed
• Fragments: total number of packets received that were less than 64 octets in length and had either
a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with
a not-integral number of octets (Alignment Error)
• CRC Align Errors Rx: total number of packets received that had a length between 64 and the Max
Packet Size configured on the equipment switch (in any case not exceeding 10240 bytes) with bad
Frame Check Sequence (FCS) and an integral number of octets (FCS Error) or a bad FCS with a not-
integral number of octets (Alignment Error)
• Pkts 64 Octets Rx: the total number of packets (including bad packets) received that were less than
64 octets in length (excluding framing bits but including FCS octets) (Not available for history col-
lection)
• Pkts xx to yy oct. Rx: the total number of packets (including bad packets) received that were be-
tween xx and yy octets in length (excluding framing bits but including FCS octets) (Not available
for history collection)
• Pkts ≥ 1024 Octets Rx: the total number of packets (including bad packets) received that were more
than 1024 octets in length (excluding framing bits but including FCS octets) (Not available for his-
tory collection).
All the counters described above are part of the RMON statistics and it is not possible to collect only a sub-
set of them. It is however possible to select on which equipment interface the RMON statistics are activat-
ed. This allows reducing the total amount of PM data, for example avoiding data collection from unused
LAN interfaces. This can be done on all LAN interfaces (regardless if electrical or optical) and on the radio
interface as well.
Note: up to 74 Ethernet Statistics and up to 74 Ethernet History can be created in total (10 based on port
and 64 based on service).
In addition to the Ethernet counters per Port, on AGS-20 equipment it is possible to monitor some Ethernet
Services with the following counters types:
• Port & VLAN, intended as the VLAN ID included in the related tag (C or S-tag)
• Port & Priority, i.e. frame priority imprinted on p-bits of the related tag (C or S-tag).
Also for services an Ethernet Service Statistics has to be created before enabling the Ethernet Service His-
tory.
The Service RMON counters allow the equipment to track the VLAN Service (VLAN Tag):
• related to VLAN History, no more than one probe can be created on the same VLAN
The Priority statistics are based on PCP field (p-bits) in the VLAN tag: a probe for each priority/queue can
be created.
Differently from RMON counters, Service and Priority counters can be activated only for the following var-
iables:
• octets Tx: total number of octets of data (including those in bad packets) transmitted
• octets Rx: total number of octets of data (including those in bad packets) received by the interface
72 MN.00329.E - 010
• pkts Rx: total number of packets (including bad packets, broadcast packets, and multicast packets)
received
• received discard pkts: total number of discarded packets at ingress in case of VLAN forbidden, policy
exceeded, MAC source deny (ACL)
• sent discard pkts: total number of discarded packets at egress in case of exceeded port egress rate,
output shaping, exceeded MTU
• received unicast pkts: the total number of received unicast packets (including bad packets)
• sent unicast pkts: the total number of sent unicast packets (including bad packets)
• received not unicast pkts: the total number of received not-unicast packets (including bad packets)
• sent not unicast pkts: the total number of sent not-unicast packets (including bad packets).
Note: up to 74 Ethernet Statistics and up to 74 Ethernet History can be created in total (10 based on port
and 64 based on service).
5.10 PROGRAMMABILITY
AGS-20 radio system is managed by a microprocessor that makes it totally programmable via software to
perform the following functions:
- link ID
- Tx frequency and power
• main management
- IP port configurable and supervisioning
- routing table
- permanent Tx Off
- performance monitoring (G.828, Rx PWR, Tx PWR, ACM Ethernet Statistic Rmon) with alarm
threshold
- S/N measure
- backup/restore configuration
- software update
MN.00329.E - 010 73
- SNTP alignment
- Tx transmitter OFF
- LAN loop
• Ethernet switch management and relevant functionalities
• E1 enabling
• STM1 enabling
• synchronization
• TDM traffic routing between IF ports and the local E1/STM-1 interfaces by means of an embedded
TDM cross-connection matrix (GAI0217-2, GAI0218-1, GAI0224-2 and GAI0226-1)
• TDM traffic routing among IDUs of the same group (called Node) by means of Nodal Bus managed
by cross-connection matrix (GAI0217-2, GAI0218-1, GAI0224-2 and GAI0226-1) 1.
5.10.1 Software
AGS-20 is provided with an embedded Web Server and can be locally/remotely controlled by a HTTP brows-
er running on PC (Firefox recommended): this application is called WebLCT. It is also available software
with additional features that allows the file transfer (Backup/Restore config. and firmware update):
• WLC (WebLCT console): a downloadable free software from the site www.siaemic.com after regis-
tration
• NMS5UX/LX that can manage a subnetwork of thousand SIAE network elements and nodal config-
uration.
The network management system (NMS5LX/UX) functionalities, WebLCT and the Console Line Interface
(CLI) are widely described in the separated relevant manual.
Depending on hardware and system version, the following AGS-20 versions are available:
74 MN.00329.E - 010
• AGS-20 QUAD ETH (SYV 1.2) GAI0222-2
• SD card expansion
In Fig.41 the basic version of AGS-20 is shown. All the other version have this set of interfaces beside of
a variety of ports towards SIAE ODUs.
48V „ª
LCT -+
URG 1PPS
NURG R M 5A
SW 250V ON
TEST SYNC Console
2 LAN 2 LAN 4 LAN 6
1 1 3 5 TOD ALARM
MN.00329.E - 010 75
• Ethernet connectivity compatible with SIAE Full-Outdoor (ALFOplus80, ALFOplus80HD, ALFOplus,
ALFOplus2, etc....)
48V „ª
ODU A LAN C LAN D LCT -+
URG 1PPS
NURG R M 5A
SW 250V ON
TEST 4 6 SYNC Console
2 LAN 2 LAN LAN
1 1 3 5 TOD ALARM
In AGS-20 Single IF/16E1 (see Fig.43) the following functionalities are available:
48V „ª
ODU A LAN C LAN D LCT -+
URG 1PPS
NURG R M 5A
SW 250V ON
TEST 4 6 SYNC Console
Trib. 1-8 Trib. 9-16 2 LAN 2 LAN LAN
1 1 3 5 TOD ALARM
76 MN.00329.E - 010
5.11.5 AGS-20 Dual IF/16E1
In AGS-20 Dual IF/16E1 (see Fig.45) the following functionalities are available:
In AGS-20 Quad Eth (see Fig.46) the following functionalities are available:
• Ethernet connectivity compatible with SIAE Full-Outdoor (ALFOplus80, ALFOplus80HD, ALFOplus,
ALFOplus2, etc....)
• 2x COMBO (1Gbps electrical @ RJ45 or 1Gbps optical @SFP) with PoE functionalities
• 2x Optical (1Gbps or 2.5Gbps optical @ SFP)
In AGS-20 Quad Eth/16E1 (see Fig.47) the following functionalities are available:
• 2x COMBO (1Gbps electrical @RJ45 or 1Gbps optical @SFP) with PoE functionalities
MN.00329.E - 010 77
POE POE LAN C LAN D
In AGS-20 PP Single IF/16E1 (see Fig.48) the following functionalities are available:
In AGS-20 Dual IF/16E1 + 2STM1 + Nodal (see Fig.49) the following functionalities are available:
• TDM cross connect matrix for TDM routing line and radio side
• 2xNodal Bus (NBUS1 and NBUS2) for TDM routing between adjacent IDUs 2
• up to 32 PWE3 services.
78 MN.00329.E - 010
Fig.49 - AGS-20 Dual IF/16E1 + 2STM1 + Nodal (GAI0217-2)
In AGS-20 PP Single IF/16E1 + 2STM1 + Nodal (see Fig.50) the following functionalities are available:
• up to 32 PWE3 services.
In AGS-20 Quad Eth/16E1 + 2xSTM1 + Nodal (see Fig.51) the following functionalities are available:
• 2xCOMBO (1Gbps electrical @RJ45 or 1Gbps optical @SFP) with PoE functionalities
• TDM cross connect matrix for TDM routing line and radio side
• 16xE1 (@2xSCSI connectors) to be managed as native TDM or PWE3
• up to 32 PWE3 services.
MN.00329.E - 010 79
Fig.51 - AGS-20 Quad Eth/16E1 + 2STM1 + nodal (GAI0224-2)
In AGS-20 PP Single IF/16E1 + 2STM1 + Nodal (see Fig.52) the following functionalities are available:
• TDM cross connect matrix for TDM routing line and radio side
• up to 32 PWE3 services.
80 MN.00329.E - 010
5.11.14 AGS-20 Quad IF/16E1
In AGS-20 Quad IF/16E1 (see Fig.54) the following functionalities are available:
• TDM cross connect matrix for TDM routing line and radio side
• double power connector.
In AGS-20 Quad IF/16E1 + 2STM1 + Nodal (see Fig.55) the following functionalities are available:
• radio interface protection and L1 aggregation
• TDM cross connect matrix for TDM routing line and radio side
• 2xSTM1 (STM1-1 and STM1-2)
• 2xNodal Bus (NBUS1 and NBUS2) for TDM routing between adjacent IDUs 2
The following ODUs can be connected to AGS-20 by means of ARI interface (IF interface):
• ASN
• ASNK.
MN.00329.E - 010 81
5.13 SUPPORTED FULL ODUS
The following Full ODUs can be connected to AGS-20 by means of DRI interface (Ethernet interface):
• ALFOplus
• ALFOplus80HD
• ALFOplus2.
82 MN.00329.E - 010
6 TECHNICAL SPECIFICATIONS
In the following paragraphs are listed the electrical characteristics of all the. interfaces present in the AGS-
20 front panel. Connector pinout is reported in Section 3. INSTALLATION
• E1
• STM-1 3
Input side
Output side
MN.00329.E - 010 83
- Bit rate 2048 kbit/s ±50 ppm
AGS-20 IDU provides access to up to 16E1 tributaries organized on two 50-pin SCSI connectors and comply
with the rec. ITU-T G.703. Galvanic isolation is provided by means of transformers.
The selection between balanced and unbalanced interfaces with 120 Ohm or 75 Ohm impedance is carried
out by appropriate wiring of the cable according to pinout table.
Input side
Output side
4
6.1.1.3 STM1 optical
The STM1 interface can be specialised for different applications, by simply equipping the STM1 interface
with the appropriate pluggable optical or electrical transceiver. Optical interface has LC connectors. Electric
interface has 1.0/2.3 connectors. The characteristics of all the possible optical interfaces are summarised
in Tab.23.
Minimum
Launched Operating Distance
Interface Ref. sensitivity Transceiver Fibre
power (dBm) wavelength (km)
(dBm)
I-1 ANSI -14 ... -20 -28 1263 - 1360 Laser MultiMode Up to 2
The LIM is provided with Automatic Laser Shutdown as prescribed by ITU-T G.664 Recommendation.
84 MN.00329.E - 010
6.1.1.4 Electrical Ethernet (Ports LAN1, LAN2, LAN3, LAN4)
Ports LAN1 and LAN2 are COMBO interfaces and can use electrical or optical interface (software configur-
able).
All the ports can be set UNI or NNI and used as DCN. By default LAN3 port is set as DCN.
Ports LAN1 and LAN2 are COMBO interfaces and can use electrical or optical interface (software configur-
able).
Operating
Interface Ref. Link budget Wavelength Fibre Distance
(nm)
ARI is an IF analog connection (single coaxial cable for both Tx and Rx) towards SIAE ODUs.
When more than one ARI interface is available, Physical Layer Aggregation of two (or more in future) Radio
Channels can be realized in order to set up a single radio Bundle.
MN.00329.E - 010 85
- Telemetry ODU -> IDU 5.5 MHz
Optical interfaces are connected through SFP pluggable transceiver with LC type connector. Ports can be
set UNI or NNI.
Optical and electrical interfaces can be selected through software. In GAI0222-2, GAI0223-2 an electrical
interface PoE is available (see paragraph 6.1.6 PoE - Power over Ethernet).
Optical interface
Electrical interface
6.1.2.1 LCT
86 MN.00329.E - 010
6.1.2.2 Alarm
6.1.2.3 Console
This is the user connection to be used for synchronization purpose related to dummy E1 or 2 MHz signals
(SYNC). Input signal can be use to synchronize AGS-20 to an external clock reference while output signal
can be used to synchronize an external equipment to a reference recovered by AGS-20.
Since both HDB3 (2Mbps) and sinusoidal (2MHz) signals can be managed by AGS-20 with the same con-
nector, operator must be able to indicate mode of operation.
1PPS (Pulse Per Second) interface is used for timing services required in access network.
On the front panel 4 LEDs are present. They summarize status and alarms, see Tab.26.
MN.00329.E - 010 87
Tab.26 - Front panel system LEDs
Link/Active indication is close to relevant connector for each electrical or optical Ethernet interface, see
Tab.27.
0 Blink/s = No link
1 Blink/s = 10 Mb/s
Speed Yellow Interface speed
2 Blink/s = 100 Mb/s
3 Blink/s = 1000 Mb/s
LAN A and LAN B ports in unit GAI0222-2 and GAI0223-2 have PoE functionalities.
PoE alarms can be recognized by means of a pair of LEDs, Red (Alarm) and Green (Power), close to port
data LEDs (see Tab.28).
On On Cable open
Off On PoE OK
For each radio channel the supported bandwidth and modulations are the following:
Bandwidth
88 MN.00329.E - 010
• ANSI: (future evaluation)
Modulation
• Modulation profiles: from 4QAM up to 2048QAM (2048QAM not available in XPIC configuration)
• Hitless switch from one profile to the adjacent, in upshift and in downshift
• No restriction in minimum and maximum modulation level selection for each radio channel
• High_Throughput
Rescue, 4SQAN, 4QAM, 16SQAM, 16QAM, 32QAM, 64QAM, 128QAM, 256QAM, 512QAM, 1024QAM
2048QAM
• High_Gain
Rescue, 4SQAM, 4QAM, 16SQAM, 16QAM 32QAM, 64QAM, 128QAM, 256QAM, 512SQAM,
1024SQAM
“Rescue” profile (4QAMs @ reference modulation power and no TDM traffic allocated) is used during TDM
traffic reconfiguration for avoiding permanent loss of remote terminal due to air frame incompatibility at
different TDM traffic allocation.
Ethernet throughput
Tab.29 - Net radio throughput in Mbit/s versus channel bandwidth for AGS-20 equipment
7 14 28 56
200.0 399.5
512QAM 46.5 97.5 a
(189.5) (378.0) a.
223.5
1024QAM 51.5 107.0 446.0
(213.0) a.
7 14 28 56
MN.00329.E - 010 89
4QAM - 19.5 41.0 82.0
197.0 393.0
512QAM - 97.0
(186.5) a. (367.0) a.
220.0
1024QAM - 106.0 439.0
(209.5) a.
2048QAM - - - -
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
Modulation: 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 due to the increase of the hop attenuation, a
microprocessor (μP), at the receiver side of the remote terminal 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 starts to work before ACM. The behaviour
of the system is always 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.
90 MN.00329.E - 010
6.1.5 Power supply, consumption and max current absorption
Power Supply (PS) interface is used to support DC powering only. Consumption and max current are (guar-
anteed values):
- Normal service voltage range extended voltage range -38.4 Vdc to -57.6 Vdc
- Fuse
PoE functionalities are available on RJ45 connector of LAN A and LAN B of the following AGS-20 versions:
PoE functionalities can be enabled at the same time on LAN A and LAN B.
Characteristics are:
MN.00329.E - 010 91
• max voltage available in output 55 Vdc
If LAN A and LAN B are connected to Full ODUs (ALFOplus80HD, ALFOplus, ....) and these are supplied via
separated/dedicated power cables, PoE functionalities on LAN A and LAN B must be turned off.
6.1.7.1 Dimensions
AGS-20 is a standard sub-rack unit compatible with standard ETSI N3 and 19” racks.
Sub-rack dimensions:
- Height 44mm (1RU)
6.1.7.2 Weight
92 MN.00329.E - 010
6.2 AVAILABLE ODUS AND FULL ODUS
6.2.1 ODUs
In Tab.30 are listed the ODUs that can be connected to ARI ports.
• ALFOplus
• ALFOplus80HD
• ALFOplus2
• one “N” type connector for IF cable interfacing IDU and ODU
• one “BNC” connector for connection to a multimeter with the purpose to measure the received field
strength
• one ground bolt.
The 1+1 configuration consists of two ODUs mechanically secured to a structure housing the hybrid circu-
lator or branching unit for the connection towards the antenna.
MN.00329.E - 010 93
ASN ODU
The ASN ODU is shown in Fig.56 (single ODU) and in Fig.57 (1+1 ODU with branching unit). Electrical and
mechanical characteristics are listed in a separate addendum relevant to ODU frequency.
ASNK ODU
The ASNK ODU is shown in Fig.57 (single ODU with F15 GHz) and in Fig.58 (single ODU with F15 GHz).
Electrical and mechanical characteristics are listed in a separate addendum relevant to ODU frequency.
6.3.1.2 Description
• cable interface
• power supply
• Tx section
• Rx section
The cable interface permits to interface the IF cable interconnecting IDU to ODU and viceversa.
It receives/transmits the following signals:
The 17.5 MHz and 5.5 MHz FSK modulated carriers, carry the telemetry channel. This latter consists of two
388 kbit/s streams one from IDU to ODU with the information to manage the ODU (RF power, RF frequen-
cy, capacity, etc...) while the other, from ODU to IDU, sends back to IDU measurements and alarms of the
ODU. The ODU management is made by a µP.
The battery voltage is dropped from the IF cable interface and then sent to a DC/DC converter to generate
three stabilized output voltages to be distributed to the ODU circuitry.
6.3.1.5 Tx section
The 330 MHz QAM modulated carrier from the cable interface (see chapter 6.3.1.3 IF cable interface) is
forwarded to a mixer passing through a cable equalizer for cable loss compensation up to 40 dB at 330
MHz. The mixer and the following bandpass filter give rise to a second IF Tx carrier the frequency of which
depends on the go/return frequency value. The mixer is of SHP type. All the IF and RF local oscillators are
P controlled. The IF carrier is converted to RF and then amplified making use of a MMIC circuit. The con-
version mixer is SSB type with side band selection.
94 MN.00329.E - 010
The power at the MMIC output can be manually attenuated by 20 dB, 1 dB step.
The automatic adjustment is performed making use of an ATPC (see paragraph ATPC operation for de-
tails). The regulated output power is kept constant against amplifier stage gain variation by a feedback
including the AGC.
Before reaching the antenna side the RF signal at the output of MMIC passes through the following circuits:
A particular setting of Tx and Rx RF oscillators allows to obtain a RF Loop, managed by Controller module.
The particular way used to perform the RF loop avoids the necessity to switch off the remote Transmitter.
ATPC operation
The ATPC regulates the RF output power of the local transmitter depending on the value of the RF level at
the remote terminal. This value has to be preset from the local terminal as threshold high and low. The
difference between the two thresholds must be equal or higher than 3 dB.
As soon as the received level crosses the preset threshold level low (see Fig.62) due to the increase of the
hop attenuation, a microP at the received side of the remote terminal sends back to the local terminal a
control to increase the transmitted power.
If the hop attenuation decreases and the threshold high is crossed then the control sent by the microP
causes the output power to decrease.
6.3.1.6 Rx section
The RF signal from the Rx passband filter is sent to a low noise amplifier that improves the receiver sen-
sitivity. The following down–converter translates the RF frequency to approximately 765 MHz. The conver-
sion mixer is SSB type. The sideband selection is given through a µP control.
A second down converter generates the 140 MHz IF carrier to be sent to the demodulator within the IDU.
The level of the IF carrier is kept constant to –5 dBm thank to the IF amplifier stages, AGC controlled,
distributed in the IF chain.
Between two amplifiers a passband filter assures the required selectivity to the receiver. The filter is SAW
type and the bandwidth depends on the transmitted capacity.
The two ODUs are coupled to the antenna side via a balanced or unbalanced hybrid in case of 1+1 hot
stand-by.
The two ODUs are coupled to the antenna side via a circulator in case of 1+1 frequency diversity.
1+1 Tx switching occurs in the 1+1 hot stand–by 1 antenna or 2 antennas versions as shown in Fig.60 and
Fig.61.
The transmitter switchover is controlled by Processor and the attenuation of the stand-by transmitter is
at least 50 dB.
MN.00329.E - 010 95
Reference tooth
O-ring
ODU side flange
ASN version
ASNK version (for frequency ≤ 15 GHz)
"N"
"BNC"
Ground bolt
96 MN.00329.E - 010
ASN version
Suncover (optional) ASNK version (for frequency ≤15 GHz)
MN.00329.E - 010 97
ODU 1+0
98 MN.00329.E - 010
PTx att.
control
Vdc
MN.00329.E - 010
to radio controller
0 to 30 dB (ODU ASNK)
to IF circuitry
0 to 20 dB (ODU ASN)
Vdc to RF circuitry
AGC
-48 V
x
N type 330
Cable MHz Cable IF Tx
interface equaliz. T
MMIC
140 LNA
MHz
variable 140
µP bandwidth MHz
(capacity Rx LO
depending)
AGC
µP
99
Tx side
SW control
Rx side
Antenna
side
Tx side
SW control
Rx side
Tx side
SW control
First
antenna
Rx side
Tx side
SW control
Second
antenna
Rx side
Local Remote
Tx Rx
Thresh High
PTx actuation PRx recording
Thresh Low level
μP μP
PTx control
Transmission
Rx Tx
of PTx control
Local PTx
dBm
PTx max.
30 dB (ODU ASNK)
20 dB (ODU ASN)
ATPC range
PTx min.
The equipment is a split mount (indoor-outdoor) radio link system operating in the frequency ranges 4, 6,
7, 8, 13, 15, 18, 23, 25, 28 and 38 GHz, for low, medium and high transport capacity (from 4 up to 622
Mbit/s), designed to establish LAN-LAN connections and PDH/SDH access. For the details related to the
actual used frequency band refer to the label on the equipment.
The system is provided with an integral antenna; however, in case its antenna is not used, it should be
connected to an antenna conforming to the requirements of ETSI EN 302 217-4-2 for the relevant frequen-
cy band.
• Baseband (indoor)
Warning: Class 2 radio equipment subject to Authorisation of use. The equipment can operate only at the
frequencies authorised by the relevant National Authority.
Warning: The deployment and use of this equipment shall be made in agreement with the national regu-
lation for the Protection from Exposure to Electromagnetic Field.
Warning: The symbol indicates that, within the European Union, the product is subject to separate
collection at the product end-of-life. Do not dispose of these products as unsorted municipal waste. For
more information, please contact the relevant supplier for verifying the procedure of correct disposal.
The equipment consists of IDU and ODU(s) or Full ODU(s) units and is mechanically made up of a wired
19” subrack (IDU) and a weather proof metallic container (ODU and Full ODUs). The two units are shipped
together in an appropriate cardboard box.
Installation of Full ODUs: everything concerns a Full ODU (mechanical installation and relevant antenna
aiming, cable towards the Full ODU, connectors of the Full ODU, grounding of the Full ODUs) is described
in the HW manual relevant that kind of Full ODU.
After unpacking, mechanical installation takes place followed by electrical connections as described in the
following paragraphs.
The installation phases of the whole system are described in the following paragraphs and it must be done
only by service person suitably trained.
7.3.1 IDU
On their sides the subracks making up the several IDU versions are provided with two holes for the M6
screws fastening the subracks to a rack or to a 19” mechanical structure. The front of the IDU mechanical
structure is provided with the holes at the sides. This permits to fasten the subrack to a 19” rack by means
of 4 M6 screws.
In case of installation of more IDUs (all the versions except the Quad IF), IDUs can be stacked.
In case of QUAD IF AGS-20 (GAI0219-1, GAI0220-1, GAI0221-1) a free air gap of at least 1/2 rack unit
must be left between adjacent units.
Warning: Sufficient air-cooling must be ensured. Do not cover the ventilation openings of the appliance box
that provide the necessary ventilation to ensure reliable operation and to prevent overheating.
The electrical wiring must be done using appropriate cables thus assuring the equipment responds to the
electromagnetic compatibility standards.
The cable terminates to flying connectors which have to be connected to the corresponding connectors on
the equipment front.
Position and pin–out of the equipment connectors are available in this section.
Tab.31 shows the characteristics of the cables to be used and the flying connector types.
a. Select the correct size and type of cable for any installation case according to specific
length.
b. Power cable operative temperature 60°C.
c. It is suggested the usage of ferrules with insulating collar (according to DIN 46228-4)
with cross section of 1.5 sq.mm.
In case of necessity of optical connectors, please use the optical plug-in modules supplied by SIAE. Ask
SIAE Microelettronica for different modules.
During the final installation, the IDU must be protected by a magneto-thermal switch (not supplied with
the equipment), whose characteristics must comply with the laws in force in one's country.
The disconnection from the supply mains is made disconnecting the connector P04184 from the IDU.
The typical magneto thermal switch has characteristics at least 48 Vdc @6A with overcurrent relay class
“C” or “K” tripping curve.
- Shielding effectiveness 90 dB
7.7.2 Connectors
With the 1/4” cable, the max length is 300m for all modulation profile.
With 1/8” cable, any length that respects max 24dB at 330 MHz and a Max total DC resistance of 4 Ohm.
RG8 or 1/4” cable on any coaxial cable that respect the previous electrical characteristics.
In a XPIC link, the difference between IF cable length of V polarization and IF cable length of H polarization
must be compliant with:
• in case of BW = 14 MHz 12 m
• in case of BW = 28 MHz 6 m
• in case of BW = 56 MHz 3 m.
Fig.63 and annexed legend show how to perform the grounding connections.
Indoor 3 4
3 4
ODU
unit
1 5
7 IDU 2
unit
(+) (-)
6
Station Local
ground ground
ground
rack
Legend
1. IDU grounding point, copper faston type. The cross section area of the cable used must be
4 sq.mm. The Faston is available on the IDU both sides.
2. ODU grounding M6 bolt copper faston type. The cross section area of the cable used must be 16
sq.mm (V60052)
3. IDU–ODU interconnection cable type Celflex CUH 1/4” or RG8 cable terminated with N–type male
connectors at both sides.
4. Grounding kit type Cabel Metal or similar to connect the shield of interconnection cable.
5. Matching cable (tail) terminated with SMA male and N female connectors.
6. Battery grounding point of IDU to be connected to earth by means of a cable with a section area
2.5 sq.mm. Length 10 m.
7. Grounding cords connected to a real earth internal of station. The cross section area of the cable
must be 16 sq.mm
• grounding kit
• a short tape (to define the part of the jacket to remove from the cable)
In order to install the grounding kit, follow the instructions supplied with the kit itself and position the kit
in the proper points along the IDU-ODU cable (position and number of the points can vary depending on
local rules and/or customer request).
After grounding kit installation, it is necessary to seal it. Please, use two kinds of tape in the following or-
der:
• apply the first (of two) layer of sealing tape overlapping the IDU-ODU cable jacket by 3 cm on each
ends. The layer must cover 3cm of cable before the grounding clamp, the clamp itself and 3 cm
after the clamp.
The grounding bolt (opposite to the grounding clamp of the kit) must remain without sealing.
Fig.64
In order to install the grounding kit, follow the instructions supplied with the kit itself and position the kit
in the proper points along the IDU-ODU cable (position and number of the points can vary depending on
local rules and/or customer request).
2. insert one end of the tin copper tube of 3 mm of diameter in the relevant hole over the plate copper
bar of the grounding kit
4. put the plate copper bar over the shield of the cable and tie firmly the plate to the cable using the
tin copper tube. When the tin copper tube is over, wedge its end inside a notch of the plate in order
to fix it
5. apply two layers of vinyl mastic self amalgamating waterproof tape overlapping the IDU-ODU cable
jacket by 3cm on each ends as in Fig.65. Every wrapping must overlap the previous.
6. Apply two layers of black PVC UV proof tape overlapping the waterproof tape layers as in Fig.65.
Every wrapping must overlap the previous.
The grounding bolt (opposite to the grounding clamp of the kit) must remain without sealing.
The front panel of the AGS-20 depends on the selected version. Available versions are shown in paragraph
5.11 AVAILABLE VERSIONS.
8.1 CONNECTORS
- Ethernet LANC and LAND optical SFP 1 Gbps or SFP 2.5 Gbps (proprietary)
- Ethernet optical
1000BaseSX/1000BaseLX SFP LC
- Trib 1-8, 75 Ohm and 120 Ohm E1 in/out 50 pin SCSI female
(Tab.33 for 75 Ohm and Tab.34 per 120 Ohm)
- Trib 9-16, 75 Ohm and 120 Ohm E1 in/out 50 pin SCSI female
(Tab.33 for 75 Ohm and Tab.34 per 120 Ohm)
E1, 75 Ohm and 120 Ohm interfaces are present in the same connector (with different pins).
5 It is available a security lock Z21196 for single connector and Z21197 for double connector.
Function
Pin RJ45
10/100BaseT 1000BaseT
4 n.c. BI_DD+
5 n.c. BI_DD-
7 n.c. BI_DC+
8 n.c. BI_DC-
Pin 75 Ohm
48 Ground A
50 Ground A
47 Ground A
45 Ground A
42 Ground A
43 Ground A
40 Ground A
39 Ground A
36 Ground B
37 Ground B
34 Ground B
33 Ground B
29 Ground B
31 Ground B
28 Ground B
26 Ground B
Note: Join pin 44 with ground A pins, join pin 32 with ground B pins.
25 1
.........................
.........................
50 26
44 Ground A
44 Ground A
44 Ground A
44 Ground A
44 Ground A
44 Ground A
44 Ground A
44 Ground A
32 Ground B
32 Ground B
32 Ground B
32 Ground B
32 Ground B
32 Ground B
32 Ground B
2 Tributary 8/16output
32 Ground B
25 1
.........................
.........................
50 26
1 Sync_out_120
2 Sync_out-com
3 GND
4 Sync_in_120
5 Sync_in-com
6 Sync_in_75
7 GND
8 Sync_out_75
4 GND
5 GND
7 ToD_N
8 ToD_P
3 TxD (Output)
4 GND
5 GND
6 RxD (Input)
1 Alarm User-In 0
2 Alarm User-In 1
3 GND
9.1 FOREWORD
The description concerns pole mounting of ODU, in 1+0 and 1+1 version, using following installation kits:
Differences regard the dimensions and the presence of the centring ring (see Fig.69):
Following installation kits are supplied with the equipment depending on different versions.
1+0 version
- pole support system plus antenna (already assembled) and pole fixing brackets
1+1 version
- pole support system plus antenna (already assembled) and pole fixing brackets
• N.2 17 mm spanner.
Warning: if screwing operation concerns more than one screw or bolt, tighten subsequently everyone and
its opposite, step by step.
1+0 version
1. antenna polarization
5. installation of ODU
6. antenna aiming
7. ODU grounding
1+1 version
1. antenna polarization
2. installation of the centring ring on the antenna
5. installation of hybrid
6. installation of ODUs
7. antenna aiming
8. ODU grounding.
Fig.69 – Set the antenna in such a position to operate on its rear side. Locate the four M3 Allen screws
around the antenna flange. Unscrew them (use 2.5 mm Allen wrench) and position the antenna flange ac-
cording on: horizontal wave guide –> vertical polarization, vertical wave guide –> horizontal polariza-
tion. Screw again the four Allen screws (torque = 1 Nm).
Fig.69 – Set the antenna in such a position to operate on its rear side. Locate the three holes around the
antenna flange. Mount the centring ring onto antenna flange and tight it with the 3 Allen screws M4 (use
3mm Allen wrench, torque 2 = Nm).
Fig.69 – Mount the support onto assembled structure (pole support system plus antenna) using the four
M8 Allen screws (use 6 mm Allen wrench, torque 18 = Nm). Two of the four screws, diagonally opposed,
must be mounted with the two bushes around.
Fig.69 – Mount the assembled structure on the pole using the two pole fixing brackets and the four M10
screws (use 17 mm spanner, torque = 13 Nm); the heads of the screws are inserted on the antenna side,
the four nuts and the springs between nut and brackets are inserted on bracket side.
Fig.70 – Apply seal and lubricant grease Dow Corning 4 on the O–ring by protecting fingers with gloves.
Fig.71 – Bring the ODU with the two hands and position the ODU handle at the bottom side. The handle
can assume the positions shown in the figure depending on the polarization. Position the ODU body near
the support and align the wave guide of the ODU to the Wave guide of the antenna: respect to the position
of wave guide alignment, turn the ODU body approx. 30° counter–clockwise into the support and search
for matching between reference tooth on the support (see Fig.72) and reference tooth on the ODU body.
Fig.73 – When alignment of the references teeth is achieved, turn the ODU body clockwise until rotation is
stopped. In figure are shown ODU final position for both polarizations.
Fig.72 – When ODU positioning is over, secure ODU body on the support by tightening bolts (use 13mm
spanner, torque = 6Nm).
Antenna aiming procedure for 1+0 version or 1+1 version is the same.
Horizontal aiming: ±5° operating on the 17 mm nut shown in Fig.74 with a 17 mm spanner, only after
having loosen the two 17 mm nut on the pivot.
Vertical aiming: ±20° operating on the 13 mm nut shown in Fig.74 with a 13 mm spanner, only after having
loosen the three 13 mm nut on the pole support.
Once optimum position is obtained, tighten firmly all the nuts previously loosen.
as shown in Fig.75.
In further page are explained all the mounting step not already discussed in paragraph “9.5 1+0
MOUNTING PROCEDURES”.
Fig.76 – The polarization disk must be always fixed on hybrid flange. Apply seal and lubricant grease Dow
Corning 4 on the O–rings by protecting fingers with gloves. Bring the polarization twist disk with the posi-
tion marker down. Insert the O–ring into polarization twist disk.
Vertical polarization: fix the twist disk on hybrid flange placing the marker of the disk towards V mark.
Horizontal polarization: fix the twist disk on hybrid flange placing the marker of the disk towards H mark.
In 13 GHz and 15 GHz ODUs the polarization disk is fixed to the hybrid flange by means of 3 screws as
shown in Fig.77.
Tighten progressively and alternatively the screws and the spring washer with following torque:
Fig.78 – Fix hybrid body to 1+0 support with four M8 bolts (use 13 mm spanner, torque = 18 Nm), tighten
progressively and alternatively the bolts.
Fig.70 – Apply seal and lubricant grease Dow Corning 4 to the O–ring by protecting fingers with gloves.
Fig.71 – Bring the ODU with the two hands and position the ODU handle at the bottom side. The handle
can assume the positions shown in the figure depending on the polarization. Position the ODU body near
the support and align the wave guide of the ODU to the wave guide of the hybrid: respect to the position
of wave guide alignment, turn the ODU body approx. 30° counter–clockwise and then insert the ODU body
into the support. For 1+1 system the handle of the ODU is always positioned on the right. The polarization
twist disk on the hybrid matches the antenna polarization.
Fig.79 – When alignment of the reference teeth is achieved, turn the ODU body clockwise until the rotation
stops. In figure are shown ODUs final position.
Fig.72 – When ODU positioning is over, secure ODU body on the support by tightening bolts (use 17 mm
spanner, torque = 6 Nm).
Warning: Internal codes (e.g. installation items, antennas, PCB) are here reported only as example. The
Manufacturer reserves the right to change them without any previous advice.
Four 13mm
screws
Centring ring
(not present in V32309)
1+0 support
Two bushes
O-ring
ODU wave guide
"N"
"BNC"
Vertical Horizontal
Fig.71 - Position of the ODU handle depending on the polarisation for 1+0. For 1+1 the polari-
sation is always horizontal. Handle at the right side.
1
5
4 4
1
2
3
1. 6 mm Allen screw
Vertical aiming:
13mm block screws
Pole support
1
2
3
4
5
ASN/ASNK version
1. Bolt
2. Spring washer
3. Flat washer
5. Flat washer
2
4
6
1. O–ring
2. Polarization twist disk
6. O–ring
7. Allen screws
8. Spring washer
Vertical polarization
ASN/ASNK version
10.1 FOREWORD
The installation onto the pole of the ODU with integrated dual polarization antenna concerns 2+0 ODU
(with/without XPIC) and purpose of this chapter is to describe how to install ODUs over an orthomode
transducer (OMT) to achieve a double polarization microwave link.
Dual polarization antenna, orthomode transducer and pole support assembly are supplied by different sup-
pliers.
Depending on supplier and antenna dimension the final assembled structure can vary.
An example in Fig.80.
• Pole support system with antenna and orthomode transducer (from various suppliers)
• 2 standard lock ODUs with O-rings and accessories for ground connection and with standard lock
flange.
• Pole support system with antenna and orthomode transducer (from various suppliers)
• 2 Fast lock ODUs with O-rings and accessories for ground connection and with fastlock flange
• 1x 3 mm Allen wrench
• 1x 6 mm Allen wrench
• 1x 13 mm spanner
• 2x 17 mm spanner
Warning: if screwing operation concerns more than one screw or bolt, tighten subsequently everyone and
its opposite, step by step.
Two installation procedures are available depending the ODU mounting flange.
1. Installation of the 2 centring rings on the two lateral flanges of the orthomode transducer
2. Installation over the pole of the assembled structure: antenna with orthomode and pole support
system
3. Installation of standard lock ODUs
4. Antenna aiming
5. ODU grounding
1. Installation of the 2 centring rings on the two lateral flanges of the orthomode transducer
3. Installation over the pole of the assembled structure: antenna with orthomode and pole support
system
5. Antenna aiming
6. ODU grounding
Two centring rings must be mounted over the two lateral flanges of the OMT (see Fig.81).
• Set the OMT in such a position to operate on its lateral side flange.
• Locate the three holes around the flange and mount the first centring ring onto this flange and
tight it with the 3 Allen screws M4 (use 3mm Allen wrench, torque 2 = Nm).
• Repeat the procedure on the flange on opposite side of the OMT in order to mount the second cen-
tring ring.
See the instructions included in the antenna box (instructions vary depending on antenna vendor).
Two ODUs must be mounted using four 25mm bolts for each one.
• Add lubricant paste, e.g. MOLYKOTE P-40, on threads of four 25mm M10 bolts (M10). The sliding
surfaces should be cleaned. The paste should then be applied with a suitable brush, rag or grease
gun. It should not be mixed with grease or oils. Chemical protective gloves should be used.
• Screw partially these four 25mm M10 bolts in the relevant four holes around the OMT lateral flange:
each bolt should be tightened to have the square head out of the hole of about 13-14mm (the thick-
ness of hook), use 15mm spanner
• Apply seal and lubricant grease DOW CORNING 4 to the O-ring, protecting hands with gloves, and
insert in the proper track on the ODU flange
• Position the ODU vertically near the four bolts on the OMT lateral flange and align the ODU to match
the polarization of the OMT flange itself.
• After the right position has been found, rotate 30° counter clockwise the ODU and approach the
ODU to the OMT flange in order to have the four slots of the Standard Lock cross between the four
bolts
• Rotate 30° clockwise the ODU to hook each slots on the relevant bolt
• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15mm spanner,
torque=46mm)
• Optional: sun cover kit - Insert the sun cover and tie one of its bottom holes to the ODU handle by
means of the black plastic strip included in the sun cover kit
• Now the ODU is ready to be connected to the IDU-ODU cable and to the grounding cable.
Repeat this procedure for the second ODU on the opposite side of the OMT.
For horizontal and vertical aiming see the instructions included in the antenna box (instructions vary de-
pending on antenna vendor). Remember to tighten firmly all the nuts previously loosen.
For polarization adjustment see the instructions included in the antenna box (instructions vary depending
on antenna vendor). Remember to tighten firmly all the nuts previously loosen.
as shown in Fig.75.
Two centring rings must be mounted over the two lateral flanges of the OMT (see Fig.81).
• Set the OMT in such a position to operate on its lateral side flange.
• Locate the three holes around the flange and mount the first centring ring onto this flange and
tight it with the 3 Allen screws M4 (use 3mm Allen wrench, torque 2 = Nm).
• Repeat the procedure on the flange on opposite side of the OMT in order to mount the second cen-
tring ring.
See Fig.82. The orientation of the ODU support is the one that allows the mounting of the support over the
OMT. The fast lock ODU can be mounted inserted inside the ODU support in two different orientations just
to match the OMT wave guide flange.
• Mount the support onto OMT lateral flange using the four M8 Allen screws (1 in Fig.82). Use 6 mm
Allen wrench, torque 18 = Nm.
• Two of the four screws, diagonally opposed, must be mounted with the two bushes (2 in Fig.82).
around
See the instructions included in the antenna box (instructions vary depending on antenna vendor).
• In each fast lock ODUs apply seal and lubricant grease DOW CORNING 4 on the groove of the O-
ring by protecting hands with gloves.
• Bring the ODU with the two hands and position the ODU handle at the bottom side.
• Position the ODU body near the support and align the wave guide of the ODU to the wave guide of
the OMT flange.
• Respect to the position of wave guide alignment, turn the ODU body approx. 30° counter-clockwise
into the support and search for matching between reference tooth (4 or 5 in Fig.82, point the one
that allows the two waveguides matching) on the support and reference tooth on the ODU body.
• When alignment of the references teeth is achieved, turn the ODU body clockwise until rotation is
stopped and secure ODU body on the support by tightening bolts (3 in Fig.82). Use 13mm spanner,
torque = 6Nm.
Repeat this procedure for the second ODU on the opposite side of the OMT.
For horizontal and vertical aiming see the instructions included in the antenna box (instructions vary de-
pending on antenna vendor). Remember to tighten firmly all the nuts previously loosen.
For polarization adjustment see the instructions included in the antenna box (instructions vary depending
on antenna vendor). Remember to tighten firmly all the nuts previously loosen.
as shown in Fig.75.
Centering ring
3
1
1
5
4 4
1
2
3
4. Reference point
5. Reference point
O-ring
ODU ASN/ASNK
Eyelet terminal
Grounding bolt
11.1 FOREWORD
The installation onto the pole of the ODU with integrated antenna concerns both 1+0 and 1+1 version.
Following installation kits are supplied with the equipment depending on different versions.
1+0 version
1+1 version
- pole support system plus antenna (already assembled) and pole fixing brackets
• N.1 13 mm spanner
• N.2 17 mm spanner.
Warning: if screwing operation concerns more than one screw or bolt, tighten subsequently everyone and
its opposite, step by step.
1+0 version
1. antenna polarization
2. installation of the centring ring on the antenna
6. antenna aiming
7. ODU grounding
1+1 version
1. antenna polarization
2. installation of the centring ring on the antenna
5. installation of hybrid
6. installation of ODUs
7. antenna aiming
8. ODU grounding.
Fig.69 – Set the antenna in such a position to operate on its rear side. Locate the four M3 Allen screws
around the antenna flange. Unscrew them (use 2.5 mm Allen wrench) and position the antenna flange ac-
cording on: horizontal wave guide –> vertical polarization, vertical wave guide –> horizontal polariza-
tion. Screw again the four Allen screws (torque = 1 Nm).
Fig.69 – Set the antenna in such a position to operate on its rear side. Locate the three holes around the
antenna flange. Mount the centring ring onto antenna flange and tight it with the 3 Allen screws M4 (use
3mm Allen wrench, torque 2 = Nm).
Fig.69 – Mount the support onto assembled structure (pole support system plus antenna) using the four
M8 Allen screws (use 6 mm Allen wrench, torque 18 = Nm). Two of the four screws, diagonally opposed,
must be mounted with the two bushes around.
Fig.69 – Mount the assembled structure on the pole using the two pole fixing brackets and the four M10
screws (use 17 mm spanner, torque = 13 Nm); the heads of the screws are inserted on the antenna side,
the four nuts and the springs between nut and brackets are inserted on bracket side.
Fig.70 – Apply seal and lubricant grease Dow Corning 4 on the O–ring by protecting fingers with gloves.
Fig.71 – Bring the ODU with the two hands and position the ODU handle at the bottom side. The handle
can assume the positions shown in the figure depending on the polarization. Position the ODU body near
the support and align the wave guide of the ODU to the Wave guide of the antenna: respect to the position
of wave guide alignment, turn the ODU body approx. 30° counter–clockwise into the support and search
for matching between reference tooth on the support (see Fig.72) and reference tooth on the ODU body.
Fig.73 – When alignment of the references teeth is achieved, turn the ODU body clockwise until rotation is
stopped. In figure are shown ODU final position for both polarizations.
Fig.72 – When ODU positioning is over, secure ODU body on the support by tightening bolts (use 13mm
spanner, torque = 6Nm).
Antenna aiming procedure for 1+0 version or 1+1 version is the same.
Horizontal aiming: ±5° operating on the 17 mm nut shown in Fig.74 with a 17 mm spanner, only after
having loosen the two 17 mm nut on the pivot.
Vertical aiming: ±20° operating on the 13 mm nut shown in Fig.74 with a 13 mm spanner, only after having
loosen the three 13 mm nut on the pole support.
Once optimum position is obtained, tighten firmly all the nuts previously loosen.
as shown in Fig.75.
In further page are explained all the mounting step not already discussed in paragraph “9.5 1+0
MOUNTING PROCEDURES”.
Fig.76 – The polarization disk must be always fixed on hybrid flange. Apply seal and lubricant grease Dow
Corning 4 on the O–rings by protecting fingers with gloves. Bring the polarization twist disk with the posi-
tion marker down. Insert the O–ring into polarization twist disk.
Vertical polarization: fix the twist disk on hybrid flange placing the marker of the disk towards V mark.
Horizontal polarization: fix the twist disk on hybrid flange placing the marker of the disk towards H mark.
In 13 GHz and 15 GHz ODUs the polarization disk is fixed to the hybrid flange by means of 3 screws as
shown in Fig.77.
Tighten progressively and alternatively the screws and the spring washer with following torque:
Fig.78 – Fix hybrid body to 1+0 support with four M8 bolts (use 13 mm spanner, torque = 18 Nm), tighten
progressively and alternatively the bolts.
Fig.70 – Apply seal and lubricant grease Dow Corning 4 to the O–ring by protecting fingers with gloves.
Fig.71 – Bring the ODU with the two hands and position the ODU handle at the bottom side. The handle
can assume the positions shown in the figure depending on the polarization. Position the ODU body near
the support and align the wave guide of the ODU to the wave guide of the hybrid: respect to the position
of wave guide alignment, turn the ODU body approx. 30° counter–clockwise and then insert the ODU body
into the support. For 1+1 system the handle of the ODU is always positioned on the right. The polarization
twist disk on the hybrid matches the antenna polarization.
Fig.79 – When alignment of the reference teeth is achieved, turn the ODU body clockwise until the rotation
stops. In figure are shown ODUs final position.
WARNING: Internal codes (e.g. installation items, antennas, PCB) are here reported only as example. The
Manufacturer reserves the right to change them without any previous advice.
Three 3 mm
Centering ring Allen screws
Antenna Four 13mm screws
1+0 support
O-ring
ODU wave guide
"N"
"BNC"
Vertical Horizontal
Fig.86 - Position of the ODU handle depending on the polarisation for 1+0. For 1+1 the polari-
sation is always horizontal. Handle at the right side.
1
4
3 3
1
Vertical aiming
2
1
Horizontal aiming
4
5
ASN/ASNK version
1. Bolt
2. Spring washer
3. Flat washer
2
4
6
1. O–ring
2. Polarization twist disk
6. O–ring
7. Allen screws
8. Spring washer
Vertical polarization
ODUs can have two different coupling kits: fast lock and standard.
ODU ASN/ASNK can mount two different coupling kits in order to obtain a Fast Lock ASN/ASNK or a Stand-
ard ASN/ASNK. After having mounted the proper coupling kit the ODU needs O-ring and grounding bolt.
After the fast lock coupling kit installation, the ODU needs O-ring and grounding bolt only.
See Fig.95 - Put the Fast Lock coupling kit on the ODU.
Align the four holes of the coupling kit with the four nut screws on the ODU. Insert and tighten the four
screws.
The standard coupling kit is mounted on ASN/ASNK ODU by means of four screws.
See Fig.96 - Put the standard coupling kit on the ODU. Align the four holes of the coupling kit with the four
nut screws on the ODU. Insert and tighten the four screws.
The installation of ODUs with Fast Lock coupling kit is described in previous chapters.
• M10 bolts
• ODU with O-ring and devices for ground connection
Install the antenna using the antenna installation guide (specific for each antenna) inside the antenna box
provided by antenna producer. Keep attention to the polarization of the antenna feeder depending on re-
quested polarization.
After the antenna is installed onto the pole, the ODU must be installed, see Fig.97.
• Position the three holes circular flange (1) on the antenna flange and align the three holes on the
circular flange with the three relevant holes on the antenna flange
• Insert and tighten the three 3mm M4 Allen screws (2) using a 3mm Allen wrench (torque = 2 Nm)
• Add lubricant paste, e.g. MOLYKOTE P-40, on threads of four 25mm bolts (3). The sliding surfaces
should be cleaned. The paste should then be applied with a suitable brush, rag or grease gun. It
should not be mixed with grease or oils. Chemical protective gloves should be worn where repeated
or prolonged contact can occur.
• 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 span-
ner)
• Apply seal and lubricant grease Dow Corning 4 to the O-ring, protecting fingers with gloves, and
insert in the proper track on the ODU flange
• Position the ODU (5) vertically near the four bolts on the antenna flange and align the ODU to match
the polarization of the antenna feeder:
- vertical polarization: the handle (6) of the ODU is at the bottom left corner
• After the right position has been found, rotate 30° counter clockwise the ODU and approach the
ODU to the antenna flange in order to have the four slots of the Standard Lock cross between the
four bolts
• Rotate 30° clockwise the ODU to hook each slots on the relevant bolt
• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15mm spanner,
torque=46mm)
• Optional: sun cover kit - Insert the sun cover and tie one of its bottom holes to the ODU handle by
means of the black plastic strip included in the sun cover kit
• The ODU is ready to be connected to the IDU-ODU cable and to the grounding cable.
Install The antenna using the antenna installation guide (specific for each antenna) inside the antenna box
by antenna producer. Keep attention to the polarization of the antenna feeder depending on requested po-
larization.
After the antenna is installed onto the pole, follow the procedure below, see Fig.98.
• Insert and tighten the three 3mm M4 Allen screws (2) using a 3mm Allen wrench (torque = 2mm)
• Prepare the polarization disk (see Fig.99) with the two O-rings: seal and lubricant grease Dow Corn-
ing 4 must be applied to the O-ring, protecting fingers with gloves; each O-ring must be inserted in
the proper track on each surface of the disk
• Mount always (with vertical and with horizontal polarization) the polarization disk on the hybrid
flange (antenna side) as shown in Fig.99 and tighten the four screws (only three screws in 13 GHz
and 15 GHz hybrid). The polarization disk must br oriented depending on requested polarization by
antenna feeder (position V or H as shown in Fig.99. Torque values as in Tab.41.
• Mount the hybrid on the back of the antenna by means of four M10 bolts (4) (torque = 46 Nm)
• Add lubricant paste, e.g. MOLYKOTE P-40, on threads of four 25mm bolts (3). The sliding surfaces
should be cleaned. The paste should then be applied with a suitable brush, rag or grease gun. It
should not be mixed with grease or oils. Chemical protective gloves should be worn where repeated
or prolonged contact can occur.
• Screw partially four M10 bolts (4) on the hybrid flange (ODU side): each bolt should be tightened
to have the square head out of the hole of about 13-14 mm, use 15 mm spanner
• Apply seal and lubricant grease Dow Corning 4 to the O-ring, protecting fingers with gloves, and
insert in the proper track on the ODU flange
• Position the ODU (5) vertically near the four bolts on the antenna flange and align the ODU to match
the polarization of the antenna feeder: horizontal polarization must be used, the handle (6) of the
ODU is at the bottom right corner
• After the right position has been found, rotate 30° counter clockwise the ODU and approach the
ODU to the antenna flange in order to have the four slots (7) of the Standard Lock cross between
the four bolts on the hybrid
• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15 mm spanner, torque
= 46Nm)
• Optional: sun cover kit - Insert the sun cover and tie one of its bottom holes to the ODU handle by
means of the black plastic strip included in the sun cover kit
• Now the ODU is ready to be connected to the IDU-ODU cable and to the grounding cable
• Now the ODU is ready to be connected to the IDU-ODU cable and to the grounding cable.
The installation of ODUs with Fast Lock coupling kit is described in previous chapters.
• Supporting plate, fixing bracket with M10 130mm bolts (with washer, spring and nut)
• Supporting plate, fixing bracket with M10 130mm bolts (with washer, spring and nut)
See Fig.100.
• Position the supporting plate (1) on the pole and fix the rear bracket (2) to it by means of the four
130 mm M10 bolt (3) with relevant washers, springs and nuts (use 15mm spanner, torque =
46Nm).
• Fix the antenna side flange (4) with the proper screws (in Fig.100 the antenna flange is shown in
two different positions depending on the polarization), the screw holes side is the side where the
waveguide must be installed.
• Add lubricant paste, e.g. MOLYKOTE P-40, on threads of four 25mm bolts (3). The sliding surfaces
should be cleaned. The paste should then be applied with a suitable brush, rag or grease gun. It
should not be mixed with grease or oils. Chemical protective gloves should be worn where repeated
or prolonged contact can occur.
• On the supporting plate, on the opposite side respect to the antenna flange just mounted, insert in
holes (5) on the supporting plate the four 25mm M10 bolts (3): screw them partially, each bolt
should be tightened to have the square head out of the hole of about 13-14 mm (the thickness of
hook (4), use 15mm spanner).
• Apply seal and lubricant grease Dow Corning 4 to the O-ring, protecting fingers with gloves, and
insert it in the proper track on the ODU flange.
• Position the ODU vertically near the four bolts on the supporting plate and align the ODU to match
the polarization of the antenna flange:
- vertical polarization: the handle of the ODU is at the bottom left corner
- horizontal polarization: the handle of the ODU is at the bottom right corner
• After the right position has been found, rotate 30° counter clockwise the ODU and approach the
ODU to the supporting plate in order to have the four slots of the Standard Lock cross between the
four bolts
• Rotate 30° clockwise the ODU to hook each slots on the relevant bolt
• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15 mm spanner, torque
=46 Nm).
See Fig.101.
• Position the supporting plate (1) on the pole and fix the rear bracket (2) to it by means of the four
130 mm M10 bolt (3) with relevant washers, springs and nuts (use 15 mm spanner, torque = 46
Nm)
• Mount the hybrid (4) on the back of the antenna by means of four 25 mm M10 bolts (5) (use 15
mm spanner with torque = 46 Nm) in the holes (6).
Mounting each ODU on the hybrid:
• Add lubricant paste, e.g. MOLYKOTE P-40, on threads of four 25mm bolts (3). The sliding surfaces
should be cleaned. The paste should then be applied with a suitable brush, rag or grease gun. It
should not be mixed with grease or oils. Chemical protective gloves should be worn where repeated
or prolonged contact can occur.
• Screw partially four 25 mm M10 bolts positioning them in the holes (7) on the hybrid flange (ODU
side): each bolt should be tightened to have the square head out of the hole of about 13-14 mm,
use 15 mm spanner
• Apply seal and lubricant grease Dow Corning 4 to the O-ring, protecting fingers with gloves, and
insert in the proper track on the ODU flange
• Position the ODU vertically near the four bolts on the antenna flange and align the ODU to match
the polarization of the antenna feeder: horizontal polarization must be used, the handle of the ODU
is at the bottom right corner
• After the right position has been found, rotate 30° counter clockwise the ODU and approach it to
the antenna flange in order to have the four slots of the Standard Lock cross between the four bolts
on the hybrid
• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15 mm spanner, torque
= 46 Nm)
• Optional: sun cover kit - insert the sun cover and tie one of its bottom holes to the ODU handle by
means of the black plastic strip included in the sun cover kit
• Now the ODU is ready to be connected to the IDU-ODU cable and to the grounding cable
After having installed the ODU in 1+0 configuration or in 1+1 configuration, the waveguide towards the
antenna must be installed.
• 1+0: the waveguide must be fixed to the antenna flange on the supporting plate of the ODU. In
case of flexible waveguides, an excessive folding can damage the waveguide, see Tab.42 for details.
• 1+1: the waveguide must be fixed to the hybrid. In case of flexible waveguides, an excessive folding
can damage the waveguide, see Tab.42 for details.
Bending radius with- Bending radius with- Bending radius with Bending radius with
out rebending out rebending rebending rebending
Frequency
mm (inch) mm (inch) mm (inch) mm (inch)
E-plane a H-plane b E-plane a. H-plane b.
6 GHz or 7 GHz
200 (7,9) 500 (19,8) 300 (11,9) 600 (23,7)
low
7 GHz high 200 (7,9) 500 (19,8) 250 (9,9) 600 (23,7)
a. Bending E-plane
Rmin/E
Bending E-plane
(short side of the section)
b. Bending H-plane
Rmin/H
Bending H-plane
(long side of the section)
Screws
O-ring
ODU ASN/ASNK
Eyelet terminal
Coupling torque for the grounding bolt is 9.5 Nm
Grounding bolt
O-ring
ODU ASN/ASNK
Eyelet terminal
Grounding bolt
4
M10
2 (Torque 2Nm)
7
3
4
6
1
114-60
3
5
2
Warning: use only shielded Ethernet cables for AGS20 and FO interconnection.
For the Full ODU installation, see relevant manual depending on Full ODU version.
14 LINE–UP OF AGS-20
In this section are listed all the operations necessary for the line-up of AGS-20 with or without a ODU.
In case of a Full ODU is connected to AGS-20, the operations necessary for the line-up of the Full ODU are
described in the manual relevant that version of Full ODU.
14.1 GENERAL
• equipment switch–on
• connection procedure
Operations involving the use of WebLCT are roughly described here. For further details please refer to soft-
ware manual.
• antenna presence - check the connection between ODU/Full ODU output flange and antenna.
If everything is correct, power on the AGS-20.
Check alarm LEDs on front panel and on the Full ODU (if any). Alarm information can be found in Section
5. MAINTENANCE.
Ethernet connection between PC and AGS-20 can occur if both the IP Addresses belong to the same subnet.
• RJ45 LCT port with IP address 192.168.0.1 and netmask 255.255.255.0 (default settings)
- 172.20.255.15 and netmask 255.255.0.0 if the IDU has been tested with a H radio
- 172.20.254.14 and netmask 255.255.0.0 if the IDU has been tested with a L radio.
When the connection is active the WebLCT is available in order to configure and manage unit and link.
Through the same ports, using Hyperterminal, a CLI session can be used to configure the Ethernet switch
of the unit. The maximum number of CLI sessions, active at the same time, is 7. The maximum number
of WebLCT sessions active at the same time is 4.
2. type in the search bar the proper AGS20 IP address (see paragraph 14.4 CONNECTION TO
EQUIPMENT)
- password: admin
4. select or not the “Remember me” option to remind login data for further accesses
1. open WLC
2. add LCT/LAN3 port IP address to LAN address book field in the WLC using the “Add +” button
- username: admin
- password: admin
5. select or not the “Remember me” option to remind login data for further accesses
1. open Hyperterminal and, in the window Connection Description, write the name/icon for the con-
nection
2. write the LCT/LAN3 port IP address in Host address field. Port number is 23
The radio link configuration is made up by equipment configuration applied on both side of the hop.
Parameters to set are the same local and remote side except Tx Frequency (it depends on ssb: ODU H or
ODU L).
• IP address
Run WebLCT and write the new IP address, netmask, default gateway and eventual Vid (1) in DCN menu
for In Band management.
Warning: before starting the BW & MOD/Link ID configuration enter in Equipment ->General Preset and
Disable the synchronization setup protocol (SSP) to avoid the rescue alarm and condition.
At the end of the line up procedure, then it is suggested to enable the SSP. Further details on SSP protocol
are available in the AG20 WebLCT Software manual - code: MN. 00327E.
- Bandwidth
• Tx frequency
• Duplex frequency
Warning: Remember that radio link can work only if ODUs have equal subband and different Tx module
(example: ODU 1H and ODU 1L).
Run WebLCT and In Radio, select Radio Branch. In ODU Powers card set:
or
• Automatic
- Max Ptx
- ATPC Regulation
- High
- Low
Automatic Transmission Power Control (ATPC) regulates RF Ptx of the remote transmitter depending on
the value of the RF level at the local terminal. This value has to be preset in the local terminal between the
two thresholds high and low.
A proper setting of these thresholds is with the ATPC Low Level value 5/10 dB higher than the upper profile
downshift threshold and, higher is the ODU RF band, higher must be the difference between them.
Into WebLCT in Main, Equipment Properties, select General Info card and set:
• Equipment ID (name of the local unit)
To add a routing line in the existing table select the button Add:
• set default Gateway IP address and the distance from it (number of interfaces to cross).
Run the WebLCT and expand Remote element list area (expansion arrows on the right).
Select Clear and Apply just to delete the previous configuration.
In station field select Add, type the new station name and press OK.
Proceed as follows:
The relationship between AGC voltage and received field is shown in Fig.102. The received field level has
a tolerance of ±4 dB in the full temperature range.
2,625
2,25
1,875
1,5
1,125
0,75
0 dBm
For the Full ODU antenna aiming, see relevant manual depending on Full ODU version.
15 ALARMS
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 SIAE radio system, groups of alarms are defined. These alarms can be independent or
interdependent 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 not urgent, that might be locally removed without having to replace the unit.
Alarm severity can be modified or masked in “Alarm severity configuration” via WebLCT by the operator.
The visual indication are given by LEDs. The information provided are:
• ON (green LED)
• SW (red LED)
- OFF: none
- OFF: none
- ON: some manual operation active (Loops, Radio Switch, Fade Margin, PRBS, etc....)
During the AGS-20 boot, the display LEDs follow the order:
• half a minute with a clockwise continuos ring interesting SW, NURG, URG, TEST LEDs
Now it is active.
Alarms are divided in groups to refer to a particular functionality and are characterized by programmable
severity.
In the following you can find a class list and the item they described:
• COMMON - Failure or status relevant to whole equipment
ETH LAN Eth Lan Phy Link Loss Loss of Ethernet signal Major
Radio Cable Short Alarm IDU-ODU cable damaged (short circuit) Major
Link Local IDU Synthesis There are some alarms in Loc IDU Major
IDU
ppi Los Alarm Pdh Physical Interface Loss Of Signal Major
Queue Queue Depth Profile mismatch Queue Ethernet configuration mismatch Warning
Radio Rx Power Low Warning Received power below the fixed threshold Major
Radio Idu Odu Communication Signal from IDU to ODU is missing Major
Radio Odu Idu Communication Signal from ODU to IDU is missing Major
Radio Local Odu Alarm Synthesis There are some alarms in Loc ODU Status
Radio Rem Odu Alarm Synthesis There are some alarms in Rem ODU Status
Link Xpic Rem Tx Off Alarm Local Xpic has turn off Remote Tx Status
Link Remote Idu Alarm Synthesis There are some alarms in Rem IDU Major
Link Setup Mismatch Alarm TDM Mismatch in Local & Remote Major
16.1 GENERAL
In the following pages are listed all the procedures to follow for AGS-20 maintenance.
When corrective maintenance is necessary, a troubleshooting procedure helps the operator to identify the
failure unit to replace it with a spare one.
16.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.
System routine maintenance consists in a series of routine checks aiming to verify correct operating mode
of an alarm–free system.
• 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 AGS-20 software
manual.
Corrective maintenance starts as soon as one or more alarm indication become active.
Corrective maintenance purpose is to locate the faulty unit and replace it with spare after having verified
that the cause of faulty is not external to the equipment.
Corrective maintenance does not include malfunction due to a wrong or incomplete configuration of the
system or to failure due to alarm indication system itself or any other cause external to the system, i.e.:
cabling damage, main voltage loss, antenna misalignment and propagation problems.
16.3 TROUBLESHOOTING
• Propagations of microwave
- interference (in a link radio turn off the Ptx module (local & remote) and monitoring the Prx dur-
ing the day, active local Link ID)
- desalign of antenna (check positions and screws, maximize the voltage on the ODU)
- obstacle in the 1° Fresnel Zone (tree, tower building, etc....)
- particular condition (heavy rain, stratification of different air temperature, flat surface, etc....)
• Radio hardware faulty
- faulty (using radio BER test generator and loops, to check hardware failure)
• External event
• reading Current Alarms and Alarm History labels and trying to figure out which part of the equip-
ment is affected.
• SW/HW restart
• factory default
• firmware update
Present alarms:
In order to understand why quality alarms are present, RxPwr performance window must be used (in NMS
or WebLCT).
Local status
Rx levels are low.... and before? From RxPWR table it is possible to see that in the
last 15min record Rx level is <-80dBm but in previous records Rx levelwas higher.
From the situation the reason of quality problem is rain (...f>10Ghz).
If the two alarms are present during a high Rx level period (Rx level >-50dBm) the
quality fall should be caused by interference.Investigate about.
If the problem suggests rain or other weather related fading condition and
it matches the prevailing weather conditions, do not perform any further
action until the situation gets better.
Fig.103
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.
When propagation problems occur, the link performance will be restored as the weather gets back to nor-
mal and if problems persist (Rx level remain different from normal) the reason must be searched in wrong
antenna disalignment (probably caused by strong wind or snow/ice).
Radio link affected by interference has quality problems in one direction only (possible alarms are Rx Qual-
ity warning, Rx Quality alarm, Telemetry fail increasing the interference severity). Rx level in the interfered
site is not reduced by interference.
When these symptoms occur check if new radio links have been installed in close areas (higher the fre-
quency, smaller the search radius).
In any case interference can be confirmed by a spectrum analyser through a multi-angle investigation per-
formed at antenna side.
AGS20 give the possibility to perform several maintenance tests to verify the correct equipment working.
Fig.104
For more detailed information related to Maintenance software command make reference to WEBLct Man-
ual.
Warning: Command available only for equipment with TDM module 16xE1 or Nodal.
It is possible to enable for each E1 port a PRBS TX Injector and RX PRBS detector for TDM circuit continuity
check without the necessity to use additional test instrument.
• 2 ^ 15-1
• 2 ^ 23-1
• Elapsed Time. Time (expressed in day/hours/minutes/seconds) range after the measure active
• Fail Alarms (option). Number of times that the Fail Alarm activated from the start of the measure.
• Fail Alarm (box). Status of the Fail Alarm. The color of the box represents the alarm status and se-
verity:
Fig.105 - PRBS
Warning: Command available only for equipment with Radio module and with at least one Radio Link de-
fined.
IF loop at modem level check the correct working of the local baseband and modem unit.
• IF Loop ETH SQUELCHED, loop back only the TDM traffic
• IF Loop ETH NOT SQUELCHED, loop back TDM traffic and ETH traffic too.
RF Loop at ODU TX, RX level check the correct working of the complete Local IDU and ODU.
Warning: RF Loop will perform a self check at fixed modulation format. TDM traffic & ETH traffic is not guar-
anteed to be the same as in the normal traffic condition – STM1 Bulk is not looped back.
During the execution of the test, the Test Loop box shows the progression of the operation.
The status of the test is pointed out by the Test Loop Result box:
During the test execution, the real traffic connected to AGS20 is not looped back; after the test result then
the real traffic will be partially looped back according to the fixed modulation in use for this test.
16.4.2.2 RT PSU
In order to disconnect the ODU from the cable or cable substitution, it should be necessary to set in OFF
the RT PSU and then restore ON at the end of the maintenance operation.
16.4.2.3 TX Transmitter
This menu set the ODU TX off temporary, (according to MAN. OP setting), or permanent OFF until the user
restore manually the normal ON status.
This test could be useful for lab testing or antenna panning in case of problem finding the radiation central
lobe.
The test duration depend on MAN.OP setting.
The Manual Operations command manages the available maintenance operations (MAN. OP); for the fol-
lowing test, see the related reference.
• Enable/disable the used E1 signal for the PRBS measure see paragraph 16.4.1.
Other manual operations are available according to AGS20 Hardware and software configuration:
TDM interfaces, SDH and E1, give the possibility to activate line or internal loopback:
MST
1 to 16 E1 SCSI
L I
1 to 2 NBUS
Cross PWE3
connection (Pseudo Wire)
1000BaseX/2.5Gbps SFP
LAN6 Gi-0/5
1000BaseX/2.5Gbps SFP LAN A (Gi-0/6)
LAN5 Gi-0/4 Combo
10/100/1000BaseT
LAN4 Gi-0/8
Switch
10/100/1000BaseT/1000BaseX Ethernet
LAN2 Gi-0/10 Combo
L2 LAN B (Gi-0/7)
10/100/1000BaseT/1000BaseX Combo
LAN1 Gi-0/9 Combo
Management traffic:
10/100/1000BaseT
LAN3 Gi-0/3 Mngt
16.5.1 Introduction
In a frequency re-used system with XPIC the behavior of the equipment on a given polarization may be
affected by faults occurred on hardware that manages the signals on the other polarization: an hardware
failure could cause a wrong behavior of the Cross Polar Canceller. In order to manage the faults that may
have consequences on the signals on both polarizations, a specific XPIC Fault Management Procedure
(FMP) has been inserted in the AGS-20 Equipment Controller.
Aim of FMP is to detect possible faults by means of IDU and ODU alarms analysis and, consequently, to
activate appropriate actions in order to preserve the correct behavior of the unaffected polarization.
The XPIC FMP may be enabled or disabled by the operator, using the LCT or the remote NMS.
The XPIC Fault Management Procedure aims to detect actual equipment faults and to distinguish fault con-
ditions from propagation consequences.
When XPIC is used on a double polarized link, an hardware fault (on a receiver or on a transmitter) can
prejudice the correct functioning of the XPIC: hardware faults can produce mutual interference and, con-
sequently, without FMP intervention, also the bearer on the polarization not affected by faults could not
work properly.
Depending on the value of the parameters under observation, the FMP may force commands on equipment
in both terminal in order to preserve the desired signal from interference and/or noise.
The FMP usage is very useful for modulation levels higher than 256QAM for which the antenna polarization
decoupling (XPD) could be not enough in presence of mutual interference between bearers on opposite
polarization, also in absence of bad propagation conditions.
The Fault Management Procedure analyzes equipment alarms sampling alarms each second. Different
alarm observation periods are considered depending to the group of alarms considered during the analysis:
at the end of each “alarm period evaluation”, the content of alarms can trigger FMP and relevant actions
will be activated.
FMP can have different intervention times depending on the events detected by the procedure. If hardware
failures are detected unequivocally, the FMP can act quickly in order to minimize the link outage. In other
cases, longer observation periods should be considered in order to activate FMP only when its usage is ap-
propriate.
Different alarms are considered in order to detect events for which FMP must be activated. Four different
group of events are taken into account with different FPM intervention times. In particular:
a. RX ODU failure alarms, IDU-ODU cable alarms, demodulator failure alarms at local terminal
equipments: FMP acts if relevant alarms are detected for 10 consecutive seconds
b. TX ODU failure alarms, IDU-ODU cable alarms, demodulator failure alarms at remote terminal
equipments: FMP acts if relevant alarms are detected for 15 consecutive seconds
c. RX alarms or local terminal demodulator parameters that show a possible failure on the remote
TX: FMP acts if relevant alarms are detected for 45 consecutive seconds
d. Local demodulator unlock: FMP acts if two different events (demodulator preamble unlock and
PRx level under a specified threshold) are detected for at least 120 seconds in a observation
period of 180 seconds.
All the above events are considered separately for both polarizations.
Alarms belonging to previous group of events “a” and “b” report unequivocally a hardware failure: in the
first case (a) a fault on the RX ODU, IDU-ODU cable or demodulator is locally detected, while in the second
case (b) a fault on the TX ODU, IDUODU cable or demodulator is signaled by telemetry to the controller
unit in the local terminal. For both cases, the Fault
Management Procedure can act quickly in order to minimize the outage of link.
In particular, in order to detect a possible fault on the Remote TX (group of events “c”) in presence of a
loss on the link telemetry (the link is down on both polarizations), three different conditions are checked:
• presence of a gap higher than 24 dB between Received power level (PRX) measured on each polar-
ization
If these three conditions are verified at the same time for at least 45 seconds, a remote TX fault is deduced
and, consequently, the FMP can act.
In absence of conditions belonging to group of events “a” and “c”, a local demodulator unlock could occur
due to hardware faults. In order to exclude situations for which the demodulator unlock is due to propa-
gation problems, the FMP acts only if at least one of the two PRX measured on both polarizations is higher
than a predefined threshold (about 25dB higher than the BER 10^-6 Threshold for 4QAM modulation). In
particular, the following table shows the PRX thresholds considered by FMP:
Tab.44
13.75 - 20 -60
27.5 - 40 -57
50 - 56 -54
If the above condition on PRX and a alarm of demodulator unlock are verified for at least 120 seconds in
an observation period equal to 180 seconds, the FMP is triggered.
In order to allow the equipment reaching a stable condition after start-up or after enabling FMP, a “stability
timeout” has been defined: it is fixed at 40 seconds and it is not configurable. During this period the FMP
is not active.
After the proper intervention time associated to each group of alarms under analysis (see paragraph
16.5.2.2 Parameters considered by FMP), the XPIC Fault Management Procedure may force the following
commands on the equipment in both terminals:
• Switch-off the remote transmitter on the polarization interested by the fault in order to eliminate a
potential source of interference towards the receiver on the opposite polarization.
• Local XPIC disable on the polarization not interested by the fault in order to prevent noise on the
desired signal. In addition, FMP generates:
- an alarm on the local equipment with the indication of radio on which the XPIC functionality has
been disabled
- an alarm on the remote equipment with the indication of radio on which the Transmitter has
been switched off
The alarms and the commands forced by the procedure can be removed only by an operator using the
WEBLct, disabling and then enabling again the FMP.
The operator can also disable the usage of FMP by means of WEBLct
ODU A Tx OFF
ODU A Cable Alarm
Station A Station B
ODU A Rx Fail
Station A Station B
ODU A Rx Failure
ODU A Tx OFF
Station A Station B
When the fault is restored, in order to come back to the normal working condition, the user need to RESET
FMP on both stations.
For testing purposes, it is possible to disable the XPIC functionality or the FMP procedure:
In case of activation of other commands like TX Off, RTN PS OFF etc. etc. the XPIC function will be tempo-
rary disabled; please make reference to the related WEBLct manual for details.
16.6.1 Introduction
The possible Manual Operations expected in case of QUAD IF AGS20 1+1XPIC HS/FD are:
• transmitter off
• carrier only
• RT PSU off
• IF loop
• RF loop
• XPIC disable.
We take as reference the 2 XPIC clusters and 2 protected clusters reported in the Fig.116.
XPIC Cluster 1
Protection Cluster 1
Protection Cluster 2
XPIC Cluster 2
Fig.116
a. The TX switching is forced on XPIC cluster 1 or at least the second ODU of the protection cluster 2 is
with TX alarmed or is missing; if we switch off the transmitter on ODU A, B,C or D we will have the
following consequential action:
TX‐OFF (ODU‐A): CASE‐A TX‐OFF (ODU‐B): CASE‐A
TX‐off XPIC 1 XP IC 1
A A XPIC OF F A A
(1‐A ) A (1‐A) (1‐A) (1‐A)
XPIC OFF B TX‐off
(1‐B) B B (1‐B) (1‐B) B B (1‐B)
XPIC OFF C
(2‐A ) C C (2‐A) (2‐A) C C (2‐A)
XPI C OFF D
(2‐B) D D (2‐B) (2‐B) D D (2‐B)
XPIC 2 XP IC 2
b. No protection TX forced on XPIC cluster 1 and no ODU of protection cluster is with TX alarmed or is
missing; if we switch off the transmitter on ODU A, B,C or D we will not have any XPIC consequential
action:
TX‐OFF (ODU‐A): CASE‐B TX‐OFF (ODU‐B): CASE‐B
TX‐off XPIC 1 XP IC 1
(1‐A ) A A (1‐A) (1‐A) A A (1‐A)
TX‐off
(1‐B) B B (1‐B) (1‐B) B B (1‐B)
In this case, the two XPIC clusters are completely independent; if we switch off the transmitter on ODU A,
B, C or D we will have the following consequential action:
If we activate the Carrier only test, we will have the same consequential action described in chapter TX OFF
a. The TX switching is forced on XPIC cluster 1 or at least the second ODU of the protection cluster is with
TX alarmed or is missing; the RX protection system is in Auto. In this case we have the same conse-
quential action seen in paragraph 16.6.2.1 Hot Stand-by configuration: TX OFF.
b. No TX switching is forced on XPIC cluster 1 and no ODU of the protection cluster is with TX alarmed or
is missing; RX switching is in AUTO. In this case no consequential action will be expected
c. The TX switching is forced on XPIC cluster 1 or at least the second ODU of the protection cluster is with
TX alarmed or is missing; the RX protection system is forced on the XPIC cluster where we apply for
the RT PSU OFF command.
a. The RX is forced to the cluster XPIC of which the ODU is switched off or the other ODU protection cluster
is missing or with RX alarmed.
b. The RX is NOT forced to the cluster XPIC of which the ODU is switched off and the other ODU protection
cluster is not missing or with RX alarmed.
16.6.5 IF Loop
a. The RX is forced to the XPIC cluster where the IF Loop is NOT applied:
b. The RX IS or IS NOT forced to the XPIC cluster where we apply the IF loop:
IF loop (ODU‐A): CASE‐B IF loop (ODU‐B): CASE‐B
XPIC OF F A
IF loop XPIC 1 TX‐off XP IC 1
(1‐A ) A A (1‐A) (1‐A) A XPIC OFF A A (1‐A)
IF loo p TX‐off
(1‐B) B XPIC OFF B B (1‐B) (1‐B) B
XPIC OF F B
B (1‐B)
TX‐off
(2‐A ) C C (2‐A) (2‐A) C C (2‐A)
TX‐off
(2‐B) D D (2‐B) (2‐B) D D (2‐B)
XPIC 2 XP IC 2
IF loop (ODU‐C): CASE‐B IF loop (ODU‐D): CASE‐B
X PIC 1 TX‐off XPIC 1
(1‐ A) A A (1‐A) (1‐A) A A (1‐A )
TX‐off
(1‐ B) B B (1‐B) (1‐B) B B (1‐B)
IF loop TX‐off
(2‐ A) C C (2‐A) (2‐A) C XPIC OF
IF loop
F C
C (2‐A )
XPIC OF F C TX‐o ff
(2‐ B) D D (2‐B) (2‐B) D D (2‐B)
XPIC OFF D XPIC OFF D
X PIC 2 XPIC 2
a. The RX is forced on the XPIC cluster where the IF Loop is NOT applied:
b. The RX IS or IS NOT forced to the XPIC cluster where we apply the IF loop:
IF loop (ODU‐C): CASE‐B IF loop (ODU‐D): CASE‐B
X PIC 1 XPIC 1
(1‐ A) A A (1‐A) (1‐A) A A (1‐A )
(1‐ B) B B (1‐B) (1‐B) B B (1‐B)
IF loop TX‐off
(2‐ A) C C (2‐A) (2‐A) C XPIC OF
IF loop
F C
C (2‐A )
XPIC OFF C TX‐o ff
(2‐ B) D D (2‐B) (2‐B) D D (2‐B)
XPIC OFF D XPIC OFF D
X PIC 2 XPIC 2
A software reset command implies the software reboot of the unit and it is traffic affecting.
• through WebLCT/NMS
• pressing the R button on the front panel (the SW LED remain steady on).
• more than 5 seconds -> all the devices of the unit and the microprocessor restart; the outage time
of the traffic is longer.
The software reset command does not set the unit as in factory default and does not modify any configu-
ration parameter.
18.1 GENERAL
AGS-20 is programmed and supervised using CLI and WebLCT. This subject is fully described in the sepa-
rated software manual.
18.2 SUPERVISION
On SIAE AGS-20 different ports are related to the management of the equipment:
• LAN 3: Ethernet LAN port configured as the port dedicated to the management traffic (default op-
tion)
• LCT (Local Craft Terminal): RJ45 port to access the local and remote network elements
LAN 3 is the default LAN port assigned to the management traffic of the equipment, (emulated out of
band). This setting can be changed just through the CLI interface, converting the LAN 3 in a port dedicated
to the transport of normal payload traffic or modifying another LAN port to be used as MNGT port.
LCT port is physically connected to the CPU of the device and let’s manages the equipment locally. Addi-
tionally, with the proper routing configuration, all the network elements in the chain/cluster can be ac-
cessed. In fact the CPU interface associated to the LCT port can be used in the routing process like all the
other CPU IP interfaces.
As factory default configuration, AGS20 is configured as Emulated Out of Band DCN L2.
The interface VLAN 1 is defined for the management as default option and the default IP address is accord-
ing to ODU Tx frequency:
The VLAN ID 1 is enable on the radio port ODU A and on the LAN interface used for management: on SIAE
AGS-20 the LAN 3 port is assigned to the management by default. In case the user configures another
VLAN for the management traffic, the VLAN 1 cannot be removed from the VLAN table but no ports can be
assigned to it.
18.2.3 Configurability
In general the management plane can be configured using WebLCT or CLI (see separated software man-
ual). The combinations of management configuration are shown in paragraphs 18.2.3.1 In Band DCN (L2),
18.2.3.2 Emulated Out of Band (L2) and 18.2.3.3 Out of Band DCN (L3).
In the In Band scenario the DCN traffic is mixed with data traffic, differentiated just on VLAN basis. They
are received on the same cable connected to a single interface and forwarded on the radio link exploiting
all the available bandwidth. A specific VLAN ID is dedicated to the DCN traffic transportation, while the
normal payload traffic can be forwarded using different VLAN IDs.
To configure the equipment management in a In Band scenario and to manage the device through the re-
served VLAN interface, it is necessary to define the related MNGT VLAN into the VLAN table, then to define
and configure a VLAN IP address and a default gateway IP address. These latter parameters can be inserted
under the Management Port Configuration area, as shown in Fig.119, as well as the choice of the MNGT
VLAN. Once this VLAN interface is created and an IP address is assigned to it, the management traffic is
forwarded over the different ports associated to this same VLAN, according to the equipment VLAN table.
In Emulated Out Of Band scenario, the management traffic is provided to the IDU through a dedicated port,
separated from the payload traffic. As the previous case, no dedicated channel is used on the radio path,
where the management traffic is carried with a dedicated VLAN separately from the payload traffic.
In the Out Of Band scenario a dedicated channel (128 kbps) embedded in the header of the radio frame is
available for the transmission of management data to the far end, completely separated from the payload
traffic.
This management traffic must be routed at L3 by the IDU microprocessor and transmitted using a PPP con-
nection on the radio link between the two nodes over an HDLC channel.
To configure the Out of Band management scenario, first of all a PPP link has to be enabled on the radio
port in the MNGT Out of Band area.
Under the MNGT Port Configuration area, an IP address has to be assigned to the LAN interface that has
anyway to be associated to a MNGT VLAN ID. In fact, besides on the radio channel the management traffic
is forwarded through the PPP channel and the radio port has to be removed from the MNGT VLAN, on the
line direction, the management traffic can be forwarded either on a dedicated cable connected to the MNGT
port with no VLAN tag or through the same cable of the payload traffic using a different VLAN ID.
Additionally, the user has to set the next hop to reach the default gateway that in this case can be either
a PPP interface or a simple gateway IP address with the related network mask.
• numbered PPP: it assigns two valid IP addresses to the local and remote peer of the PPP connection
in the same subnet. In order to save addresses it is suggested to use /30 (255.255.255.252) subnet
mask
• unnumbered PPP: the radio interface is assigned to a correspondent loopback IP address, i.e. a sin-
gle host /32 (255.255.255.255) IP address. In this case there is no need of the /30 subnet to ad-
dress local and remote NE, that has to be configured in the same way. Each PPP instance on the
same SIAE AGS-20 requires a different loopback interface. After the interface is created it is possible
to define it as a valid interface in a static route to reach the equipment from a remote location.
Additionally, SIAE AGS-20 allows configuring and managing network routing. Internal routing between all
interfaces of the microprocessor is automatically resolved by the equipment by meaning of connected
routes. External routing must be defined by the user with static routes and default gateway, to be inserted
in the equipment routing table.
19 COMPOSITION OF IDU
19.1 GENERAL
There are several versions of AGS-20, each of them with different hardware characteristics.
Following statements:
• you must have 2 ODUs, the first working in the lower selected subband and the second one working
in the correspondent higher subband.
Part number, hardware layout and equipment composition are subject to change without notice.
Every version is identified by a specific part number shown on a label (see Tab.45) attached on IDU. Other
information such as power consumption, allowed configuration, feature key, system version, part number
P/N and serial number S/N are also written.
2 A AL equipment
3 I Indoor installation
20.1 GENERAL
The ODU consists of a mechanical structure that houses all the transceiver circuitry. In 1+1 HSB version
the connection to the antenna is performed through a passive hybrid.
Both transceiver and hybrid are offered in different versions depending on the operating bands, the anten-
na configuration etc...
A label attached on the ODU structure shows the most significant parameters as go/return frequency value,
subband, operating band and part number.
Part number identifies the ODU type. ODU description in the following tables shows frequency, go-return,
channel and capacity if specified.
In Tab.46 and Tab.47 various ODU versions and hybrid part number are listed.
Part number, hardware layout and equipment composition are subject to change without notice.
21 LIST OF FIGURES
Fig.5 ............................................................................................................................ 26
Fig.6 ............................................................................................................................ 26
Fig.17 - (1+1) XPIC protection: all IF ports are part of the cluster........................................ 33
Fig.18 - (4+0) FD: all IF ports are part of the cluster ......................................................... 33
Fig.19 - (4+0) XPIC: all IF ports are part of the cluster ...................................................... 33
Fig.27 - Port config 11 and 12: (2+0) cluster 3 & (1+1) cluster 2 ........................................ 40
Fig.28 - Port config from 13 to 16: (1+1) cluster 1 & (1+1) cluster 2 ................................... 40
Fig.29 - Port config from 17 to 20: (2+0) cluster 1 & (2+0) cluster 2 ................................... 41
Fig.39 – Select the LAN port that sends LLF status ............................................................. 63
Fig.40 – Select the circuit that manages the LLF protected LAN port..................................... 64
Fig.41 - AGS-20 switch (GAI0212-1)................................................................................ 75
Fig.66 - IDU AGS-20 front panel example for GAI0216 ..................................................... 111
Fig.71 - Position of the ODU handle depending on the polarisation for 1+0. For 1+1 the polarisation
is always horizontal. Handle at the right side.................................................................... 122
Fig.73 - ODU housing final position for both polarization ................................................... 124
Fig.86 - Position of the ODU handle depending on the polarisation for 1+0. For 1+1 the polarisation
is always horizontal. Handle at the right side.................................................................... 141
Fig.88 - ODU housing final position for both polarization ................................................... 143
Fig.92 - Polarization disk fixing (only for 13 GHz and 15 GHz) ........................................... 147
Fig.95 - ODU ASN/ASNK with fast lock coupling flange ..................................................... 157
Tab.6 - Dual IF: N+0 RLAG (Physical Radio Link Aggregation) ..............................................31
Tab.29 - Net radio throughput in Mbit/s versus channel bandwidth for AGS-20 equipment........89
Tab.44 ........................................................................................................................185
Tab.45 - IDU part number .............................................................................................. 204
For more information, refer to the section relevant to the technical support on the Internet site of the com-
pany manufacturing the product.