AGS20 Manual PDF

AGS-20
User manual
MN.00329.E - 007
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 9
1 DECLARATION OF CONFORMITY ............................................................................... 9
2 FIRST AID FOR ELECTRICAL SHOCK AND SAFETY RULES .........................................11

2.1 FIRST AID FOR ELECTRICAL SHOCK ....................................................................11
2.1.1 Artificial respiration .................................................................................11
2.1.2 Treatment of burns .................................................................................11
2.2 SAFETY RULES .................................................................................................13
2.3 CORRECT DISPOSAL OF THIS PRODUCT (WASTE ELECTRICAL &
ELECTRONIC EQUIPMENT) .................................................................................14
2.4 INTERNAL BATTERY ..........................................................................................14
3 PURPOSE AND STRUCTURE OF THE MANUAL ............................................................15

3.1 PURPOSE OF THE MANUAL .................................................................................15
3.2 AUDIENCE BASIC KNOWLEDGE ..........................................................................15
3.3 STRUCTURE OF THE MANUAL .............................................................................15
Section 2.
DESCRIPTIONS AND SPECIFICATION 17
4 ACRONYMS AND ABBREVIATION .............................................................................17

4.1 ACRONYMS AND ABBREVIATION LIST .................................................................17
5 SYSTEM PRESENTATION ..........................................................................................21

5.1 GENERAL.........................................................................................................21
5.2 APPLICATIONS .................................................................................................21
5.2.1 Functionalities ........................................................................................22
5.3 RADIO LINK CONFIGURATIONS ..........................................................................23
5.3.1 1+0 ......................................................................................................23
5.3.2 1+1 Hot Stand-by...................................................................................23
5.3.3 1+1 Space diversity ................................................................................23
5.3.4 1+1 frequency diversity...........................................................................24
5.3.5 1+1 frequency and space diversity ............................................................24
5.3.6 2+0 single pipe with L1 aggregation ..........................................................24
MN.00329.E - 007 1
5.3.7 2+0 single pipe with L1 aggregation in XPIC ...............................................25
5.3.8 4+0 single pipe with L1 aggregation in XPIC ...............................................25
5.3.9 AGS-20 Multiple Direction ........................................................................25
5.3.10 4+0 single pipe with L1 aggregation ..........................................................25
5.4 ETHERNET SWITCH...........................................................................................26
5.4.1 Ethernet interfaces..................................................................................26
5.4.2 Traffic treatment.....................................................................................27
5.5 DATA PLANE ....................................................................................................27
5.5.1 Ethernet features ....................................................................................28
5.5.1.1 Auto-negotiation ......................................................................28
5.5.1.2 MDI/MDI-X ..............................................................................28
5.5.1.3 Ingress Filtering .......................................................................28
5.5.1.4 MTU .......................................................................................28
5.5.1.5 Storm Control ..........................................................................29
5.5.1.6 MAC Learning Rules ..................................................................29
5.5.1.7 MAC Forwarding Rules ..............................................................29
5.5.2 VLAN Forwarding ....................................................................................30
5.5.2.1 IEEE 802.1q ............................................................................30
5.5.2.2 VLAN Stacking - QinQ ...............................................................30
5.5.2.3 VLAN Threatment .....................................................................30
5.5.2.4 Service Instance Mapping Criteria...............................................31
5.5.2.5 Ingress Manipulation.................................................................32
5.5.3 QoS Management ...................................................................................32
5.5.3.1 Classification with Priority Map ...................................................33
5.5.3.2 Classification with Class Map......................................................34
5.5.4 Policing .................................................................................................35
5.5.4.1 Metering .................................................................................35
5.5.4.2 Policy Map ...............................................................................36
5.5.5 Congestion Avoidance..............................................................................36
5.5.6 Output queues........................................................................................37
5.5.7 Scheduling method .................................................................................39
5.5.8 Egress Shaping.......................................................................................39
5.5.9 Egress Manipulation ................................................................................40
5.5.10 Packet Header Compression .....................................................................40
5.5.11 PWE3 ....................................................................................................42
5.5.11.1 Encapsulation ..........................................................................42
5.5.11.2 PWE3 in Customer Bridge mode .................................................43
5.5.11.3 PWE3 in Provider Edge Bridge mode ...........................................43
5.6 CONTROL PLANE ..............................................................................................44
5.6.1 ELP .......................................................................................................44
5.6.2 Link Aggregation.....................................................................................44
5.6.2.1 Layer 1 radio link aggregation ....................................................45
5.6.2.2 LACP ......................................................................................45
5.6.2.3 Static LAG ...............................................................................46
5.6.3 LLF .......................................................................................................46
5.6.3.1 Bidirectional LLF.......................................................................46
5.6.3.2 Parameters in Bidirectional LLF...................................................47
5.6.4 STP and RSTP.........................................................................................48
5.6.4.1 BPDU......................................................................................48
5.6.4.2 Root Bridge election .................................................................49
5.6.4.3 Root Port Election.....................................................................49
5.6.4.4 Designated Port Election............................................................49
5.6.4.5 Alternate Port ..........................................................................49
2 MN.00329.E - 007
5.6.4.6 STP/RSTP Configurability...........................................................49
5.7 SYNCHRONIZATION ..........................................................................................50
5.7.1 Sources .................................................................................................50
5.7.2 Output ..................................................................................................51
5.7.3 Priority ..................................................................................................51
5.7.4 Quality and SSM .....................................................................................52
5.7.5 Source settings.......................................................................................52
5.7.6 Ethernet Interfaces .................................................................................53
5.8 ETHERNET MAINTENANCE..................................................................................53
5.8.1 OAM......................................................................................................53
5.8.2 RMON ...................................................................................................55
5.8.2.1 Ethernet Statistics ....................................................................55
5.8.2.2 RMON Counters in each interface................................................56
5.8.2.3 Ethernet Services Statistics .......................................................56
5.9 PROGRAMMABILITY ..........................................................................................57
5.9.1 Software................................................................................................58
5.10 AVAILABLE VERSIONS.......................................................................................59
5.10.1 AGS-20 switch........................................................................................59
5.10.2 AGS-20 Single IF ....................................................................................60
5.10.3 AGS-20 Single IF/16E1 ............................................................................60
5.10.4 AGS-20 Dual IF ......................................................................................60
5.10.5 AGS-20 Dual IF/16E1 ..............................................................................61
5.10.6 AGS-20 Quad ETH...................................................................................61
5.10.7 AGS-20 Quad ETH/16E1 ..........................................................................62
5.10.8 AGS-20 PP Single IF/16E1........................................................................62
5.10.9 AGS-20 Dual IF/16E1 + 2STM1 + Nodal.....................................................63
5.10.10AGS-20 Single IF/16E1 + 2STM1 + Nodal .................................................63
5.10.11AGS-20 Quad Eth/16E1 + 2STM1 + Nodal.................................................64
5.10.12AGS-20 PP Single IF/16E1 + 2STM1 + Nodal .............................................64
5.10.13AGS-20 Quad IF ....................................................................................65
5.10.14AGS-20 Quad IF/16E1 ............................................................................65
5.10.15AGS-20 Quad IF/16E1 + 2STM1+ Nodal....................................................65
5.11 SUPPORTED ODUS............................................................................................66
5.12 SUPPORTED FULL ODUS ....................................................................................66
6 TECHNICAL SPECIFICATIONS ..................................................................................67

6.1 IDU INTERFACES ..............................................................................................67
6.1.1 Traffic interfaces .....................................................................................67
6.1.1.1 E1 (Connector Trib.1-8, Trib.9-16) .............................................67
6.1.1.2 STM-1 electrical ......................................................................68
4
6.1.1.3 STM1 optical .........................................................................68
6.1.1.4 Electrical Ethernet (Ports LAN1, LAN2, LAN3, LAN4) ......................69
6.1.1.5 Optical Ethernet (Ports LAN1, LAN2, LAN5, LAN6) .........................69
6.1.1.6 ARI (Connector ODU A, ODU B, ODU C, ODU D) ...........................69
6.1.1.7 DRI (Connector LAN C, LAN D) ...................................................70
6.1.1.8 COMBO (Connector LAN A, LAN B) ..............................................70
6.1.2 Service interfaces ...................................................................................70
6.1.2.1 LCT ........................................................................................70
6.1.2.2 Alarm .....................................................................................70
6.1.2.3 Console...................................................................................71
6.1.2.4 SYNC (SYNC-1 interface)...........................................................71
6.1.2.5 ToD (SYNC-2 interface) .............................................................71
MN.00329.E - 007 3
6.1.2.6 1PPS (SYNC-3 interface) ...........................................................71
6.1.3 Optical indications...................................................................................71
6.1.3.1 System LEDs ...........................................................................71
6.1.3.2 Ethernet interface activity .........................................................72
6.1.3.3 PoE LEDs ................................................................................72
6.1.4 Modulation, bandwidth and relevant capacity ..............................................72
6.1.5 Power supply, consumption and max current absorption...............................74
6.1.6 PoE - Power over Ethernet .......................................................................74
6.1.6.1 PoE characteristics ...................................................................74
6.1.6.2 PoE settings ............................................................................75
6.1.7 IDU general characteristics.......................................................................75
6.1.7.1 Dimensions .............................................................................75
6.1.7.2 Weight....................................................................................75
6.1.7.3 Environment conditions .............................................................75
6.2 AVAILABLE ODUS AND FULL ODUS .....................................................................76
6.2.1 ODUs ....................................................................................................76
6.2.2 Full ODUs ..............................................................................................76
6.3 ODUS, DESCRIPTION AND TECHNICAL CHARACTERISTICS.....................................76
6.3.1 ODU description......................................................................................76
6.3.1.1 ODU versions...........................................................................76
6.3.1.2 Description ..............................................................................77
6.3.1.3 IF cable interface .....................................................................77
6.3.1.4 Power supply ...........................................................................77
6.3.1.5 Tx section ...............................................................................77
6.3.1.6 Rx section ...............................................................................78
6.3.1.7 1+1 Tx system .......................................................................78
6.3.1.8 Full ODUs, description and technical characteristics.......................84
Section 3.
INSTALLATION 87
7 INSTALLATION AND PROCEDURES FOR ENSURING THE ELECTROMAGNETIC

COMPATIBILITY.......................................................................................................87
7.1 GENERAL INFORMATION TO BE READ BEFORE THE INSTALLATION..........................87
7.2 GENERAL.........................................................................................................88
7.3 MECHANICAL INSTALLATION..............................................................................88
7.3.1 IDU.......................................................................................................88
7.3.2 IDU installation.......................................................................................88
7.4 ELECTRICAL WIRING.........................................................................................88
7.5 OPTICAL CONNECTORS .....................................................................................89
7.6 CONNECTIONS TO THE SUPPLY MAINS ................................................................89
7.7 IDU-ODU INTERCONNECTION CABLE...................................................................90
7.7.1 Electrical characteristics...........................................................................90
7.7.2 Connectors ............................................................................................90
7.7.3 Max length.............................................................................................90
7.7.4 Suggested cable .....................................................................................90
7.8 GROUNDING CONNECTION ................................................................................91
7.9 IDU-ODU CABLE GROUNDING KIT INSTALLATION .................................................91
7.9.1 Grounding kit K09283F (for RG8 or 1/8” cable) ...........................................91
4 MN.00329.E - 007
7.9.2 Grounding kit ICD00072F (for any cable with shield) ...................................92
7.10 SURGE AND LIGHTNING PROTECTION .................................................................93
8 CONNECTORS ...........................................................................................................94
8.1 CONNECTORS ..................................................................................................94
9 INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED ANTENNA

(KIT V32307, V32308, V32309) .............................................................................100
9.1 FOREWORD ................................................................................................... 100
9.2 INSTALLATION KIT ......................................................................................... 100
9.3 REQUIRED TOOLS FOR MOUNTING (NOT SUPPLIED) ........................................... 101
9.4 INSTALLATION PROCEDURE ............................................................................. 101
9.5 1+0 MOUNTING PROCEDURES ......................................................................... 102
9.5.1 Setting antenna polarization ................................................................... 102
9.5.2 Installation of the centring ring on the antenna ......................................... 102
9.5.3 Installation of 1+0 ODU support ............................................................. 102
9.5.4 Installation onto the pole of the assembled structure ................................. 102
9.5.5 Installation of ODU (on 1+0 support)....................................................... 102
9.5.6 Antenna aiming .................................................................................... 103
9.5.7 ODU grounding..................................................................................... 103
9.6.1 Installation of Hybrid ............................................................................. 103
9.6.2 Installation of ODUs (on hybrid for 1+1 version) ....................................... 104
10 INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED DUAL

POLARIZATION ANTENNA ......................................................................................112
10.1 FOREWORD ................................................................................................... 112
10.2 INSTALLATION KIT FOR STANDARD LOCK ODU .................................................. 112
10.3 INSTALLATION KIT FOR FAST LOCK ODU ........................................................... 112
10.6 STANDARD LOCK ODUS MOUNTING PROCEDURE ................................................ 114
10.6.1 Installation of the centring rings over the OMT .......................................... 114
10.6.2 Installation over the pole of the assembled structure: antenna, OMT and pole
support system..................................................................................... 114
10.6.3 Installation of the standard lock ODUs over the OMT.................................. 114
10.6.4 Antenna aiming .................................................................................... 115
10.6.5 ODU grounding..................................................................................... 115
10.7 FAST LOCK ODUS MOUNTING PROCEDURE ........................................................ 115
10.7.1 Installation of the centring rings over the OMT .......................................... 115
10.7.2 Installation of the fast lock 1+0 ODU support ........................................... 115
10.7.3 Installation over the pole of the assembled structure: antenna, OMT and pole
support system..................................................................................... 115
10.7.4 Installation of the fast lock ODUs over the OMT......................................... 116
10.7.5 Antenna aiming .................................................................................... 116
10.7.6 ODU grounding..................................................................................... 116
11 INSTALLATION ONTO THE POLE OF THE ODU WITH RFS INTEGRATED ANTENNA...119
11.1 FOREWORD ................................................................................................... 119
11.2 INSTALLATION KIT ......................................................................................... 119
MN.00329.E - 007 5
11.5.1 Setting antenna polarization ................................................................... 120
11.5.2 Installation of the centring ring on the antenna ......................................... 121
11.5.3 Installation of 1+0 ODU support ............................................................. 121
11.5.4 Installation onto the pole of the assembled structure ................................. 121
11.5.5 Installation of ODU (on 1+0 support)....................................................... 121
11.5.6 Antenna aiming .................................................................................... 121
11.5.7 ODU grounding..................................................................................... 122
11.6.1 Installation of Hybrid ............................................................................. 122
11.6.2 Installation of ODUs (on hybrid for 1+1 version) ....................................... 122
12 INSTALLATION ONTO THE POLE OF ODU ASN/ASNK WITH STANDARD LOCK ........133
12.1 ODU COUPLING KIT ........................................................................................ 133
12.1.1 ODU ASN/ASNK .................................................................................... 133
12.1.1.1 Fast lock coupling kit .............................................................. 133
12.1.1.2 Standard coupling kit .............................................................. 133
12.2 INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED ANTENNA ........... 134
12.2.1 ODU ASN/ASNK (Fast Lock) ................................................................... 134
12.2.2 ODU ASN/ASNK (Standard Lock)............................................................. 134
12.2.2.1 1+0 ODU .............................................................................. 134
12.2.2.2 1+1 ODU .............................................................................. 135
12.3 INSTALLATION ONTO THE POLE OF THE ODU WITH SEPARATED ANTENNA............. 136
12.3.1 ODU ASN/ASNK (Fast Lock) ................................................................... 136
12.3.2 ODU ASN/ASNK (Standard Lock)............................................................. 136
12.3.2.1 1+0 ODU .............................................................................. 137
12.3.2.2 1+1 ODU .............................................................................. 137
12.3.2.3 Waveguide towards the antenna............................................... 139
13 INSTALLATION OF THE FULL ODU ..........................................................................147
Section 4.
LINE-UP 149
14 LINE–UP OF AGS-20...............................................................................................149
14.1 GENERAL....................................................................................................... 149
14.2 SWITCH ON ................................................................................................... 150
14.3 ALARM LED CHECK ......................................................................................... 150
14.4 CONNECTION TO EQUIPMENT .......................................................................... 150
14.4.1 Connection to LCT or LAN3 port .............................................................. 150
14.4.2 Connection using WLC ........................................................................... 151
14.4.3 CLI session using Hyperterminal (or a similar software) ............................. 151
14.5 RADIO LINK CONFIGURATION .......................................................................... 151
14.6 EQUIPMENT CONFIGURATION .......................................................................... 151
14.6.1 IP address setting ................................................................................. 152
14.6.2 Bandwidth, modulation, TDM and Link ID setting....................................... 152
14.6.3 Tx frequency setting.............................................................................. 152
14.6.4 Tx power setting ................................................................................... 153
14.6.5 Equipment ID and Agent IP setting.......................................................... 153
14.6.6 Routing Table setting............................................................................. 153
6 MN.00329.E - 007
14.6.7 Remote Element Table........................................................................... 153
14.7 ANTENNA ALIGNMENT AND RX POWER .............................................................. 154
14.7.1 ODU ASN and ODU ASNK ....................................................................... 154
14.7.2 Full ODU .............................................................................................. 154
Section 5.
MAINTENANCE 155
15 ALARMS .................................................................................................................155
15.1 ALARM SYSTEM .............................................................................................. 155
15.1.1 LED status ........................................................................................... 156
15.1.2 Alarm group ......................................................................................... 156
16 MAINTENANCE AND TROUBLESHOOTING ...............................................................160

16.1 GENERAL....................................................................................................... 160
16.2 MAINTENANCE ............................................................................................... 160
16.2.1 Periodical checks .................................................................................. 160
16.2.2 Corrective maintenance (troubleshooting) ................................................ 161
16.3 TROUBLESHOOTING ....................................................................................... 161
16.3.1 Quality alarms ...................................................................................... 162
16.3.2 Radio link affected by fading................................................................... 162
16.3.3 Radio link affected by interference .......................................................... 163
17 SOFTWARE RESET ..................................................................................................164

17.1 SOFTWARE RESET .......................................................................................... 164
Section 6.
PROGRAMMING AND SUPERVISION 165
18 PROGRAMMING AND SUPERVISION .......................................................................165

18.1 GENERAL....................................................................................................... 165
18.2 SUPERVISION ................................................................................................ 165
18.2.1 Configurability ...................................................................................... 165
18.2.2 AGS-20 - In Band ................................................................................. 166
18.2.3 AGS-20 - Emulated Out Of Band (L2) ...................................................... 166
18.2.4 AGS-20 – Out of Band (L3) .................................................................... 167
18.2.5 Address ............................................................................................... 168
18.2.6 Console access mode ............................................................................ 168
18.3 COMPILING SCRIPT AT STARTUP ...................................................................... 168
MN.00329.E - 007 7
Section 7.
COMPOSITION 169
19 COMPOSITION OF IDU ...........................................................................................169

19.1 GENERAL....................................................................................................... 169
19.2 IDU PART NUMBER ......................................................................................... 169
20 COMPOSITION OF OUTDOOR UNIT.........................................................................171

20.1 GENERAL....................................................................................................... 171
Section 8.
LISTS AND SERVICES 181
21 LIST OF FIGURES ...................................................................................................181
22 LIST OF TABLES .....................................................................................................185
23 ASSISTANCE SERVICE............................................................................................187
8 MN.00329.E - 007
Section 1.
USER GUIDE
1 DECLARATION OF CONFORMITY
SIAE Microelettronica S.p.A. declares that the products:
- digital radio relay system ASN6 and ASNK6

complies with the essential requirements of article 3 of the R&TTE Directive (1999/5/EC) and therefore is
marked CE.
The following standards have been applied:
- EN 60950-1: 2006 “Safety of information technology equipment”.
- EN 301 489–4 V.1.3.1 (2002–8): “Electromagnetic compatibility and radio spectrum Matters (ERM);
Electromagnetic Compatibility (EMC) standard for radio equipment and services; Part 4. Specific con-
ditions for fixed radio links and ancillary equipment and services”
- ETSI EN 301 751 V.1.1. (2002–12): “Fixed Radio Systems; Point–to point equipment and antennas;
generic harmonized standard for point–to–point digital fixed radio systems and antennas covering the
essential requirements under article 3.2 of the 1999/5/EC Directive”
- EN 302 217 for digital point to point fixed radio
- EN 300 132-2 characteristics of power supply
- EN 300 019 climatic characteristics (operation: class 3.2 for IDU and class 4.1 for ODU; storage: class
1.2; transport: class 2.3)
MN.00329.E - 007 9
- EN 60950-1 and EN60950-22 for safety
- IEEE 802.3 for Ethernet interfaces
- ITU-T G.8261 for timing and synchronization aspects in packet networks.
10 MN.00329.E - 007
2 FIRST AID FOR ELECTRICAL SHOCK AND SAFETY
RULES
2.1 FIRST AID FOR ELECTRICAL SHOCK
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.
2.1.1 Artificial respiration
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.
2.1.2 Treatment of burns
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
• Do not attempt to remove clothing from burnt sections
• Apply dry gauze on the burns
• Do not apply ointments or other oily substances.
MN.00329.E - 007 11
Tab.1 - Artificial respiration
Step Description Figure
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.
Lift the patient’s head and let it recline backwards as far

2 as possible.
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.
3 While performing these operations take a good supply of oxy-

gen by taking deep breaths with your mouth open
With your thumb between the patient’s chin and mouth keep
his lips together and blow into his nasal cavities
While performing these operations observe if the patient’s

chest rises. If not it is possible that his nose is blocked: in that
case open the patient’s mouth as much as possible by pressing
on his chin with your hand, place your lips around his mouth
and blow into his oral cavity. Observe if the patient’s chest
5
heaves. This second method can be used instead of the first
even when the patient’s nose is not obstructed, provided his
nose is kept closed by pressing the nostrils together using the
hand you were holding his head with. The patient’s head must
be kept sloping backwards as much as possible.
Start with ten rapid expirations, hence continue at a rate of

twelve/fifteen expirations per minute. Go on like this until the
6
patient has regained conscious–ness, or until a doctor has as-
certained his death.
12 MN.00329.E - 007
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.
Fig.1 - Components electrostatic charge sensitive indication
In order to prevent the units from being damaged while handling, it is advisable to wear an elasticized band
(Fig.2) around the wrist ground connected through coiled cord (Fig.3).
Fig.2 - Elasticized band
Fig.3 - Coiled cord
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).
MN.00329.E - 007 13
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.
Fig.4 - WEEE symbol - 2002/96/CE EN50419
2.4 INTERNAL BATTERY
Inside the equipment, in IDU unit, there is a lithium battery.
CAUTION: Risk of explosion if battery is replaced by an incorrect type. Dispose of used batteries
according to law.
14 MN.00329.E - 007
3 PURPOSE AND STRUCTURE OF THE MANUAL
3.1 PURPOSE 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.
3.2 AUDIENCE BASIC KNOWLEDGE
The following knowledge and skills are required to operate the equipment:
• a basic understanding of microwave transmission
• installation and maintenance experience on digital radio system
• a good knowledge of IP/OSI networks and routing policy.
3.3 STRUCTURE OF THE MANUAL
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.
Section 1 – User Guide
It provides the information about the main safety rules and expounds the purpose and the structure of the
manual.
Section 2 – Description and specifications
It traces the broad line of equipment operation and lists the main technical characteristics of the whole
equipment and units it consists of.
List of abbreviation meaning is also supplied.
MN.00329.E - 007 15
Section 3 – Installation
The mechanical installation procedures are herein set down as well as the user electrical connections.
The content of the tool kit (if supplied) is also listed.
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.
Section 6 – Programming and supervision
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.
Each description of software tools is supplied in a separated manual.
Section 7 – Composition
Position, part numbers of the components the equipment consist of, are shown in this section.
Section 8 – Lists and assistance
This section contains the lists of figures and tables and the assistance service information.
16 MN.00329.E - 007
Section 2.
DESCRIPTIONS AND
SPECIFICATION
4 ACRONYMS AND ABBREVIATION
4.1 ACRONYMS AND ABBREVIATION LIST
- ACL Access Control Lists
- ACM Adaptive Code Modulation

- ADC Analog to Digital Converter
- AFE Analog Front End
- AGS-20 Access Gateway System

- AIS Alarm Indication Signal
- ANSI American National Standards Institute
- ARI Analog Radio Interface
- BER Bit Error Ratio
- BPDU Bridge Protocol Data Unit
- BW Bandwidth
- CBPDU Configuration BPDU
- CFM Connectivity Fault Management
- CIR Committed Information Rate
- CRC Cyclic Redundancy Check
- DAC Digital to Analog Converter
- DCN Data Control §Network
- DDR3 Double Data Rate 3
- DRI Digital Radio Interface
- DSCP Differentiated Services Code Point
MN.00329.E - 007 17
- E1 European Plesiochronous Transport Module level-1
- EEC Ethernet Equipment slave Clock
- EIR Excess Information Rate
- ELP Ethernet Link Protection
- ESMC Ethernet Synchronization Messaging Channel
- ETH Ethernet
- ETSI European Telecommunications Standards Institute

- FD Frequency Diversity
- FEC Forward Error Correction
- FIFO First In First Out
- FPGA Field Programmable Gate Array
- FSK Frequency-Shift Keying
- GE Gigabit Ethernet
- GPI General Purpose Interface
- GPM General Purpose Multiplexer
- HDB3 High Density Bipolar Code order 3
- HDLC High-Level Data Link Control

- HW Hardware
- ICM Internal Control Management
- IDU In-Door Unit

- ILS Independent Line Schemes
- ITU International Telecommunication Union
- LACP Link Aggregation Control Protocol
- LAG Link Aggregation Group
- LAN Local Area Network
- LDPC Low Density Parity Check

- LED Light Emitting Diode
- LLF Link Loss Forwarding
- LOF Loss Of Frame

- LOS Loss Of Signal
- MA Maintenance Association
- MAC Medium Access Control

- MCM MW Capacity Management
- MD Maintenance Domain
- MEP Maintenance End Point

- MIB Management Information Base
- MIP Maintenance Intermediate Point
- MNG Management
- MPLS Multi Protocol Label Switching
- MPU MicroProcessor Unit
- MuLeHC Multi Level Header Compression

- MTU Maximum Transmission Unit
- MW Microwaves
18 MN.00329.E - 007
- N.C. Not Connected
- NE Network Element
- NNI Network to Network Interface
- N.U. Not Used
- OAM Operations, Administration and Maintenance
- ODU Out-Door Unit
- OMI Out of band Management Interface

- OSSP Organization Specific Slow Protocol
- PCP Priority Code Point
- PDH Plesiochronous Digital Hierarchy
- PLA Physical Level Aggregation
- PoE Power over Ethernet
- PPS Pulse Per Second
- PWE3 Pseudo Wire Emulation Edge-to-Edge
- PWR Power
- QAM Quadrature Amplitude Modulation
- QL Quality
- QoS Quality of Service
- RDI Remote Defect Indicator
- RPL Ring Protection Link

- RS Reed Solomon
- RSTP Rapid Spanning Tree Protocol
- RJ45 Registered Jack 45
- SCSI Small Computer System Interface
- SDH Synchronous Digital Hierarchy
- SETS Synchronization Equipment Timing Source

- SFP Small Form factory Pluggable
- SGMII Serial Gigabit Media Independent Interface
- SIAE Società Italiana Apparecchiature Elettroniche

- SLA Service Level Agreement
- SNMP Simple Network Management Protocol
- SSM Synchronous Status Message

- STM1 Synchronous Transport Module level-1
- STP Spanning Tree Protocol
- SW Software
- tbc to be confirmed
- tbd to be defined
- TCA Topology Change Notification Acknowledge
- TCN Topology Change Notification
- TDM Time Division Multiplexing
- TLV Type Length Value

- ToD Time of Day
- ToS Type of Service
MN.00329.E - 007 19
- UART Universal Asynchronous Receiver-Transmitter
- UNI User Network Interface
- USB Universal Serial Bus
- VLAN Virtual Local Area Network
- VPN Virtual Private Network
- VSM Vendor Specific Message
- XPIC Cross Polarization Interference Cancellation

- WTR Wait To Restore
- µP Microprocessor.
20 MN.00329.E - 007
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
• Leased Lines replacement
• Utility Networks (Railways, Oil&Gas)
• Private Data Networks (WANs, LANs, etc)
• WiMAX Backhauling
• Fiber Optics extension, termination and backup
• Spur Links for Backbones/Rings
• High capacity Broadband Access Networks
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:
• Aggregation for All Outdoor Radio including E-Band
• Next Generation indoor Unit for split Mount Radio
• Gateway handling Small Cell Radio Cluster
MN.00329.E - 007 21
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:
• Connectivity towards ALFOplus and ALFOplus80 series
• 2.5 Gbps optical interface
Next generation unit for split mount radio
AGS-20 set a new industry benchmark in split mount microwave by featuring the following capabilities:
• Carrier Ethernet 2.0 data plane (MPLS ready)
• Modulation up to 2048 QAM

• Enhanced QoS feature set (ex. four level hierarchical scheduling)
Gateway handling small cell radio cluster
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
• Modulation from 4QAM to 2048QAM
• Hitless ACM adaptive code and modulation
• MultiLayer Header Compression
• Convergence of all outdoor and split-mount microwave
• Mixed TDM/Ethernet interfaces for dual native transport
• Synchronous Ethernet and IEEE1588 v2 support

• CISCO Microwave Adaptive Bandwidth feature interworking
• Extended buffer for maximum TCP/IP efficiency in LTE networks
• Integrated antennas up to 1.8m
• Single universal ODU for any capacity and modulation
• Unified Network Management System - NMS5
• MEF-9 and MEF-14 certified
• 8 queues with flexible scheduler (Strict Priority, WRR and mixed)
• 4 level hierarchical scheduler
• Flexible QoS definition based on VLAN, IPv4, IPv6, MPLS exp bits
• Per queue WRED congestion avoidance
• Flow Based Ingress Policing (CIR & EIR definition)
22 MN.00329.E - 007
• Egress shaping
• ERP G.8032 and linear protection G.8031
• RMON statistics per service
• VLAN stacking (IEEE 802.1ad QinQ)
• Jumbo Frames
• RSTP (IEEE 802.1D-2004).
5.3 RADIO LINK CONFIGURATIONS
Here the Link configurations that AGS-20 can support are shortly described depending on the following
characteristics:
• hardware protection
• diversity protection
• management of radio directions
• physical layer aggregation of two channels capacity

In addition the AGS-20 can be connected to SIAE Full Outdoor equipment through all the available LAN
interfaces with the management of multiple radio directions.
No protected configurations can be managed by the IDU on the LAN ports.
5.3.1 1+0
Description:
• no HW or diversity protection
• single radio direction
• single channel radio capacity
5.3.2 1+1 Hot Stand-by
Description:
• ODU HW protection
• 1 antenna with balanced or unbalanced hybrid
5.3.3 1+1 Space diversity
Description:
MN.00329.E - 007 23
• radio diversity protection
• 2 antennas without hybrid losses.
In order to implement this configuration, the AGS-20 has to be configured in 1+1HSB configuration, i.e.
the equipment configuration is the same of 1+1 Hot Stand-by but the 2 ODUs are connected to different
antennas.
5.3.4 1+1 frequency diversity
Description:
• radio frequency diversity protection

• 1 antenna with hybrid or circulator.
5.3.5 1+1 frequency and space diversity
Description:
• radio frequency diversity protection
• radio space diversity protection

• 2 antennas without hybrid/circulator losses
5.3.6 2+0 single pipe with L1 aggregation
Description:
• 2 RF channels
• no HW protection
• double channel radio capacity

• 1 antenna with hybrid or circulator losses or 2 antennas without losses.
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.
24 MN.00329.E - 007
5.3.7 2+0 single pipe with L1 aggregation in XPIC
Description:
• 1 RF channels in double polarization (Frequency reuse)
• double channel radio capacity
• 1 dual polariz. antenna with OMT.
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.
5.3.8 4+0 single pipe with L1 aggregation in XPIC
Description:
• 2 RF channels in double polarization (CCDP with Frequency reuse)
• quadruple channel radio capacity

• 1 dual polariz. antenna with OMT and circulators.
In this configuration a single Ethernet logical channel with quadruple capacity is available on the radio ob-
tained by means of Layer 1 link aggregation of the 4 physical radio channels.
5.3.9 AGS-20 Multiple Direction
Description:
• no HW or diversity protection
• multiple radio directions can be managed through IF interfaces (one per each IF, not yet available
for 4+0)
• multiple Full-Outdoor radio links can be connected by means of LAN interfaces
• single channel radio capacity on each direction (not yet available for 4+0).
5.3.10 4+0 single pipe with L1 aggregation
Description:
• 4 RF channels in double polarization (ACCP, ACAP)
• quadruple channel radio capacity
• 1 dual polariz. antenna with OMT and/or circulators depending on configuration.
In this configuration a single Ethernet logical channel with quadruple capacity is available on the radio ob-
tained by means of Layer 1 link aggregation of the 4 physical radio channels.
MN.00329.E - 007 25
5.4 ETHERNET SWITCH
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.
5.4.1 Ethernet interfaces
The following Ethernet interfaces are present:
• 6 external LAN interfaces (LAN 1-6) present in each version
• up to 4 interfaces that, depending on hw configuration (see paragraph 5.10 AVAILABLE VERSIONS),

can be digital (ETH) and/or analog (IF)
In Tab.2 are listed the technical parameters of the switch and in Fig.5 is represented the Ethernet block
diagram.
Tab.2 - Technical characteristics of the AGS-20 Switch
Technical characteristics of the layer 2 payload switch
Number of LAN ports Up to 10xGE
Maximum frame length 12266bytes software selectable
To be shared among all VLAN ba-

Address Learning capacity 16000 MAC entries
sed tables
MAC Aging Time 10 ÷ 1000000s software selectable
VLANs Stacking 802.1ad suppor-

802.1q VLANs Up to 256 (with VLAN ID: 0-4094)
ted
MEF EVCs Up to 128 Per port
Reserved/Shared between ports

Packet Buffer Total Size 96Mbytes
and queues
8 Output Ethernet Queue (Radio Queue depth is software selecta-

Up to 8 for each port
Side) ble
Queue Weight with scheduling Strict Priority, D-W.R.R., Strict Pri-

Software selectable
algorithm ority + D-W.R.R.
Per port, IEEE 802.1p, IPv4 ToS/

QoS Priority Classification Software selectable
DSCP
Queue Drop Type Tail Drop, RED, WRED
Ring Protection RSTP 802.1d-2004
Internal Synchronism Sources SyncE, E1/2MHz, Radio
Speed/Duplex auto negotiation Yes Software selectable
MDI / MDIX Yes Software selectable
26 MN.00329.E - 007
Up to 4 interfaces (Eth/IF)
depending on Hw version
Fig.5 – AGS-20 Ethernet block diagram
5.4.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.3
Tab.3 - Switch bridge modes
Bridge Mode (802.1ad) Description Components Port Types
The network element operates accor-

Customer Bridge (or “VLAN ding to 802.1q VLAN bridge. This mode
C-VLAN
bridge” or “C-VLAN bridge) is supported for compatibility with net-
works that do not manage the S-tag
A system comprising a single S-VLAN

Provider
component implemented in accordance S-VLAN only - Provider Network Port
Core Bridge
with clause 5 of IEEE Std 802.1q
Provider
Bridge - Provider Network Port
Switch operates as a 802.1ad provider
Provider S-VLAN and
edge bridge with S-VLAN component - Customer Network Port
Edge Bridge C-VLAN
and at least one C-VLAN component
- Customer Edge Port
5.5 DATA PLANE
In the next paragraphs are listed the Ethernet features offered by the switch of AGS-20.
MN.00329.E - 007 27
5.5.1 Ethernet features
5.5.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.5.1.2 MDI/MDI-X
For Electrical interfaces only, available values are MDI, MDI-X and Auto mode.
5.5.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:
• Acceptable Frame Types
- all: the port accepts all the following packets

- tagged: packet containing, in its header, one TPID identified as valid by the port, one VLAN
tag different from 0 and the field “User Priority”
- untagged: packet with a TPID not valid for the port
- priority tagged: packet with a TPID valid for the port, a VLAN tag equal to 0 and the field
“User Priority”
- 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.5.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).
Packets that exceed the configured MTU size are dropped.
This configuration can be either global for the Ethernet switch or assigned per port.
28 MN.00329.E - 007
5.5.1.5 Storm Control
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.
5.5.1.6 MAC Learning Rules
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.
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:
• specify which protocols shall be discarded, transparently tunneled or peered
• specify which frames are always sent to multicast port.

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
5.5.1.7 MAC Forwarding Rules
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
MN.00329.E - 007 29
• 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.
5.5.2 VLAN Forwarding
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).
5.5.2.1 IEEE 802.1q
The Ethernet switch supports the IEEE 802.1q VLAN management.
VLAN forwarding can be configured in two different ways, depending on incoming frames:
• 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.
5.5.2.2 VLAN Stacking - QinQ
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.
5.5.2.3 VLAN Threatment
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.
30 MN.00329.E - 007
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
- priority-tagged frames (VLAN ID = 0)

- C-tag frames in case the switch is in Provider Bridge Mode, as the frame is considered as untag-
ged (no S-tag)
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 ID and Ethertype are defined (0x8100 C-VLAN, 0x88A8 S-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.
5.5.2.4 Service Instance Mapping Criteria
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
MN.00329.E - 007 31
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-VID: assigned by the user (EVC identifier)
- 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
5.5.2.5 Ingress Manipulation
With CLI it’s possible to specify additional port :
- 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
5.5.3 QoS Management
QoS features available on Ethernet LAN and radio ports are summarized in Fig.6.
32 MN.00329.E - 007
Fig.6 – QoS block diagram
5.5.3.1 Classification with Priority Map
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)
The user can specify:
• the in-priority-type: L2 PCP or L3 IP-DSCP
• the input priority value (InPriority)
• the output queue value (Regen-Priority)
As default Layer 2 PCP 802.1p is enable on each port, with a 8-level default priority-map (from 0 to 7).
MN.00329.E - 007 33
The default 802.1p map, see Fig.7, cannot be removed but only modified.
Fig.7 - Default 802.1p PCP-queue map
The default Tos (DSCP) map is in Fig.8.
Fig.8 - Default ToS (DSCP) map
5.5.3.2 Classification with Class Map
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
• C-VLAN in customer bridge mode
• C-VLAN + C-PCP in customer bridge mode
• 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 for incoming double S-Tagged frames in provider bridge mode
34 MN.00329.E - 007
• 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.
Note: a class-map has a higher priority compared to a priority-map.
5.5.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.
Here below are the main parameters involved in this process:
• 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.5.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 type of service (e.g. voice, signaling, data, etc..)

• 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).
Metering is applied at ingress port.
The bandwidth profile classifies the service frames into 3 "colors", each denoting a certain compliance lev-
el:
• green – Frames within the CIR / CBS compliance level
• 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)
MN.00329.E - 007 35
• 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.
The actions that can be applied to not-compliant traffic are:
• yellow packets can be configured if to be immediately discarded or not
• 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.
5.5.4.2 Policy Map
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.
5.5.5 Congestion Avoidance
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:
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:
• DP (drop precedence) options are:
36 MN.00329.E - 007
- 0 – low drop precedence: green frames for TCP frames
- 1 – medium drop precedence: yellow frames for TCP frames
- 3 - low drop precedence: green frames for not-TCP frames
- 4 – medium drop precedence: yellow frames for not-TCP frames
• 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)
• mark-probability-denominator: max probability of discarding a packet in percentage (0 – 100%)

• 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.
Fig.9 – Red Curve
5.5.6 Output queues
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:
• full dynamic memory see Tab.4
• priority based memory allocation (1 radio port and 2 radio port) see Tab.5 and Tab.6
• uniform memory allocation (1 radio port and 2 radio ports) see Tab.7 and Tab.8
MN.00329.E - 007 37
• line ports dynamic memory see Tab.9
Tab.4 – Full dynamic memory
Parameter Type Buffer Size
Reference frame length [byte] 2048
Total reserved memory [Mbyte] 0
Total dynamic memory [Mbyte] 96
Radio ports reserved memory [Mbyte] 0
Radio ports dynamic memory [Mbyte] 17
Line ports reserved memory [Mbyte] 0
Line ports dynamic memory [Mbyte] 17
Tab.5 – Priority based memory (1 radio port)
Total reserved memory [Mbyte] 81.5
Total dynamic memory [Mbyte] 14.5
Radio ports reserved memory [Mbyte] 32,16,8,4,2,1,0.512,0.256
Line ports reserved memory [Mbyte] 0.512,0.256,0.128,0.064,0.032,0.032,0.032,0.032
Line ports dynamic memory per queue [Mbyte] 14
Tab.6 – Priority based memory (2 radio ports)
Radio ports reserved memory [Mbyte] 16,8,4,2,1,0.512,0.256,0.128
Radio ports dynamic memory [Mbyte] 8,4,1,1,0.750,0.200,0.200,0.200
Line ports reserved memory [Mbyte] 0.512,0.256,0.128,0.064,0.032,0.032,0.032,0.032
Line ports dynamic memory [Mbyte] 0.750,0.200,0.200,0.200,0.200,0.200,0.200,0.200
Tab.7 – Uniform memory (1 radio port)
Total reserved memory [Mbyte] 76.5
Total dynamic memory [Mbyte] 19.5
Radio ports dynamic memory [Mbyte] 4
Line ports reserved memory [Mbyte] 0.512
38 MN.00329.E - 007
Line ports dynamic memory [Mbyte] 4.3
Tab.8 – Uniform memory (2 radio ports)
Radio ports dynamic memory [Mbyte] 7.6
Line ports reserved memory [Mbyte] 0.256
Line ports dynamic memory [Mbyte] 4.2
Tab.9 – Line ports dynamic memory (2 radio ports)
Line ports reserved memory [Mbyte] 0
Line ports dynamic memory per queue [Mbyte] 17
5.5.7 Scheduling method
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.
5.5.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
MN.00329.E - 007 39
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
• burst-value: defines the maximum output burst in kbit
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.
Note: output rate limiter on queues acts before port rate-limiter.
5.5.9 Egress Manipulation
Per each port it’s possible to define the packet format to egress. In particular the actions that can be con-
figured are:
• no change in packet format
• remove outer tag, based on port criterion or port + VID criterion.
5.5.10 Packet Header Compression
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).
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.
40 MN.00329.E - 007
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.
Every row of the table corresponds to one radio port.
The lower part of the contextual area displays protocols and modes supported by the Parser of Header
Compression functionality as in Fig.10.
Fig.10 - WEBLCT Header Compression field
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:
• 16 bytes (up to 2048 contexts)
• 128 bytes (up to 256 contexts).

The parameter “Parsing Mode” indicates the modality used by the compressor to parse the header of the
Ethernet packets, done in a completely automatic way. The following modalities are supported:
• IPv4/IPv6 without C.W., EoMPLS with C.W.

• EoMPLS without C.W.
• Always IPv4/IPv6
The compressor considers the most outer header of the packet as Ethernet.
Supported protocols are:
• Ethernet, with the following assumptions:
- standard 802.1d, 802.1q (C-TAG), 802.1ad (S-TAG)
- 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
• Ethernet-over-MPLS (EoMPLS)
• IPv4 and IPv6

• UDP, TCP, RTP, GTP-U, IP Tunneling on GTP-U
MN.00329.E - 007 41
5.5.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:
• Maximum number of PW-Channels configurable per equipment: depends on IDU version
• VLAN tags available for PWE3 service configuration:
- all VLAN IDs (2-4094) can be used
- each bundle require a different VLAN ID
- the VLAN ID used for PWE3 cannot be used for other services
The Ethernet band required for a single PW-Channel depends on:
• 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)
• 2352 Kbit/s for MPLS (overhead of 34 bytes)
• 2512 Kbit/s for IPV4-UDP (overhead of 54 bytes)

• 2672 Kbit/s for IPV6-UDP (overhead of 74 bytes).
5.5.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:
• detection of loss or bad ordering of packets
• differentiation between PSN and attachment circuit problems as causes for emulated service outage
• PSN bandwidth conservation by not transferring invalid data (AIS)
• signalling of faults detected at the PW egress to the PW ingress
In Fig.11 is shown the PW Control Word by:
Fig.11 – PW Control Word structure
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:
• for ARI-1 IDU version ODU B
• 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.
42 MN.00329.E - 007
5.5.11.2 PWE3 in Customer Bridge mode
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:
• label: the bundle identifier

• 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:
- Ethernet (defined by MEF8)
- 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 MEF8 is set no other parameters are necessary
• if MPLS is set fills in MPLS outer label a correct value
• 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.
5.5.11.3 PWE3 in Provider Edge Bridge mode
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 - 007 43
5.6 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.6.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
In Fig.12 there is an example of ELP
Fig.12 – ELP between a SIAE AGS-20 and an external switch
5.6.2 Link Aggregation
Link Aggregation can be managed in different ways:
44 MN.00329.E - 007
• 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.
5.6.2.1 Layer 1 radio link aggregation
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:
• about 1% (for 1518 bytes packets)
• about 7% (for 64bytes packets)
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.6.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 - 007 45
• hashing: all the packets carried by the trunk are assigned to each physical channel depending on
the values of different parameters:
- source and destination MAC (DA) addresses
- VLAN ID
- ethertype
- switch port identifier

The decision is made by combining several bits of the previous frame fields through a XOR function
(three by three). The result of this function is a number between 0 and 7 that is used to decide over
which port of the bundle the frame has to be sent, starting from the first interface and increasing it
in a cyclic way. Maximum number of LAN involved is 8.
The LACP protocol has to be enabled on both sides to allow the communication through BPDUs necessary
to the protocol operation, so it is recommended to perform a prior interoperability check on both the units.
5.6.2.3 Static LAG
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.6.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:
• unidirectional LLF: the local LAN interface is forced in a LOS state

• bidirectional LLF: the device is able to communicate a LOS state to their counterpart, so that both
of them shut down the corresponding LAN interface
The most common applications are based on Bidirectional LLF.
5.6.3.1 Bidirectional LLF
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.
46 MN.00329.E - 007
5.6.3.2 Parameters in Bidirectional LLF
In LLF window (see Fig.13) in WEBLCT are present the following:
• 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).
Fig.13 – Select the LAN port that sends LLF status
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.14, the circuit is mainly identified by the following parame-
ters:
• circuit ID: from #1 to #8
• 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 - 007 47
Fig.14 – Select the circuit that manages the LLF protected LAN port
5.6.4 STP and RSTP
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:
• discarding - No user data is sent over the port

• learning - The port is not forwarding frames yet, but is populating its MAC-address-table
• forwarding - The port is fully operational.
5.6.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.
The operation of RSTP is as follows:
• 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.
48 MN.00329.E - 007
5.6.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.
5.6.4.3 Root Port Election
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.
5.6.4.4 Designated Port Election
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.
5.6.4.5 Alternate 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.
5.6.4.6 STP/RSTP Configurability
Common parameters (figure above):
• version: it can be set to “STP Compatible” or “RSTP Compatible”
• priority: field for the Root Bridge election. The switch with the smallest Priority is elected Root
Bridge
• Tx Hold Count: maximum number of transmitted BPDUs in 1 s (settable between 1 and 10 s)
• 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 - 007 49
• 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).
The convergence time of the protocol depends on different factors:
• number of bridges that are involved in the re-configuration
• 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.7 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
• T2, represents an E1 signal carrying traffic as input interface
• T1, represents a STM-1 signal carrying traffic as input interface
• T0, represents the internal clock as output interface.
5.7.1 Sources
The selectable sources of synchronization are listed and explained below:
• T3-SYNC, configurable as a no traffic channel of 2Mbit/s or 2MHz on RJ-45
- 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)
50 MN.00329.E - 007
• 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”
• T1 STM1, one of the STM-1 (T1 A -> STM-1 1, T1 B -> STM-1 2)

• Internal Clock: with the Synchronization not enabled the IDU is locked into its internal clock (SETS).
5.7.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
- 2 Mbit/s: this option allows to provide an E1 CK signal to an external equipment. It is a framed

E1 (G.704 framed) created locally with AIS
• Radio (i.e. ODU/LAN A, B, C, D): the synchronism is transmitted independently on each remote ra-
dio interface (up to two IF interfaces and two GbE optical interfaces in case of AGS-20)
• 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.7.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 - 007 51
5.7.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)
• SSUT: Synchronization Supply Unit Transit (Rubidium Clock)
• SSUL: Synchronization Supply Unit Local

• SEC: SDH Equipment Clock (Cristal Clock)
• DNU: Do not Use – This signal informs the receiver to do not use this clock.
The quality procedure can be enable or disable in unit WEBLCT:
• 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:
• it chooses the sources with the highest quality
• 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.
5.7.5 Source settings
The quality of the synchronism has to be enabled for each unit and can be transported on the following
interfaces:
• on the Spare bits on the TS 0 of an E1
• on the Ethernet Interfaces through a standard protocol (according to ITU-T G.8264)
• on the radio interface within Ethernet packets.
Maintenance configurations are available:
• 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.
Relating to SSM, it is possible:
• visualize Rx Quality and Tx Quality
• overwrite Rx Quality and Tx Quality selecting a choices in the quality list.
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.
52 MN.00329.E - 007
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.
5.7.6 Ethernet Interfaces
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.
5.8 ETHERNET MAINTENANCE
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.8.1 OAM
Through CLI interface, OAM configuration is available on all Ethernet interfaces, regardless of their physical
port connection.
Main concepts are:
• 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 - 007 53
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)
- to perform a bi-directional in-service or out-of-service diagnostics test between a pair of peer

MEPs. This includes verifying bandwidth throughput, detecting bit errors, and so on (unicast
LBM).
• Link Trace Protocol: it is a message similar to the Loopback. Every equipment reached by this mes-
sage answers to the sender providing its own MAC Address. In this way the sender knows its MA
composition.
Five types of alarm are available MEP side:
• cross-connect: the MEP is receiving CCMs from other MA/Level/Domain
• 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.
54 MN.00329.E - 007
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.8.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 implementation in SIAE Network Elements is classified into two groups:
• 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.
5.8.2.1 Ethernet Statistics
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:
- from 1 to 3600 s, (persistence of the results is disabled)
- 60, 300, 600, 900, 1800, 3600 s, (persistence of the results is enabled).
MN.00329.E - 007 55
In general, if the 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.
5.8.2.2 RMON Counters in each interface
• 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
• 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).
5.8.2.3 Ethernet Services Statistics
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)
56 MN.00329.E - 007
• 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
• on each equipment an History collection can be set for up to 40 different VLANs.
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
• pkts Tx: total number of packets transmitted
• octets Rx: total number of octets of data (including those in bad packets) received by the interface
• 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.9 PROGRAMMABILITY
AGS-20 radio system is managed by a microprocessor that makes it totally programmable via software to
perform the following functions:
• radio link management
- bandwidth and modulation
- ACM engine configuration
- link ID
- Tx frequency and power
- ATPC (Automatic Transmission Power Control)
• main management
- IP port configurable and supervisioning
- routing table
- remote element list

- alarm severity configuration (modify alarm)
- user manager (password, user Privilege level, authentication, SNMP login)
- SNMP V.1/V.2/V.3 compatible
MN.00329.E - 007 57
- Security Management (SSH, SFTP)
- Secure HTTP access (HTTP)
• operation and maintenance
- permanent Tx Off
- Rx signal threshold alarm
- performance monitoring (G.828, Rx PWR, Tx PWR, ACM Ethernet Statistic Rmon) with alarm
threshold
- S/N measure
- LAN summary, statistic basis on port, VLAN or Priority
- backup/restore configuration
- software update
- report&logger maintenance (inventory, fault, commands)
- SNTP alignment
• manual operations (depends on timeout)

- Tx transmitter OFF
- force switch synch
- radio BER test
- RF and IF modem loop
- 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.9.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 hardware platform is based on PC at least the following characteristics:
• HD with 200 Mbyte of free space
• Windows XP/Windows 7 (WLC), UNIX or LINUX (NMS5UX/LX).
The network management system (NMS5LX/UX) functionalities, WebLCT and the Console Line Interface
(CLI) are widely described in the separated relevant manual.
1 Not working in actual system version.
58 MN.00329.E - 007
5.10 AVAILABLE VERSIONS
Depending on hardware and system version, the following AGS-20 versions are available:
• AGS-20 SINGLE IF/16E1 (SYV 1.1) GAI0214-1
• AGS-20 SWITCH (SYV 1.1) GAI0212-1

• AGS-20 SINGLE IF (SYV 1.1) GAI0213-1
• AGS-20 DUAL IF (SYV 1.1) GAI0215-1
• AGS-20 DUAL IF/16E1 (SYV 1.1) GAI0216-1
• AGS-20 QUAD ETH (SYV 1.2) GAI0222-2
• AGS-20 QUAD ETH/16E1 (SYV 1.2) GAI0223-2
• AGS-20 DUAL IF (SYV 1.3) GAI0215-2
• AGS-20 DUAL IF/16E1 (SYV 1.3) GAI0216-2
• AGS-20 PP SINGLE IF/16E1 (SYV 1.3) GAI0225-1
• AGS-20 DUAL IF/16E1+2STM1+NODAL (SYV 1.4) GAI0217-2
• AGS-20 SINGLE IF/16E1+2STM1+NODAL (SYV 1.4) GAI0218-1
• AGS-20 QUAD ETH/16E1+2STM1+NODAL (SYV 1.4) GAI0224-2
• AGS-20 PP SINGLE IF/16E1+2STM1+NODAL (SYV 1.4) GAI0226-1
• AGS-20 QUAD IF (SYV 1.5) GAI0219-1
• AGS-20 QUAD IF/16E1 (SYV 1.5) GAI0220-1
• AGS-20 QUAD IF/16E1+2STM1+NODAL (SYV 1.5) GAI0221-1
All the AGS-20 versions have the following functionalities:
• 2x GE (1Gbps electrical ports @ RJ-45 connector)
• 2x Optical (1Gbps or 2.5 Gbps optical Ports @ SFP connector)
• 2x COMBO (1Gbps electrical @ RJ-45 or 1Gbps optical @ SFP)
• 1x RJ45 Local Access

• 1x Console (@ RJ-45 connector)
• 1x SYNK-E1 (@ RJ-45 connector)
• Synchronization (Sync-E; 1588v2)

• 1x ToD (@ RJ-45 connector)
• 1x PPS (@ 1.0/2.3 microSIEMENS connector)
• Housekeeping alarm interface (@ RJ-45 connector)
• SD card expansion
• Front panel R button for software reset.
5.10.1 AGS-20 switch
In Fig.15 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.
MN.00329.E - 007 59
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
Fig.15 - AGS-20 switch (GAI0212-1)
5.10.2 AGS-20 Single IF
In AGS-20 Single IF (see Fig.16) the following functionalities are available:
• modem section with ACM
• IF connectivity compatible with BEP 2.0 Outdoor Units (ASN/ASNK)

• Ethernet connectivity compatible with SIAE Full-Outdoor (ALFOplus80, ALFOplus80HD, ALFOplus,
ALFOplus2, etc....)
• 1x IF (compatible with current SIAE ODU)
• 2x Optical (1Gbps or 2.5Gbps optical @ SFP)
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
Fig.16 - AGS-20 Single IF (GAI0213-1)
5.10.3 AGS-20 Single IF/16E1
In AGS-20 Single IF/16E1 (see Fig.17) the following functionalities are available:

ALFOplus2, etc....)
• 16x E1 (@ 2x SCSI connectors).
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
Fig.17 - AGS-20 Single IF/16E1 (GAI0214-1)
5.10.4 AGS-20 Dual IF
In AGS-20 Dual IF (see Fig.18) the following functionalities are available:
60 MN.00329.E - 007
• radio interface protection and L1 aggregation

ALFOplus2, etc....)
• double power connector.
Fig.18 - AGS-20 Dual IF (GAI0215-2)
5.10.5 AGS-20 Dual IF/16E1
In AGS-20 Dual IF/16E1 (see Fig.19) the following functionalities are available:

ALFOplus2, etc....)
• 16x E1 (@ 2xSCSI connectors)

Fig.19 - AGS-20 Dual IF/16E1 (GAI0216-2)
5.10.6 AGS-20 Quad ETH
In AGS-20 Quad Eth (see Fig.20) the following functionalities are available:

ALFOplus2, etc....)
• 2x COMBO (1Gbps electrical @ RJ45 or 1Gbps optical @SFP) with PoE functionalities
MN.00329.E - 007 61
POE POE LAN C LAN D
LAN A LAN B LCT 2

URG 1PPS
NURG R ON
1
SW
TEST SYNC Console 48V „ª
2 2 4 6 M 10A
1 LAN 1 LAN 3 LAN 5 TOD ALARM 250V -+
Fig.20 - AGS-20 Quad ETH (GAI0222-2)
5.10.7 AGS-20 Quad ETH/16E1
In AGS-20 Quad Eth/16E1 (see Fig.21) the following functionalities are available:

ALFOplus2, etc.....)
• 2x COMBO (1Gbps electrical @RJ45 or 1Gbps optical @SFP) with PoE functionalities
• 2x Optical (1Gbps or 2.5Gbps optical @SFP)
• 16xE1 (@ 2x SCSI connectors)

POE POE LAN C LAN D
LAN A LAN B LCT 2

URG 1PPS
NURG R ON
1
SW
Trib. 1-8 Trib.9-16 2 2 4 6 M 10A
Fig.21 - AGS-20 Quad ETH/16E1 (GAI0223-2)
5.10.8 AGS-20 PP Single IF/16E1
In AGS-20 PP Single IF/16E1 (see Fig.22) the following functionalities are available:
• IF connectivity compatible with BEP 2.0 outdoor units (ASN/ASNK)
• Ethernet connectivity compatible with SIAE Full-Outdoor (ALFOplus80, ALFIplus80HD, ALFOplus,

ALFOplus2, etc....)
• 1xIF (compatible with current SIAE ODU)
• 2xOptical (1Gbps or 2.5Gbps optical @ SFP
• 16xE1 (@ 2xSCSI connectors)
Fig.22 - AGS-20 PP Single IF/16E1 (GAI0225-1)
62 MN.00329.E - 007
5.10.9 AGS-20 Dual IF/16E1 + 2STM1 + Nodal
In AGS-20 Dual IF/16E1 + 2STM1 + Nodal (see Fig.23) the following functionalities are available:

• 2xoptical (1Gbps or 2.5 Gbps optical @SFP)
• 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
Fig.23 - AGS-20 Dual IF/16E1 + 2STM1 + Nodal (GAI0217-2)
5.10.10 AGS-20 Single IF/16E1 + 2STM1 + Nodal
In AGS-20 PP Single IF/16E1 + 2STM1 + Nodal (see Fig.24) the following functionalities are available:
• Ethernet connectivity compatible with SIAE full-outdoor (ALFOplus80, ALFOplus80HD, ALFOplus,

ALFOplus2, etc....)
• 2xOptical (1Gbps or 2.5Gbps optical @SFP)
• 16xE1 (@2xSCSI connectors)
• TDM cross-connect matrix for TDM routing line and radio side

2
• 2xNodal Bus (NBUS1 and NBUS2) for TDM routing between adjacent IDUs.
Fig.24 - AGS-20 single IF/16E1 + 2STM1 +Nodal (GAI0218-1)
2 Not working in actual system version.
MN.00329.E - 007 63
5.10.11 AGS-20 Quad Eth/16E1 + 2STM1 + Nodal
In AGS-20 Quad Eth/16E1 + 2xSTM1 + Nodal (see Fig.25) the following functionalities are available:

ALFOplus2, etc....)
• 2xCOMBO (1Gbps electrical @RJ45 or 1Gbps optical @SFP) with PoE functionalities
• 2xNodal Bus (NBUS1 and NBUS2) for TDM routing between adjacent IDUs. 2
Fig.25 - AGS-20 Quad Eth/16E1 + 2STM1 + nodal (GAI0224-2)
5.10.12 AGS-20 PP Single IF/16E1 + 2STM1 + Nodal
In AGS-20 PP Single IF/16E1 + 2STM1 + Nodal (see Fig.26) the following functionalities are available:

• Double power connector
• 2xNodal Bus (NBUS1 and NBUS2) for TDM routing between adjacent IDUs 2
Fig.26 - AGS-20 PP Single IF/16E1 + 2STM1 + Nodal (GAI0226-1)
64 MN.00329.E - 007
5.10.13 AGS-20 Quad IF
In AGS-20 Quad IF (see Fig.27) the following functionalities are available:
Fig.27 - AGS-20 Quad IF (GAI0219-1)
5.10.14 AGS-20 Quad IF/16E1
In AGS-20 Quad IF/16E1 (see Fig.28) the following functionalities are available:

Fig.28 - AGS-20 Quad IF/16E1 (GAI0220-1)
5.10.15 AGS-20 Quad IF/16E1 + 2STM1+ Nodal
In AGS-20 Quad IF/16E1 + 2STM1 + Nodal (see Fig.29) the following functionalities are available:


2
• 2xNodal Bus (NBUS1 and NBUS2) for TDM routing between adjacent IDUs
MN.00329.E - 007 65
Fig.29 - AGS-20 Quad IF/16E1 + 2STM1 + Nodal (GAI0221-1)
5.11 SUPPORTED ODUS
The following ODUs can be connected to AGS-20 by means of ARI interface (IF interface):
• ASN
• ASNK.
5.12 SUPPORTED FULL ODUS
The following Full ODUs can be connected to AGS-20 by means of DRI interface (Ethernet interface):
• ALFOplus
• ALFOplus80HD
• ALFOplus2.
66 MN.00329.E - 007
6 TECHNICAL SPECIFICATIONS
6.1 IDU INTERFACES
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
6.1.1 Traffic interfaces
The traffic interfaces on front panel are the following:
• E1
• STM-1 3
• Ethernet (electrical and optical)
• ARI (IF analog interface towards SIAE ODUs)

• DRI (digital optical interface towards SIAE Full ODUs)
• Combo (similar to previous DRI but can be electrical or optical)
6.1.1.1 E1 (Connector Trib.1-8, Trib.9-16)
- Connector type SCSI 50 pin
Input side
- Bit rate 2048 kbit/s ±50 ppm
- Line code HDB3
- Rated impedance 75 Ohm or 120 Ohm
- Rated level 2.37 Vp/75 Ohm or 3 Vp/120 Ohm
- Return loss 12 dB from 57 kHz to 102 kHz

18 dB from 102 kHz to 2048 kHz
14 dB from 2048 kHz to 3072 kHz
- Max attenuation of the input cable 6 dB according to trend

- Accepted jitter see Tab.2, CCITT Rec. G.823
- Transfer function see Fig.1, CCITT Rec. G.742
Output side
3 Depending on roadmap availability.
MN.00329.E - 007 67
- Bit rate 2048 kbit/s ±50 ppm
- Rated impedance 75 Ohm or 120 Ohm
- Rated level 2.37 Vp/75 Ohm or 3 Vp/120 Ohm
- Output jitter according to G.742/G.823
- Pulse shape see Fig.15, CCITT Rec. G.703.
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.
6.1.1.2 STM-1 electrical 4
Input side
• Bit rate 155520 kbit/s ±4.6 ppm
• Line code CMI
• Rated impedance 75 Ohm
• Rated level 1 Vpp ±0.1V

• Return loss 15 dB from 8 MHz to 240 MHz
• Max attenuation of the input cable 12.7 dB at 78 MHz ( f trend)
Output side
• Bit rate 155520 kbit/s ±4.6 ppm
• Rated level 1 Vpp ±0.1 V

• Pulse shape see Fig. 24 and Fig. 25 of ITU-T Rec. G.703
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.10.
Tab.10 - Optical interface characteristics
Minimum
Launched Operating Distance
Interface Ref. sensitivity Transceiver Fibre
power (dBm) wavelength (km)
(dBm)
L-1.2 G.957 0 ... -5 -34 1480 - 1580 Laser Single-Mode Up to 80
L-1.1 G.957 0 ... -5 -34 1263 - 1360 Laser Single-Mode Up to 40
S-1.1 G.957 -8 ... -15 -28 1263 - 1360 Laser Single-Mode Up to 15
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.
4 Depending on roadmap availability.
68 MN.00329.E - 007
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).
- Connector type RJ45 IEEE 10/100/1000BaseT
- Max bitrate 1 Gbps.
All the ports can be set UNI or NNI and used as DCN. By default LAN3 port is set as DCN.
6.1.1.5 Optical Ethernet (Ports LAN1, LAN2, LAN5, LAN6)
Ports LAN1 and LAN2 are COMBO interfaces and can use electrical or optical interface (software configur-
able).
- Max bitrate 1 Gbps
- Connector type SFP LC, see Tab.11
Ports LAN5 and LAN6 have optical interface only
- Max bitrate 1Gbps (2.5 Gbps if connected to SIAE

ALFOplus80HD, ALFOplus2, AGS-20)
All the ports can be set UNI or NNI.
Tab.11 - SFP transceiver
Operating
Interface Ref. Link budget Wavelength Fibre Distance
(nm)
Gigabit Ethernet IEEE

850 Multimode Up to 2km
1000BaseSx 802.3z

9.5dB 1310 Single Mode Up to 10km
1000BaseLx 802.3z

19dB 1310 Single Mode Up to 40km
1000BaseLx 802.3z

25dB 1550 Single Mode Up to 80km
1000BaseLx 802.3z
6.1.1.6 ARI (Connector ODU A, ODU B, ODU C, ODU D)
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.
Electrical characteristics are:
- Cable length 300m
- Cable rated impedance 50 Ohm
- Signal running along the cable
- Tx nominal frequency 330 MHz
- Rx nominal frequency 140 MHz
- Telemetry IDU -> ODU 17.5 MHz
MN.00329.E - 007 69
- Telemetry ODU -> IDU 5.5 MHz
- Transceiver management signals 388 kbit/s bidirectional
- Remote power supply voltage direct from battery voltage
6.1.1.7 DRI (Connector LAN C, LAN D)
DRI (Digital Radio Interface) are optical Ethernet interfaces:
- Max bitrate 1Gbps (2.5 Gbps if connected to SIAE

ALFOplus80HD, ALFOplus2, AGS-20)
Optical interfaces are connected through SFP pluggable transceiver with LC type connector. Ports can be
set UNI or NNI.
6.1.1.8 COMBO (Connector LAN A, LAN B)
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
- Max bitrate 1 Gbps
Electrical interface
- Max bitrate 1Gbps
- Connector type IEEE 802.3 10/100/1000BaseT RJ45

- PoE
- Output voltage 54 Vdc
- Max current 1.7 A
Ports can be set UNI o NNI.
6.1.2 Service interfaces
6.1.2.1 LCT
- Connector type RJ45 IEEE 10/100BaseT
- Max bitrate 100 Mbps
6.1.2.2 Alarm
Dedicated RJ45 (Housekeeping Alarm Interface) for primary alarm report.
70 MN.00329.E - 007
User IN: typical Open/GND:
• OPEN or Vin > 1.5V -> Alarm
• GND or Vin < 0.5V -> No Alarm.
Alarm/No-alarm state is user configurable by LCT.
Tab.12 - Alarm characteristics
Contact ratings Maximum switching power 30W (resistive) 37.5VA (resistive)
Maximum switching voltage 220Vdc 250Vac
Maximum switching current 1A
Maximum carrying current 1A
6.1.2.3 Console
Serial connection with RJ45 connector for console access.
- Serial connection parameters 115200 bps 8-N-1-N
6.1.2.4 SYNC (SYNC-1 interface)
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.
6.1.2.5 ToD (SYNC-2 interface)
Dedicated RJ45 for application where Time of Day is required.
6.1.2.6 1PPS (SYNC-3 interface)
1PPS (Pulse Per Second) interface is used for timing services required in access network.
The interface is available with a 1.0/2.3 microSIEMENS connector.
6.1.3 Optical indications
6.1.3.1 System LEDs
On the front panel 4 LEDs are present. They summarize status and alarms, see Tab.13.
MN.00329.E - 007 71
Tab.13 - Front panel system LEDs
Name Colour State/Alarm Function
NURG Red Active when ON Minor alarm
URG Red Active when ON Major alarm
SW Red Active when ON System mismatch alarm
TEST Yellow Active when ON Manual test ongoing
ON Green Active when ON Power ON
6.1.3.2 Ethernet interface activity
Link/Active indication is close to relevant connector for each electrical or optical Ethernet interface, see
Tab.14.
Tab.14 - Electrical/Optical Ethernet interface status LEDs
Name Colour State/Alarm Function
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
OFF = Link down

Link/Active Green ON = Link up wo/ activity Data presence on Tx or Rx
Blink/s = Link up w/activity
6.1.3.3 PoE LEDs
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.15).
Tab.15 - Meaning of PoE LEDs
Alarm LED (Red) Power LED (Green) Meaning
On On Cable open
Off On PoE OK
On Off Cable short circuit
Off Off PoE off
6.1.4 Modulation, bandwidth and relevant capacity
For each radio channel the supported bandwidth and modulations are the following:
Bandwidth
• ETSI: 7 MHz, 14 MHz, 28 MHz, 40 MHz and 56 MHz
72 MN.00329.E - 007
• ANSI: (future evaluation)
Modulation
ACM is supported, characteristics are:
• 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
• Each modulation profile can be set as reference profile
Two groups of profile setting are configurable by operator:
• 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.
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
ATPC and ACM interaction
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.
MN.00329.E - 007 73
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):
- IDU GAI0212-1 < 29W; < 0.6A
- IDU GAI0213-1 < 48W; < 1A
- IDU GAI0214-1 < 55W; < 1.15A
- IDU GAI0215-2 < 63W; < 1.3A
- IDU GAI0216-2 < 70W; < 1.45A
- IDU GAI0222-2 < 48W; < 1A
- IDU GAI0223-2 < 55W; < 1.15A
- IDU GAI0225-1 < 55W; < 1.15A
- IDU GAI0217-2 < 80W; < 1.65A

- IDU GAI0218-1 < 65W; < 1.35A
- IDU GAI0224-2 < 65W; < 1.35A
- IDU GAI0226-1 < 65W; < 1.35A

- IDU GAI0219-1 < 87W; < 1.8A
- IDU GAI0220-1 < 94W; < 1.95A
- IDU GAI0221-1 < 104W; < 2.15A.
Power characteristics are listed below:
- Power-on voltage threshold -28Vdc
- Normal service voltage range extended voltage range -38.4 Vdc to -57.6 Vdc
- Maximum steady reverse voltage 100Vdc
- Maximum reverse current 1mA
- Fuse
- Nominal current depends on hw version
- Nominal voltage 250 Vac/dc
- Type medium timed M

- Dimensions 5mmx20mm
6.1.6 PoE - Power over Ethernet
PoE functionalities are available on RJ45 connector of LAN A and LAN B of the following AGS-20 versions:
• AGS-20 QUAD ETH (GAI0222-2)
• AGS-20 QUAD ETH/E1 (GAI0223-2)
• AGS-20 QUAD ETH/E1 + 2STM1 + Nodal (GAI0224-2).
6.1.6.1 PoE characteristics
PoE functionalities can be enabled at the same time on LAN A and LAN B.
Characteristics are:
• max power available on each port 85W
74 MN.00329.E - 007
• max voltage available in output 55 Vdc
• max cable length 100m
• overcurrent protection common on both the ports.
6.1.6.2 PoE settings
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 IDU general characteristics
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)
- Width 442mm without brackets and

481mm with brackets
- Depth 223mm
6.1.7.2 Weight
Weight of AGS-20 IDU is 2.8 kg or less according to versions.
6.1.7.3 Environment conditions
- IDU operating temperature -5°C to +45°C for GAI0XXX-1

-5°C to +55°C for GAI0XXX-2
- ODU operating temperature -33°C to +55°C
- IDU survival temperature -10°C to +55°C
- IDU maximum acoustic noise 48 dBSPL
- ODU survival temperature -40°C to +60°C
- ODU operating humidity 95% at 35°C
- ODU operating condition according to IP65
- ODU dissipation thermal resistance 0.5° C/W

- ODU solar heat gain < 5°C
- ODU max height 4000m
- Storage condition according to T.1.2 ETSI EN 300 019-1-1 (weather

protected, not temperature controlled storage
locations)
MN.00329.E - 007 75
6.2 AVAILABLE ODUS AND FULL ODUS
6.2.1 ODUs
In Tab.16 are listed the ODUs that can be connected to ARI ports.
Tab.16 - ODUs that can be connected to AGS-20
ODUs 4QAM/256QAM 512QAM/1024QAM 2048QAM
ASN (after test) Available Only with feature upgrade Not available
ASNK Available Available Available
6.2.2 Full ODUs
The full ODUs that can be connected to DRI ports are:

• ALFOplus
• ALFOplus80HD
• ALFOplus2
6.3 ODUS, DESCRIPTION AND TECHNICAL CHARACTERISTICS
6.3.1 ODU description
6.3.1.1 ODU versions
Two ODU versions are available: ASN and ASNK.
In the following pages eventual differences are pointed out.
The ODU (refer to Fig.30) consists of a two shell aluminium mechanical structure, one shell housing all the
ODU circuits, the other forming the covering plate.
On the ODU are accessible:
• 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.
76 MN.00329.E - 007
ASN ODU
The ASN ODU is shown in Fig.30 (single ODU) and in Fig.31 (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.31 (single ODU with F15 GHz) and in Fig.32 (single ODU with F15 GHz).
Electrical and mechanical characteristics are listed in a separate addendum relevant to ODU frequency.
6.3.1.2 Description
The blocks that arrange the ODU are the following:
• cable interface
• power supply
• Tx section
• Rx section
• 1+1 branching unit
6.3.1.3 IF cable interface
The cable interface permits to interface the IF cable interconnecting IDU to ODU and viceversa.
It receives/transmits the following signals:
• 330 MHz (from IDU to ODU)
• 140 MHz (from ODU to IDU)
• 17.5 MHz (from IDU to ODU)

• 5.5 MHz (from ODU to IDU)
• remote power supply.
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.
6.3.1.4 Power supply
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
Refer to block diagram shown in Fig.33.
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.
MN.00329.E - 007 77
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 detector diode to measure the output power
• a circulator to protect the amplifier stages
• a ON/OFF switch for 1+1 operation
• an RF passband filter for antenna coupling.
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.36) 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.
The maximum ATPC range depends on the ODU type.
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.
6.3.1.7 1+1 Tx system
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.34 and
Fig.35.
The transmitter switchover is controlled by Processor and the attenuation of the stand-by transmitter is
at least 50 dB.
78 MN.00329.E - 007
Reference tooth
O-ring
ODU side flange
ASN version
ASNK version (for frequency ≤ 15 GHz)
"N"
"BNC"
Ground bolt
Fig.30 - ASN or ASNK ODU
MN.00329.E - 007 79
ASN version
Suncover (optional) ASNK version (for frequency ≤15 GHz)
Fig.31 - Final 1+1 assembly with ASN or ASNK ODU
80 MN.00329.E - 007
ODU 1+0
ODU 1+1 (Standard lock)
Fig.32 - ASNK ODU (for frequency > 15 GHz)
MN.00329.E - 007 81
82
PTx att.
control
Vdc 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
MOD Alarm Alm Tx LO

388 manag comm
5.5 kbit/s MUX Tx
5.5 loops
MHz MHz DEMUX &
ctrl ctrl
control IF LO
DEM unit µP
BNC REC
17.5 17.5 388
17.5 MHz kbit/s Rx antenna
MHz
MHz side
PRx
meas.
Fig.33 - ODU block diagram

ctrl
IF Rx
140 LNA
MHz
variable 140
µP bandwidth MHz
(capacity Rx LO
depending)
AGC
µP
MN.00329.E - 007
Tx side
SW control
Rx side
Antenna
side
Tx side
SW control
Rx side
Fig.34 - 1+1 hot stand–by 1 antenna
Tx side
SW control
First
antenna
Rx side
Tx side
SW control
Second
antenna
Rx side
Fig.35 - 1+1 hot stand–by 2 antennas
MN.00329.E - 007 83
Remote PRx
dBm
Local Remote
Tx Rx
Thresh High
PTx actuation PRx recording
Thresh Low level
μP μP
PTx control
Transmission
Rx Tx
of PTx control
Hop attenuation (dB)
Local PTx
dBm
PTx max.
30 dB (ODU ASNK)
20 dB (ODU ASN)
ATPC range
PTx min.
Hop attenuation (dB)
Fig.36 - ATPC operation
6.3.1.8 Full ODUs, description and technical characteristics
Full ODU description
See manual of the relevant Full ODU.
Full ODU characteristics
84 MN.00329.E - 007
See manual of the relevant Full ODU.
MN.00329.E - 007 85
86 MN.00329.E - 007
Section 3.
INSTALLATION
7 INSTALLATION AND PROCEDURES FOR ENSUR-

ING THE ELECTROMAGNETIC COMPATIBILITY
7.1 GENERAL INFORMATION TO BE READ BEFORE THE INSTALLA-

TION
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.
The equipment is composed by the following separate units:
• radio unit (outdoor) with or without integral antenna
• Baseband (indoor)
Warning: This equipment makes use of non-harmonized frequency bands.
Warning: Class 2 radio equipment subject to Authorisation of use. The equipment can operate only at the
frequencies authorised by the relevant National Authority.
Warning: The deployment and use of this equipment shall be made in agreement with the national regu-
lation for the Protection from Exposure to Electromagnetic Field.
Warning: The symbol indicates that, within the European Union, the product is subject to separate
collection at the product end-of-life. Do not dispose of these products as unsorted municipal waste. For
more information, please contact the relevant supplier for verifying the procedure of correct disposal.
MN.00329.E - 007 87
7.2 GENERAL
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 MECHANICAL INSTALLATION
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.
7.3.2 IDU installation
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.
7.4 ELECTRICAL WIRING
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.17 shows the characteristics of the cables to be used and the flying connector types.
88 MN.00329.E - 007
Tab.17 - Characteristics of the cables
Type of connector terminating the

Interconnecting points Type of cable/conductor
cable
Max section of each wire =

Battery 3 pin P04184
1.5 sq.mm a b
8 conductor cable different

Tributary signals SCSI 50 pin male connector for 75 Ohm and 120 Ohm
signals
Alarm RJ45 Standard CAT5 cable
LCT RJ45 Standard CAT5 cable
F035998 - 0.3m superflex

F03597 - 0.5m
NBUS RJ45 F03580 - 0.75m
F03581 - 1m
F03592 - 2.95m
STM1 Plug-in Relevant to plug-in module
Optical LAN port Plug-in Relevant to plug-in module
Electrical LAN port RJ45 Standard CAT5 cable
Console RJ45 F03588
GND Faston male type Section area  6 sq. mm.
a. Select the correct size and type of cable for any installation case according to specific
length.
b. Power cable operative temperature  60°C.
7.5 OPTICAL CONNECTORS
In case of necessity of optical connectors, please use the optical plug-in modules supplied by SIAE. Ask
SIAE Microelettronica for different modules.
7.6 CONNECTIONS TO THE SUPPLY MAINS
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.
MN.00329.E - 007 89
7.7 IDU-ODU INTERCONNECTION CABLE
7.7.1 Electrical characteristics
- Cable type coaxial
- Cable impedance 50 ohm
- Insertion loss 24 dB at 330 MHz

- Return loss (connectors included) better than 22 dB (from 100 MHz to 400 MHz)
- Max total DC resistance 4 Ohm
- Shielding effectiveness 90 dB
7.7.2 Connectors
N-type male connectors on both sides.
7.7.3 Max length
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.
7.7.4 Suggested cable
RG8 or 1/4” cable on any coaxial cable that respect the previous electrical characteristics.
90 MN.00329.E - 007
7.8 GROUNDING CONNECTION
Fig.37 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
Fig.37 - Grounding connection
7.9 IDU-ODU CABLE GROUNDING KIT INSTALLATION
7.9.1 Grounding kit K09283F (for RG8 or 1/8” cable)
The kit is made up by:
• grounding kit
• sealant (in a small sachet)
• a short tape (to define the part of the jacket to remove from the cable)
MN.00329.E - 007 91
• a transparent plastic bag, with instructions printed over, which contains all the items.
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:
• self amalgamating waterproof tape against water and moisture
• black PVC tape against sun UV
Procedure for both tapes:
• 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.
• every wrapping must overlap the previous.
The grounding bolt (opposite to the grounding clamp of the kit) must remain without sealing.
7.9.2 Grounding kit ICD00072F (for any cable with shield)
Fig.38
The kit is made up by:
• a copper plate connected to a M8x20 grounding bolt
• 50 cm of tin copper tube of 3mm of diameter
• 30 cm of vinyl mastic self amalgamating waterproof tape
• 2 m of black PVC tape against sun UV.
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).
The installation procedure is the following:
1. remove 52mm of jacket from the cable that has to be grounded
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
92 MN.00329.E - 007
3. the grounding kit must be placed as Fig.39 (the plate copper bar must be higher point of the ground-
ing 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.39. Every wrapping must overlap the previous.
6. Apply two layers of black PVC UV proof tape overlapping the waterproof tape layers as in Fig.39.
Every wrapping must overlap the previous.
7. Insert the grounding bolt in the closest grounding point.
The grounding bolt (opposite to the grounding clamp of the kit) must remain without sealing.
Fig.39 - Grounding kit positioning
7.10 SURGE AND LIGHTNING PROTECTION
Gas dischargers are present both in IDU and ODU.
Characteristics
- DC spark-over voltage 150V ±20%
- Nominal impulse discharge current (wave 8/20 ms) 20kA
- Single impulse discharge current (wave 8/20 ms) 25kA
- Performances in accordance to EN 301 489.
MN.00329.E - 007 93
8 CONNECTORS
The front panel of the AGS-20 depends on the selected version. Available versions are shown in paragraph
5.10 AVAILABLE VERSIONS.
8.1 CONNECTORS
- Ethernet LAN1 and LAN2 COMBO (it can be electrical or optical)
- Ethernet LAN3 and LAN4 electrical RJ45

- Ethernet LAN5 and LAN6 optical SFP 1 Gbps or SFP 2.5 Gbps (proprietary)
- Ethernet LANA and LANB COMBO
- Ethernet LANC and LAND optical SFP 1 Gbps or SFP 2.5 Gbps (proprietary)
- Ethernet electrical, 10/100/1000BaseT RJ45 (see Tab.18)
- Ethernet optical
1000BaseSX/1000BaseLX SFP LC
- Trib 1-8, 75 Ohm and 120 Ohm E1 in/out 50 pin SCSI female
(Tab.19 for 75 Ohm and Tab.20 per 120 Ohm)
- Trib 9-16, 75 Ohm and 120 Ohm E1 in/out 50 pin SCSI female
(Tab.19 for 75 Ohm and Tab.20 per 120 Ohm)
E1, 75 Ohm and 120 Ohm interfaces are present in the same connector (with different pins).
- Connector for 50 Ohm interconnection

to ODUA and ODUB SMA (max tightening torque=0.5 Nm)
5
- -48 Vdc power supply Green connector (pinout on the panel) P04184
- LCT local management (Ethernet) RJ45 (see Tab.18)
- Synk-1 synchronization in/out RJ45 (see Tab.21)
- ToD Time of Day interface RJ45 (see Tab.22)
- Console RJ45 (see Tab.23)
- Alarm RJ45 (see Tab.24)
ODU A ODU B LAN C LAN D LCT 2

URG 1PPS
NURG R ON
1
SW
Trib. 1-8 Trib. 9-16 2 2 4 6 M 5A
Fig.40 - IDU AGS-20 front panel example for GAI0216
5 It is available a security lock Z21196 for single connector and Z21197 for double connector.
94 MN.00329.E - 007
Tab.18 - 10/100/1000BaseT, RJ45
Function
Pin RJ45
10/100BaseT 1000BaseT
1 Twisted pair IN_P BI_DB+
2 Twisted pair IN_N BI_DB-
3 Twisted pair OUT_P BI_DA+
4 n.c. BI_DD+
5 n.c. BI_DD-
6 Twisted pair OUT_N BI_DA-
7 n.c. BI_DC+
8 n.c. BI_DC-
MN.00329.E - 007 95
Tab.19 - 8xE1, 50 pin SCSI female 75 Ohm
Pin 75 Ohm
48 Ground A
23 Tributary 1/9 input
50 Ground A
25 Tributary 1/9 output
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
Fig.41 - Pin-out Tributary 50 pin SCSI female
96 MN.00329.E - 007
Tab.20 - 8xE1, 50 pin SCSI female 120 Ohm)
Pin 120 Ohm
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
MN.00329.E - 007 97
Pin 120 Ohm
32 Ground B
32 Ground B
32 Ground B
2 Tributary 8/16output
32 Ground B
25 1
.........................
.........................
50 26
Fig.42 - Pin-out Tributary 50 pin SCSI female
Tab.21 - SYNK-1 interface pinout
RJ45 pin Function
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
Tab.22 - ToD interface pinout
RJ45 pin Function
4 GND
5 GND
7 ToD_N
8 ToD_P
98 MN.00329.E - 007
Tab.23 - Console connector pinout
RJ45 pin Function
3 TxD (Output)
4 GND
5 GND
6 RxD (Input)
Tab.24 - Alarm connector pinout
RJ45 pin Function
1 Alarm User-In 0
2 Alarm User-In 1
3 GND
6 Alarm User-Out: Relé-Com
7 Alarm User-Out: Relé-N.O.
8 Alarm User-Out: Relé N.C.
MN.00329.E - 007 99
9 INSTALLATION ONTO THE POLE OF THE ODU
WITH INTEGRATED ANTENNA (KIT V32307,
V32308, V32309)
9.1 FOREWORD
The description concerns pole mounting of ODU, in 1+0 and 1+1 version, using following installation kits:
- V32307 for ODU with frequency from 10 to 13 GHz

Differences regard the dimensions and the presence of the centring ring (see Fig.43):
- V32307 centring ring for antenna flange from 10 to 13 GHz

- V32308 centring ring for antenna flange from 15 to 38 GHz
- V32309 no centring ring (and relevant screws).
9.2 INSTALLATION KIT
Following installation kits are supplied with the equipment depending on different versions.
1+0 version
• 60 to 129 mm pole mounting kit:
- centring ring and relevant screws
- pole support system plus antenna (already assembled) and pole fixing brackets
- 1+0 ODU support and relevant screws
- ODU with O–ring and devices for ground connection
1+1 version
- 1+0 ODU support
- hybrid and relevant screws
- polarization twist disk and relevant screws
- 2 ODUs with O–rings and devices for ground connection.
100 MN.00329.E - 007

9.3 REQUIRED TOOLS FOR MOUNTING (NOT SUPPLIED)
• N.1 2.5 mm Allen wrench
• N.1 3 mm Allen wrench

• 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.
9.4 INSTALLATION PROCEDURE
Installation procedure is listed below:
1+0 version
1. antenna polarization
2. installation of the centring ring on the antenna
3. installation of 1+0 ODU support
4. installation onto the pole of the assembled structure
5. installation of ODU
6. antenna aiming
7. ODU grounding
1+1 version
5. installation of hybrid
6. installation of ODUs
7. antenna aiming
8. ODU grounding.
MN.00329.E - 007 101

9.5 1+0 MOUNTING PROCEDURES
9.5.1 Setting antenna polarization
Fig.43 – 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).
9.5.2 Installation of the centring ring on the antenna
Fig.43 – 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).
9.5.3 Installation of 1+0 ODU support
Fig.43 – 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.
9.5.4 Installation onto the pole of the assembled structure
Fig.43 – 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.
9.5.5 Installation of ODU (on 1+0 support)
Fig.44 – Apply seal and lubricant grease Dow Corning 4 on the O–ring by protecting fingers with gloves.
Fig.45 – 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.46) and reference tooth on the ODU body.
Fig.47 – 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.46 – When ODU positioning is over, secure ODU body on the support by tightening bolts (use 13mm
spanner, torque = 6Nm).
102 MN.00329.E - 007

9.5.6 Antenna aiming
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.48 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.48 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.
9.5.7 ODU grounding
ODU grounding is achieved with:
• M8 screw without washers
• M6 screw with washer
as shown in Fig.49.
In further page are explained all the mounting step not already discussed in paragraph “9.5 1+0
MOUNTING PROCEDURES”.
9.6.1 Installation of Hybrid
Fig.50 – 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.51.
Tighten progressively and alternatively the screws and the spring washer with following torque:
Tab.25 - Torques for tightening screws
Frequencies Screw Tool Torque
from 18 to 38 GHz Allen screw M3 Allen key 2.5 mm 1 Nm
up to 15 GHz Allen screw M4 Allen key 3 mm 2 Nm
Fig.52 – Fix hybrid body to 1+0 support with four M8 bolts (use 13 mm spanner, torque = 18 Nm), tighten
progressively and alternatively the bolts.
MN.00329.E - 007 103

9.6.2 Installation of ODUs (on hybrid for 1+1 version)
For both ODUs.
Fig.44 – Apply seal and lubricant grease Dow Corning 4 to the O–ring by protecting fingers with gloves.
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.53 – 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.46 – 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)
Three 3mm Allen screws Antenna

(not present in V32309)
1+0 support
Two bushes
Fig.43 - 1+0 pole mounting
104 MN.00329.E - 007

Reference tooth
O-ring
ODU wave guide
"N"
"BNC"
Coupling torque for the grounding bolt is 9.5 Nm Ground bolt
Fig.44 - ODU body reference tooth
Vertical Horizontal
Fig.45 - 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.
MN.00329.E - 007 105

3
1
1
5
4 4
1
2
3
1. 6 mm Allen screw
2. Bush (diagonally placed)
3. 17 mm Tightening bolts (max torque = 6 Nm)
4. Reference point for horizontal polarization
5. Reference point for vertical polarization
Fig.46 - 1+0 support
106 MN.00329.E - 007

1+0 ODU HP with handle on the right:
horizontal polarization
1+0 ODU standard with handle on the left:

vertical polarization
Fig.47 - ODU housing final position for both polarization
MN.00329.E - 007 107

Horizontal aiming:
two 17mm block screws
Vertical aiming:
13mm block screws
Pole support
17mm nut for horizontal

adjustment of antenna
Internal 5mm Allen

screw for vertical
adjustment of antenna
Fig.48 - Antenna aiming
1
2
3
4
5
ASN/ASNK version
Coupling torque for the grounding bolt is 9.5 Nm
1. Bolt
2. Spring washer
3. Flat washer
4. Earth cable collar
5. Flat washer
Fig.49 - ODU grounding
108 MN.00329.E - 007

7
2
4
6
1. O–ring
2. Polarization twist disk
3. Hybrid mechanical body
4. Position marker of twist disk
5. Reference label for twist disk
6. O–ring
7. Allen screws
8. Spring washer
Fig.50 - Hybrid and twist disk
MN.00329.E - 007 109

Horizontal polarization
Vertical polarization
Fig.51 - Polarization disk fixing (only for 13 GHz and 15 GHz)
110 MN.00329.E - 007

Fig.52 - Hybrid installation
ASN/ASNK version
Fig.53 - 1+1 ODUs installation
MN.00329.E - 007 111

WITH INTEGRATED DUAL POLARIZATION AN-
TENNA
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.
The OMT we speak about is a generic one.
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.54.
The installation of ASN or ASNK ODU is the same.

Installation changes regarding the kind of ODU RF flange that can be fast locking or standard.
10.2 INSTALLATION KIT FOR STANDARD LOCK ODU
A generic installation kit includes the following items:
• Pole support system with antenna and orthomode transducer (from various suppliers)
• 2 centring rings and relevant screws (see Fig.55)
• 2 standard lock ODUs with O-rings and accessories for ground connection and with standard lock
flange.
10.3 INSTALLATION KIT FOR FAST LOCK ODU
• Pole support system with antenna and orthomode transducer (from various suppliers)
• 2 centring rings and relevant screws (see Fig.55)
• 2 fast lock 1+0 ODU support
• 2 Fast lock ODUs with O-rings and accessories for ground connection and with fastlock flange
112 MN.00329.E - 007

• 1x 2.5 mm Allen wrench
• 1x 3 mm Allen wrench
• 1x 6 mm Allen wrench
• 1x 13 mm spanner
• 2x 17 mm spanner
Two installation procedures are available depending the ODU mounting flange.
Standard lock ODUs
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
Fast lock ODUs
1. Installation of the 2 centring rings on the two lateral flanges of the orthomode transducer
2. Installation of the 2 fast lock 1+0 ODU support
3. Installation over the pole of the assembled structure: antenna with orthomode and pole support
system
4. Installation of the fast lock ODUs
5. Antenna aiming
6. ODU grounding
MN.00329.E - 007 113

10.6 STANDARD LOCK ODUS MOUNTING PROCEDURE
10.6.1 Installation of the centring rings over the OMT
Two centring rings must be mounted over the two lateral flanges of the OMT (see Fig.55).
• 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.
10.6.2 Installation over the pole of the assembled structure: antenna,

OMT and pole support system
See the instructions included in the antenna box (instructions vary depending on antenna vendor).
10.6.3 Installation of the standard lock ODUs over the OMT
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.
114 MN.00329.E - 007

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.
10.6.5 ODU grounding
as shown in Fig.49.
10.7 FAST LOCK ODUS MOUNTING PROCEDURE
10.7.1 Installation of the centring rings over the OMT
Two centring rings must be mounted over the two lateral flanges of the OMT (see Fig.55).
• 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.
10.7.2 Installation of the fast lock 1+0 ODU support
See Fig.56. 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.56). 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.56).
around
10.7.3 Installation over the pole of the assembled structure: antenna,

OMT and pole support system
See the instructions included in the antenna box (instructions vary depending on antenna vendor).
MN.00329.E - 007 115

10.7.4 Installation of the fast lock ODUs over the OMT
• 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.56, 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.56). 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.49.
Dual pol. antenna
Pole support system
OMT OMT flange where ODU

must be installed
OMT flange where ODU

must be installed
Fig.54 - Assembled structure (DP antenna, OMT, mounting system)
116 MN.00329.E - 007

1 Screws
Centering ring
Fig.55 - Centring ring
3
1
1
5
4 4
1
2
3
1. 6mm Allen screw
2. Bush (diagonally placed)

3. 17mm tightening bolts (max torque=6Nm)
4. Reference point
5. Reference point
Fig.56 - Fast lock ODU support
MN.00329.E - 007 117

Screws
Standard coupling flange
O-ring
ODU ASN/ASNK
Eyelet terminal
Grounding bolt
Fig.57 - ODU ASN/ASNK Standard lock
118 MN.00329.E - 007

WITH RFS INTEGRATED ANTENNA
11.1 FOREWORD
The installation onto the pole of the ODU with integrated antenna concerns both 1+0 and 1+1 version.
11.2 INSTALLATION KIT
Following installation kits are supplied with the equipment depending on different versions.
1+0 version

- 1+0 ODU support and relevant screws
- ODU with O–ring and devices for ground connection
1+1 version
- 1+0 ODU support
- hybrid and relevant screws
- polarization twist disk and relevant screws
- 2 ODUs with O–rings and devices for ground connection.
• N.1 2.5 mm Allen wrench
MN.00329.E - 007 119

• N.1 13 mm spanner
• N.2 17 mm spanner.
Installation procedure is listed below:
1+0 version

5. installation of ODU
6. antenna aiming
7. ODU grounding
1+1 version
5. installation of hybrid
6. installation of ODUs
7. antenna aiming
8. ODU grounding.
11.5.1 Setting antenna polarization
Fig.43 – 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).
120 MN.00329.E - 007

11.5.2 Installation of the centring ring on the antenna
Fig.43 – 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).
11.5.3 Installation of 1+0 ODU support
Fig.43 – 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.
11.5.4 Installation onto the pole of the assembled structure
Fig.43 – 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.
11.5.5 Installation of ODU (on 1+0 support)
Fig.44 – Apply seal and lubricant grease Dow Corning 4 on the O–ring by protecting fingers with gloves.
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.46) and reference tooth on the ODU body.
Fig.47 – 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.46 – 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.48 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.48 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.
MN.00329.E - 007 121

as shown in Fig.49.
In further page are explained all the mounting step not already discussed in paragraph “9.5 1+0
MOUNTING PROCEDURES”.
11.6.1 Installation of Hybrid
Fig.50 – 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.51.
Tighten progressively and alternatively the screws and the spring washer with following torque:
Fig.52 – Fix hybrid body to 1+0 support with four M8 bolts (use 13 mm spanner, torque = 18 Nm), tighten
progressively and alternatively the bolts.
11.6.2 Installation of ODUs (on hybrid for 1+1 version)
For both ODUs.
Fig.44 – Apply seal and lubricant grease Dow Corning 4 to the O–ring by protecting fingers with gloves.
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.
122 MN.00329.E - 007

Fig.53 – 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.46 – 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.
Three 3 mm
Centering ring Allen screws
Antenna Four 13mm screws
1+0 support
Fig.58 - 1+0 pole mounting
MN.00329.E - 007 123

Reference tooth
O-ring
ODU wave guide
"N"
"BNC"

Ground bolt
Fig.59 - ODU body reference tooth
Vertical Horizontal
Fig.60 - 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.
124 MN.00329.E - 007

2
1
1
4
3 3
1
1. 6 mm Allen screw M10

2. 17 mm Tightening bolts (max torque = 6 Nm)
3. Reference point for horizontal polarization
4. Reference point for vertical polarization
Fig.61 - 1+0 support
MN.00329.E - 007 125

1+0 ODU with handle on the left:
vertical polarization
1+0 ODU with handle on the right:

horizontal polarization
Fig.62 - ODU housing final position for both polarization
126 MN.00329.E - 007

Pole support
Vertical aiming
2
1
Horizontal aiming
Fig.63 - Antenna aiming
MN.00329.E - 007 127

1
2
3
4
5
ASN/ASNK version
1. Bolt
2. Spring washer
3. Flat washer
4. Earth cable collar

5. Flat washer
Fig.64 - ODU grounding
128 MN.00329.E - 007

7
2
4
6
1. O–ring
2. Polarization twist disk
3. Hybrid mechanical body
4. Position marker of twist disk
5. Reference label for twist disk
6. O–ring
7. Allen screws
8. Spring washer
Fig.65 - Hybrid and twist disk
MN.00329.E - 007 129

Horizontal polarization
Vertical polarization
Fig.66 - Polarization disk fixing (only for 13 GHz and 15 GHz)
130 MN.00329.E - 007

Fig.67 - Hybrid installation
MN.00329.E - 007 131

ASN/ASNK version
Fig.68 - 1+1 ODUs installation
132 MN.00329.E - 007

12 INSTALLATION ONTO THE POLE OF ODU
ASN/ASNK WITH STANDARD LOCK
12.1 ODU COUPLING KIT
ODUs can have two different coupling kits: fast lock and standard.
12.1.1 ODU ASN/ASNK
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.
12.1.1.1 Fast lock coupling kit
After the fast lock coupling kit installation, the ODU needs O-ring and grounding bolt only.
Coupling kit assembly procedure
See Fig.69 - 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.
12.1.1.2 Standard coupling kit
The standard coupling kit is mounted on ASN/ASNK ODU by means of four screws.
Coupling kit assembly procedure
See Fig.70 - 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.
MN.00329.E - 007 133

12.2 INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRAT-
ED ANTENNA
12.2.1 ODU ASN/ASNK (Fast Lock)
The installation of ODUs with Fast Lock coupling kit is described in previous chapters.
12.2.2 ODU ASN/ASNK (Standard Lock)
Mounting kit 1+0 version
• Centring ring and relevant screws
• M10 bolts
• ODU with O-ring and devices for ground connection
• Centring ring and relevant screws
• M10 bolts for hybrid and ODU mounting
• Hybrid mechanical body
• Polarization twist disk (see Fig.73)
• 2 ODUs with O-rings and devices for ground connection.
12.2.2.1 1+0 ODU
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.71.
• 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
• 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
134 MN.00329.E - 007

- horizontal polarization: the handle (6) of the ODU is at the bottom right corner
ODU to the antenna flange in order to have the four slots of the Standard Lock cross between the
four bolts
• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15mm spanner,
torque=46mm)
• The ODU is ready to be connected to the IDU-ODU cable and to the grounding cable.
12.2.2.2 1+1 ODU
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.72.
Mounting the hybrid (3) on the back of the antenna:

• Position the three holes circular flange (1) on the antenna flange and align the holes on the circular
flange with the relevant holes on the antenna flange
• Insert and tighten the three 3mm M4 Allen screws (2) using a 3mm Allen wrench (torque = 2mm)
• Prepare the polarization disk (see Fig.73) 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.73 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.73. Torque values as in 12.3.2.2.
• Mount the hybrid on the back of the antenna by means of four M10 bolts (4) (torque = 46 Nm)
Mounting each ODU on the hybrid:
• Screw partially four M10 bolts (4) on the hybrid flange (ODU side): each bolt should be tightened
to have the square head out of the hole of about 13-14 mm, use 15 mm spanner
• Position the ODU (5) vertically near the four bolts on the antenna flange and align the ODU to match
the polarization of the antenna feeder: horizontal polarization must be used, the handle (6) of the
ODU is at the bottom right corner
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
MN.00329.E - 007 135

• When each slot is firmly hooked on the relevant bolt, tighten each bolt (use 15 mm spanner, torque
= 46Nm)
• Now the ODU is ready to be connected to the IDU-ODU cable and to the grounding cable
• Repeat for the other ODU on the other side

• Optional: sun cover kit. Insert the sun cover and tie one of its bottom holes to the ODU handle by
• Now the ODU is ready to be connected to the IDU-ODU cable and to the grounding cable.
12.3 INSTALLATION ONTO THE POLE OF THE ODU WITH SEPARAT-

ED ANTENNA
• Diameter of the pole 60-114 mm
12.3.1 ODU ASN/ASNK (Fast Lock)
The installation of ODUs with Fast Lock coupling kit is described in previous chapters.
12.3.2 ODU ASN/ASNK (Standard Lock)
• Supporting plate, fixing bracket with M10 130mm bolts (with washer, spring and nut)
• 1 antenna side flange, variable as function of RF frequency, with relevant screws
• M10 25mm bolts for ODU mounting
• ODU with O-ring and devices for ground connection
• Supporting plate, fixing bracket with M10 130mm bolts (with washer, spring and nut)
• M10 25mm bolts for hybrid and ODUs mounting
• Hybrid mechanical body
• Polarization twist disk (see Fig.73)
• 2 ODUs with O-rings and devices for ground connection.
136 MN.00329.E - 007

12.3.2.1 1+0 ODU
See Fig.74.
• 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.74 the antenna flange is shown in two
different positions depending on the polarization), the screw holes side is the side where the wave-
guide must be installed.
• 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).
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
ODU to the supporting plate in order to have the four slots of the Standard Lock cross between the
four bolts
=46 Nm).
12.3.2.2 1+1 ODU
See Fig.75.
• 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:
• 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
• 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
MN.00329.E - 007 137

= 46 Nm)
• Optional: sun cover kit - insert the sun cover and tie one of its bottom holes to the ODU handle by
• Now the ODU is ready to be connected to the IDU-ODU cable and to the grounding cable
• Repeat for the other ODU on the other side
138 MN.00329.E - 007

12.3.2.3 Waveguide towards the antenna
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.28 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.28 for details.
Coupling torque for the grounding bolt is 9.5 Nm.
Tab.28 - Waveguide bending radius according to frequency
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)
11 GHz 130 (5,1) 280 (11,0) 150 (5,9) 300 (11,9)
13 GHz 130 (5,1) 280 (11,0) 150 (5,9) 300 (11,9)
15 GHz 130 (5,1) 280 (11,0) 150 (5,9) 300 (11,9)

18 GHz 130 (5,1) 280 (11,0) 150 (5,9) 300 (11,9)
23 GHz 110 (4,3) 230 (9,1) 130 (5,1) 250 (9,9)
38 GHz 80 (3,1) 140 (5,5) 90 (3,6) 150 (5,9)
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)
MN.00329.E - 007 139

Fast lock coupling flange
Screws
O-ring
ODU ASN/ASNK
Eyelet terminal
Grounding bolt
Fig.69 - ODU ASN/ASNK with fast lock coupling flange
140 MN.00329.E - 007

Screws
Standard coupling flange
O-ring
ODU ASN/ASNK
Eyelet terminal
Grounding bolt
Fig.70 - ODU ASN/ASNK with standard coupling flange
MN.00329.E - 007 141

5
3 (Torque 46Nm)
4
M10
2 (Torque 2Nm)
Fig.71 - 1+0 ODU installation
142 MN.00329.E - 007

4
5
7
3
4
6
1
Fig.72 - 1+1 ODU installation
MN.00329.E - 007 143

Fig.73 - Polarization disk
114-60
3
Fig.74 - 1+0 antenna flange
144 MN.00329.E - 007

7
4
3
1
5
2
Fig.75 - 1+1 antenna flange
MN.00329.E - 007 145

146 MN.00329.E - 007
13 INSTALLATION OF THE FULL ODU
For the Full ODU installation, see relevant manual depending on Full ODU version.
MN.00329.E - 007 147

148 MN.00329.E - 007
Section 4.
LINE-UP
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
The line–up consists of the following steps:

• on site radio terminal installation (user connections and ODU/Full ODU installation as described in
the relevant chapters)
• equipment switch–on
• alarm LEDs check
• connection procedure
• equipment configuration (through PC software)
• optimizing antenna orientation
• check of Ethernet connections
• quality evaluation with performance monitoring
Operations involving the use of WebLCT are roughly described here. For further details please refer to soft-
ware manual.
MN.00329.E - 007 149

14.2 SWITCH ON
Checks to be performed before switching on the unit are:
• check external power supply voltage
• antenna presence - check the connection between ODU/Full ODU output flange and antenna.
If everything is correct, power on the AGS-20.
14.3 ALARM LED CHECK
Check alarm LEDs on front panel and on the Full ODU (if any). Alarm information can be found in Section
5. MAINTENANCE.
14.4 CONNECTION TO EQUIPMENT
Ethernet connection between PC and AGS-20 can occur if both the IP Addresses belong to the same subnet.
The Ethernet ports available for the management of AGS-20:
• RJ45 LCT port with IP address 192.168.0.1 and netmask 255.255.255.0 (default settings)
• RJ45 LAN3 port with default address is
- 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.
14.4.1 Connection to LCT or LAN3 port
Connection to LCT/LAN3 port:
1. open a browser (IE 9)
2. write 192.168.0.1/(LAN3 port IP address)
3. in the WebLCT Login page, write:
- username: admin
- password: admin
4. select or not the “Remember me” option to remind login data for further accesses
5. click Login button.
150 MN.00329.E - 007

14.4.2 Connection using WLC
Connection to LCT/LAN3 port by means of WLC (WebLCT console):
1. open WLC
2. add LCT/LAN3 port IP address to LAN address book field in the WLC using the “Add +” button
3. double click on the address just added
4. in the WebLCT login page, write:
- username: admin
- password: admin
5. select or not the “Remember me” option to remind login data for further accesses
6. click Login button.
14.4.3 CLI session using Hyperterminal (or a similar software)
Connect the laptop to LCT port or to LAN3 port:
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
3. click the OK button
4. at the prompt SM-OS login: write admin
5. at the prompt Password: write admin
6. push Enter to have the prompt SM-OS#.
14.5 RADIO LINK CONFIGURATION
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).
14.6 EQUIPMENT CONFIGURATION
Parameters to set are the following:
• IP address
• Bandwidth, modulation, link ID and TDM setting
• Tx frequency & power
• Traffic port configuration
• Agent IP address and equipment ID
MN.00329.E - 007 151

• Routing table
• Remote element list
After setting parameters, restart the equipment.
14.6.1 IP address setting
Run WebLCT and write the new IP address, netmask, default gateway and eventual Vid (1) in DCN menu
for In Band management.
Push Apply and Store.
Push Restart to reboot and use new address.
14.6.2 Bandwidth, modulation, TDM and Link ID setting
Run the WebLCT and select BW & MOD/LINK ID in Equipment menu.
1. In Modulation&Capacity card this must be set:
- Bandwidth
- Reference modulation (which relevant max Tx power is a limit in output power)

- Permanent TDM Traffic (number of E1 in radio frame at all modulation profiles)
- ACM engine status (in order to have variable modulation ACM must be enabled)
- Lower profile
- Upper profile
- Profile management
Push Apply and Confirm.
2. In Local link ID card, set the Local Link ID value.
Push Apply and Confirm.
Warning: use the same parameters on remote unit.
14.6.3 Tx frequency setting
Run the WebLCT and in Radio, select Radio Branch.
In ODU Setting card insert:
• Tx frequency
• Duplex frequency
Press Apply and Confirm.
Local Tx frequency must be set as remote Rx frequency.
Warning: Remember that radio link can work only if ODUs have equal subband and different Tx module
(example: ODU 1H and ODU 1L).
152 MN.00329.E - 007

14.6.4 Tx power setting
Run WebLCT and In Radio, select Radio Branch. In ODU Powers card set:
• Manual mode and relevant Max Ptx
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.
14.6.5 Equipment ID and Agent IP setting
Into WebLCT in Main, Equipment Properties, select General Info card and set:
• Equipment ID (name of the local unit)
• Agent IP address (generally equal to ethernet IP address)
14.6.6 Routing Table setting
Into WebLCT in Main, Baseband, DCN, select Routing Table.
To add a routing line in the existing table select the button Add:
• set Destination IP address with netmask and interface kind
• set default Gateway IP address and the distance from it (number of interfaces to cross).
14.6.7 Remote Element Table
Run the WebLCT and expand Remote element list area (expansion arrows on the right).
Select Clear and Apply just to delete the previous configuration.
A new remote element list must be created.
In station field select Add, type the new station name and press OK.
• Select the station just created and add local element:
- IP address: type local radio IP agent address
- type of element: managed by SCT

Press OK, Apply and Confirm
• Add remote element:
MN.00329.E - 007 153

- IP address: type remote radio IP agent address
- Type of element: remote link

Press OK, Apply and Confirm.
14.7 ANTENNA ALIGNMENT AND RX POWER
14.7.1 ODU ASN and ODU ASNK
Purpose of antenna alignment is to maximize the RF received signal level.
Proceed as follows:
• connect a multimeter to BNC connector on the ODU for AGC measurement

• adjust antenna pointing as soon as the maximum AGC voltage value is achieved.
The relationship between AGC voltage and received field is shown in Fig.76. 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
-100 -80 -70 -60 -50 -40 -30 -20
Fig.76 - Detected voltage versus RF received signal
14.7.2 Full ODU
For the Full ODU antenna aiming, see relevant manual depending on Full ODU version.
154 MN.00329.E - 007

Section 5.
MAINTENANCE
15 ALARMS
In this document a description of alarms is present in order to help operators to perform equipment trou-
bleshooting.
15.1 ALARM SYSTEM
There are two way to identify the alarms:
• 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:
• Critical (red): out-of-service, hw failure, urgent alarm

• Major (orange): loss of signal, minimum residual functionality, urgent alarm
• minor (yellow): failure neither urgent, high residual functionality, not urgent alarm
• warning (light blue): indication or wrong configuration, not urgent alarm
• Status (green): no alarm or masked 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.
MN.00329.E - 007 155

15.1.1 LED status
The visual indication are given by LEDs. The information provided are:
• ON (green LED)
- OFF: IDU turned off or power failure
- ON: IDU turned ON
• SW (red LED)
- OFF: none
- ON: software/firmware mismatch

• TEST (yellow LED)
- OFF: none
- ON: some manual operation active (Loops, Radio Switch, Fade Margin, PRBS, etc....)
• URG (red LED)
- OFF: no urgent alarm
- ON: one or more urgent alarms (Critical, Major)
• NURG (red LED)
- OFF: no Not urgent alarm
- ON: one or more Not urgent alarms (minor, warning)
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
• only SW LED, for about 15 seconds

• only TEST LED for about 5 seconds.
Now it is active.
15.1.2 Alarm group
Alarms are divided in groups to refer to a particular functionality and are characterized by programmable
severity.
Alarms, with group and a short description, are listed in Tab.29.
In the following you can find a class list and the item they described:
• COMMON - Failure or status relevant to whole equipment
• ETH LAN - Failure on Ethernet traffic
• IDU - Failure on IDU board

• P.M. G.828 - performance monitoring on signal quality
• P.M. ACM - Performance monitoring on ACM
• P.M. Rx Power - Performance monitoring on received signal
• P.M. Tx Power - Performance monitoring on transmitted signal
• Plug-in module - Alarm on plug-in device
• Queue Depth - Queue Configuration Alarm

• RADIO - alarm on Tx/Rx section of radio
• SETS - Synchronisation alarm or status
• Unit - Hardware or software unit alarm
156 MN.00329.E - 007

Tab.29 - Alarm severity list
Class WebLCT name Description Default severity
COMMON Equip Manual Operation At least one manual operation on Warning
ETH LAN Eth Lan Phy Link Loss Loss of Ethernet signal Major
Radio Modulator Fail Alarm Alarm on radio transmitting side Major
Radio Demodulator fail Alarm Alarm on radio receiving side Major
IDU-ODU cable open (not connected,

Radio Cable Open Alarm Major
damaged)
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
ppi Rx Ais Alarm Alarm Indication Signal received in E1 Major
ppi E1 Sync Alarm No synchronisation through E1 Major
ppi PRBS Fail Alarm PRBS signal is missing Major
IF Alarm IF signal is missing Major
PM ACM - 24H Alarm Major

ACM measurements on received radio
P.M. ACM
PM ACM - 15M Alarm signal Major
pm G828 - 24H SepAlarm Major
pm G828 - 15M SepAlarm Major
pm G828 - UAS Alarm Major

Quality measurements on radio signal re-
P.M. G.828 pm G828 - 24H Ses Alarm Major
ceived a
pm G828 - 24H ES Alarm Major
pm G828 - 15M Ses Alarm Major
pm G828 - 15M ES Alarm Major
pm RxPwr - 24H Rlts Alarm Major

Rx Power measurements on radio signal
P.M. Rx Power
pm RxPwr - 15M Rlts Alarm received a. Major
pm TxPwr - 24H Rlts Alarm Major

Tx Power measurements on radio signal
P.M. Tx Power
pm TxPwr - 15M Rlts Alarm transmitted a. Major
Plug-in module Plug-in Module Alarm SPF module is missing Major
Queue Queue Depth Profile mismatch Queue Ethernet configuration mismatch Warning
MN.00329.E - 007 157

Radio Invalid Frequency Alarm Wrong frequency on radio link Major
Radio Rx Power Low Warning Received power below the fixed threshold Major
Transmitted power below the fixed

Radio Tx Power Low Alarm Major
threshold
Radio Rt Vco Fail Voltage Controlled Oscillator failure Major
Radio Rx AGC Alarm Automatic Gain Controller Failure Major
Radio Tx AGC Alarm Automatic Gain Controller Failure 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
Wrong configuration set in local&remote

Radio Configuration Mismatch Major
radio
RADIO
Radio Rx Quality Low Alarm Insufficient received signal quality Major
Radio Rx Quality Low Warning Received signal quality degraded Warning
Radio Equip Link Telemetry Fail

Telemetry failed to radio link missing Major
Alarm
Link Reduced Capacity Alarm Signal to noise is not enough Major
Link ID Alarm Wrong Link ID received Warning
Link Radio Eoc Alarm Embedded Over Channel missing Critical
Link Rescue Setup Alarm Local configured in rescue mode Major
Link Xpic Procedure Block Alarm Local Xpic Off Major
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
Link Tfc Alarm - Minor
Timing Sync Active Status Timing Sync is active Status
Timing Sync Drift Alarm Selected Synch bad quality Major
Timing Sync Los Alarm Selected Synch missing Major
Timing Generator Holdover Status Equipment in holdover status Warning

SETS
Timing Generator Free Running
Equipment in Free Running status Warning
Status
Timing Generator T0 Fail Alarm T0 synch missing Major
Timing Generator T4 Squelch T4 synch missing Major
158 MN.00329.E - 007

Unit SW Mismatch Alarm SW mismatch detected on the unit Major
Unit HW Mismatch Alarm HW mismatch detected on the unit Major
Unit Not Responding Alarm No response from the unit Major
Unit Missing Alarm Missing condition on the unit Major

Unit
Unit Fail Alarm Failure on the unit Major
Temp Sensor Alarm Threshold 1 Over temperature threshold 1 Warning
Temp Sensor Alarm Threshold 2 Over temperature threshold 2 Critical
Fans Alarm Fans failure Major
A local MEP receives RDI from remote

RDI CCM Alarm Warning
MEPs
A local MEP receives MAC status down

MAC Status Alarm Major
from remote MEPs
OAM A local MEP does not receive CCM from

Remote CCM Alarm Major
remote MEPs
Error CCM Alarm A local MEP receives unexpected CCM Major
A local MEP receives unexpected CCM

XCon CCM Alarm Major
from other domains
a. Regarding periods of 15 minutes or 24 hours.
MN.00329.E - 007 159

16 MAINTENANCE AND TROUBLESHOOTING
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
Maintenance consists of two stages:
1. periodical checks to be carried out using WebLCT

2. corrective 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.
16.2.1 Periodical checks
System routine maintenance consists in a series of routine checks aiming to verify correct operating mode
of an alarm–free system.
These checks are made through WebLCT program, installed on a PC.
The items to be checked are:
• Tx power (i.e., attenuation value in dB vs. nominal value)
• Rx field (value measured must comply with that resulting from hop calculation)
• S/N (presence of possible interference)
• BER (values measured must comply with hop calculations)
How these operations are carried out is specified in “Line–up” section or, more widely, in AGS-20 software
manual.
160 MN.00329.E - 007

16.2.2 Corrective maintenance (troubleshooting)
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.
See paragraph 16.3 TROUBLESHOOTING for details.
16.3 TROUBLESHOOTING
Main purpose of troubleshooting is to identify the possible cause of alarm:
• 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....)
- using the “Performance Monitoring” Prx, Ptx BER measuring
- particular condition (heavy rain, stratification of different air temperature, flat surface, etc....)
• Radio hardware faulty
- alarms due of a wrong configurations or actual status of the radio
- faulty (using radio BER test generator and loops, to check hardware failure)
• External event
- no constant 48 Volt power supply during the day/night
- very high temperature, humidity inside waveguide

- ODU operating range -33°C to +55°C; survival temperature range -40°C to +65°C
- ODU waterproof according to IP65 environmental class
The troubleshooting procedure is performed with:
• check value of Power Transmitter and Receiver
• reading Current Alarms and Alarm History labels and trying to figure out which part of the equip-
ment is affected.
• disabled All Manual Operations
• verifying with radio BER test a hardware failure or S/N measure
• verifying the correct initialization of the Local and Remote Radio
• SW/HW restart
• factory default
• firmware update
• replace with a spare part.
MN.00329.E - 007 161

16.3.1 Quality alarms
Present alarms:
• Rx Quality Warning BER<10-10
• Rx Quality Alarm BER<10-6
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.
Usage of Px/Pwr window is important because troubleshooting can be performed

also after the problem disappearing....comparing the starting time of the alarms
with older Rx power measurements relevant the alarm period.
Fig.77
16.3.2 Radio link affected by fading
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.
These alarms are fleeting because of the fluctuating attenuation:

• F>10 GHz the fading is given by rain (for F>30 GHz rain is a serious problem)
• F<10 GHz the fading is given by ducting and multipath.
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).
162 MN.00329.E - 007

16.3.3 Radio link affected by interference
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.
MN.00329.E - 007 163

17 SOFTWARE RESET
17.1 SOFTWARE RESET
A software reset command implies the software reboot of the unit and it is traffic affecting.
AGS-20 can receive a “software reset” command in the following modes:
• through WebLCT/NMS
• pressing the R button on the front panel (the SW LED remain steady on).
Pressing R button for:
• less than 2 seconds -> the microprocessor restarts

• 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.
164 MN.00329.E - 007

Section 6.
PROGRAMMING AND SUPERVI-
SION
18 PROGRAMMING AND SUPERVISION
18.1 GENERAL
AGS-20 is programmed and supervised using CLI and WebLCT. This subject is fully described in the sepa-
rated software manual.
Operating system compatibility are Windows XP or Windows 7.
18.2 SUPERVISION
The description of management plane depends on the possible interconnections and application:
• In Band management (local and remote units belong to the same subnet)
• L2 Emulated Out of band (local and remote units belong to the same subnet)
• Out of Band (local and remote units belong to different subnets).
18.2.1 Configurability
In general the management plane can be configured using CLI (see separated software manual). The com-
binations of management configuration are shown in the following.
MN.00329.E - 007 165

18.2.2 AGS-20 - In Band
In this configuration the management plane transport is shared with the data plane (see Fig.78). The dif-
ferentiation is obtained by managing different VLANs. A VLAN dedicated to the management shall be de-
fined (VLANmng) and configured by the user.
Within "InBand context" it shall be possible to:
• Define which ports participate to the VLANmng and the port connectivity scheme to obtain the de-
sired reachability (local only or also remote)
• In particular it shall be possible to dedicate a LAN to the management only (in this case untagged
management frames at this interface shall be supported)
• Configure the priority of management VLAN (PCP) and ToS.
Fig.78 shows an example of LAN1, P, ODU A as member of the VLANmng.
µP
IDU µP
data
1 1
VIDMng
A A
2 2
Switch Switch
LCT LCT
mng
Fig.78 - Example of InBand management, LAN1 with local and remote visibility
µP µP
data
1 1
VIDMng
mng A A
2 2
Switch Switch
LCT LCT
mng
Fig.79 - In band Management example, LAN2 port is dedicated to the management and accesses
to local CPU only
LAN3, in default status, is a management VLAN member (VID=1).
18.2.3 AGS-20 - Emulated Out Of Band (L2)
There is a LAN port dedicated to the management but the radio port is shared with the data. Therefore the
differentiation of the management over the air is performed by the system at logical level (adding a re-
served VLAN tag) that keeps data and management plane separated.
Note that the traffic expected over management LAN port can be tagged or untagged.
It shall be possible to assign a policer/shaper to the management and payload traffic for bandwidth allo-
cation.
166 MN.00329.E - 007

µP
data
1
A data
mng
2
LCT Switch
mng
Fig.80 - Emulated out of band (L2)
18.2.4 AGS-20 – Out of Band (L3)
In Out of Band (L3) configuration one local port is used for local management (untagged) and a dedicated
PPP channel is used to communicate with the remote radio.
mng
µP PPP
data
1
A data
Switch
mng
Fig.81 - Out of Band (L3)
This Out of Band DCN is available in Level 3 modality (Routing) only and for this reason local and remote
units belong to different subnets.
Two Out of Band settings are available:
• Numbered – Every interface has a IP address
• Unnumbered – Only one IP address is used by all the interfaces
Using WEBLCT console (see Fig.82) is possible selecting the Out Of Band PPP mode (Unnumbered or Stand-
ard) and in Routing Table the routing line must be added to reach the remote unit (and in the Routing Table
of the remote unit the line must be added to see the local one).
Fig.82 - Out Of Band commands
MN.00329.E - 007 167

18.2.5 Address
The unit uses a single IP address associated at the management port of controller and a single “default
gateway”.
18.2.6 Console access mode
The “Console access” is available in console port through serial port (F03588 cable) via Hyperterminal
(115200bps,n,8,1):
• default login: admin
• default password: admin
18.3 COMPILING SCRIPT AT STARTUP
Some Ethernet configurations may require further settings and executed by Telnet CLI commands (i.e.:
management VLAN, bridge mode change, ...).
The Telnet CLI commands can be sent locally or remotely line by line.
System version v.1.1.0 and successive allow to execute on microprocessor flash a script previously loaded,
without commands interruption.
Load and run script procedure:
• create a textual script (suggested editor “Notepad++”)
• convert textual script to Unix format with Notepad++ and save script
• the file name must not contain special characters, including _ or -

• start and configure a TFTP server (suggested Tftp32 for Windows or tftp On Unix/Linux
• connect to console port through the F03588 serial console cable
• login SM-OS via Telnet
• load the script (e.g.: script.txt) to microprocessor non volatile memory via TFTP with the following
commands:
SM-OS# copy tftp://server_ip/script.txt flash:script.txt
SM-OS# run script script.txt
SM-OS# sh vx
[Unit IP address]> reboot (...and Enter).
168 MN.00329.E - 007

Section 7.
COMPOSITION
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.
19.2 IDU PART NUMBER
Every version is identified by a specific part number shown on a label (see Tab.30) 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.
P/N consists of seven digits with the following meaning:
MN.00329.E - 007 169

Tab.30- IDU part number
Digit Letter/number Meaning
Functional assembly of units completed by a mechanical

1 G
structure
2 A AL equipment
3 I Indoor installation
Hardware version - Code description

0212-1 - AGS-20 Switch
0213-1 - AGS-20 Single IF
0214-1 - AGS-20 Single IF w/16
0218-1 - AGS-20 Single IF w/16xE1+2xSTM1+Nodal
0215-1 - AGS-20 Dual IF
0216-1- AGS-20 Dual IF w/16
0215-2 - AGS-20 Dual IF
0216-2 - AGS-20 Dual IF w/16
4 to 7 0212 to .....
0217-2 - AGS-20 Dual IF w/16xE1+2xSTM1+Nodal
0219-1 - AGS-20 Quad IF
0220-1 - AGS-20 Quad IF w/16xE1
0221-1 - AGS-20 Quad IF w/16xE1+2xSTM1+Nodal
0222-2 - AGS-20 Quad IF
0223-2 - AGS-20 Quad ETH w/16xE1
0224-2 - AGS-20 Quad ETH w/16E1+2xSTM1+Nodal
0225-1 - AGS-20 Single IF PP w/16xE1
0226-1 - AGS-20 Single IF PP X/16xE1+2xSTM1+N
170 MN.00329.E - 007

20 COMPOSITION OF OUTDOOR UNIT
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.31 and Tab.32 various ODU versions and hybrid part number are listed.
Part number, hardware layout and equipment composition are subject to change without notice.
Tab.31 - ODU ASN part number and description
RF band in GHz ODU description Part number
ODU ASN6L SB=1H GE9501
ODU ASN6L SB=1L GE9500

6
ODU ASN6U SB=1H GE9509
ODU ASN6U SB=1L GE9508
MN.00329.E - 007 171

ODU ASN7L/161 SB=1H GE9519
ODU ASN7L/161 SB=1L GE9518
7 ODU ASN7L/161 SB=3H GE9523
ODU ASN7M/154 SB=1H GE9535
ODU ASN7M/154 SB=1L GE9534
7 ODU ASN7M/154 SB=4H GE9541
ODU ASN8/311,32 SB=1H GE9583
ODU ASN8/311,32 SB=1L GE9582
ODU ASN8/311,32 SB=2H GE9585
ODU ASN8/311,32 SB=2L GE9584

8
ODU ASN8/311,32 SB=3H GE9587
ODU ASN8/311,32 SB=3L GE9586
ODU ASN8/311,32 SB=4H GE9589
ODU ASN8/311,32 SB=4L GE9588
172 MN.00329.E - 007

ODU ASN10/350 SB=1H GE9601

10
ODU ASN10/350 SB=1L GE9600
ODU ASN13 SB=1H GE9613
ODU ASN13 SB=1L GE9612

13
ODU ASN15 315/322 SB=1H GE9629
ODU ASN15 315/322 SB=1L GE9628

15

18
MN.00329.E - 007 173

ODU ASN23/1200/1232 SB=1H GE9727

23
ODU ASN23/1200/1232 SB=1L GE9726
ODU ASN23/1200/1232 SB=2H GE9729
ODU ASN23/1200/1232 SB=2L GE9728
ODU ASN23/1200/1232 SB=3H GE9731
ODU ASN23/1200/1232 SB=3L GE9730

25
174 MN.00329.E - 007

Tab.32 - ODU ASNK part number and description
ODU ASNK6L/256,04 HP SB=1H GE3501-42
ODU ASNK6L/256,04 HP SB=1L GE3500-42
ODU ASNK6U/340 HP CH=1H GE2101-42
ODU ASNK6U/340 HP CH=1L GE2100-42

6
ODU ASNK7H/245 SB=1H GE8557-42
ODU ASNK7H/245 SB=1L GE8556-42

7
ODU ASNK7L/154 SB=1H GE8621-42
ODU ASNK7L/154 SB=1L GE8620-42
MN.00329.E - 007 175

7 ODU ASNK7LM/161 SB=1H GE8475-42
ODU ASNK7LM/161 SB=1L GE8474-42
ODU ASNK7LM/161 SB=2H GE8477-42
ODU ASNK7M/154 SB=1H GE8535-42
ODU ASNK7M/154 SB=1L GE8534-42
176 MN.00329.E - 007

ODU ASNK7M/168 HP CH=1H GE2202-42
ODU ASNK7M/168 HP CH=1L GE2201-42
7 ODU ASNK7M/168 HP CH=3L GE2205-42
ODU ASNK8/119 SB=1H GE8591-42
ODU ASNK8/119 SB=1L GE8590-42

8
MN.00329.E - 007 177


8
ODU ASNK8/311,32 SB=1H GE8583-42
ODU ASNK8/311,32 SB=1L GE8582-42
ODU ASNK8/311,32 SB=2H GE8585-42
ODU ASNK8/311,32 SB=2L GE8584-42
ODU ASNK8/311,32 SB=3H GE8587-42
ODU ASNK8/311,32 SB=3L GE8586-42
ODU ASNK8/311,32 SB=4H GE8589-42
ODU ASNK8/311,32 SB=4L GE8588-42
ODU ASNK8/311,32 SB=5H GE8599-42
ODU ASNK8/311,32 SB=5L GE8598-42
ODU ASNK11 HP 490/530 SB=2H GE3609-42
ODU ASNK11 HP 490/530 SB=2L GE3608-42
ODU ASNK11 HP 490/530/500 SB=1H GE3607-42

11
ODU ASNK11 HP 490/530/500 SB=1L GE3606-42
ODU ASNK11 HP 490/530/500 SB=3H GE3611-42
ODU ASNK11 HP 490/530/500 SB=3L GE3610-42

13
178 MN.00329.E - 007

ODU ASNK15/315/322 SB=1H GE8629-42
ODU ASNK15/315/322 SB=1L GE8628-42
ODU ASNK15/315/322 SB=2H GE8631-42
ODU ASNK15/315/322 SB=2L GE8630-42
ODU ASNK15/315/322 SB=3H GE8633-42
ODU ASNK15/315/322 SB=3L GE8632-42
ODU ASNK15/315/322 SB=4H GE8635-42
ODU ASNK15/315/322 SB=4L GE8634-42
ODU ASNK15/315/322 SB=5H GE8637-42
ODU ASNK15/315/322 SB=5L GE8636-42

15
ODU ASNK18/1008/1010 SB=1H GE8701-42
ODU ASNK18/1008/1010 SB=1L GE8700-42
ODU ASNK18/1008/1010 SB=2H GE8703-42
ODU ASNK18/1008/1010 SB=2L GE8702-42

18
ODU ASNK18/1008/1010 SB=3H GE8705-42
ODU ASNK18/1008/1010 SB=3L GE8704-42
ODU ASNK18/1560 SB=1H GE8717-42
ODU ASNK18/1560 SB=1L GE8716-42
MN.00329.E - 007 179

ODU ASNK23/1008 SB=1H GE8719-42
ODU ASNK23/1008 SB=1L GE8718-42
ODU ASNK23/1008 SB=2H GE8721-42
ODU ASNK23/1008 SB=2L GE8720-42
ODU ASNK23/1200/1232 SB=1H GE8727-42

23
ODU ASNK23/1200/1232 SB=1L GE8726-42
ODU ASNK23/1200/1232 SB=2H GE8729-42
ODU ASNK23/1200/1232 SB=2L GE8728-42
ODU ASNK23/1200/1232 SB=3H GE8731-42
ODU ASNK23/1200/1232 SB=3L GE8730-42
ODU ASNK25/1008 SB=1H GE8737-42
ODU ASNK25/1008 SB=1L GE8736-42

25
ODU ASNK25/1008 SB=2H GE8739-42
ODU ASNK25/1008 SB=2L GE8738-42
ODU ASNK38/1260 SB=1H GE8783-42
ODU ASNK38/1260 SB=1L GE8782-42

38
ODU ASNK38/1260 SB=2H GE8785-42
ODU ASNK38/1260 SB=2L GE8784-42
ODU ASNK42/1500 SB=1H GE8791-42
ODU ASNK42/1500 SB=1L GE8790-42
ODU ASNK42/1500 SB=2H GE8793-42

42
ODU ASNK42/1500 SB=2L GE8792-42
ODU ASNK42/1500 SB=3H GE8795-42
ODU ASNK42/1500 SB=3L GE8794-42
180 MN.00329.E - 007

Section 8.
LISTS AND SERVICES
21 LIST OF FIGURES
Fig.1 - Components electrostatic charge sensitive indication................................................ 13
Fig.2 - Elasticized band .................................................................................................. 13

Fig.3 - Coiled cord ......................................................................................................... 13
Fig.4 - WEEE symbol - 2002/96/CE EN50419 .................................................................... 14
Fig.5 – AGS-20 Ethernet block diagram ............................................................................ 27

Fig.6 – QoS block diagram.............................................................................................. 33
Fig.7 - Default 802.1p PCP-queue map ............................................................................. 34
Fig.8 - Default ToS (DSCP) map ...................................................................................... 34
Fig.9 – Red Curve.......................................................................................................... 37
Fig.10 - WEBLCT Header Compression field....................................................................... 41
Fig.11 – PW Control Word structure ................................................................................. 42

Fig.12 – ELP between a SIAE AGS-20 and an external switch .............................................. 44
Fig.13 – Select the LAN port that sends LLF status ............................................................. 47
Fig.14 – Select the circuit that manages the LLF protected LAN port..................................... 48
Fig.15 - AGS-20 switch (GAI0212-1)................................................................................ 60
Fig.16 - AGS-20 Single IF (GAI0213-1) ............................................................................ 60
Fig.17 - AGS-20 Single IF/16E1 (GAI0214-1) .................................................................... 60
Fig.18 - AGS-20 Dual IF (GAI0215-2) .............................................................................. 61
Fig.19 - AGS-20 Dual IF/16E1 (GAI0216-2) ...................................................................... 61
Fig.20 - AGS-20 Quad ETH (GAI0222-2)........................................................................... 62
Fig.21 - AGS-20 Quad ETH/16E1 (GAI0223-2) .................................................................. 62
Fig.22 - AGS-20 PP Single IF/16E1 (GAI0225-1)................................................................ 62
Fig.23 - AGS-20 Dual IF/16E1 + 2STM1 + Nodal (GAI0217-2)............................................. 63
MN.00329.E - 007 181

Fig.24 - AGS-20 single IF/16E1 + 2STM1 +Nodal (GAI0218-1) ............................................ 63
Fig.25 - AGS-20 Quad Eth/16E1 + 2STM1 + nodal (GAI0224-2).......................................... 64
Fig.26 - AGS-20 PP Single IF/16E1 + 2STM1 + Nodal (GAI0226-1) ...................................... 64
Fig.27 - AGS-20 Quad IF (GAI0219-1) ............................................................................. 65
Fig.28 - AGS-20 Quad IF/16E1 (GAI0220-1) ..................................................................... 65
Fig.29 - AGS-20 Quad IF/16E1 + 2STM1 + Nodal (GAI0221-1)............................................ 66
Fig.30 - ASN or ASNK ODU ............................................................................................. 79

Fig.31 - Final 1+1 assembly with ASN or ASNK ODU .......................................................... 80
Fig.32 - ASNK ODU (for frequency > 15 GHz) ................................................................... 81
Fig.33 - ODU block diagram ............................................................................................ 82
Fig.34 - 1+1 hot stand–by 1 antenna ............................................................................... 83
Fig.35 - 1+1 hot stand–by 2 antennas ............................................................................. 83
Fig.36 - ATPC operation ................................................................................................. 84
Fig.37 - Grounding connection ........................................................................................ 91
Fig.38 .......................................................................................................................... 92
Fig.39 - Grounding kit positioning .................................................................................... 93
Fig.40 - IDU AGS-20 front panel example for GAI0216 ....................................................... 94

Fig.41 - Pin-out Tributary 50 pin SCSI female ................................................................... 96
Fig.42 - Pin-out Tributary 50 pin SCSI female ................................................................... 98
Fig.43 - 1+0 pole mounting .......................................................................................... 104

Fig.44 - ODU body reference tooth ................................................................................ 105
Fig.45 - 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.................................................................... 105
Fig.46 - 1+0 support ................................................................................................... 106
Fig.47 - ODU housing final position for both polarization ................................................... 107
Fig.48 - Antenna aiming ............................................................................................... 108

Fig.49 - ODU grounding ............................................................................................... 108
Fig.50 - Hybrid and twist disk ....................................................................................... 109
Fig.51 - Polarization disk fixing (only for 13 GHz and 15 GHz) ........................................... 110
Fig.52 - Hybrid installation............................................................................................ 111
Fig.53 - 1+1 ODUs installation ...................................................................................... 111
Fig.54 - Assembled structure (DP antenna, OMT, mounting system)................................... 116

Fig.55 - Centring ring .................................................................................................. 117
Fig.56 - Fast lock ODU support...................................................................................... 117
Fig.57 - ODU ASN/ASNK Standard lock........................................................................... 118

Fig.58 - 1+0 pole mounting .......................................................................................... 123
Fig.59 - ODU body reference tooth ................................................................................ 124
Fig.60 - 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.................................................................... 124
Fig.61 - 1+0 support ................................................................................................... 125
Fig.62 - ODU housing final position for both polarization ................................................... 126
Fig.63 - Antenna aiming ............................................................................................... 127
Fig.64 - ODU grounding ............................................................................................... 128
Fig.65 - Hybrid and twist disk ....................................................................................... 129
182 MN.00329.E - 007

Fig.66 - Polarization disk fixing (only for 13 GHz and 15 GHz) ........................................... 130
Fig.67 - Hybrid installation............................................................................................ 131
Fig.68 - 1+1 ODUs installation ...................................................................................... 132
Fig.69 - ODU ASN/ASNK with fast lock coupling flange ..................................................... 140
Fig.70 - ODU ASN/ASNK with standard coupling flange..................................................... 141
Fig.71 - 1+0 ODU installation........................................................................................ 142
Fig.72 - 1+1 ODU installation........................................................................................ 143

Fig.73 - Polarization disk .............................................................................................. 144
Fig.74 - 1+0 antenna flange ......................................................................................... 144
Fig.75 - 1+1 antenna flange ......................................................................................... 145
Fig.76 - Detected voltage versus RF received signal ......................................................... 154
Fig.77 ........................................................................................................................ 162
Fig.78 - Example of InBand management, LAN1 with local and remote visibility ................... 166
Fig.79 - In band Management example, LAN2 port is dedicated to the management and accesses
to local CPU only .......................................................................................................... 166
Fig.80 - Emulated out of band (L2) ................................................................................ 167
Fig.81 - Out of Band (L3) ............................................................................................. 167
Fig.82 - Out Of Band commands.................................................................................... 167
MN.00329.E - 007 183

184 MN.00329.E - 007
22 LIST OF TABLES
Tab.1 - Artificial respiration .............................................................................................12
Tab.2 - Technical characteristics of the AGS-20 Switch ........................................................26
Tab.3 - Switch bridge modes ...........................................................................................27
Tab.4 – Full dynamic memory ..........................................................................................38
Tab.5 – Priority based memory (1 radio port).....................................................................38
Tab.6 – Priority based memory (2 radio ports) ...................................................................38
Tab.7 – Uniform memory (1 radio port).............................................................................38
Tab.8 – Uniform memory (2 radio ports) ...........................................................................39
Tab.9 – Line ports dynamic memory (2 radio ports) ............................................................39

Tab.10 - Optical interface characteristics ...........................................................................68
Tab.11 - SFP transceiver .................................................................................................69
Tab.12 - Alarm characteristics..........................................................................................71

Tab.13 - Front panel system LEDs ....................................................................................72
Tab.14 - Electrical/Optical Ethernet interface status LEDs ....................................................72
Tab.15 - Meaning of PoE LEDs..........................................................................................72
Tab.16 - ODUs that can be connected to AGS-20 ................................................................76
Tab.17 - Characteristics of the cables................................................................................89
Tab.18 - 10/100/1000BaseT, RJ45 ...................................................................................95
Tab.19 - 8xE1, 50 pin SCSI female 75 Ohm ......................................................................96
Tab.20 - 8xE1, 50 pin SCSI female 120 Ohm) ....................................................................97
Tab.21 - SYNK-1 interface pinout .....................................................................................98
Tab.22 - ToD interface pinout ..........................................................................................98
Tab.23 - Console connector pinout....................................................................................99
Tab.24 - Alarm connector pinout ......................................................................................99
Tab.25 - Torques for tightening screws............................................................................ 103
Tab.28 - Waveguide bending radius according to frequency ............................................... 139
Tab.29 - Alarm severity list............................................................................................ 157
Tab.30 - IDU part number .............................................................................................. 170

Tab.31 - ODU ASN part number and description ............................................................... 171
Tab.32 - ODU ASNK part number and description ............................................................. 175
MN.00329.E - 007 185

186 MN.00329.E - 007
23 ASSISTANCE SERVICE
For more information, refer to the section relevant to the technical support on the Internet site of the com-
pany manufacturing the product.
SIAE helpdesk mail is: help@siaemic.it
MN.00329.E - 007 187

188 MN.00329.E - 007

AGS20 Manual PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AGS20 Manual PDF

Uploaded by

Copyright:

Available Formats

AGS-20

1 DECLARATION OF CONFORMITY ............................................................................... 9

2 FIRST AID FOR ELECTRICAL SHOCK AND SAFETY RULES .........................................11

3 PURPOSE AND STRUCTURE OF THE MANUAL ............................................................15

4 ACRONYMS AND ABBREVIATION .............................................................................17

5 SYSTEM PRESENTATION ..........................................................................................21

6 TECHNICAL SPECIFICATIONS ..................................................................................67

7 INSTALLATION AND PROCEDURES FOR ENSURING THE ELECTROMAGNETIC

9 INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED ANTENNA

10 INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED DUAL

13 INSTALLATION OF THE FULL ODU ..........................................................................147

16 MAINTENANCE AND TROUBLESHOOTING ...............................................................160

17 SOFTWARE RESET ..................................................................................................164

18 PROGRAMMING AND SUPERVISION .......................................................................165

19 COMPOSITION OF IDU ...........................................................................................169

20 COMPOSITION OF OUTDOOR UNIT.........................................................................171

21 LIST OF FIGURES ...................................................................................................181

22 LIST OF TABLES .....................................................................................................185

SIAE Microelettronica S.p.A. declares that the products:

- digital radio relay system ASN6 and ASNK6

- digital radio relay system ASN7 and ASNK7

- digital radio relay system ASN8 and ASNK8

- digital radio relay system ASN10 and ASNK10

- digital radio relay system ASN11 and ASNK11

- digital radio relay system ASN15 and ASNK15

- digital radio relay system ASN18 and ASNK18

- digital radio relay system ASN23 and ASNK23

- digital radio relay system ASN25 and ASNK25

- digital radio relay system ASN28 and ASNK28

- digital radio relay system ASN32 and ASNK32

- digital radio relay system ASN38 and ASNK38

The following standards have been applied:

- EN 60950-1: 2006 “Safety of information technology equipment”.

- EN 302 217 for digital point to point fixed radio

- EN 300 132-2 characteristics of power supply

- IEEE 802.3 for Ethernet interfaces

- ITU-T G.8261 for timing and synchronization aspects in packet networks.

2.1 FIRST AID FOR ELECTRICAL SHOCK

2.1.1 Artificial respiration

2.1.2 Treatment of burns

• Do not attempt to remove clothing from burnt sections

• Apply dry gauze on the burns

• Do not apply ointments or other oily substances.

Step Description Figure

Lift the patient’s head and let it recline backwards as far

3 While performing these operations take a good supply of oxy-

While performing these operations observe if the patient’s

Start with ten rapid expirations, hence continue at a rate of

Fig.1 - Components electrostatic charge sensitive indication

Fig.2 - Elasticized band

Fig.3 - Coiled cord

Fig.4 - WEEE symbol - 2002/96/CE EN50419

2.4 INTERNAL BATTERY

Inside the equipment, in IDU unit, there is a lithium battery.

3.1 PURPOSE OF THE MANUAL

3.2 AUDIENCE BASIC KNOWLEDGE

• installation and maintenance experience on digital radio system

• a good knowledge of IP/OSI networks and routing policy.

3.3 STRUCTURE OF THE MANUAL

Section 1 – User Guide

Section 2 – Description and specifications

List of abbreviation meaning is also supplied.

The content of the tool kit (if supplied) is also listed.