mn00329e - v12 - AGS20

AGS-20

User manual

MN.0032 9.E - 01 2

Contents

Section 1. USER GUIDE

2

1

DECLARATION DECLARA TION OF CONFORMITY CONFORMITY ...... ........... .......... ........... ............ ........... ........... ............ ........... ........... ............ ........... ........... ............ ...... 2

2

FIRST AID FOR FOR ELECTRICA ELECTRICAL L SHOCK SHOCK AND AND SAFETY SAFETY RULES RULES ...... ........... .......... ........... ............ ............ ............ ........ .. 3

2.1

FIRST FIRST AID FOR ELECTRICAL ELECTRICAL SHOCK SHOCK ....... ........... ....... ...... ...... ...... ....... ........ ....... ...... ....... ........ ....... ....... ........ ....... ...... ....... ....... ... 3 2.1.1 Artificial Artificial respiration respiration ............ ................... ............. ............. ............. ............ ............. .............. .............. ............. ............. ........... .... 3 2.1.2 Treatment Treatment of burns ............. ................... ............. .............. ............. ............. ............. ............ ............. ............. ............. ........... .... 3

2.2

SAFETY RULES ............. ................... ............. ............. ............. ............. ............. .............. .............. .............. ............. ............. .............. ............ ..... 5 2.2.1 Electrostatic Electrostatic discharge........... discharge.................. ............. ............. ............. ............. .............. .............. .............. .............. ............. ...... 5 2.2.2 Laser safety .............. ..................... ............. ............. .............. ............. ............. ............. ............ ............. ............. ............. ............. ...... 6

3

2.3

CORR CORREC ECT T DISPO DISPOSAL SAL OF OF THIS THIS PRODU PRODUCT CT (WAST (WASTE E ELECT ELECTRIC RICAL AL & ELECTRONIC EQUIPMENT) .................................................................................. 7

2.4

INTERNAL BATTERY ............. .................... .............. .............. ............. ............. ............. ............ ............. .............. ............. ............. ............ ..... 7

PURPOSE AND AND STRUCTURE STRUCTURE OF THE MANUAL........ MANUAL.............. ............ ............ ............ ............ ............ ............ ............ ........... ..... 8

3.1

PURPOSE OF THE MANUAL................ MANUAL...................... ............. ............. ............. ............. ............ ............. ............. ............. ............. ........ .. 8

3.2

AUDIENC AUDIENCE E BASIC KNOWLE KNOWLEDGE DGE ...... ......... ...... ...... ....... ....... ...... ...... ...... ....... ........ ....... ...... ...... ...... ....... ....... ...... ...... ....... ....... ...... ..... 8

3.3

STRUCTUR STRUCTURE E OF THE MANUAL MANUAL ...... ......... ...... ....... ........ ....... ...... ...... ...... ....... ....... ...... ...... ...... ....... ....... ...... ...... ....... ........ ....... ...... ...... ... 8

Section 2. DESCRIPTIONS AND SPECIFICATION

4

ACRONYMS ACRONY MS AND ABBREVIA ABBREVIATION TION ...... ........... .......... .......... ........... ............ ........... .......... .......... ........... ........... .......... ........... ........... .......10 ..10

4.1 5

10

ACRONYMS ACRONYMS AND ABBREVIA ABBREVIATION TION LIST ...... ......... ...... ....... ........ ....... ...... ...... ...... ....... ........ ....... ...... ...... ....... ....... ...... ...... ......1 ...10 0

SYSTEM PRESENTA PRESENTATION TION ...... ............ ........... .......... ........... ........... ........... ........... ........... ........... ........... ............ ........... .......... ........... ........... .......14 ..14

5.1

GENERAL........... GENERAL.................. .............. .............. .............. ............. ............. ............. ............ ............. ............. ............. .............. .............. ..............14 .......14

5.2

APPLICATIONS APPLICATIONS ............. .................... ............. ............. ............. ............. ............. ............ ............. ............. ............. .............. .............. ............14 .....14 5.2.1 Functionaliti Functionalities es ............. ................... ............. .............. .............. .............. .............. .............. .............. ............. ............. ..............15 .......15

5.3

RADIO LINK CONFIGURATION CONFIGURATIONS S ............. ................... ............. .............. ............. ............. ............. ............. .............. ............. ........16 ..16 5.3.1 Ethernet Ethernet Layer 1 Radio Link Aggregation.......... Aggregation................ ............ ............. .............. ............. ............ ..........16 ....16 5.3.2 Hitless RLag ............. .................... .............. ............. ............. ............. ............ ............. ............. ............. .............. .............. ............17 .....17

5.4

BRIEF RADIO LINK DESCRIPTION DESCRIPTION ............. .................... ............. ............. ............. ............. ............. ............. ............. ............18 ......18 5.4.1 1+0 .............. ..................... ............. ............. .............. .............. .............. .............. .............. .............. ............. ............. .............. .............18 ......18

MN.00329.E - 012

1

5.4.2 1+1 hot stand-by........ stand-by............... .............. ............. ............. .............. ............. ............. ............. ............. ............. ............ ..........18 ....18 5.4.3 1+1 space diversity.... diversity........... ............. ............. ............. ............. ............. ............. .............. .............. ............. ............. ...........18 ....18 5.4.4 1+1 frequency frequency diversity......... diversity................ ............. ............. .............. ............. ............. .............. .............. .............. ............18 .....18 5.4.5 1+1 frequency and space diversity................ diversity...................... ............. .............. ............. ............. ............. ...........19 .....19 5.4.6 2+0 single pipe with L1 aggregation........... aggregation................. ............ ............. ............. ............. ............. ............. .........19 ..19 5.4.7 2+0 single pipe pipe with L1 aggregation aggregation in XPIC ............. ................... ............ ............. ............. ............ .........19 ...19 5.4.8 AGS-20 multiple multiple direction ............ ................... ............. ............ ............. ............. ............. ............. ............. ............. ........19 ..19 5.4.9 Radio link link configurati configurations ons with AGS-20 AGS-20 Single Single IF interface interface ............. ................... ............ ..........20 ....20 5.4.10 Radio link configurations with AGS-20 Dual IF interface................................ 20 5.4.10.1 Port clusters clusters configuratio configuration n ............. .................... ............. ............. .............. ............. ............. ...........20 ....20 5.4.10.2 Dual IF system system configura configurations tions ............. .................... .............. ............. ............. ............. ............21 ......21 5.4.11 Radio link configurations with AGS-20 Quad IF interface............................... 23 5.4.11.1 Quad IF: Port Port clusters clusters configuratio configurations ns ............. ................... ............. .............. .............. .........23 ..23 5.4.11.2 Quad IF: system system configuratio configurations............ ns................... ............. ............. .............. ............. ...........24 .....24 5.5

ETHERNET SWITCH.............. SWITCH.................... ............. ............. ............ ............. ............. ............ ............. ............. ............ ............. ..............32 .......32 5.5.1 Ethernet Ethernet interfaces........ interfaces.............. ............. ............. ............. ............. ............. .............. .............. .............. ............. ............. ........33 .33 5.5.2 Traffic treatment..... treatment............ ............. ............ ............. .............. .............. ............. ............. ............. ............. ............. ............. ........34 .34

5.6

DATA PLANE ............. ................... ............. ............. ............. ............. ............ ............. .............. .............. ............. ............. .............. .............. ........35 .35 5.6.1 Ethernet Ethernet features.............. features..................... .............. ............. ............. ............. ............ ............. .............. ............. ............. ...........35 ....35 5.6.1.1

Auto-negotiati Auto-negotiation on ............ ................... ............. ............ ............. .............. .............. ............. ............. ............35 .....35

5.6.1.2

MDI/MDI-X MDI/MDI-X ............. .................... ............. ............. ............. ............ ............. ............. ............. .............. .............35 ......35

5.6.1.3

Ingress Filtering........... Filtering.................. .............. .............. ............. ............. ............. ............. ............. .............35 .......35

5.6.1.4

MTU ............. .................... .............. .............. .............. ............. ............. ............. ............ ............. .............. ............. .......36 .36

5.6.1.5

Storm Control............... Control..................... ............ ............. ............. ............. ............. ............. ............. ............. ........36 .36

5.6.1.6

MAC Learning Learning Rules................. Rules........................ ............. ............. ............. ............. ............. ............ ..........36 ....36

5.6.1.7 5.6.1.7

MAC Forward Forwarding ing Rules Rules ...... ......... ....... ........ ....... ...... ...... ...... ....... ........ ....... ...... ...... ....... ....... ...... ...... ......37 ...37

5.6.2 VLAN Forwarding Forwarding ............. .................... ............. ............. ............. ............ ............. ............. ............. ............. ............. .............37 ......37 5.6.2.1

IEEE 802.1q .............. .................... ............. ............. ............ ............. ............. ............. ............. ............. ...........37 ....37

5.6.2.2

VLAN Stacking - QinQ ............ ................... .............. .............. ............. ............. .............. .............. ..........37 ...37

5.6.2.3

VLAN Threatment Threatment ............. .................... .............. ............. ............. ............. ............. ............. ............ ..........37 ....37

5.6.2.4

Service Instance Mapping Mapping Criteria........ Criteria.............. ............. ............. ............ ............. ............. .......38 .38

5.6.2.5

Ingress Manipulation. Manipulation........ ............. ............ ............. ............. ............. ............. ............. ............. ............39 ......39

5.6.3 QoS Management Management ............ ................... ............. ............. .............. ............. ............. ............. ............ ............. ............. ............39 ......39 5.6.3.1

Classification Classification with Priority Priority Map .............. .................... ............. .............. .............. .............. ..........40 ...40

5.6.3.2

Classification Classification with Class Map................ Map...................... ............ ............. ............. ............. .............41 ......41

5.6.4 Policing Policing ............. ................... ............. ............. ............. .............. .............. ............. ............. ............. ............. ............. ............. ............42 .....42 5.6.4.1

Metering Metering ............. .................... ............. ............ ............. .............. .............. .............. .............. ............. ............. ........42 .42

5.6.4.2

Policy Map................. Map....................... ............. ............. ............ ............. .............. .............. ............. ............. ..........43 ...43

5.6.5 Congestion Congestion Avoidance..... Avoidance............ ............. ............. ............. ............ ............. ............. ............. .............. .............. ..............43 .......43 5.6.6 Output queues......... queues............... ............. .............. .............. ............. ............. ............. ............. ............. ............. ............. .............44 .......44 5.6.7 Scheduling Scheduling method ............. ................... ............. ............. ............ ............. ............. ............. .............. .............. .............. .........46 ..46 5.6.8 Egress Shaping.......... Shaping................. .............. .............. ............. ............. ............. ............. ............. ............. ............. ............. ...........47 ....47 5.6.9 Egress Manipulation Manipulation ............. .................... ............. ............. ............. ............. ............. ............. ............. ............. ............. ........47 ..47 5.6.10 Packet Header Compression .................................................... .................47 5.6.11 PWE3 .................................................................... ................................49 5.6.11.1 Encapsulation Encapsulation .............. ..................... .............. ............. ............. ............. ............ ............. .............. ............. .......49 .49 5.6.11.2 PWE3 in Customer Customer Bridge Bridge mode mode ............. .................... .............. ............. ............. ............. .........50 ...50 5.6.11.3 PWE3 in Provider Provider Edge Edge Bridge Bridge mode mode ............ ................... ............. ............. ............. ...........50 .....50 5.7

CONTROL PLANE ............ ................... .............. ............. ............. .............. ............. ............. ............. ............ ............. ............. ............. ..........51 ...51 5.7.1 ELP ............. ................... ............. ............. ............. ............. ............. .............. ............. ............. ............. ............ ............. ............. ............51 ......51 5.7.2 Link Aggregation..... Aggregation............ ............. ............. ............. ............. .............. ............. ............. ............. ............. ............. ............ ........52 ..52

2

5.7.2.1

Layer 1 radio link aggregation........ aggregation............... ............. ............ ............ ............. ............. ............52 ......52

5.7.2.2

LACP ............. ................... ............ ............. .............. .............. ............. ............. ............. ............. ............. ............. ........52 .52

MN.00329.E - 012

5.7.2.3

Static LAG ............. ................... ............. ............. ............ ............. ............. ............. ............. ............. ............. ........53 ..53

5.7.3 LLF .............. .................... ............. .............. .............. ............. ............. ............. ............ ............. ............. ............. ............. ............. ...........53 ....53 5.7.3.1

Bidirection Bidirectional al LLF.............. LLF..................... ............. ............. ............. ............. ............. ............. .............. ...........53 ....53

5.7.3.2

Parameters Parameters in Bidirection Bidirectional al LLF........... LLF.................. ............. ............. .............. ............. .............54 .......54

5.7.4 STP and RSTP............ RSTP................... ............. ............. .............. .............. .............. ............. ............. ............. ............. ............. ..........55 ....55

5.8

5.7.4.1

BPDU............... BPDU...................... .............. .............. .............. .............. .............. .............. .............. ............. ............. .........55 ..55

5.7.4.2

Root Bridge election election ............. .................... .............. ............. ............. ............. ............. ............. ............56 ......56

5.7.4.3

Root Port Election........ Election............... ............. ............. .............. ............. ............. ............. ............. ............. ........56 ..56

5.7.4.4

Designated Designated Port Election..... Election............ ............. ............. ............. ............. .............. ............. ............. .........56 ..56

5.7.4.5

Alternate Alternate Port ............. .................... ............. ............. ............. ............. ............. ............. .............. ............. ........56 ..56

5.7.4.6

STP/RSTP Configurabi Configurability........ lity.............. ............. .............. ............. ............. ............. ............. ............56 .....56

SYNCHRONIZATION SYNCHRONIZATION ............. ................... ............. ............. ............. .............. ............. ............. ............. ............ ............. ............. ............57 ......57 5.8.1 Sources................... Sources.......................... ............. ............. ............. ............. ............. ............ ............. ............. ............. ............. .............57 .......57 5.8.2 Output ............ ................... .............. ............. ............. .............. .............. .............. .............. .............. .............. ............. ............. ...........58 ....58 5.8.3 Priority Priority ............. ................... ............. .............. .............. ............. ............. ............. ............ ............. .............. .............. ............. ............58 ......58 5.8.4 Quality Quality and SSM ............ ................... .............. .............. .............. .............. .............. .............. ............. ............. .............. ...........59 ....59 5.8.5 Source settings....... settings.............. .............. .............. .............. ............. ............. ............. ............. ............. ............. ............. .............59 .......59 5.8.6 Ethernet Ethernet Interfaces Interfaces ............. .................... ............. ............ ............. .............. .............. .............. .............. .............. ............. .......60 .60

5.9

ETHERNET MAINTENANCE........ MAINTENANCE............... .............. .............. .............. ............. ............. ............. ............. ............. ............. ............. .......60 .60 5.9.1 OAM............ OAM................... ............. ............. .............. .............. ............. ............. ............. ............. ............. ............. ............. ............. ...........60 ....60 5.9.2 RMON .............. .................... ............. .............. .............. .............. .............. .............. .............. ............. ............. .............. .............. ..........62 ...62 5.9.2.1

Ethernet Ethernet Statistics Statistics ............. .................... .............. .............. .............. .............. .............. ............. .............62 .......62

5.9.2.2

RMON Counters Counters in each interface....... interface............. ............. .............. .............. .............. ..............62 .......62

5.9.2.3 5.9.2.3

Etherne Ethernett Ser Service vices s Statist Statistics ics ...... .......... ....... ...... ...... ...... ....... ....... ...... ...... ....... ....... ...... ...... ...... ....... ....63 63

5.9.3 Data Plane ............. ................... ............. ............. ............ ............. ............. ............. .............. ............. ............. ............. ............. .........64 ..64 5.9.3.1 5.10

Encryption........ Encryption............... ............. ............. ............. ............ ............. .............. .............. .............. ............. ...........64 .....64

PROGRAMMABILITY PROGRAMMABILITY ............ ................... ............. ............. ............. ............. ............. ............ ............. .............. .............. ............. ............65 ......65 5.10.1 Software .............................................................................. ..................67

5.11

AVAILABLE AVAILABLE VERSIONS............ VERSIONS.................. ............ ............ ............. ............. ............. .............. ............. ............. ............. ............. ...........67 ....67 5.11.1 AGS-20 switch.............. .......................................................................... 68 5.11.2 AGS-20 Single IF ................................................................................. ...69 5.11.3 AGS-20 Single IF/16E1 ............................................................................ 69 5.11.4 AGS-20 Dual IF ............................................................................... .......69 5.11.5 AGS-20 Dual IF/16E1 ....................................................................... .......70 5.11.6 AGS-20 Quad ETH................................. ..................................................7 0 5.11.7 AGS-20 Quad ETH/16E1 ............. ................... ............. .............. .............. .............. ............. ............. ............. ............. ........71 .71 5.11.8 AGS-20 PP Single IF/16E1 ........................................................................ 71 5.11.9 AGS-20 Dual IF/16E1 + 2STM1 + Nodal.......................................... ...........71 5.11.10AGS-20 Single IF/16E1 + 2STM1 + Nodal ................................................. 72 5.11.11AGS-20 Quad Eth/16E1 + 2STM1 + Nodal.................................................72 5.11.12AGS-20 PP Single IF/16E1 + 2STM1 + Nodal ............................................. 73 5.11.13AGS-20 Quad IF ........................................................................... .........73 5.11.14AGS-20 Quad IF/16E1 ............................................................................ 74 5.11.15AGS-20 Quad IF/16E1 + 2STM1+ Nodal....................................................74 5.11.16AGS-20-XG Quad-IF...............................................................................75 5.11.17AGS-20-XG Quad-IFw/ 16xE1..................................................................75 5.11.18AGS-20- XG Quad-IFw/ 16xE1+2xSTM1+2xN odal .......................................7 5

6

5.12

SUPPORTED ODUS.............. ODUS..................... ............. ............. ............. ............. ............. ............ ............. ............. ............. .............. .............76 ......76

5.13

SUPPORTED FULL FULL ODUS ............. ................... ............. ............. ............. .............. .............. .............. .............. ............. ............. ...........76 ....76

TECHNICAL TECHNIC AL SPECIFI SPECIFICATION CATIONS S ...... ............ ........... ........... ............ ........... ........... ............ ........... ........... ........... .......... ........... ........... .........77 ....77

6.1

IDU INTERFACES INTERFACES ............. .................... ............. ............. ............. ............ ............. ............. ............. ............. ............. ............. ............. ..........77 ...77

MN.00329.E - 012

3

6.1.1 Traffic interfaces............ interfaces.................. ............. ............. ............. ............. ............ ............. ............. ............. ............. ............. .........77 ..77 6.1.1.1 6.1.1.1

E1 (Connec (Connector tor Trib.1-8, Trib.1-8, Trib.9-16 Trib.9-16)) ...... .......... ....... ...... ...... ...... ....... ........ ....... ...... ...... ....... ......77 ..77

6.1.1.2

STM-1 electrical electrical ............. .................... .............. .............. .............. ............. ............. ............. ............. ..........78 ...78

6.1 6.1.1.3 1.3

STM1 TM1 op optical cal 5 .........................................................................78

6.1.1.4 6.1.1.4

Combo Combo ports ports LAN 1, LAN 2, LAN LAN A, LAN B........ B........... ...... ...... ....... ....... ...... ...... ...... ......79 ...79

6.1.1.5 6.1.1.5

SFP ports ports LAN5, LAN6, LAN6, LAN C, LAN D ...... ......... ...... ...... ....... ........ ....... ...... ...... ...... ...... ....... ....79 79

6.1.1.6

Ethernet Ethernet electrical electrical ports LAN3, LAN4.................. LAN4........................ ............. ............. ............79 ......79

6.1.1.7

Optical Optical XG Lan interface interface ............. ................... ............. ............. ............. .............. ............. ............ ........80 ..80

6.1.1.8 6.1.1.8

ARI (Conn (Connecto ectorr ODU A, A, ODU B, B, ODU C, C, ODU D) D) ...... ......... ....... ....... ...... ...... ...... .....80 ..80

6.1.2 Service interfaces interfaces ............. ................... ............. .............. .............. .............. ............. ............. ............. ............. ............. ..........80 ....80 6.1.2.1

LCT ............. .................... ............. ............. ............. ............. ............. ............. .............. .............. ............. ............. .........80 ..80

6.1.2.2

Alarm .............. ..................... ............. ............. ............. ............ ............. .............. .............. ............. ............. ............80 .....80

6.1.2.3

Console....... Console............. ............. ............. ............ ............. ............. ............. ............. ............. ............. ............. ............81 .....81

6.1.2.4

SYNC (SYNC-1 interface)........... interface)................. ............. ............. ............. .............. .............. .............. ........81 .81

6.1.2.5

ToD (SYNC-2 interface)............ interface).................. ............. .............. .............. .............. .............. .............. ........81 .81

6.1.2.6 6.1.2.6

1PPS (SYNC-3 (SYNC-3 interf interface) ace) ...... .......... ....... ...... ....... ....... ...... ....... ........ ....... ...... ....... ....... ....... ........ ....... ....81 .81

6.1.3 Optical indications...... indications............ ............. ............. ............. ............. ............ ............. ............. ............. ............. ............. .............81 ......81 6.1.3.1

System LEDs ............. ................... ............. .............. ............. ............. ............. ............. .............. ............. .........81 ...81

6.1.3.2

Ethernet Ethernet interface interface activity activity ............ ................... ............. ............. .............. ............. ............. ............82 .....82

6.1.3.3

PoE LEDs ............. ................... ............ ............. .............. .............. .............. .............. .............. ............. .............82 .......82

6.2

MODULA MODULATIO TION, N, BANDWIDTH BANDWIDTH AND RELEVAN RELEVANT T CAPACITY... CAPACITY....... ....... ....... ....... ...... ....... ....... ...... ....... ....... ...... .....82 ..82

6.3

POWER POWER SUPPLY SUPPLY,, CONSUM CONSUMPTIO PTION N AND AND MAX MAX CURREN CURRENT T ABSORPT ABSORPTION ION ....... .......... ...... ....... ........ ....... ....85 .85

6.4

POE - POWER OVER ETHERNET....... ETHERNET.............. .............. .............. .............. .............. .............. .............. .............. ............. ............86 ......86 6.4.1 PoE characteristi characteristics cs ............. .................... ............. ............. ............. ............. ............. ............. ............. ............. ............. ..........86 ....86 6.4.2 PoE settings settings ............. ................... ............. ............. ............ ............. ............. ............. ............. ............ ............. .............. ............. .......87 .87

6.5

IDU GENERAL CHARACTERISTICS........... CHARACTERISTICS.................. ............. ............. .............. ............. ............. ............. ............. ..............87 .......87 6.5.1 Dimensions Dimensions ............. ................... ............. .............. .............. .............. .............. .............. .............. ............. ............. .............. ...........87 ....87 6.5.2 Weight ............ ................... .............. ............. ............. .............. .............. .............. ............. ............. ............. ............. ............. ............87 ......87 6.5.3 Environment Environment conditions conditions ............ ................... .............. .............. ............. ............. ............. ............. ............. ............. ..........87 ...87

6.6

AVAILABL AVAI LABLE E ODUS ODUS AND FULL FULL ODUS ODUS ...... .......... ....... ....... ....... ...... ...... ....... ....... ...... ...... ...... ...... ....... ....... ...... ...... ....... ....... ...... ....88 .88 6.6.1 ODUs .............. ..................... ............. ............. .............. .............. .............. .............. .............. .............. ............. ............. .............. ...........88 ....88 6.6.2 Full ODUs ............. ................... ............. ............. ............. ............. ............. ............. ............. ............. ............. ............. ............ ..........88 ....88

6.7

ODUS, ODUS, DESCRIPTIO DESCRIPTION N AND TECHNICAL TECHNICAL CHARACTE CHARACTERIST RISTICS... ICS...... ....... ........ ....... ....... ........ ....... ...... ...... ......8 ...88 8 6.7.1 ODU description.... description.......... ............. ............. ............. ............. ............. ............. ............ ............. ............. ............. ............. ...........88 .....88 6.7.1.1

ODU versions........ versions............... ............. ............. .............. ............. ............. ............. ............. ............. ............ ........88 ..88

6.7.1.2

Description........... Description................. ............. ............. ............. ............. ............ ............. ............. ............. .............. .........89 ..89

6.7.1.3

IF cable interface interface ............. ................... ............. .............. ............. ............. ............. ............. ............. ..........90 ....90

6.7.1.4

Power supply................... supply.......................... ............. ............ ............. .............. ............. ............. ............. ..........90 ....90

6.7.1.5

Tx section section .............. ..................... .............. .............. ............. ............. ............. ............. ............. ............. ............90 .....90

6.7.1.6

Rx section .............. ..................... ............. ............. ............. ............. ............. ............. ............. ............. .............91 ......91

6.7.1.7 6.7.1.7

1+1 Tx system system ....... .......... ....... ........ ....... ...... ...... ...... ....... ....... ...... ....... ........ ....... ...... ...... ....... ....... ...... ....... ....91 91

6.7.1.8 6.7.1.8

Full Full ODUs, ODUs, descripti description on and technica technicall characte characteris ristic tics..... s......... ........ ....... ...... ...... ....96 .96

Section 3. INSTALLATION

7

INSTALLATION INSTALL ATION AND PROCEDURE PROCEDURES S FOR ENSURIN ENSURING G THE ELECTRO ELECTROMAGNETI MAGNETIC C COMPATIBILITY.......................................................................................................98

7.1

4

98

GENERAL GENERAL INFOR INFORMATI MATION ON TO BE READ READ BEFORE BEFORE THE INSTALL INSTALLATIO ATION... N...... ....... ....... ...... ...... ...... ...... ....98 .98

MN.00329.E - 012

7.2

GENERAL.........................................................................................................99

7.3

MECHANICAL INSTALLATION..............................................................................99 7.3.1 IDU Installation inside a rack....................................................................99 7.3.2 IDU temperature in case of rack mounting .................................................99

7.4

ELECTRICAL WIRING.......................................................................................100

7.5

OPTICAL CONNECTORS ...................................................................................101 7.5.1 SFP module installation..........................................................................101 7.5.2 SFP module removal..............................................................................102 7.5.3 SFP module for AGS-20 .........................................................................103

7.6

CONNECTIONS TO THE SUPPLY MAINS ..............................................................104

7.7

IDU-ODU INTERCONNECTION CABLE.................................................................104 7.7.1 Electrical characteristics.........................................................................104 7.7.2 Connectors ..........................................................................................104 7.7.3 Max length........................................................................................... 104 7.7.4 Suggested cable ...................................................................................104 7.7.5 IF cables in XPIC radio link.....................................................................105

7.8

GROUNDING CONNECTION ..............................................................................105

7.9

IDU-ODU CABLE GROUNDING KIT INSTALLATION...............................................106 7.9.1 Grounding kit K09283F (for RG8 or 1/8” cable) ......................................... 106 7.9.2 Grounding kit ICD00072F (for any cable with shield) .................................106

7.10 8

CONNECTORS .........................................................................................................109

8.1 9

SURGE AND LIGHTNING PROTECTION ...............................................................108

CONNECTORS ................................................................................................109

INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED ANTENNA (KIT V32307, V32308, V32309).............................................................................115

9.1

FOREWORD ...................................................................................................115

9.2

INSTALLATION KIT .........................................................................................115

9.3

REQUIRED TOOLS FOR MOUNTING (NOT SUPPLIED) ...........................................116

9.4

INSTALLATION PROCEDURE .............................................................................116

9.5

1+0 MOUNTING PROCEDURES .........................................................................117 9.5.1 Setting antenna polarization................................................................... 117 9.5.2 Installation of the centring ring on the antenna.........................................117 9.5.3 Installation of 1+0 ODU support ............................................................. 117 9.5.4 Installation onto the pole of the assembled structure ................................. 117 9.5.5 Installation of ODU (on 1+0 support)....................................................... 117 9.5.6 Antenna aiming ....................................................................................118 9.5.7 ODU grounding.....................................................................................118

9.6

1+1 MOUNTING PROCEDURES .........................................................................118 9.6.1 Installation of Hybrid.............................................................................118 9.6.2 Installation of ODUs (on hybrid for 1+1 version) ....................................... 119

10 INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED DUAL POLARIZATION ANTENNA ......................................................................................127

10.1

FOREWORD ...................................................................................................127

10.2

INSTALLATION KIT FOR STANDARD LOCK ODU ..................................................127

10.3

INSTALLATION KIT FOR FAST LOCK ODU ...........................................................127

10.4


10.5

INSTALLATION PROCEDURE.............................................................................128

10.6

STANDARD LOCK ODUS MOUNTING PROCEDURE ................................................129 10.6.1 Installation of the centring rings over the OMT.......................................... 129 10.6.2 Installation over the pole of the assembled structure: antenna, OMT and pole

MN.00329.E - 012

5

support system............................................. ........................................ 129 10.6.3 Installation of the standard lock ODUs over the OMT.................................. 129 10.6.4 Antenna aiming ..................................................................... ............... 130 10.6.5 ODU grounding............. ........................................................................ 130 10.7

FAST LOCK ODUS MOUNTING PROCEDURE ........................................................130 10.7.1 Installation of the centring rings over the OMT.......................................... 130 10.7.2 Installation of the fast lock 1+0 ODU support ...........................................130 10.7.3 Installation over the pole of the assembled structure: antenna, OMT and pole support system............................................. ........................................ 130 10.7.4 Installation of the fast lock ODUs over the OMT................................ ......... 131 10.7.5 Antenna aiming ..................................................................... ............... 131 10.7.6 ODU grounding............. ........................................................................ 131

11 INSTALLATION ONTO THE POLE OF THE ODU WITH RFS INTEGRATED ANTENNA...1 34

11.1

FOREWORD ...................................................................................................134

11.2

INSTALLATION KIT .........................................................................................134

11.3


11.4

INSTALLATION PROCEDURE.............................................................................135

11.5

1+0 MOUNTING PROCEDURES ......................................................................... 135 11.5.1 Setting antenna polarization............. ...................................................... 135 11.5.2 Installation of the centring ring on the antenna..... .................................... 136 11.5.3 Installation of 1+0 ODU support ............................................................. 136 11.5.4 Installation onto the pole of the assembled structure ................................. 136 11.5.5 Installation of ODU (on 1+0 support)........................................ ............... 136 11.5.6 Antenna aiming ..................................................................... ............... 136 11.5.7 ODU grounding............. ........................................................................ 137

11.6

1+1 MOUNTING PROCEDURES ......................................................................... 137 11.6.1 Installation of Hybrid ............................................................................. 137 11.6.2 Installation of ODUs (on hybrid for 1+1 version) .......................................137

12 INSTALLATION ONTO THE POLE OF ODU ASN/ASNK WITH STANDARD LOCK ........148

12.1

ODU COUPLING KIT ........................................................................................148 12.1.1 ODU ASN/ASNK ........................................................................... ......... 148 12.1.1.1 Fast lock coupling kit ..............................................................148 12.1.1.2 Standard coupling kit ..............................................................148

12.2

INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED ANTENNA ........... 149 12.2.1 ODU ASN/ASNK (Fast Lock) ................................................................... 149 12.2.2 ODU ASN/ASNK (Standard Lock)................................. ............................ 149 12.2.2.1 1+0 ODU .............................................................................. 149 12.2.2.2 1+1 ODU .............................................................................. 150

12.3

INSTALLATION ONTO THE POLE OF THE ODU WITH SEPARATED ANTENNA.............151 12.3.1 ODU ASN/ASNK (Fast Lock) ................................................................... 151 12.3.2 ODU ASN/ASNK (Standard Lock)................................. ............................ 151 12.3.2.1 1+0 ODU .............................................................................. 152 12.3.2.2 1+1 ODU .............................................................................. 152 12.3.2.3 Waveguide towards the antenna............................................... 154

13 INSTALLATION OF THE FULL ODU ..........................................................................161

6

MN.00329.E - 012

Section 4. LINE-UP

162

14 LINE–UP OF AGS-20...............................................................................................162

14.1

GENERAL.......................................................................................................162

14.2

SWITCH ON ...................................................................................................163

14.3

ALARM LED CHECK .........................................................................................163

14.4

CONNECTION TO EQUIPMENT .......................................................................... 163 14.4.1 Connection to LCT or LAN3 port .............................................................. 163 14.4.2 Connection using WLC ........................................................................... 164 14.4.3 CLI session using Hyperterminal (or a similar software) .............................164

14.5

RADIO LINK CONFIGURATION .......................................................................... 164

14.6

EQUIPMENT CONFIGURATION ..........................................................................164 14.6.1 IP address setting ................................................................................. 165 14.6.2 Bandwidth, modulation, TDM and Link ID setting............................ ........... 165 14.6.3 Tx frequency setting............................................................ .................. 165 14.6.4 Tx power setting ................................................................................... 166 14.6.5 Equipment ID and Agent IP setting................................................. ......... 166 14.6.6 Routing Table setting............................................................................. 166 14.6.7 Remote Element Table....................... .................................................... 166

14.7

ANTENNA ALIGNMENT AND RX POWER..............................................................167 14.7.1 ODU ASN and ODU ASNK .............................................................. ......... 167 14.7.2 Full ODU ............................................................................... ............... 168

Section 5. MAINTENANCE

170

15 ALARMS .................................................................................................................170

15.1

ALARM SYSTEM ..............................................................................................170 15.1.1 LED status ................................................................................ ........... 171 15.1.2 Alarm group.......................................................................... ............... 171

16 MAINTENANCE AND TROUBLESHOOTING ...............................................................178

16.1

GENERAL.......................................................................................................178

16.2

MAINTENANCE ...............................................................................................178 16.2.1 Periodical checks ..................................................................................178 16.2.2 Corrective maintenance (troubleshooting) ................................................ 179

16.3

TROUBLESHOOTING .......................................................................................179 16.3.1 Quality alarms ............................................................................. ......... 180 16.3.2 Radio link affected by fading.................................................................. . 180 16.3.3 Radio link affected by interference .......................................................... 181

16.4

SOFTWARE MANUAL OPERATIONS & TESTS ....................................................... 181 16.4.1 PRBS Menu ........................................................................... ............... 181 16.4.2 Radio Loop & Cmd Menu ................................................................. ....... 182 16.4.2.1 IF LOOP & RF LOOP ................................................................182 16.4.2.2 RT PSU ................................................................................. 183 16.4.2.3 TX Transmitter.......................................................................183 16.4.2.4 Carrier Only...........................................................................184

MN.00329.E - 012

7

16.4.3 Manual Operation Menu .........................................................................184 16.5

XPIC FAULT MANAGEMENT PROCEDURE.............................................................185 16.5.1 Introduction ............................................................................ ............. 185 16.5.2 XPIC Fault Management Procedure (FMP) description.................................186 16.5.2.1 Preliminary Remarks...............................................................186 16.5.2.2 Parameters considered by FMP ................................................. 186 16.5.2.3 Commands and Alarms generated by FMP .................................187 16.5.2.4 FMP: IDU-ODU Cable Alarm .....................................................187 16.5.2.5 FMP: TX_Failure Alarm............................................................189 16.5.2.6 FMP: RX_Failure/alarms, Demodulator unlock ............................ 190 16.5.2.7 FMP Reset Procedure ..............................................................190 16.5.2.8 XPIC Manual Operation ...........................................................190 16.5.2.9 Interaction between other Maintenance command and XIPC FMP ..191

16.6

MAN.OP. AND CONSEQUENTIAL ACTION FOR 1+1 XPIC HS/FD ............................. 191 16.6.1 Introduction ............................................................................ ............. 191 16.6.2 TX OFF ............................................................................ .................... 192 16.6.2.1 Hot Stand-by configuration: TX OFF.......................................... 192 16.6.2.2 Frequency Diversity configuration: TX OFF................................. 193 16.6.3 Carrier Only ............................................................................ ............. 193 16.6.4 RT PSU OFF.......................................................................... ................ 194 16.6.4.1 1+1 HOT STBY configuration: RT PSU OFF ................................. 194 16.6.4.2 Configuration Frequency diversity: RT PS OFF ............................194 16.6.5 IF Loop.............................. .................................................................. 196 16.6.5.1 System Configuration Hot-STBY: IF loop....................................196 16.6.5.2 System configuration Frequency Diversity: IF Loop ..................... 197 16.6.6 RF Loop ....................................................................... ........................ 199 16.6.6.1 System Configuration Hot-STBY: RF Loop .................................. 199 16.6.6.2 System Configuration Frequency Diversity: RF Loop....................200

17 SOFTWARE RESET ..................................................................................................201

17.1

SOFTWARE RESET ..........................................................................................201

Section 6. PROGRAMMING AND SUPERVISION

202

18 PROGRAMMING AND SUPERVISION .......................................................................202

18.1

GENERAL.......................................................................................................202

18.2

SUPERVISION ................................................................................................ 202 18.2.1 Focus on management ports................................................................... 202 18.2.2 Default values ............................................................................. ......... 203 18.2.3 Configurability ....................................................................... ............... 203 18.2.3.1 In Band DCN (L2)...................................................................203 18.2.3.2 Emulated Out of Band (L2) ...................................................... 204 18.2.3.3 Out of Band DCN (L3) .............................................................205 18.2.4 OSPF (Open Shortest Path First) Protocol .................................................206 18.2.4.1 OSPF Areas ........................................................................... 207 18.2.4.2 Virtual Links ..........................................................................209 18.2.4.3 Stub Areas ............................................................................209 18.2.4.4 Neighbours............................................................................211

8

MN.00329.E - 012

18.2.4.5

Route Summarization ............................................................ 211

18.2.4.6 OSPF programmability ............................................................211 18.2.4.7 Basic settings ........................................................................212 18.2.4.8 Area .....................................................................................213 18.2.4.9 Interface...............................................................................213 18.2.4.10 Summary Address..................................................................214 18.2.4.11 Neighbour .............................................................................215 18.2.4.12 Lsa DB.................................................................................. 215 18.2.4.13 Example DCN L3 Out Of Band with OSPF protocol .......................215

Section 7. COMPOSITION

220

19 COMPOSITION OF IDU ...........................................................................................220

19.1

GENERAL.......................................................................................................220

19.2

IDU PART NUMBER .........................................................................................220

20 COMPOSITION OF OUTDOOR UNIT.........................................................................222

20.1

GENERAL.......................................................................................................222

Section 8. LISTS AND SERVICES

232

21 LIST OF FIGURES ...................................................................................................232

22 LIST OF TABLES .....................................................................................................238

23 ASSISTANCE SERVICE ............................................................................................240

MN.00329.E - 012

9

10

MN.00329.E - 012

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 international regulations. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, without written permission from Siae Microelettronica S.p.A. Unless otherwise specified, reference to a Company, name, data and address produced on the screen displayed 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.

Section 1. USER GUIDE

1

DECLARATION OF CONFORMITY

SIAE MICROELETTRONICA Via Buonarroti, 21 - Cologno (MI) - Italy DECLARES THAT THE PRODUCT

Digital Radio Relay Systems AGS-20 complies with the essential requirements of article 3 of the R&TTE Directive (1999/05/EC) and with Directive 2011/65/EU and therefore are marked: The following standards have been applied: EN 60950-1:2006 + A11:2009 + A1:2010 - A12:2011 and EN 60950-22:2006 “Safety of information technology equipment” EN 301 489-4 v.2.1.1 (2012-11) “Electromagnetic compatibility and Radio spectrum Matters (ERM); ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 4: Specific conditions for fixed radio links and ancillary equipment and services” ETSI EN 302 217-2-2 V2.2.1 (2014-04) “Fixed Radio Systems; Characteristics and requirements for point-to-point equipment and a ntennas; Part 2-2: Digital systems operating in frequency bands where frequency co-ordinated is applied; Harmonized EN covering the essential requirements of Article 3.2 of R&TTE Directive” The equipment makes use of non-harmonized frequency bands. Following the requirements of the R&TTE Directive (article 12) and the relevant decision of the EC, in term of classification of Radio Equipment and Telecommunications Terminal Equipment and associated identifiers, the transmitting equipment shall carry the 'class 2' identifier: Cologno Monzese, 14/04/2015

MN.00329.E - 012

On behalf of SIAE MICROELETTRONICA Chairman and Executive Officer Alberto Mascetti

2

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

3

•

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 - 012

Tab.1 - Artificial respiration

Step

Description

1

Lay the patient on his back with his arms parallel to the body. If the patient is laying on an inclined plane, ma ke sure that his stomach is slightly lower than his chest. Open the patients mouth and check that there is no foreign ma tter in mouth (dentures, chewing gum, etc.).

Figure

Kneel beside the patient level with his head. Put an hand under the patient’s head and one under his neck. 2

Lift the patient’s head and let it recline backwards as far 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 oxygen 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

4

5

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 a s 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 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.

6

Start with ten rapid expirations, hence continue at a rate of twelve/fifteen expirations per minute. Go on like this until the patient has regained conscious–ness, or until a doctor has ascertained his death.

MN.00329.E - 012

4

2.2

SAFETY RULES

2.2.1

Electrostatic discharge

Electrostatic discharge (ESD), caused by hand touching semiconductor components, can destroy them and their proper operation is not guaranteed anymore. Circuitry with semiconductor components sensible to electrostatic discharge are identified by warning labels with the barred-hand symbol (see Fig.1). Precaution: •

wear cotton clothes in order not having electrostatic charging

•

handle electronics devices by means of the insertion and removal facilities only

•

handle the SFP modules at the edges only

•

ground the rack

•

wear a conductive band (see Fig.2) connected to the rack ESD connection nut by means of a coiled cord (see Fig.3)

•

work in an ESD safe work area with a grounded work surface

•

conductible connect all test equipment and instruments to the rack ESD connection nut

•

do not use ESD sensitive devices unless the previous rules are not satisfied.

Fig.1 - Components electrostatic charge sensitive indication

In order to prevent the units from being damaged while handling, it is a dvisable to wear an elasticized band (Fig.2) around the wrist ground connected through coiled cord ( Fig.3).

Fig.2 - Elasticized band

5

MN.00329.E - 012

Fig.3 - Coiled cord

2.2.2

Laser safety

SIAE equipment are designed to ensure that operating personnel are not endangered by laser radiation during normal system operation. This device has Class I LASER modules: it is not required to have a laser w arning label or other laser statement (IEC 60825-1).

MN.00329.E - 012

6

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 s hould 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. Bus iness 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 b atteries

according to law.

7

MN.00329.E - 012

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 - 012

8

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

9

MN.00329.E - 012

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 - 012

10

11

-

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

MN.00329.E - 012

-

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 - 012

12

13

-

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.

MN.00329.E - 012

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 ma de up by a complete range of interfaces (Gigabit/Fast Ethernet, E1, STM-1) towards both IF compatible SIAE ODU and Ethernet compatible 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 capabilities, 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-technology 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 - 012

14

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/ALFOplus2 and ALFOplus80/ALFOplus80HD

•

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 Macrocell backhaul layer. Such network evolution demands for data tra ffic aggregation capability and some management intelligence in the network nodes to avoid flood of management traffic and prevent overwhelming complexity towards central NMS. AGS-20 (EasyCell Gateway) acts as s mall-cell cluster aggregator and manager providing the following features: •

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

15

Functionalities

•

Modulation from 4QAM to 2048QAM

•

Hitless ACM adaptive code and modulation

•

Hitless Rlag

•

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

MN.00329.E - 012

•

Flow Based Ingress Policing (CIR & EIR definition)

•

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)

•

AES Radio Payload Encryption (only Ethernet).

5.3

RADIO LINK CONFIGURATIONS

AGS-20 split mount radio system can support multiple configurations depending on the following characteristics: •

hardware protection

•

space diversity protection

•

frequency diversity protection

•

management of radio directions

•

up to 4 Rlag (Physical Radio Link Aggregation).

In addition the AGS-20 can be connected to SIAE Full outdoor equipment through all the available LAN interfaces, supporting multiple radio directions.

5.3.1

Ethernet Layer 1 Radio Link Aggregation

AGS-20 is able to simultaneously manage N radio links outgoing from the available IF interfaces. In case the N links are parallel (i.e. deployed between the same two sites) the Ethernet capac ity can be aggregated in order to increase the capacity of the Ethernet connection. In this case the Link Aggregation mechanism is not based on MAC hashing, but on a more efficient Layer 1 distribution of the traffic over the two radio channels. The traffic received from the line interfaces, after the L2 Ethernet switch processing, is fragmente d and labeled with proprietary protocols. The additional labeling is used to keep trace of the original order of the fragments before to send it over the radio. On the receiver side the fragments are recomposed with the original order. In this way the correct packet order is preserved, independently from the frequency channel over which each packet has been sent. The fragments are sent over the air in order to balance the load between the N frequency channels. The balancing mechanism is able to take into account also the imbalance in the available capacity on the N radio links (for example, in the case an ACM modulation down-switch occurs only on one radio branch). The final result is that the traffic is balanc ed over the N 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 channels). The maximum capacity that can be aggregated is relevant to N times the maximum channel available on AGS-20. However, due to the additional fragment labeling used by the protocol there is a slight loss in terms of available capacity over the radio link. This loss is dependent from the Ethernet packet length.

MN.00329.E - 012

16

5.3.2

Hitless RLag

Hitless RLag consists in making a “hitless" management (removal and reintroduction) of concatenated ODU (ASN/ASNK) from Physical LAG according to current ACM profile.

Hitless Physical Level Aggregation

Up to 4 ODU in case of IDU Quad-IF

IDU AGS-20 (all HW versions)

Fig.5

The hitless PLA management behaves in this way: •

continuously checks every link degradation in order to remove a bad quality link in advance from LAG (link status estimator)

•

if necessary removes the degrades link from PLA.

The Link Status Estimator uses a new profile in the ACM range: the Hitless profile (= Lower profile +1). This new profile introduces two more thresholds: •

radio link removal threshold

•

radio link re-introduction threshold

Every time in Rx the S/N of a radio link of the group goes under the Removal threshold, that radio link leaves the hitless PLA and every time th e S/N overtakes the Reintroduction thresh old that radio link enters again in the group. Removal and the reintroduction are performed without errors.

Fig.6

17

MN.00329.E - 012

5.4

BRIEF RADIO LINK DESCRIPTION

5.4.1

1+0

Description: •

no HW or diversity protection

•

single radio direction

•

single channel radio capacity.

5.4.2

1+1 hot stand-by

Description: •

ODU HW protection

•


•

single channel radio capacity

•

1 antenna with balanced or unbalanced hybrid.

5.4.3

1+1 space diversity

Description: •

ODU HW protection

•

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

1+1 frequency diversity

Description: •

ODU HW protection

•

radio frequency diversity protection

•


•


•

1 antenna with hybrid or circulator.

MN.00329.E - 012

18

5.4.5

1+1 frequency and space diversity

Description: •

ODU HW protection

•

radio frequency diversity protection

•

radio space diversity protection

•


•


•

2 antennas without hybrid/circulator losses.

5.4.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 chann el with double capacity is available on the radio obtained by means of layer 1 link aggregation of the 2 physical radio channels.

5.4.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 chann el with double capacity is available on the radio obtained by means of layer 1 link aggregation of the 2 physical radio channels.

5.4.8

AGS-20 multiple direction

Description:

19

•

no HW or diversity protection

•

multiple radio directions can be managed through IF interfaces (one per each IF)

•

multiple Full-Outdoor radio links can be connected by means of LAN interfaces

•

single channel radio capacity on each direction.

MN.00329.E - 012

5.4.9

Radio link configurations with AGS-20 Single IF interface

Only 1+0 radio configuration is available with Single IF IDUs. Supported port configurations are: •

N.C. stands for Not Connected and it means that the interface is unused.

•

SINGLE stands for single not protected connection. It can be realized with 1+0 radio configuration. Tab.2 - Single IF system configurations table

Port Configurations

SYV

ODU-A

0

1.1.0

(1+0) or N.C.

1+0

f 1

f

Fig.7 - 1+0 System configuration

5.4.10

Radio link configurations with AGS-20 Dual IF interface

5.4.10.1

Port clusters configuration

In this HW configuration 2 IF interfaces are available. Fig.8, Fig.9 and Fig.10 show the available port clusters for each specific radio configuration. Protection cluster 1: ODU-A; ODU-B

Fig.8 - (1+1) Protection: one cluster is available

(2+0)XPIC cluster 1: ODU-A; ODU-B

Fig.9 - (2+0)XPIC: one cluster is available

MN.00329.E - 012

20

(2+0) FD cluster 1: ODU-A; ODU-B

Fig.10 - (2+0)FD: one cluster is available

5.4.10.2

Dual IF system configurations

System configuration is compound of 3 configurations related to the 2 IF ports and, when necessary, up to 1 cluster identification (ports<->cluster association). Supported port configurations are: •


•

SINGLE stands for single not protected connection. It can be realized with 1+0 radio configuration.

•

PROTECTION stands for protected connection. It can be realized with one of the following radio configurations:

•

-

1+1 HSB

-

1+1 SD (not displayed in the system configuration table because in practice it is a 1+1 HSB with space diversity antenna installation)

-

1+1 FD.

SHARING or RLAG stands for the Physical Layer Aggregation of more than one radio channels in order to set up a single radio bundle. It can be realized with one of the following radio configurations: -

(2+0)FD and (4+0)FD

-

(2+0)XPIC and (4+0)XPIC. Tab.3 - Dual IF system configurations table

Port configurations

SYV

ODU-A

ODU-B

0

1.1.0

(1+0) or N.C.

(1+0) or N.C.

1

1.1.0

(1+1) HSB cluster 1

(1+1) HSB cluster 1

2

1.1.0

(1+1) FD cluster 1

(1+1) FD cluster 1

3

1.1.0

(2+0) RLAG-FD cluster 1


4

1.1.0

(2+0) RLAG-XPIC cluster 1


Tab.4 - Port configuration 0: Up to 2 independent radio links

21

Port Configurations

SYV

ODU-A

ODU-B

0

1.1.0

(1+0) or N.C.

(1+0) or N.C.

MN.00329.E - 012

1+0

1+0

f 1

f 2

f

Fig.11 - 2x(1+0) different directions

Tab.5 - 1+1 protected radio link

Port configurations

SYV

ODU-A

ODU-B

1

1.1.0

(1+1) HSB cluster 1

(1+1) HSB cluster 1

2

1.1.0

(1+1) FD cluster 1

(1+1) FD cluster 1

Hot Standby solution f1

f

1+1

Frequency Diversity solution f1

f2

f

Fig.12 - Port configuration 1, 2: (1+1) cluster 1

Tab.6 - Dual IF: N+0 RLAG (Physical Radio Link Aggregation)

Port configurations

SYV

ODU-A

ODU-B

3

1.1.0



4

1.1.0



MN.00329.E - 012

22

CCDP solution f1

f

ACAP solution f1

f2

2+0

f

ACCP solution f1

f2

f

Fig.13 - Port configuration 3, 4: (2+0) cluster 1

5.4.11

Radio link configurations with AGS-20 Quad IF interface

5.4.11.1

Quad IF: Port clusters configurations

In order to support protection for XPIC configuration a specific interconnection between modem chips must be provided. Fig.14, Fig.15, Fig.16, Fig.17, Fig.18 and Fig.19 show the available port clusters for each s pecific radio configuration.

Protection cluster 1: ODU-A; ODU-C

Protection cluster 2: ODU-B; ODU-D

Fig.14 - (1+1) protection: two clusters are available

(2+0)XPIC cluster 1: ODU-A; ODU-B

(2+0)XPIC cluster 2: ODU-C; ODU-D

Fig.15 - (2+0) XPIC: two clusters are available

23

MN.00329.E - 012

(2+0) FD cluster 3: ODU-A; ODU-C

(2+0) FD cluster 1: ODU-A; ODU-B

(2+0) FD cluster 2: ODU-C; ODU-D

Fig.16 - (2+0) FD: three clusters are available

XPIC Protection sub-cluster 1: ODU-A; ODU-B

XPIC Protection cluster: 4 IF ports

XPIC Protection sub-cluster 2: ODU-C; ODU-D

Fig.17 - (1+1) XPIC protection: all IF ports are part of the cluster

(4+0) FD cluster: 4 IF ports

Fig.18 - (4+0) FD: all IF ports are part of the cluster

(4+0) XPIC sub-cluster 1: ODU-A; ODU-B

(4+0) XPIC cluster: 4 IF ports

(4+0)XPIC sub-cluster 2: ODU-C; ODU-D

Fig.19 - (4+0) XPIC: all IF ports are part of the cluster

5.4.11.2

Quad IF: system configurations

System configuration is compound of 4 configurations related to the 4 IF ports and, when necessary, up to 2 clusters identification (ports<->cluster association). Port configurations that must be supported are: •


•

SINGLE stands for single not protected connection. It can be realized with 1+0 radio configuration.

•

PROTECTION stands for protected connection. It can be realized with one of the following radio configurations: -

1+1 HSB

MN.00329.E - 012

24

•

•

-

1+1 SD (not displayed in the system configuration table because in practise it is a 1+1 HSB with space diversity antenna installation)

-

1+1 FD.

SHARING or RLAG stands for the Physical Layer Aggregation of more than one radio channels in order to set up a single radio bundle. It can be realized with one of the following radio configurations: -

(2+0) FD and (4+0) FD

-

(2+0) XPIC and (4+0) XPIC.

XPIC PROTECTION stands for protected connection of two (2+0) XPIC radio bundle. It can be realized with the following radio configuration: -

25

1+1 XPIC (3 possible protection sub-types: HSB; SD (not displayed in the system configuration table because in practise it is a 1+1 HSB with space diversity antenna installation) and FD)

MN.00329.E - 012

Tab.7 - Quad IF: system configurations table

Port Min SYV configuration

ODU-A

ODU-B

ODU-C

ODU-D

0

1.6.0

(1+0) or N.C.

(1+0) or N.C.

(1+0) or N.C.

(1+0) or N.C.

1

1.6.0

(1+1) HSB cluster 1

(1+0) or N.C.

(1+1) HSB cluster 1

(1+0) or N.C.

2

1.6.0

(1+1) FD cluster 1

(1+0) or N.C.

(1+1) FD cluster 1

(1+0) or N.C.

3

1.6.0



(1+0) or N.C.

(1+0) or N.C.

4

1.6.0



(1+0) or N.C.

(1+0) or N.C.

5

1.6.0

(3+0) FD

(3+0) FD

(3+0) FD

(1+0) or N.C.

6

1.5.0

(4+0) FD

(4+0) FD

(4+0) FD

(4+0) FD

7

1.5.0

(4+0) XPIC

(4+0) XPIC

(4+0) XPIC

(4+0) XPIC

8

1.6.0


(1+0) or N.C.


(1+0) or N.C.

9

1.6.0

(1+0) or N.C.

(1+1) HSB cluster 2

(1+0) or N.C.

(1+1) HSB cluster 2

10

1.6.0

(1+0) or N.C.

(1+1) FD cluster 2

(1+0) or N.C.

(1+1) FD cluster 2

11

1.6.0


(1+1) HSB cluster 2


(1+1) HSB cluster 2

12

1.6.0


(1+1) FD cluster 2


(1+1) FD cluster 2

13

1.6.0

(1+1) HSB cluster 1

(1+1) FD cluster 2

(1+1) HSB cluster 1

(1+1) FD cluster 2

14

1.6.0

(1+1) FD cluster 1

(1+1) HSB cluster 2

(1+1) FD cluster 1

(1+1) HSB cluster 2

15

1.6.0

(1+1) HSB cluster 1

(1+1) HSB cluster 2

(1+1) HSB cluster 1

(1+1) HSB cluster 2

16

1.6.0

(1+1) FD cluster 1

(1+1) FD cluster 2

(1+1) FD cluster 1

(1+1) FD cluster 2

17

1.6.0





18

1.6.0





19

1.6.0





20

1.6.0





21

1.6.0

(1+1) XPIC/HSB

(1+1) XPIC/HSB

(1+1) XPIC/HSB

(1+1) XPIC/HSB

22

1.6.0

(1+1) XPIC/FD

(1+1) XPIC/FD

(1+1) XPIC/FD

(1+1) XPIC/FD

Tab.8 - Quad IF: up to 4 independent 1+0 radio links

Port Min SYV configuration 0

1.6.0

MN.00329.E - 012

ODU-A

ODU-B

ODU-C

ODU-D

(1+0) or N.C.

(1+0) or N.C.

(1+0) or N.C.

(1+0) or N.C

26

1+0

1+0

1+0

1+0

f 1

f 2

f 3

f 4

f

Fig.20 - Port config 0: Nx(1+0) different directions

Tab.9 - Quad IF: 1+1


ODU-A

ODU-B

ODU-C

ODU-D

1

1.6.0

(1+1) HSB cluster 1

(1+0) or N.C.

(1+1) HSB cluster 1

(1+0) or N.C

2

1.6.0

(1+1) FD cluster 1

(1+0) or N.C.

(1+1) FD cluster 1

(1+0) or N.C

9

1.6.0

(1+0) or N.C.

(1+1) HSB cluster 2

(1+0) or N.C.

(1+1) HSB cluster 2

10

1.6.0

(1+0) or N.C.

(1+1) FD cluster 2

(1+0) or N.C.

(1+1) FD cluster 2


f

1+1


f2

f

Fig.21 - Port config 1 and 2: (1+1) cluster 1

27

MN.00329.E - 012


f

1+1


f2

f

Fig.22 - Port config 9 and 10: (1+1) cluster 2

Tab.10 -N+0 RLAG (Radio Link Aggregation L1)


ODU-A

ODU-B

ODU-C

ODU-D

(2+0)RLAG-FD cluster 1


(1+0) or N.C.

(1+0) or N.C.

(1+0) or N.C.

(1+0) or N.C.

3

1.6.0

4

1.6.0

5

1.6.0

(3+0)FD

(3+0)FD

(3+0)FD

(1+0) or N.C

6

1.5.0

(4+0)FD

(4+0)FD

(4+0)FD

(4+0)FD

7

1.5.0

(4+0)XPIC

(4+0)XPIC

(4+0)XPIC

(4+0)XPIC

8

1.6.0


(1+0) or N.C.


(1+0) or N.C.

(2+0)RLAG-XPIC cluster 1 (2+0)RLAG-XPIC cluster 1

MN.00329.E - 012

28

CCDP solution f1

f

ACAP solution f1

f2

2+0

f

ACCP solution f1

f2

f

Fig.23 - Port config. 3, 4: (2+0) cluster 1

3+0

ACCP solution f1

f2

f3

f

Fig.24 - Port config 5: (3+0)

29

MN.00329.E - 012

CCDP solution f1

f2

f

ACAP solution f1

f2

f3

f4

4+0

f

ACCP solution f1

f2

f3

f4

f

Fig.25 - Port config 6 and 7: (4+0)

ACAP solution f1

f2

2+0

f

ACCP solution f1

f2

f

Fig.26 - Port config 8: (2+0) cluster 3

Tab.11 - 2+0 RLAG & 1+1


ODU-A

ODU-B

ODU-C

ODU-D

11

1.6.0


(1+1) HSB cluster 2


(1+1) HSB cluster 2

12

1.6.0


(1+1) FD cluster 2


(1+1) FD cluster 2

MN.00329.E - 012

30

2+0


ACAP solution f1

f

1+1

f2

f


ACCP solution f1

f2

f

f2

f

Fig.27 - Port config 11 and 12: (2+0) cluster 3 & (1+1) cluster 2

Tab.12 - 2 independent 1+1


ODU-A

ODU-B

ODU-C

ODU-D

13

1.6.0

(1+1) HSB cluster 1

(1+1) FD cluster 2

(1+1) HSB cluster 1

(1+1) FD cluster 2

14

1.6.0

(1+1) FD cluster 1

(1+1) HSB cluster 2

(1+1) FD cluster 1

(1+1) HSB cluster 2

15

1.6.0

(1+1) HSB cluster 1

(1+1) HSB cluster 2

(1+1) HSB cluster 1

(1+1) HSB cluster 2

16

1.6.0

(1+1) FD cluster 1

(1+1) FD cluster 2

(1+1) FD cluster 1

(1+1) FD cluster 2

1+1

Hot Standby solution

Hot Standby solution

f1

f1

f


f

1+1

Frequency Diversity solution

f2

f1

f2

f

f

Fig.28 - Port config from 13 to 16: (1+1) cluster 1 & (1+1) cluster 2

Tab.13 - 2 independent 2+0 RLAG (Physical Link Aggregation L1)

Port Min SYV configuration 17

1.6.0

18

1.6.0

19

1.6.0

20

1.6.0

31

ODU-A (2+0) RLAG-FD cluster 1

ODU-B

ODU-D

(2+0) RLAG-FD cluster 1 (2+0) RLAG-XPIC cluster 2 (2+0) RLAG-XPIC cluster 2

(2+0) RLAG-XPIC cluster 1 (2+0) RLAG-XPIC cluster 1 (2+0) RLAG-FD cluster 1

ODU-C






(2+0) RLAG-XPIC cluster 1 (2+0) RLAG-XPIC cluster 1 (2+0) RLAG-XPIC cluster 2 (2+0) RLAG-XPIC cluster 2

MN.00329.E - 012

CCDP solution f1

CCDP solution

f

f1 2+0

f

ACAP solution f1

ACAP solution f1

f

f2

f

ACCP solution f1

ACCP solution f1

f2

2+0

f2

f

f2

f

Fig.29 - Port config from 17 to 20: (2+0) cluster 1 & (2+0) cluster 2

Tab.14 - 1+1 XPIC


ODU-A

ODU-B

ODU-C

ODU-D

21

1.6.0

(1+1) XPIC/HSB

(1+1) XPIC/HSB

(1+1) XPIC/HSB

(1+1) XPIC/HSB

22

1.6.0

(1+1) XPIC/FD

(1+1) XPIC/FD

(1+1) XPIC/FD

(1+1) XPIC/FD

1+1 XPIC Hot Standby solution f1

f

1+1 XPIC

1+1 XPIC Freq. Div. solution f1

f2

f

Fig.30 - Port config 21 and 22: (1+1) XPIC HSB or FD

5.5

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.

MN.00329.E - 012

32

5.5.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.11 AVAILABLE VERSIONS), can be digital (ETH) and/or analog (IF)

In Tab.15 are listed the technical parameters of the switch and in Fig.32 is represented the Ethernet block diagram. Tab.15 - 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

Address Learning capacity

16000 MAC entries

To be shared among all VLAN based tables

MAC Aging Time

10 ÷ 1000000s

software selectable

802.1q VLANs

Up to 256 (with VLAN ID: 0-4094)

VLANs Stacking 802.1ad supported

MEF EVCs

Up to 128

Per port

Packet Buffer Total Size

96Mbytes

Reserved/Shared between ports and queues

8 Output Ethernet Queue (Radio Side)

Up to 8 for each port

Queue depth is software selectable

Queue Weight with scheduling algorithm

Strict Priority, D-W.R.R., Strict Priority + D-W.R.R.

Software selectable

QoS Priority Classification

Per port, IEEE 802.1p, IPv4 ToS/ DSCP

Software selectable

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

Up to 4 interfaces (Eth/IF) depending on Hw version

Fig.31 - AGS-20 Ethernet block diagram

33

MN.00329.E - 012

Ex0/2

SFP

XG-LAN 2 Up to 10Gbps

PHY 10G Ex0/1

SFP

4xETH A

Up to 4 interfaces (Eth/IF) depending on Hw version

Gi0/7

B

Gi0/8

Gi0/5 Gi0/4

C

Gi0/1

D

Gi0/6

PHY

Gi0/3

XG-LAN 1 Up to 10Gbps

RJ45

LAN4

RJ45

LAN3

E t h e r n e t c o n n e c t i o n s

RJ45 LAN2

SFP

Gi0/2

RJ45 LAN1

SFP

Fig.32 – AGS-20 Ethernet block diagram

5.5.2

Traffic treatment

With reference to 802.1ad, the switch can be set through WEBLCT or CLI in predefined configurations: •

Customer Bridge (default mode): in this mode the L2 Ethernet switch is a 802.1q aware component. There is interoperability with customer devices that are not able to manage S-VLANs, as they are not 802.1ad aware: only C-VLAN modality is used. Moreover, in this mode the transport over the radio link is more efficient since a double tag is not added.

•

Provider Bridge: in this mode the L2 Ethernet switch is a 802.1ad aware component. The switch operates with S-VLAN frames, forwarding the packets accordingly. Further, in accordance with MEF requirements (basically MEF 10.2 and MEF 6.1) each EVC is identified using a S-tag, added by the equipment at UNI ports (at Customer Edge) or rec eived at NNI ports (at Provider Edge). If C-VLANs are also involved a further classification is necessary as in Tab.16 Tab.16 - Switch bridge modes

Bridge Mode (802.1ad)

Description

The network element operates accorCustomer Bridge (or “VLAN ding to 802.1q VLAN bridge. This mode bridge” or “C-VLAN bridge) is supported for compatibility with networks that do not manage the S-tag

Components

C-VLAN

A system comprising a single S-VLAN Provider component implemented in accordance Core Bridge with clause 5 of IEEE Std 802.1q

S-VLAN only

Switch operates as a 802.1ad provider edge bridge with S-VLAN component and at least one C-VLAN component

S-VLAN and C-VLAN

Provider Bridge Provider Edge Bridge

MN.00329.E - 012

Port Types

- Provider Network Port - Provider Network Port - Customer Network Port - Customer Edge Port

34

5.6

DATA PLANE

In the next paragraphs are listed the Ethernet features offered by the switch of AGS-20.

5.6.1

Ethernet features

5.6.1.1

Auto-negotiation

Auto-negotiation standards are regarding speed from 10BaseT to 1000BaseT, Full Duplex. In addition, for 1000BaseT, auto-negotiation determines the master/slave configuration between the PHYs at the ends of the link, necessary to establish the source of the timing control of each SETS. Auto-negotiation is not necessary for optical interface ports with speed of 1Gbps or 2.5Gbps both Full Duplex.

5.6.1.2

MDI/MDI-X

For Electrical interfaces only, available values are MDI, MDI-X and Auto mode.

5.6.1.3

Ingress Filtering

In each interface, it is possible to specify which frame types are accepted or denied. The Ingress Filtering criteria are based on the following configurable parameters: •

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 Cu stomer Network Port the only option avail-

able is “Untagged and Priority Tagged”. •

35

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

MN.00329.E - 012

5.6.1.4

MTU

MTU correspond to the maximum dimension (in byte) of the data field accepted by the interface without the bytes of Ethernet header and CRC (frame size between <46-12266> in Byte (Jumbo Frames). Packets that exceed the configured MTU size are dropped. This configuration can be either global for the Ethernet switch or assigned per port.

5.6.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 table

•

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

MAC Learning Rules

The MAC learning mechanism operates on VLAN ID basis: the incoming packet is associated to a VLAN (determined 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 MA C address. The Learning process in VLAN independent: the information learned by a VLAN is not u sed by other VLAN’s to forward their frames. The MAC Learning mode has to be activated configuring the Ethernet switch “Bas ic 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 (discarded). The frames of the following protocols can be managed by the AGS-20 switch: •

Dot1x

•

LACP

•

STP

•

GVRP

•

GMRP

•

IGMP

MN.00329.E - 012

36

5.6.1.7

MAC Forwarding Rules

L2 forwarding function establishes the egress port for each incoming frames, on the base of its MAC address and/or VLAN ID. Consequently, the MAC forwarding rule of each LAN interface is the following: •

MAC Destination Address + VID Basis: the incoming packet is associated to a VLAN (determined by Outer-VLAN tag or assigned as Port VID). Within the ports belonging to the same VLAN, the egress port is then determined on the base of the frame MAC destination address

•

VID Basis: if the MAC learning option is disabled, the forwarding is performed among all ports configured 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.6.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 compliant with standard IEEE 802.1q and 802.1ad (QinQ).

5.6.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.6.2.2

VLAN Stacking - QinQ

The additional tag is defined in the standard IEEE802.1ad. VLAN stacking differentiates the traffic at different 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.6.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:

37

-

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

MN.00329.E - 012

-

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, Customer Network Port and Provider Network Port. The Customer Edge Port (CEP) performs the following actions: -

Create a PtoP connection between two ports of the switch through an EVC, mapping an ingress C-tagged packet to an S-tagged packet one-to-one emulating the virtual communication between 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 Stagged 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 “portbased” 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 untagged (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 tw o or more ports of the switch, defining the proper network interfaces and mapping the incoming C- tagged frames into an S-tagged frame.

5.6.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: -

MN.00329.E - 012

Costumer EtherType: fixed to 0x8100

38

-

-

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 corresponding to the C-VID of the frames

2. In Provider Bridge the EVC is identified by an S-tag. Configurable mapping rules are (per each UNIport): -

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 below: -

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

-

5.6.2.5

-

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

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 another 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, regardless of VLAN ID or destination MAC address. In the example below, port forwards frames just to port, forwards frames just to port as well and port forwards frames just to and

-

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

QoS Management

QoS features available on Ethernet LAN and radio ports are summarized in Fig.33.

39

MN.00329.E - 012

Fig.33 – QoS block diagram

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

MN.00329.E - 012

40

•

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). The default 802.1p map, see Fig.34, cannot be removed but only modified.

Fig.34 - Default 802.1p PCP-queue map

The default Tos (DSCP) map is in Fig.35.

Fig.35 - Default ToS (DSCP) map

5.6.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:

41

•

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

MN.00329.E - 012

•

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

•

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 class ification 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 s ingle Class with a single Layer 2 ACL and creates the c orrespondence 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 consequent 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.6.4

Policing

Traffic policing, also known as rate limiting, defines a bandwidth profile (BWP) depending on the Service Level Specification that has been agreed upon by the Subscriber and the Service Provider. Specifically, this phase defines a set of traffic rate limits and performs actions on traffic that is not conformed 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 occasionally a customer is allowed to send, in condition of no congestion

5.6.4.1

Metering

The bandwidth profile rates are enforced through a meter algorithm which is commonly implemented as a token bucket algorithm. The MEF has defined a two rate three color marker (trTCM) algorithm which marks packets based on two rates and two burst sizes, guaranteeing only the transmission of the smaller one, and implemented via two token buckets. Basing on the ingress filtering policies, it is possible to assign different bandwidth profiles (i.e. CIR/EIR and CBS/EBS profiles) to the incoming Ethernet services, defining specific CIR/EIR parameters basing on: •

the 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 fra mes into 3 "colors", each denoting a certa in compliance level: •

green – Frames within the CIR / CBS compliance level

MN.00329.E - 012

42

•

yellow – Frames exceeding the CIR/CBS but are within the EIR/EBS. These frames are delivered as "best effort". The equipment may drop some or all of these frames based on congestion conditions in the network (available yellow tokens)

•

red – Frames not conforming to the bandwidth profile are dropped, either because the rate exceeds the sum of CIR and EIR or because there are insufficient yellow tokens to admit a frame that is within EIR/EBS

SIAE switch is color blind: the packets are considered green upon entering the metering process and are marked as yellow or red if the traffic class exceeds the correspondent bandwidth limits. 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.6.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, matching 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.6.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:

43

MN.00329.E - 012

In case of WRED congestion template, the e quipment OS can manage up to 4 different traff ic 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: -

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.36 – Red Curve

5.6.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), w ith the only difference between line ports and radio ports that can have different configurations. The following are the available type of queue configurations with the values of the related parameters:

MN.00329.E - 012

44

•

full dynamic memory

see Tab.17

•

priority based memory allocation (1 radio port and 2 radio port)

see Tab.18 and Tab.19

•

uniform memory allocation (1 radio port and 2 radio ports)

see Tab.20 and Tab.21

•

line ports dynamic memory

see Tab.22 Tab.17 – 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.18 – Priority based memory (1 radio port)

Parameter Type

Buffer Size


2048


81.5


14.5


32,16,8,4,2,1,0.512,0.256


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.19 – Priority based memory (2 radio ports)

Parameter Type

Buffer Size


2048


82


14


16,8,4,2,1,0.512,0.256,0.128


8,4,1,1,0.750,0.200,0.200,0.200


0.512,0.256,0.128,0.064,0.032,0.032,0.032,0.032


0.750,0.200,0.200,0.200,0.200,0.200,0.200,0.200

Tab.20 – Uniform memory (1 radio port)

45

Parameter Type

Buffer Size


2048


76.5


19.5

MN.00329.E - 012


4


4


0.512


4.3

Tab.21 – Uniform memory (2 radio ports)

Parameter Type

Buffer Size


2048


54


42


2


7.6


0.256


4.2

Tab.22 – Line ports dynamic memory (2 radio ports)

Parameter Type

Buffer Size


2048


0


96


0

Line ports dynamic memory per queue [Mbyte]

17

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

MN.00329.E - 012

46

5.6.8

Egress Shaping

This feature manages output shaping for constant and bursting traffic out of a port, limiting the egress throughput defining a rate limiter on it. Differently from the input filtering policy, the packets are not discarded when the egress rate is reached, but buffered and released with the selected output rate. The shaping process retains excess packets in the buffer of the port and then schedules the excess for later transmission over increments of time. The result of traffic shaping is a smoothed packet output rate. The shaper is configured with a shaper template, two different parameters can be configured to drive the rate limiter: •

rate-value: defines the maximum output rate for constant traffic in kbit/s

•

burst-value: defines the maximum output burst in kbit

Output rate limiter acts after the traff ic is queued, so scheduling is done according to defined output bandwidth. No rate-limiter is defined as a default value and the burst-value is an optional one: if it is not specified 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 shaper. 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 template 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.6.9

Egress Manipulation

Per each port it’s possible to define the packet format to egress. In particular the actions that can be configured are: •

no change in packet format

•

remove outer tag, based on port criterion or port + VID criterion.

5.6.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 compression/decompression module is defined as the context of the compression. Hop-by-hop Header Compression h as the basic idea to store at both ends of a radio link all the informa tion that are repeated identically in all the packets belonging to the same data flow and transmit only the variable fields with good gains in throughput in case of long communication streams with a great number of packets (for example, real-time communication).

47

MN.00329.E - 012

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 c apacity 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 decompress ion function will operate in the opposite direction. On the WEB LCT platform is available the contextual area of the Header Compression functionality for the Ethernet packets in output from the LAN ports to the radio. 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.37.

Fig.37 - WEBLCT Header Compression field

The parameter “Context Depth” indicates the total s ize 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

MN.00329.E - 012

48

•

Ethernet-over-MPLS (EoMPLS)

•

IPv4 and IPv6

•

UDP, TCP, RTP, GTP-U, IP Tunneling on GTP-U

5.6.11

PWE3

The transmission of TDM channels over Packed switched Networks (PSN) can be emulated by Pseudo-Wire Emulation Edge to Edge (PWE3). Using the PWE3 feature on AGS-20, we have to take into account of the following maximum capabilities: •

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

Encapsulation

PWE3 has an encapsulation process called "Structure Agnostic TDM over Packet" (SAToP, see RFC4553). This process places a P seudo-Wire Control Word in front of the TDM data, plus, if se t, 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.38 is shown the PW Control Word by:

Fig.38 – 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: •

49

for ARI-1 IDU version

ODU B

MN.00329.E - 012

•

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.

5.6.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 cre ated in the VLAN table, assigning at least the PWE 3 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 version 4 syntax

•

if IPv6-UDP is set fills in UDP destination port, destination IP address and source IP address in version 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.6.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 between 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 paragraph.

MN.00329.E - 012

50

5.7

CONTROL PLANE

In this chapter are described all the AGS-20 features belonging to the Control Plane. Some of these features are commonly deployed in Ethernet switches and routers for traffic control (e.g. RSTP, etc…), while other features are microwave specific implementations that a llow the interaction between the radio channel and the AGS-20 embedded Ethernet switch (e.g. LLF, LACP, RSTP, etc…). In the following paragraphs it is described the SIAE implementation of these features and some application examples.

5.7.1

ELP

ELP (Ethernet Line Protection) is a proprietary feature that protects a LAN interface against cable failure or accidental disconnection. It allows connecting the unit to another netw ork 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 Manager of WEBLCT. Two LAN ports must be added to the logical bundle in the New Aggregation window in LA Manager of WEBLCT. Note: in Provider switch mode, the ELP can be implemented only among ports of Provider Network type

In Fig.39 there is an example of ELP

Fig.39 – ELP between a SIAE AGS-20 and an external switch

51

MN.00329.E - 012

5.7.2

Link Aggregation

Link Aggregation can be managed in different ways: •

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

5.7.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 c ase 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 balancing 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 capacity 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 an d ODU B) in the switch settings just one interface is available and c onfigurable, i.e. ODU A port.

5.7.2.2

LACP

LACP (Link Aggregation Control Protocol) allows aggregating multiple Ethernet parallel connections into a single logical Ethernet connection. The main purpose of this protocol is to provide a s ingle aggregated capacity 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 network devices. So all the LACP links are bundled to provide an in creased capacity, however, at th e 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 w hich 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 setting this configuration the minimum number of active ports has to be equal to 2 (N+1 with N ≥2).

MN.00329.E - 012

52

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.

•

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 th e previous frame fields through a XOR f unction (three by three). The result of this fu nction 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.7.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.7.3

LLF

LLF (Link Loss Forwarding) is a feature that forces a local LAN in a LOS state in case of radio failure or remote LAN failure. It consists in a controlled shout-down of the Ethernet link thanks to the propagation of a Ethernet link failure condition. The aim of this feature is to inform an external device (i.e. customer switch/router) about the radio link failure. When the switch/router receives the LOS signal on the LAN interface connected to the AGS-20, it can take the proper counter actions, for example switching the traffic to the backup path. The LLF can be configured on each LAN interface (not on radio port) and the main applications are the following: •

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.7.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 t he need to shut down the link in both directions even if there is only a unidirectional link failure.

53

MN.00329.E - 012

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.

5.7.3.2

Parameters in Bidirectional LLF

In LLF window (see Fig.40) 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 unidirectional 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 cons idered 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 activated 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 aggregated links)

-

enable: the failure of both links triggers the LLF activation (logic AND between the aggregated links).

Fig.40 – Select the LAN port that sends LLF status

In the “Mapped circuit on current port selection” area is possible to create several circuits a ssociated to the LAN port selected in the area above. As in Fig.41, the circuit is mainly identified by the following parameters: •

circuit ID: from #1 to #8

•

link ID: from #1 to #4; it represent a specific radio interface (depending on HW version of the AGS20, 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 propagate a LOS alarm into the circuit toward the remote equipment in case just one port is in LOS condition 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 - 012

54

Fig.41 – Select the circuit that manages the LLF protected LAN port

5.7.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 modern Ethernet networks, adding new bridge port roles in order to speed conve rgence 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.7.4.1

BPDU

All switches with RSTP enabled generate and process data messages called Bridge Protocol Data Units (BPDUs). 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 redundant links. The operation of RSTP is as follows:

55

•

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.

MN.00329.E - 012

5.7.4.2

Root Bridge election

Through the BPDU the switches compare Root Bridge ID and Sender Bridge ID (six byte MAC address head er and a two byte Bridge Priority header). The switch with the smallest Bridge Priority is automatically elected as the Root Bridge. If Bridge Priority is the same on all switches then the switch with the smaller MAC address is elected as the Root Bridge.

5.7.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 Pa th Cost field in each BPDU ( four bytes) according 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.7.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 lowes t 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.7.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 rece ive nor transmit frames) ensuring that the network is loop-free.

5.7.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 information. 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 - 012

56

•

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 context (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, Designated 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 generates a LOS alarm. For the same reason, in case of radio failure, it is recommended to enable the LLF protocol

•

RSTP configuration settings as Hello Time, Forward Delay and Max Age.

5.8

SYNCHRONIZATION

Different approaches can be done to carry the synch signal in existing networks: •

exploit TDM circuits if they are kept in the network while starting carrying Ethernet traffic (valid when the network is deployed with hybrid native TDM/Eth approach)

•

use Synchronous Ethernet, by synchronizing the Ethernet line CK to a reference one. In this way, the Ethernet connections are converted to synchronized lines. In this case the precision of the CK recovered in the peripheral site is guaranteed by the fac t that the CK is transferred at ph ysical 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 rebuilt 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.8.1

Sources

The selectable sources of synchronization are listed and explained below: •

•

57

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 correspondent 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)

MN.00329.E - 012

•

Radio Interface (ODU/LANx): It is very important to keep in mind that all the radio interfaces are seen as independent sources at the rec eiver 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 synchronization, 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.8.2

Output

Once the SIAE equipment is synchronized, the clock signal has to be passed toward external equipment through different interfaces: •

E1: In order to modify the output timing of the E1 stream the user has to enable the “Retiming” option for each E1 If the “Retiming” option is not enable, the E1s pass through the MW without any synch. modification remaining with its original CK

•

T3-SYNC: this interface is configurable as 2 Mbit/s or 2 MHz channel, always locked to the SETS -

2MHz: in this configuration the port can be used to provide a 2MHz CK to an external equipment

-

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 radio 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 electrical 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 signa l is provided onto all the LAN interfaces.

5.8.3

Priority

Each synch source can be enable or disable, being available or not in the selection process. If no sync source is enabled, the clock of the system will work as “free running”, locked to the internal oscillator and marked with a SEC quality level. WARNING: if all the sources are disabled, the synchronization management is disabled.

A priority method is used to define the preferred source: nine priority levels are ass igned to each synchronization source and are used in case two or more sources have the same quality (with SSM protocol enabled). 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 received 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 occu rs, 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 - 012

58

5.8.4

Quality and SSM

The unit supports the SSM protocol to forward the quality of the synchronization sources and to manage their classification (ITU-T G.781 and ITU-T G.8264). As the SSM transmits the quality of the transmitting source, it represents a unidirectional channel between tx CK and rx CK. According to SSM, the classification of clock quality, from better to worse, is: •

PRC: Primary Reference Clock – Best quality clock reachable (Cesium Clock)

•

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 quality 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 sec ond 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 qua lity 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.8.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 parameter 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 qua lity available. If the 2 MHz signal is the only source available, the unit uses the internal clock instead of a source without quality.

59

MN.00329.E - 012

This can be avoided by overwriting the Rx qua lity in input of the 2 MHz cable. S ame approach can be used in case a source of synchronization does not support SSM.

5.8.6

Ethernet Interfaces

First of all, the SSM can be enabled on all the LAN interfaces. When the SSM is not ac tive, in order to properly propagate the clock signal through the Ethernet electrica l interface, it is necessary to set correctly the master/slave option as the SyncE transmission has to be unidirectional, 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 autonegotiated). 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 mas ter/slave assignment has to be re-negotiated with a conse quent loss of traffic. In fact, this re-negotiation implies an interruption 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.9

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 netw ork path, topology, operators or network layer that carries the traffic between service endpoints.

5.9.1

OAM

Through CLI interface, OAM configuration is ava ilable 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 providers. Eight MEG Levels are and roles are: -

Customer Domain is the higher and includes both ends of the Ethernet service (three MEG Levels: 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 - 012

60

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 specified. 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 c apable of initiating and terminating OAM frames for fault management 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 interfac e can have a MEP. Once chosen the interface, th e 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 interface 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 equipment, 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 Messa ges is adjustable from 1 to 8192 cons ecutive 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 message 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:

61

•

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 different)

•

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.

MN.00329.E - 012

The trap messages of the first four alarms are active by default option, while the trap of the last alarm has to be activated from CLI interface.

5.9.2

RMON

RMON (Remote Monitoring) is a standard whose function is monitoring the activity of a LAN network. SIAE equipment support RMONv1, first MIB, as defined in RFC2819. This MIB contains real-time LAN statistics e.g. utilization, collisions and CRC errors. These counters are managed locally into the radio equipment 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 th ese data are seen as the RMON His tory.

5.9.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. Th is 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” c onfigured 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).

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

MN.00329.E - 012

62

•

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 address

•

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 notintegral 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 collection)

•

Pkts xx to yy oct. Rx: the total number of packets (including bad packets) received that were between 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 pac kets (including bad packets) received that were more than 1024 octets in length (excluding framing bits but including FCS octets) (Not available for history collection).

All the counters described above are part of the RMON statistics a nd it is not possible to collect only a subset of them. It is however possible to select on which equipment interface the RMON statistics are activated. 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.9.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)

•

Port & Priority, i.e. frame priority imprinted on p-bits of the related tag (C or S-tag).

Also for services an Ethernet Service Statist ics has to be created before enabling the Ethernet Service H istory. 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 variables:

63

•

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

MN.00329.E - 012

•

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

Data Plane

5.9.3.1

Encryption

Payload encryption is implemented for protecting Ethernet user data transferred over the radio link aga inst sniffing and decoding by unauthorized entities. In fact normally input and output system user data a re unprotected Ethernet frames and their coding is performed by external equipment, when required. AGS20 encryption is based on the block cipher AES128 or AES 256, i.e. a deterministic algorithm operating on fixed-length groups of bits, in counter (CTR) mode of operation, that describes how to repeatedly apply a the cipher's single-block operation to securely encrypt amounts of data larger than a block. AES algorithm is implemented into AGS20 programmable logic (FPGA module).

Fig.42

“Radio payload encryption” is the equipment feature key activating the AE S payload cryptography.

MN.00329.E - 012

64

Fig.43

Payload Encryption Configuration Once this feature is enabled in the system, the e ncryption is configurable through the AGS-20 GUI, in order to set the AES engine inside the programmable logic. Otherwise its configuration is forbidden and there is no way to cipher the radio link data stream. It is important that the WEB LCT session is opened through the HTTPS protocol and that the security protocols HTTPS and SNMPv3 associated to that specific user are enabled.

Fig.44

During the configuration is possible to enable or disable the radio encryption func tion in the programmable logic module, previously allocating the required resources. Additionally, the user can specify the ciphering algorithm used for the coding process and, eventually, the encryption key.

5.10

PROGRAMMABILITY

AGS-20 radio system is managed by a microprocessor that makes it totally programmable via software to perform the following functions: •

65

radio link management

MN.00329.E - 012

•

•

•

1

-

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

-

Security Management (SSH, SFTP)

-

Secure HTTP access (HTTP)

-

Radio Payload Encryption

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.

Not available in actual system version.

MN.00329.E - 012

66

5.10.1

Software

AGS-20 is provided with an embedded Web Server a nd can be locally/remotely controlled by a HTTP browser 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 registration

•

NMS5UX/LX that can manage a subnetwork of thousand SIAE network elements and nodal configuration.

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.

5.11

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 obsolete replaced with GAI0215-2

•

AGS-20 DUAL IF/16E1

(SYV 1.1)

GAI0216-1obsolete replaced with GAI0216-2

•

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

•

AGS-20-XG DUAL-IF

(SYV 1.7)

GAI0230

•

AGS-20-XG DUAL-IFw/16xE1

(SYV 1.7)

GAI0231

•

AGS-20-XG DUAL-IFw/16xE1+2xSTM1-2xNODAL(SYV 1.7)

GAI0232

Up to SYV 1.6 all the AGS-20 versions have the following functionalities:

67

•

2x GE (1Gbps electrical ports @ RJ-45 connector)

•

2x SFP (1Gbps electrical or optical, 2.5Gbps optical ports)

MN.00329.E - 012

•

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.

With SYV 1.7 GAI0232, GAI0234, GAI0235: •

2x GE (1Gbps electrical ports @ RJ-45 connector)

•

2x COMBO (1Gbps electrical @ RJ-45 or 1Gbps optical @ SFP )

•

2x 1/10Gbps 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.11.1

AGS-20 switch

In Fig.45 the basic version of AGS-20 is shown. All the other version have this set of interfaces beside of a variety of ports towards SIAE ODUs. 48V „ª

-+

LCT URG NURG SW TEST

1PPS

R

M 5A

250V

2 1

LAN

2 1

LAN

4 3

LAN

6 5

SYNC T OD

ON

Console A LA RM

Fig.45 - AGS-20 switch (GAI0212-1)

MN.00329.E - 012

68

5.11.2

AGS-20 Single IF

In AGS-20 Single IF (see Fig.46) 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 SFP (1Gbps electrical or optical, 2.5Gbps optical ports) 48V „ª ODU A

LAN C

-+

LCT

LAND URG NURG SW TEST

1PPS

R

M 5A

ON

250V

2 1

2 1

LAN

4 3

LAN

6 5

LAN

SYNC TOD

Console ALARM

Fig.46 - AGS-20 Single IF (GAI0213-1)

5.11.3

AGS-20 Single IF/16E1

In AGS-20 Single IF/16E1 (see Fig.47) the following functionalities are available: •


•


•


•


•


•

16x E1 (@ 2x SCSI connectors) to be managed as native TDM or PWE3. 48V „ª ODU A

LAN C

Trib. 1-8

URG NURG SW TEST

Trib. 9-16

-+

LCT

LAND

1PPS

R

M 5A

250V

2 1

LAN

2 1

LAN

4 3

LAN

6 5

SYNC TOD

ON

Console ALARM

Fig.47 - AGS-20 Single IF/16E1 (GAI0214-1)

5.11.4

AGS-20 Dual IF

In AGS-20 Dual IF (see Fig.48) the following functionalities are available:

69

•

radio interface protection and L1 aggregation

•


•


•


•


•


•

double power connector.

MN.00329.E - 012

Fig.48 - AGS-20 Dual IF (GAI0215-2)

5.11.5

AGS-20 Dual IF/16E1

In AGS-20 Dual IF/16E1 (see Fig.49) the following functionalities are available: •


•


•


•


•


•


•

16x E1 (@ 2xSCSI connectors) to be managed as native TDM or PWE3

•


Fig.49 - AGS-20 Dual IF/16E1 (GAI0216-2)

5.11.6

AGS-20 Quad ETH

In AGS-20 Quad Eth (see Fig.50) the following functionalities are available: •


•

2x COMBO (1Gbps electrical @ RJ45 or 1Gbps optical @SFP) with PoE functionalities

•


•

double power connector. POE

LAN A

POE

LANC

LAND

LAN B

2


1PPS

R

1 2 1

LAN

2 1

LAN

4 3

LAN

6 5

SYNC T OD

Console A LA RM

M10A 250V

ON 48V „ª -+

Fig.50 - AGS-20 Quad ETH (GAI0222-2)

MN.00329.E - 012

70

5.11.7

AGS-20 Quad ETH/16E1

In AGS-20 Quad Eth/16E1 (see Fig.51) the following functionalities are available: •

Ethernet connectivity compatible with SIAE Full-Outdoor (ALFOplus80, ALFOplus80HD, ALFOplus, ALFOplus2, etc.....)

•

2x COMBO (1Gbps electrical @RJ45 or 1Gbps optical @SFP) with PoE functionalities

•


•

16xE1 (@ 2x SCSI connectors) to be managed as native TDM or PWE3

•


LAN A

Trib. 1-8

LANC

POE

POE

LAND

LAN B

2


Trib.9-16

1PPS

R

1 2 1

LAN

2 1

LAN

4 3

LAN

6 5

SYNC T OD

Console A LA RM

ON 48V „ª -+

M10A 250V

Fig.51 - AGS-20 Quad ETH/16E1 (GAI0223-2)

5.11.8

AGS-20 PP Single IF/16E1

In AGS-20 PP Single IF/16E1 (see Fig.52) 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)

•


•

16xE1 (@ 2xSCSI connectors) to be managed as native TDM or PWE3

•


Fig.52 - AGS-20 PP Single IF/16E1 (GAI0225-1)

5.11.9

AGS-20 Dual IF/16E1 + 2STM1 + Nodal

In AGS-20 Dual IF/16E1 + 2STM1 + Nodal (see Fig.53) the following functionalities are available:

71

•


•


•


•


•


•


•

TDM cross connect matrix for TDM routing line and radio side

MN.00329.E - 012

•


•

2xSTM1 (STM1-1 and STM1-2)

•

2xNodal Bus (NBUS1 and NBUS2) for TDM routing between adjacent IDUs 2

•

double power connector

•

up to 32 PWE3 services.

Fig.53 - AGS-20 Dual IF/16E1 + 2STM1 + Nodal (GAI0217-2)

5.11.10

AGS-20 Single IF/16E1 + 2STM1 + Nodal

In AGS-20 PP Single IF/16E1 + 2STM1 + Nodal (see Fig.54) the following functionalities are available: •


•


•

Ethernet connectivity compatible with SIAE full-outdoor (ALFOplus80, ALFOplus80HD, ALFOplus, ALFOplus2, etc....)

•


•


•

16xE1 (@2xSCSI connectors) to be managed as native TDM or PWE3

•

TDM cross-connect matrix for TDM routing line and radio side

•


•


•


Fig.54 - AGS-20 single IF/16E1 + 2STM1 +Nodal (GAI0218-1)

5.11.11

AGS-20 Quad Eth/16E1 + 2STM1 + Nodal

In AGS-20 Quad Eth/16E1 + 2xSTM1 + Nodal (see Fig.55) the following functionalities are available:

2

•


•

2xCOMBO (1Gbps electrical @RJ45 or 1Gbps optical @SFP) with PoE functionalities

•


Not working in actual system version.

MN.00329.E - 012

72

•


•


•


•

2xNodal Bus (NBUS1 and NBUS2) for TDM routing between adjacent IDUs. 2

•


•


Fig.55 - AGS-20 Quad Eth/16E1 + 2STM1 + nodal (GAI0224-2)

5.11.12

AGS-20 PP Single IF/16E1 + 2STM1 + Nodal

In AGS-20 PP Single IF/16E1 + 2STM1 + Nodal (see Fig.56) the following functionalities are available: •


•


•


•


•


•

Double power connector

•


•


•


•


•


•


Fig.56 - AGS-20 PP Single IF/16E1 + 2STM1 + Nodal (GAI0226-1)

5.11.13

AGS-20 Quad IF

In AGS-20 Quad IF (see Fig.57) the following functionalities are available:

73

•


•


•


•


MN.00329.E - 012

•


Fig.57 - AGS-20 Quad IF (GAI0219-1)

5.11.14

AGS-20 Quad IF/16E1

In AGS-20 Quad IF/16E1 (see Fig.58) the following functionalities are available: •


•


•


•


•


•


•


Fig.58 - AGS-20 Quad IF/16E1 (GAI0220-1)

5.11.15

AGS-20 Quad IF/16E1 + 2STM1+ Nodal

In AGS-20 Quad IF/16E1 + 2STM1 + Nodal (see Fig.59) the following functionalities are available: •


•


•


•


•


•


•


•


•


•


Fig.59 - AGS-20 Quad IF/16E1 + 2STM1 + Nodal (GAI0221-1)

MN.00329.E - 012

74

5.11.16

AGS-20-XG Quad-IF

In AGS-20- XG Quad IF (see Fig.60) the following functionalities are available: •


•


•


•


•


•

2x1/10Gbps optical@XFP

Fig.60 - AGS-20-XG Quad-IF (GAI0233)

5.11.17

AGS-20-XG Quad-IFw/ 16xE1

In AGS-20-XG Quad-IFw/ 16xE1(see Fig.61) the following functionalities are available: •


•


•


•


•


•


•


•

2x1/10Gbps optical@XFP

Fig.61 - AGS-20-XG Quad-IFw/ 16xE1 (GAI0234)

5.11.18

AGS-20-XG Quad-IFw/ 16xE1+2xSTM1+2xNodal

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

75

•


•


•


•


•


MN.00329.E - 012

•


•


•


•


•


•

2x1/10Gbps optical@XFP.

Fig.62 - AGS-20-XG Quad-IFw/ 16xE1+2xSTM1+2xNodal (GAI0235)

5.12

SUPPORTED ODUS

The following ODUs can be connected to AGS-20 by means of ARI interface (IF interface): •

ASN 3

•

ASNK.

5.13

SUPPORTED FULL ODUS

The following Full ODUs can be connected to AGS-20 by means of DRI interface (Ethernet interface):

3

•

ALFOplus

•

ALFOplus80HD

•

ALFOplus2.

Required ASN software version: N00054-03 (maximum modulation form supported 256QAM).

MN.00329.E - 012

76

6

TECHNICAL SPECIFICATIONS

6.1

IDU INTERFACES

In the following paragraphs are listed the electrical cha racteristics of all the. interfaces present in the AGS20 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 4

•

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

4

77

Depending on roadmap availability.

MN.00329.E - 012

Output side -

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 u p to 16E1 tributaries organized on two 50-pin SCS I 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 5

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



•

Max attenuation of the input cable

12.7 dB at 78 MHz (

15 dB from 8 MHz to 240 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

6.1.1.3

STM1 optical

5

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 c onnectors. Electric interface has 1.0/2.3 connectors. The characteristics of all the possible optical interfaces are summarised in Tab.23. Tab.23 - Optical interface characteristics

Interface

Ref.

Launched power (dBm)

Minimum sensitivity (dBm)

Operating wavelength

Transceiver

Fibre

Distance (km)

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

5

Depending on roadmap availability.

MN.00329.E - 012

78

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.

6.1.1.4

Combo ports LAN 1, LAN 2, LAN A, LAN B

Ports LAN1 and LAN2 are COMBO interfaces and can be with electrical or optical interface (software configurable). •

max bitrate

1Gbps

•

electrical connector type

RJ45 IEEE 10/100/1000BaseT

•

optical Connector type

SFP LC, see par. 7.5.3 SFP module for AGS-20

In GAI0222-2, GAI0223-2 LAN A, LAN B support PoE (see par. 6.4 POE - POWER OVER ETHERNET).

PoE •

output voltage

54 Vdc

•

max current

1.7 A

Ports can be set as UNI or NNI.

6.1.1.5

SFP ports LAN5, LAN6, LAN C, LAN D

LAN5 and LAN6 can be equipped with SFP module with Optical or Electrical interface.

SFP optical interface •

max bitrate

1Gbps (2.5Gbps if connected to SIAE ALFOplus80HD, ALFOplus2, AGS-20)

•

connector type

SFP LC, see par. 7.5.3 SFP module for AGS-20

SFP electrical interface •

bitrate

1Gbps

•

connector type

RJ45, see par. 7.5.3 SFP module for AGS-20

All the ports can be set as UNI or NNI.

6.1.1.6

Ethernet electrical ports LAN3, LAN4

Ports LAN3 and LAN4 are with electrical interface: •

connector type RJ45

IEEE 10/100/1000BaseT

•

max bitrate

1Gbps.

All the ports can be set as UNI or NNI and used for DCN. By default LAN3 port is set as Management Port.

79

MN.00329.E - 012

6.1.1.7

Optical XG Lan interface

AGS-20 XG family provides 2 LAN Optical port SFP+ with Rate 1/10 GB/s interface (see par. 7.5.3 SFP module for AGS-20). Note: due to the fact that the validated SFP modules list is always under revision, please refer to SIAE for

the last updated list with the related part number. Possible SFP+ modules suggested: •

10GBASE-SR (Short reach) Media type: Serial multi-mode Wavelength: 850 nm Max range: 300m

•

10GBASE-LR (Long reach) Media type: Serial single-mode Wavelength: 1310 nm Max range: 10Km

6.1.1.8

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 inte rface 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

•

telemetry ODU -> IDU 5.5 MHz

•

transceiver management signals 388 kbit/s bidirectional

•

remote power supply voltage direct from battery voltage.

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. User IN: typical Open/GND: •

OPEN or Vin > 1.5V -> Alarm

MN.00329.E - 012

80

•

GND or Vin < 0.5V -> No Alarm.

Alarm/No-alarm state is user configurable by LCT. Tab.24 - Alarm characteristics

Maximum switching power

30W (resistive)

37.5VA (resistive)

Maximum switching voltage

220Vdc

250Vac

Contact ratings

6.1.2.3

Maximum switching current

1A

Maximum carrying current

1A

Console

Serial connection with RJ45 connector for console access. -

Serial connection parameters

6.1.2.4

115200 bps 8-N-1-N

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 connector, 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.25. Tab.25 - Front panel system LEDs

81

Name

Colour

State/Alarm

Function

NURG

Red

Active when ON

Minor alarm

MN.00329.E - 012

6.1.3.2

Name

Colour

State/Alarm

Function

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

Ethernet interface activity

Link/Active indication is close to relevant connector for each electrical or optical Ethernet interface, see Tab.26. Tab.26 - Electrical/Optical Ethernet interface status LEDs

Name

Colour

State/Alarm

Function

Speed

Yellow

0 Blink/s = No link 1 Blink/s = 10 Mb/s 2 Blink/s = 100 Mb/s 3 Blink/s = 1000 Mb/s

Interface speed

Link/Active

Green

OFF = Link down ON = Link up wo/ activity Blink/s = Link up w/activity

Data presence on Tx or Rx

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.27). Tab.27 - Meaning of PoE LEDs

6.2

Alarm LED (Red)

Power LED (Green)

Meaning

On

On

Cable open

Off

On

PoE OK

On

Off

Cable short circuit

Off

Off

PoE off

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

MN.00329.E - 012

82

•

83

ANSI: (future evaluation)

MN.00329.E - 012

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 us ed during TDM traffic reconfiguration for avoiding permanent loss of remote terminal due to air frame incompatibility at different TDM traffic allocation.

Ethernet throughput Tab.28 - Net radio throughput in Mbit/s versus channel bandwidth for AGS-20 equipment

Net radio throughput (Mbit/s) Modulation type

Channel bandwidth (MHz) 7

14

28

56

4QAMs

8.5

17.5

36.5

72.0

4QAM

10.0

20.5

42.0

84.5

16QAMs

17.5

35.5

72.5

144.0

16QAM

20.5

42.5

83.5

165.5

32QAM

24.5

50.5

104.5

207.0

64QAM

30.0

63.5

131.5

262.0

128QAM

36.0

75.5

156.5

310.5

256QAM

42.0

87.5

180.0

358.5

512QAM

46.5

97.5

200.0 (189.5) a

399.5 (378.0) a.

1024QAM

51.5

107.0

223.5 (213.0) a.

446.0

2048QAM

-

111.0

233.5

471.5

Net radio throughput with XPIC b Modulation type

MN.00329.E - 012

Channel bandwidth (MHz) 7

14

28

56

4QAMs

-

17.0

34.5

70.0

4QAM

-

19.5

41.0

82.0

16QAMs

-

35.5

71.5

140.0

84

16QAM

-

42.5

82.5

162.0

32QAM

-

50.5

103.5

202.0

64QAM

-

63.5

129.5

258.0

128QAM

-

76.0

156.5

306.0

256QAM

-

87.0

177.0

353.0

512QAM

-

97.0

197.0 (186.5) a.

393.0 (367.0) a.

1024QAM

-

106.0

220.0 (209.5) a.

439.0

2048QAM

-

-

-

-

a.

The Net Radio Throughput values in brackets refer to ASN ODU.

b.

The Net Radio Throughput values refer to a single polarization.

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 c hannel 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.

6.3

POWER SUPPLY, CONSUMPTION AND MAX CURRENT ABSORPTION

Power Supply (PS) interface is us ed to support DC powering only. Consumption and max current are (guaranteed values): -

85

IDU GAI0212-1

< 29W; < 0.6A

MN.00329.E - 012

-

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

-

IDU GAI0233

<89W; <1.85A

-

IDU GAI0234

<96W; <2A

-

IDU GAI0235

<105W; <2.2A

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

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

PoE characteristics

PoE functionalities can be enabled at the same time on LAN A and LAN B. Characteristics are:

MN.00329.E - 012

86

•

max power available on each port

85W

•

max voltage available in output

55 Vdc

•

max cable length

100m

•

overcurrent protection

common on both the ports.

6.4.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.5

6.5.1

IDU GENERAL CHARACTERISTICS

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

Weight

Weight of AGS-20 IDU is 2.8 kg or less according to versions.

6.5.3

87

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

MN.00329.E - 012

-

ODU max height

4000m

-

Storage condition

according to T.1.2 ETSI EN 300 019-1-1 (weather protected, not temperature controlled storage locations)

6.6

AVAILABLE ODUS AND FULL ODUS

6.6.1

ODUs

In Tab.29 are listed the ODUs that can be connected to ARI ports. Tab.29 - ODUs that can be connected to AGS-20

ODUs

4QAM/256QAM

512QAM/1024QAM

2048QAM

ASN a

Available b

Only with feature upgrade

Not available

ASNK

Available

Available

Available

a.

Only High Gain modem profile

b.


6.6.2

Full ODUs

The full ODUs that can be connected to DRI ports are: •

ALFOplus

•

ALFOplus80HD

•

ALFOplus2

6.7

ODUS, DESCRIPTION AND TECHNICAL CHARACTERISTICS

6.7.1

ODU description

6.7.1.1

ODU versions

Two ODU versions are available: ASN and ASNK. In the following pages eventual differences are pointed out.

MN.00329.E - 012

88

The ODU (refer to Fig.63) consists of a two shell aluminium mechanica l 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 circulator or branching unit for the connection towards the antenna.

ASN ODU The ASN ODU is shown in Fig.63 (single ODU) and in Fig.64 (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.64 (single ODU with F15 GHz) and in Fig.65 (single ODU with F15 GHz). Electrical and mechanical characteristics are listed in a separate addendum relevant to ODU frequency.

6.7.1.2

Description

The blocks that arrange the ODU are the following:

89

•

cable interface

•

power supply

•

Tx section

•

Rx section

•

1+1 branching unit

MN.00329.E - 012

6.7.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 MH z FSK modulated carriers, carry the telemetry channel. Th is latter consists of two 388 kbit/s streams one from IDU to ODU with the information to manage the ODU ( RF power, RF frequency, 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.7.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.7.1.5

Tx section

Refer to block diagram shown in Fig.66. The 330 MHz QAM modulated carrier from the cable interface (see chapter 6.7.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 f ilter give rise to a second IF Tx carrier the freque ncy 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 conversion mixer is SSB type with side band selection. 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 details). The regulated output power is kept constant against amplifier stage gain variation by a feedback including the AGC. Before reaching the antenna side the RF signal at the output of MMIC passes through the following circuits: •

a 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.69) 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.

MN.00329.E - 012

90

6.7.1.6

Rx section

The RF signal from the Rx passband filter is sent to a low noise amplifier that improves the receiver sensitivity. The following down–converter translates the RF frequency to approximately 765 MHz. The conversion 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.7.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.67 and Fig.68. The transmitter switchover is controlled by Processor and the attenuation of the stand-by transmitter is at least 50 dB.

Reference tooth O-ring ODU side flange

ASN version ASNK version (for frequency ≤ 15 GHz)

"N"

"BNC"

Ground bolt

Fig.63 - ASN or ASNK ODU

91

MN.00329.E - 012

Suncover (optional)

ASN version ASNK version (for frequency ≤15 GHz)

Fig.64 - Final 1+1 assembly with ASN or ASNK ODU

MN.00329.E - 012

92

ODU 1+0

ODU 1+1 (Standard lock) Fig.65 - ASNK ODU (for frequency > 15 GHz)

93

MN.00329.E - 012

a n n e d e i t n s a

x

C I M M

m r a l a r e w o P x T

O L x T C G A

. l ) ) t K t o N a r S t N A x n S A T o U P c U D D O ( O ( B d B d 0 2 0 3 o t o t 0 0

T x T F I

C G A

r e l l o y r t y r r i t n i t o u u c c c r r i o i i c d c F a F r I R o t o t o t

c d V

0 z H 3 3 M

s / t 8 i 8 b 3 k

z D 5 . H O 5 M M z 5 . H 5 M

O L x R

P µ

x R F I

x R m r a l a U n o D i O t - a c i U n D I u m m o C

P µ

. z i e l l b a a u C q e

V 8 4 -

l i a F O C V l r t T c R

y d r t n e a b m e e s l e a T b

l i a F O C V T R

I S S R

P µ

t O i L n x F u T I l r t c s l p r m l t o A c o l

m r a l A C G A x T

c d V

A N L

l i a F O C V T R

0 z H 4 1 M

l r t c s / t 8 i 8 b 3 k z 5 . H M 7 E M 1 D

z 5 . H 7 M 1

) h t y g e d l n t i i i b c d a w a i r d p n a n a e v a c p e ( b d

0 z 4 H 1 M

C G A

m r a l a C G A x R

e e c a l f b r a e C t n i e p y t N

C N B

I S S R

Fig.66 - ODU block diagram

MN.00329.E - 012

94

Tx side SW control

Rx side

Antenna side Tx side SW control

Rx side

Fig.67 - 1+1 hot stand–by 1 antenna

Tx side SW control

First antenna

Rx side

Tx side SW control Second antenna Rx side

Fig.68 - 1+1 hot stand–by 2 antennas

95

MN.00329.E - 012

Remo Remote te PRx PRx dBm

Local

Remote Rx

Tx

Thresh High

PTx PTx actua actuati tion on

PRx recording level

Thresh Low µP

µP PTx control Transmission

Rx

Tx

of PTx PTx con control trol

Hop attenuation (dB) Loca Locall PTx PTx dBm

PTx PTx max. max. 30 dB (ODU ASNK) 20 dB (ODU ASN) ATPC range PTx PTx min. min.

Hop attenuation (dB)

Fig.69 - ATPC operation

6.7.1. 6.7 .1.8 8

Fulll OD Ful ODUs, Us, de descr scrip iptio tion n and tec techni hnical cal cha charac racter terist istic ics s

Full ODU description See manual of the relevant Full ODU.

Full ODU characteristics See manual of the relevant Full ODU.

MN.00329.E - 012

96

97

MN.00329.E - 012

Section 3. INSTALLATION

7

INSTALLATION AN AND PR PROCEDURES FO FOR EN ENSURING THE ELECTROMAG ELECTROMAGNETIC NETIC COMPATIBILITY

7.1 7. 1

GENERA GENE RAL L INF INFOR ORMA MATI TION ON TO BE RE READ AD BE BEFO FORE RE TH THE E INS INSTA TALL LLAATION

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 21 7-4-2 for the relevant frequency band. The equipment is composed by the following separate units: •

radio radio unit unit (outd (outdoor oor)) with with or without without integ integral ral antenn antenna a

•

Base Baseba band nd (in (ind door oor)

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 - 012

98

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 s hipped 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 w hole system are described in the following paragraphs an d it must be done only by service person suitably trained.

7 .3

MECHANICAL INSTALLATION

7 .3 .1

IDU Installation inside a rack

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. 7. 3.2 2

IDU ID U te tem mpe pera ratu ture re in cas ase e of rac ack k mou ount ntin ing g

Depending on the IDU, the installation inside a rack has these prerogatives: •

AGS-20 AGS-20 diff differe erent nt than than QUAD QUAD IF IF – IDUs IDUs can can be stack stacked ed

•

AGS-20 QUAD QUAD IF (GAI0219-1, (GAI0219-1, GAI0220-1, GAI0221-1) - a free air gap of at least least 1/2 RU (22mm) (22mm) must be left above each IDU unit.

More general and comprehensive guidance of the installation of subrack into ETSI racks can be found in ETSI TR 102 489.

IDU thermal characteris characteristics tics •

IDU operating temperature range:

from -5°C to +45°C.

•

Intake air grille position

front panel and lateral panels

•

Outlet hot air grille position

rear panel

•

etwee en intake air and and outlet air ∆T betwe

<15° 15°C (di (diffe fference nce of the air temperatu ature measured in outlet hot air from rear gratings and the front/lateral intake air gratings)

Unobstructed air passages must be provided for ventilation purposes. The distance given below are to be considered measured from the relevant vertical face of a parallelepiped circumscribing the IDU: •

99

lateral lateral and front front intake intake air grating gratings: s: leave at least 6cm of clear clear space, no cabling in front of the gratings

MN.00329.E - 012

•

rear ventilat ventilation ion grating: grating: leave leave at least least 2cm of clear clear space, space, no cabling cabling in front front of the the gratings. gratings.

After installation the temperature of incoming air can be measured by means of a thermometer, leaning close to the IDU intake air gratings: the temperature value must remain inside the IDU operating temperature range declared above In Fig.70 Fig.70 are are highlighted the direction of fresh air entering the IDU from the front and the side panels and the hot air outgoing from the rear panel.

Out

TOP VIEW Side in

Side in

Front in Fig.70 – Ventilation air flows in AGS-20 IDU

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.30 shows Tab.30 shows the characteristics of the cables to be used and the flying connector types.

MN.00329.E - 012

100

Tab.30 - Characteristics of the cables

Interconnecting points

Type of connector terminating the cable

Type of cable/conductor

Battery

3 pin P04184

Max section of each wire = 1.5 sq.mm a b c

Tributary signals

SCSI 50 pin male connector

8 conductor cable different for 75 Ohm and 120 Ohm signals

Alarm

RJ 4 5

Standard CAT5 cable

LCT

RJ 4 5

Standard CAT5 cable

NB U S

RJ 4 5

F035998 - 0.3m superflex F03597 - 0.5m 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

R J 45

Standard CAT5 cable

Console

RJ 4 5

F03588

G ND

Faston male type

Section area  6 sq. mm.

a. Select the the correct correct size and and type of cable for any installation installation case case according according to specific specific length. b.

Power Power cabl cable e operat operative ive temper temperatur ature e  60°C.

c. It is suggested suggested the usage usage of ferrules ferrules with insulati insulating ng collar collar (according (according to DIN 46228-4) 46228-4) with cross section of 1.5 sq.mm.

7 .5

OPTICAL CONNECTORS

In case of usage of optical connectors, please use the optical plug-in modules supplied by SIAE. Ask SIAE Microelettronica for different modules. SFP modules are sensitive to electrostatic discharge, take all the necessary precautions before their handling.

7 .5 .1

SFP module installation

Insertion:

101

•

extract extract black plastic plastic protect protection ion cap from from the receptacl receptacle e that is going going to receive the module module

•

position position the the module module locking locking tab notches towards towards the bottom bottom side side of the receptacle receptacle

•

push the the module module in in up to to complete complete insertion insertion (a click can be heard).

MN.00329.E - 012

7.5.2

SFP module removal

Removal: •

•

SFP provided by built in extraction lever: -

operate on the extraction lever unlocking the module from its receptacle and pull it out using the lever itself

-

after complete removal insert black plastic protection cap to close SFP receptacle on the IDU

SFP without built in extraction lever: -

use the extraction tool provided together with the module. This extraction tool depends on module brand and vendor: see the relevant instructions

-

after the complete removal insert black plastic protection cap to close the SFP receptacle on the IDU.

MN.00329.E - 012

102

7.5.3

SFP module for AGS-20

Note: due to the fact that the validated SFP modules list is always under revision, please refer to SIAE for

the last updated list with the related part number. Tab.31

Standard

Note

Max length

1000BaseLx

Laser FP singlemode 1310nm

10 km

1000BaseLx

Laser FP multimode 850nm

550 m

2.5Gb

Laser VCSE multimode 850nm

250 m

1000Base-BX a

SFP single fiber 10KM Tx-1310NM RX-1490NM

10 km

1000Base-BX


10 km

1000Base-BX


40 km

1000Base-BX


40 km

2.5 Gb

Laser singlemode 1310 nm

10GBase-LR

10GBASE-LR 1310 nm

10 km

10GBase-SR

10GBASE-SR 850 nm

400 m

1000BaseT

IEEE 802.3ab 1000BASE-T SyncE compliant and transparent for the IEEE 1588v2 protocol

100 m

a. BiDi SFP transceiver has only one optical port which uses an integrated WDM coupler to transmit and receive signals over a single strand fiber.

Since BiDi SFP transmits and receives signals with different wavelengths, we should connect the two BiDi SFPs which have the opposite wavelength together. For example, we use a 1310nm-Tx/1490nm-Rx BiDi SFP at one end, then we must use a 14 90nm-Tx/1310nm-Rx BiDi SFP on the other en d (shown in following figure)

103

MN.00329.E - 012

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.

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.

MN.00329.E - 012

104

7 .7 .5

IF cables in XPIC radio link

In a XPIC link, the difference between IF cable length of V polarization and IF cable length of H polarization must be compliant with: •

in case case of BW = 14 14 MHz MHz 12 m

•

in cas case e of of BW BW = 28 MHz MHz 6 m

•

in case case of BW = 56 56 MHz MHz 3 m. m.

7 .8

GROUNDING CONNECTION

Fig.71 and Fig.71 and annexed legend show how to perform the grounding connections. Indoor

3

4

3

4

ODU unit 1

5

IDU unit

7

(+) (-)

2

6

Station ground

Local ground

ground rack

Legend 1. IDU grounding grounding point, point, copper faston faston type. The cross section section area of the cable used must be  4 sq.mm. The Faston is available on the IDU both sides. 2. ODU grounding grounding M6 bolt bolt copper faston faston type. The cross cross section area area of the cable used must must be  16 sq.mm (V60052) 3. IDU–ODU IDU–ODU interconnection interconnection cable cable type Celflex Celflex CUH 1/4” or RG8 cable terminated terminated with N–type N–type male connectors at both sides. 4. Grounding Grounding kit type type Cabel Metal or similar similar to connect connect the shield of interconne interconnection ction cable. cable. 5. Matching Matching cable (tail) (tail) terminated terminated with with SMA male and N female female connectors. connectors. 6. Battery groundi grounding ng point of of IDU to be connected connected to earth earth by means of a cable with with a section area area 2.5 sq.mm. Length  10 m. 7. Grounding Grounding cords connected connected to a real earth internal internal of station. station. The cross section section area of the cable must be  16 sq.mm Fig.71 - Grounding connection

105

MN.00329.E - 012

7.9 7. 9

IDU ID U-O -ODU DU CA CABL BLE E GRO GROU UND NDIN ING G KIT KIT INS INSTA TALL LLAT ATIO ION N

7.9. 7. 9.1 1

Grou Gr ound ndin ing g kit kit K0 K092 9283 83F F (fo (for r RG RG8 or or 1/8 1/8” ” cab cable le) )

The kit is made up by: •

grounding kit

•

seal sealant ant (in (in a smal smalll sach sachet et))

•

a short tape (to define the part part of the the jacket jacket to remove remove from the the cable) cable)

•

a transparent transparent plastic plastic bag, bag, with instructi instructions ons printed printed over, over, which contains contains all all the items. 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 order: •

self amalgamating amalgamating waterproof waterproof tape against water and moisture moisture

•

black black PVC tape tape aga again inst st sun UV

Procedure for both tapes: •

apply the first first (of two) two) layer of of sealing sealing tape overlap overlapping ping the the IDU-ODU IDU-ODU cable jacket 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 eve ry wrap wrappin ping g must must over overlap lap the pre previo vious. us.

The grounding bolt (opposite to the grounding clamp of the kit) must remain without sealing.

7.9. 7. 9.2 2

Grou Gr ound ndin ing g ki kitt IC ICD0 D000 0072 72F F (f (for or an any y ca cabl ble e wi with th sh shie ield ld) )

Fig.72

The kit is made up by: •

a copper copper plat plate e connecte connected d to a M8x20 M8x20 groundi grounding ng bolt bolt

MN.00329.E - 012

106

•

50 cm cm of tin copper copper tube of 3mm 3mm of of diame diameter ter

•

30 cm of viny vinyll mastic mastic self self amalgam amalgamati ating ng waterp waterproo rooff tape

•

2 m of of black black PVC tape tape aga again inst st sun sun UV. 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 remove 52mm of jacket jacket from from the cable cable that has has to be grounded grounded 2. insert one end of the tin tin copper tube of 3 mm of diameter diameter in the relevant hole hole over the plate copper copper bar of the grounding kit 3. the grou groundi nding ng kit kit must must be placed placed as as Fig.73 Fig.73 (the (the plate copper bar must be higher point of the grounding kit) 4. put the plate plate copper bar bar over the shield shield of the cable and tie tie firmly the the plate to the cable 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 layers of vinyl mastic self amalgamatin amalgamating g waterproof waterproof tape overlapping overlapping the IDU-ODU IDU-ODU cable jacket by 3cm on each ends a s in Fig.73 Fig.73.. Every wrapping must overlap the previous. 6. Apply two two layers of black black PVC UV proof tape overlapping overlapping the waterpro waterproof of tape layers layers as in Fig.73 Fig.73.. Every wrapping must overlap the previous. 7. Insert the grounding grounding bolt bolt in the closest groundi grounding ng point. point. The grounding bolt (opposite to the grounding clamp of the kit) must remain without sealing.

Fig.73 - Grounding kit positioning

107

MN.00329.E - 012

7.10 7. 10

SURG SU RGE E AND AND LIG LIGHT HTNI NING NG PR PROT OTEC ECTI TION ON

General recommendations: EN 301 489.

Telecommunications interfaces for indoor connections Reference specifications: EN61000-4-5 (cl.2).

Telecommunications Telecomm unications interfaces interfaces for full outdoor connections (LAN A, LAN B) Reference sp specifications: EN EN61000-4-5 (c (cl.5)

Shielded ca cables.

IF interfaces for IDU-ODU connections (ODU x) Reference sp specifications: EN EN61000-4-5 (c (cl.5)

Coaxial ca cables.

IF interfaces protection details (ODU x) Gas dischargers Technical Characteristics DC spark-over voltage

15 0 V + / - 2 0 %

Nominal impulse discharge current (8/20s)

20 kA

Single impulse discharge current (8/20s)

25 kA.

MN.00329.E - 012

108

8

CONNECTORS

The front panel of the AGS-20 depends on the selected version. Available versions are shown in para graph 5.11 AVAILABLE VERSIONS. VERSIONS.

8 .1

CONNECTORS

-

Optical XG LAN1 and LAN2

SFP+ 1Gbps or 10Gbps

-

Ethernet LAN1 and LAN2

COMBO (it can be electrical or optical)

-

Ethernet LAN3 and LAN4 electrical

RJ 4 5

-

Ethernet LAN5 and LAN6 SFP

SFP optical or electrical interface 1 Gbps, SFP optical interface 2.5 Gbps (proprietary)

-

Ethernet LANA and LANB

COMBO

-

Ethernet LANC and LAND SFP

SFP optical or electrical interface 1 Gbps, SFP optical interface 2.5 Gbps (proprietary)

-

Trib 1-8, 75 Ohm and 120 Ohm E1 in/out

50 pin SCSI female (Tab.33 Tab.33 for for 75 Ohm and Tab.34 Tab.34 per per 120 Ohm)

-

Trib 9-16, 75 Ohm and 120 Ohm E1 in/out

50 pin SCSI female (Tab.33 Tab.33 for for 75 Ohm and Tab.34 Tab.34 per per 120 Ohm)

E1, 75 Ohm and 120 Ohm interfaces are present in the same connector (with different pins).

-

Conne Connecto ctorr for 50 50 Ohm inte interco rconn nnect ectio ion n to ODUA and ODUB

SMA (max tightening torque=0.5 Nm)

-

-48 Vdc power supply

Green connector (pinout on the panel) P04184 6

-

LCT local management (Ethernet)

RJ45 (see Tab.32 Tab.32))

-

Synk-1 synchronization in/out


-

ToD Time of Day interface


-

Console


-

Alarm


ODU A

Trib. 1-8

ODUB

Trib. 9-16

LAN C

2

LCT

LAND URG NURG SW TEST

1PPS

R

1 2 1

LAN

2 1

LAN

4 3

LAN

6 5

SYNC TOD

Console ALARM

ON 48V „ª -+

M 5A

250V

Fig.74 - IDU AGS-20 front panel example for GAI0216

6

109

It is available available a security security lock lock Z21196 for single single connector connector and Z21197 for for double double connector connector..

MN.00329.E - 012

Tab.32 - 10/100/1000BaseT, RJ45

Function Pin RJ45

MN.00329.E - 012

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-

110

Tab.33 - 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

22

Tributary 2/10 input

45

Ground A

20


42

Ground A

17


43

Ground A

18


40

Ground A

15


39

Ground A

14


36

Ground B

11


37

Ground B

12


34

Ground B

9


33

Ground B

8


29

Ground B

4


31

Ground B

6


28

Ground B

3


26

Ground B

1


Note: Join pin 44 with ground A pins, join pin 32 with ground B pins. 25

.........................

1

.........................

50

26

Fig.75 - Pin-out Tributary 50 pin SCSI female

111

MN.00329.E - 012

Tab.34 - 8xE1, 50 pin SCSI female 120 Ohm)

MN.00329.E - 012

Pin

120 Ohm

49

Tributary 1/9 input

23

Tributary 1/9 input

44

Ground A

24


25


44

Ground A

21


22


44

Ground A

46


20


44

Ground A

16


17


44

Ground A

19


18


44

Ground A

41


15


44

Ground A

13


14


44

Ground A

10


11


32

Ground B

38


12


32

Ground B

35


9


32

Ground B

7


8


32

Ground B

112

Pin

120 Ohm

5


4


32

Ground B

30


6


32

Ground B

27


3


32

Ground B

2

Tributary 8/16output

1


32

Ground B 25

.........................

1

.........................

50

26

Fig.76 - Pin-out Tributary 50 pin SCSI female

Tab.35 - 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.36 - ToD interface pinout

RJ45 pin

Function

1 2 3 4

GND

5

GND

6

113

7

ToD_N

8

ToD_P

MN.00329.E - 012

Tab.37 - Console connector pinout

RJ45 pin

Function

1 2 3

TxD (Output)

4

GND

5

GND

6

RxD (Input)

7 8

Tab.38 - Alarm connector pinout

RJ45 pin

Function

1

Alarm User-In 0

2

Alarm User-In 1

3

GND

4 5

MN.00329.E - 012

6

Alarm User-Out: Relé-Com

7

Alarm User-Out: Relé-N.O.

8

Alarm User-Out: Relé N.C.

114

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

-

V32308


-

V32309


Differences regard the dimensions and the presence of the centring ring (see Fig.77): -

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 •

115



-


-

1+0 ODU support

-

hybrid and relevant screws

-

polarization twist disk and relevant screws

-

2 ODUs with O–rings and devices for ground connection.

MN.00329.E - 012

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 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 hybrid 6. installation of ODUs 7. antenna aiming 8. ODU grounding.

MN.00329.E - 012

116

9.5

9.5.1

1+0 MOUNTING PROCEDURES

Setting antenna polarization

Fig.77 – 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 according on: horizontal wave guide –> vertical polarization, vertical wave guide –> horizontal polarization. Screw again the four Allen screws (torque = 1 Nm).

9.5.2

Installation of the centring ring on the antenna

Fig.77 – 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.77 – 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.77 – 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.78 – Apply seal and lubricant grease Dow Corning 4 on the O–ring by protecting fingers with gloves. Fig.79 – 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 th e ODU to the Wave guide of the antenn a: 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.80) and reference tooth on the ODU body. Fig.81 – When alignment of the referen ces teeth is achieved, turn the ODU body clockwise until rotation is stopped. In figure are shown ODU final position for both polarizations. Fig.80 – When ODU positioning is over, secure ODU body on the support by tightening bolts (use 13mm spanner, torque = 6Nm).

117

MN.00329.E - 012

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.82 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 sh own in Fig.82 with a 13 mm spanner, only after ha ving 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: •

M6 screw with washer

as shown in Fig.83.

9.6


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.84 – 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 position 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.85. Tighten progressively and alternatively the screws and the spring washer with following torque: Tab.39 - 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.86 – 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 - 012

118

9.6.2

Installation of ODUs (on hybrid for 1+1 version)

For both ODUs. Fig.78 – Apply seal and lubricant grease Dow Corning 4 to the O–ring by protecting fingers with gloves. Fig.79 – Bring the ODU with the two hands and position the ODU handle at the bottom side. The handle can assume the positions shown in the figure depending on the polarization. Position the ODU body near the support and align the wave guide of the ODU to the wave guide of the hybrid: respect to the position of wave guide alignment, turn the ODU body approx. 30° counter–clockwise and then insert the ODU body into the support. For 1+1 system the handle of the ODU is always positioned on the right. The polarization twist disk on the hybrid matches the antenna polarization. Fig.87 – When alignment of the reference teeth is achieved, turn the ODU body clockwise unt il the rotation stops. In figure are shown ODUs final position. Fig.80 – 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 (not present in V32309)

Antenna

1+0 support Two bushes

Fig.77 - 1+0 pole mounting

119

MN.00329.E - 012

Reference tooth O-ring ODU wave guide

"N" "BNC"

Coupling torque for the grounding bolt is 9.5 Nm

Ground bolt

Fig.78 - ODU body reference tooth

Vertical

Horizontal

Fig.79 - 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.

MN.00329.E - 012

120

3 1 2

1 5 4

4 1 5

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.80 - 1+0 support

121

MN.00329.E - 012

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

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

Fig.81 - ODU housing final position for both polarization

MN.00329.E - 012

122

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.82 - 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.83 - ODU grounding

123

MN.00329.E - 012

7 8 1 2 4

6

5

3

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.84 - Hybrid and twist disk

MN.00329.E - 012

124

Horizontal polarization

Vertical polarization

Fig.85 - Polarization disk fixing (only for 13 GHz and 15 GHz)

125

MN.00329.E - 012

Fig.86 - Hybrid installation

ASN/ASNK version

Fig.87 - 1+1 ODUs installation

MN.00329.E - 012

126

10

INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED DUAL POLARIZATION ANTENNA

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 suppliers. Depending on supplier and antenna dimension the final assembled structure can vary. An example in Fig.88. The installation of ASN 7 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.89)

•

2 standard lock ODUs with O-rings and accessories for ground connection and with standard lock flange.

10.3

7

127

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.89)

•

2 fast lock 1+0 ODU support

•

2 Fast lock ODUs with O-rings and accessories for ground connection and with fastlock flange


MN.00329.E - 012

10.4


•

1x 2.5 mm Allen wrench

•

1x 3 mm Allen wrench

•

1x 6 mm Allen wrench

•

1x 13 mm spanner

•

2x 17 mm spanner



10.5


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 - 012

128

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.89). •

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 centring 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 squ are head out of the hole of about 13-14mm (the thickness 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.

129

MN.00329.E - 012

10.6.4

Antenna aiming

For horizontal and vertical aiming see the instructions included in the antenna box (instructions vary depending 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.83.

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.89). •

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 centring ring.

10.7.2

Installation of the fast lock 1+0 ODU support

See Fig.90. The orientation of the ODU su pport is the one that allows the moun ting 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.90). 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.90). 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 - 012

130

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 Oring 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.90, 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 th e support by tightening bolts (3 in Fig.90). Use 13mm spanner, torque = 6Nm.

Repeat this procedure for the second ODU on the opposite side of the OMT.

10.7.5

Antenna aiming

For horizontal and vertical aiming see the instructions included in the antenna box (instructions vary depending 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.7.6

ODU grounding



as shown in Fig.83.

Dual pol. antenna

Pole support system OMT

OMT flange where ODU must be installed

OMT flange where ODU must be installed

Fig.88 - Assembled structure (DP antenna, OMT, mounting system)

131

MN.00329.E - 012

1 Screws

Centering ring

Fig.89 - Centring ring

3 1 2

1 5 4

4 1 5

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.90 - Fast lock ODU support

MN.00329.E - 012

132

Standard coupling flange

Screws

O-ring

ODU ASN/ASNK

Eyelet terminal Grounding bolt Coupling torque for the grounding bolt is 9.5 Nm

Fig.91 - ODU ASN/ASNK Standard lock

133

MN.00329.E - 012

11

INSTALLATION ONTO THE POLE OF THE ODU 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 •

11.3



-


-

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 - 012

134

•


•

N.1 13 mm spanner

•

N.2 17 mm spanner.



11.4


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 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 hybrid 6. installation of ODUs 7. antenna aiming 8. ODU grounding.

11.5

11.5.1


Setting antenna polarization

Fig.77 – 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 according on: horizontal wave guide –> vertical polarization, vertical wave guide –> horizontal polarization. Screw again the four Allen screws (torque = 1 Nm).

135

MN.00329.E - 012

11.5.2

Installation of the centring ring on the antenna

Fig.77 – 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.77 – 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.77 – 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.78 – Apply seal and lubricant grease Dow Corning 4 on the O–ring by protecting fingers with gloves. Fig.79 – 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 th e ODU to the Wave guide of the antenn a: 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.80) and reference tooth on the ODU body. Fig.81 – When alignment of the referen ces teeth is achieved, turn the ODU body clockwise until rotation is stopped. In figure are shown ODU final position for both polarizations. Fig.80 – When ODU positioning is over, secure ODU body on the support by tightening bolts (use 13mm spanner, torque = 6Nm).

11.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.82 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 sh own in Fig.82 with a 13 mm spanner, only after ha ving 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 - 012

136

11.5.7

ODU grounding



as shown in Fig.83.

11.6


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.84 – 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 position 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.85. Tighten progressively and alternatively the screws and the spring washer with following torque: Tab.40 - 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.86 – 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.78 – Apply seal and lubricant grease Dow Corning 4 to the O–ring by protecting fingers with gloves. Fig.79 – Bring the ODU with the two hands and position the ODU handle at the bottom side. The handle can assume the positions shown in the figure depending on the polarization. Position the ODU body near the support and align the wave guide of the ODU to the wave guide of the hybrid: respect to the position of wave guide alignment, turn the ODU body approx. 30° counter–clockwise and then insert the ODU body into the support. For 1+1 system the handle of the ODU is always positioned on the right. The polarization twist disk on the hybrid matches the antenna polarization. Fig.87 – When alignment of the reference teeth is achieved, turn the ODU body clockwise unt il the rotation stops. In figure are shown ODUs final position.

137

MN.00329.E - 012

Fig.80 – 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.

Centering ring

Three 3 mm Allen screws Four 13mm screws

Antenna

1+0 support

Fig.92 - 1+0 pole mounting

MN.00329.E - 012

138

Reference tooth O-ring ODU wave guide

"N" "BNC"


Ground bolt

Fig.93 - ODU body reference tooth

Vertical

Horizontal

Fig.94 - 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.

139

MN.00329.E - 012

2 1

1 4 3

3 1 4

1

2

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.95 - 1+0 support

MN.00329.E - 012

140

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

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

Fig.96 - ODU housing final position for both polarization

141

MN.00329.E - 012

Pole support Vertical aiming 2

1 Horizontal aiming

Fig.97 - Antenna aiming

MN.00329.E - 012

142

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.98 - ODU grounding

143

MN.00329.E - 012

7 8 1 2 4

6

5

3

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.99 - Hybrid and twist disk

MN.00329.E - 012

144

Horizontal polarization

Vertical polarization

Fig.100 - Polarization disk fixing (only for 13 GHz and 15 GHz)

145

MN.00329.E - 012

Fig.101 - Hybrid installation

MN.00329.E - 012

146

ASN/ASNK version

Fig.102 - 1+1 ODUs installation

147

MN.00329.E - 012

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 tw o different coupling kits in order to obtain a Fast Lock ASN/ASNK or a S tandard 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.103 - 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.104 - 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 - 012

148

12.2

INSTALLATION ONTO THE POLE OF THE ODU WITH INTEGRATED 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.107)

•

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 requested polarization. After the antenna is installed onto the pole, the ODU must be installed, see Fig.105. •

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 w orn 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-1 4mm (the thickness of hook (4) , use 15mm spanner)

•

Apply seal and lubricant grease Dow Corning 4 to the O-ring, protecting fingers with gloves, and insert in the proper track on the ODU flange

•

Position the ODU (5) vertically near the four bolts on the antenna flange and align the ODU to match the polarization of the antenna feeder: -

149

vertical polarization: the handle (6) of the ODU is at the bottom left corner

MN.00329.E - 012

-

horizontal horizontal polari polarizatio zation: n: the handle handle (6) of the ODU is is at the bottom bottom right right corner corner

•

After the the right position position has been been found, found, rotate 30° counter counter clockwise clockwise the the ODU and approach approach the ODU to the antenna flange in order to have the four slots of the Standard Lock cross between the four bolts

•

Rotate Rotate 30° clockwise clockwise the ODU to to hook hook each slots on the relevant relevant bolt bolt

•

When each each slot is firmly firmly hooked on the relevant relevant bolt, tighten tighten each bolt bolt (use 15mm 15mm spanner, spanner, torque=46mm)

•

Optional: Optional: sun cover cover kit - Insert Insert the sun sun cover and tie one of of its bottom bottom holes holes to the ODU ODU handle handle by means of the black plastic strip included in the sun cover kit

•

The ODU ODU is ready ready to be connected connected to the IDU-ODU IDU-ODU cable and and to the the grounding grounding cable. cable.

12.2.2.2

1+1 ODU

Install The antenna using the antenna insta llation guide (specific for each antenna) inside the antenna box by antenna producer. Keep attention to the polarization of the an tenna feeder depending on requested polarization. After the antenna is installed onto the pole, follow the procedure below, see Fig.106 Fig.106.. Mounting the hybrid (3) on the back of the antenna: •

Position Position the three three holes holes circular circular flange flange (1) on the antenna antenna flange flange and align align the holes holes on the the circular circular flange with the relevant holes on the antenna flange

•

Insert and tighten tighten the the three three 3mm M4 M4 Allen screws (2) using a 3mm Allen Allen wrench wrench (torque (torque = 2mm) 2mm)

•

Prepar Prepare e the the polari polarizat zation ion disk disk (see Fig.107 Fig.107)) with the two O-rings: seal and lubricant grease Dow Corning 4 must be applied to the O-ring, protecting fingers with gloves; each O-ring must be inserted in the proper track on each surface of the disk

•

Mount always always (with vertical vertical and with with horizontal horizontal polarizat polarization) ion) the polarizati polarization on disk on the hybrid hybrid flange (antenna side) as shown in Fig.107 Fig.107 and and tighten the four screws (only three screws in 13 GHz and 15 GHz hybrid). The polarization disk mus t br oriented depending on requested polarization by antenna feeder (position V or H as shown in Fig.107 Fig.107.. Torque values as in Tab.41 Tab.41.. Tab.41 - 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

1 Nm

Mount the hybrid hybrid on on the back back of the the antenna antenna by means means of four four M10 bolts (4) (torque (torque = 46 Nm)

Mounting each ODU on the hybrid: •

Add lubricant lubricant paste, paste, e.g. e.g. MOLYKOTE MOLYKOTE P-40, on on threads threads of four 25mm 25mm bolts bolts (3). The sliding 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 w orn where repeated or prolonged contact can occur.

•

Screw partially partially four M10 bolts bolts (4) (4) on the hybrid hybrid flange flange (ODU (ODU side): each each bolt should be be tightened tightened to have the square head out of the hole of about 13-14 mm, use 15 mm spanner

•

Apply seal and lubrican lubricantt grease Dow Corning Corning 4 to the the O-ring, O-ring, protecting protecting fingers fingers with gloves, gloves, and insert in the proper track on the ODU flange

•

Position Position the ODU ODU (5) vertically vertically near the four bolts bolts on the the antenna flange flange and and align align the ODU ODU to match the polarization of the antenna feeder: horizontal polarization must be used, the handle (6) of the ODU is at the bottom right corner

•

After the the right position position has been been found, found, rotate 30° counter counter clockwise clockwise the the ODU and approach approach the ODU to the antenna flange in order to have the four slots (7) of the Standard Lock cross between the four bolts on the hybrid

MN.00329.E - 012

150

•


•

When each slot slot is firmly firmly hooked hooked on the relevant relevant bolt, bolt, tighten tighten each bolt bolt (use 15 mm mm spanner, spanner, torque torque = 46Nm)

•

Optional: Optional: sun cover cover kit - Insert Insert the sun sun cover and tie one of of its bottom bottom holes holes to the ODU ODU handle handle by means of the black plastic strip included in the sun cover kit

•

Now the ODU is ready to be connecte connected d to the the IDU-ODU IDU-ODU cable cable and to the grounding grounding cable

•

Repeat Repeat for the other other ODU ODU on on the the other other side side

•

Optional: Optional: sun cover cover kit. Insert Insert the sun cover cover and tie tie one of its bottom bottom holes holes to the the ODU handle handle by means of the black plastic strip included in the sun cover kit

•

Now the ODU is ready to be connecte connected d to the the IDU-ODU IDU-ODU cable cable and to the grounding grounding cable.

12.3 12. 3

•

INSTALLATI INSTALL ATION ON ONT ONTO O THE THE POL POLE E OF OF THE THE ODU WIT WITH H SEPA SEPARAT RAT-ED ANTENNA

Diameter of the pole

12.3.1

60-114 mm

ODU ASN/ASNK (F (Fast Loc ock k)

The installation of ODUs with Fast Lock coupling kit is described in previous chapters.

12.3 12 .3.2 .2

ODU OD U ASN SN/A /ASN SNK K (S (Sta tand nda ard Lo Lock ck) )


Supporting Supporting plate, plate, fixing fixing bracket bracket with M10 130mm bolts (with washer, washer, spring spring and and nut)

•

1 antenna antenna side flange, variable variable as function function of RF frequency, frequency, with with relevant relevant screws screws

•

M10 M10 25mm 25mm bolt bolts s for for ODU ODU mou mounti nting ng

•

ODU with with O-ring O-ring and and devic devices es for for ground ground conne connectio ction n

Mounting kit 1+1 version

151

•

Supporting Supporting plate, plate, fixing fixing bracket bracket with M10 130mm bolts (with washer, washer, spring spring and and nut)

•

M10 25mm bolts bolts for for hybr hybrid id and and ODUs ODUs moun mountin ting g

•

Hybr Hybrid id me mech chan anic ical al bod body y

•

Pola Polari rizat zatio ion n twis twistt disk disk (see (see Fig.107 Fig.107))

•

2 ODUs ODUs with O-ri O-rings ngs and devi devices ces for for ground ground connec connectio tion. n.

MN.00329.E - 012

12.3.2.1

1+0 ODU

See Fig.108 Fig.108.. •

Position Position the supporting supporting plate (1) on on the pole and and fix the rear rear bracket (2) to it by means means of the four four 130 mm M10 bolt (3) with relevant washers, springs and nuts (use 15mm spanner, torque = 46Nm).

•

Fix the the antenna antenna side side flange flange (4) (4) with the the prope properr screws screws (in Fig.108 Fig.108 the the antenna flange is shown in two different positions depending on the polarization), the screw holes side is the side where the waveguide must be installed.

•

Add lubricant lubricant paste, paste, e.g. e.g. MOLYKOTE MOLYKOTE P-40, P-40, on threads threads of four four 25mm bolts bolts (3). The The sliding sliding surfaces 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 w orn where repeated or prolonged contact can occur.

•

On the supportin supporting g plate, on on the opposite opposite side side respect to the antenna flange flange just mounted, mounted, insert insert in holes (5) on the supporting plate the four 25mm M10 bolts (3): screw them partially, each bolt should be tightened to have the square head out of the hole of about 13-14 mm (the thickness of hook (4), use 15mm spanner).

•

Apply seal and lubrican lubricantt grease Dow Corning Corning 4 to the the O-ring, O-ring, protecting protecting fingers fingers with gloves, gloves, and insert it in the proper track on the ODU flange.

•

Position Position the ODU vertical vertically ly near the four four bolts bolts on the supporting supporting plate plate and align align the ODU ODU to match the polarization of the antenna flange: -

vertical vertical polariz polarization: ation: the handle handle of of the ODU is is at the bottom bottom left left corner corner

-

horizontal horizontal polari polarizatio zation: n: the handle handle of the ODU ODU is at the bottom bottom right right corner

•

After the the right position position has been been found, found, rotate 30° counter counter clockwise clockwise the the ODU and and approach approach the ODU to the supporting plate in order to have the four slots of the Standard Lock cross between the four bolts

•


•

When each slot slot is firmly firmly hooked hooked on the the relevant relevant bolt, bolt, tighten tighten each bolt bolt (use 15 mm mm spanner, spanner, torque torque =46 Nm).

12.3.2.2

1+1 ODU

See Fig.109 Fig.109.. •

Position Position the supporting supporting plate (1) on on the pole and and fix the rear rear bracket (2) to it by means means of the four four 130 mm M10 bolt (3) with relevant washers, springs and nuts (use 15 mm spanner, torque = 46 Nm)

•

Mount the hybrid hybrid (4) (4) on the back of the antenna antenna by means means of four four 25 mm mm M10 bolts bolts (5) (use 15 mm spanner with torque = 46 Nm) in the holes (6).

Mounting each ODU on the hybrid: •

Add lubricant lubricant paste, paste, e.g. e.g. MOLYKOTE MOLYKOTE P-40, on on threads threads of four 25mm 25mm bolts bolts (3). The sliding 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 w orn where repeated or prolonged contact can occur.

•

Screw partiall partially y four 25 mm M10 bolts bolts positio positioning ning them in in the holes (7) (7) on the hybrid hybrid flange flange (ODU side): each bolt should be tightened to have the square head out of the hole of about 13-14 mm, use 15 mm spanner

•

Apply seal and lubrican lubricantt grease Dow Corning Corning 4 to the the O-ring, O-ring, protecting protecting fingers fingers with gloves, gloves, and insert in the proper track on the ODU flange

•

Position Position the ODU vertica vertically lly near the four bolts bolts on on the antenna flange flange and and align 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 the right position position has been found, rotate rotate 30° counter clockwi clockwise se the ODU and approach approach it to 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 - 012

152

153

•


•

When each slot slot is firmly firmly hooked hooked on the relevant relevant bolt, bolt, tighten tighten each bolt bolt (use 15 mm mm spanner, spanner, torque torque = 46 Nm)

•

Optional: Optional: sun cover cover kit - insert insert the sun cover cover and tie tie one of its bottom bottom holes holes to the ODU ODU handle by by means of the black plastic strip included in the sun cover kit

•

Now the ODU is ready to be connecte connected d to the the IDU-ODU IDU-ODU cable cable and to the grounding grounding cable

•

Repeat Repeat for the other other ODU ODU on on the the other other side side

MN.00329.E - 012

12.3 12 .3.2 .2.3 .3

Wave Wa vegu guid ide e tow towar ards ds th the e ant anten enna na

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 waveguide must must be fixed fixed to the the antenna flange flange on the the supporting supporting plate plate of the the ODU. In case of flexible waveguides, an excessive folding can damage the waveguide, see Tab.42 Tab.42 for for details.

•

1+1: the waveguid waveguide e must be fixed to to the hybrid. hybrid. In case case of flexible flexible waveguides, waveguides, an excessive excessive foldin folding g can damage the waveguide, see Tab.42 Tab.42 for for details.

Coupling torque for the grounding bolt is 9.5 Nm. Tab.42 - Waveguide bending radius according to frequency

Frequency

Bending radius with- Bending radius with- Bending radius with Bending radius with out rebending out rebending rebending rebending 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 low

200 (7,9)

500 (19,8)

3 0 0 ( 11 , 9 )

600 (23,7)

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.

Bend Bendiing E-p E-pla lane ne

Rmin/E Bending E-plane (short side of the section) b.

Bend Bendin ing g H-pl H-plan ane e

Rmin/H Bending H-plane (long side of the section)

MN.00329.E - 012

154

Fast lock coupling flange

Screws

O-ring

ODU ASN/ASNK

Eyelet terminal


Grounding bolt Fig.103 - ODU ASN/ASNK with fast lock coupling flange

155

MN.00329.E - 012

Standard coupling flange

Screws

O-ring

ODU ASN/ASNK

Eyelet terminal Grounding bolt Coupling torque for the grounding bolt is 9.5 Nm

Fig.104 - ODU ASN/ASNK with standard coupling flange

MN.00329.E - 012

156

5

) m N 6 4 e u q r o T ( 3

0 1 M

4

1

) m N 2 e u q r o T ( 2

Fig.105 - 1+0 ODU installation

157

MN.00329.E - 012

4

5

7

3

4

6

1

2

5

Fig.106 - 1+1 ODU installation

MN.00329.E - 012

158

Fig.107 - Polarization disk

114-60 3

1

2

4

5

4

Fig.108 - 1+0 antenna flange

159

MN.00329.E - 012

7

4

3

1

5

2 6

Fig.109 - 1+1 antenna flange

MN.00329.E - 012

160

13

INSTALLATION OF THE FULL ODU

Warning: use only shielded Ethernet cables for AGS-20 and FO interconnection.

For the Full ODU installation, see relevant manual depending on Full ODU version.

161

MN.00329.E - 012

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 a re roughly described here. For further details please refer to software manual.

MN.00329.E - 012

162

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 oc cur 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. type in the search bar the proper AGS-20 IP address (see paragraph 14.4 CONNECTION TO EQUIPMENT) 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.

163

MN.00329.E - 012

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 connection 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 - 012

164

•

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

Warning: before starting the BW & MOD/Link ID configuration enter in Equipment ->General Preset and

Disable the synchronization setup protocol (SSP) to avoid the rescue alarm and condition. At the end of the line up procedure, then it is suggested to enable the SSP. Further details on SSP protocol are available in the AG20 WebLCT Software manual - code: MN. 00327E.

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

165

MN.00329.E - 012

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

•

Automatic

or

-

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)

Press Apply and Confirm.

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

Press Apply and Confirm.

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 - 012

166

-

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

Warning: Required ASN software version: N00054-03 (maximum modulation form supported 256QAM).

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.110. The received field level has a tolerance of ±4 dB in the full temperature range.

V

3 2,625 2,25 1,875 1,5 1,125 0,75

dBm

0 -100

-80

-70

-60

-50

-40

-30

-20

Fig.110 - Detected voltage versus RF received signal

167

MN.00329.E - 012

14.7.2

Full ODU

For the Full ODU antenna aiming, see relevant manual depending on Full ODU version.

MN.00329.E - 012

168

169

MN.00329.E - 012

Section 5. MAINTENANCE

15

ALARMS

In this document a description of alarms is present in order to help operators to perform equipment troubleshooting.

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 - 012

170

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.43. In the following you can find a class list and the item they described:

171

•

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

MN.00329.E - 012

Tab.43 - Alarm severity list

Class

Common

E1 Path Protection

ETH LAN

IDU

MN.00329.E - 012

WebLCT Name

Description

Default Severity

equipManualOperation

Equip Manual Operation

Warning

pwTdmChannelLocalTdmDownAlarm

PWE3: Local TDM Down Channel

Major

pwTdmChannelLocalPsnDownAlarm

PWE3: Local PSN Down Channel

Major

pwTdmChannelRemoteTdmDownAlarm

PWE3: Remote TDM Down Channel

Warning

pwTdmChannelRemotePsnDownAlarm

PWE3: Remote PSN Down Channel

Warning

sdCardAlarm

SD Card Alarm

Warning

rdEncryptMismatchAlarm

Radio Encryption Mismatch Alarm

Minor

e1AISAlarm

E1 AIS Alarm

Warning

e1BERAlarm

E1 BER Alarm

Major

e1BERAlarm

E1 Out of Frame Alarm

Major

e1BERAlarm

E1 Out of Multiframe Alarm

Major

ifextLosAlarm

Ethernet Loss of Signal Alarm

Major

radioModulatorFailAlarm

Modulator Fail Alarm

Major

radioDemodulatorFailAlarm

Demodulator Fail Alarm

Major

radioRemDemodulatorFailAlarm

Remote Demodulator Fail Alarm

Major

radioCableOpenAlarm

IDU-ODU Cable Open Alarm

Major

radioCableShortAlarm

IDU-ODU Cable Short Alarm

Major

ppiLosAlarm

E1 signal loss Alarm

Major

ppiRxAisAlarm

E1 AIS Alarm

Warning

ppiE1SyncAlarm

E1 synchronisation Alarm

Warning

ppiPrbsFailAlarm

PRBS Fail Alarm

Warning

llfAlarm

Link Loss Forwarding Alarm

Major

poeZeroCurrentAlarm

POE Zero Current Alarm

Major

poeOverCurrentAlarm

POE Over Current Alarm

Major

pwrSupplyAlarm

Power Supply Alarm

Major

172

Class

WebLCT Name

Description

Default Severity

defErrorCcmAlarm

Error CCM Alarm

Major

defMacStatusAlarm

MAC Status Alarm

Major

defRdiCcmAlarm

RDI Alarm

Warning

defRemoteCcmAlarm

Remote CCM Alarm

Major

defXconCcmAlarm

Xconn CCM Alarma

Major

defRdiConditionAlarm

RDI Condition Alarm

Warning

deflossOfContinuityAlarm

Loss of continuity Alarm

Major

defUnexpectedPeriodAlarm

Unexpected period Alarm

Major

defUnexpectedMepAlarm

Unexpected MEP Alarm

Major

defMisMergeAlarm

Mismerge Alarm

Major

defUnexpectedMegAlarm

Unexpected MEG Alarm

Major

defAisConditionAlarm

AIS Condition Alarm

Major

acmsTpProfile15mAlarm

threshold cross Alarm

Major

acmsTpProfile24HAlarm

threshold cross Alarm

Major

pmG828-15MEsAlarm

15M counter ES threshold cross Alarm

Major

pmG828-15MSepAlarm

15M counter SEP threshold cross Alarm

Major

pmG828-15MSesAlarm

15M counter SES threshold cross Alarm

Major

pmG828-24HEsAlarm

24H counter ES threshold cross Alarm

Major

pmG828-24HSepAlarm

24H counter SEP threshold cross Alarm

Major

pmG828-24HSesAlarm

24H counter SES threshold cross Alarm

Major

pmG828-UASAlarm

UAS Alarm

Major

pmRxPwr-15MRltsAlarm

15M counter Rlts1 threshold cross Alarm

Major

pmRxPwr-15MRlts2Alarm

15M counter Rlts2 threshold cross Alarm

Major

OAM

P.M. ACM

P.M.G.828

P.M. RX Power

173

MN.00329.E - 012

Class

P.M. STM-1 MST

P.M. STM-1 RST

WebLCT Name

Description

Default Severity

pmStm1-15MEsAlarm


Major

pmStm1-15MSesAlarm


Major

pmStm1-15MSepAlarm


Major

pmStm1-24HEsAlarm


Major

pmStm1-24HSesAlarm


Major

pmStm1-24HSepAlarm


Major

pmStm1-UASAlarm

UAS Alarm

Major

pmStm1-15MEsFEAlarm

15M counter ES-FE threshold cross Alarm

Major

pmStm1-15MSesFEAlarm

15M counter SES-FE threshold cross Alarm

Major

pmStm1-15MSepFEAlarm

15M counter SEP-FE threshold cross Alarm

Major

pmStm1-24HEsFEAlarm

24H counter ES-FE threshold cross Alarm

Major

pmStm1-24HSesFEAlarm

24H counter SES-FE threshold cross Alarm

Major

pmStm1-24HSepFEAlarm

24H counter SEP-FE threshold cross Alarm

Major

pmStm1-UASFEAlarm

UAS-FE Alarm

Major

pmStm1-UASBIDIAlarm

UASBIDI Alarm

Major

pmStm1-15MEsAlarm


Major

pmStm1-15MSesAlarm


Major

pmStm1-15MSepAlarm


Major

pmStm1-24HEsAlarm


Major

pmStm1-24HSesAlarm


Major

pmStm1-24HSepAlarm


Major

pmStm1-UASAlarm

UAS Alarm

Major

pmTxPwr-15MTltsAlarm

15M counter Tlts1 threshold cross Alarm

Major

pmTxPwr-24HTltsAlarm

24H counter Tlts1 threshold cross Alarm

Major

P.M. Tx Power

MN.00329.E - 012

174

Class

WebLCT Name

Description

Default Severity

pmVc-15MEsAlarm


Major

pmVc-15MSesAlarm


Major

pmVc-15MSepAlarm


Major

pmVc-24HEsAlarm


Major

pmVc-24HSesAlarm


Major

pmVc-24HSepAlarm


Major

pmVc-UASFEAlarm

UAS Alarm

Major

pmVc-15MEsFEAlarm

15M counter ES-FE threshold cross Alarm

Major

pmVc-15MSesFEAlarm

15M counter SES-FE threshold cross Alarm

Major

pmVc-15MSepFEAlarm

15M counter SEP-FE threshold cross Alarm

Major

pmVc-24HEsFEAlarm

24H counter ES-FE threshold cross Alarm

Major

pmVc-24HSesFEAlarm

24H counter SES-FE threshold cross Alarm

Major

pmVc-24HSepFEAlarm

24H counter SEP-FE threshold cross Alarm

Major

pmVc-UASFEAlarm

UAS-FE Alarm

Major

pmVc-UASBIDIAlarm

UASBIDI Alarm

Major

Plug-in module

plug-inModuleAlarm

Plug-in module Fail Alarm

Major

Queue Depth

qdProfileMismatchAlarm

Queue Depth Profile Mismatch Alarm

Warning

P.M. VC 12

175

MN.00329.E - 012

Class

Radio

WebLCT Name

Description

Default Severity

radioInvalidFrequencyAlarm

Invalid Frequency Alarm

Major

radioRxPowerLowAlarm

Rx Power Low Alarm

Major

radioTxPowerAlarm

Tx Power Alarm

Major

radioRtVcoFail

Vco Fail Alarm

Major

radioRxAGCAlarm

Rx AGC Alarm

Major

radioTxAGCAlarm

Tx AGC Alarm

Major

radioIduOduCommunicationAlarm

IDU ODU Communication Alarm

Major

radioOduIduCommunicationAlarm

ODU IDU Communication Alarm

Major

radioConfigMismatch

Configuration parameter Mismatch Alarm

Major

radioRxQualityLowAlarm

Radio Rx Quality Low Alarm

Major

radioRxQualityWarningAlarm

Radio Rx Quality Warning Alarm

Warning

linkLinkTelemetryFailAlarm

Telemetry Fail Alarm

Major

linkReducedCapacityAlarm

Adaptive Modulation Reduced Capacity Notification

Warning

linkIdAlarm

ID Alarm

Major

linkRadioEocAlarm

Radio EOC Alarm

Major

linkSetupMismatchAlarm

Setup Mismatch Alarm

Warning

linkRescueSetupAlarm

Rescue Modulation Setup Alarm

Major

linkXpicProcedureBlockAlarm

FMP: Xpic disable

Major

linkXpicRemTxOffAlarm

FMP: Tx Off Under Remote End Request

Major

linkNoMatchingRadiosAlarm

No Matching Radios Parameters

Major

linkTfcAlarmBER

Transmitter Switch on Remote Terminal

Minor

aggrL1FailAlarm

L1 Aggregation Port Fail Alarm

Major

aggrL1DegradeAlarm

L1 Aggregation Port Degrade Alarm

Major

aggrL1RealignmentAlarm

L1 Aggregation Port Realignment Alarm

Major

timingSynkDriftAlarm

BASE BAND Sets Drift Alarm

Major

timingSynkLossAlarm

BASE BAND Sets LTI Alarm

Major

timingGeneratorFreeRunningStatus

BASE BAND Sets Free Running Status

Warning

timingGeneratorHoldoverStatus

BASE BAND Sets Holdover Status

Warning

timingGeneratorT0FailAlarm

BASE BAND Sets T0 Fail Alarm

Major

timingGeneratorT4SquelchAlarm

BASE BAND Sets T4 Squelch Alarm

Major

SETS

MN.00329.E - 012

176

Class

STM-1

UNIT

VC12

VC4

177

WebLCT Name

Description

Default Severity

stm1LosAlarm

LOS Alarm

Major

stm1LofAlarm

LOF Alarm

Major

stm1RsTimAlarm

TIM Alarm

Warning

stm1MsAisAlarm

MS AIS Alarm

Warning

stm1MsExcAlarm

B2 Excessive BER Alarm

Warning

stm1MsDegAlarm

Signal Degrade Alarm

Warning

stm1MsRdiAlarm

MS RDI Alarm

Warning

unitFailAlarm

Unit Fail Alarm

Major

unitMissingAlarm

Unit Missing Alarm

Major

unitNotRespondingAlarm

Unit Not Responding Alarm

Major

unitHwMismatchAlarm

Unit Hw Mismatch Alarm

Major

unitSwMismatchAlarm

Unit Sw Mismatch Alarm

Major

tempSensorAlarmThreshold1

Temperature threshold 1 exceeded Alarm

Warning

tempSensorAlarmThreshold2

Temperature threshold 2 exceeded Alarm

Critical

lpvcTimAlarm

STM-1 - VC-12 - TIM Alarm

Major

lpvcUneqAlarm

STM-1 - VC-12 - Unequipped Alarm

Major

lpvcPlmAlarm

STM-1 - VC-12 - Signal Label Mismatch Alarm

Major

lpvcExcAlarm

STM-1 - VC-12 - Excessive BER Alarm

Major

lpvcDegAlarm

STM-1 - VC-12 - Signal Degrade Alarm

Minor

lpvcRdiAlarm

STM-1 - VC-12 - RDI Alarm

Warning

lpvcTuAisAlarm

STM-1 - VC-12 -TU Path AIS Alarm

Warning

lpvcTuLopAlarm

STM-1 - VC-12 - TU LOP Alarm

Major

hpvcTimAlarm

STM-1 TIM Alarm

Major

hpvcUneqAlarm

STM-1 Unequipped Alarm

Major

hpvcPlmAlarm

STM-1 Signal Label Mismatch Alarm

Major

hpvcExcAlarm

STM-1 B3 Excessive BER Alarm

Major

hpvcDegAlarm

STM-1 B3 Signal Degrade Alarm

Minor

hpvcRdiAlarm

STM-1 Hp-RDI Alarm

Warning

hpvcLomAlarm

STM-1 Loss Of Multiframe Alarm

Major

hpvcAuAisAlarm

STM-1 AU-4 AIS Alarm

Warning

hpvcAuLopAlarm

STM-1 AU-4 LOP Alarm

Major

MN.00329.E - 012

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 consis ts 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-2 0 software manual.

MN.00329.E - 012

178

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 during 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:

179

•

check value of Power Transmitter and Receiver

•

reading Current Alarms and Alarm History labels and trying to figure out which part of the equipment 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 - 012

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

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 phenomena) 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 normal and if problems persist (Rx level remain different from normal) the rea son must be searched in w rong antenna disalignment (probably caused by strong wind or snow/ice).

MN.00329.E - 012

180

16.3.3

Radio link affected by interference

Radio link affected by interference has quality problems in one direction only (possible alarms are Rx Qua lity 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 frequency, smaller the search radius). In any case interference c an be confirmed by a spectrum analyser through a m ulti-angle investigation performed at antenna side.

16.4

SOFTWARE MANUAL OPERATIONS & TESTS

AGS-20 give the possibility to perform several maintena nce tests to verify the correct equipment working.

Fig.112

For more detailed information related to Maintenance software command make reference to WEBLct Manual.

16.4.1

PRBS Menu

Warning: Command available only for equipment with TDM module 16xE1 or Nodal.

It is possible to enable for each E1 port a PRBS T X Injector and RX PRBS detector for TDM c ircuit continuity check without the necessity to use additional test instrument. It is possible to inject the following test pattern: •

fixed word (AIS)

•

2 ^ 15-1

•

2 ^ 23-1

The possible Test Results:

181

•

BER. Dynamically updated BER value during the measure

•

Errors. Number of errors detected from the start of the measure

•

Elapsed Time. Time (expressed in day/hours/minutes/seconds) range after the measure active

•

Fail Alarms (option). Number of times that the Fail Alarm activated from the start of the measure.

•

Fail Alarm (box). Status of the Fail Alarm. The color of the box represents the alarm status and severity:

MN.00329.E - 012

-

Red, Orange, Yellow, Light blue. Alarm activated coupled respectively with the Critical, Major, Minor, Warning severity.

-

Green. Alarm activated coupled with the Status severity level.

-

Grey. Alarm deactivated.

Fig.113 - PRBS

16.4.2

Radio Loop & Cmd Menu

Warning: Command available only for equipment with Radio module and with at least one Radio Link de-

fined.

16.4.2.1

IF LOOP & RF LOOP

Fig.114 - IF Loop & RF Loop

IF loop at modem level check the correct working of the local baseband and modem unit. •

IF Loop ETH SQUELCHED, loop back only the TDM traffic

•

IF Loop ETH NOT SQUELCHED, loop back TDM traffic and ETH traffic too.

RF Loop at ODU TX, RX level check the correct working of the complete Local IDU and ODU. Warning: RF Loop will perform a self check at fixed modulation format. TDM tra ffic & ETH traffic is not guar-

anteed to be the same as in the normal traffic condition – STM1 Bulk is not looped back.

MN.00329.E - 012

182

The activation of a loop activates the MAN. OP alarm. During the execution of the test, the Test Loop box shows the progression of the operation. The status of the test is pointed out by the Test Loop Result box: •

Grey box - wording None. Test to execute.

•

White box - wording Running. Test in progress.

•

Green box - wording Passed. Test executed correctly (ODU operating).

•

Red box - wording Fail. Test failed (ODU faulted).

•

Red box - wording Interrupted. Test interrupted by the system.

During the test execution, the real traffic connec ted to AGS-20 is not looped back; after the test res ult then the real traffic will be partially looped back according to the fixed modulation in use for this test. The duration of the test depends on MANOP setting.

Fig.115 - Radio Loop &Cmd

16.4.2.2

RT PSU

RT PSU, enable or disable the -48 volt into the IF cable. In order to disconnect the ODU from the cable or cable substitution, it should be necessary to set in OFF the RT PSU and then restore ON at the end of the maintenance operation. The RT PSU OFF condition duration, depend on MANOP setting.

16.4.2.3

TX Transmitter

This menu set the ODU TX off temporary, (according to MAN. OP s etting), or permanent OFF until the user restore manually the normal ON status. TX off is very useful to test possible interference problem in a radio link.

183

MN.00329.E - 012

16.4.2.4

Carrier Only

This menu set the IF at the output of the modulator as: •

ON, (normal condition) modulated

•

OFF, not modulated.

This test could be useful for lab testing or a ntenna panning in case of problem finding the radiation c entral lobe. The test duration depend on MAN.OP setting.

16.4.3

Manual Operation Menu

The Manual Operations command manages the available maintenance operations (MAN. OP); for the following test, see the related reference. •

Turn-off/turn-on the transmitter

see paragraph 16.4.2.1

•

Disable/enable the modulation of the RF carrier


•

Disable/enable the operation of the RT power supply


•

Activate/deactivate a radio loop or execute the RF Test


•

Activate/reset the PRBS measure

see paragraph 16.4.1

•

Deactivate the PRBS measure

see paragraph 16.4.1

•

Enable/disable the used E1 signal for the PRBS measure

see paragraph 16.4.1.

Other manual operations are available according to AGS-20 Hardware and software configuration: •

Disable temporarily/restore the XPIC function

(2+0 xpic, 2x(1+1HS/FD)xpic)

•

Force the management of the switching in reception

(1+1HS/FD)

•

Force the management of the switching in transmission

(1+1 HS)

•

Force the status of the T0 synchronization

•

Force the use of a synchronism source

•

Activate/deactivate the E1 loops

•

Force the use of a STM-1

•

Enable/disable the STM-1 loops (line side and internal side)

•

Ethernet Port line loopback.

(STM1 1+1MSP)

TDM interfaces, SDH and E1, give the possibility to activate line or internal loopback:

MN.00329.E - 012

184

L

I

STM1 configurator

1 to 2 STM1 SFP

MST 1 to 16 E1 SCSI L

I

1 to 2 NBUS Cross connection

PWE3 (Pseudo Wire)

Fig.116 - TDM Loopback

Ethernet interfaces provides only Line Loopback

LAN6 Gi-0/5 LAN5 Gi-0/4 LAN4 Gi-0/8 LAN2 Gi-0/10 Combo LAN1 Gi-0/9 Combo

1000BaseX/T or 2.5Gbps SFP LAN A (Gi-0/6) Combo

1000BaseX/T or 2.5Gbps SFP 10/100/1000BaseT 10/100/1000BaseT/1000BaseX 10/100/1000BaseT/1000BaseX

Switch Ethernet L2

LAN B (Gi-0/7) Combo

Management traffic:

LAN3 Gi-0/3 Mngt

10/100/1000BaseT

Fig.117 - ETH Loopback

16.5

16.5.1

XPIC FAULT MANAGEMENT PROCEDURE

Introduction

In a frequency re-used system with XPIC the behaviour of the equipment on a given polarization may be affected by faults occurred on hardware that manages the signals on the other polarization: an hardware failure could cause a wrong behaviour of the Cross Polar Canc eller. In order to manage the faults that may have consequences on the signals on both polarizations, a specific XPIC Fault Management Procedure (FMP) has been inserted in the AGS-20 Equipment Controller. Aim of FMP is to detect possible faults by means of IDU and ODU alarms analysis and, consequently, to activate appropriate actions in order to preserve the correct behaviour of the unaffected polarization.

185

MN.00329.E - 012

This document describes the AGS-20 XPIC Fault Management Procedure (FMP) implemented in the Equipment Controller. The XPIC FMP may be enabled or disabled by the operator, using the LCT or the remote NMS. The FMP procedure is not available in case of 1+1 XPIC configuration, (in this case the single fault is protected by the protection mechanism directly).

16.5.2

XPIC Fault Management Procedure (FMP) description

16.5.2.1

Preliminary Remarks

The XPIC Fault Management Procedure aims to detect actual equipment faults and to distinguish fault conditions from propagation consequences. When XPIC is used on a double polarized link, an hardware fault (on a receiver or on a transmitter) can prejudice the correct functioning of the XPIC: hardware faults can produce mutual interference and, consequently, without FMP intervention, also the bearer on the polarization not affected by faults could not work properly. Depending on the value of the parameters under observation, the FMP may force commands on equipment in both terminal in order to preserve the desired signal from interference and/or noise. The FMP usage is very useful for modulation levels higher than 256QAM f or which the antenna polarization decoupling (XPD) could be not enough in presence of mutual interference between bearers on opposite polarization, also in absence of bad propagation conditions. The Fault Management Procedure analyses equipment alarms sampling alarms each second. Different alarm observation periods are considered depending to the group of alarms considered during the analysis: at the end of each “alarm period evaluation”, the content of alarms can trigger FMP and relevant actions will be activated. FMP can have different intervention times depending on the events detected by the procedure. If hardware failures are detected unequivocally, the FMP can act quickly in order to minimize the link outage. In other cases, longer observation periods should be considered in order to activate FMP only when its usage is appropriate. Further details have been provided in the following sections.

16.5.2.2

Parameters considered by FMP

Different alarms are considered in order to detect events for which FMP must be activated. Four different group of events are taken into account with different FPM intervention times. In particular: a. RX ODU failure alarms, IDU-ODU cable alarms, demodulator failure alarms at local terminal equipment: FMP acts if relevant alarms are detected for 10 consecutive seconds b. TX ODU failure alarms, IDU-ODU cable alarms, demodulator failure alarms at remote terminal equipment: FMP acts if relevant alarms are detected for 15 consecutive seconds c. RX alarms or local terminal demodulator parameters that show a possible failure on the remote TX: FMP acts if relevant alarms are detected for 45 consecutive seconds d. Local demodulator unlock: FMP acts if two different events (demodulator preamble unlock and PRx level under a specified threshold) are detected for at least 120 seconds in a observation period of 180 seconds. All the above events are considered separately for both polarizations. Alarms belonging to previous group of events “a” and “b” report unequivocally a hardware failure: in the first case (a) a fault on the RX ODU, IDU-ODU ca ble or demodulator is locally detected, while in the second case (b) a fault on the TX ODU, IDUODU cable or demodulator is signalled by telemetry to the controller unit in the local terminal. For both cases, the Fault Management Procedure can act quic kly in order to minimize the outage of link.

MN.00329.E - 012

186

In other cases, the fault is detected by means of different link parameters. In order to minimize the probability of unjustified intervention of FMP, a longer observation period is considered by FMP. In particular, in order to detect a possible fault on the Remote TX (group of events “c”) in presence of a loss on the link telemetry (the link is down on both polarizations), three different conditions are checked: •

presence of a gap higher than 24 dB between Received power level (PRX) measured on each polarization

•

demodulator preamble unlock

•

absence of alarms belonging to group of events “a”.

If these three conditions are verified at the same time for at least 45 seconds, a remote TX fault is deduced and, consequently, the FMP can act. In absence of conditions belonging to group of events “a” and “c”, a local demodulator unlock could occur due to hardware faults. In order to exclude situations for which the demodulator unlock is due to propagation problems, the FMP acts only if at least one of the two PRX measured on both polarizations is higher than a predefined threshold (about 25dB higher than the BER 10^-6 Threshold for 4QAM modulation). In particular, the following table shows the PRX thresholds considered by FMP: Tab.44

Channel spacing (MHz)

PRX FMP threshold (dBm)

13.75 - 20

-60

27.5 - 40

-57

50 - 56

-54

If the above condition on PRX and a alarm of demodulator unlock are verified for at least 120 seconds in an observation period equal to 180 seconds, the FMP is triggered. In order to allow the equipment reach ing a stable condition after start-u p or after enabling FMP, a “stability timeout” has been defined: it is fixed at 40 seconds and it is not configurable. During this period the FMP is not active.

16.5.2.3

Commands and Alarms generated by FMP

After the proper intervention time associated to each group of alarms under analysis (see paragraph 16.5.2.2 Parameters considered by FMP), the XPIC Fault Management Procedure may force the following commands on the equipment in both terminals: •

Switch-off the remote transmitter on the polarization interested by the fault in order to eliminate a potential source of interference towards the receiver on the opposite polarization.

•

Local XPIC disable on the polarization not interested by the fault in order to prevent noise on the desired signal. In addition, FMP generates: -

an alarm on the local equipment with the indication of radio on which the XPIC functionality has been disabled

-

an alarm on the remote equipment with the indication of radio on which the Transmitter has been switched off

The alarms and the commands forced by the procedure can be removed only by an operator using the WEBLct, disabling and then enabling again the FMP. The operator can also disable the usage of FMP by means of WEBLct

16.5.2.4

FMP: IDU-ODU Cable Alarm

In this example we suppose to have a Cable Alarm detected in station A. Fig.118 and Fig.119 display the FMP action and Alarm status in station A e station B.

187

MN.00329.E - 012

ODU A Tx OFF

ODU A Cable Alarm

ODU B XPIC disable

Station A

ODU B XPIC disable

Station B

Fig.118 - Station A Status

MN.00329.E - 012

188

Fig.119 - Station B status

16.5.2.5

FMP: TX_Failure Alarm

In this case we suppose to have a Tx Block failure detected in station A that will caus e a ODU B XPIC disable in station B processed by FMP.

ODU A Tx Fail

ODU B XPIC disable

Station A

Station B

Fig.120 - FMP TX Failure Alarm

189

MN.00329.E - 012

16.5.2.6

FMP: RX_Failure/alarms, Demodulator unlock

In Fig.121 it is displayed an ODU A Rx Failure detected in station A; FMP will proceed with ODU B XPIC disable in station A and ODU A Tx OFF in station B.

ODU A Rx Failure ODU A Tx OFF

ODU B XPIC disable

Station A

Station B

Fig.121 - RX Failure/Alarms, Demodulator unlock

16.5.2.7

FMP Reset Procedure

When the fault is restored, in order to come back to the normal working condition, the user need to RESET FMP on both stations.

Fig.122 - FMP RESET Procedure

16.5.2.8

XPIC Manual Operation

For testing purposes, it is possible to disable the XPIC functionality or the FMP procedure:

MN.00329.E - 012

190

Fig.123 - XPIC Manual Operation

16.5.2.9

Interaction between other Maintenance command and XIPC FMP

In case of activation of other commands like TX Off, RTN PS OFF etc. etc. the XPIC function will be temporary disabled; please make reference to the related WEBLct manual for details.

16.6

MAN.OP. AND CONSEQUENTIAL ACTION FOR 1+1 XPIC HS/FD

16.6.1

Introduction

The possible Manual Operations expected in case of QUAD IF AGS-20 1+1XPIC HS/FD are: •

transmitter off

•

carrier only

•

RT PSU off

•

IF loop

•

RF loop

•

XPIC disable.

We take as reference the 2 XPIC clusters and 2 protected clusters reported in the Fig.124.

Protection Cluster 1

A

XPIC Cluster 1

H

H <-> H

H

B

B V

V

C Protection Cluster 2

A

D

V <-> V

C D

XPIC Cluster 2

Fig.124

191

MN.00329.E - 012

16.6.2

TX OFF

16.6.2.1

Hot Stand-by configuration: TX OFF

a. The TX switching is forced on XPIC cluster 1 or at least the second ODU of the protection cluster 2 is with TX alarmed or is missing; if we switch off the transmitter on ODU A, B,C or D we will have the following consequential action: TX-OFF (ODU-A): CASE-A TX-off

(1-A) (1-B) (2-A) (2-B)

TX-OFF (ODU-B): CASE-A

XPIC 1

XPIC 1

A B C

XPIC OFF B

D

XPIC OFF D

(1-A) (1-B)

(1-B)

C

(2-A)

(2-A)

B C

D

(2-B)

(2-B)

D

(1-A)

TX-off

XPIC OFF C

XPIC 2

XPIC 1

A

(2-A)

B C

(2-B)

D

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

A

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

TX-OFF (ODU-D): CASE-A

XPIC 1

(1-B)

A

XPIC 2

TX-OFF (ODU-C): CASE-A (1-A)

XPIC OFF A

A

A B

XPIC OFF B TX-off

XPIC OFF D

A B

(1-A)

(1-A)

A

(1-B)

(1-B)

C

(2-A)

(2-A)

B C

D

(2-B)

(2-B)

D

XPIC OFF A

XPIC OFF C TX-off

XPIC 2

XPIC 2

Tab.45

Local terminal MANOP

Remote terminal

Consequential action


Radio-1A (ODU-A)

1B Xpic Disable 2B Xpic Disable

Radio-2A (ODU-C)

1B Xpic Disable 2B Xpic Disable

Radio-1B (ODU-B)

1A Xpic Disable 2A Xpic Disable

Radio-2B (ODU-D)

1A Xpic Disable 2A Xpic Disable

b. No protection TX forced on XPIC cluster 1 and no ODU of protection cluster is with TX alarmed or is missing; if we switch off the transmitter on ODU A, B,C or D we will not have any XPIC consequential action:

TX-OFF (ODU-A): CASE-B TX-off

(1-A)

A

(2-A)

B C

(2-B)

D

(1-B)

TX-OFF (ODU-B): CASE-B

XPIC 1

XPIC 1

A B

(1-A) (1-B)

(1-B)

C

(2-A)

(2-A)

D

(2-B)

(2-B)

(1-A)

A

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

A

A

(1-A)

B C

B

(1-B)

C

(2-A)

D

(2-B)

A B C D

TX-off

XPIC 2

XPIC 2

TX-OFF (ODU-C): CASE-B

TX-OFF (ODU-D): CASE-B

XPIC 1

(1-A) (1-B) (2-A) (2-B)

A B C

TX-off

D XPIC 2

MN.00329.E - 012

XPIC 1

A B

(1-A)

(1-A)

(1-B)

(1-B)

C

(2-A)

(2-A)

D

(2-B)

(2-B)

D

TX-off XPIC 2

192

Tab.46


Remote terminal



Radio-1A (ODU-A) Radio-2A (ODU-C) Radio-1B (ODU-B) Radio-2B (ODU-D)

16.6.2.2

Frequency Diversity configuration: TX OFF

In this case, the two XPIC clusters are completely independent; if we switch off the transmitter on ODU A, B, C or D we will have the following consequential action: TX-OFF (ODU-A) TX-off

(1-A)

XPIC 1

XPIC 1

A

(2-A)

B C

(2-B)

D

(1-B)

TX-OFF (ODU-B)

XPIC OFF B

(1-A) (1-B)

(1-B)

C

(2-A)

(2-A)

B C

D

(2-B)

(2-B)

D

(1-A)

TX-off

XPIC 2

(2-A) (2-B)

XPIC 1

A B C

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

A

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

TX-OFF (ODU-D)

XPIC 1

(1-B)

A

XPIC 2

TX-OFF (ODU-C) (1-A)

XPIC OFF A

A

A B

TX-off

XPIC OFF D

D

A B

(1-A)

(1-A)

A

(1-B)

(1-B)

C

(2-A)

B C

D

(2-B)

(2-A) (2-B)

D

XPIC OFF C TX-off

XPIC 2

XPIC 2

Tab.47


16.6.3


Remote terminal Consequential action

Radio-1A (ODU-A)

1B Xpic Disable

Radio-2A (ODU-C)

2B Xpic Disable

Radio-1B (ODU-B)

1A Xpic Disable

Radio-2B (ODU-D)

2A Xpic Disable

Carrier Only

If we activate the Carrier only test, we will have the same consequential action desc ribed in chapter TX OFF

193

MN.00329.E - 012

16.6.4

RT PSU OFF

16.6.4.1

1+1 HOT STBY configuration: RT PSU OFF

a. The TX switching is forced on XPIC cluster 1 or at least the second ODU of the protection cluster is with TX alarmed or is missing; the RX protection system is in Auto. In this case we have the same consequential action seen in paragraph 16.6.2.1 Hot Stand-by configuration: TX OFF. b. No TX switching is forced on XPIC cluster 1 and no ODU of the protection cluster is with TX alarmed or is missing; RX switching is in AUTO. In this case no consequential action will be expected c. The TX switching is forced on XPIC cluster 1 or at least the second ODU of the protection cluster is with TX alarmed or is missing; the RX protection system is forced on the XPIC cluster where we apply for the RT PSU OFF command. RT PSU-OFF (ODU-A): C ASE-RXA PSU-off

(1-A)

TX-off

A

(2-A)

B C

(2-B)

D

(1-B)

XPIC 1

RT PSU-OFF (ODU-B): CASE-RXA

XPIC OFF B TX-off

XPIC 1

A B

(1-A)

(1-A)

(1-B)

(1-B)

C

(2-A)

(2-A)

D

(2-B)

(2-B)

A XPIC OFF A B C

PSU-off

TX-off

TX-off

D

XPIC 2

XPIC 1

(1-B) (2-A) (2-B)

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

A

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

XPIC 2

RT PSU-OFF (ODU-C): CASE-RXA (1-A)

A

RT PSU-OFF (ODU-D): CASE-RXA TX-off

A B PSU-off C D

TX-off

XPIC OFF DXPIC 2

XPIC 1

A B

(1-A) (1-B)

(1-B)

C

(2-A)

(2-A)

D

(2-B)

(1-A)

(2-B)

A TX-off

B C XPIC OFF C D

PSU-off

TX-off XPIC 2

Tab.48

Local terminal

16.6.4.2

Remote terminal

MANOP



Radio-1A (ODU-A)

1B Xpic Disable

Radio-1A transmitter off Radio-2A transmitter off

Radio-2A (ODU-C)

2B Xpic Disable


Radio-1B (ODU-B)

1A Xpic Disable

Radio-1B transmitter off Radio-2B transmitter off

Radio-2B (ODU-D)

2A Xpic Disable


Configuration Frequency diversity: RT PS OFF

a. The RX is forced to the cluster XPIC of which the ODU is switched off or the other ODU protection cluster is missing or with RX alarmed.

MN.00329.E - 012

194

RT PSU-OFF (ODU-A): CASE-A (1-A) (1-B) (2-A) (2-B)

PSU-off

XPIC 1

RT PSU-OFF (ODU-B): CASE-A TX-off

A

XPIC OFF B

B XPIC OFF B C D

A B

(1-A)

(1-A)

(1-B)

(1-B)

C

(2-A)

(2-A)

D

(2-B)

(2-B)

XPIC 1

A XPIC OFF A B C

TX-off

D

XPIC 2

(1-B) (2-A) (2-B)

A

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

A

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

XPIC 2

RT PSU-OFF (ODU-C): CASE-A (1-A)

XPIC OFF A

PSU-off

RT PSU-OFF (ODU-D): CASE-A

XPIC 1

A B PSU-off C

TX-off

XPIC OFF D

XPIC OFF D

D

XPIC 1

A B

(1-A)

(1-A)

A

(1-B)

(1-B)

C

(2-A)

(2-A)

B C XPIC OFF C

(2-B)

(2-B)

D

D

XPIC OFF C

PSU-off

XPIC 2

TX-off XPIC 2

Tab.49

Local terminal

Remote terminal

MANOP



Radio-1A (ODU-A)

1B Xpic Disable

Radio-1A transmitter off 1B Xpic Disable

Radio-2A (ODU-C)

2B Xpic Disable

Radio-2A transmitter off 2B Xpic Disable

Radio-1B (ODU-B)

1A Xpic Disable

Radio-1B transmitter off 1A Xpic Disable

Radio-2B (ODU-D)

2A Xpic Disable

Radio-2B transmitter off 2A Xpic Disable

b. The RX is NOT forced to the cluster XPIC of which the ODU is switched off and the other ODU protection cluster is not missing or with RX alarmed.

RT PSU-OFF (ODU-A): CASE-B PSU-off

(1-A)

XPIC 1

XPIC 1

A

(2-A)

B C

(2-B)

D

(1-B)

RT PSU-OFF (ODU-B): CASE-B

XPIC OFF B

(1-A) (1-B)

(1-B)

C

(2-A)

(2-A)

B C

D

(2-B)

(2-B)

D

(1-A)

PSU-off

XPIC 2

(1-B)

B PSU-off C

(2-A) (2-B)

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

A

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

RT PSU-OFF (ODU-D): CASE-B

XPIC 1

A

A

XPIC 2

RT PSU-OFF (ODU-C): CASE-B (1-A)

XPIC OFF A

A

A B

XPIC 1

XPIC OFF D

D

A B

(1-A)

(1-A)

A

(1-B)

(1-B)

C

(2-A)

B C

D

(2-B)

(2-A) (2-B)

D

XPIC OFF C PSU-off

XPIC 2

XPIC 2

Tab.50


195



Radio-1A (ODU-A)

1B Xpic Disable

Radio-2A (ODU-C)

2B Xpic Disable

MN.00329.E - 012


Remote terminal



Radio-1B (ODU-B)

1A Xpic Disable

Radio-2B (ODU-D)

2A Xpic Disable

16.6.5

IF Loop

16.6.5.1

System Configuration Hot-STBY: IF loop

a. The RX is forced to the XPIC cluster where the IF Loop is NOT applied: IF loop (ODU-A): CASE-A XPIC OFF A IF loop

(1-A) (1-B) (2-A) (2-B)

IF loop (ODU-B): CASE-A

XPIC 1

XPIC 1

A B C

XPIC OFF B

D

A XPIC OFF A

A B

(1-A)

C D

(2-A)

(1-B) B XPIC OFF B (2-A) C

(2-B)

(2-B)

(1-B)

(1-A)

IF loop

D

XPIC 2

XPIC 1

A B

IF loop

(2-A) C XPIC OFF C (2-B) D XPIC OFF D

B

(1-B)

C

(2-A)

D

(2-B)

IF loop (ODU-D): CASE-A

XPIC 1

(1-B)

(1-A)

XPIC 2

IF loop (ODU-C) : CASE-A (1-A)

A

A B

(1-A)

(1-A)

A

A

(1-A)

(1-B)

(1-B)

(1-B)

C

(2-A)

B OFF C C XPIC IF loop

B

(2-A)

C

(2-A)

D

(2-B)

(2-B) D XPIC OFF D

D

(2-B)

XPIC 2

XPIC 2

Tab.51

Local terminal

MN.00329.E - 012

MANOP


Radio-1A (ODU-A)

1A Xpic Disable 1B Xpic Disable

Radio-2A (ODU-C)


Radio-1B (ODU-B)


Radio-2B (ODU-D)



196

b. The RX IS or IS NOT forced to the XPIC cluster where we apply the IF loop:

IF loop (ODU-A): CASE-B XPIC OFF A IF loop

(1-A) (1-B) (2-A) (2-B)

IF loop (ODU-B): CASE-B

XPIC 1

TX-off

A XPIC OFF B

B C

TX-off

D

XPIC 1

A B

(1-A)

(1-A)

(1-B)

(1-B)

C

(2-A)

D

(2-B)

(2-A) (2-B)

A XPIC OFF A IF loop

B C

TX-off

XPIC OFF B TX-off

D

XPIC 2

TX-off

A B C

IF loop

TX-off

(2-A) XPIC OFF C (2-B) D XPIC OFF D

B

(1-B)

C

(2-A)

D

(2-B)

A

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

A

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

IF loop (ODU-D): CASE-B

XPIC 1

(1-B)

(1-A)

XPIC 2

IF loop (ODU-C): CASE-B (1-A)

A

XPIC 1

A B

(1-A) (1-B)

(1-B)

C

(2-A)

(2-A)

D

(2-B)

XPIC 2

(1-A)

A TX-off


(2-B) D XPIC OFF D

TX-off

XPIC 2

Tab.52

Local terminal

16.6.5.2

Remote terminal

MANOP



Radio-1A (ODU-A)



Radio-2A (ODU-C)



Radio-1B (ODU-B)



Radio-2B (ODU-D)



System configuration Frequency Diversity: IF Loop

a. The RX is forced on the XPIC cluster where the IF Loop is NOT applied: IF loop (ODU-A): CASE-A XPIC OFF A IF loop

(1-A) (1-B) (2-A) (2-B)

XPIC 1

A B C

IF loop (ODU-B): CASE-A

XPIC OFF B

D

XPIC 1

A XPIC OFF A

A B

(1-A)

(1-A)

(1-B)

C

(2-A)


D

(2-B)

(2-B)

IF loop

D

XPIC 2

XPIC 2

IF loop (ODU-C) : CASE-A

IF loop (ODU-D): CASE-A

XPIC 1

(1-A) (1-B)

A B

IF loop


197

XPIC 2

XPIC 1

A B

(1-A)

(1-A)

A

A

(1-A)

(1-B)

(1-B)

(1-B)

C

(2-A)

C

(2-A)

D

(2-B)

B OFF C C XPIC IF loop D

B

(2-A)

(2-B) XPIC OFF D

D

(2-B)

XPIC 2

MN.00329.E - 012

Tab.53

Local terminal

Remote terminal

MANOP


Radio-1A (ODU-A)


Radio-2A (ODU-C)


Radio-1B (ODU-B)


Radio-2B (ODU-D)



b. The RX IS or IS NOT forced to the XPIC cluster where we apply the IF loop: IF loop (ODU-A): CASE-B XPIC OFF A IF loop

(1-A)

TX-off

A

(2-A)

B C

(2-B)

D

(1-B)

IF loop (ODU-B): CASE-B

XPIC 1

XPIC OFF B

XPIC 1

A XPIC OFF A

A B

(1-A)

C D

(2-A)


(2-B)

(2-B)

(1-B)

(1-A)

IF loop

TX-off

D

XPIC 2

(1-B)

B C

(2-A) (2-B)

XPIC 1

IF loop

TX-off

XPIC OFF C

D

XPIC OFF D

B

(1-B)

C

(2-A)

D

(2-B)

IF loop (ODU-D): CASE-B

XPIC 1

A

(1-A)

XPIC 2

IF loop (ODU-C): CASE-B (1-A)

A

A B

(1-A)

(1-A)

A

A

(1-A)

(1-B)

(1-B)

(1-B)

C

(2-A)


B

(2-A)

C

(2-A)

D

(2-B)

D XPIC 2

(2-B)

(2-B) D XPIC OFF D

TX-off

XPIC 2

Tab.54

Local terminal

MN.00329.E - 012

Remote terminal

MANOP



Radio-1A (ODU-A)


Radio-1A transmitter off

Radio-2A (ODU-C)



Radio-1B (ODU-B)


Radio-1B transmitter off

Radio-2B (ODU-D)



198

16.6.6

RF Loop

16.6.6.1

System Configuration Hot-STBY: RF Loop

RF loop (ODU-A) XPIC OFF A RF loop

(1-A) (1-B) (2-A) (2-B)

RF loop (ODU-B)

XPIC 1

B C

XPIC 1

TX-off

A

XPIC OFF B

XPIC OFF B

TX-off

C

XPIC OFF D

D

A B D

(1-A) (1-B) (2-A) (2-B)

(1-A)

A XPIC OFF A

TX-off

(1-B) B XPIC OFF B (2-A) C (2-B)

XPIC OFF C TX-off

D

XPIC 2

B

XPIC 1

TX-off

A

XPIC OFF B RF loop


(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

A

(1-A)

B

(1-B)

C

(2-A)

D

(2-B)

RF loop (ODU-D)

XPIC 1

(1-B)

A

XPIC 2

RF loop (ODU-C) (1-A)

XPIC OFF A

RF loop

TX-off

XPIC OFF D

A B

(1-A)

C

(2-A)

D

XPIC 2

(1-B)

(2-B)

(1-A) (1-B) (2-A)

XPIC OFF A

A

TX-off

B OFF C C XPIC RF loop

(2-B) D XPIC OFF D

XPIC OFF C TX-off

XPIC 2

Tab.55




Radio-1A (ODU-A)


Radio-1A transmitter off Radio-2A transmitter off 1B Xpic Disable 2B Xpic Disable

Radio-2A (ODU-C)


Radio-1A transmitter off Radio-2A transmitter off 1B Xpic Disable 2B Xpic Disable

Radio-1B (ODU-B)


Radio-1B transmitter off Radio-2B transmitter off 1A Xpic Disable 2A Xpic Disable


Radio-1B transmitter off Radio-2B transmitter off 1A Xpic Disable 2A Xpic Disable

Radio-2B (ODU-D)

199

Remote terminal

MN.00329.E - 012

16.6.6.2

System Configuration Frequency Diversity: RF Loop

RF loop (ODU-A) RF loop

(1-A) (1-B) (2-A) (2-B)

RF loop (ODU-B)

XPIC 1

TX-off

A B C D

XPIC OFF B

XPIC 1

A XPIC OFF A

A B

(1-A)

(1-A)

(1-B)

C

(2-A)


D

(2-B)

(2-B)

RF loop

TX-off

D

XPIC 2

XPIC 1

A B RF loop C

(2-A) XPIC OFF C (2-B) D XPIC OFF D

B

(1-B)

C

(2-A)

D

(2-B)

RF loop (ODU-D)

XPIC 1

(1-B)

(1-A)

XPIC 2

RF loop (ODU-C) (1-A)

A

TX-off

A B

(1-A)

(1-A)

A

A

(1-A)

(1-B)

(1-B)

B

(1-B)

C D

(2-A)

(2-A)

B OFF C C XPIC RF loop

C

(2-A)

D

(2-B)

XPIC 2

(2-B)

(2-B) D XPIC OFF D

TX-off

XPIC 2

Tab.56

Local terminal

MN.00329.E - 012

Remote terminal

MANOP



Radio-1A (ODU-A)



Radio-2A (ODU-C)



Radio-1B (ODU-B)



Radio-2B (ODU-D)



200

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 configuration parameter.

201

MN.00329.E - 012

Section 6. PROGRAMMING AND SUPERVISION

18

PROGRAMMING AND SUPERVISION

18.1

GENERAL

AGS-20 is programmed and supervised using CLI and WebLCT. This subject is fully described in the separated software manual. Operating system compatibility are Windows XP or Windows 7.

18.2

SUPERVISION

Three main modalities of DCN can be implemented with SIAE AGS-20: •

In Band DCN at Layer 2

•

Emulated Out of Band DCN at Layer 2

•

Out of Band DCN at Layer 3.

18.2.1

Focus on management ports

On SIAE AGS-20 different ports are related to the management of the equipment: •

LAN 3: Ethernet LAN port configured as the port dedicated to the management traffic (default option)

•

LCT (Local Craft Terminal): RJ45 port to access the local and remote network elements

MN.00329.E - 012

202

•

Console: RJ45 serial port to directly access the command line interface (CLI) of the device for installation and debugging purposes.

Fig.125 - Ports dedicated to management

LAN 3 is the default LAN port assigned to the management traffic of the equipment, (emulated out of band). This setting can be changed just th rough the CLI interface, converting the LAN 3 in a port dedicated to the transport of normal payload traffic or modifying another LAN port to be used as MNGT port. LCT port is physically connected to the CPU of the device and let’s manages the equipment locally. Additionally, with the proper routing configuration, all the network elements in the chain/cluster can be accessed. In fact the CPU interface associated to the LCT port can be used in the routing process like all the other CPU IP interfaces. By CLI it is also possible to enable the DHCP server service on LCT port.

18.2.2

Default values

As factory default configuration, AGS-20 is configured as Emulated Out of Band DCN L2. The interface VLAN 1 is defined for the managemen t as default option and the default IP address is according to ODU Tx frequency: •

low ODU (or no ODU): 172.20.254.14

•

high ODU: 172.20.255.15.

The VLAN ID 1 is enable on the radio port ODU A and on the LAN interface used for management: on SIAE AGS-20 the LAN 3 port is assigned to the management by default. In case the user configures another VLAN for the management traffic, the VLAN 1 cannot be removed from the VL AN table but no ports can be assigned to it. LCT port as default is presetted with IP address 192.168.0.1.

18.2.3

Configurability

In general the management plane can be configured using WebLCT or CLI (see separated software manual). The combinations of management configuration are shown in paragraphs 18.2.3.1 In Band DCN (L2), 18.2.3.2 Emulated Out of Band (L2) and 18.2.3.3 Out of Band DCN (L3).

18.2.3.1

In Band DCN (L2)

In the In Band scenario the DCN traffic is mixed with data traffic, differentiated just on VLAN basis. They are received on the same cable connected to a single interface and forwarded on the radio link exploiting all the available bandwidth. A specific VLAN ID is dedicated to the DCN traffic transportation, while the normal payload traffic can be forwarded using different VLAN IDs.

203

MN.00329.E - 012

Fig.126 - In Band DCN cabling

To configure the equipment management in a In Band scenario and to manage the device through the reserved VLAN interface, it is necess ary to define the related MNGT VLAN into the VLAN table, then to define and configure a VLAN IP address and a default gateway IP address. These latter parameters can be inserted under the Management Port Configuration area, as shown in Fig.127, as well as the choice of the MNGT VLAN. Once this VLAN interface is created and an IP address is assigned to it, the management traffic is forwarded over the different ports associated to this same VLAN, according to the equipment VLAN table.

Fig.127 - Management port configuration

18.2.3.2

Emulated Out of Band (L2)

In Emulated Out Of Band scenario, the management traffic is provided to the IDU through a dedicated port, separated from the payload traffic. As the previous case, no dedicated channel is used on the radio path, where the management traffic is carried with a dedicated VLAN separately from the payload traffic.

MN.00329.E - 012

204

Fig.128 - Emulated Out Of Band DCN Cabling

18.2.3.3

Out of Band DCN (L3)

In the Out Of Band scenario a dedicated channel (128 kbps) embedded in the header of the radio frame is available for the transmission of management data to the far end, completely separated from the payload traffic. This management traffic must be routed at L3 by the IDU microprocessor and transmitted using a PPP connection on the radio link between the two nodes over an HDLC channel. To configure the Out of Band management scenario, first of all a PPP link has to be enabled on the radio port in the MNGT Out of Band area.

Fig.129 - Out of Band PPP configuration

Under the MNGT Port Configuration area, an IP address has to be assigned to the LAN interface that has anyway to be associated to a MNGT VLAN ID. In fact, besides on the radio chan nel the management traffic is forwarded through the PPP channel and the radio port has to be removed from the MNGT VLAN, on the line direction, the management traffic can be forwarded either on a dedicated cable connected to the MNGT port with no VLAN tag or through the same cable of the payload traffic using a different VLAN ID. Additionally, the user has to set the next hop to reach the default gateway that in this case can be either a PPP interface or a simple gateway IP address with the related network mask.

205

MN.00329.E - 012

The PPP interfaces allocated in the same SIAE AGS-20 device have to be addressed with a set of IP addresses belonging to different subnets. Regarding the single Out of Band PPP channel, two different configurations are possible: •

numbered PPP: it assigns two valid IP addresses to the local and remote peer of the PPP connection in the same subnet. In order to save addresses it is suggested to use /30 (255.255.255.252) su bnet mask

•

unnumbered PPP: the radio interface is assigned to a correspondent loopback IP address, i.e. a single host /32 (255.255.255.255) IP address. In this case there is no need of the /30 subnet to address local and remote NE, that has to be configured in the same way. Each PPP instance on the same SIAE AGS-20 re quires a different loopback interface. After the interface is crea ted it is possible to define it as a valid interface in a static route to reach the equipment from a remote location.

Additionally, SIAE AGS-20 allows configuring and managing network routing. Internal routing between all interfaces of the microprocessor is automatically resolved by the equipment by meaning of connected routes. External routing must be defined by the user with static routes and default gateway, to be inserted in the equipment routing table.

Fig.130 - Example of AGS-20 routing table

18.2.4

OSPF (Open Shortest Path First) Protocol

The Open Shortest Path First (OSPF) is a protocol that allows the dynamic routing of IP packets between different routers of an IP network. This Interior Gateway Protocol (IGP) is used to distribute routing information within a single Autonomous System. Moreover, OSPF is a Link State protocol. The main advantages offered by OSPF compared to sta tic routing are the following: •

using static routing in large IP networks, the network routers could need several routing lines to reach all the Network Elements. OSPF allows reducing the costs of network planning an d provisioning

•

if the network evolves rapidly, using static routing each upgrade of the network may cause a reconfiguration of the already installed equipment. OSPF allows the automatic re-configuration of all the Network Elements after the network upgrades

•

in case of link failure, OSPF search for alternative paths in order to keep all the networks connected (i.e. if an alternative path is present the OSPF offers redundancy)

•

OSPF chooses the shortest path to route packets between two network elements. To each link it is assigned a weight (cost), so that, for example, in the shortest path calculation, high capacity links are preferred to the low capacity ones (the capacity is one of the possible metric to be used).

By default the cost of an interface is calculated on the basis of its bandwidth. As it relates the metric value of an interface, it is inversely proportional to the bandwidth of that interface.

MN.00329.E - 012

206

However, the network designer can force a differen t cost to each interface. Each router generates its routing table from the Link State Database by calculating a tree of shortes t paths with the router itself as root. The shortest path is calculated using the Dijkstra’s algorithm. The implementation of OSPF protocol among routers present in the IP network consists of several steps which enable all the involved routing elements to build their own routing tables from the information contained in the Link State Database, by calculating a tree of shortest paths with the router itself as root. The following steps briefly resume how OSPF works: 1. the router learns the information relevant to its interfaces and the neighbouring routers (Link State information) 2. upon initialization or due to any change in routing information, a router will generate Link State Advertisement (LSA) packets and then send them to other routers. This advertisement will represent the collection of all Link States on that router 3. each router collects the Link State Advertisements of all the network routers in a Link State Database. All the routers of the network must have the same Link State Database. All the routers’ databases are synchronized using the sequence numbers 4. on the basis of the Link State Database information, each router uses the Dijkstra algorithm in order to calculate the Shortest Path Tree to reach the other routers of the network 5. in case no changes in the OSPF network occur, such as cost of a link or a network being added or deleted, OSPF should be very quiet. Any changes that occur are communicated via LSA packets, and the Dijkstra algorithm is recalculated to find an alternative shortest path.

18.2.4.1

OSPF Areas

OSPF uses flooding to exchange Link State updates between routers. Any change in routing information is flooded to all routers in the network. Areas are introduced to put a bounda ry on the explosion of Link State updates. Flooding and calculation of the Dijkstra algorithm on a router is limited to changes within an area (see Fig.131). All routers within an area have the exact Link State Database. Each area belonging to a certain OSPF routing process is defined by an Area-Identifier (Area-ID). If more than one area is configured, one of these areas has be to be Area 0.0.0.0). This is called the Backbone. When designing networks it is good practice to start with Area 0.0.0.0 and then expand into other areas later on. OSPF has special restrictions whe n multiple areas are involved: the Backbone has to be a t the centre of all other Areas, and all other Areas have to be physically connected to the Backbone. The reasoning behind this is that OSPF expects all Areas to inject routing information into the Backbone and in turn the Backbone will disseminate that information into other Areas (see Fig.131). The main advantages resulting from such a OSPF hierarchical structure are:

207

•

the topology of an area is invisible from the outside of the area. Routers internal to a given area know nothing of the detailed topology external to the area

•

because each area maintains a separate link state database (whose information may be summarized towards the rest of the network by the connecting router), the amount of routing traffic between parts of an autonomous system is reduc ed with respect to the hypothetical scenario for which the entire Autonomous System works with a single Link State Domain

•

with the introduction of Areas, it is no longer true that all routers in the Autonomous System (AS) have an identical Link State Database. A router actually has a separate Link Sta te Database for each area it is connected.

MN.00329.E - 012

Fig.131

When the Autonomous System is s plit into multiple Areas, the routers are further divided according to function into the following overlapping categories (Fig.132): •

a router that has all of its interfaces within the same area is called an Internal Router (IR)

•

routers that belong to multiple areas, and connect these areas to the backbone area (Area #0) are called Area Border Routers (ABR). ABRs must therefore maintain information describing the backbone areas and other attached areas

•

routers that act as gateways (redistribution) between OSPF and other routing protocols (IGRP, EIGRP, IS-IS, RIP, BGP, Static) or other instances of the OSPF routing process are called Autonomous System Boundary Router (ASBR).

It is worth to underline that any router can be selected as ABR or ASBR.

Fig.132

Once defined the hierarchical of OSPF network, different types of routing information will flow through areas (Fig.133): •

routes that are generated from within an area (the destination belongs to the area) are called intraarea routes.

•

routes that originate from other areas are called inter-area or Summary routes.

MN.00329.E - 012

208

•

routes that originate from other routing protocols (or different OSPF processes) and that are injected into OSPF via redistribution are called external routes.

When multiple different routes to the same destination are available, the OSPF protocol will select the route with the following priority order: intra-area, inter-area and external.

Fig.133

18.2.4.2

Virtual Links

In general, the Area 0.0.0.0 (Backbone) must be contiguous to peripheral areas. So doing, all Areas will be directly connected to the Backbone as shown in Fig.132. However, it doesn’t need to be physica lly contiguous: backbone connectivity can be established/maintained through the configuration of virtual links. In other words, Virtual Links are used for two purposes: •

linking an area that does not have a physical connection to the Backbone. The Virtual Link will provide the disconnected area a logical path to the Backbone. The Virtual Link has to be established between two ABRs having a common area, with one ABR connected to the Backbone

•

patching the Backbone in case a discontinuity of the Area #0 occurs. Two Area #0s could be linked together through a Virtual Link. In some cas es, Virtual Links are added for redundancy in c ase some router failure causes the backbone to be split into two.

18.2.4.3

Stub Areas

In the autonomous systems, large amounts of external information may be injected into the OSPF domain via the autonomous system boundary router. External information is further propagated by all areas. To take this into account, there is a concept known as Stub Area. A stub Area only accepts link state advertisement with regard to its own OSPF system. Routing in external system take place on a default route, which is generated by its area border router. this restriction can potentially reduce the size of router tables within the stub area. Stability within the area also increases, as

209

MN.00329.E - 012

modifications in external system do not lfood the area. Because external information is to be avoided, it is not possible to use an autonomous system boundary router in a stub area. Stub area is an attribute that is bound to an area and not to a router within the area. it is therefore only possible to declare whole areas as stub and not routers within them. Typical applications for this are star topologies with the network central unit in the center. The external sites become stub areas, as they do not need to know every network in the corporate backbone. However, all unknown networks can still be reached by default routes.

Fig.134 - OSPF Stub Areas

Fig.135 - OSPF Stub Areas

MN.00329.E - 012

210

18.2.4.4

Neighbours

Routers that share a common segment become neighbours on that segment. Neighbours are elected via the Hello protocol. Hello packets are sent periodically out of each interface using IP multicast. Routers become neighbours as soon as they see themselves listed in the neighbour's Hello packet. This way, a two way communication is guaranteed. Two routers will not become neighbours unless they agree on the following: •

Area-ID: two routers having a common segment; their interfaces have to belong to the same area on that segment. Of course, the interfaces should belong to the same subnet and have a similar mask

•

Authentication: OSPF allows for the configuration of a password for a specific area. Routers that want to become neighbours have to exchange the same password on a particular segment.

•

Hello and Dead Intervals: OSPF exchanges Hello packets on each segment. This is a form of keep alive used by routers in order to acknowledge their existence on a segment. The Hello interval specifies the length of time, in seconds, between the hello packets that a router sends on an OSPF interface. The dead interval is the number of seconds that a router's He llo packets have not been seen before its neighbours declare the OSPF router down. OSPF requires these intervals to be exactly the same between two neighbours. If any of these intervals are different, these routers will not become neighbours on a particular segment.

•

Stub Area flag: two routers have to also agree on the stub area flag in the Hello packets in order to become neighbours.

18.2.4.5

Route Summarization

When designing OSPF networks it is good practice to start with Area 0.0.0.0 and then expand into other areas later on. OSPF expects all areas to inject routing information into the Backbone and in turn the Backbone will disseminate that Information into other areas. Route summarization allows optimizing the number of routes propagated into each area, through consolidation of multiple routes into one single advertisement. This is normally done at the boundaries of Area Border Routers (ABRs). It is better to summarize in the direction of the Backbone. Th is way the Backbone receives all the aggregate addresses and in turn will injects them, already summarized, into other areas. The advantage of summarization is to reduce the total number of subnetworks advertised in the whole network and, as a consequence, the number of routing line to be processed by each router. In OSPF there are two types of summarization: •

inter-area route summarization: it is done by ABRs and it allows to consolidate multiple routes of an area into one single route. It does not apply to external routes injected into OSPF via redistribution.

•

external route summarization: it is done by ASBRs, it allows to consolidate multiple external routes into one single route. External routes are injected into the OSPF network by the ASBR.

18.2.4.6

OSPF programmability

In order to give the proper setting to OSPF protocol, in the WEBLct is present the following menu:

211

MN.00329.E - 012

Fig.136

Then the possible context will be available: •

basic settings

•

area

•

interface

•

neighbour (read only)

•

Lsa DB (read only)

18.2.4.7

Basic settings

Here is it Enable/Disable OSPF protocol, set what kind of router must be the equipment in an OSPF network, and set some basic parameters of the feature.

Fig.137

MN.00329.E - 012

212

18.2.4.8

Area

Here is it possible to create different areas than the default (i.e. 0.0.0.0 or backbone) to which the interfaces (by the context Interface) on equipment can be assigned.

Fig.138

18.2.4.9

Interface

Here we can select the router interfaces and their characteristics to be used by OSPF protocol.

Fig.139

213

MN.00329.E - 012

18.2.4.10 Summary Address Through the Summary menu it is possible to add a new Route Summarization to the router. The new Route Summarization has to be identified by: •

“area-ID” that is the identification number of the OSPF Area that contains the sub-networks grouped into a single Route Summarization.

•

“net” that represents the range of addresses that are grouped into the Route Summarization.

•

“mask” that is the mask relevant to the Net which summarizes the sub-networks belonging to the OSPF Area having the Area-ID defined above.

Fig.140

MN.00329.E - 012

214

18.2.4.11 Neighbour Neighbour information and status tab, read-only parameters.

Fig.141

18.2.4.12 Lsa DB Lsa DB information tab, read-only parameters.

Fig.142

18.2.4.13 Example DCN L3 Out Of Band with OSPF protocol In this example we consider a point to point link in 1+0 configuration. Both the network elements belong to the default OSPF Backbone AREA 0.0.0.0 As OSPF interfaces we use the DCN port LAN3 an d the out of band Radio Interface with PPP protocol in unnubured mode.

215

MN.00329.E - 012

PPP OduA Unnumbered 192.168.80.2

PPP OduA Unnumbered 192.168.80.4

DCN LAN3 192.168.79.20/24 DCN LAN3 192.168.81.21/24

Station A

Station B

PC Port 192.168.79.1/24 GW:192.168.79.20/24

Fig.143

In the station A we have the following setting:

Fig.144 - DCN Port, (LAN 3)station A

Fig.145 - PPP Protocol enabled in Un-numbered mode

MN.00329.E - 012

216

Fig.146 - OSPF Basic settings

Fig.147 - OSPF default AREA

Fig.148 - OSPF Interfaces assignment, (PPP Radio Interface type pTp, Vlan1 Lan3 Interface type broadcast)

Fig.149 - Neighbour discovered

217

MN.00329.E - 012

Fig.150 - Lsa DB

Fig.151 - Routing Table created by OSPF

In the station B we have the following setting:

Fig.152 - DCN Port, (LAN3) Station B

Fig.153 - PPP Protocol enabled in Un-numbered mode

MN.00329.E - 012

218

Fig.154 - OSPF protocol Basic Settings

Fig.155 - OSPF default AREA

Fig.156 - OSPF Interfaces assignment, (PPP Radio Interface type pTp, Vlan1 Lan3 Interface type broadcast)

Fig.157 - Routing Table created by OSPF

219

MN.00329.E - 012

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.57) 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 - 012

220

Tab.57- IDU part number

Digit

Letter/number

Meaning

1

G

Functional assembly of units completed by a mechanical structure

2

A

AL equipment

3

I

Indoor installation

0212 to .....

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 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 0233 - AGS-20-XG Quad IF 0234 - AGS-20-XG Quad IF W/16xE1 0235 - AGS-20-XG Quad IF w/16xE1+2xSTM-1+Nodal

4 to 7

221

MN.00329.E - 012

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 off ered in different versions depending on the operating bands, th e antenna 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.58 and Tab.59 various ODU versions and hybrid part number are listed. Part number, hardware layout and equipment composition are subject to change without notice. Tab.58 - ODU ASN part number and description

RF band in GHz

ODU description

Part number

ODU ASN6L SB=1H

GE9501

ODU ASN6L SB=1L

GE9500

ODU ASN6L SB=2H

GE9503

ODU ASN6L SB=2L

GE9502

ODU ASN6L SB=3H

GE9505

ODU ASN6L SB=3L

GE9504

ODU ASN6L SB=4H

GE9507

ODU ASN6L SB=4L

GE9506

ODU ASN6U SB=1H

GE9509

ODU ASN6U SB=1L

GE9508

ODU ASN6U SB=2H

GE9511

ODU ASN6U SB=2L

GE9510

ODU ASN6U SB=3H

GE9513

ODU ASN6U SB=3L

GE9512

6

MN.00329.E - 012

222

RF band in GHz

7

7

ODU description

Part number

ODU ASN7L/161 SB=1H

GE9519

ODU ASN7L/161 SB=1L

GE9518

ODU ASN7L/161 SB=2H

GE9521

ODU ASN7L/161 SB=2L

GE9520

ODU ASN7L/161 SB=3H

GE9523

ODU ASN7L/161 SB=3L

GE9522

ODU ASN7L/196 SB=1H

GE9525

ODU ASN7L/196 SB=1L

GE9524

ODU ASN7L/196 SB=2H

GE9527

ODU ASN7L/196 SB=2L

GE9526

ODU ASN7L/196 SB=3H

GE9529

ODU ASN7L/196 SB=3L

GE9528

ODU ASN7M/154 SB=1H

GE9535

ODU ASN7M/154 SB=1L

GE9534

ODU ASN7M/154 SB=2H

GE9537

ODU ASN7M/154 SB=2L

GE9536

ODU ASN7M/154 SB=3H

GE9539

ODU ASN7M/154 SB=3L

GE9538

ODU ASN7M/154 SB=4H

GE9541

ODU ASN7M/154 SB=4L

GE9540

ODU ASN7M/154 SB=5H

GE9543

ODU ASN7M/154 SB=5L

GE9542

ODU ASN7M/161 SB=1H

GE9545

ODU ASN7M/161 SB=1L

GE9544

ODU ASN7M/161 SB=2H

GE9547

ODU ASN7M/161 SB=2L

GE9546

ODU ASN7M/161 SB=3H

GE9549

ODU ASN7M/161 SB=3L

GE9548

ODU ASN8/311,32 SB=1H

GE9583

ODU ASN8/311,32 SB=1L

GE9582


GE9585


GE9584


GE9587


GE9586


GE9589


GE9588

8

223

MN.00329.E - 012

RF band in GHz

ODU description

Part number

ODU ASN10/350 SB=1H

GE9601

ODU ASN10/350 SB=1L

GE9600

ODU ASN13 SB=1H

GE9613

ODU ASN13 SB=1L

GE9612

ODU ASN13 SB=2H

GE9615

ODU ASN13 SB=2L

GE9614

ODU ASN13 SB=3H

GE9617

ODU ASN13 SB=3L

GE9616

ODU ASN13 SB=4H

GE9619

ODU ASN13 SB=4L

GE9618

ODU ASN15 315/322 SB=1H

GE9629

ODU ASN15 315/322 SB=1L

GE9628

ODU ASN15/420 SB=1H

GE9647

ODU ASN15/420 SB=1L

GE9646

ODU ASN15/420 SB=2H

GE9649

ODU ASN15/420 SB=2L

GE9648

ODU ASN15/420 SB=3H

GE9651

ODU ASN15/420 SB=3L

GE9650

ODU ASN15/420 SB=4H

GE9653

ODU ASN15/420 SB=4L

GE9652

ODU ASN15/644 SB=1H

GE8679

ODU ASN15/644 SB=1L

GE8678

ODU ASN15/644 SB=2H

GE8681

ODU ASN15/644 SB=2L

GE8680

ODU ASN15/728 SB=1H

GE9691

ODU ASN15/728 SB=1L

GE9690

ODU ASN18/1010 SB=1H

GE9701

ODU ASN18/1010 SB=1L

GE9700


GE9703


GE9702


GE9705


GE9704


GE9707


GE9706


GE9717


GE9716

10

13

15

18

MN.00329.E - 012

224

RF band in GHz

ODU description

Part number


GE9719


GE9718


GE9721


GE9720

ODU ASN23/1200/1232 SB=1H

GE9727

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

ODU ASN25 SB=1H

GE9737

ODU ASN25 SB=1L

GE9736

ODU ASN25 SB=2H

GE9739

ODU ASN25 SB=2L

GE9738

23

25

225

MN.00329.E - 012

Tab.59 - ODU ASNK part number and description

RF band in GHz

ODU description

Part number

ODU ASNK6L/256,04 HP SB=1H

GE3501-42

ODU ASNK6L/256,04 HP SB=1L

GE3500-42


GE3503-42


GE3502-42


GE3505-42


GE3504-42


GE3507-42


GE3506-42

ODU ASNK6U/340 HP CH=1H

GE2101-42

ODU ASNK6U/340 HP CH=1L

GE2100-42


GE2103-42


GE2102-42


GE2105-42


GE2104-42


GE2107-42


GE2106-42


GE2109-42


GE2108-42


GE2111-42


GE2110-42


GE2113-42


GE2112-42


GE2115-42


GE2114-42

ODU ASNK7H/245 SB=1H

GE8557-42

ODU ASNK7H/245 SB=1L

GE8556-42


GE8559-42


GE8558-42


GE8561-42


GE8560-42

ODU ASNK7L/154 SB=1H

GE8621-42

ODU ASNK7L/154 SB=1L

GE8620-42


GE8623-42


GE8622-42


GE8625-42


GE8624-42

6

7

MN.00329.E - 012

226

RF band in GHz

7

227

ODU description

Part number


GE8627-42


GE8626-42


GE8519-42


GE8518-42


GE8521-42


GE8520-42


GE8523-42


GE8522-42


GE8533-42


GE8532-42


GE8525-42


GE8524-42


GE8527-42


GE8526-42


GE8529-42


GE8528-42


GE8531-42


GE8530-42

ODU ASNK7LM/161 SB=1H

GE8475-42

ODU ASNK7LM/161 SB=1L

GE8474-42


GE8477-42


GE8476-42


GE8479-42


GE8478-42


GE8481-42


GE8480-42

ODU ASNK7M/154 SB=1H

GE8535-42

ODU ASNK7M/154 SB=1L

GE8534-42


GE8537-42


GE8536-42


GE8539-42


GE8538-42


GE8541-42


GE8540-42


GE8545-42


GE8544-42


GE8547-42

MN.00329.E - 012

RF band in GHz

7

ODU description

Part number


GE8546-42


GE8549-42


GE8548-42


GE8485-42


GE8484-42

ODU ASNK7M/168 HP CH=1H

GE2202-42

ODU ASNK7M/168 HP CH=1L

GE2201-42


GE2204-42


GE2203-42


GE2206-42


GE2205-42


GE2208-42


GE2207-42


GE2210-42


GE2209-42


GE8551-42


GE8550-42


GE8553-42


GE8552-42


GE8555-42


GE8554-42

ODU ASNK8/119 SB=1H

GE8591-42

ODU ASNK8/119 SB=1L

GE8590-42

ODU ASNK8/119 SB=2H

GE8593-42

ODU ASNK8/119 SB=2L

GE8592-42

ODU ASNK8/119 SB=3H

GE8595-42

ODU ASNK8/119 SB=3L

GE8594-42

ODU ASNK8/119 SB=4H

GE8597-42

ODU ASNK8/119 SB=4L

GE8596-42

ODU ASNK8/126 SB=1H

GE8655-42

ODU ASNK8/126 SB=1L

GE8654-42

ODU ASNK8/126 SB=2H

GE8657-42

ODU ASNK8/126 SB=2L

GE8656-42

ODU ASNK8/126 SB=3H

GE8659-42

ODU ASNK8/126 SB=3L

GE8658-42

ODU ASNK8/126 SB=4H

GE8661-42

ODU ASNK8/126 SB=4L

GE8660-42

8

MN.00329.E - 012

228

RF band in GHz

ODU description

Part number

ODU ASNK8/266 SB=1H

GE8571-42

ODU ASNK8/266 SB=1L

GE8570-42

ODU ASNK8/266 SB=2H

GE8573-42

ODU ASNK8/266 SB=2L

GE8572-42

ODU ASNK8/266 SB=3H

GE8575-42

ODU ASNK8/266 SB=3L

GE8574-42

ODU ASNK8/310 SB=1H

GE8577-42

ODU ASNK8/310 SB=1L

GE8576-42

ODU ASNK8/310 SB=2H

GE8579-42

ODU ASNK8/310 SB=2L

GE8578-42

ODU ASNK8/310 SB=3H

GE8581-42

ODU ASNK8/310 SB=3L

GE8580-42

ODU ASNK8/311,32 SB=1H

GE8583-42

ODU ASNK8/311,32 SB=1L

GE8582-42


GE8585-42


GE8584-42


GE8587-42


GE8586-42


GE8589-42


GE8588-42


GE8599-42


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

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

ODU ASNK13/266 SB=1H

GE8613-42

ODU ASNK13/266 SB=1L

GE8612-42


GE8615-42


GE8614-42


GE8617-42


GE8616-42


GE8619-42


GE8618-42

8

11

13

229

MN.00329.E - 012

RF band in GHz

ODU description

Part number

ODU ASNK15/315/322 SB=1H

GE8629-42

ODU ASNK15/315/322 SB=1L

GE8628-42


GE8631-42


GE8630-42


GE8633-42


GE8632-42


GE8635-42


GE8634-42


GE8637-42


GE8636-42


GE8647-42


GE8646-42


GE8649-42


GE8648-42


GE8651-42


GE8650-42


GE8653-42


GE8652-42


GE8663-42


GE8662-42


GE8665-42


GE8664-42


GE8667-42


GE8666-42


GE8669-42


GE8668-42


GE8691-42


GE8690-42

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

ODU ASNK18/1008/1010 SB=3H

GE8705-42

ODU ASNK18/1008/1010 SB=3L

GE8704-42


GE8717-42


GE8716-42

15

18

MN.00329.E - 012

230

RF band in GHz

ODU description

Part number


GE8719-42


GE8718-42


GE8721-42


GE8720-42

ODU ASNK23/1200/1232 SB=1H

GE8727-42

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


GE8737-42


GE8736-42


GE8739-42


GE8738-42


GE8783-42


GE8782-42


GE8785-42


GE8784-42


GE8791-42


GE8790-42


GE8793-42


GE8792-42


GE8795-42


GE8794-42

23

25

38

42

231

MN.00329.E - 012

Section 8. LISTS AND SERVICES

21

LIST OF FIGURES

Fig.1 - Components electrostatic charge sensitive indication............... .................................. 5 Fig.2 - Elasticized band ................................................................................................ ... 5 Fig.3 - Coiled cord .................................................................................... ...................... 6 Fig.4 - WEEE symbol - 2002/96/CE EN50419 ..................................................................... 7 Fig.5 ............................................................................................................................ 17 Fig.6 ............................................................................................................................ 17 Fig.7 - 1+0 System configuration .................................................................................. .. 20 Fig.8 - (1+1) Protection: one cluster is available ............................................................... 20 Fig.9 - (2+0)XPIC: one cluster is available....... ................................................................. 20 Fig.10 - (2+0)FD: one cluster is available ......................................................................... 21 Fig.11 - 2x(1+0) different directions ................................................................................ 22 Fig.12 - Port configuration 1, 2: (1+1) cluster 1 ........................................................ ........ 22 Fig.13 - Port configuration 3, 4: (2+0) cluster 1 ........................................................ ........ 23 Fig.14 - (1+1) protection: two clusters are available .......................................................... 23 Fig.15 - (2+0) XPIC: two clusters are available ................................................................. 23 Fig.16 - (2+0) FD: three clusters are available ........................................................ .......... 24 Fig.17 - (1+1) XPIC protection: all IF ports are part of the cluster........................................ 24 Fig.18 - (4+0) FD: all IF ports are part of the cluster ......................................................... 24 Fig.19 - (4+0) XPIC: all IF ports are part of the cluster .............................................. ........ 24 Fig.20 - Port config 0: Nx(1+0) different directions ............................................................ 27 Fig.21 - Port config 1 and 2: (1+1) cluster 1.......................... ........................................... 27 Fig.22 - Port config 9 and 10: (1+1) cluster 2 ................................................................... 28 Fig.23 - Port config. 3, 4: (2+0) cluster 1 ......................................................................... 29

MN.00329.E - 012

232

Fig.24 - Port config 5: (3+0). ........................................................................................ .. 29 Fig.25 - Port config 6 and 7: (4+0) .................................................................................. 30 Fig.26 - Port config 8: (2+0) cluster 3.............................................................................. 30 Fig.27 - Port config 11 and 12: (2+0) cluster 3 & (1+1) cluster 2 ........................................ 31 Fig.28 - Port config from 13 to 16: (1+1) cluster 1 & (1+1) cluster 2 ................................... 31 Fig.29 - Port config from 17 to 20: (2+0) cluster 1 & (2+0) cluster 2 ................................... 32 Fig.30 - Port config 21 and 22: (1+1) XPIC HSB or FD ....................................................... 32 Fig.31 - AGS-20 Ethernet block diagram. .......................................................................... 33 Fig.32 – AGS-20 Ethernet block diagram ......................................................... ................. 34 Fig.33 – QoS block diagram ...................................................................................... ...... 40 Fig.34 - Default 802.1p PCP-queue map ........................................................................... 41 Fig.35 - Default ToS (DSCP) map .................................................................................. .. 41 Fig.36 – Red Curve ........................................................................................ ................ 44 Fig.37 - WEBLCT Header Compression field...................................... ................................. 48 Fig.38 – PW Control Word structure ........................................................................... ...... 49 Fig.39 – ELP between a SIAE AGS-20 and an external switch .............................................. 51 Fig.40 – Select the LAN port that sends LLF status ........................................................... .. 54 Fig.41 – Select the circuit that manages the LLF protected LAN port..................................... 55 Fig.42 .......................................................................................................................... 64 Fig.43 .......................................................................................................................... 65 Fig.44 .......................................................................................................................... 65 Fig.45 - AGS-20 switch (GAI0212-1) ................................................................................ 68 Fig.46 - AGS-20 Single IF (GAI0213-1) ............................................................................ 69 Fig.47 - AGS-20 Single IF/16E1 (GAI0214-1) .................................................................... 69 Fig.48 - AGS-20 Dual IF (GAI0215- 2) .............................................................................. 70 Fig.49 - AGS-20 Dual IF/16E1 (GAI0216-2 ) ...................................................................... 70 Fig.50 - AGS-20 Quad ETH (GAI0222-2).......................................... ................................. 70 Fig.51 - AGS-20 Quad ETH/16E1 (GAI0223-2) .................................................................. 71 Fig.52 - AGS-20 PP Single IF/16E1 (GAI0225-1) ................................................................ 71 Fig.53 - AGS-20 Dual IF/16E1 + 2STM1 + Nodal (GAI0217-2)............................. ................ 72 Fig.54 - AGS-20 single IF/16E1 + 2STM1 +Nodal (GAI0218-1) ............................................ 72 Fig.55 - AGS-20 Quad Eth/16E1 + 2STM1 + nodal (GAI0224-2).......................................... 73 Fig.56 - AGS-20 PP Single IF/16E1 + 2STM1 + Nodal (GAI0226-1) ...................................... 73 Fig.57 - AGS-20 Quad IF (GAI0219-1) ............................................................................. 74 Fig.58 - AGS-20 Quad IF/16E1 (GAI0220-1) ........................................................... .......... 74 Fig.59 - AGS-20 Quad IF/16E1 + 2STM1 + Nodal (GAI0221-1)...................................... ...... 74 Fig.60 - AGS-20-XG Quad-IF (GAI0233) ............................................................... ............ 75 Fig.61 - AGS-20-XG Quad-IFw/ 16xE1 (GAI0234) .............................................................. 75 Fig.62 - AGS-20-XG Quad-IFw/ 16xE1+2xSTM1+2xNodal (GAI0235) ................................... 76 Fig.63 - ASN or ASNK ODU ............................................................................. ................ 91 Fig.64 - Final 1+1 assembly with ASN or ASNK ODU ................................................ .......... 92 Fig.65 - ASNK ODU (for frequency > 15 GHz) ..................................................... .............. 93 Fig.66 - ODU block diagram .......................................................................................... .. 94

233

MN.00329.E - 012

Fig.67 - 1+1 hot stand–by 1 antenna........................ ....................................................... 95 Fig.68 - 1+1 hot stand–by 2 antennas ............................................................................. 95 Fig.69 - ATPC operation ..................................................................................... ............ 96 Fig.70 – Ventilation air flows in AGS-20 IDU ................................................................... 1 00 Fig.71 - Grounding connection ................................................................................ ...... 105 Fig.72 ........................................................................................................................ 106 Fig.73 - Grounding kit positioning .................................................................................. 1 07 Fig.74 - IDU AGS-20 front panel example for GAI0216 ..................................................... 109 Fig.75 - Pin-out Tributary 50 pin SCSI female ............................................................. .... 111 Fig.76 - Pin-out Tributary 50 pin SCSI female ............................................................. .... 113 Fig.77 - 1+0 pole mounting .................................................................................... ...... 119 Fig.78 - ODU body reference tooth ................................................................................ 120 Fig.79 - 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.................................................................... 120 Fig.80 - 1+0 support ................................................................................ ................... 121 Fig.81 - ODU housing final position for both polarization ................................................... 122 Fig.82 - Antenna aiming .............................................................................. ................. 123 Fig.83 - ODU grounding ................................................................................ ............... 123 Fig.84 - Hybrid and twist disk ............................................................................... ........ 124 Fig.85 - Polarization disk fixing (only for 13 GHz and 15 GHz) ........................................... 125 Fig.86 - Hybrid installation................................................................................ ............ 126 Fig.87 - 1+1 ODUs installation .............................................................................. ........ 126 Fig.88 - Assembled structure (DP antenna, OMT, mounting system)................................... 131 Fig.89 - Centring ring ............................................................................................ ...... 132 Fig.90 - Fast lock ODU support............................. ......................................................... 1 32 Fig.91 - ODU ASN/ASNK Standard lock............................................................. .............. 133 Fig.92 - 1+0 pole mounting .................................................................................. ........ 138 Fig.93 - ODU body reference tooth ................................................................................ 139 Fig.94 - 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.................................................................... 139 Fig.95 - 1+0 support ................................................................................ ................... 140 Fig.96 - ODU housing final position for both polarization ................................................... 141 Fig.97 - Antenna aiming .............................................................................. ................. 142 Fig.98 - ODU grounding ................................................................................ ............... 143 Fig.99 - Hybrid and twist disk ............................................................................... ........ 144 Fig.100 - Polarization disk fixing (only for 13 GHz and 15 GHz).......................................... 145 Fig.101 - Hybrid installation .......................................................................................... 146 Fig.102 - 1+1 ODUs installation .................................................................................... 147 Fig.103 - ODU ASN/ASNK with fast lock coupling flange.................................................. .. 155 Fig.104 - ODU ASN/ASNK with standard coupling flange ................................................... 156 Fig.105 - 1+0 ODU installation ...................................................................................... 1 57 Fig.106 - 1+1 ODU installation ...................................................................................... 1 58 Fig.107 - Polarization disk .......................................................................................... .. 159 Fig.108 - 1+0 antenna flange ....................................................................................... 159

MN.00329.E - 012

234

Fig.109 - 1+1 antenna flange ................................................................................. ...... 160 Fig.110 - Detected voltage versus RF received signal ....................................................... 167 Fig.111 ....................................................................................................... ............... 180 Fig.112 ....................................................................................................... ............... 181 Fig.113 - PRBS........................................... ................................................................. 182 Fig.114 - IF Loop & RF Loop....................................................... ................................... 18 2 Fig.115 - Radio Loop &Cmd .......................................................................................... 183 Fig.116 - TDM Loopback .......................................................................... ..................... 185 Fig.117 - ETH Loopback ................................................................................. .............. 185 Fig.118 - Station A Status .......................................................................................... .. 188 Fig.119 - Station B status ............................................................................ ................. 189 Fig.120 - FMP TX Failure Alarm ....................................................................... .............. 189 Fig.121 - RX Failure/Alarms, Demodulator unlock ............................................................ 190 Fig.122 - FMP RESET Procedure........................ ............................................................. 190 Fig.123 - XPIC Manual Operation ............................................................................. ...... 191 Fig.124 ....................................................................................................... ............... 191 Fig.125 - Ports dedicated to management........ ............................................................... 203 Fig.126 - In Band DCN cabling ...................................................................................... 2 04 Fig.127 - Management port configuration ....................................................................... 204 Fig.128 - Emulated Out Of Band DCN Cabling....................................... ........................... 205 Fig.129 - Out of Band PPP configuration ......................................................................... 20 5 Fig.130 - Example of AGS-20 routing table ..................................................................... 2 06 Fig.131 ....................................................................................................... ............... 208 Fig.132 ....................................................................................................... ............... 208 Fig.133 ....................................................................................................... ............... 209 Fig.134 - OSPF Stub Areas ............................................................................... ............ 210 Fig.135 - OSPF Stub Areas ............................................................................... ............ 210 Fig.136 ....................................................................................................... ............... 212 Fig.137 ....................................................................................................... ............... 212 Fig.138 ....................................................................................................... ............... 213 Fig.139 ....................................................................................................... ............... 213 Fig.140 ....................................................................................................... ............... 214 Fig.141 ....................................................................................................... ............... 215 Fig.142 ....................................................................................................... ............... 215 Fig.143 ....................................................................................................... ............... 216 Fig.144 - DCN Port, (LAN 3)station A ............................................................................. 216 Fig.145 - PPP Protocol enabled in Un-numbered mode. ..................................................... 21 6 Fig.146 - OSPF Basic settings............................. ........................................................... 217 Fig.147 - OSPF default AREA....................................................................................... .. 217 Fig.148 - OSPF Interfaces assignment, (PPP Radio Interface type pTp, Vlan1 Lan3 Interface type broadcast)................................... ................................................................................ 217 Fig.149 - Neighbour discovered ............................................................................. ........ 217 Fig.150 - Lsa DB .................................................................................. ....................... 218

235

MN.00329.E - 012

Fig.151 - Routing Table created by OSPF ........................................................................ 218 Fig.152 - DCN Port, (LAN3) Station B ......................................................................... .... 218 Fig.153 - PPP Protocol enabled in Un-numbered mode. ..................................................... 21 8 Fig.154 - OSPF protocol Basic Settings ........................................................................... 21 9 Fig.155 - OSPF default AREA............................................................................. ............ 219 Fig.156 - OSPF Interfaces assignment, (PPP Radio Interface type pTp, Vlan1 Lan3 Interface type broadcast)................................... ................................................................................ 219 Fig.157 - Routing Table created by OSPF ........................................................................ 219

MN.00329.E - 012

236

237

MN.00329.E - 012

22

LIST OF TABLES

Tab.1 - Artificial respiration ...................................................................................... ........ 4 Tab.2 - Single IF system configurations table ................................................... .................20 Tab.3 - Dual IF system configurations table ...................................................... .................21 Tab.4 - Port configuration 0: Up to 2 independent radio links ............................................... 21 Tab.5 - 1+1 protected radio link......................... ..............................................................2 2 Tab.6 - Dual IF: N+0 RLAG (Physical Radio Link Aggregation) .............................................. 22 Tab.7 - Quad IF: system configurations table .................................................... .................26 Tab.8 - Quad IF: up to 4 independent 1+0 radio links .............................................. ...........26 Tab.9 - Quad IF: 1+1 .......................................................................................... ...........27 Tab.10 -N+0 RLAG (Radio Link Aggregation L1) ............................................. ....................28 Tab.11 - 2+0 RLAG & 1+1 .......................................................................................... .....30 Tab.12 - 2 independent 1+1 ................................................................................. ...........31 Tab.13 - 2 independent 2+0 RLAG (Physical Link Aggregation L1).........................................31 Tab.14 - 1+1 XPIC ........................................................................................ .................32 Tab.15 - Technical characteristics of the AGS-20 Switch ................................................. .....33 Tab.16 - Switch bridge modes.......................................................................................... 34 Tab.17 – Full dynamic memory ............................................................................... .........45 Tab.18 – Priority based memory (1 radio port) ................................................. ..................45 Tab.19 – Priority based memory (2 radio ports)........................................................... .......45 Tab.20 – Uniform memory (1 radio port) ................................................. ..........................45 Tab.21 – Uniform memory (2 radio ports)................................................ ..........................46 Tab.22 – Line ports dynamic memory (2 radio ports) ................................................. .........46 Tab.23 - Optical interface characteristics .......................................................... .................78 Tab.24 - Alarm characteristics .......................................................................................... 81 Tab.25 - Front panel system LEDs ........................................................................... .........81 Tab.26 - Electrical/Optical Ethernet interface status LEDs .................................................... 82 Tab.27 - Meaning of PoE LEDs.................................. ........................................................82 Tab.28 - Net radio throughput in Mbit/s versus channel bandwidth for AGS-20 equipment........84 Tab.29 - ODUs that can be connected to AGS-20 ................................................. ...............88 Tab.30 - Characteristics of the cables.............. ................................................................ 101 Tab.31 ........................................................................................................................103 Tab.32 - 10/100/100 0BaseT, RJ45 ................................................................................. 110 Tab.33 - 8xE1, 50 pin SCSI female 75 Ohm .................................... ................................ 111 Tab.34 - 8xE1, 50 pin SCSI female 120 Ohm) ..................................................... ............. 112 Tab.35 - SYNK-1 interface pinout ................................................................................ ... 113 Tab.36 - ToD interface pinout ........................................................................... ............. 113 Tab.37 - Console connector pinout.......................................................... ........................ 114

MN.00329.E - 012

238

Tab.38 - Alarm connector pinout .................................................................................... 114 Tab.39 - Torques for tightening screws.................................. .......................................... 118 Tab.40 - Torques for tightening screws.................................. .......................................... 137 Tab.41 - Torques for tightening screws.................................. .......................................... 150 Tab.42 - Waveguide bending radius according to frequency ............................................... 154 Tab.43 - Alarm severity list................................................................................... ......... 172 Tab.44 ........................................................................................................................187 Tab.45 ........................................................................................................................192 Tab.46 ........................................................................................................................193 Tab.47 ........................................................................................................................193 Tab.48 ........................................................................................................................194 Tab.49 ........................................................................................................................195 Tab.50 ........................................................................................................................195 Tab.51 ........................................................................................................................196 Tab.52 ........................................................................................................................197 Tab.53 ........................................................................................................................198 Tab.54 ........................................................................................................................198 Tab.55 ........................................................................................................................199 Tab.56 ........................................................................................................................200 Tab.57 - IDU part number .............................................................................. ................ 221 Tab.58 - ODU ASN part number and description .................................................. ............. 222 Tab.59 - ODU ASNK part number and description ................................................ ............. 226

239

MN.00329.E - 012

23

ASSISTANCE SERVICE

For more information, refer to the section relevant to the technical support on the I nternet site of the company manufacturing the product.

SIAE helpdesk mail is: [email protected]

MN.00329.E - 012

240

mn00329e - v12 - AGS20

Recommend Documents