Radwin 2000+ Series Point To Point Broadband Wireless: User Manual

USER
MANUAL
RADWIN 2000+ SERIES POINT TO POINT
BROADBAND WIRELESS
Release 4.2.40
Table of Contents
Part 1: Preliminaries
Chapter 1: About this User Manual
1.1 Manual Structure ................................................................................................................ 1‐1
1.2 Notifications ........................................................................................................................ 1‐2
1.3 Customer Support ............................................................................................................... 1‐2
Chapter 2: Introduction
2.1 Welcome to the RADWIN 2000+ Series .............................................................................. 2‐1
2.2 What’s New in Release 4.2.40............................................................................................. 2‐1
2.3 Key features of the RADWIN 2000+ Series.......................................................................... 2‐2
2.4 Components of a RADWIN 2000+ Series Link ..................................................................... 2‐2
2.4.1 Major Components ..................................................................................................... 2‐2
2.4.2 Accessories ................................................................................................................. 2‐2
2.4.3 Link Management Tools ............................................................................................. 2‐3
Part 2: Basic Installation
Chapter 3: Site Survey
3.1 Scope of this Chapter .......................................................................................................... 3‐1
3.2 Planning the Link Site .......................................................................................................... 3‐1
3.2.1 Overview ..................................................................................................................... 3‐1
3.3 The Site Survey .................................................................................................................... 3‐2
3.3.1 Introduction ................................................................................................................ 3‐2
3.3.2 Recommended Equipment ......................................................................................... 3‐2
3.4 Stage 1: Preliminary Survey................................................................................................. 3‐2
3.5 Stage 2: Physical Survey ...................................................................................................... 3‐3
3.5.1 Additional Outdoor Site Requirements ....................................................................... 3‐4
3.5.2 Additional Indoor Site Requirements .......................................................................... 3‐4
3.6 Stage 3: RF Survey ............................................................................................................... 3‐4
3.7 RF Planning for Dense Installations and Collocated Sites ................................................... 3‐5
Chapter 4: Hardware Installation
4.1 Scope of This Chapter.......................................................................................................... 4‐1
4.2 Safety Practices and Provisions ........................................................................................... 4‐1
4.2.1 Preventing Overexposure to RF Energy ...................................................................... 4‐1
4.2.2 Grounding ................................................................................................................... 4‐1
4.2.3 Protection Against Lightning ...................................................................................... 4‐2
4.2.4 General ....................................................................................................................... 4‐2
4.2.5 Internal ESD Protection circuits .................................................................................. 4‐2
4.3 Kit Contents......................................................................................................................... 4‐3
4.3.1 Radio Units ................................................................................................................. 4‐3
4.3.2 Power over Ethernet (PoE) Devices ............................................................................ 4‐5
4.3.3 IDU‐H/HP aggregation unit ........................................................................................ 4‐6
4.3.4 Antennas .................................................................................................................... 4‐7
4.3.5 Accessories ................................................................................................................. 4‐8
4.4 Tools Required for Installation .......................................................................................... 4‐11
4.4.1 Tools and Materials .................................................................................................. 4‐11
4.4.2 Cables and connectors .............................................................................................. 4‐11
4.5 Unpacking and Checking ................................................................................................... 4‐11
4.6 Site Preparation................................................................................................................. 4‐12
RADWIN 2000+ Series User Manual Release 4.2.40 i
4.7 Mounting Units ................................................................................................................. 4‐12
4.7.1 Mounting an ODU, GSU, or HSS ............................................................................... 4‐12
4.7.2 Mounting an External Antenna ................................................................................ 4‐19
4.7.3 Mounting the IDU‐H/HP and RADWIN 2000i ........................................................... 4‐20
4.8 External Connections ........................................................................................................ 4‐24
4.8.1 Small Form‐Factor (RADWIN 2000 A+) ODU ............................................................ 4‐24
4.8.2 Large Form‐Factor (RADWIN 2000 C+, RADWIN 2000 D+) ....................................... 4‐24
4.8.3 RADWIN 2000i .......................................................................................................... 4‐25
4.8.4 PoE Devices ............................................................................................................... 4‐26
4.8.5 IDU‐H/HP .................................................................................................................. 4‐26
4.8.6 RADWIN GSU ............................................................................................................ 4‐27
4.9 Hardware Setup for Hub Site Synchronization.................................................................. 4‐28
4.9.1 Serial Hub Site Synchronization ................................................................................ 4‐28
4.9.2 Ethernet Hub Site Synchronization ........................................................................... 4‐29
4.9.3 GPS Hub Site Synchronization with an external GSU ................................................ 4‐30
4.9.4 GPS Hub Site Synchronization with an Internal GSU ................................................ 4‐32
4.10 Lightning Protection ........................................................................................................ 4‐32
4.10.1 Lightning Protection for RF Cables ......................................................................... 4‐32
4.10.2 Lightning Protection Unit (LPU) for CAT‐5e Cables ................................................ 4‐33
4.11 Antenna Alignment ......................................................................................................... 4‐39
4.11.1 Antenna Alignment Procedure ............................................................................... 4‐39
Chapter 5: RADWIN Manager
5.2 Installing the RADWIN Manager Application ...................................................................... 5‐1
5.2.1 Minimum System Requirements ................................................................................ 5‐1
5.2.2 Installing the Software ............................................................................................... 5‐2
5.3 Logging On to the RADWIN Manager.................................................................................. 5‐2
5.3.1 Preparation for First Log‐on (check connectivity) ....................................................... 5‐2
5.3.2 First Log‐on ................................................................................................................. 5‐3
5.3.3 Log‐On with Local Connection .................................................................................... 5‐5
5.4 Other Log‐on Options.......................................................................................................... 5‐5
5.5 Log‐on Errors and Cautions ................................................................................................. 5‐8
5.5.1 Unsupported Device ................................................................................................... 5‐8
5.5.2 Incorrect IP Address .................................................................................................... 5‐8
5.5.3 Incorrect Password ..................................................................................................... 5‐9
5.5.4 Invalid Read/Write Community String or SNMPv3 Passwords ................................... 5‐9
5.6 The Initial RADWIN Manager Main Window..................................................................... 5‐10
5.7 Master ODU vs. Slave ODU................................................................................................ 5‐10
5.7.1 Define One Unit as an RT‐A(HBS) ............................................................................. 5‐11
5.8 Setting RADWIN Manager Preferences............................................................................. 5‐14
5.8.1 Preferences: Monitor ................................................................................................ 5‐15
5.8.2 Preferences: Events .................................................................................................. 5‐16
5.8.3 Preferences: Advanced ............................................................................................. 5‐17
Part 3: Link Management
Chapter 6: Initial Link Configuration
6.2 Link Establishment .............................................................................................................. 6‐1
6.2.1 Link Configuration Workflow ...................................................................................... 6‐1
6.2.2 Activating the RT‐A(HBS) ............................................................................................ 6‐2
6.2.3 Registering the RT‐B(HSU) ........................................................................................ 6‐12
6.2.4 Basic Configuration for Operations .......................................................................... 6‐12
6.3 Advanced Link Configuration ............................................................................................ 6‐16
RADWIN 2000+ Series User Manual Release 4.2.40 ii
6.3.1 Air Interface .............................................................................................................. 6‐16
6.3.2 Ethernet .................................................................................................................... 6‐19
6.3.3 Changing the Link Band ............................................................................................ 6‐21
6.3.4 Configuring AES 256 Encryption Support ................................................................. 6‐26
6.4 Configuration with Telnet ................................................................................................. 6‐28
6.4.1 Telnet Access to Either ODU ..................................................................................... 6‐28
Chapter 7: Link Configuration in Detail
7.2 Link Tool Bar........................................................................................................................ 7‐1
7.3 Link Configuration Window................................................................................................. 7‐2
7.4 Configuration Tabs .............................................................................................................. 7‐4
7.4.1 System ........................................................................................................................ 7‐4
7.4.2 Tx & Antenna .............................................................................................................. 7‐4
7.4.3 Hub Site Sync (RT‐A(HBS) Only) .................................................................................. 7‐5
7.4.4 Management .............................................................................................................. 7‐5
7.4.5 Link Configuration Tool Bar ...................................................................................... 7‐27
7.5 Deactivate RT‐A(HBS) ........................................................................................................ 7‐28
7.6 Deregister RT‐B(HSU) ........................................................................................................ 7‐28
7.7 Suspend a Deregistered RT‐B(HSU)................................................................................... 7‐28
7.8 Reset the ODU................................................................................................................... 7‐28
Chapter 8: Monitoring and Diagnostics
8.1 Retrieving Link Information................................................................................................. 8‐1
8.2 Throughput Checking .......................................................................................................... 8‐3
8.3 Recent Events...................................................................................................................... 8‐4
8.4 Performance Monitoring..................................................................................................... 8‐6
8.4.1 Obtaining Reports ...................................................................................................... 8‐6
8.4.2 More on the Thresholds .............................................................................................. 8‐9
8.5 Manager Traps .................................................................................................................. 8‐10
8.6 Active Alarms..................................................................................................................... 8‐11
8.7 Other Diagnostic Aids........................................................................................................ 8‐12
8.7.1 Link Budget Calculator ............................................................................................. 8‐12
8.7.2 Online Help ............................................................................................................... 8‐12
8.7.3 Customer Service ...................................................................................................... 8‐12
Part 4: Site Synchronization
Chapter 9: Hub Site Synchronization
9.2 What is Hub Site Synchronization (HSS)? ............................................................................ 9‐1
9.3 HSS Implementation............................................................................................................ 9‐3
9.3.1 Radio Frame Pattern .................................................................................................. 9‐3
9.3.2 HSS Types ................................................................................................................... 9‐4
Chapter 10: Serial Hub Site Synchronization
10.1 Scope of this Chapter ...................................................................................................... 10‐1
10.2 SHSS Hardware Installation ............................................................................................. 10‐1
10.2.1 Connecting an HSS Unit .......................................................................................... 10‐1
10.2.2 Using a Single HSS Unit .......................................................................................... 10‐3
10.2.3 Using More than One HSS Unit .............................................................................. 10‐4
10.3 ODU/HSS Unit Connection Pinout................................................................................... 10‐5
10.4 Sector Configuration and HSS ......................................................................................... 10‐6
10.5 Sync Status Messages and Color Codes .......................................................................... 10‐7
Chapter 11: Hub Site Synchronization over Ethernet
RADWIN 2000+ Series User Manual Release 4.2.40 iii

11.2 RADWIN Ethernet HSS..................................................................................................... 11‐1
11.2.1 Ethernet HSS Requirements .................................................................................... 11‐1
11.2.2 HSSoE Concepts ...................................................................................................... 11‐2
11.3 Installing Collocated HSSoE ODUs ................................................................................... 11‐4
11.3.1 Ethernet Services Only ............................................................................................ 11‐4
11.3.2 Ethernet and TDM Services .................................................................................... 11‐4
11.4 Link Configuration and HSSoE ......................................................................................... 11‐4
11.4.1 Setup for Illustration ............................................................................................... 11‐4
11.4.2 Configuring the RT‐A(HBS) as an HSS master ......................................................... 11‐4
11.4.3 Configuring the RT‐A(HBS) as an HSS client ........................................................... 11‐9
11.5 Sync Status Messages and Color Codes ........................................................................ 11‐11
Chapter 12: GPS Hub Site Synchronization
12.2 Overview ......................................................................................................................... 12‐1
12.3 GHSS for the RADWIN 2000 A+, RADWIN 2000 C+, or RADWIN 2000 D+ .................... 12‐1
12.3.1 GSU ......................................................................................................................... 12‐2
12.3.2 GSU Kit Contents .................................................................................................... 12‐2
12.3.3 GSU Commissioning and Installation ..................................................................... 12‐3
12.4 GHSS for the RADWIN 2000i ........................................................................................... 12‐8
12.4.1 Overview ................................................................................................................. 12‐8
12.4.2 Transmission Phase Shift ........................................................................................ 12‐9
12.4.3 Configuring GHSS with an Internal GPS Unit ........................................................ 12‐10
Part 5: Advanced Installation Topics
Chapter 13: Software Upgrade
13.2 What is the Software Upgrade Utility? ........................................................................... 13‐1
13.3 Upgrading an Installed Link ............................................................................................. 13‐1
13.4 Bulk Software Backup...................................................................................................... 13‐5
Chapter 14: Software Backup and Restore
14.2 Backup and Restore Facilities.......................................................................................... 14‐1
14.3 Bulk Software Backup...................................................................................................... 14‐1
14.4 Site Backup ...................................................................................................................... 14‐4
Chapter 15: VLAN Functionality
15.2 VLAN Tagging ‐ Overview ................................................................................................ 15‐1
15.2.1 VLAN and Related Terminology .............................................................................. 15‐1
15.2.2 VLAN Background Information on the Web ........................................................... 15‐1
15.3 Requirements .................................................................................................................. 15‐1
15.4 VLAN Tagging .................................................................................................................. 15‐2
15.4.1 QinQ (Double Tagging) for Service Providers ......................................................... 15‐2
15.4.2 VLAN Untagging ..................................................................................................... 15‐2
15.4.3 Port Functionality ................................................................................................... 15‐2
15.5 VLAN Configuration Using the RADWIN Manager .......................................................... 15‐4
15.5.1 Management Traffic and Ethernet Service Separation .......................................... 15‐4
15.5.2 Configuration of VLAN Tagging for Ethernet Service ............................................. 15‐5
Chapter 16: Quality of Service
16.2 Prerequisites ................................................................................................................... 16‐1
16.3 QoS ‐ Overview................................................................................................................ 16‐1
16.4 Setting up the Link for QoS ............................................................................................. 16‐2
RADWIN 2000+ Series User Manual Release 4.2.40 iv
16.4.1 Preparing for QoS ................................................................................................... 16‐2
16.4.2 Assigning Queue Priorities ...................................................................................... 16‐4
Chapter 17: False Radar Mitigation Facilities
17.2 Who needs it ................................................................................................................... 17‐1
17.3 DFS and False Radar Mitigation....................................................................................... 17‐1
17.3.1 About DFS ............................................................................................................... 17‐1
17.3.2 What is False Radar Mitigation .............................................................................. 17‐1
17.4 Configuring False Radar Mitigation ................................................................................. 17‐2
17.5 FCC/IC Requirements ...................................................................................................... 17‐3
Chapter 18: FCC/IC DFS Considerations
18.2 FCC 5.4GHz Device Registration ...................................................................................... 18‐1
18.3 Registering the Device..................................................................................................... 18‐1
18.4 TDWR Table..................................................................................................................... 18‐5
Part 6: Field Installation Topics
Chapter 19: Link Budget Calculator
19.2 Overview ......................................................................................................................... 19‐1
19.2.1 User Input ............................................................................................................... 19‐1
19.2.2 Link Budget Calculator Internal Data ..................................................................... 19‐2
19.3 Calculations ..................................................................................................................... 19‐2
19.3.1 EIRP ........................................................................................................................ 19‐2
19.3.2 Expected RSS and Fade Margin .............................................................................. 19‐2
19.3.3 Min and Max Range ............................................................................................... 19‐2
19.3.4 Service .................................................................................................................... 19‐3
19.3.5 Availability .............................................................................................................. 19‐3
19.3.6 Antenna Height ...................................................................................................... 19‐3
19.4 About the Fresnel Zone ................................................................................................... 19‐4
19.5 Running the Link Budget Calculator ............................................................................... 19‐5
Chapter 20: Spectrum View
20.2 What is Spectrum View ................................................................................................... 20‐1
20.3 Who needs it ................................................................................................................... 20‐1
20.4 Two Ways to Run Spectrum View ................................................................................... 20‐1
20.5 Where is the Spectrum View Data stored ....................................................................... 20‐2
20.6 Spectrum View Main Window......................................................................................... 20‐2
20.7 Spectrum View Display Function Buttons ....................................................................... 20‐4
20.8 Running Spectrum View .................................................................................................. 20‐5
20.9 Zooming in and out ......................................................................................................... 20‐7
Chapter 21: Using the Web Interface
21.2 What is it For ................................................................................................................... 21‐1
21.3 Who Needs it................................................................................................................... 21‐1
21.4 How it Works................................................................................................................... 21‐1
21.5 What it Provides.............................................................................................................. 21‐2
21.6 Prerequisites ................................................................................................................... 21‐2
21.6.1 Hardware ................................................................................................................ 21‐2
21.6.2 Software ................................................................................................................. 21‐2
21.6.3 Technical Background ............................................................................................ 21‐2
21.7 Special Considerations Working with the WI .................................................................. 21‐2
RADWIN 2000+ Series User Manual Release 4.2.40 v
21.7.1 Advanced Configurations ....................................................................................... 21‐2
21.7.2 Operational Effects ................................................................................................. 21‐2
21.7.3 Some Working Tips ................................................................................................. 21‐3
21.8 Logging on ....................................................................................................................... 21‐3
21.9 Site Management ‐ Master ODU ..................................................................................... 21‐4
21.9.1 The Main Window .................................................................................................. 21‐4
21.9.2 The Tool Bar ........................................................................................................... 21‐5
21.9.3 Events ................................................................................................................... 21‐10
21.9.4 Reset ..................................................................................................................... 21‐10
21.10 Site Management ‐ Slave ODU .................................................................................... 21‐10
Part 7: Product Reference
Appendix A: Terminology
Appendix B: RF Exposure
Appendix C: Setting Antenna Parameters
C.1 Antenna Issues .................................................................................................................... C‐1
C.2 About Single and Dual Antennas......................................................................................... C‐1
C.2.1 Dual Antennas at the RT‐A(HBS) and RT‐B(HSU) ........................................................ C‐1
C.2.2 Single Antennas at Both Sites ..................................................................................... C‐2
C.2.3 Single at One Site, Dual Antennas at the Other ......................................................... C‐2
C.3 Considerations for Changing Antenna Parameters............................................................. C‐3
Appendix D: Wiring Specifications
D.1 ODU‐PoE Cable () ................................................................................................................D‐1
D.2 HBS/HSS Unit Connection Pinout........................................................................................D‐2
D.3 User Port Connectors..........................................................................................................D‐3
D.3.1 LAN Port .....................................................................................................................D‐3
D.4 DC Power Terminals............................................................................................................D‐3
D.4.1 DC PoE ........................................................................................................................D‐3
Appendix E: Regional Notice: French Canadian
E.1 Procédures de sécurité........................................................................................................ E‐1
E.1.1 Généralités ................................................................................................................. E‐1
E.1.2 Mise à la terre ............................................................................................................ E‐1
E.1.3 Protection contre la foudre ........................................................................................ E‐1
E.1.4 Précautions de sécurité pendant le montage de ODU ................................................ E‐2
E.1.5 Connecter la terre à IDU‐C .......................................................................................... E‐3
E.2 Installation sur pylône et mur ............................................................................................. E‐3
E.2.1 Contenu du kit de montage ODU ................................................................................ E‐3
E.2.2 Montage sur un pylône .............................................................................................. E‐4
E.2.3 Montage sur un mur ................................................................................................... E‐4
E.2.4 Montage d'une antenne externe ................................................................................ E‐4
E.2.5 Contenu du kit de montage d'une antenne externe ................................................... E‐4
Part 8: Regulatory Notices
RADWIN 2000+ Series User Manual Release 4.2.40 vi
List of Figures
FIGURE 4‐1 GBE POE DEVICE .................................................................................................. 4‐6
FIGURE 4‐2 IDU‐H/HP.......................................................................................................... 4‐6
FIGURE 4‐3 EXTERNAL ANTENNAS FOR USE WITH RADWIN 2000+ SERIES .................................... 4‐7
FIGURE 4‐4 HSS INTERCONNECTION UNIT ................................................................................. 4‐8
FIGURE 4‐5 RADWIN GSU.................................................................................................... 4‐9
FIGURE 4‐6 RADWIN LIGHTNING PROTECTOR........................................................................... 4‐9
FIGURE 4‐7 RADWIN ETHERNET CABLE REPEATER................................................................... 4‐10
FIGURE 4‐8 MOUNTING KIT .................................................................................................. 4‐10
FIGURE 4‐9 MOUNTING KIT CONTENTS ................................................................................... 4‐12
FIGURE 4‐10 CONNECT POLE CLAMP TO RADIO HOLDER ........................................................... 4‐13
FIGURE 4‐11 TIGHTEN BOLTS ................................................................................................ 4‐13
FIGURE 4‐12 ROTATE CLAMP AND TIGHTEN BOLTS .................................................................... 4‐14
FIGURE 4‐13 MOUNTING KIT ON POLE ................................................................................... 4‐14
FIGURE 4‐14 MOUNTING A SMALL FORM‐FACTOR ODU OR GSU (1) .......................................... 4‐15
FIGURE 4‐15 MOUNTING A SMALL FORM‐FACTOR ODU OR GSU (2) .......................................... 4‐15
FIGURE 4‐16 SMALL FORM‐FACTOR ODU OR GSU ON A VERTICAL POLE ...................................... 4‐15
FIGURE 4‐17 MOUNTING A LARGE FORM‐FACTOR ODU (1)....................................................... 4‐16
FIGURE 4‐18 MOUNTING A LARGE FORM‐FACTOR ODU(2)........................................................ 4‐16
FIGURE 4‐19 LARGE FORM‐FACTOR ODU ON A VERTICAL POLE ................................................... 4‐16
FIGURE 4‐20 MOUNTING AN ODU ON A HORIZONTAL POLE ....................................................... 4‐17
FIGURE 4‐21 CONNECT POLE CLAMP TO RADIO HOLDER ........................................................... 4‐17
FIGURE 4‐22 TIGHTEN BOLTS ................................................................................................ 4‐17
FIGURE 4‐23 ROTATE CLAMP AND TIGHTEN BOLTS .................................................................... 4‐18
FIGURE 4‐24 MOUNTING KIT ON THIN POLE ............................................................................ 4‐18
FIGURE 4‐25 MOUNTING A UNIT ON A WALL (1)...................................................................... 4‐18
FIGURE 4‐26 MOUNTING A UNIT ON A WALL (2)...................................................................... 4‐18
FIGURE 4‐27 FLAT PANEL ANTENNA MOUNTING KIT ADAPTER...................................................... 4‐19
FIGURE 4‐28 FLAT PANEL ANTENNA ‐ REAR WITH MOUNTING KIT ADAPTER ................................... 4‐19
FIGURE 4‐29 FLAT PANEL ANTENNA ‐ MOUNTED TO A POLE ....................................................... 4‐20
FIGURE 4‐30 MOUNTING A SINGLE IDU‐H/HP ....................................................................... 4‐21
FIGURE 4‐31 SINGLE IDU‐H/HP MOUNTED IN A 19IN. RACK ..................................................... 4‐21
FIGURE 4‐32 CONNECTING TWO IDU‐H/HP UNITS................................................................... 4‐22
FIGURE 4‐33 TWO IDU‐H/HP UNITS MOUNTED IN A 19IN. RACK ............................................... 4‐22
FIGURE 4‐34 MOUNTING THE RADWIN 2000I ....................................................................... 4‐23
FIGURE 4‐35 RADWIN 2000I MOUNTED IN A 19 IN. RACK ....................................................... 4‐23
FIGURE 4‐36 EXTERNAL CONNECTIONS: RADWIN 2000 A+ ..................................................... 4‐24
FIGURE 4‐37 EXTERNAL CONNECTIONS: RADWIN 2000 C+ AND RADWIN 2000 D+ ................. 4‐25
FIGURE 4‐38 EXTERNAL CONNECTIONS: RADWIN 2000I.......................................................... 4‐25
FIGURE 4‐39 EXTERNAL CONNECTIONS: POE DEVICE ................................................................ 4‐26
FIGURE 4‐40 EXTERNAL CONNECTIONS: IDU‐H/HP.................................................................. 4‐27
FIGURE 4‐41 EXTERNAL CONNECTIONS: RADWIN GSU............................................................ 4‐28
FIGURE 4‐42 CONNECTIONS: SERIAL HSS USING THE HSS UNIT .................................................. 4‐29
FIGURE 4‐43 CONNECTIONS: HSS OVER ETHERNET USING THE IDU‐H/HP ................................... 4‐30
FIGURE 4‐44 CONNECTIONS: HSS VIA GPS USING THE RADWIN GSU ....................................... 4‐31
FIGURE 4‐45 CONNECTIONS: HSS VIA GPS USING AN INTERNAL GPS (FOR THE RADWIN 2000I)... 4‐32
FIGURE 4‐46 GROUNDING AN EXTERNAL ANTENNA .................................................................. 4‐33
RADWIN 2000+ Series User Manual Release 4.2.40 vii

FIGURE 4‐47 BASIC USE OF LIGHTNING PROTECTOR UNITS .......................................................... 4‐35
FIGURE 4‐48 LPU: BOTTOM VIEW......................................................................................... 4‐35
FIGURE 4‐49 LPU: SIDE VIEW............................................................................................... 4‐35
FIGURE 4‐50 LPU ATTACHED TO POLE WITH METAL TIE ............................................................. 4‐36
FIGURE 4‐51 CONNECTING CABLES TO THE LPU (1).................................................................. 4‐36
FIGURE 4‐52 CONNECTING CABLES TO THE LPU (2).................................................................. 4‐36
FIGURE 4‐53 INSTALLING AN LPU ON A POLE (SIDE VIEW).......................................................... 4‐37
FIGURE 4‐54 INSTALLING AN LPU ON A WALL .......................................................................... 4‐38
FIGURE 4‐55 EXPOSING THE TACKY SIDE OF THE SEALING TAPE .................................................... 4‐38
FIGURE 4‐56 WATERPROOFING AN EXTERNAL CONNECTION ........................................................ 4‐39
FIGURE 4‐57 BEEP SEQUENCE FOR ANTENNA ALIGNMENT .......................................................... 4‐40
FIGURE 5‐1 PINGING THE BASE STATION.................................................................................... 5‐3
FIGURE 5‐2 LOG‐ON WINDOW ‐ DEFAULT .................................................................................. 5‐4
FIGURE 5‐3 LOG‐ON WINDOW USING AN IP ADDRESS .................................................................. 5‐4
FIGURE 5‐4 EXTENDED LOG‐ON WINDOW .................................................................................. 5‐6
FIGURE 5‐5 LOG ON WINDOW EXPOSING THE USER TYPES............................................................. 5‐6
FIGURE 5‐6 LOG‐ON WINDOW WITH SNMPV3 .......................................................................... 5‐7
FIGURE 5‐7 UNSUPPORTED DEVICE MESSAGE ............................................................................. 5‐8
FIGURE 5‐8 UNREACHABLE DEVICE MESSAGE .............................................................................. 5‐8
FIGURE 5‐9 INVALID USER TYPE OR PASSWORD ........................................................................... 5‐9
FIGURE 5‐10 MAIN WINDOW PRIOR TO LINK CONFIGURATION .................................................... 5‐10
FIGURE 5‐11 MONITOR PREFERENCES .................................................................................... 5‐15
FIGURE 5‐12 ADVANCED PREFERENCES ................................................................................... 5‐17
FIGURE 5‐13 RSS EXTENDED VIEW ENABLED............................................................................ 5‐18
FIGURE 5‐14 RSS EXTENDED VIEW DISABLED ........................................................................... 5‐18
FIGURE 5‐15 TX/RX EXTENDED VIEW ENABLED ........................................................................ 5‐18
FIGURE 5‐16 TX/RX EXTENDED VIEW DISABLED ....................................................................... 5‐18
FIGURE 6‐1 MAIN WINDOW PRIOR TO LINK CONFIGURATION ........................................................ 6‐2
FIGURE 6‐2 MAIN WINDOW: RT‐A(HBS) ACTIVATED, RT‐B(HSU) READY FOR REGISTRATION.......... 6‐11
FIGURE 6‐3 MAIN WINDOW: LINK MASTER ODU ACTIVATED, SLAVE ODU REGISTERED .................. 6‐12
FIGURE 6‐4 MAIN WINDOW: LINK FULLY OPERATIONAL.............................................................. 6‐15
FIGURE 6‐5 LINK AIR INTERFACE PARAMETERS ‐ NO ACS ........................................................... 6‐16
FIGURE 6‐6 LINK AIR INTERFACE PARAMETERS ‐ ACS ENABLED ................................................... 6‐17
FIGURE 6‐7 LINK AIR INTERFACE PARAMETERS ‐ DBS ENABLED, ACS ON BY DEFAULT ..................... 6‐18
FIGURE 6‐8 RT‐A(HBS) COLLOCATED CLIENT OR INDEPENDENT UNIT ........................................... 6‐20
FIGURE 6‐9 RT‐A(HBS) CO‐LOCATED MASTER ......................................................................... 6‐20
FIGURE 6‐10 CHANGE OR ADD BANDS.................................................................................... 6‐21
FIGURE 6‐11 ADD/CHANGE BAND DIALOG .............................................................................. 6‐22
FIGURE 6‐12 ADD BANDS INSTRUCTIONS PANEL....................................................................... 6‐24
FIGURE 6‐13 USING THE MASTER ODU (HBS) CONFIGURATION BUTTON FOR LICENSING................ 6‐26
FIGURE 6‐14 TELNET SESSION LOG ON TO THE RT‐A(HBS) ........................................................ 6‐28
FIGURE 7‐1 LINK TOOL BARS ................................................................................................... 7‐1
FIGURE 7‐2 LINK CONFIGURATION WINDOW ‐ RT‐A(HBS)........................................................... 7‐2
FIGURE 7‐3 LINK CONFIGURATION WINDOW ‐ RT‐B(HSU) .......................................................... 7‐3
FIGURE 7‐4 VLAN FOR MANAGEMENT ..................................................................................... 7‐9
FIGURE 7‐5 SUPPORTED PROTOCOLS ....................................................................................... 7‐10
FIGURE 7‐6 ADD OR EDIT A USER ........................................................................................... 7‐13
FIGURE 7‐7 SNMPV3 USERS LIST .......................................................................................... 7‐14
FIGURE 7‐8 DEFAULT SNMP LOG‐ON DIALOG .......................................................................... 7‐16
FIGURE 7‐9 SECTOR SECURITY SETTINGS ‐ RT‐A(HBS) .............................................................. 7‐19
RADWIN 2000+ Series User Manual Release 4.2.40 viii

FIGURE 7‐10 CHANGE LINK PASSWORD DIALOG BOX ................................................................. 7‐20
FIGURE 7‐11 LOST OR FORGOTTEN LINK PASSWORD RECOVERY ................................................... 7‐20
FIGURE 7‐12 CHANGING THE COMMUNITY STRINGS/PASSWORDS ............................................... 7‐22
FIGURE 7‐13 ALTERNATIVE COMMUNITY DIALOG BOX ............................................................... 7‐23
FIGURE 7‐14 DATE AND TIME CONFIGURATION ........................................................................ 7‐24
FIGURE 7‐15 CHANGE DATE AND TIME ................................................................................... 7‐24
FIGURE 7‐16 SETTING ETHERNET SERVICES .............................................................................. 7‐25
FIGURE 7‐17 RESTORE FACTORY SETTINGS, LICENSE ACTIVATION AND CHANGE ODU MODE ........... 7‐26
FIGURE 8‐1 GET DIAGNOSTICS WINDOW ................................................................................... 8‐2
FIGURE 8‐2 SETTING THE UPPER TRAFFIC THRESHOLD ‐ DOWNLINK ................................................ 8‐7
FIGURE 8‐3 DOWNLINK ‐ PERFORMANCE MONITORING REPORT ‐ VALID DATA ................................. 8‐8
FIGURE 8‐4 PERFORMANCE MONITORING REPORT ‐ SHOWING INVALID DATA .................................. 8‐9
FIGURE 9‐1 INTERFERENCE CAUSED BY COLLOCATED UNITS ........................................................... 9‐2
FIGURE 9‐2 COLLOCATED UNITS USING HUB SITE SYNCHRONIZATION (1) ........................................ 9‐2
FIGURE 9‐3 COLLOCATED UNITS USING HUB SITE SYNCHRONIZATION (2) ........................................ 9‐3
FIGURE 9‐4 RADIO FRAME PATTERN ......................................................................................... 9‐3
FIGURE 10‐1 HSS INTERCONNECTION UNIT ............................................................................. 10‐2
FIGURE 10‐2 HSS WIRING SCHEMATIC ................................................................................... 10‐3
FIGURE 10‐3 HSS SYNC SIGNAL PATH WITH ODU 1 AS HSS MASTER .......................................... 10‐3
FIGURE 10‐4 CASCADING TWO HSS UNITS .............................................................................. 10‐4
FIGURE 10‐5 CASCADING THREE HSS UNITS ............................................................................ 10‐5
FIGURE 10‐6 HSS SETTINGS WINDOW .................................................................................... 10‐6
FIGURE 10‐7 SETTING RT‐A(HBS) AS HUB SYNC MASTER OR HUB SYNC CLIENT ........................... 10‐7
FIGURE 10‐8 RT‐A(HBS) AS HUB SITE MASTER ...................................................................... 10‐7
FIGURE 11‐1 HSS SETTINGS WINDOW .................................................................................... 11‐5
FIGURE 11‐2 EXTENDED PROTOCOL PARAMETERS FOR HSSOE ................................................... 11‐6
FIGURE 11‐3 HSS DISCOVERY FILTERS ..................................................................................... 11‐6
FIGURE 11‐4 CONFIGURATION FOR HSS MASTER ...................................................................... 11‐8
FIGURE 12‐1 GENERAL GSU CONFIGURATION USING BOTH ETHERNET AND AN HSS UNIT ................ 12‐2
FIGURE 12‐2 GSU MAIN WIDOW AT STARTUP ......................................................................... 12‐4
FIGURE 12‐3 GPS STATUS UNDER NORMAL USE ....................................................................... 12‐4
FIGURE 12‐4 GSU CONFIGURATION WINDOW ......................................................................... 12‐5
FIGURE 12‐5 GHSS WITH MULTIPLE SITES ............................................................................... 12‐8
FIGURE 12‐6 HSS SETTINGS WINDOW ‐ GHSS ...................................................................... 12‐10
FIGURE 12‐7 GPS STATUS UNDER NORMAL USE ..................................................................... 12‐13
FIGURE 13‐1 SOFTWARE UPGRADE UTILITY ‐ MAIN WINDOW ..................................................... 13‐2
FIGURE 13‐2 ADD / REMOVE SITE BUTTONS ............................................................................ 13‐2
FIGURE 13‐3 ADDING A SINGLE SITE FOR UPGRADE ................................................................... 13‐3
FIGURE 13‐4 SOFTWARE UPGRADE IN PROGRESS ‐ NOTE THE STOP BUTTON .................................. 13‐5
FIGURE 13‐5 SOFTWARE UPGRADE COMPLETED SUCCESSFULLY .................................................... 13‐5
FIGURE 14‐1 BULK BACKUP SETUP WINDOW............................................................................ 14‐2
FIGURE 14‐2 ADD / REMOVE SITE BUTTONS ............................................................................ 14‐2
FIGURE 14‐3 ADDING A SINGLE SITE FOR BACKUP ..................................................................... 14‐3
FIGURE 16‐1 QOS CONFIGURATION WINDOW .......................................................................... 16‐2
FIGURE 16‐2 THE FOUR QOS DATA QUEUES ............................................................................ 16‐4
FIGURE 17‐1 FALSE RADAR MITIGATION ................................................................................. 17‐3
FIGURE 19‐1 FRESNEL ZONE .................................................................................................. 19‐4
FIGURE 19‐2 LINK BUDGET WINDOW ‐ STARTUP ....................................................................... 19‐5
FIGURE 19‐3 RADWIN 2000+ SERIES LBC MAIN WINDOW ..................................................... 19‐6
FIGURE 19‐4 BAND SELECTOR ............................................................................................... 19‐7
RADWIN 2000+ Series User Manual Release 4.2.40 ix
FIGURE 19‐5 CALCULATION OF DISTANCE FROM SITE COORDINATES............................................. 19‐8
FIGURE 19‐6 CLIMACTIC C FACTORS ....................................................................................... 19‐9
FIGURE 19‐7 CLIMACTIC C FACTOR DESCRIPTION .................................................................... 19‐10
FIGURE 19‐8 WORLD MAP SHOWING C FACTOR CONTOURS ..................................................... 19‐10
FIGURE 19‐9 LBC ‐ RESULTS SECTION ................................................................................... 19‐11
FIGURE 20‐1 SPECTRUM VIEW ANALYSIS COLOR CODES ............................................................. 20‐6
FIGURE 21‐1 WEB INTERFACE ‐ LOG ON.................................................................................. 21‐3
FIGURE 21‐2 WEB INTERFACE ‐ MAIN WINDOW ....................................................................... 21‐4
FIGURE 21‐3 LINK STATUS PANEL ........................................................................................... 21‐5
FIGURE E‐1 CONTENU DU KIT DE MONTAGE ODU....................................................................... E‐3
FIGURE E‐2 MONTAGE SUR UN PYLÔNE (1) ............................................................................... E‐4
FIGURE E‐3 MONTAGE SUR UN PYLÔNE (2) ............................................................................... E‐4
FIGURE E‐4 MONTAGE SUR UN MUR (1) ................................................................................... E‐4
FIGURE E‐5 MONTAGE SUR UN MUR (2) ................................................................................... E‐4
RADWIN 2000+ Series User Manual Release 4.2.40 x
List of Tables
TABLE 1‐1 USER MANUAL ‐ GENERAL LAYOUT .......................................................................... 1‐1
TABLE 2‐1 RADWIN 2000+ SERIES MODEL COMPARISONS ....................................................... 2‐1
TABLE 4‐1 RADIO UNITS ‐ SMALL FORM FACTORS ..................................................................... 4‐4
TABLE 4‐2 RADIO UNITS ‐ LARGE FORM FACTORS...................................................................... 4‐5
TABLE 4‐3 LPU KIT CONTENTS ............................................................................................. 4‐33
TABLE 5‐1 PC REQUIREMENTS FOR THE RADWIN MANAGER APPLICATION................................... 5‐1
TABLE 5‐2 USER TYPES, DEFAULT PASSWORDS AND FUNCTION...................................................... 5‐7
TABLE 6‐1 AES INDICATORS FOR A LINK ................................................................................. 6‐27
TABLE 6‐2 ODU TELNET ‐ DISPLAY COMMANDS ..................................................................... 6‐28
TABLE 6‐3 ODU TELNET ‐ SET IMMEDIATE COMMANDS ........................................................... 6‐29
TABLE 6‐4 ODU TELNET ‐ SET COMMANDS REQUIRING RESET ................................................... 6‐30
TABLE 7‐1 LINK BUTTONS ‐ DESCRIPTION ................................................................................. 7‐1
TABLE 7‐2 SNMPV3 PREDEFINED USERS ................................................................................ 7‐13
TABLE 8‐1 GET DIAGNOSTICS DATA AND DESCRIPTION ............................................................... 8‐1
TABLE 8‐2 PERFORMANCE MONITORING FIELDS ........................................................................ 8‐8
TABLE 8‐3 RADWIN MANAGER TRAP MESSAGES ................................................................... 8‐10
TABLE 10‐1 EXTERNAL PULSE STATUS .................................................................................... 10‐8
TABLE 11‐1 EXTERNAL PULSE STATUS .................................................................................. 11‐11
TABLE 15‐1 PORT SETTINGS ‐ INGRESS DIRECTION .................................................................... 15‐3
TABLE 15‐2 PORT SETTINGS ‐ EGRESS DIRECTION ..................................................................... 15‐4
TABLE 15‐3 FURTHER VLAN CONFIGURATION OPTIONS AND RESULTS BY TAG MODE ..................... 15‐7
TABLE 16‐1 DEFAULT PRIORITIES AN D ALLOCATION BY VLAN ID AND DIFFSERV ........................... 16‐1
TABLE 18‐1 LATITUDE AND LONGITUDE LOCATIONS OF TDWRS ................................................. 18‐5
TABLE 20‐1 SPECTRUM VIEW ANALYSIS DISPLAY BUTTONS FUNCTIONALITY .................................. 20‐5
TABLE A‐1 TERMINOLOGY ......................................................................................................A‐1
TABLE B‐1 SAFETY DISTANCES FOR THE RADWIN 2000 A+ AND RADWIN 2000 C+ ...................B‐1
TABLE B‐2 SAFETY DISTANCES FOR THE RADWIN 2000 D+ AND RADWIN 2000I........................B‐2
TABLE B‐3 SAFETY DISTANCES FOR RADWIN 2000+ SERIES ETSI PRODUCTS ...............................B‐2
TABLE D‐1 ODU‐POE RJ‐45 CONNECTOR PINOUT....................................................................D‐1
TABLE D‐2 LAN‐GBE POE RJ‐45 CONNECTOR PINOUT..............................................................D‐1
TABLE D‐3 HBS/HSS UNIT CONNECTION PINOUT .....................................................................D‐2
TABLE D‐4 FAST ETHERNET CONNECTOR PINOUT .......................................................................D‐3
TABLE D‐5 TERMINAL BLOCK 2‐PIN ‐48VDC ............................................................................D‐3
RADWIN 2000+ Series User Manual Release 4.2.40 xi
Part 1: Preliminaries
Release 4.2.40
Chapter 1: About this User
Manual
1.1 Manual Structure
This User Manual is divided into seven functionally distinct sections reflecting the activities
required to set up a RADWIN 2000+ Series link. The division is shown in the following table:
Table 1‐1: User Manual ‐ General layout
Section General Content Purpose
About this manual, Introduction to the RADWIN 2000+
1 Preliminaries
Series of radio products.
• Information to physically install a link: Site prepara‐
tion and hardware Installation
2 Basic Installation
• Understanding the RADWIN Manager on a basic
level
• Setting up and configuring a link
3 Link Management
• Monitoring and diagnostics
Intra‐site with Hub Site Synchronization, including the
4 Site Synchronization
various methods of implementing HSS.
Advanced Software upgrade, backup and restore, VLAN, QoS, Radar
5
Installation Topics mitigation and avoidance, DFS
Field Installation
6 Link Budget Calculator, Spectrum View, Web interface
Topics
Terminology, RF Exposure, Setting antenna parameters,
7 Product Reference
various wiring specifications
8 Regulatory Notices Various regulatory notices
RADWIN 2000+ Series User Manual Release 4.2.40 1‐1

Notifications
1.2 Notifications
Notifications consist of Warnings, Cautions and Notes.
Warning: risk of danger to persons.
Caution: risk of damage to equipment or of service degradation
• Provide additional background
• Offer a recommendation
• Remind you of something that should be kept in mind
1.3 Customer Support
For additional information, please contact the RADWIN distributor nearest to you or one of
RADWIN's offices worldwide.

Chapter 2: Introduction
2.1 Welcome to the RADWIN 2000+ Series
RADWIN 2000+ Series delivers up to 750 Mbps (depending on the specific model) in a point‐
to‐point link, and is the ideal choice for last mile enterprise connectivity and high‐end
applications that demand assured performance with guaranteed link bandwidth.
The RADWIN 2000+ Series has several models, each offering different characteristics. The
main differences are shown below. Other differences are noted throughout this publication.
Table 2‐1: RADWIN 2000+ Series Model Comparisons
Hub Site AES 256
Model Name Max Throughput Form Factor
Synchronization Support
Ethernet,
RADWIN 2000 A+ 25 Mbps Small No
External GPS
Serial, Ethernet,
RADWIN 2000 C+ 250 Mbps Large Yes
External GPS
Serial, Ethernet,
RADWIN 2000 D+ 750 Mbps Large No
External GPS
Ethernet,
RADWIN 2000i 750 Mbps Indoor No
Internal GPS
Some options and models may not be available for your regulatory environment.
2.2 What’s New in Release 4.2.40
Maximum range extended (value depends on specific installation configuration).

Key features of the RADWIN 2000+ Series
This release presents the complete RADWIN 2000+ Series in one publication.
Feature 4.2.40 adds RADWIN’s new radio unit: The all‐indoor RADWIN 2000i.
2.3 Key features of the RADWIN 2000+ Series
» Ethernet connectivity
» Advanced OFDM & MIMO 2x2 for nLOS performance
» Enhanced interference mitigation capability
» Inter & intra site sync to reduce self interference
» Regulations supported ‐ FCC/IC/ETSI/WPC/MII/Universal
» Simple to deploy
» Web Interface for link management
» Fully integrated with RADWIN’s family of solutions:
• Master ODU of RADWIN 2000+ Series can co‐exist with other Master ODUs, as well
as with base stations of all other RADWIN products
• Common RADWIN Manager
• Common RNMS
» Separate uplink and downlink configurable Maximum Information Rate (MIR)
2.4 Components of a RADWIN 2000+ Series
Link
2.4.1 Major Components
The major element of each site is the radio transceiver.
For the RADWIN 2000 A+, RADWIN 2000 C+, and RADWIN 2000 D+, the radio unit is
connected to a PoE device. The PoE provides an Ethernet LAN connection to user equipment
(typically a switch).
For the RADWIN 2000i, the radio unit has separate power and Ethernet LAN connections.
2.4.2 Accessories
To build a 2000+ link you will require some of the following accessories:
• PoE devices ‐ Both Gigabit and 100 Mbps (not relevant for the RADWIN 2000i)
• HSS unit ‐ Collocation unit for intra‐site synchronization (not relevant for the RADWIN
2000i)
• IDU‐H/HP Aggregation unit for a collocated hub site instead of multiple PoE devices
• GSU for inter‐site synchronization (not relevant for the RADWIN 2000i)

Link Management Tools
• Antennas ‐ A wide variety of directional and link antennas is available
• ODU and antenna mounting kits
• Lightning protector for use with all RADWIN outdoor products
• Ethernet repeater ‐ enables you to extend non‐GbE PoE ‐ ODU cables beyond the 100m
limit
• CAT 5e cables of various lengths specifically for use with RADWIN radios and PoE
devices
• Grounding cables
2.4.3 Link Management Tools
RADWIN Manager
The RADWIN Manager is an SNMP‐based management application which manages a
complete link over a single IP address.
The intuitive, easy‐to‐use RADWIN Manager has a rich graphical user interface.
The Web Interface enables you to carry out basic link management functions using a Web
browser. It is an easy way to rapidly configure and setup a link.
It may be used to ‐
• Establish a link on a minimal basis
• Check link parameters and make basic changes
• View the link Inventory
• Inspect the Recent Events logs
Full details are supplied in Using the Web Interface.
RADWIN Network Management System (RNMS)
The RADWIN Network Management System enables Service Providers to manage all RADWIN
links in their network from a Network Operations Center (NOC).
Using the RNMS, Service Providers can configure and monitor up to 10,000 RADWIN links1.
The intuitive easy‐to‐use RNMS provides a full range of network surveillance, monitoring,
configuration and fault management capabilities. It offers users complete visibility and
control over their RADWIN‐based networks.
1. Depending on license type

Part 2: Basic Installation
Release 4.2.40
Chapter 3: Site Survey
3.1 Scope of this Chapter
This chapter presents some general guidelines about conducting a site survey, which is a plan
of what radio units to place where and in what configuration.
3.2 Planning the Link Site
Similar models only can work opposite each other (that is, RADWIN 2000 A+ vs.
RADWIN 2000 A+, RADWIN 2000 C+ vs. RADWIN 2000 C+, RADWIN 2000 D+ vs.
RADWIN 2000 D+ and RADWIN 2000i vs. RADWIN 2000i), even though their
maximum throughput might be the same.
3.2.1 Overview
Link site planning consists of a set of surveys, which must be carried out before any
equipment is brought to the site. If for some reason, the outcome of any of these surveys is
negative, site re‐location will need to be considered.
A Site Survey consists of three stages:
1. Preliminary survey ‐ The proposed link is analyzed in the office using a topographic map.
2. Physical survey ‐ The locations of the indoor and outdoor equipment are determined on‐
site.
3. Radio Frequency (RF) survey ‐ It is recommended that the installation area be scanned
with a spectrum analyzer, to identify RF interference so as to determine a clear channel for
radio installation (on‐site).

The Site Survey
3.3 The Site Survey
3.3.1 Introduction
RADWIN wireless links must be planned before installation. The designated installation site
must be appraised to determine that the wireless system is able to operate efficiently and
provide connectivity without signal degradation.
RADWIN 2000+ Series offers a wide operating frequency range. A free frequency channel
must be determined within the operating range, for optimum performance.
3.3.2 Recommended Equipment
Stage 1: Preliminary Survey
• Topological map of the area
• Urban map of the area
• Compass
Stage 2: Physical Survey
• 100 meter tape measure
• Ohmmeter, to check ground connection
• Binoculars
• Map
• Digital camera
• Paper, pencil, and a clipboard
• GPS device (optional)
• Compass (optional)
Stage 3: RF Survey
• Spectrum Analyzer with Max Hold function and screen capture facility that can store
multiple images, for documentation purposes
• RF accessories (connectors and cables)
• Communication devices (for example, cellular phones, or a set of walkie‐talkies)
3.4 Stage 1: Preliminary Survey
Before visiting potential installation sites, as much detail as possible should be obtained
about the two designated radio installation sites and the area between them.
 To perform a preliminary survey:
1. Mark the two designated installation sites on a topographic map of the area.
2. Measure the distance between the sites; check that it is within the specified range
of the equipment.

Stage 2: Physical Survey
3. On the urban map, check for developed areas situated between the two installation
sites. Pay attention to these areas when performing the physical site survey; there
may be tall buildings, RF towers, or transmitters, which could cause interference to
the link.
4. Check the area between the two sites for obstructions such as:
• High ground ‐ hills or mountains
• Lakes or large bodies of water. Water has a reflection effect on RF signals like a building.
This type of reflection causes the received amplitude to be reduced. As a rule of thumb,
the presence of a large body of water between the link sites may double the required
antenna height.
5. Determine and record the compass bearings between both radio units, relative to
north.
6. If there are obstructions between the two sites, calculate the Fresnel Zone (see Link
Budget Calculator for details).
7. If the site chosen does not meet requirements, consider alternative sites.
8. Use the Link Budget Calculator (on the CD supplied with the equipment or using the
RADWIN Manager) to determine the expected performance.
3.5 Stage 2: Physical Survey
During this stage, you review the environment of the proposed installation location, to ensure
that the link sites are suitable for the wireless network. The results of the physical site survey
should be recorded.
When we mention “ODU”, we mean an outdoor radio unit, or its antenna. If you
are working with the RADWIN 2000i, which is an indoor unit and requires an
external antenna, replace the term “ODU” with “the radio unit’s antenna”.
 To perform a physical survey:
1. From the compass readings taken in the preliminary survey, find the azimuth (hori‐
zontal position) that the first ODU should face towards the second ODU.
2. Using binoculars, locate any obstructions such as tall trees, high buildings, hills or
mountains. Look for other RF towers between the two sites. Mark the locations of
the obstructions on the map.
3. Determine the location for the ODU (having regard for existing rooftop installations
and tower space). It should be above any obstructions, considering the Fresnel zone
(see Link Budget Calculator).
4. If you need to install the radio’s antenna on a tower, make sure that the tower is far
away from overhead electric power lines.

Additional Outdoor Site Requirements
5. Determine a location for the indoor equipment; it should be as close as possible to
the antenna. At an existing site, there is probably an equipment room with cable‐
routing channels.
The IDU ‐ radio cable length limit is 100m, in accordance with 10/100BaseT
interface.
6. Measure and record the path length of the cable from the ODU position to the
indoor equipment room.
7. Determine the ground and lightning connection points of the installation. The ODU
and IDU must both be grounded.
8. Using the Ohmmeter, measure and record the resistance of the required installation
to the grounding point. The resistance must be less than 1O ohm.
9. Review the results of the physical site survey. Decide if the site is suitable for the
wireless network installation.
• If the site is suitable, continue with stage 3, the RF survey
• If the site is not suitable, survey another site
3.5.1 Additional Outdoor Site Requirements
The ambient outdoor operating temperature should be ‐35 to 60C (‐31 to 140F).
3.5.2 Additional Indoor Site Requirements
The following requirements guarantee proper operation of the system:
• For IDU‐C/IDU‐H/HP and RADWIN 2000i units, allow at least 90 cm (36 “) of front clear‐
ance for operating and maintenance accessibility. Allow at least 10 cm (4 “) clearance at
the rear of the unit for signal lines and interface cables
• The ambient operating temperature should be 0 to 50°C (32 to 122 °F) at a humidity of
up to 90%, non condensing
3.6 Stage 3: RF Survey
At this stage, you must examine the wireless environment of the installation site, to
determine whether there are available channels within the radio operating frequency band.
An RF survey is performed using a spectrum analyzer.
Familiarize yourself with the spectrum analyzer before going out on site, specifically the Max
Hold and Marker functions.
Perform the RF survey at both proposed link sites.

RF Planning for Dense Installations and Collocated Sites
Carry out during a busy time of day, to best judge the worst‐case radio interference. Allow 2‐4
hours duration for a good RF survey.
It is possible to install the link and use the RADWIN Manager to find a clear
channel. Each frequency channel can be evaluated in turn. Achievement of
a clear channel is indicated by the marker in the Quality bar on the
Channel Setting window (see Figure 6‐4) moving into the green area.
3.7 RF Planning for Dense Installations and
Collocated Sites
Interference may arise from:
• Collocated RADWIN radios
• Other collocated radio devices installed on the same site
To avoid or minimize interference, follow these recommendations:
• For collocated RADWIN units, implement Hub Site Synchronization (HSS). This synchro‐
nizes the transmission/reception times of the collocated radio unit.
• If one or more collocated units are not RADWIN units, ensure that there is a physical
separation of at least three meters between a RADWIN unit and any other collocated
radio on the site.
• Use the largest possible frequency gap between these units.
• Choose the best frequency channel (as clear as possible form interference). You may
have to use the Change Band facility available for all RADWIN 2000+ Series products.
• To select a frequency channel, move the link to Installation Mode (using Site configura‐
tion) and start the Installation wizard. In the Channel Settings window, use the quality
bar at the bottom to help you choose a better channel (clearer of interference).
• Use the Spectrum View tool to find the best working channel (Tools | Spectrum View).
• Decreasing the Tx Power of a link will reduce collocation interference (Site Configura‐
tion | Air Interface).
Use the Link Budget Calculator to determine the minimum Tx Power
required to maintain link stability.

Chapter 4: Hardware
Installation
4.1 Scope of This Chapter
This chapter covers the procedures for the hardware installation and alignment of a RADWIN
2000+ Series sector in accordance with prior planning. (See Site Survey.) It is intended to
assist qualified field technicians.
4.2 Safety Practices and Provisions
4.2.1 Preventing Overexposure to RF Energy
To protect against overexposure to RF energy, install the antennas of the units so as to
provide and maintain minimal separation distances from all persons.
When the system is operational, avoid standing directly in front of the antenna. Strong RF
fields are present when the transmitter is on. The ODU must not be deployed in a location
where it is possible for people to stand or walk inadvertently in front of the antenna.
4.2.2 Grounding
All RADWIN products should be grounded during operation. In addition:
• All ODUs should be grounded by a wire with diameter of at least 10 AWG.
RADWIN 2000+ Series ODUs must be properly grounded to protect against lightning. It
is the user's responsibility to install the equipment in accordance with Section 810 of
the National Electric Code, ANSI/NFPA No.70‐1984 or Section 54 of the Canadian
Electrical Code. These codes describe correct installation procedures for grounding
outdoor units, masts, lead‐in wiring and discharge units. It also lays down the size of
grounding conductors and connection requirements for grounding electrodes. RADWIN
2000+ Series ODUs must be grounded to a Protective Ground in accordance with the
Local Electrical Regulations. The RG‐45 connector must be connected to the ground
shield of the CAT‐5e cable.

Protection Against Lightning
• The ground lug on an IDU‐H/HP should be connected to the protective ground at all
times, by a wire with a diameter of 18 AWG or wider. Rack‐mounted equipment should
be mounted only in grounded racks and cabinets.
Further, you should ‐
• Always make the ground connection first and disconnect it last
• Never connect telecommunication cables to ungrounded equipment
• Ensure that all other cables are disconnected before disconnecting the ground
4.2.3 Protection Against Lightning
The use of lightning protection is dependent on regulatory and end user requirements. All of
RADWIN outdoor units are designed with surge limiting circuits to minimize the risk of
damage due to lightning strikes. For CAT‐5E cables, RADWIN recommends the use of the LPU
(Lightning Protection Unit). For RF cables, RADWIN recommends the use of additional surge
arrestor devices to protect the equipment from nearby lightning strikes.
4.2.4 General
• It is recommended that installation of outdoor units be contracted to a professional
installer
• Before working on equipment connected to power lines or telecommunication lines,
remove jewelry or any other metallic object that may come into contact with energized
parts
• Use extreme care when installing antennas near power lines
• Use extreme care when working at heights
• When using an AC power source for RADWIN devices, always use the AC power adapter
supplied by RADWIN
• Use the right tools!
• Do not mount an ODU upside down or horizontally. Doing this may void you product
warranty.
4.2.5 Internal ESD Protection circuits
RADWIN equipment is designed to meet the ETSI/FCC/Aus/NZ/CSA EMC and Safety
requirements. To fulfill these requirements, the system's Telecom lines at the ODU/PoE are
Transformer‐isolated and include internal ESD (Electro‐Static‐Discharge) Protection circuits.

Kit Contents
4.3 Kit Contents
The specific contents of your order depends on your specific order. We describe here typical
contents.
4.3.1 Radio Units
Radio units can come in different form factors (sizes), depending on the specific model. This
section describes the various models.
For each radio unit, a self‐adhesive label with the MAC address and alternative Community
string. Keep these labels in a safe place for future reference.
• Radios that work with an external antenna have 2xN‐type connectors for connecting an
external antenna. Relevant for all models.
• Radios that have an integrated flat panel antenna contain both the radio and the
antenna as a single unit housed in a weatherproof (IP67) case. Relevant for the RADWIN
2000 A+, RADWIN 2000 C+, and RADWIN 2000 D+.

Radio Units
RADWIN 2000 A+
The RADWIN 2000 A+ has a small form factor, as shown below. The radio unit can have an
integrated antenna (small or large), or be connectorized for an external antenna:
Front View Rear View
Connectorized
Integrated
Antenna:
small
Integrated
Antenna:
large
Table 4‐1: Radio Units ‐ Small Form Factors

Power over Ethernet (PoE) Devices
RADWIN 2000 C+ and RADWIN 2000 D+
The RADWIN 2000 C+ and RADWIN 2000 D+ are constructed in a large form factor. This form
factor can have an integrated antenna, or be connectorized for an external antenna. Both
versions are shown below:
Connectorized
Integrated
Antenna
Table 4‐2: Radio Units ‐ Large Form Factors
RADWIN 2000i
The RADWIN 2000i is an indoor unit, as shown below. It uses external antennas only:
4.3.2 Power over Ethernet (PoE) Devices
RADWIN’s Gigabit Power over Ethernet (GbE PoE) device provides data and power to 2000+
outdoor units. The PoE device is available with a variety of AC cables with different plug types.
The unit comes with a VAC cable. Both the cable length and plug are region dependent.

IDU‐H/HP aggregation unit
Figure 4‐1: GbE PoE device
PoE devices are not used for the RADWIN 2000i.
4.3.3 IDU‐H/HP aggregation unit
The IDU‐H/HP provides aggregation for multiple RADWIN radios at a hub site. It supports all
RADWIN radios. It features ‐
• 6 PoE ports (PoE legacy mode / RADWIN PoE), up to 35W per PoE port
• 2 LAN Interfaces 10/100/1000 Mbps; auto‐negotiation
• 2 SFP ports of 1000 Mbps (standard MSA)
It is 19” rack mounted, 1U and half width. Power feeding is 44VDC ‐ 56VDC, Dual redundant
inputs through standard adapters.
Figure 4‐2: IDU‐H/HP

Antennas
4.3.4 Antennas
The RADWIN 2000 A+, RADWIN 2000 C+, and RADWIN 2000 D+ may be operated with an
integrated antenna that is part of the radio, or with external antennas connected to the radio
via N‐type connectors. The RADWIN 2000i uses external antennas only.
All cables and connections must be connected correctly to reduce RF losses. The required
antenna impedance is 50..
Integrated Antennas
• The 5.x GHz Integrated Antenna unit is provided with a 370 mm (1.2ft) flat panel
antenna, with a gain of 23dBi (5.x GHz) / 19dBi (4.9 GHz) and 8° beam width.
• The 2.x GHz Integrated Antenna ODU is provided with 370 mm (1.2ft) flat panel
antenna, with a gain of 16dBi and 16° beam width. The radio and the antenna are
housed in a weatherproof case as a single unit.
External Antennas
External antennas are available for the RADWIN 2000+ Series radios, varying in operating
frequencies, form factor, size and gain, dual or single polarization.
Flat Antenna Dish Antenna Mesh Antenna
Figure 4‐3: External Antennas for use with RADWIN 2000+ Series
See the RADWIN products catalog for a more detailed offering of external antennas.
A typical antenna kit contains ‐
• An antenna
• Two RF cables
• Mounting kit (see also Mounting an External Antenna)

Accessories
4.3.5 Accessories
Hub Site Synchronization (HSS) Unit
The HSS is not relevant for the RADWIN 2000 A+ and RADWIN 2000i. See
Chapter 9, Hub Site Synchronization for more details.
The HSS unit provides a connection between RADWIN 2000 C+ and RADWIN 2000 D+ radio
units that enables serial hub site synchronization (for more details on the various options for
hub site synchronization, see Chapter 9, Hub Site Synchronization). The HSS Unit is a
compact, weatherproof (IP67) connector box that is installed at the same location as the
radio units. It has a mounting ear on its rear side, and can be mounted on a pole or wall in the
same manner as an outside radio unit or antenna. See Mounting an ODU, GSU, or HSS for
instructions. All collocated units connect to this box use an HSS cable. Cables in prepared
lengths are available for purchase.
A single HSS unit supports up to ten collocated radios. Each radio is connected to a separate
port on the HSS, and any HSS port not in use is must be closed with a protective cover.
Figure 4‐4: HSS Interconnection Unit
See Hub Site Synchronization for further details about the use of HSS.
RADWIN GSU
The external RADWIN GSU is not needed for the RADWIN 2000i, as this unit has an
integrated GPS unit and uses GPS hub site synchronization. See GPS Hub Site
Synchronization for more details.
The GPS‐based synchronization unit (GSU) is designed to handle inter‐site interferences
under large‐scale deployment scenarios.
The RADWIN GSU is a small form factor outdoor unit. It uses a GPS antenna and a PoE device.

Accessories

Figure 4‐5: RADWIN GSU
The RADWIN GSU may be operated over Ethernet or connected to an HSS Unit using a
standard HSS cable. It synchronizes the transmission timing of multiple Hub‐Sites to a GPS
clock source thus eliminating self‐interference (see GPS Hub Site Synchronization)
Lightning Protector Unit (LPU)
The RADWIN Lightning Protection Unit is used for CAT‐5e cables, and can work with any
RADWIN product. The use of lightning protection is dependent on regulatory and end user
requirements. The RADWIN 2000+ Series ODU is designed with surge limiting circuits to
minimize the risk of damage due to lightning strikes.
Figure 4‐6: RADWIN Lightning Protector
The LPU works with CAT‐5e (ethernet) cables, but not RF cables. When
installing a unit with an external antenna, we recommend using a Surge
Protector along the RF cable for lightning protection.
Ethernet Cable Repeater
The RADWIN Ethernet repeater enables you to extend the PoE to ODU cable beyond the
100m limit (but no more than 200m). The repeater supports 10/100baseT.

Accessories
Figure 4‐7: RADWIN Ethernet Cable Repeater
The Ethernet repeater cannot be used with GbE PoE‐ODU cables.
ODU/External Antenna Mounting Kit
Outdoor radio units, external antennas, and other outdoor devices can be mounted on a pole
or wall using the RADWIN Mounting Kit:
Figure 4‐8: Mounting Kit

Tools Required for Installation
4.4 Tools Required for Installation
The following is a list of the equipment and materials required to install RADWIN 2000+ Series
hardware.
4.4.1 Tools and Materials
• Crimping tool for RJ‐45 (if the ODU‐PoE cable is without connectors)
• Spanner/wrench 13 mm (½”)
• Drill (for wall mounting only)
• Cable ties
• Sealing material
• Waterproofing tape such as Scotch 23 Tape ¾” wide, from 3M to ensure IP‐67 compliant
protection against water and dust
4.4.2 Cables and connectors
• ODU grounding cable 10 AWG
• ODU‐PoE cable (outdoor class, CAT‐5e, 4 twisted pairs, 24AWG):
• Up to 100 m. for 100BaseT connection.
• For a 1000BaseT connection (HBS only) use an ODU‐PoE cable no longer than 75m.
For 1000BaseT, you should use RADWIN supplied ODU‐PoE cables, which
guarantees 1Gb performance. RADWIN cannot guarantee 1Gb
performance if you use third party cables.
• External CAT‐5e cable diameter should be between 7‐9 mm to ensure waterproof
sealing.
4.5 Unpacking and Checking
 For each item:
1. Remove the equipment from the box.
2. Check that everything listed on the included Bill of Materials or Pro‐forma Invoice is
present.
3. If any item is missing, contact Customer Service. You will be advised whether to
return the package for replacement, or whether the missing item can be supplied
separately.
4. Do not dispose of the packaging until the unit is installed and operational.

Site Preparation
4.6 Site Preparation
Site Preparation includes ‐
• Obtaining any necessary legal and statutory permits for installation of radio equipment
• Clearing physical obstructions as far as possible
• Erecting a mast or tower if required. A mast‐sited ODU or external antenna typically
uses a pole attached to the mast.
• Installing a pole on a building wall if required
• Constructing a weather‐proof cabinet to house a PoE device or other IDU if it is not to
be housed indoors
• Ensuring availability of power, typically standard local AC power
• Ensuring that there is a LAN cable in place from the user’s switch to the PoE/IDU loca‐
tion
4.7 Mounting Units
4.7.1 Mounting an ODU, GSU, or HSS
Use a mounting kit to mount an ODU, GSU, or HSS on a wall or pole as shown in the following
figures:
Figure 4‐9: Mounting Kit Contents

Mounting an ODU, GSU, or HSS
• Tighten all bolts with a torque of 15 N*m.
• When mounting an ODU on a pole or wall, ensure that the unit is
oriented so that the cable connectors are at the bottom.
• Do not mount an ODU horizontally
• Ensure that there are no direct obstructions in front of an integrated
antenna ODU or interference from man‐made obstacles.
Mounting on a Pole
1. Connect the pole clamp to the radio holder with the 8x90 bolts, but do not tighten
the bolts all the way ‐ tighten them so that they are not closer than a distance
equal to the radius of the pole. You will then have one “unit” that you can take to
the location on the pole where you want to mount the ODU. (See Figure 4‐21 to
Figure 4‐24 for mounting on a thin pole).
Figure 4‐10: Connect Pole Clamp to Radio Figure 4‐11: Tighten bolts
Holder

2. Place this “assembly” on the pole where you want to mount the ODU.
3. Once it is in place, rotate the pole clamp as shown, then tighten both bolts.
Figure 4‐12: Rotate Clamp and tighten bolts Figure 4‐13: Mounting Kit on pole

4. Using an 8x40 bolt, mount an ODU to the mounting kit’s radio holder.
• A small form‐factor ODU (RADWIN 2000 A+) or GSU can be seen in Figure 4‐14
through Figure 4‐16 below.
• A large form‐factor ODU (RADWIN 2000 C+ or RADWIN 2000 D+) can be seen in
Figure 4‐17 through Figure 4‐19 below.
Figure 4‐14: Mounting a small form‐factor Figure 4‐15: Mounting a small form‐factor
ODU or GSU (1) ODU or GSU (2)
Figure 4‐16: Small form‐factor ODU or GSU on a vertical pole

Figure 4‐17: Mounting a large form‐factor Figure 4‐18: Mounting a large form‐factor
ODU (1) ODU(2)

Figure 4‐19: Large form‐factor ODU on a vertical pole

To attach an ODU, GSU, or external antenna to a horizontal pole, use the radio vertical
adaptor as shown:
Figure 4‐20: Mounting an ODU on a horizontal pole
When mounting on a thin pole, position the pole clamp as shown in the following figures:
Figure 4‐21: Connect Pole Clamp to Radio Figure 4‐22: Tighten bolts
Holder

5. Place this “unit” on the pole where you want to mount the ODU.
6. Once it is in place, rotate the pole clamp as shown, then tighten both bolts.
Figure 4‐23: Rotate Clamp and tighten bolts Figure 4‐24: Mounting Kit on thin pole
Mounting on a Wall
When mounting an unit on a wall, the pole clamp is not needed, but the vertical adaptor is, as
shown:
Figure 4‐25: Mounting a unit on a wall (1) Figure 4‐26: Mounting a unit on a wall (2)

Mounting an External Antenna
4.7.2 Mounting an External Antenna
Mounting External Antennas using the Mounting Kit
When using an external antennas for a radio unit, a flat panel antenna such as that shown in
Figure 4‐4 is typically used. It has four bolts for a mounting kit adapter. The mounting kit
adaptor appears as shown in Figure 4‐27:

Figure 4‐27: Flat panel antenna mounting kit adapter
Attach the mounting kit adaptor to the rear of the external antenna as shown:
Figure 4‐28: Flat Panel antenna ‐ rear with mounting kit adapter
Mount the antenna with the adaptor to a vertical or horizontal pole or to a wall in a similar
manner as shown in Figure 4‐9 to Figure 4‐24.

Mounting the IDU‐H/HP and RADWIN 2000i
Figure 4‐29 shows a mounted antenna. Attach the mounting bolt to the side of the adaptor
with the recess, as shown.
Figure 4‐29: Flat Panel antenna ‐ mounted to a pole
Grounding an external antenna
Groud external antennas using a suitable Grounding Kit such as an Andrew Type 223158‐2
(http://www.commscope.com).
4.7.3 Mounting the IDU‐H/HP and RADWIN 2000i
Indoor units are installed on a 19in rack, or on almost any other convenient location located
indoors, such as a table.
Mounting the IDU‐H/HP
The IDU‐H/HP takes up half of a rack width. Use the small mounting ear on one side, and the
large mounting ear on the other side to mount this unit (see Figure 4‐30). A single IDU‐H/HP
mounted on a 19 in rack is shown in Figure 4‐31.

If you are using two units on one shelf, you can use the connecting flange to connect them, as
shown in Figure 4‐32. Use the two small mounting ears to mount the connected units. See
Figure 4‐33.
Figure 4‐30: Mounting a Single IDU‐H/HP
Figure 4‐31: Single IDU‐H/HP mounted in a 19in. rack

Figure 4‐32: Connecting two IDU‐H/HP units
Figure 4‐33: Two IDU‐H/HP units mounted in a 19in. rack
Mounting the RADWIN 2000i
The RADWIN 2000i can be mounted in a 19 in. rack. It takes up the whole rack width.

Figure 4‐34: Mounting the RADWIN 2000i
Figure 4‐35: RADWIN 2000i mounted in a 19 in. rack

External Connections
4.8 External Connections
4.8.1 Small Form‐Factor (RADWIN 2000 A+) ODU
The external connections for the connectorized RADWIN 2000 A+ are shown in Figure 4‐36.
• Ground: Ground cable is attached to the ground lug.
• Antenna (x2): RF cables connect to the two antenna sockets (does not appear with
models with an integrated antenna)
• Power (IDU): The IDU port provides both a power and network connection from a PoE
device via a CAT‐5e cable.
• Network (IDU): The IDU port provides both a power and network connection from a
PoE device via a CAT‐5e cable.
Figure 4‐36: External Connections: RADWIN 2000 A+
4.8.2 Large Form‐Factor (RADWIN 2000 C+, RADWIN 2000
D+)
The external connections for the connectorized RADWIN 2000 C+ and RADWIN 2000 D+ are
shown in Figure 4‐37.
• Power (IDU): The IDU port provides both a power and network connection from a PoE
device via a CAT‐5e cable.
• Sync: Connect the HSS serial unit to this port using an HSS cable (if you are using serial
hub site synchronization).
• Antenna: RF cables connect to the two antenna sockets (does not appear for models
with an integrated antenna)

RADWIN 2000i
• Ground: Ground cable is attached to the ground lug
Figure 4‐37: External Connections: RADWIN 2000 C+ and RADWIN 2000 D+
4.8.3 RADWIN 2000i
The external connections for the RADWIN 2000i are shown in Figure 4‐37.
• GPS Antenna: RF cable connects to a GPS antenna, if hub site sychronization is used.
• Antenna (2x): RF cables connect to the two antenna sockets
• LAN2: Provides SFP connection (copper or fiber)
• LAN1: RJ‐45 ethernet connection
• VDC Input: DC input ‐20 to ‐60 V, 2A, twin cable (polarity as indicated on unit)
Figure 4‐38: External Connections: RADWIN 2000i

PoE Devices
4.8.4 PoE Devices
The external connections for the indoor PoE device are shown in Figure 4‐39.
• AC Power IN: AC power is supplied here. The specific adaptor is country‐dependent
• Ethernet IN: Inbound ethernet RJ‐45 connection
• PoE OUT: Outbound RJ‐45 / CAT‐5e cable to outdoor radio unit
AC Power IN
Ethernet IN
PoE OUT
Figure 4‐39: External Connections: PoE Device
4.8.5 IDU‐H/HP
The external connections for the IDU‐H/HP are shown in Figure 4‐40.
• PoE to radio units: Using a CAT‐5e cable, connect the radio units that are being syn‐
chronized here. Up to 6 radio units can be connected to one IDU‐H/HP.
• DC input primary: Use only a vendor‐approved AC/DC adaptor.
• DC input secondary: Used as a backup in case of power failure, connect a battery to
this input (however, a battery can be used for either the primary or secondary power
input).
• SFP 1 and SFP 2: SFP connection, either copper or fiber
• LAN (x2): Input LAN/ethernet connection

RADWIN GSU
Figure 4‐40: External Connections: IDU‐H/HP
4.8.6 RADWIN GSU
The GSU is used when GPS synchronization is needed, but when the radio unit does not have
an internal GPS capability.
The RADWIN GSU is not needed for the RADWIN 2000i.
The GSU’s external connections are shown in Figure 4‐41.
• Antenna: RF cable connects to the GPS antenna
• Sync: If you are not using the IDU‐H/HP to connect the radio units when using GPS
hub site synchronization, use this port to connect the ethernet switch. If you are
using the IDU‐H/HP (recommended), this port is not needed.
• Power (IDU): The IDU port provides both a power and network connection from a

Hardware Setup for Hub Site Synchronization
Figure 4‐41: External Connections: RADWIN GSU
All external ODU ports should be water sealed. See Additional Considerations for
Waterproofing for instructions on doing so.
4.9 Hardware Setup for Hub Site
Synchronization
For a complete description of the functionality of hub site synchronization, see Chapter 9,
Hub Site Synchronization.
Here, we describe how to connect the various options:
• Serial hub site synchronization
• Ethernet hub site synchronization
• GPS hub site synchronization with an external GSU
• GPS hub site synchronization when the radio unit has an integrated GPS capability (rele‐
vant for the RADWIN 2000i only).
4.9.1 Serial Hub Site Synchronization
Serial hub site synchronization is This method is applicable for the RADWIN 2000 C+ and
RADWIN 2000 D+ only.
Serial hub site synchronization requires the external HSS unit. The general connections
between the the HSS unit and the radio units are shown in Figure 4‐42 below. However, a

Ethernet Hub Site Synchronization
complete description of the HSS serial connections are more complex ‐ see SHSS Hardware
Installation on page 10‐1. for complete directions.
RADWIN recommends that you seal each connection against water leakage. See Additional
Considerations for Waterproofing for instructions on doing so.
Figure 4‐42: Connections: Serial HSS using the HSS unit
4.9.2 Ethernet Hub Site Synchronization
In this case, the relevant units are connected via a the IDU‐H/HP.
The units are connected to the PoE port on the IDU‐H/HP. The port the radio unit uses for this
connection depends on the specific model you are working with, as follows:
• RADWIN 2000 C+: Connect to IDU port
• RADWIN 2000 D+: Connect to IDU port
• RADWIN 2000 A+: Connect to PoE port
• RADWIN 2000i: Connect to either the LAN1 or LAN2 port

The Ethernet HSS (HSSoE) method requires Layer 2 Ethernet connectivity
between collocated ODUs. For more details, see HSSoE Concepts.

GPS Hub Site Synchronization with an external GSU
Figure 4‐43: Connections: HSS over Ethernet using the IDU‐H/HP
It is possible to synchronize the base stations of any RADWIN radio product co‐located with a
RADWIN 2000+ Series Master ODU.
It is possible to use HSS over Ethernet with a 3rd‐party L2 switch instead of the
IDU‐H/HP. If you do so, make sure the L2 switch fulfills these conditions:
‐ Must support GbE
‐ Does not support EEE (Energy Efficient Ethernet), or
‐ If it supports EEE, it should be according to the IEEE 802.3az standard
4.9.3 GPS Hub Site Synchronization with an external GSU
If you wish to use a GPS signal to carry out hub site synchronization, and the unit you are
working with does not have an integrated/internal GPS capability, you can use the RADWIN
GSU. This device connects to the IDU‐H/HP on the one side, and to the GPS satellite on the
other, via a GPS antenna. The IDU‐H/HP in turn, connects to the various co‐located base
stations, as shown:

GPS Hub Site Synchronization with an external GSU
Figure 4‐44: Connections: HSS via GPS using the RADWIN GSU

GPS Hub Site Synchronization with an Internal GSU
4.9.4 GPS Hub Site Synchronization with an Internal GSU
The RADWIN 2000i has an internal GPS unit that enables it to synchronize with other units
using a GPS signal. The only special connection required in this case is with a GPS antenna, at
the GPS antenna port of the unit:
Figure 4‐45: Connections: HSS via GPS using an internal GPS (for the RADWIN 2000i)
4.10 Lightning Protection
The use of lightning protection is dependent on regulatory and end user requirements. 2000+
radio units have surge limiting circuits that minimize the risk of damage due to lightning
strikes. RADWIN recommends the use of additional surge arrestor devices to protect the
equipment from nearby lightning strikes.
Lightning protection is carried out differently for RF cables vs. CAT‐5e cables: RF cables are
connected to the ground point of the outdoor radio unit, whereas CAT‐5e cables use an
additional LPU (lightning protection unit)
4.10.1 Lightning Protection for RF Cables
Connect the RF cables of the external antennas (if external antennas are used) to the
grounding point of the radio unit using a grounding kit such as the Andrew Type 223158‐2
(http://www.commscope.com).
Ground the RF cables to the pole, attaching the grounding kit as close as possible to the
antenna (see figure 4‐46, Grounding an External Antenna). RADWIN recommends that you
add an additional ground connection close to the outdoor radio unit.

Lightning Protection Unit (LPU) for CAT‐5e Cables
Figure 4‐46: Grounding an External Antenna
4.10.2 Lightning Protection Unit (LPU) for CAT‐5e Cables
Lightning protection for CAT‐5e cables is accomplished using RADWIN’s LPU, as described
here.
Table 4‐3: LPU Kit contents
Item Qty View/Remarks
LPU 1
RJ‐45 connectors 2

Table 4‐3: LPU Kit contents (Continued)
Item Qty View/Remarks
0.5m CAT‐5e cable 1
Metal tie 1
ScotchTM 23 Tape 2

For any type of indoor‐to‐outdoor unit connection along a CAT‐5e cable, lightning protection
units (LPUs) are installed in pairs, as shown in Figure 4‐47:
Figure 4‐47: Basic use of lightning protector units
The LPU has two cable glands on the bottom for CAT‐5e cables, in addition to a grounding lug.
There is an extra hole for a second screw when installed on a wall. On the side of the LPU is a
slot for the metal tie when installed on a pole, as shown in Figure 4‐48 and Figure 4‐49:
Figure 4‐48: LPU: Bottom View Figure 4‐49: LPU: Side View
 To install an LPU on a pole:
1. Choose a location as close as possible to the ODU.
2. Insert the metal tie through the slots as shown in Figure 4‐49. Make sure the LPU is
oriented in the correct direction, as shown in Figure 4‐50.

Figure 4‐50: LPU attached to pole with metal tie
3. Tighten the metal tie.
4. Connect the grounding lug to a grounding source.
5. Remove the cable glands.
6. Thread the CAT‐5e cables through the cable glands, and connect the cables to the
LPU as shown in Figure 4‐51.
7. Tighten the cable glands around the CAT‐5e cables as shown in Figure 4‐52.
Figure 4‐51: Connecting cables to the LPU (1) Figure 4‐52: Connecting cables to the LPU (2)
8. Route one CAT‐5e up to the ODU, and the other down to the IDU or PoE (via the
lower LPU). An LPU installed on a pole is shown in Figure 4‐53.
9. RADWIN recommends that you add extra waterproofing to the connections
(see Additional Considerations for Waterproofing on page 4‐38).

Figure 4‐53: Installing an LPU on a pole (side view)
 To install an LPU on a wall:
1. Remove the grounding lug.
2. Attach the LPU to the wall using wood or masonry screws (not included), via the
holes as shown in Figure 4‐54.
3. Connect the left screw (where the grounding lug was located) to a ground source.
4. Remove the cable glands.
5. Thread the CAT‐5e cables through the cable glands, and connect the cables to the
LPU as shown in Figure 4‐51.
6. Tighten the cable glands around the CAT‐5e cables as shown in Figure 4‐52.
7. Route one CAT‐5e up to the ODU (via the upper LPU), and the other to the IDU or
PoE.
8. RADWIN recommends that you add extra waterproofing to the connections
(see Additional Considerations for Waterproofing on page 4‐38).

Figure 4‐54: Installing an LPU on a wall
Additional Considerations for Waterproofing
Protect all connections between any outdoor devices (ODUs, LPUs, Ethernet Repeaters, etc)
and cables from rain, dust, moisture and salt according to the procedure below:
1. Use a high quality sealing material such as Scotch 23 Tape ¾” wide, to ensure IP‐67
compliant protection against water and dust.
2. Cut two pieces each 25 cm long, of Scotch 23 splicing tape. Remove the plastic
cover to expose the tacky side of the sealing tape as shown in Figure 4‐55.
Figure 4‐55: Exposing the tacky side of the sealing tape
3. After connecting a cable to a unit, tighten the cable gland cap firmly and use the
insulation tape to fully cover the cable gland.

Antenna Alignment

Figure 4‐56: Waterproofing an external connection
4.11 Antenna Alignment
• An audible buzzer is used on both the Master ODU and the Slave ODU. If the external
antenna is positioned so far away from the unit so as to make the buzzer inaudible, you
may need to use two people to perform antenna alignment.
• Antenna alignment is carried out in three stages:
• Master ODU gross alignment
• Slave ODU fine alignment
• Master ODU fine alignment
4.11.1 Antenna Alignment Procedure
1. Ensure that power is connected to all radio units.
2. If you are working with an external antenna, connect the vertical polarization
connector of the antenna to the ANT 1 connector of the radio unit, and the
horizontal polarization connector of the antenna to the ANT 2 connector of the
radio unit.
There is no particular reason to use ANT 1 and ANT 2 in that order: They
just have to be the same for each ODU in the sector. Further, adopting a
convention like “ANT 1 is always vertical” avoids mistakes across a large
sector.
3. Ensure that the buzzer on both radio units is configured to Auto (see Link
Configuration Tool Bar on page 7‐27). An unaligned ODU starts beeping 20 seconds
after power up, and continues beeping until it is aligned.

Antenna Alignment Procedure
4. Point the antenna1 of the Master ODU in the general direction of the Slave ODU,
and secure it to the pole or wall.
5. From the Slave ODU, make a horizontal sweep of 180 degrees with its antenna so
that the strongest signal from the Master ODU can be detected.
6. Slowly turn the Slave ODU antenna back towards the position of the Master ODU,
listening to the tone until the best signal is reached. See the following figure for
audible signal variations.
Figure 4‐57: Beep Sequence for antenna alignment
• Three beeps and a pause is 'best signal so far'
• Two beeps and a pause is 'signal quality increased'
• One beep and short pause is 'no change in signal'
• Long beep and short pause is 'signal quality decreased'
• One beep and a long pause is 'no air link'
• Any other signal does not relate to antenna alignment
7. Secure the Slave ODU antenna to the pole/wall.
8. Repeat the above steps from the Master ODU, listening to its buzzer: make a
horizontal sweep of 180 degrees with its antenna so that the strongest signal from
the Slave ODU can be detected.
9. Slowly turn the Master ODU antenna back towards the position of the Slave ODU,
listening to the tone until the best signal is reached.
10. Secure the Master ODU antenna to the pole/wall.
11. Turn off the buzzer of the radio units from the RADWIN Manager (see Link
Configuration Tool Bar on page 7‐27).
1. If your unit has an integrated antenna, “pointing the antenna” consists of pointing the unit itself.

Chapter 5: RADWIN Manager
This chapter describes how to install and basic operation of the RADWIN Manager, which is
an application that allows you to configure the radio units and the link between them.
5.2 Installing the RADWIN Manager
Application
5.2.1 Minimum System Requirements
The RADWIN Manager application is distributed on a CD. Operating system specific PC
resources required by the application are set out in Table 5‐1 below:
Table 5‐1: PC Requirements for the RADWIN Manager Application
Windows Version
Vista/7/8
XP Pro
32 bit 64 bit
Memory 512 Mb 1 Gb 2 Gb

Processor P IV P IV Dual Core
Requirements common to all systems are:
• Hard disk: 1 GB free space
• Network: 10/100BaseT NIC
• Graphics: 1024x768 screen resolution with 16 bit color
• Any modern Web browser to view additional material, use the Web Interface or get
help from the RADWIN Web site.

Installing the Software
5.2.2 Installing the Software
Any PC running the RADWIN Manager application can be used to configure a RADWIN 2000+
Series sector.
 To install the RADWIN Manager application:
1. Insert the CD into the CD/DVD drive of your computer.
2. The CD opening window appears:
3. Choose Install RADWIN Manager and follow the on‐screen instructions of the
installation wizard to complete the setup of the RADWIN Manager application.
If the installation program fails to start, browse to your CD/DVD drive, chose the
setup.exe program and run it.
5.3 Logging On to the RADWIN Manager
5.3.1 Preparation for First Log‐on (check connectivity)
1. Connect the managing computer to the IDU or LAN port of one of your radio units.
2. The default IP address on all new radios is 10.0.0.120 with subnet mask, 255.0.0.0.
Set your network interface to an available IP address on that subnet, say 10.0.0.111.
This is the preferred way of logging on.

First Log‐on
3. Check that you have connectivity to the radio unit. You can do this by opening up a
command line session (Start|Run and then type, cmd). At the command prompt,
type
ping 10.0.0.120
You should see a display similar to this:
Figure 5‐1: Pinging the base station.
Any other response from ping means that the radio unit is not responding. Check
your Ethernet connection and that the PoE is switched on (or voltage is connected
to the radio unit) and then try again. If you do not succeed, seek assistance from
RADWIN Customer Service.
4. Dismiss the command line session.
5.3.2 First Log‐on
1. Open the RADWIN Manager from the desktop icon, or click Start|Programs|RAD‐
WIN Manager|RADWIN Manager.
The Log‐on dialog box appears:

First Log‐on
Figure 5‐2: Log‐on window ‐ default
2. Log on with IP address 10.0.0.120 and password admin:
Figure 5‐3: Log‐on window using an IP address
• The RADWIN Manager stores the last 10 successful log‐on IP
addresses.
• Other log‐on options are described below in Other Log‐on Options.
3. If the log‐on was successful, you should see the initial RADWIN Manager screen (see
Figure 5‐10).

Log‐On with Local Connection
5.3.3 Log‐On with Local Connection
Alternatively, you can log on using Local Connection (Figure 5‐2) without having to change
your Network Interface Card address.
• The Local Connection method uses broadcast packets to “discover”
the attached radio unit.
• If you log on using Local Connection, but your physical connection is
not local, then any configuration you carry out may affect other links
in the network. Do not do this!
• Do not carry out this procedure using a multi homed managing com‐
puter also connected to a network. It will flood the network with
broadcast packets. Further, it will throw any other links on the net‐
work into Installation or Inactive mode.
• As a precaution, default log‐on over Local Connection is read‐only
mode. Check the Read/Write enable box to carry out installation pro‐
cedures.
• Network log on (IP address to the radio unit) is recommended.
5.4 Other Log‐on Options
SNMPv3: RADWIN 2000+ Series supports SNMPv1 and SNMPv3 either separately or
together. The log‐on procedure differs slightly between operation under
SNMPv1 and SNMPv3. Table 5‐2 shows the difference between SNMPv1 and
SNMPv3 at log‐on time.
User Types: The RADWIN Manager provides three levels of access in one of two entry
modes. To see them, click Options at any time in the Log on window (Figure 5‐
2 above). You are offered an extended log‐on window:

Other Log‐on Options
Figure 5‐4: Extended log‐on window
At the User Type field, click the list button:
Figure 5‐5: Log on window exposing the user types.
There are three user types:
• An Observer has read‐only access to the sector. An Observer can monitor the sector,
generate reports, but may not change any sector parameters.
• An Operator can install and configure the sector.
• An Installer can, in addition to functioning as an Operator, also change the operating
frequency band (or regulation). The latter function has legal ramifications, requiring
familiarity with local regulations.
You may choose the SNMP version. If your firewall blocks SNMPv3 messages and for security
reasons cannot be changed them use SNMPv1. To log on under SNMPv3, click Settings from
the extended log‐on window:

Other Log‐on Options
Figure 5‐6: Log‐on window with SNMPv3
If you are using Trap Authentication, enter the User and Password. Leaving these fields blank
or incorrect, will not prevent you from logging on. You will not be able to see trap messages
directed to the trap message address associated with a defined user. The allocation and
association of a trap address with a user is described in Management.
If you are connecting through the RNMS server check the RNMS connect button and enter
your server IP address.
The following table summarizes these options:
Table 5‐2: User types, default passwords and function
SNMPv1 SNMPv3
Default
User Type Function Communi Default
Password Community Password
ty String Value
Observer admin Monitoring Read‐Only public Read‐Only public

Installation,
Operator admin Read‐Write netman Read‐Write netman
configuration
Operator plus
Installer wireless Read‐Write netman Read‐Write netman
set‐band
The Network Manager should change the default passwords as soon as possible, particularly
if SNMPv3 is to be used.

Log‐on Errors and Cautions
Once you have set all fields properly, click OK. The RADWIN Manager main screen (Figure 5‐
10) should appear.
• Leave the default Community passwords, netman for read‐write,
and public for read‐only.
• If you are a user with read‐only permission, then you may only log
on as Observer.
• The two fields serve as SNMPv1 Community strings and SNMPv3
passwords.
5.5 Log‐on Errors and Cautions
5.5.1 Unsupported Device
Attempting to connect to an unsupported device on an otherwise valid IP address (for
example, a LAN printer) will result in the following error message:
Figure 5‐7: Unsupported device message
5.5.2 Incorrect IP Address
If the IP address chosen is invalid or the sector is unreachable, the following error message
will be displayed:
Figure 5‐8: Unreachable device message

Incorrect Password
5.5.3 Incorrect Password
If you type an incorrect password in the Login window, the follwing message will be
displayed:
Figure 5‐9: Invalid user type or password
5.5.4 Invalid Read/Write Community String or SNMPv3
Passwords
This will result in the same message as shown in Figure 5‐8.
 To deal with lost or forgotten Community Strings:
1. Send an email request for to RADWIN Customer Service for an alternative key. Your
email must include the radio unit serial number shown on the adhesive sticker on
rear of one of your radio units.
2. The reply will contain an alternative key, which functions as a temporary master
Community String. Copy/paste the supplied alternative key to both the Read‐Only
and Read‐Write fields in the log‐on window (Figure 5‐4). This gets you to the
RADWIN Manager main window.
3. Use the procedure in Editing SNMPv1 Community Strings to enter new Community
Strings.

The Initial RADWIN Manager Main Window
5.6 The Initial RADWIN Manager Main
Window
Upon successful log on, the main window is displayed:
Figure 5‐10: Main window prior to link configuration
5.7 Master ODU vs. Slave ODU
In a point‐to‐point link, one radio unit functions as the “dominant” unit. This unit is called the
Master ODU. The other unit is called the Slave ODU. This terminology describes their relative
roles.
In the RADWIN Manager software application, the dominant unit is also called Radio Terminal
A (RT‐A(HBS)), and the other unit is called Radio Terminal B (RT‐B(HSU)). This terminology is
taken from point‐to‐multipoint technology, where one unit is a Base Station (HBS), and is the
dominant unit, and the other units are Subscriber Units (HSU), where there can be multiple
Subscriber Units.
All 2000+ radios are shipped from the factory defined as Slave ODUs. You must re‐define one
as a Master ODU. Instructions for doing this are found in Define One Unit as an RT‐A(HBS).
Although any side can be a Master ODU or Slave ODU, take the following into consideration
when determining which side will be defined as either:

Define One Unit as an RT‐A(HBS)
• Hub Site Synchronization: Only Master ODUs can be synchronized with other units
to avoid interference. Chapter 9, Hub Site Synchronization for a description of hub
site synchronization.
• VLANs: VLANs can be defined from Slave ODUs only. See Chapter 15, VLAN Func‐
tionality for a description of how VLANs are defined.
5.7.1 Define One Unit as an RT‐A(HBS)
1. Make sure that the managing computer is connected to the unit that will be defined as a
Master ODU.
2. Install the RADWIN Manager and log on to the unit (see Installing the RADWIN
Manager Application on page 5‐1).
3. Click the Link Configuration button on the left unit in the central part of the main
window.
Link Configuration button

4. The Configuration window appears. Click Operations:
5. From Change ODU Mode, click RT‐A(HBS).
6. A warning message will appear. Click OK.

7. The screen will be grayed‐out while the system is re‐configuring. No action is
necessary on your part.
8. A warning message appears stating that connection to the unit was lost. This is
normal, and of no concern. No action is necessary on your part.
9. After a few moments, the Main Window appears as follows:

Setting RADWIN Manager Preferences
The left unit is now defined as a Master ODU (or RT‐A(HBS), the right unit as a Slave ODU
(or RT‐B(HSU)).
10.From this point, you can activate, register, and then configure each unit.
Instructions for doing this are found in Chapter 6, Link Configuration.
11.However, we recommend you first set certain preferences when working with the
RADWIN Manager.
5.8 Setting RADWIN Manager Preferences
The Preferences tabs appearing on both the RT‐A(HBS) and RT‐B(HSU) relate entirely to the
way the Manager displays certain items for the connected unit. They are completely local to
the managing computer. They are identical for both the RT‐A(HBS) and RT‐B(HSU).
Each technician servicing a sector will need to set up his managing
computer (typically a laptop) with his own preferences.

Preferences: Monitor
5.8.1 Preferences: Monitor
Figure 5‐11: Monitor Preferences
File: Place a checkmark here to save traffic and identification information to the Monitor
file. The content of the Monitor file is described in detail in Chapter 8, Monitoring
and Diagnostics.
Click the explorer button to select the location of this file.
Click the select headers button to select the categories of data to be saved
in the Monitor file.
From the screen that appears, place a checkmark next to each category of data
you wish to be saved in the Monitor file1. Click OK to accept your choices.
Interval:Save the data every X seconds to the Monitor file (and the Utilization file if relevant).
X can be an integer value only, and from 1 to 60. This file can be very large very
quickly, so if you want to store data for a lengthy period of time, choose a large
number.
The KMZ button is not functional here and can be ignored.
Rx/Tx Rate Units: Choose Mega bits per second (Mbps), or Frames per second (Fps)
Show IP:Determine which IP address format to show on the main window for each unit: IPv4
or IPv6. The IPv6 option will work only if you have defined an IPv6 address for the
unit.
IPv6 Address Format: If showing IPv6 addresses, choose Compressed or Expanded.
1. There may be categories listed that are not relevant for the specific radio model you are working with. Ignore
those categories.

Preferences: Events
5.8.2 Preferences: Events
Critical ... Info:Choose your own color coding for the Recent Event display (see Monitoring
and Diagnostics).
Reset Settings:Restore the color coding to the default values.
Background color:Choose the background color for the Recent Event display (see Monitoring
and Diagnostics)
File: Place a checkmark here to save a file for events logs, and click the explorer
button to select the location of this file. These settings are per individual
radio unit.
SNMPv3 Trap Authentication: Choose the user name and password for SNMPv3 trap
authorization. The SNMPv3 User and Password are relevant if you are using
SNMPv3. In this, case trap messages are keyed to the user name and password
and not visible to anyone else. The preferences entered here relate to trap
messages sent to the specified user if specified, or to all trap messages,
otherwise.

Preferences: Advanced
5.8.3 Preferences: Advanced
Figure 5‐12: Advanced Preferences
Change Password: You may change your log‐on password here from the default value.
Restore Alerts:Many alert messages in the RADWIN Manager have an option of the form “Do
not show this message again”. These alert messages can be reverted to their
default state (shown) by clicking this button. You will be asked to confirm:
Enable RSS Balance Indication for Mobility: This item is not functional for PtP links, and may
be ignored.

Preferences: Advanced
Enable RSS Extended View: Checking this box enables a dual chain view for RSS. Disabled, the
RSS is shown as a single bar for each radio. The effect is visible immediately.
Figure 5‐13: RSS Extended view enabled
Figure 5‐14: RSS Extended view disabled
Enable Tx/Rx Extended View: Place a checkmark here to enable viewing the Rx and Tx rate of
each LAN line attached to the unit. Disabled, the rate shown is an aggregate
rate for both LAN lines.
This will appear in all cases, but will only have meaning if your unit has more
than one LAN line, and if they both are connected. See Chapter 4, Hardware
Installation for the external connections of the unit you are using.
Figure 5‐15: Tx/Rx Extended View enabled
Figure 5‐16: Tx/Rx Extended View disabled
Enable Unicode in Text fields: This allows you to write non‐standard text in the various fields
you use. We do not recommend this because it would be difficult or impossible
to coordinate with systems and equipment that may not be able to detect this
text, and you could therefore lose connections.
Map View Background Mode: You have a choice of two map providers, a default or a self‐
chosen background. If you log on without an Internet connection, you will get
a default gray background or, if you have caching enabled, your last used map.
If you want a background image for the map view, choose Background Image
then click the explorer button to select the location of the image file.

Part 3: Link Management
Release 4.2.40
Chapter 6: Initial Link
Configuration
This chapter covers the two phases of Link configuration:
1. Link establishment: Initial setup
2. Link maintenance: Fine tuning and special functions
Link establishment is typically a once‐only task. Link maintenance is required for fine‐tuning
the link and configuration of special features such as VLAN, Quality of Service and more.
6.2 Link Establishment
6.2.1 Link Configuration Workflow
As soon power and network connections are supplied to the radio unit, it will commence
transmitting and receiving packets related to management only ‐ that is, no service traffic will
be sent or received.
Activation: For the RT‐A(HBS) to carry out service, it must be activated. Activation and
Deactivation are effected quite simply by clicking a toggle button.
Discovery: Assuming that the radio unit intended as the RT‐B(HSU) (Slave ODU) is mounted,
aligned, and powered up, it will discover the RT‐A(HBS) establishing a link for
management only. At this point the RT‐B(HSU) may be managed over the air.
Registration: Having Identified the Link RT‐B(HSU), the latter must be registered to the RT‐
A(HBS) to enable traffic between them.
Following registration, you can set separately,
• MIMO mode
• Transmission ratio between uplink and downlink
• Uplink and downlink Maximum Information Rate (MIR) in Mbps

Activating the RT‐A(HBS)
• VLAN parameters
• Quality of Service parameters.
In what follows, we assume that you are logged on to RT‐A(HBS) on IP address as shown in the
previous chapter. Here is the opening situation:
Figure 6‐1: Main window prior to link configuration
6.2.2 Activating the RT‐A(HBS)
 To activate the RT‐A(HBS):
1. Click the Activate button. The Activation Wizard opens.

2. Click Next:
Enter the Sector ID, Name and Location. All fields are mandatory. Here are the
entries for our demonstration link:

You may also ignore the Coordinates button.
3. The Link Password may also be changed by clicking Change:
Full details for changing the Link Password may be found in Changing the Link Pass‐
word. It is best left as is if there is no pressing need to change it.
If you skipped an entry, it will be framed in red like this:
4. From the previous Activation Wizard window, click Next.

Enter the IP details. Here are our demonstration IP details:
To continue, click Next.
5. The next window is used to set the frequency and channels.

The default frequency is the lowest available in the operating band.
The frequency range and bandwidths available depend on the specific model in
the RADWIN 2000+ Series you are working with. The values shown in the screen
shot above are for illustrative purposes only.
6. Click Other to see other available bands for this radio unit.
7. For our purposes, we choose 5.820 GHz:

right hand selector wheel
Observe that the right hand spin‐wheel is no longer displayed. Had you
left Other enabled, you could have chosen a frequency by working through those
available in 5MHz increments.
8. Choose the required Channel Bandwidth:
For the RADWIN 2000 C+, RADWIN 2000 D+, and RADWIN 2000i, choose
at least 40 MHz Channel Bandwidth to enable the supported net
aggregate capacity.
The RADWIN 2000+ Series has Dynamic Bandwidth Selection: If you choose the
maximum value available for the bandwidth, the link may dynamically switch
between the maximum value and values as low as 20MHz to ensure the best

throughput. Selecting 20, 10 or 5 MHz CBW sets your choice as the fixed CBW for
the link.
9. Using ACS:
• Choosing 40 or 80 MHz (if available) CBW automatically enables ACS. All that you
may do is remove some of the channels:
Do not use ACS prior to antenna alignment.

• For CBW 20MHz or less, enable ACS by checking the Automatic Channel Selection
box:

You can perform a customized channel selection or click Select All to check all the
channel boxes as shown:
10. Click Next. The Antenna type and Tx Power window is presented:

The choice of Tx Power, antenna gain and cable loss (between the radio and the
antenna) determines the EIRP and is affected by such considerations as radio limita‐
tions and regulatory restrictions.
Before completing antenna installation, you might like to consider the background
information about setting antenna parameters, in Setting Antenna Parameters.
When setting Required Tx Power, it is your responsibility to chose a value
in compliance with your local regulations.
Choose your Antenna Type, Required Tx Power, Antenna Gain and Cable Loss. We
will set Required Tx Power to 5 dBm for our example. Click Next.
11. The Summary window of the Wizard is displayed.

Check that all information showed is correct and click Activate. After a few
moments the RT‐B(HSU) will be displayed in the Manager main panel as shown in
the next figure:
Figure 6‐2: Main window: RT‐A(HBS) activated, RT‐B(HSU) ready for registration
Notice the Rate line shown enlarged:

Registering the RT‐B(HSU)
Observe that under management mode (no traffic) the throughput and MCS is min‐
imal to support a link and the CBW is also at its minimum for DBS.
12. If you are using Local Connection, log out and log back in to the RT‐A(HBS) on its IP
address.
You may have observed that operating frequency 5.770 GHz shown, is not what we chose
(5.820 GHz). The RT‐A(HBS) tries to optimize the frequency to minimize interference effects.
We next register and configure the RT‐B(HSU). Many of the configuration and service
parameters may be set prior to registration. During link establishment the order does not
matter. However, many configuration changes to a link after registration, will affect traffic or
even reset the link.
6.2.3 Registering the RT‐B(HSU)
After few moments, the registration process completes. Here is the status of the link:
Figure 6‐3: Main window: Link Master ODU activated, Slave ODU registered
6.2.4 Basic Configuration for Operations
Several basic parameters should be configured for both link sites. Use the appropriate site
Configuration button:

Basic Configuration for Operations
RT‐A(HBS)
Go to Configuration | System and change the Contact to something other than the default
entry, “Person”:
This only affects reports.
RT‐B(HSU)
 To complete basic configuration of the Slave ODU:
1. Go to Configuration | System and change the Name, Contact and Location fields to
meaningful values:

2. In the Tx & Antenna tab, ensure that Tx Power is set appropriately. For our
demonstration link, we reduce it to 5dBm:
3. Open the Management tab and set the IP address, Subnet Mask and Default
Gateway to their required values. Here are ours:

4. Click OK on the Configuration window to save your changes. You are asked to
confirm:
5. Accept the changes. Here is the status of the Link:
Figure 6‐4: Main window: Link fully operational

Advanced Link Configuration
Notice the Rate line shown enlarged:
Observe that in traffic mode the throughput and MCS are at their maximum and the CBW is
also at its maximum. Under adverse conditions, such as high interference, DBS will cause
these parameters to fallback for best throughput.
6.3 Advanced Link Configuration
The link as configured so far, is sufficient to provide basic service. Additional link‐level
services that can be configured from the Link Configuration tab on the top left of the main
window.
6.3.1 Air Interface
Figure 6‐5: Link Air Interface parameters ‐ no ACS

Air Interface
Figure 6‐6: Link Air Interface parameters ‐ ACS enabled

Air Interface
Figure 6‐7: Link Air Interface parameters ‐ DBS enabled, ACS on by default
Figure 6‐5 to Figure 6‐7 contain a subset of the Activation Air Interface settings. You may only

change the Operating channel with ACS disabled.
These parameters are automatically inherited by the RT‐B(HSU) when you click OK.
Throughput Mode
The Advanced button enables you to choose a throughput mode:
Throughput Mode determines how the Adaptive Modulation mechanism works. Maximum
Throughput (default) should be chosen if throughput is more important than higher delay.
Conversely, Reduced Latency minimizes delay at the expense of lower throughput.
Link ID
You may change this to any convenient string. After you click OK, the RT‐B(HSU) will be
immediately updated over the air without interruption to service.

Ethernet
6.3.2 Ethernet
Link Configuration: MIMO Modes
If you are using dual antennas, you may check a MIMO Mode: Spatial Multiplexing (default)
splits the data in to two streams on transmission and recombines it on reception providing
maximum throughput. Diversity transmits the same data on both antennas and check for
correctness on reception. For further details about MIMO antenna modes, see Initial Link
Configuration.
Link Configuration: Transmission Ratio
The Transmission Ratio shows the allocation of throughput between downlink and uplink
traffic at RT‐A(HBS).

Ethernet
Figure 6‐8: RT‐A(HBS) Collocated client or independent unit
The permissible Transmission Ratio is also dependent on RT‐A(HBS)’s HSS (collocation) status.
(For further details about configuring and using HSS, see Hub Site Synchronization.)
If the RT‐A(HBS) is an HSS master, you will see something like this:
Figure 6‐9: RT‐A(HBS) Co‐located master
Moving the slider to the right in stages, yields the following:
The effective available range for Asymmetric allocation is determined by channel bandwidth
as shown as well as link distance.

Changing the Link Band
Link Configuration: Maximum Information Rate
You can set separately, the uplink and downlink Maximum Information Rate (MIR) in Mbps or
leave it as Unlimited. The MIR acts as a throttle; leaving the uplink or downlink as Unlimited
commits the link to operating at best effort.
VLAN and Quality of Service
These services are covered respectively in VLAN Functionality and Quality of Service.
6.3.3 Changing the Link Band
Changing the Band in use is always carried out at the link level (not per installed radio unit).
To change the Link Band you must be logged on to the RT‐A(HBS) as Installer. In Installer
mode, the Tools drop‐down menu has an extra function, Change Band.
 To change the Link Band:
1. Click Change Band. A list of available Bands is displayed:
Figure 6‐10: Change or Add Bands
2. Select the required Band and click OK. For our purposes, we choose 5.720‐5.960
GHz Universal. The band is highlighted and right button is enabled.

Figure 6‐11: Add/Change Band dialog
3. Click the right button. The following window opens:
4. Here you may chose the working channel bandwidth and channel selection as in the
activation process. (We will set CBW to 80 MHz and ACS fully selected.) Click OK to
accept your choice. You are returned to the display in Figure 6‐11.
5. Click OK again. The following cautionary message is displayed:

6. Click Yes to continue. After a short delay, you are offered a final confirmation:
7. Click OK. A link re‐sync follows. Here is the final result:
Having set the channel bandwidth and operating channels earlier, there is no need
for de‐activation and re‐activation.
You may also add new Bands by clicking the Add Bands button. There are several provisos to
this:
• Additional Bands must be available for your hardware

• Such additional Bands must be available within the framework of your local regulations
The foregoing applies to both regulated and unregulated Bands.
 To obtain and install additional bands:
1. As Installer, open the window of Figure 6‐10 above, and click Add Bands. The fol‐
lowing instruction panel is displayed:
Figure 6‐12: Add Bands Instructions Panel
The serial numbers displayed are those of the ODUs in the link. Click Copy to Clip‐
board.
2. Now carry out steps 2 to 5 in Figure 6‐12. Step 2 will take you to a Web page, which
contains a form like this:

3. Fill out the requested details. Remember to terminate the dialog by clicking the Get
Key button.
4. The results of your request will be displayed with further instructions.
A few minutes later, you should receive an email, containing in its body, a list of
license keys.

Configuring AES 256 Encryption Support
You may see error messages in the Status Column such as Band not
supported or Serial not found. Supported bands typically reflect your
local regulations. Check missing serial numbers with RADWIN Customer
Service.
5. Copy and Paste the license keys into a plain text file and save it to a safe known
place.
6. Open the Configure | Operations tab for either radio unit.
Figure 6‐13: Using the Master ODU (HBS) Configuration button for licensing
Check the License File button and navigate to the file you saved in the last step.
7. Click Activate. The next time you enter the Change Bands tab, the new bands will
be available.
6.3.4 Configuring AES 256 Encryption Support
AES 256 support is available for the RADWIN 2000 C+ only.
AES 256 support is enabled from the RT‐A(HBS).
 To enable AES 256 Encryption support for a sector:
1. Ensure that the RT‐A(HBS) is hardware ready for AES 256: From the HBS Configura‐
tion button, open the Inventory page and check that the hardware version is 9 or
higher. Open a text file and copy/paste the serial number of the RT‐A(HBS) to it.
2. Repeat step 1 for the RT‐B(HSU).
3. Save the text file and send it to your equipment supplier with your license purchase
order.
4. You will receive by return email a text attachment showing serial number and
license key. Save the file to a known safe location.
5. At either ODU, open the Configuration | Operations tab. Check the License File
button and navigate to the file you saved in the previous step.
6. Click Activate. Yo can confirm activation by opening the Security tab. The AES 265
check box, previously grayed out, is now available.

Configuring AES 256 Encryption Support
Check it to commence AES 256 Encryption.
You can confirm AES 256 support per ODU by looking at the Encryption icon at the bottom
right hand corner of the main window as shown in the following tables:
Table 6‐1: AES Indicators for a link
AES Level
Licensed for AES 256 RT‐B(HSU) Encryption Icon
Supported
128 N/A
No
256
Yes
In addition, the Security tab on the RT‐B(HSU) Configuration widow (from the RT‐A(HBS) or
direct logon) will indicate when appropriate, that AES 256 is enabled:

Configuration with Telnet
6.4 Configuration with Telnet
6.4.1 Telnet Access to Either ODU
A Telnet terminal can be used to configure and monitor the RADWIN 2000+ Series radio units.
To start a Telnet session on the RT‐A(HBS), use telnet <ODU_IP>.
For example, if you run Telnet as follows,
telnet 10.104.3.2
you will be asked for a user name and password.
The Telnet log on user name is the password that you used to enter the RADWIN Manager
(for example, the default: admin). The Telnet password is the corresponding Community
string (default: netman).
Figure 6‐14: Telnet session log on to the RT‐A(HBS)
A Read‐Only Community string allows you to use display commands only whereas a Read‐
Write Community string allows you to use display commands and execute set commands.
Supported radio unit (ODU) Telnet commands are shown in Table 6‐2 to Table 6‐4. They apply
to both RT‐A(HBS) and RT‐B(HSU)
Table 6‐2: ODU Telnet ‐ Display Commands
Command Explanation
Displays radio unit product name, Name, Location,
display inventory hardware and software revisions, uptime, MAC
address.
display management Displays IP, subnet, Gateway, Traps table
display link Displays all static details about the link
display ethernet Displays Port table (State, Status and action)
display ethernet_errors Displays Cable statistics
display ntp Displays Time, Server and Offset

Telnet Access to Either ODU
Table 6‐2: ODU Telnet ‐ Display Commands (Continued)
Command Explanation
Shows the performance monitor tables for each
display PM <interface:AIR,LAN1>
interface according to user defined monitoring
<interval:current,day,month>
intervals
display bands Displays available bands
display ldpc_mode On or off; default off
Table 6‐3: ODU Telnet ‐ Set Immediate Commands
Command Explanation
Set the radio unit IP address, subnet mask and
set ip <ipaddr> <subnetMask>
gateway. The user must reset the radio unit after the
<gateway>
command completion
set trap <index:1‐10> <ipaddr> Set a specific trap from the traps table (e.g. set trap 3
<port:0‐65535> 192.168.101 162)
set readpw <oldpasswd> <passwd> Set the read access password (Read Community)
Set the read‐write access password (Read‐Write
set writepw <oldpasswd> <passwd>
Community)
set trappw <oldpasswd> <passwd> Set the trap Community string
set buzzer <mode> mode: 0 = off, 1 = auto, 2 = on
set tpc<power:Value between Set the radio unit Tx Power. If a wrong value is
minimal Tx power, and maximal Tx entered, both min and max values shall be displayed
power> in the error reply
set name <new name> Set the name of the link
set location <new location> Set the name of the location
set contact <new contact> Set the name of the site manager
set ethernet <port:LAN1>
<mode:AUTO,10H,10F,100H,100F,D Set the mode and speed of the Ethernet port
ISABLE>
Resets the radio unit. The user is warned that the
command will reset the radio unit. A new Telnet
reboot
session to the radio unit may be opened after the
reset is complete.
help Displays the available commands

Telnet Access to Either ODU
Table 6‐4: ODU Telnet ‐ Set Commands requiring Reset
Command Explanation
set secId <SectorID> Set new sector ID
set ldpc_mode <mode:on,off> Sets ldpc mode

Chapter 7: Link Configuration
in Detail
In this chapter we describe the Link Configuration window in detail, noting differences
between the RT‐A(HBS) and RT‐B(HSU). We also comment briefly on the last four items in
Table 7‐1.
7.2 Link Tool Bar
Here are the link tool bars and their functions:
Figure 7‐1: Link Tool Bars
Table 7‐1: Link Buttons - Description

Applies to which side of
Menu Button Purpose / Reference
the link?
Both Open the Link Configuration Window
Both Recent Events
Both Active Alarms
RT‐A(HBS) Deactivate RT‐A(HBS)
Both Reset the ODU

Link Configuration Window
Table 7‐1: Link Buttons - Description

Applies to which side of
Menu Button Purpose / Reference
the link?
RT‐B(HSU) Deregister RT‐B(HSU)
RT‐B(HSU) Suspend a Deregistered RT‐B(HSU)
7.3 Link Configuration Window
The Link Configuration windows are slightly different for the RT‐A(HBS) and RT‐B(HSU).
Figure 7‐2: Link Configuration window ‐ RT‐A(HBS)

Link Configuration Window
Figure 7‐3: Link Configuration window ‐ RT‐B(HSU)
The RT‐A(HBS) side has a tab to configure HSS. Otherwise, the side tabs have identical
functionality for both sides. Further, the tool bars are common to both, and have identical
functionality.

Configuration Tabs
7.4 Configuration Tabs
7.4.1 System
7.4.2 Tx & Antenna
You may use this tab at either side to further fine‐tune Tx Power parameters set at Activation
time.

Hub Site Sync (RT‐A(HBS) Only)
Changing the Tx and Antenna parameters will take immediate effect without service
interruption.
7.4.3 Hub Site Sync (RT‐A(HBS) Only)
See Hub Site Synchronization for details about configuring HSS.
Only RADWIN 2000+ Series RT‐A(HBS) units can be co‐located with other
base stations. RT‐B(HSU)s cannot be collocated.
7.4.4 Management
IP Addresses
Here is a “classic” IPv4 configuration:

Management
IP Version
You may configure a link for IPv4, IPv6 or both:
Here we choose both and enter the IPv6 addresses:

Management
Using both IP versions is useful in conjunction with applications that do not fully support IPv6.
here are the results of setting IPv6 addresses for both sides and enabling Show IP to IPv6 in
Preferences | Monitor:

Management
Trap Destinations
 To change a trap IP address:
1. Open an entry with its edit button:
The following entry window is displayed:
2. Enter the Trap Destination IP Address and Port. It could be the IP address of the
managing computer. The events log will be stored at the addresses chosen.
IP addresses may be IPv4 or IPv6.

Management
3. For Security model you may choose between SNMPv1 or SNMPv3. The choice is site
dependent. If you choose SNMPv1, you may only enter an IP address and port
number. For SNMPv3, you should supply a user name and password:
4. Click OK to save your choice.
Note that for each active trap destination, the Clear Trap Destination button is enabled:
VLAN for Management
Management VLAN Configuration
Figure 7‐4: VLAN for Management
VLAN IDs are used by RADWIN products in three separate contexts:
Management VLAN, Traffic VLAN and Ethernet Ring. It is recommended
that you use different VLAN IDs for each context.
VLAN Management enables separation of user traffic from management traffic whenever
such separation is required. It is recommended that each member of a sector be configured
with different VLAN IDs for management traffic. (This reduces your chances of accidentally
locking yourself out of the link.)
 To enable VLAN for management:
1. In the window of Figure 7‐4, check the Enabled box.
2. Enter a VLAN ID. Its value should be between 2 and 4094.
After entering the VLAN ID, only packets with the specified VLAN ID are processed
for management purposes by the radio unit. This includes all the protocols sup‐

Management
ported by the radio unit (ICMP, SNMP, Telnet and NTP). Using VLAN for management
traffic affects all types of management connections (local, network and over the
air).
3. Enter a Priority number between 0 and 7.
The VLAN priority is used for the traffic sent from the ODU to the managing com‐
puter.
4. Change the VLAN ID and Priority of the managing computer NIC to be the same as
those of steps 2 and 3 respectively.
5. Click Apply or OK.
Lost or forgotten VLAN ID
If the VLAN ID is forgotten or there is no VLAN traffic connected to the ODU, then reset the
relevant ODU.
If the managing computer is directly connected to an ODU, and you enable
management VLAN, you will lose connectivity. To log on again, You will
need to configure the managing computer NIC to use the management
VLAN number.
During the first two minutes of connection, the ODU uses management
packets both with and without VLAN. You may use this period to
reconfigure the VLAN ID and priority.
Supported Protocols
Supported protocols are shown in Figure 7‐5:
Figure 7‐5: Supported protocols
SNMP support is permanently enabled. You may choose between SNMPv1, SNMPv3 or both.
If you choose SNMPv3, you will be offered the following cautionary message:

Management
For a link managed as part of a network, direct access using Telnet is considered to be a
security breach. Telnet access may be enabled or disabled by clicking the Protocol tab and
enabling/disabling Telnet access using the Telnet check‐box. Similar considerations apply to
access via the Web Interface.
• For further details about Telnet access see Configuration with Telnet.
• For further details about the Web Interface, see Using the Web Interface.
Telnet and Web Interface access modes when available, are site specific. If for example, you
want Telnet access from a specific site, you should enable it for that site and disable it for
others.
Conversely, If the Telnet or Web Interface access modes pose a general security risk, you must
disable them for each site separately.
Multiuser Support under SNMPv3
If you chose SNMPv3 or both versions, you are asked to log on again:
For the first log‐on under SNMPv3, use as password, the User Name, admin. There is one
change to the main window. The title bar now shows the SNMPv3 user name:

Management
Further, there is an additional button, SNMPv3 Users, in the Management window:
Using the new button opens up the following entry list:

Management
To make any of the following changes, you must be logged on as user admin. The SNMPv3
passwords for admin and operator are as follows:
Table 7‐2: SNMPv3 predefined users
User Name Password Profile
admin netwireless Read Write
operator netpublic Read Only
 To add an SNMPv3 user:
1. Click the right hand edit icon on any empty line of the list:
2. An Edit window is displayed:
Figure 7‐6: Add or Edit a user
3. Enter a user name and password. Confirm the password as indicated.
4. Choose a Profile:
• Read Only provides Observer level log‐on access.
• Read Write provides Operator level log‐on access
• Disabled stores the user details in the data base for future use. It must be
changed to Read Only or Read Write to become usable.

Management
5. Click OK to accept. Here is the result of adding one more Read Write user, one Read
Only User and one “Disabled” user:
Figure 7‐7: SNMPv3 users list
 To edit an existing user:
1. Use the same procedure as above to choose a user for editing. For illustration, we
will correct the spelling of Teleman’s name:
2. Click the edit button:

Management
3. Correct the spelling of the name:
4. Enter and confirm the user’s password:
5. Click OK to finish. The change will be reflected in the display of Figure 7‐7.
6. Use the same method to change the user’s profile.
Passwords are never displayed as clear text. If a user looses his password,
the only way that the situation can be corrected is to delete the user name
and re‐create the same user name with another password.
Note
Logging on as a SNMPv3 User
 To log off as user admin and log on as a Read Write profile user (Vivaldi):
1. Here is the default log‐on dialog:

Management
Figure 7‐8: Default SNMP log‐on dialog
2. In the right hand window, enter the user name (Vivaldi) and password.
3. For a Read Write profile user, you may log on as any user type (Observer, Operator,
Installer). For example, log on Vivaldi as Operator. Since Vivaldi belongs to the Read
Write profile, in the left hand window, use admin for the Password and leave User
Type as is. (If necessary, you can use wireless and Installer, respectively.)
In the main window we see the user name in the title bar:

Management
 To log on as a Read Only profile user (Handel):
1. In Figure 7‐8, log on as Handel instead of Vivaldi.
2. On the left hand side, set user type to Installer and password to wireless.
In the main window we see the user name in the title bar as follows:
The rule is, that the logged on privilege level will be the lowest of the SNMPv3 user type and
the RADWIN Manager user type.

Management
Inventory
You might like to capture or copy the information here:
The information listed under ODU shows the parameters relating to the radio unit. Use the
button to the right of the Serial Number field to copy the serial number to the clipboard. The
Inventory information will be required by Customer Service should you require assistance.
The information listed under SFP (if this appears for your product) shows the parameters of
the SFP unit inserted in the appropriate LAN port.

Management
Security
Figure 7‐9: Sector Security settings ‐ RT‐A(HBS)
The Security dialog enables you to change the Link Password and the SNMP Community
strings.
Changing the Link Password
This item is available as follows:
• At the RT‐A(HBS)
• At an isolated RT‐B(HSU)
Here are the details:
The default password is wireless‐p2mp. Optionally, you can change the link password as
explained here.
 To change the link password:
1. Open the Security tab (Figure 7‐9).
The Change Link Password dialog box opens.
Use the Hide characters check box for maximum security

Management
Figure 7‐10: Change Link Password dialog box
2. Enter the current link password (The default link password for a new ODU is
wireless‐p2mp).
If you have forgotten the Link Password, click the Forgotten Link Password button.
The following window is displayed:
Figure 7‐11: Lost or forgotten Link Password recovery
Follow the instructions to use the Alternative Link Password, and click OK to finish.
You are returned to the window in Figure 7‐10 above. Continue with the next step.
3. Enter a new password.
4. Retype the new password in the Confirm field.
5. Click OK.
6. Click Yes when asked if you want to change the link password.
7. Click OK at the Password changed success message.
• A link password must contain at least eight but no more than 16 char‐
acters excluding SPACE, TAB, and any of “>#@|*?;.”
• Restoring Factory Defaults returns the Link Password to wireless‐
p2mp.

Management
RADWIN Manager Community Strings
The ODU communicates with the RADWIN Manager using the SNMPv1 or SNMPv3 protocol.
The SNMPv1 protocol defines three types of communities:
• Read‐Only for retrieving information from the ODU
• Read‐Write to configure and control the ODU
• Trap used by the ODU to issue traps.
The Community string must be entered at log on. You must know the password and the
correct Community string to gain access to the system. You may have read‐only privileges. It is
not possible to manage the ODU if the read‐write or the read Community values are
forgotten. A new Community value may be obtained from RADWIN Customer Service for the
purpose of setting new Community. You must also have available the serial number or the
MAC address of the ODU.
The read‐write Community strings and read‐only Community strings have a minimum of five
alphanumeric characters. (bru1 and bru4097 are not permitted). Changing the trap
Community is optional and is done by clicking the check box.
Editing SNMPv1 Community Strings
When editing these strings, both read‐write and read‐only communities must be defined.
Upon logging on for the first time, use the following as the current Community:
• For Read‐Write Community, use netman.
• For Read‐Only Community, use public.
• For Trap Community, use public
 To change a Community string:
1. Type the current read‐write Community (default is netman).
2. Choose the communities to be changed by clicking the check box.
3. Type the new Community string and re‐type to confirm. A community string must
contain at least five and no more than 32 characters excluding SPACE, TAB, and any
of “>#@|*?;."
4. Click OK to save.
Editing SNMPv3 Passwords
To commence the process, you must enter the current Read‐Write Community password as
shown in the first field of Figure 7‐12 below. Change the Read‐Write an d Read‐Only
passwords as indicated. A password must be between 8 and 31 characters long. The same
character restrictions for the SNMPv1 community strings also apply here.

Management
Figure 7‐12: Changing the Community Strings/Passwords
Forgotten SNMPv1 Community String
If the read‐write Community string is unknown, an alternative Community key can be used.
The alternative Community key is unique per ODU and can be used only to change the
Community strings. The alternative Community key is supplied with the product, and should
be kept in a safe place.
If both the read‐write Community and the alternative Community key are unavailable, then
an alternative Community key can be obtained from RADWIN Customer Service using the
ODU serial number or MAC address. The serial number is located on the product label. The
serial number and the MAC address are displayed in the Link Configuration inventory tab.
When you have the alternative Community key, click the Forgot Community button and enter
the Alternative Community key (Figure 7‐13). Then change the read‐write Community string.

Management
Figure 7‐13: Alternative Community Dialog box
Date & Time
The ODU maintains a date and time. The date and time should be synchronized with any
Network Time Protocol (NTP) version 3 compatible server.
During power‐up the ODU attempts to configure the initial date and time using an NTP Server.
If the server IP address is not configured or is not reachable, a default time is set.
When configuring the NTP Server IP address, you should also configure the offset from the
Universal Coordinated Time (UTC). If there is no server available, you can either set the date
and time, or you can set it to use the date and time from the managing computer. Note that
manual setting is not recommended since it will be overridden by a reset, power up, or
synchronization with an NTP Server.
The NTP uses UDP port 123. If a firewall is configured between the ODU
and the NTP Server this port must be opened.
It can take up to 8 minutes for the NTP to synchronize the ODU date and
time.
 To set the date and time:
1. Determine the IP address of the NTP server to be used.
2. Test it for connectivity using the command, for example:
w32tm /stripchart /computer:216.218.192.202

Management
Figure 7‐14: Date and Time Configuration
3. If entering an IP address for the NTP Server, click Clear, and then enter the new
address.
4. Set the Offset value in minutes ahead or behind GMT1.
5. To manually set the date and time, click Change and edit the new values.
Figure 7‐15: Change Date and Time
6. Click OK to return to the Configuration dialog.
1. Greenwich Mean Time

Management
Ethernet
Figure 7‐16: Setting Ethernet services
Aging Time
The RT‐A(HBS) works in Bridge Mode. In Bridge mode the ODU performs both learning and
aging, forwarding only relevant packets over the sector. The aging time of the ODU is by
default, 300 seconds.
Ethernet Ports Configuration
For the RADWIN 2000 A+, RADWIN 2000 C+, and RADWIN 2000 D+, the Port will appear as
LAN1. For the RADWIN 2000i, two ports will appear: LAN1 and LAN2 (SFP), relating to the
ports on front panel of the unit.
The Ethernet port mode is configurable for line speed (10/100/1000BaseT) and duplex mode
(half or full duplex).
Line speed 1000BaseT is only available if the ODU is connected to A GbE PoE device.

Management
An Auto Detect feature is provided, whereby the line speed and duplex mode are detected
automatically using auto‐negotiation. Use manual configuration when attached external
equipment does not support auto‐negotiation. The default setting is Auto Detect.
The icon next to the CRC error count may be clicked to reset the counter to zero.
Do not reconfigure the port that is used for the managing computer
connection, since a wrong configuration can cause a management
disconnection or Ethernet services interruption.
 To configure the Ethernet Mode:
• In the Ethernet Ports Configuration pane, use the drop‐down menus to choose the
required modes.
Operations
Figure 7‐17: Restore Factory Settings, License Activation and Change ODU Mode

Link Configuration Tool Bar
Reverting to Factory Settings
Clicking the Restore Defaults button opens the following self explanatory dialog:
License Activation
Some product enhancements require a license key or a file of license keys. For a single key,
just enter the supplied license Key and click Activate. If you have a list of them (a text file) you
will need to use the License File option.
In some instances it may involve purchasing the relevant license from RADWIN. Contact
Customer Service for details.
Change ODU Mode
When you set up your link, you defined one unit as an RT‐A(HBS) (Master ODU) and the other
as an RT‐B(HSU) (Slave ODU). If you need to change this, use this option.
Changing the ODU Mode will change the fundamental behavior of the specific unit being
changed.
7.4.5 Link Configuration Tool Bar
Backup and Restore
The Backup and Restore buttons provide for backup and restore of the ODU software.For
further information about Backup and Restore, see Software Backup and Restore.
Buzzer
The Buzzer button sets or mutes the buzzer.
The buzzer tone is primarily used for ODU antenna alignment. The default setting is Auto.
Off ‐ Turn off buzzer
On ‐ Turn on buzzer

Deactivate RT‐A(HBS)
Auto ‐ Buzzer responds according to signal strength. This is the setting used for antenna
alignment. For details see Antenna Alignment on page 4‐39
Advanced Auto ‐ Buzzer on while link down, remains on for an extra two minutes.
Refresh
The Refresh button restores the current window to its previous state abandoning any changes
you made, provided that you did not click Apply or OK.
7.5 Deactivate RT‐A(HBS)
Deactivating the RT‐A(HBS) halts traffic over the link and drops it back to the default
transmission mode prior to configuration with one exception: The RT‐B(HSU) remains
“registered” but inaccessible over the air. You can reactivate the RT‐A(HBS) without need to
re‐register the RT‐B(HSU). All of the RT‐B(HSU) configuration settings are preserved.
7.6 Deregister RT‐B(HSU)
Deregistering the RT‐B(HSU) stops link traffics but leaves it accessible over the air from the RT‐
A(HBS). All of the RT‐B(HSU) tool bar functions are available.
7.7 Suspend a Deregistered RT‐B(HSU)
You may break the link (cause a full sync loss) to the deregistered RT‐B(HSU) for a fixed
amount of time.
7.8 Reset the ODU
The reset functions are equivalent to powering the ODU down and then powering it up again.

Chapter 8: Monitoring and
Diagnostics
The RADWIN Manager application enables you to monitor the link between the Master ODU
and Slave ODU, as well as perform basic diagnostic operations such as throughput testing.
This chapter covers:
• Retrieving Link Information
• Throughput Checking
• Recent Events
• Performance Monitoring
• Manager Traps
• Active Alarms
Other relevant facilities include:
• Link Budget Calculator
• Customer Service
8.1 Retrieving Link Information
The Get Diagnostics feature collects and writes link and Manager information from selected
sites into a text file. The file information can be used for diagnostics and should be sent to
RADWIN Customer Service to expedite assistance.
The following table lists link and system information that can be monitored.
Table 8‐1: Get Diagnostics Data and Description
Data Description
System Data General information about the system
• List of system events including those from other sites if this
Events Log site is defined as the trap destination
• Last 256 events from all sites

Retrieving Link Information
Table 8‐1: Get Diagnostics Data and Description (Continued)
Data Description
Link Information Information about the RT‐A(HBS) and RT‐B(HSU) settings
Site Configuration Data about the site parameters
Monitor Detailed event data record
Active Alarms Active Alarms are raised for any event affecting availability or
Service Configuration Settings: MIMO, Tx Ratio, MIR, VLAN, QoS
Performance Monitor Network performance data over defined time periods ‐ ‐ every 15
Spectrum Analysis For RT‐A(HBS), selected RT‐B(HSU)s and general interference
 To get diagnostics:
1. Click the Get Diagnostics button:
Figure 8‐1: Get Diagnostics window
2. Select or deselect the data options. If the file is to be sent to RADWIN Customer
Service leave all options checked.
3. Click File Path to specify the file name and older in which you want to save the file
and then click Run to save the information.
On completion, the status of the checked items is confirmed:

Throughput Checking
The content of the Diagnostics report is an aggregate of all the more specific reports
discussed below. It is primarily intended for use by RADWIN Customer Service.
The Spectrum Analysis output is available directly from the Spectrum
View utility as a CSV file (see Spectrum View). The format in the
Diagnostics report is intended for use by RADWIN Customer Service.
The Spectrum Analysis section of the Diagnostics report is based on the
last available spectrum analysis (if any). If you are submitting a support
request involving interference issues, or if you are specifically asked by
Customer Service to submit a Diagnostics report containing a recent
spectrum analysis, you should carry out the analysis in accordance with
the Spectrum View instructions prior to using the Get Diagnostics facility.
8.2 Throughput Checking
In this mode, RADWIN 2000+ Series estimates Ethernet throughput by filling frames over the
air to maximum for 30 seconds. This mode should not influence service.
 To use Throughput Checking:
1. Chose Estimated Throughput from the Tools tab:

Recent Events
2. You are asked to enter the testing period:
3. Enter the required time and click OK to continue. The Ethernet services area
changes appearance and the estimated throughput is displayed:
At the end of 30 seconds, the display reverts to normal.
8.3 Recent Events
The Recent Events log records system failures, loss of synchronization, loss of signal,
compatibility problems and other fault conditions and events.
Alarms (traps) are displayed in the Events Log in the lower panel of the main window. The
Events Log may be saved as a text file.

Recent Events
The foregoing event types include events from all links for which this
managing computer has been defined as the traps address. Only events
from RADWIN equipment will be shown.
The Events Log includes the following fields:
» Sequential number (ID)
» Date and time stamp
» Message
» Trap source
» IP address of the ODU that initiated alarm.
You may filter the events shown by choosing All or Internal.
A full report may be seem by clicking Recent Events in either ODU tool bar:
In each case the report has the same format:
Here is a more readable enlargement of the table area:

Performance Monitoring
The left button may be used to save the report to a file.
8.4 Performance Monitoring
8.4.1 Obtaining Reports
RADWIN 2000+ Series Performance Monitoring constantly monitors traffic over the radio link
and collects statistics data for the air interface and Ethernet ports. It does so continuously,
even when the RADWIN Manager is not connected. The report is obtained from the Tools tab:
The on‐screen and generated reports have the same general formats, but there are
differences in what is reported.
The Performance Monitoring window offers the following button menu:
You can choose monitoring for Uplink or Downlink:
Choose the data period required with the 15 Minutes button.

Obtaining Reports
• Current gives you the latest entry.
• 15 Minutes provides data in a scroll down list in 15 minute intervals
• Daily (24 hours) shows results for the last 30 days at midnight.
The Threshold button enables you to set the upper traffic thresholds for reporting. Traffic
conditions above the threshold indicate congestion and probably lost frames. The thresholds
are set separately for uplink and downlink:
Figure 8‐2: Setting the upper traffic threshold ‐ Downlink
To get data for display, click Get Data. The process may take a few seconds.
Here is an extract for the downlink Performance Monitoring report based on 15 minutes
recording:

Obtaining Reports
Figure 8‐3: Downlink ‐ Performance Monitoring report ‐ Valid data
The on‐screen report may be scrolled vertically and horizontally. The meaning of the column
headings is shown in the following table:
Table 8‐2: Performance Monitoring Fields
Abbreviation
Column Heading Description
Meaning
Green checkmark for current and valid; Red cross for
invalidated data (See example below). Note that the
Integrity Valid data flag Performance Monitoring data is not valid if not all the
values were stored (e.g., due to clock changes within
the interval or power up reset)
Data are recorded every 15 minutes; the last 30 days
Date & Time Time stamp
of recordings are maintained. Roll‐over is at midnight.
Unavailable
UAS Seconds in which the interface was out of service.
Seconds
The number of seconds in which there was at least
ES Errored seconds
one error block.
Severe Errored The number of seconds in which the service quality
SES
Seconds was low as determined by the BBER threshold.
Background
BBE The number of errored blocks in an interval.
Block Error
Received The number of Megabytes received at the specified
Rx MBytes
Mbytes port within the interval
Transmitted The number of Megabytes transmitted at the
Tx MBytes
Mbytes specified port within the interval.
Above Traffic Threshold set in Seconds count when actual traffic exceeded the
Thresh Figure 8‐2 threshold
The number of seconds that the configured Ethernet
Active Seconds
service is active

More on the Thresholds
Data becomes invalidated following a reset. In the example below, the Slave ODU was reset
shortly after 08:45. All data prior to that time becomes invalidated. The only valid items are
the recordings following the re‐sync.
Figure 8‐4: Performance Monitoring report ‐ Showing invalid data
Use the Save button to store the current data to a file and the Clear button to delete currently
stored performance data.
8.4.2 More on the Thresholds
RSL Thresholds
Two RSL Thresholds can be defined. They are used as an indicator of problems in the radio
channel. You can check the RSS from the Link Budget Calculator results during installation.
Values of ‐5dB and ‐8dB from the current RSS are typical.
TSL Threshold
A counter is maintained, of the number of second intervals during which Tx power exceeds
this threshold.
BBER Threshold
The Background Block Error Ratio is measured as a percentage. The threshold can be set from
0.1% up to 50%.
An 8% threshold is recommended. If there are no problems during the interval, then for that
threshold, the recommended BBER value should be 0. Since the system provides a lossless
Ethernet service, there is throughput degradation in case of interference. The degradation is
proportional to the BBER.
Ethernet Thresholds ‐ Capacity
This is used as a basis for checking adherence to a Service Level Agreement. It is the number
of seconds count that the link capacity falls bellow the threshold.
Ethernet Thresholds ‐ Traffic
The number of seconds count that received traffic exceeded this threshold. It can be used to
measure traffic peaks.

Manager Traps
8.5 Manager Traps
The RADWIN Manager application issues traps to indicate various events, displayed in the
Events Log.
Table 8‐3: RADWIN Manager Trap Messages
Trap Message Severity Remarks
Cannot bind to trap service port. Port Warning RADWIN Manager will not catch any

162 already in use by ProcessName traps from the ODU, some other
(pid: ProcessId) application has grabbed this port.
Device unreachable! Error Check connectivity to ODU
Connected to <site_name> Information
<site_name> Site will be reset. Information
Restore Factory Default Settings in Information
process on Site <site_name>
Factory Settings: The process was not Warning Factory setting failed due to
finished due to connection issues. connectivity problem to ODU
Reset: The process was not finished Warning Factory setting failed due to
due to connection issues. connectivity problem to target ‐ ODU
will not be reset
Cannot Write to Monitor file. There is Warning Free some space on disk on the
not enough space on the disk. managing computer and retry
Windows Error: <error_ID>. Cannot Warning Operating System error on the
Write to Monitor file. managing computer
Identical IP addresses at Warning Set up a different IP to each site
<local_site_name> and
<remote_site_name>
The Product is not identified at the Warning RADWIN Manager is incompatible
<local_site_name> site. with the ODU software version
The Product is not identified at the Warning
<remote_site_name> site.
The Product is not identified at both Warning
sites.
Product Not Identified! Warning

Active Alarms
Table 8‐3: RADWIN Manager Trap Messages (Continued)
Trap Message Severity Remarks
The Manager identified a newer ODU Warning ODU release is newer than RADWIN

release at the <remote_site_name> Manager release.
site. Wizards are not available. RADWIN
Manager will be used just for
monitoring. Upgrade the RADWIN
Manager. (You will get this message
as a pop up)
The Manager identified a newer ODU Warning
release at the <local_site_name>
site.
Newer Version identified at the Warning ODU release is newer than RADWIN
<local_site_name> site. Manager release.
Wizards are not available. RADWIN
Manager will be used just for
monitoring. Upgrade the RADWIN
Manager.
Newer Version identified at the Warning
<remote_site_name> site.
Newer Version Identified! Warning
8.6 Active Alarms
Active Alarms are raised for any event affecting availability or quality of service. They are site
specific and are obtained using the site tool bar:
Here is an example:
Here is the table part in more detail:

Other Diagnostic Aids
Current Active Alarms may be saved to a file. The list displayed will not be updated unless you
click Refresh.
8.7 Other Diagnostic Aids
8.7.1 Link Budget Calculator
The Link Budget Calculator is part of the RADWIN Manager software and is found in the Help
menu. This useful utility enables you to calculate the expected performance of the wireless
link and the possible configurations for a specific link range including antenna size, cable loss
and climate conditions. For full details, see Link Budget Calculator.
 To run the Link Budget Calculator from the Windows Start Menu:
• Go to Start | Programs | RADWIN Manager | Link Budget Calculator
8.7.2 Online Help
Online help can be accessed from the Help menu on the main window of the RADWIN
Manager. Using most common Web browsers, it may also be run going to
Start | Programs | RADWIN Manager | User Manual RADWIN 5000
8.7.3 Customer Service
Customer support for this product can be obtained from the local VAR, Integrator or
distributor from whom it was purchased.
For further information, please contact the RADWIN distributor nearest to you or one of
RADWIN's offices worldwide.

Part 4: Site Synchronization
Release 4.2.40
Chapter 9: Hub Site
Synchronization
This chapter describes what is hub site synchronization, why it is needed, and an overview of
the various ways it is implemented in a RADWIN radio system.
9.2 What is Hub Site Synchronization (HSS)?
When several radio units are co‐located at a common site, interference may occur from one
unit to another. This interference, if it occurs, happens when at a given moment in time one
unit is transmitting, but the other is receiving: the receiving unit may detect the transmitting
signals of its immediate neighbor instead of (or in addition to) signals from where it should.
Figure 9‐1 illustrates interference caused by non‐synchronized co‐located units: If Unit1 is
receiving at a given moment from Unit1A, and at that same moment Unit2 is transmitting to
Unit2A, Unit1 might receive signals directly from Unit2.

What is Hub Site Synchronization (HSS)?
Unit1 Unit1A
Unit2
Unit2A
Figure 9‐1: Interference caused by collocated units
This interference can be mitigated by using different frequencies for the Unit1/1A pair and
the Unit2/2A pair, but this not always feasible.
Hub Site Synchronization (HSS) is a technique that prevents this interference from occurring
without requiring the co‐located units to use different frequencies. This synchronization
ensures that all co‐located units transmit and receive at the same time, as illustrated below:
Figure 9‐2: Collocated units using Hub Site Synchronization (1)

HSS Implementation
Figure 9‐3: Collocated units using Hub Site Synchronization (2)
9.3 HSS Implementation
HSS is implemented using a master (which transmits synchronization pulses), where the rest
of the co‐located units are defined as clients. These client radio units synchronize their
transmission to the pulses received by the master.
HSS can be carried out between all co‐located RADWIN radio products, so long as they are
defined as a base station.
9.3.1 Radio Frame Pattern
The synchronization signal is transmitted once per a specific time period, and determines
when the co‐located units will transmit and when they will receive. This cycle of transmit and
receive is called the Radio Frame Pattern. Figure 9‐4 shows the Radio Frame Pattern of 3 co‐
located outdoor units (ODUs).

Figure 9‐4: Radio Frame Pattern
If the master is one of the co‐located ODUs, it is called the Hub Site Master (HSM). The other
co‐located ODUs are called the Hub Site Clients (HSC).

HSS Types
Although the master unit can be defined as one of the co‐located radio units, a GPS signal can
also furnish a synchronization signal. In this case, all the co‐located units are clients, and the
“master” is the GPS signal source.
9.3.2 HSS Types
RADWIN offers several types of HSS:
Serial HSS
The RADWIN Serial Hub Site Synchronization (SHSS) method uses an external HSS unit
that is connected between the HSS master radio unit to all collocated radio units; this
cable carries the synchronization pulses sent to each radio unit, which synchronize
their transmission with each other. SHSS is covered in Serial Hub Site Synchronization.
SHSS can be used with the RADWIN 2000 C+ and RADWIN 2000 D+ only.
Ethernet HSS
The Ethernet HSS (HSSoE) method connects the co‐located radio units via an ethernet
connection. One co‐located unit is defined as the HSS master, and it sends its synchro‐
nization pulses to the HSS clients via the ethernet connection. HSSoE is covered in Hub
Site Synchronization over Ethernet.
GPS HSS
The GHSS method uses a GPS signal as the master, and all co‐located radio units are
defined as clients. For the RADWIN 2000 A+, RADWIN 2000 C+, and RADWIN 2000 D+,
an additional GPS unit is required to receive the GPS signals. For the RADWIN 2000i,
no such unit is required as it has an internal GPS capability. GHSS is covered in GPS
Hub Site Synchronization.

Chapter 10: Serial Hub Site
Synchronization
This chapter describes Serial hub site synchronization (SHSS), and how to implement it.
10.2 SHSS Hardware Installation
SHSS can be used with the RADWIN 2000 C+ or RADWIN 2000 D+ only.
10.2.1 Connecting an HSS Unit
The HSS Unit is a compact, weatherproof (IP67) connector box that is installed on the same
mast as the ODUs. All collocated units using SHSS connect to this box using a CAT‐5e cable. A
single HSS unit can support up to ten collocated ODUs.
The HSS unit is supplied with ten protective covers; any port not in use must be closed with a
protective cover.

Connecting an HSS Unit
Figure 10‐1: HSS Interconnection Unit
• For a single HSS unit, ensure that the collocated units are connected
in sequence from SYNC 1. If an ODU is removed from the hub site,
then all remaining ODUs must be reconnected in order to maintain
the connectivity.
• You may cascade (daisy‐chain) two or more HSS Units with an HSS
cable. The method is described in detail below.
 To connect an ODU to an HSS unit:
1. Unscrew the protective cover from the port marked SYNC 1.
2. Connect the RJ‐45 connector from one end of the prepared CAT‐5e cable to SYNC 1.
3. Connect the other end of the CAT‐5e cable to the ODU connector labeled SYNC.
4. Tighten the protective seal that is on the prepared cable over the RJ‐45 connector.
5. Repeat for all ODUs that are to be collocated at the hub site. The next ODU to be
connected is inserted in SYNC 1, SYNC 2, followed by SYNC 3 and so on.

Using a Single HSS Unit
10.2.2 Using a Single HSS Unit
Figure 10‐2: HSS Wiring schematic
The wiring for a single HSS is shown in Figure 10‐2.
The Sync signal path is as follows: If we set ODU 1 (on SYNC 1) to HSS Master, the Sync signal
path is as shown in Figure 10‐3. The signal travels from ODU 1 to SYNC 1, from SYNC 1 to SYNC
2, from SYNC 2 to ODU 2 and back again. The back and forth paths repeat for the second to
fourth ODU, from left to right. The signal exits the HSS unit at SYNC 5 and terminates in ODU
5.
The choice of the ODU on SYNC 1 as HSS master is not mandatory, but is good practice. If for
example we were to use ODU 3 as HSS master, the Sync signal path would be ODU 3 to SYNC
3, then left and right to SYNC 2 and SYNC 4. It would then propagate to ODUs 2 and 4,
terminating at both ODUs 1 and 5.
Figure 10‐3: HSS sync signal path with ODU 1 as HSS Master

Using More than One HSS Unit
10.2.3 Using More than One HSS Unit
In a large collocation site, several HSS units may be cascaded (daisy‐chained) subject to the
following conditions:
Condition 1: Cabling Sequence
1. Up to nine ODUs may be connected to the first HSS unit using HSS ports SYNC 1, SYNC 2,
SYNC 3,... up to SYNC 9 in order without leaving empty ports.
2. The next available SYNC port of the first HSS unit should be connected to SYNC 10
of the second HSS unit as shown in Figure 10‐4. In the illustration, the next
available port on the first HSS unit is SYNC 6.
3. The second HSS unit may be filled out with up to nine more ODUs in reverse order.
That is, connect SYNC 9, SYNC 8, SYNC 7... as shown in Figure 10‐4.
Figure 10‐4: Cascading two HSS units
4. To add a a further HSS unit: Connect the next available SYNC port from the second
HSS unit in descending order (SYNC 5 in Figure 10‐4) to SYNC 1 of the third HSS
unit.
5. ODUs are connected to the third HSS unit from SYNC 2 as shown in Figure 10‐5, in
ascending order:

ODU/HSS Unit Connection Pinout
Figure 10‐5: Cascading three HSS units
6. If further ODUs are required, observe the convention that additional even
numbered units are populated in descending order from SYNC 9 and odd
numbered HSS units are populated in ascending order from SYNC 2.
If an ODU is disconnected from an HSS unit, then all remaining ODUs must
be moved up or down in order to maintain the connectivity.
Condition 2: Total HSS Cable Length
The total path of the HSS sync pulse must not exceed 300m. This applies no matter how many
HSS units are used. To illustrate the method for calculating the sync pulse path length we
show three examples. For our purpose, let:
Lmn denote the length of the ODU‐HSS unit cable at SYNC n on HSS unit m
Hm be the length of the cable joining HSS unit m to HSS unit m+1
One HSS unit with five collocated ODUs
PathLength = L 11 + 2  L 12 + 2  L 13 + 2  L 14 + L 15
Two cascaded HSS units as shown in Figure 10‐4
PathLength = L 11 + 2  L 12 + 2  L 13 + 2  L 14 +
2  L 15 + H 1 + 2  L 29 + 2  L 28 + 2  L 27 + L 26
Three cascaded HSS units as shown in Figure 10‐5
PathLength = L 11 + 2  L 12 + 2  L 13 + 2  L 14 +
2  L 15 + H 1 + 2  L 29 + 2  L 28 + 2  L 27 + 2  L 26 +
H 2 + 2  L 32 + 2  L 33 + 2  L 34 + L 35
10.3 ODU/HSS Unit Connection Pinout
See Table D‐3.

Sector Configuration and HSS
10.4 Sector Configuration and HSS
The Hub Site Synchronization Settings dialog box appears in the RT‐A(HBS) Site Configuration
window.
Figure 10‐6: HSS Settings window
If you click the Enabled box and choose Serial or Serial and Ethernet:
The central display (with Operational state opened) will look like this:

Sync Status Messages and Color Codes
Figure 10‐7: Setting RT‐A(HBS) as Hub Sync Master or Hub Sync Client
Continue Tx means that the RT‐A(HBS) as a client will continue to work even if there is no HSS
synchronization pulse.
If you select Hub Sync Master and click Apply, the Configuration display changes:
Figure 10‐8: RT‐A(HBS) as Hub Site Master
Setting up the RT‐A(HBS) as a client is carried out in a similar manner.
10.5 Sync Status Messages and Color Codes
The possible External Pulses conditions are shown in the following table:

Table 10‐1: External Pulse Status
Color
HSS Sync Status Meaning
code
Generating Radio unit is HSS master and generates the sync pulse
Detected Radio unit is HSS client and detects the sync pulse
Green
Radio unit is independent (neither HSS master nor client,
Not detected
this would be appropriate for an RT‐B(HSU))
Generating and
Radio unit is HSS master, but other HSS master is present
detected
Generating and
Radio unit is HSS master, but detects an HSS master signal Orange
Improperly
Detected
that is not RFP E.
Not detected Radio unit is HSS client, but no HSS master is present
Radio unit is HSS client, but the HSS master pulse doesn’t fit
Improperly the HSS client as configured. Occurs only for RADWIN 2000
Red
detected C+, RADWIN 2000 D+, and RADWIN 5000, which stop
transmitting.

Chapter 11: Hub Site
Synchronization over Ethernet
This chapter describes Ethernet hub site synchronization (EHSS), and how to implement it.
11.2 RADWIN Ethernet HSS
11.2.1 Ethernet HSS Requirements
The RADWIN Ethernet Hub Site Synchronization (HSSoE) method provides intra‐site
synchronization without the need for external cables or an HSS unit. Sync signals are
exchanged between collocated radios over the regular Ethernet connection.
The Ethernet HSS (HSSoE) method requires Layer 2 Ethernet connectivity between collocated
ODUs. It has two requirements:
• Collocated ODUs providing Ethernet services only, should be connected to an IDU‐H/
HP instead of regular PoE devices. Other simple switches may work with degraded
performance. They are not recommended and problems arising from their use will
not be eligible for any kind of support.
• Collocated RADWIN 2000+ Series class ODUs providing E1/T1 services should use an
IDU‐C or IDU‐E and then be connected to an IDU‐H/HP functioning as a switch. One
of the LAN ports on the IDU‐C or IDU‐E is connected to any of the six IDU‐H/HP PoE
ports or the two LAN ports. (This is possible because the IDU‐C or IDU‐E LAN cable
only uses four pins for data; the power pins are not used so there is no risk of dam‐
age to them.) In this way, up to eight such ODUs may be collocated.
If you are using an IDU‐C0 (GbE) it must be connected to the IDU‐H/HP
LAN port only. Connecting it to the P0E ports will damage the unit and in
any event, it will not work.

HSSoE Concepts
VLAN Tagging should not use the VLAN ID used by HSSoE and vice versa.
11.2.2 HSSoE Concepts
ODUs
For HSSoE purposes, an ODU is any RADWIN radio supporting it, even if the radio is in fact an
indoor unit.
Sync Frames
Sync frames are exchanged between collocated ODUs using Layer‐2 broadcasting.
Domain
To prevent network flooding, each group of collocated ODUs is configured with an internal
“domain name”. The default name must be changed to prevent sync frames being received
over the LAN by another ODU, which could be then mistakenly configured as a client of an
HSS master at the wrong location.
Discovery
Discovery by the HSS master and HSS clients is provided using the following choice of filters:

HSSoE Concepts
Using discovery at the HSS master, you can select only those HSS clients in the HSS master’s
domain; when configuring a new HSS client you may use discovery to pick the correct HSS
master.
VLAN
VLAN is used to separate sync frames from traffic so as to give sync frames highest priority. If
you have collocated ODUs running close to full capacity, failure to do so, would result in
excessive jitter and dropped traffic frames.
By default, the VLAN ID 1997 and priority 7 are reserved for HSS. You may change the VLAN ID
but not the priority.

Installing Collocated HSSoE ODUs
11.3 Installing Collocated HSSoE ODUs
11.3.1 Ethernet Services Only
Use an IDU‐H/HP for the collocated ODUs instead of separate PoE devices.
11.3.2 Ethernet and TDM Services
For RADWIN 2000+ Series class ODUs: To attain Layer 2 connectivity for up to two such ODUs,
you should connect one of the two the IDU‐C (or IDU‐E) LAN ports to the IDU‐H/HP LAN ports.
You may use the second IDU‐C (or IDU‐E) LAN port to connect to a switch.
11.4 Link Configuration and HSSoE
11.4.1 Setup for Illustration
We will show how to set up our demonstration link as HSS master and HSS client in turn. (The
second collocated link is a similar unit, the setup details of which, need not concern us).
11.4.2 Configuring the RT‐A(HBS) as an HSS master
 To configure the RT‐A(HBS) as an HSSoE Master:
1. Log on to the RT‐A(HBS).
2. Open the Configure | Hub Site Sync tab.

Configuring the RT‐A(HBS) as an HSS master
Figure 11‐1: HSS Settings window
3. Check the Enabled box. The grayed out bottom part of the window in Figure 11‐1 is
enabled.

Figure 11‐2: Extended Protocol Parameters for HSSoE
4. Set the Operation state as Hub Sync Master. Later, we will need one of the client
options for the collocated site.
5. Set the Protocol as Ethernet.
6. The Domain is the HSS domain and refers to the current hub site. It is used to
distinguish between hub sites to prevent inadvertent collocation to an over‐the‐air
unit. We set it as shown, to PM_Lab.
7. Leave the VLAN ID as is at 1977 unless there is some reason to change it.
8. The Discovery options are as follows:
Figure 11‐3: HSS discovery filters

9. Choose All. In our case it will show the HBS as HSS master and the collocated ODU
as HSS client:
You can save the results to a text file or change the display type from the Discovery
window tool bar:
The choices are the same as for Figure 11‐3.
10. Use the OK or Apply buttons to commit your changes. Here is the outcome:

Figure 11‐4: Configuration for HSS master
11. Click the Details button. A table of other Ethernet HSS masters with the same
domain is displayed:
This is a mistake: There should not be a second HSS master in this domain. Change it
to be HSS client and the display is updated:

Configuring the RT‐A(HBS) as an HSS client
Notice additional HSS client at IP address 10.104.3.2: It is collocated to the forego‐
ing radios using an HSS unit connected to theHBS.
11.4.3 Configuring the RT‐A(HBS) as an HSS client
We switch HSS roles between our RT‐A(HBS) and the collocated ODU.
 To configure the RT‐A(HBS) as an HSSoE Client:
1. Follow steps 1 to 4 for configuring the HSS master (see Configuring the RT‐A(HBS) as
an HSS master on page 11‐4).
2. At step 5 for HSS master, choose Hub Sync Client ‐ Continue Tx.
Here is the outcome:

Configuring the RT‐A(HBS) as an HSS client
Note that the IP address of the HSS master is displayed for confirmation.

11.5 Sync Status Messages and Color Codes
The possible External Pulses conditions are shown in the following table:
Table 11‐1: External Pulse Status
Color
HSS Sync Status Meaning
code
Generating Radio unit is HSS master and generates the sync pulse
Detected Radio unit is HSS client and detects the sync pulse
Green
Radio unit is independent (neither HSS master nor client,
Not detected
this would be appropriate for an RT‐B(HSU))
Generating and
Radio unit is HSS master, but other HSS master is present
detected
Generating and
Radio unit is HSS master, but detects an HSS master signal Orange
Improperly
Detected
that is not RFP E.
Not detected Radio unit is HSS client, but no HSS master is present
Radio unit is HSS client, but the HSS master pulse doesn’t fit
Improperly the HSS client as configured. Occurs only for RADWIN 2000
Red
detected C+, RADWIN 2000 D+, and RADWIN 5000, which stop
transmitting.

Chapter 12: GPS Hub Site
Synchronization
This chapter describes what is GPS hub site synchronization (GHSS), and how to implement it.
12.2 Overview
GPS Hub Site Synchronization using a GPS signal (GHSS). The GPS satellite signal acts as a
master, and each collocated RT‐A(HBS) unit that receives this synchronization signal acts as an
HSS Client (HSC).
GHSS works differently if there is an internal GPS capability:
• RT‐A(HBS) units based on the RADWIN 2000 A+, RADWIN 2000 C+, or RADWIN 2000 D+
require additional external equipment to work with the GPS‐based synchronization sig‐
nal.
• RT‐A(HBS) units based on the RADWIN 2000i has an integrated GPS unit, which is used
to receive this GPS‐based synchronization signal.
12.3 GHSS for the RADWIN 2000 A+,
RADWIN 2000 C+, or RADWIN 2000 D+
GHSS for the RADWIN 2000i is covered in GHSS for the RADWIN 2000i on page 12‐8.
To implement GHSS for the RADWIN 2000 A+, RADWIN 2000 C+, or RADWIN 2000 D+, the
following additional equipment is required:
• GPS Synchronization Unit (GSU) kit
• IDU‐H
• HSS Unit

GSU
12.3.1 GSU
The GSU is an outdoor unit consisting of a small size enclosure, a GPS antenna and a PoE
device.
It may be operated through an HSS unit or over Ethernet.
For use over Ethernet, the GSU requires Layer 2 connectivity to the multiple Hub‐Sites that it
is required to synchronize. It synchronizes the transmission timing of these Hub‐Sites to the
same clock source thus eliminating mutual interference. Typically, an IDU‐H/HP is used.
Figure 12‐1: General GSU configuration using both Ethernet and an HSS unit
The GSU receives a synchronization signal from the GPS once per second. It distributes a
RADWIN proprietary synchronization signal to all other ODU units using a proprietary
synchronization signal over Ethernet.
When the GSU doesn’t receive a synchronization signal from the GPS for 30 seconds, it moves
automatically to Self‐Generation mode until the GPS recovers.
12.3.2 GSU Kit Contents
The GSU package includes:

GSU Commissioning and Installation
• 1 x GSU
• 1 x GSU Mounting Kit
• 1 x GPS Antenna
• 1 x GPS Antenna Mounting Kit
• 1 x RF Cable, 1.5m
• RADWIN Manager supplied either on CD or by electronic means
12.3.3 GSU Commissioning and Installation
Preparing the GSU for Use
At the depot, log on to the unit using Local Connection or IP address 10.0.0.120 to change its
IP address from the default (10.0.0.120). The method is the same as is used for an HBS. In the
example screen captures below, we use 10.104.20.1 with Subnet Mask 255.255.0.0 and
Gateway 10.104.10.21.
GSU Installation
The GSU looks like a small form factor ODU. Mounting the GSU follows the standard pattern.
The GPS antenna is mounted outside on a wall or pole.
Configuring the GSU
To configure the GSU, you log on to it, exactly as in RADWIN Manager.
The GSU Main Window
Here is the main window for GSU configuration:

Figure 12‐2: GSU Main widow at startup
The GPS satellite data is contained in the bottom left panel:
Figure 12‐3: GPS status under normal use

The Configuration Window
Figure 12‐4: GSU Configuration window
The main tabs of interest are Management, Hub Site Sync and GPS Sync.
The Management tab is the same as the corresponding RT‐A(HBS) Management tab. If you
set the IP and related addresses correctly, there should be little to change here (see Link
Configuration in Detail).
The other three tabs, Trap Destination, VLAN and Protocol also have the same function here.
In the Hub Site Sync window, ensure that it is enabled and the Domain item set to be the
same as the corresponding item in Figure 11‐4.

The GPS Sync tab allows you to choose an RFP (see HSS Implementation) and set the
Transmission Ratio for the sector. Its value is application dependent:
(The reason that this is done at the GSU is that Transmission Ratio must always be
determined at the unit generating the sync pulses.)
For administrative purposes, you can view the Inventory:

The screen above is for illustrative purposes only. The list under “Product Family”
and the available CBW can vary among the various RADWIN 2000+ Series
products.
The GPS Sync tab allows you to choose a Radio Frame Pattern (RFP) and set the Transmission
Ratio for the sector. See see Radio Frame Pattern on page 9‐3 for a description of an RFP.
Choose the transmission ratio by clicking on its window and moving the scroll bar right or left
with the keyboard arrows. Be careful ‐ this scroll bar is sensitive to even small movements of
the mouse.

GHSS for the RADWIN 2000i
12.4 GHSS for the RADWIN 2000i
12.4.1 Overview
The RADWIN 2000i has an internal GPS unit. GHSS with an internal GPS unit can be illustrated
as follows:

Figure 12‐5: GHSS with multiple sites
A GPS synchronization signal arrives from the GPS satellite system to all RT‐A(HBS) units. The
signal instructs all units to receive and transmit at the same time. The Radio Frame Pattern
appears as follows:

Transmission Phase Shift
12.4.2 Transmission Phase Shift
In the case shown in Figure 12‐5 above, RT‐A(HBS) A1 transmits and receives opposite RT‐
B(HSU) B1. So, when RT‐A(HBS) A1 transmits, RT‐B(HSU) B1 must receive, and vice‐versa. The
above Radio Frame Pattern will then appear as follows:
However, RT‐A(HBS) B1 is co‐located with RT‐B(HSU) B1. As can be seen, this will cause
interference between these co‐located units.
To prevent this, RT‐A(HBS) B11 must have its transmission phase shifted. That is, the
transmission and receive times of RT‐A(HBS) B1 must be reversed, as shown:
As a result, the radio frame pattern of RT‐A(HBS) B1 is synchronized with that of RT‐B(HSU) B1,
and there is no interference between these two units. Configuring GHSS with an Internal GPS
Unit below describes how to configure the RT‐A(HBS) for this.
1. Another option is to shift the transmission phase of HBS A1 instead of HBS B1, but that requires shifting the
phases of *all* HBS units at Site A1, which is more time‐consuming.

Configuring GHSS with an Internal GPS Unit
12.4.3 Configuring GHSS with an Internal GPS Unit
With GHSS, all base stations (RT‐A(HBS) units) are HSS Clients, with the GPS satellite signal
being the master. RT‐B(HSU) units are always independent units (INU).
1. Log on to the RT‐A(HBS).
2. Open the Configure | Hub Site Sync tab:
Figure 12‐6: HSS Settings window ‐ GHSS
3. Check Enabled. The bottom part of the window in Figure 12‐6 is enabled (you will
soon change the Protocol from Ethernet to GPS).

4. Before you can change the Protocol from Ethernet to GPS, you must first choose the
Operational State as Hub Sync Client ‐ Continue Tx or Hub Sync Client ‐ Disable Tx,
according to your preference.
• HSS Client‐Continue Transmission (HSC‐CT): If the unit loses synchronization with
the HSS Master, the link remains active. However, without synchronization pulses,
it is possible that this unit will cause interference.
• HSS Client‐Disable Transmission (HSC‐DT): If the unit loses synchronization with
the HSS Master, the link is dropped until the synchronization pulses resume. This
setting prevents the unit from causing interference.

5. Choose GPS from the Protocol pull‐down menu:
6. If your site does not warrant the need for a shift in the transmission phase (see
page 12‐9 for a description of transmission phase), select the Normal radio button,
and click OK or Apply, then close the Hub Site Sync dialog box.
7. If your site does warrant the need for a shift in the transmission phase (see page 12‐
9 for a description of transmission phase), and the selected RT‐A(HBS) is the RT‐
A(HBS) whose transmission phase must be shifted, select the Shifted radio button,
and click OK or Apply, then close the Hub Site Sync dialog box.
If the Transmission Ratio is not *exactly* 50%, you will not be able to change the
Transmission Phase, and a warning instructing you to adjust it to 50% will appear
(For instructions on how to adjust the Transmission Ratio, see Transmission Ratio
on page 8‐27).

The GPS satellite data is shown in the bottom left panel:
Figure 12‐7: GPS status under normal use

Part 5: Advanced Installation Topics
Release 4.2.40
Chapter 13: Software Upgrade
This chapter describes the software upgrade utility, and how and when to use it.
13.2 What is the Software Upgrade Utility?
The RADWIN Manager provides a Software Upgrade Utility (SWU) to upgrade the software
(firmware) of installed radio units in a network. The update files may be located anywhere
accessible by the operator.
The SWU provides for:
• Prior backup of the current files prior to upgrade
• Upgrade from a list
• Delayed upgrade
• Various radio unit reset options
The default location of the software files is in the installation area, and can be used to restore
factory defaults.
13.3 Upgrading an Installed Link
 To upgrade software for a link:
1. In the RADWIN Manager, click the Tools | Software Upgrade button.The following
detached window appears:

Upgrading an Installed Link
Figure 13‐1: Software Upgrade Utility ‐ Main window
The default sites shown in the Software Upgrade list panel belong to the currently
installed sector. The list may be empty if you are running the RADWIN Manager
“offline”.
2. The Software upgrade list title bar has three buttons on the right hand side.
Figure 13‐2: Add / Remove site buttons
The left button opens up a Windows file dialog to locate a list of locations to
update. The list has the following format:
<IP address>,<Read‐Only community>,<Read‐Write community>
For example:
10.104.3.2,netman
10.104.3.4,netman
The list should include RT‐A(HBS)s and RT‐B(HSU)s able to accept the same upgrade.
Non‐upgradable items will result in an error message. Contact Customer Service
about upgrading them.
The center button allows you to add a single site:

Figure 13‐3: Adding a single site for upgrade
Enter the IP address of the site and the Read‐Write Community (Default: netman). If
you area SNMPv3 user, add your User Name and Password and then click OK. The
site will appear in the Software Upgrade list box.
Items from the list can be cleared by selecting them and then using the right but‐
ton.
The right button in Figure 13‐3, may be ruse to remove one or more selected sites.
3. Having created an update list, click Upgrade Package to chose the relevant files. The
default files are located in the SWU subdirectory in the RADWIN Manager
installation area. You may see one or more of the following SWU files:
Table 13‐1: SWU Files by product
File name Product
RADWIN 2000+
SWU_2k.swu
Series
SWU_5k.swu RADWIN 5000
For RADWIN 2000+ Series, always choose SWU_5k.swu (Not the 2k package).
4. To back up your existing system, check Backup device software check‐box. Then
click the button for a standard file dialog. The default location is the My
Documents directory on the managing computer or the last backup directory you
used.
The backup here is the same as that in Backup and Restore, and serves the
same purpose. It provides a fallback if the upgrade proves problematic.
5. In addition to the previous step, you may opt to perform a delayed upgrade. Check
the Delayed Upgrade box, and enter the date and time for the delayed upgrade. A
Calendar dialog box opens:

6. The radio buttons on the right determines how your radio units should be reset.
Bear in mind that on the one hand, a reset involves a service interruption, but on
the other hand, the software upgrade will not become effective until after the reset
is carried out. Here is a typical delayed upgrade scenario:
7. Click Start Upgrade to commence the process. For an immediate upgrade you will
be able to observe the upgrade progress from the green progress bars:

Bulk Software Backup
Figure 13‐4: Software upgrade in progress ‐ Note the stop button
Figure 13‐5: Software upgrade completed successfully
8. Use the title bar exit button to dismiss the Software upgrade window..
If any sites fail to update, a warning notice will be displayed.
If one or more sites of a sector update fails, you should correct the
problem and update the failed sites as soon as possible. If you do not,
following the next reset of the updated sites, you could experience a link
software mismatch which may affect service.
13.4 Bulk Software Backup
You can back up the sector software independently of Software Upgrade using the main
button menu. See Software Backup and Restore.

Chapter 14: Software Backup
and Restore
This chapter describes how and when to use the various backup and restore facilities
available for the RADWIN 2000+ Series radio units.
14.2 Backup and Restore Facilities
You can backup the radio unit software fora complete link (Bulk Backup) or a single site. The
Restore facility is selective: You may restore backed up radio units one at a time. The restore
may be the full software or just the configuration settings.
A backup (full or configuration only) may be restored to another radio unit
provided that the product IDs and revision levels of the source and target
radio units are identical. They are shown in the radio unit Inventory
window.
14.3 Bulk Software Backup
 To backup a link or sector:
1. Go to Tools | Bulk Backup:

The following detached window appears:
Figure 14‐1: Bulk Backup setup window
The default sites shown in the Bulk Backup list panel belong to the currently
installed link. The list may be empty if you are running the RADWIN Manager
“offline”.
2. The Bulk Backup list title bar has three buttons on the right hand side.
Figure 14‐2: Add / Remove site buttons
The left button opens up a Windows file dialog to locate a list of locations to
backup. The list has the following format for SNMPv1:
<IP address>,<Read‐Only community>,<Read‐Write community>
For SNMPv3 it is:
<IP address>,<Dummy>,<User_type><Password>
For example:
10.104.3.2,netman,admin,netwireless

A PtMP list will contain the HBS and registered HSUs.
The center button allows you to add a single site:
Figure 14‐3: Adding a single site for backup
Enter the IP address of the site, the Read‐Write Community (Default: netman) and
then click OK. The site will appear in the Software Upgrade list box.
Items from the list can be cleared by selecting them and then using the right but‐
ton.
The right button in Figure 14‐3, may be ruse to remove one or more selected sites.
3. You may choose the SNMP version but probably it should be best left at your log‐on
setting.
4. Click the Start Backup button. Progress bars indicate backup status.
The success or failure of the backup is displayed on completion:
Save configuration produces a text file in the format of the above example for backing up an
installed link.

Site Backup
The files produced by the above process are:
10.104.3.4_29.01.2015.backup
10.104.3.2_29.01.2015.backup
BulkBackupConfig_2015_01_29.txt
Notice that the files are date stamped. The first two files are binary. The last is the save‐
configuration text file:
The backup files are identical in naming convention and format to those produced on a site‐
by‐site basis.
14.4 Site Backup
A single site may be backed up directly from the Backup tab of the radio unit Configuration
window.
Both of the Backup and Restore buttons open standard MS Windows file dialogs respectively
to create and read a backup file. The file is stored using a proprietary binary format.
The Restore button offers two extra options, Configuration Restore or Full Restore.
Configuration Restore just restores configuration settings, whereas Full Restore reverts the
radio unit software to the backed up version.

Chapter 15: VLAN
Functionality
This chapter describes how the components of a RADWIN 2000+ Series link deal with VLAN
tagging and untagging.
15.2 VLAN Tagging ‐ Overview
15.2.1 VLAN and Related Terminology
Both the technical literature and the RADWIN Manager use the terms VLAN ID and VID
interchangeably to denote a VLAN identification number.
Reminder: RT‐A(HBS) always means the Master ODU and RT‐B(HSU) always means the Slave
ODU.
15.2.2 VLAN Background Information on the Web
The standards defining VLAN Tagging are IEEE_802.1Q and extensions.
For general background about VLAN see http://en.wikipedia.org/wiki/Virtual_LAN.
Background information about Double Tagging also known as QinQ may be found here:
http://en.wikipedia.org/wiki/802.1QinQ.
15.3 Requirements
It is assumed that you are familiar with VLAN usage and terminology.

VLAN Tagging
15.4 VLAN Tagging
VLAN tagging enables multiple bridged networks to transparently share the same physical
network link without leakage of information between networks:
IEEE 802.1Q is used as the encapsulation protocol to implement this mechanism over
Ethernet networks.
15.4.1 QinQ (Double Tagging) for Service Providers
QinQ is useful for Service Providers, allowing them to use VLANs internally in their “transport
network” while mixing Ethernet traffic from clients that are already VLAN‐tagged.
The outer tag (representing the Provider VLAN) comes first, followed by the inner tag. In QinQ
the EtherType = 0x9100. VLAN tags may be stacked three or more deep.
When using this type of “Provider Tagging” you should keep the following in mind:
• Under Provider Tagging, the system double‐tags egress frames towards the Provider’s
network. The system adds a tag with a VLAN ID and EtherType = 0x9100 to all frames, as
configured by the service provider (Provider VLAN ID).
• The system always adds to each frame, tags with VLAN ID and EtherType = 0x9100.
Therefore,
• For a frame without a tag – the system will add a tag with VLAN ID and EtherType =
0x9100 so the frame will have one tag
• For a frame with a VLAN tag – the system will add a tag with VLAN ID and EtherType
= 0x9100 so the frame will be double‐tagged
For a frame with a VLAN tag and a provider tag – the system will add a tag with VLAN ID and
EtherType = 0x9100 so the frame will be triple‐tagged and so on.
At the egress side, the RT‐B(HSU) removes the QinQ tag with EtherType = 0x9100 no matter
what the value of its VLAN ID.
15.4.2 VLAN Untagging
VLAN Untagging means the removal of a VLAN or a Provider tag.
15.4.3 Port Functionality
In a 2000+ link, all VLAN activity is configured and supported from the RT‐B(HSU).
To this end, VLAN functionality is supported at the LAN port of the RT‐B(HSU).
The RT‐B(HSU) LAN port can be configured to handle Ethernet frames at the ingress direction
(where frames enter the RT‐B(HSU)) and at the egress direction (where frames exit the RT‐
B(HSU)).

Port Functionality
Ingress Direction
Table 15‐1: Port settings ‐ Ingress direction
The port ‘does nothing’ with regard to VLANs ‐ inbound frames are left
Transparent
untouched.
Frames entering the RT‐B(HSU) port without VLAN or QinQ tagging are
tagged with VLAN ID and Prioritya, which are preconfigured by the user.
Frames which are already tagged at ingress are not modified and pass
through.
Tag
Frames entering the RT‐B(HSU) port are tagged with provider’s VLAN ID and
Priority which are preconfigured by the user. Frame.s which are already
tagged with Provider tagging at the ingress are not modified and passed
through
Provider tag
a. Priority
Code Point (PCP) which refers to the IEEE 802.1p priority. It indicates the frame priority level
from 0 (lowest) to 7 (highest), which can be used to prioritize different classes of traffic (voice, video,
data, etc).

VLAN Configuration Using the RADWIN Manager
Egress Direction
Table 15‐2: Port settings ‐ Egress direction
The port ‘does nothing’ with regard to VLANs ‐ outbound frames are left
Transparent
untouched.
Port configured to untag user VLAD tags for all frames.
Untag all
Filter
15.5 VLAN Configuration Using the RADWIN
Manager
Incorrect VLAN configuration may cause havoc on your network. The
facilities described below are offered as a service to enable you to get best
value from your RADWIN 2000+ Series links and are provided “as is”.
Under no circumstances does RADWIN accept responsibility for network
system or financial damages arising from incorrect use of these VLAN
facilities.
15.5.1 Management Traffic and Ethernet Service Separation
You can define a VLAN ID for management traffic separation. You should configure the system
to prevent conflicts as detailed below.
When configured for the default operational mode, a “Provider port” will handle ingress
traffic as follows:
• Filters frames that are not tagged with the Provider VLAN ID
• Removes the Provider double tag
Therefore, if a port is configured for management traffic separation by VLAN and as ‘Provider
port’, then the received management frames must be double tagged as follows:

Configuration of VLAN Tagging for Ethernet Service
• The outer tag has to be the Provider’s tag (so the frame is not filtered)
• The internal tag has to be management VLAN ID
To avoid mix‐ups, best practice is to:
• Separate the management and data ports
• Define only a data port with Provider function
15.5.2 Configuration of VLAN Tagging for Ethernet Service
 To set up an RT‐B(HSU) for VLAN tagging:
1. Open Link Configuration | Ethernet and then click the VLAN Configuration button.
In Disabled mode, Ethernet frames pass transparently over the radio links.
2. For Provider tagging, click the Provider Radio button:
In Provider mode, Ethernet frames are tagged with the provider’s VLAN ID before
they enter into the provider’s network/backbone.
3. Enter a Provider VLAN ID and Priority. The VLAN ID must be in the range 2 to 4094.
The VLAN Priority must be in the range 0 to 7. You may also change the TPID from
the default as shown.
4. Click OK to accept.
5. For user VLAN tagging, click the Tag Radio button:

This facility is provided to enable connection through legacy switches
requiring it. Otherwise, there is no need to change the TPID.
In Tag mode Ethernet frames are tagged or untagged to distinguish between differ‐
ent networks.
6. For completely transparent passage of tagged frames, there is nothing further to
do. Table 15‐3 shows the possible settings for each combination of Ingress and
Egress modes.

7. Click OK.
Table 15‐3: Further VLAN Configuration options and results by Tag mode
Egress
Ingress
Transparent Untag All Untag Filtered Filter
Allow VLAN IDs:
Allow up to 4 VIDs
Frames are to be passed
not modified All frames with Allow up to 4 VIDs
VLAN tag are through.b to be passed
Transparent and are
a Untag VLAN IDs:
forwarded untagged through.c
transparently Untag the VLAN tag
of the selected
VLAN IDs.
Tag: Frames are
not modified All frames with Allow up to 4 VIDs Allow up to 4 VIDs
Enter a VID (1‐
and are VLAN tag are to be passed to be passed
4094) and
forwarded untagged through through
Priority (0‐7)d transparently
a. Frames with Provider Tag 9100 or 88A8 will be passed through transparently
b. For frames with Provider Tag 8100, the filter will be applied to the outer tag
c. For frames with Provider Tag 8100, the filter will be applied to the outer tag
d. Frames with Provider Tag 8100 at egress will be stripped of the outer tag

Chapter 16: Quality of Service
This chapter describes how to set various levels of Quality of Service (QoS) for a RADWIN
2000+ Series lnk.
16.2 Prerequisites
To use the facility you must be familiar with the use of VLAN (802.1p) or Diffserv.
16.3 QoS ‐ Overview
QoS is a technique for prioritization of network traffic packets during congestion.
RADWIN 2000+ Series links support two classification criteria, VLAN based or Diffserv based.
You may choose which of them to use.
Table 16‐1: Default priorities an d allocation by VLAN ID and Diffserv
Priority
Quality queue
Diffserv VLAN
Real time 48‐63 6‐7

Near real time (responsive
32‐47 4‐5
applications)
Controlled load 16‐31 2‐3

Best effort 0‐15 0‐1
Based upon the classification criterion chosen, received packets will be mapped into one of
four quality groups: Real time, Near real time, Controlled load and Best effort.
You may partition the total link capacity across the four Quality queues. The default weights
as percentages are shown in Table 16‐1.

Setting up the Link for QoS
16.4 Setting up the Link for QoS
16.4.1 Preparing for QoS
Open Services Configuration and then click the QoS Configuration button.
Figure 16‐1: QoS Configuration window
QoS is disabled by default. You may choose between the VLAN (802.1p) and Diffserv
methods.

Preparing for QoS
The default settings for Diffserv and VLAN are as shown in the next two figures:
If you un‐check a queue, it will be disabled for the link. It will not prevent the Slave ODU from
configuring it as “live”. The purpose behind this is to avoid the necessity of reconfiguring QoS
for the Slave ODU, should the queue be reinstated.

Assigning Queue Priorities
16.4.2 Assigning Queue Priorities
Four mechanisms are available to control queue performance:
• Strict ‐ An over‐the‐air packet is loaded first with data from Real Tome queue (see
Figure 16‐2), and then from the remaining queues in order. If there is too much data for
the first queue, it will “starve” the lower queues and so on.
• Weight ‐ One solution to such “starvation” is to weight input flow to the four queues.
This could still lead to wasted resources. If in the example below, the actual traffic is all
Near Real Time, only 20% will be allocated to Near real time and the rest will be held up.
• Maximum Information Rate (MIR) ‐ This is a simple throttle mechanism, which suffers
from a drawback similar to the previous case.
• Time to Live (TTL) in ms ‐ This device is use to reduce re‐transmits of real time data (such
as voice or viewed video).
 To configure queue priorities for uplink and downlink in turn:
1. For each queue, both downlink and uplink enter the required weight, MIR and TTL.
The MIR and TTL may respectively be left Unlimited and Disabled in which case the
system will use a “best effort” method.
If you exceed 100% total weight, you will receive an error message.
Figure 16‐2: The four QoS data queues
You will be required to correct this before leaving the window other than by cancel‐
lation.
If you are under‐booked, for example by setting a queue to zero, the unused weight
will be distributed to the remaining queues. The effect of doing this will only
become apparent under congestion. In particular, a queue set to zero weight will
become nearly blocked under congestion with packets passing through on a best
effort basis.
2. When you complete your entries, in the QoS Configuration window (Figure 16‐1),
click OK to save them and continue.

Chapter 17: False Radar
Mitigation Facilities
This chapter describes how to configure the units in a RADWIN 2000+ Series link so as to
avoid interfering with certain radar systems.
17.2 Who needs it
If you are using DFS frequency bands 5.3/5.4 GHz ETSI and 5.4/5.8GHz FCC you should use this
facility.
17.3 DFS and False Radar Mitigation
17.3.1 About DFS
Under DFS frequency bands, it must be ensured that radio links do not interfere with certain
radar systems in the 5 GHz band. If radar is detected, the radio link should move
automatically to a frequency that does not interfere with the detected radar.
17.3.2 What is False Radar Mitigation
False Radar Mitigation capability is an advanced method to reduce or eliminate false radar
detection and DFS triggering (“False positives”).
False radar detection can be caused by other radios transmissions or external interference
that can be interpreted as true radar.
This option is active only in DFS frequency bands, 5.3/5.4 GHz FCC (HBS only) and 5.4/5.8GHz
ETSI (HBS & HSU).
In what follows false radar means any source of radar‐like signals which are not real radar.

Configuring False Radar Mitigation
False Radar Mitigation has two components:
1. Reduction of false positive radar detection by reduction of the probability of detecting any
kind of false radars, while allowing the system to detect real radar signals.
2. Elimination of detection of specific false radar types by blocking detection of false radars
of a specific type. There are three types of radars:
• Fixed: False radars with fixed pulse width having fixed repetition frequency
• Variable: False radars with variable pulse width having variable repetition frequency
• Staggered: False radars with variable repetition frequency within a burst period
(Applies to 5.4 GHz ETSI only)
17.4 Configuring False Radar Mitigation
The configuration method for the Master ODU (ETSI and FCC/IC) is the same as for the Slave
ODU (ETSI only). We will demonstrate the Master ODU for a link using the 5.3 GHz FCC/IC
band:
 To configure False Radar Mitigation:
1. Log on to the Master ODU as Installer.
2. Enter the Configuration window and open the Advanced tab.

FCC/IC Requirements
Figure 17‐1: False Radar Mitigation
3. The DFS Frequency Status Table at the bottom of Figure 17‐1 shows the time, type
and frequency of the last radars detected. This table should be used to select the
best option(s) to reduce or eliminate false radar detection without completely
blocking out real radar detection.
4. Check the mitigation features to be used.
5. When you are satisfied with your configuration parameters, click OK to save them
and dismiss the Configuration window.
17.5 FCC/IC Requirements
The FCC requires that devices installed within 35 km of any Terminal Doppler Weather Radars
(TDWR) location should be registered in the voluntary WISPA sponsored database.For
convenience, we supply guidelines about the way this is done in FCC/IC DFS Considerations.

Chapter 18: FCC/IC DFS
Considerations
This chapter describes the criteria for registering devices of a RADWIN 2000+ Series link in the
WISPA database, and if any should be registered, how to do so.
18.2 FCC 5.4GHz Device Registration
The FCC requires that devices installed within 35 km of any TDWR location should be
registered in the voluntary WISPA sponsored database.
The FCC has published a TDWR Location Information table that lists the exact location of all
TDWR towers (see Table 18‐1 at the end of the chapter).
1. When installing a 5.4 GHz device define your exact location (latitude and longitude)
2. Use the TDWR Location Information table to determine if the distance between
the device and any TDWR tower is less than 35 km.
3. If the distance is less than 35 km then register the device in the voluntary WISPA
sponsored database (following section)
4. Disable the frequencies between 5570 – 5680 MHz from the available channels
list.
5. The frequency range between 5.600 to 5.650 GHz is not included in the available
channels list.
18.3 Registering the Device
 To register a device:
1. Enter the website http://www.spectrumbridge.com/udia/home.aspx and follow the
instructions.

Registering the Device
At your first entry into the site, you will be required to register as a user:
2. Click the User Registration button to enter the registration page.

3. Fill in the registration page and click Register.
4. To complete device registration enter the Register Device tab as shown:

You are offered this:
5. Fill in the required information in the preceding web page and click the Register
Device button.

TDWR Table
18.4 TDWR Table
The following table contains the latitude and longitude locations of Terminal Doppler
Weather Radars (TDWR). Use this table to determine if the Master or Client device installed is
within 35 km radius of a TDWR location. If one of the installed devices is within 35 km radius
of any TDWR location then disable all frequencies between 5570 – 5680 MHz from the
available channels list.
Table 18‐1: Latitude and longitude locations of TDWRs
STATE CITY LONGITUDE LATITUDE FREQUENCY TERRAIN ELE‐ ANTENNA
VATION HEIGHT
(MSL) [ft] ABOVE TER‐
RAIN [ft]
AZ PHOENIX W 112 09 46 N 33 25 14 5610 MHz 1024 64
CO DENVER W 104 31 35 N 39 43 39 5615 MHz 5643 64
FL FT LAUDERDALE W 080 20 39 N 26 08 36 5645 MHz 7 113
FL MIAMI W 080 29 28 N 25 45 27 5605 MHz 10 113
FL ORLANDO W 081 19 33 N 28 20 37 5640 MHz 72 97
FL TAMPA W 082 31 04 N 27 51 35 5620 MHz 14 80
FL WEST PALM BEACH W 080 16 23 N 26 41 17 5615 MHz 20 113
GA ATLANTA W 084 15 44 N 33 38 48 5615 MHz 962 113
IL MCCOOK W 087 51 31 N 41 47 50 5615 MHz 646 97
IL CRESTWOOD W 087 43 47 N 41 39 05 5645 MHz 663 113
IN INDIANAPOLIS W 086 26 08 N 39 38 14 5605 MHz 751 97
KS WICHITA W 097 26 13 N 37 30 26 5603 MHz 1270 80
KY COVINGTON CINCINNATI W 084 34 48 N 38 53 53 5610 MHz 942 97
KY LOUISVILLE W 085 36 38 N 38 02 45 5646 MHz 617 113
LA NEW ORLEANS W 090 24 11 N 30 01 18 5645 MHz 2 97
MA BOSTON W 070 56 01 N 42 09 30 5610 MHz 151 113
MD BRANDYWINE W 076 50 42 N 38 41 43 5635 MHz 233 113
MD BENFIELD W 076 37 48 N 39 05 23 5645 MHz 184 113
MD CLINTON W 076 57 43 N 38 45 32 5615 MHz 249 97
MI DETROIT W 083 30 54 N 42 06 40 5615 MHz 656 113
MN MINNEAPOLIS W 092 55 58 N 44 52 17 5610 MHz 1040 80
MO KANSAS CITY W 094 44 31 N 39 29 55 5605 MHz 1040 64
MO SAINT LOUIS W 090 29 21 N 38 48 20 5610 MHz 551 97
MS DESOTO COUNTY W 089 59 33 N 34 53 45 5610 MHz 371 113
NC CHARLOTTE W 080 53 06 N 35 20 14 5608 MHz 757 113
NC RALEIGH DURHAM W 078 41 50 N 36 00 07 5647 MHz 400 113
NJ WOODBRIDGE W 074 16 13 N 40 35 37 5620 MHz 19 113
NJ PENNSAUKEN W 075 04 12 N 39 56 57 5610 MHz 39 113
NV LAS VEGAS W 115 00 26 N 36 08 37 5645 MHz 1995 64

TDWR Table
Table 18‐1: Latitude and longitude locations of TDWRs (Continued)
STATE CITY LONGITUDE LATITUDE FREQUENCY TERRAIN ELE‐ ANTENNA
VATION HEIGHT
(MSL) [ft] ABOVE TER‐
RAIN [ft]
NY FLOYD BENNETT FIELD W 073 52 49 N 40 35 20 5647 MHz 8 97
OH DAYTON W 084 07 23 N 40 01 19 5640 MHz 922 97
OH CLEVELAND W 082 00 28 N 41 17 23 5645 MHz 817 113
OH COLUMBUS W 082 42 55 N 40 00 20 5605 MHz 1037 113
OK AERO. CTR TDWR #1 W 097 37 31 N 35 24 19 5610 MHz 1285 80
OK AERO. CTR TDWR #2 W 097 37 43 N 35 23 34 5620 MHz 1293 97
OK TULSA W 095 49 34 N 36 04 14 5605 MHz 712 113
OK OKLAHOMA CITY W 097 30 36 N 35 16 34 5603 MHz 1195 64
PA HANOVER W 080 29 10 N 40 30 05 5615 MHz 1266 113
PR SAN JUAN W 066 10 46 N 18 28 26 5610 MHz 59 113
TN NASHVILLE W 086 39 42 N 35 58 47 5605 MHz 722 97
TX HOUSTON INTERCONTL W 095 34 01 N 30 03 54 5605 MHz 154 97
TX PEARLAND W 095 14 30 N 29 30 59 5645 MHz 36 80
TX DALLAS LOVE FIELD W 096 58 06 N 32 55 33 5608 MHz 541 80
TX LEWISVILLE DFW W 096 55 05 N 33 03 53 5640 MHz 554 31
UT SALT LAKE CITY W 111 55 47 N 40 58 02 5610 MHz 4219 80
VA LEESBURG W 077 31 46 N 39 05 02 5605 MHz 361 113
WI MILWAUKEE W 088 02 47 N 42 49 10 5603 MHz 820 113

Part 6: Field Installation Topics
Release 4.2.40
Chapter 19: Link Budget
Calculator
This chapter describes the Link Budget Calculator and how to use it.
19.2 Overview
The Link Budget Calculator is a utility for calculating the expected performance of the
RADWIN 2000+ Series wireless link and the possible configurations for a specific link range.
The utility allows you to calculate the expected RSS of the link, and find the type of services
and their effective throughput as a function of the link range and deployment conditions.
19.2.1 User Input
You are required to enter or choose the following parameters. Depending on the product,
some of the parameters have a default value that cannot be changed.
• Band, which determines frequency and regulation
• Radio unit series used
• Channel Bandwidth
• Tx Power (maximum Tx power per modulation is validated)
• Antenna Type (currently dual; cannot be changed for radio unit with integrated
antenna)
• Antenna Gain per site (cannot be changed for integrated antenna)
• Cable Loss per site (cannot be changed for integrated antenna)
• Fade Margin (currently 6dB)
• Rate
• Required Range and climate type

Link Budget Calculator Internal Data
19.2.2 Link Budget Calculator Internal Data
For each product (or Regulation and Band) the calculator stores the following data required
for link budget calculations:
• Maximum Transmit power (per modulation)
• Receiver Sensitivity (per modulation) for Ethernet service
• Maximum linear input power (used to calculate minimum distance)
• Antenna gain and cable loss for radio unit with integrated antenna
• Available Channel Bandwidths
19.3 Calculations
19.3.1 EIRP
(Equivalent Isotropically Radiated Power)
EIRP = TxPower + AntennaGain SiteA – CableLoss SiteA
19.3.2 Expected RSS and Fade Margin
ExpectedRSS = EIRP – PathLoss + AntennaGain SiteB – CableLoss SiteB
where:
Site A is the transmitting site
Site B is the receiving site
PathLoss is calculated according to the free space model,
PathLoss = 32.45 + 20  log 10 frequency MHz  + 20  log 10 RequiredRange Km 
ExpectedFadeM arg in = ExpectedRSS – Sensitivity

where Sensitivity is dependent on air‐rate.
19.3.3 Min and Max Range
MinRange is the shortest range for which ExpectedRSS  MaxInputPower per air‐rate.
MaxRange (with Adaptive checked) is the largest range for which
ExpectedRSS  Sensitivity , at the highest air‐rate for which this relationship is true. In a
link with adaptive rate this will be the actual behavior.
MaxRange (for a given air‐rate) is the largest range for which
ExpectedRSS  Sensitivity + RequiredFadeM arg in .

Service
19.3.4 Service
The Ethernet and configured TDM trunks throughput is calculated according to internal
product algorithms.
19.3.5 Availability
The Service Availability calculation is based on the Vigants Barnett method which predicts the
downtime probability based on a climate factor (C factor).
Availability
–7 3
= 1 – 6  10  Cfactor  frequency GHz   RequiredRange KM 
ExpectedFadeM arg in-
–-----------------------------------------------------------
10
 10
19.3.6 Antenna Height
The recommended antenna height required for line of sight is calculated as the sum the
Fresnel zone height and the boresight height. See About the Fresnel Zone below. Using the
notation of Figure 19‐1 below, splitting ExpectedRange into d1 + d2, the Fresnel zone height
at distance d1 from the left hand antenna, is given by
300
-----------------------------------  d1  d2
frequency GHz
0.6  -----------------------------------------------------------
d1 + d2
For the most conservative setting, we take the mid‐point between the antennas, setting
ExpectedRange
d 1 = d 2 = -----------------------------------------
2
2
300
-----------------------------------  ExpectedRange
-----------------------------------------
frequency GHz 2
which gives 0.6  -------------------------------------------------------------------------------------------
-
ExpectedRange ExpectedRange
----------------------------------------- + -----------------------------------------
2 2
ExpectedRange
simplifying to 0.52  ----------------------------------------- .
frequency GHz
2 ExpectedRange 2
The boresight clearance height is calculated as: R Mean + ----------------------------------------- – R Mean
2
where R Mean = 6367.4425Km .

About the Fresnel Zone
19.4 About the Fresnel Zone
The Fresnel zone is an elliptically shaped conical zone of electromagnetic energy that
propagates from the transmitting antenna to the receiving antenna. It is always widest in the
middle of the path between the two antennas.

Figure 19‐1: Fresnel zone
Fresnel loss is the path loss occurring from multi‐path reflections from reflective surfaces
such as water, and intervening obstacles such as buildings or mountain peaks within the
Fresnel zone.
Radio links should be designed to accommodate obstructions and atmospheric conditions,
weather conditions, large bodies of water, and other reflectors and absorbers of
electromagnetic energy.
The Fresnel zone provides us with a way to calculate the amount of clearance that a wireless
wave needs from an obstacle to ensure that the obstacle does not attenuate the signal.
There are infinitely many Fresnel zones located coaxially around the center of the direct
wave. The outer boundary of the first Fresnel zone is defined as the combined path length of
all paths, which are half wavelength (1/2 ) of the frequency transmitted longer than the
direct path. If the total path distance is one wavelength (1 ) longer than the direct path, then
the outer boundary is said to be two Fresnel zones. Odd number Fresnel zones reinforce the
direct wave path signal; even number Fresnel zones cancel the direct wave path signal.
The amount of the Fresnel zone clearance is determined by the wavelength of the signal, the
path length, and the distance to the obstacle. For reliability, point‐to‐point links are designed
to have at least 60% of the first Fresnel zone clear to avoid significant attenuation.

Running the Link Budget Calculator
The concept of the Fresnel zone is shown in Figure 19‐1 above. The top of the obstruction
does not extend far into the Fresnel zone, leaving 60% of the Fresnel zone clear; therefore,
the signal is not significantly attenuated.
For more about Fresnel zone, see http://en.wikipedia.org/wiki/Fresnel_zone.
19.5 Running the Link Budget Calculator
for RADWIN 2000+ Series is availableThe Link Budget Calculator for RADWIN 2000+ Series is
available at http://www.radwin.com/planner/.
Go to the URL. Your browser displays page similar to this (shown partially):
Figure 19‐2: Link Budget window ‐ startup
 To use the Link Budget Calculator for RADWIN 2000+ Series:
1. Stay on the left hand highlighted tab.

Figure 19‐3: RADWIN 2000+ Series LBC main window
2. Chose the required band. Scroll down to get to Connectorized bands.

Figure 19‐4: Band selector
For the purposes of our example, we will use 5.8 GHz FCC/IC Connectorized.
3. Choose the Series:
4. Choose the channel Bandwidth:
Collocated radio units use RFP E so there is no HSS entry
5. Choose the required Tx Power. Under Adaptive Rate, this will be the Max Tx Power
and you cannot change it.
6. Choose the required antenna type ‐ dual or single. For integrated products this item
will be disabled.
7. Enter the radio parameters for each site:

The Fade margin is the minimum required for line‐of‐sight (LOS) conditions. For
degraded link conditions, a larger Fade margin should be used. Again, it is not avail‐
able when using Adaptive Rate.
The EIRP is calculated in dBm and Watts.
8. The Rate item may be used for calculating the Link Budget under best and worst
scenarios. It is always set to maximum under Adaptive Rate.
9. If the required range between the two link sites is known, you may enter it directly.
Alternatively, you may enter the latitude and longitude of each site in the link, in
which case the distance between them will be calculated and displayed.
Figure 19‐5: Calculation of distance from site coordinates
If for example, we enter:
Site A: 41.1°N lat 75.2°W Long
Site B: 40.8°N lat 75.0°W Long

and press Set,
the range will be calculated and displayed:
10. Located to the right of the green Coordinates button is a drop‐down list of Climactic
C Factor values. It is only available if you choose a non‐adaptive rate.
Figure 19‐6: Climactic C Factors
For help about what these mean, click the button to the right of the list in
Figure 19‐6.

Figure 19‐7: Climactic C Factor description
In Figure 19‐8 we display a map of the world showing C Factor contours:
Figure 19‐8: World map showing C Factor contours
11. Click Calculate to obtain the required performance estimate.
Placing the cursor in any other calculated field will also update the
calculated results.
Note

Figure 19‐9: LBC ‐ Results section
The Expected Performance parameters are calculated and displayed:
• Expected RSS ‐ the expected RSS that the RADWIN Manager shows when the RADWIN
2000+ Series radio units are optimally aligned
• Services Type ‐ Ethernet only
• Ethernet Rate ‐ maximum throughput available for the chosen parameter combination
• Antenna height for LOS – the minimum antenna height required for line‐of‐sight opera‐
tion. It is the sum of the height required for boresight clearance due to the earth’s cur‐
vature plus the height required to clear the Fresnel zone
If the expected performance is not suitable for your application, try different parameters and
repeat the calculation.

Chapter 20: Spectrum View
This chapter shows how to use the Spectrum View tool. We assume that the reader knows
about RF Spectrum Analysis
20.2 What is Spectrum View
The RADWIN Manager Spectrum View utility is an RF survey tool designed to support the link
installation prior to full link service activation. The tool provides comprehensive and clear
spectral measurement information enabling easier, faster and better quality installations.
You can view real‐time spectrum information, save the spectral information and view
retrieved spectral information from historic spectrum scans.
Separate information is generated for the Slave and Master ‐ all by selection.
RADWIN’s spectrum measurement and estimation algorithms are designed to show accurate
information accommodating variations in frequency, temperature and interference power
and at the same time overcoming anomalies that tend to occur in high interference
environments.
20.3 Who needs it
As indicated in the previous paragraph, Spectrum View is primarily a professional tool for the
technician. The Spectrum View reports may be generated as images, CSV files or text files as
part of the Get Diagnostics feature. All of these are intended for use by to RADWIN Customer
Service to assist with diagnosing interference related problems.
20.4 Two Ways to Run Spectrum View
Spectrum View may be run from RT‐A(HBS) in which case you have a choice of analyzing both
sites in the link in one run, or choosing just one.

Where is the Spectrum View Data stored
Spectrum View may also be run on a managing computer directly connected to the RT‐
B(HSU). Remember that in such a case the results will be quite different if the RT‐B(HSU) is
already part of a link (registered or not) or if it is completely stand‐alone, for example using a
different spectral range and operating Band from the RT‐A(HBS). In the former case, expect a
“noise hump” around the channels used by the link, due to the duty signals from the RT‐
A(HBS).
20.5 Where is the Spectrum View Data stored
Spectrum View data is always stored in the ODU originating the analysis. The RT‐A(HBS)
maintains the last Spectrum View analysis data for both members of the link. If you run
Spectrum View from a directly connected ODU, it stores its own data, which may be quite
different from the analysis obtained for the same RT‐B(HSU) from the RT‐A(HBS).
20.6 Spectrum View Main Window
In this section we review the main window management controls.
From the Tools tab, choose Spectrum View.
The Spectrum View main window opens in full screen mode:

Spectrum View Main Window
Use the top left panel to set the Spectrum View configuration parameters and choose an
analysis type ‐ Entire link or Specific ODU.
The settings are “sticky” for the link and will be reused. The analysis range is limited from
4900 to 6050 MHz with a maximum difference of 500MHz. Erroneous entries will be shown
with a red border like this:
The timeout is the maximum analysis time per site. Use the bottom button bar to start or stop
an analysis:
Since a large link will clutter up the right hand display area, you may selectively Show,
minimize or remove a link member. Another way of freeing up more space for analysis
displays is to hide the left hand panel using the circled arrow:

Spectrum View Display Function Buttons

The standard X button closes the window completely (but does not loose data). The ‐ button
collapses the view to look like this:
The two side arrows (circled) are used to reorder a stack of such view on the display area:
The remaining controls on the Spectrum View main window relate to Spectrum View data
manipulation. We will cover them in the next section using a live analysis.
20.7 Spectrum View Display Function Buttons
Spectrum View data manipulation functions are provide on the top button bar:

Running Spectrum View
Table 20‐1: Spectrum View Analysis Display Buttons functionality
Butto
Purpose
n
Show/Hide Antenna A
Show/Hide Antenna B
Show/Hide average
Show/Hide current channel
(HSUs only)
Show/Hide maximum
Show/Hide DFS information
where relevant
Show/Hide point values
Save the analysis to a CSV file
Clear all link member analyses
from the display (They can be
shown again)
Each button function applies to all of the link members at once.
Note
20.8 Running Spectrum View
Click Start. You are offered the following cautionary message:

Running Spectrum View
If it is acceptable to drop the service click Yes. The processing may appear to have stopped ‐
but it is not complete until all of the Show buttons for link are enabled.
Here is the result for the RT‐A(HBS):
The keys to the color coding is permanently displayed at the bottom of the main window:
Figure 20‐1: Spectrum View Analysis color codes
The green band reflects the current Master operating frequency. Notice also the small fly‐
over diskette icon (circled) to the upper left of either graph. Clicking it opens a Windows File‐
Save dialog allowing you to save the graph to disk as a jpg file.
Here is the analysis for RT‐B(HSU). It is very similar:

Zooming in and out
The light green rectangle in the background of both antenna displays reflects actual channel
(20 MHz wide here) being used by the Slave. The title bar also contains the Slave’s IP address.
20.9 Zooming in and out
You may zoom in on a range of interest and enlarge it. Use the mouse to swipe the range from
left to right or reverse and then click.The swiped range is zoomed in. You may repeat this
several times. The zoom applies to all charts for all element in the analysis. An indicator is
provided at the top right of each chart:

Zooming in and out
Zoom Out returns you to the previous zoom state; Show all reverts you to the original display.
In a zoomed state, a horizontal scroll bar enables you to view other areas of the displayed
frequency range.

Chapter 21: Using the Web
Interface
This chapter describes how to use the Web Interface to carry out basic link management
tasks.
21.2 What is it For
The Web Interface (WI) enables you to carry out basic link management functions using a
Web browser.
It may be used to ‐
• Monitor a link on a minimal basis
• Check link parameters and make limited changes
• View the link Inventory
• Inspect the Recent Events logs
21.3 Who Needs it
The WI is a tool for technicians to “quick‐install” an radio unit in a link with minimum effort.
It may also be employed by a user for a quick look at current operating parameters and the
Recent Events logs.
21.4 How it Works
Assume the link setup, which we used in Initial Link Configuration and later.
On the managing computer, point your browser to10.104.4.2 and log on as shown below. You
can also log on over the air to the Slave ODU in the same way.

What it Provides
For stand‐alone or unregistered radio units, you must connect a managing computer directly
to the radio unit and again log on as shown below.
21.5 What it Provides
The WI is a developing technology. It is possible that the current distributed release may have
additional or slightly different features from those shown here. The description below, should
nevertheless give you a good idea of how to use the WI.
21.6 Prerequisites
21.6.1 Hardware
You need a regular LAN connection between a managing computer and one of the link radio
units. The WI can be used directly opposite the RT‐A(HBS) any of its RT‐B(HSU)s. It can also be
used over the air from the RT‐A(HBS) to any registered RT‐B(HSU).
21.6.2 Software
Your computer should have at least version 6 of MS Internet Explorer. The Web interface also
works with other browsers such as Mozilla Firefox version 3 and later.
21.6.3 Technical Background
You should be familiar with the concepts underlying the RADWIN Manager and preferably
with the Manager itself.
21.7 Special Considerations Working with the
WI
21.7.1 Advanced Configurations
For setup configurations using features such as HSS, VLAN and QoS, you will need to use the
RADWIN Manager.
21.7.2 Operational Effects
Several WI functions cause temporary sync loss. Typically, changing the number of antennas
falls into this category. These cases will be pointed out in Warning messages.

Some Working Tips
21.7.3 Some Working Tips
You can:
» Log on to a radio unit on the default IP address of 10.0.0.120/8, set the Link ID and IP
address instead of using the RADWIN Manager as in RADWIN Manager. Unlike the
Local Connection method, you need to reset the radio unit to see the change in the
Web Interface.
» Change the operating Band for the link instead of using the RADWIN Manager. You
can revert it the same way or by a direct connection, logged on as Installer.
» Look at Recent Events for either site
You cannot:
» Change default Tx Power
» Configure Spatial Multiplexing/Diversity
» Manage other features such as GSU (when supported), VLAN, QoS
» Perform Software upgrade
Be very careful:
» Using this tool if your link is providing Customer Service which may not be interrupted
with sync‐losses
21.8 Logging on
To use the Web interface, simply point your browser to the IP address of the site to which you
are connected.
Figure 21‐1: Web interface ‐ Log on

Site Management ‐ Master ODU
The User Name and Password are respectively, admin and netman as used for Telnet access.
You must click the Log In button to effect entry to the WI.
The foregoing applies to both radio units. The functionality described below is predominantly
site oriented. Site configuration items shown for Site_A may be carried out for Site_B by
logging on to it.
21.9 Site Management ‐ Master ODU
21.9.1 The Main Window
Figure 21‐2: Web interface ‐ Main window
The link ID (EBGX20560334) appears all or in part as the heading. The main panel is self
explanatory. The green Active indicator will vary according to the status of the Master ODU
shown by the RADWIN Manager. The top green item (Registered here) indicates the status of
the Slave ODU.

The Tool Bar
Figure 21‐3: Link Status panel
(it will typically be Active, Inactive, Probing etc.)
21.9.2 The Tool Bar
Configure
The Configure button opens the following display:
System
The Name, Contact and Location field may be changed. Using Save commits them. Clicking
Refresh reverts the fields to their last Saved values.
Air Interface
You can change the Sector ID (Link ID) and the Buzzer status.

The Tool Bar
You can use the Change Band button to open the following display:
The Antenna & Tx Power button opens up the following window:

The Tool Bar
The only item that can be changed is the Antenna Type:
Changing Antenna Type will call a link‐wide sync loss.
Inventory
The Inventory display is for information only.
Management
The Management fields are all fully editable:

The Tool Bar
If you change any of these fields, you will cause an radio unit reset:
Other
You may change the radio unit LAN port configuration:

The Tool Bar
You will receive the following notification:
This action of course, has no bearing on the link.

Events
21.9.3 Events
The Recent Event List is displayed:
21.9.4 Reset
Use this button to reset the radio unit. As usual, for any action causing a sync loss you wil be
asked to confirm the action:
21.10 Site Management ‐ Slave ODU
Slave ODU site management is the same as that for the Master ODU.

Part 7: Product Reference
Release 4.2.40
Appendix A: Terminology
Table A‐1: Terminology (Sheet 1 of 2)
Term Description
Assured throughput Actual number of timeslots allocated to an HSU
Base Station: a radio that can transmit and receive to more
BS
than one point. See also HBS
Data traffic from an HBS to an HSU or from a Master ODU to
Downlink
a Slave ODU
Equivalent (or Effective) Isotropically Radiated Power: Power
EIRP that a theoretical isotropic antenna emits to produce the
peak power density (see EIRP on page 19‐2).
GHSS GPS Hub Site Synchronization
High capacity Base Station. Same as a BS, same as Master
HBS
ODU, same as RT‐A(HBS)
Hub Site Client: A radio unit that is co‐located with other
HSC units, and receives a synchronization signal. This unit can
only be an HBS.
Hub Site Master: the source of the synchronization signal for
Hub Site Synchronization. This is usually one of the radio
HSM
units, but not necessarily, as the “master” can be a signal
from a GPS satellite.
High capacity Subscriber Unit. Same as an SU, same as a
HSU
Slave ODU, same as RT‐B(HSU).
The dominant radio unit in a link. Same as Base Station.
Master ODU
Same as a BS, same as RT‐A(HBS)
MIR Maximum Information Rate
Outdoor Unit. This is a generic term for a radio unit packaged
in an enclosure designed to comply with outdoor
ODU
regulations. This term can also be used to refer to the indoor
radio, RADWIN 2000i.
RADWIN 2000+ Series User Manual Release 4.2.40 A‐1

Table A‐1: Terminology (Sheet 2 of 2)
Term Description
PtMP Point to Multi‐Point
PtP Point to Point
QoS Quality of Service
RSS Radio Signal Strength
RT‐A(HBS) Radio Terminal A (HBS). Same as a BS, same as Master ODU.
RT‐B(HSU) Radio Terminal B (HSU). Same as an SU, same as a Slave ODU.
A group of radios that consists of one HBS and several HSUs
that communicate with the HBS. In the case of the RADWIN
Sector
2000+ Series, which is only point‐to‐point, this is only one
HBS vs. one HSU, also called a Link.
SLA Service Level Agreement
The non‐dominant radio unit in a link. Same as Subscriber
Slave ODU
Unit, same as SU, same as HSU, same as RT‐B(HSU).
Subscriber Unit: a radio that can transmit and receive to one
SU
point. See also HSU and RT‐B(HSU).
Uplink Data traffic from an HSU to an HBS
UCBP FCC Unrestricted Contention Based Protocol
RADWIN 2000+ Series User Manual Release 4.2.40 A‐2

Appendix B: RF Exposure
The antennas used for the following transmitters must be installed so as to provide a
minimum separation distance from bystanders as specified in the following tables:
Table B‐1: Safety Distances for the RADWIN 2000 A+ and RADWIN 2000 C+
Frequency Antenna gain Min. Safety
FCC ID IC ID
band [GHz] [dBi] Distance [cm]
5.8 (PTP) Q3KRW5XMOD 5100A‐RW5XMOD 32 354
5.8 (PMP) Q3KRW5XMOD 5100A‐RW5XMOD All gains 20
5.3/5.4 Q3KRW5XMOD 5100A‐RW5XMOD All gains 20
5.1 (PTP) Q3KRW5XMOD 5100A‐RW5XMOD 32, 29 125
5.1 (PMP) Q3KRW5XMOD 5100A‐RW5XMOD All gains 20
4.9 Q3KRW5XMOD 5100A‐RW5XMOD 32, 29 96
4.9 Q3KRW5XMOD 5100A‐RW5XMOD 24 72
4.9 Q3KRW5XMOD 5100A‐RW5XMOD 16, 15.5 31
3.5 IC only ‐‐‐ 5100A‐RW3XMOD 26 110
3.5 IC only ‐‐‐ 5100A‐RW3XMOD 22 70
3.5 IC only ‐‐‐ 5100A‐RW3XMOD 17 40
3.5 IC only ‐‐‐ 5100A‐RW3XMOD 15 31
3.5 IC only ‐‐‐ 5100A‐RW3XMOD 14 28
RADWIN 2000+ Series User Manual Release 4.2.40 B‐1

Table B‐1: Safety Distances for the RADWIN 2000 A+ and RADWIN 2000 C+ (Continued)
FCC ID IC ID
2.4 (PTP) Q3KRW24MOD 5100A‐RW24MOD 20 52
2.4 (PTP) Q3KRW24MOD 5100A‐RW24MOD 17.5 43
2.4 (PMP) Q3KRW24MOD 5100A‐RW24MOD All gains 20
Table B‐2: Safety Distances for the RADWIN 2000 D+ and RADWIN 2000i
FCC ID IC ID
5.8 (PTP) Q3K‐5XACMOD 5100A‐5XACMOD 32 313
5.8 (PTP) Q3K‐5XACMOD 5100A‐5XACMOD 20.5 Smart 94
5.8 (PTMP) Q3K‐5XACMOD 5100A‐5XACMOD All gains 20
5.3/5.4 Q3K‐5XACMOD 5100A‐5XACMOD All gains 20
5.1 (PTP) Q3K‐5XACMOD 5100A‐5XACMOD 32, 29 125
5.1 (PTP) Q3K‐5XACMOD 5100A‐5XACMOD 20.5 Smart 67
5.1 (PMP) Q3K‐5XACMOD 5100A‐5XACMOD All gains 20
4.9 Q3K‐5XACMOD 5100A‐5XACMOD 32, 29 80
4.9 Q3K‐5XACMOD 5100A‐5XACMOD 24 57
4.9 Q3K‐5XACMOD 5100A‐5XACMOD 21, 20.5 Smart 45
4.9 Q3K‐5XACMOD 5100A‐5XACMOD 16, 15.5 25
4.9 Q3K‐5XACMOD 5100A‐5XACMOD 14 and lower 20
Table B‐3: Safety Distances for RADWIN 2000+ Series ETSI Products
Min. Safety
Frequency Band Antenna gain
Distance
[GHz] [dBi]
[cm]
5.8/5.4/5.3/ All gains 20
RADWIN 2000+ Series User Manual Release 4.2.40 B‐2

Appendix C: Setting Antenna
Parameters
C.1 Antenna Issues
Before proceeding to antenna installation details, the following background information
should be considered:
C.2 About Single and Dual Antennas
Each RADWIN 2000+ Series ODU is made of two radio transceivers (radios). The radios make
use of algorithms that utilize both Spatial Multiplexing and Diversity resulting in enhanced
capacity, range and link availability. The number of antennas used is determined by user
configuration and by automatic system decisions, explained below.
C.2.1 Dual Antennas at the RT‐A(HBS) and RT‐B(HSU)
When using dual antennas at both sites (single bipolar antenna or two unipolar antennas) you
can choose between Spatial Multiplexing Mode and Diversity Mode.
Spatial Multiplexing Mode
Under this mode, the system doubles the link capacity. At the same time, it keeps the same
rate and modulation per radio as was used with single antenna, thus increasing capacity,
range and availability.
For example, at 80MHz CBW, using a dual antenna, a RADWIN 2000 D+ radio unit can transmit
at modulation of 256QAM and FEC of 5/6 and get an air rate of 866.7 Mbps, compared to
433.3 Mbps with single antenna.
To work in this mode, each antenna port must be connected to an antenna, the RSS level in
both receivers should be balanced and a minimal separation between the antennas must be
maintained. (For example, by using dual polarization antennas a cross polarization separation
is attained).
RADWIN 2000+ Series User Manual Release 4.2.40 C‐1

Single Antennas at Both Sites
Upon selecting Antenna Type as Dual, a RADWIN 2000+ Series radio automatically selects this
mode and doubles the air rates.
The RADWIN Manager indicates a case of unbalanced RSS between the two antennas in the
center panel.
Diversity Mode
Diversity Mode uses two antennas to improve the quality and reliability of the link. Often,
there is not a clear line‐of‐sight (LOS) between transmitter and receiver. Instead the signal is
reflected along multiple paths before finally being received.
Each such “bounce” can introduce phase shifts, time delays, attenuations, and even
distortions that can destructively interfere with one another at the aperture of the receiving
antenna. Antenna diversity is especially effective at mitigating these multi‐path situations.
This is because multiple antennas afford a receiver several recordings of the same signal. Each
antenna will be exposed to a different interference environment. Thus, if one antenna is
undergoing a deep fade, it is likely that another has a sufficient signal. Collectively such a
system can provide a robust link.
Antenna diversity requires a separation between the antennas; this is done by using a dual‐
polarization antenna or by two spatially separated antennas.
Use Diversity instead of Spatial Multiplexing in the following situations:
• When the system cannot operate in Spatial Multiplexing Mode
• When one of the receivers has high interference compared to the second receiver (i.e.
the system is “unbalanced”)
• When you achieve higher capacity in Diversity Mode than in Spatial Multiplexing Mode
• When high robustness is of importance and the capacity of Diversity Mode is sufficient
(up to 25 Mbps full duplex)
C.2.2 Single Antennas at Both Sites
By selecting a single antenna at both sites, the radio units operate with a single radio that is
connected to the ANT 1 connector. The second radio is automatically shut down.
C.2.3 Single at One Site, Dual Antennas at the Other
In this mode one of the sites uses the radio unit with a single antenna while the other site
uses the radio unit with a dual antenna.
The advantages in this mode in comparison to using a single antenna in both sites are
doubled total Tx Power and additional polarization and/or space diversity (depending on the
polarization of installed antennas).
The air rates used in this mode are same as when using single antennas in both sites.

Considerations for Changing Antenna Parameters
C.3 Considerations for Changing Antenna
Parameters
Let:
max Available Tx Power denote the maximum Tx Power practically available from an ODU. (It
appears as Tx Power per Radio.)
maxRegEIRP denote the maximum EIRP available by regulation. It will be determined by
three factors:
• per band/regulation
• per channel bandwidth
• antenna gain
maxRegTxPower denote the maximum regulatory Tx Power for the equipment, also having
regard the above three points.
Then, the following relationship must be satisfied:
maxAvailableTxPower  min(maxRegEIRP ... (*)
– AntennaGain + CableLoss maxRegTxPower)
The Tx Power (per radio) indicates the power of each radio inside the ODU and is used for Link
Budget Calculations. The Tx Power (System) shows the total transmission power of the ODU
and is used to calculate the EIRP according to regulations.
• To see the relationship between Tx Power (radio) and Tx Power
(system), note that dBm = 10  log 10milliWatt so that if you
double the power in milliWatts (for two radios) then dBm will
increase by 10  log 102  3 .
• The Max EIRP level will be automatically set according to the
selected band and regulation.
• The EIRP level is the sum of the System Tx Power and the Antenna
Gain minus the Cable Loss.
The inequality (*) above is always satisfied by the system in accordance with the relevant
regulation.
The precise relationship between the items in inequality (*) is as follows:
• Required Tx Power (per radio) will be adjusted down to the lesser of the value entered
and maxAvailableTxPower
• Tx Power (system) is maxAvailableTxPower + 3 (for 2 radios)
• Max EIRP is maxRegEIRP.

Appendix D: Wiring
Specifications
D.1 ODU‐PoE Cable ()
The ODU‐PoE cable is shielded/outdoor class CAT‐5e, 4 twisted‐pair 24 AWG terminated with
RJ‐45 connectors on both ends. A cable gland on the ODU side provides hermetic sealing.
The following table shows the connector pinout:
Table D‐1: ODU‐PoE RJ‐45 Connector Pinout
Function Color PoE ODU
Rx N White/Green 1 1
Rx T Green 2 2
Tx T White/Orange 3 3
Tx N Orange 6 6
Power (+) Blue 4 4
Power (+) White/Blue 5 5
Power () White/Brown 7 7
Power () Brown 8 8
Table D‐2: LAN‐GbE PoE RJ‐45 Connector Pinout
Function Color PoE LAN
TxRx A White/Green 1 1
TxRx A Green 2 2
TxRx B White/Orange 3 3
TxRx B Orange 6 6
RADWIN 2000+ Series User Manual Release 4.2.40 D‐1

HBS/HSS Unit Connection Pinout
Table D‐2: LAN‐GbE PoE RJ‐45 Connector Pinout (Continued)
Function Color PoE LAN
TxRx C & Power(+) Blue 4 4
TxRx C & Power(+) White/Blue 5 5
TxRx D & Power(‐) White/Brown 7 7
TxRx D & Power(‐) Brown 8 8
D.2 HBS/HSS Unit Connection Pinout
The pinout is for the HSS Unit, used in serial HSS.
Table D‐3: HBS/HSS Unit Connection Pinout
ODU HSS UNIT
Color
RJ‐45 RJ‐45
White/Green 1 1
Green
Not connected
White/Orange
Orange 6 6
Blue 4 4
White/Blue 5 5
White/Brown 7 7
Brown 8 8

User Port Connectors
D.3 User Port Connectors
D.3.1 LAN Port
The LAN 10/100BaseT interface terminates in an 8‐pin RJ‐45 connector, wired in accordance
to Table D‐4.
Table D‐4: Fast Ethernet Connector Pinout
Function Signal Pin
Transmit Data (positive) TD (+) 1
Transmit Data (negative) TD (–) 2
Receive Data (positive) RD (+) 3
Receive Data (negative) RD (–) 6
D.4 DC Power Terminals
D.4.1 DC PoE
Table D‐5: Terminal Block 2‐pin ‐48VDC
Function Pin
+ Right
– Left

Appendix E: Regional Notice:
French Canadian
E.1 Procédures de sécurité
E.1.1 Généralités
Avant de manipuler du matériel connecté à des lignes électriques ou de télécommunications,
il est conseillé de se défaire de bijoux ou de tout autre objet métallique qui pourrait entrer en
contact avec les éléments sous tension.
E.1.2 Mise à la terre
Tous les produits RADWIN doivent être mis à la terre pendant l'usage courant. La mise à la
terre est assurée en reliant la fiche d'alimentation à une prise de courant avec une protection
de terre. En outre:
• La cosse de masse sur l'IDU‐C doit être constamment connectée à la protection de
terre, par un câble de diamètre de 18 AWG ou plus. Le matériel monté sur rack doit être
installé seulement sur des racks ou armoires reliés à la terre
• Une ODU doit mise à la terre par un câble de diamètre de 10 AWG ou plus
• Il ne doit pas y avoir de fusibles ou d'interrupteurs sur la connection à la terre
De plus:
• Il faut toujours connecter la terre en premier et la déconnecter en dernier
• Il ne faut jamais connecter les câbles de télécommunication à du matériel non à la terre
• Il faut s'assurer que tous les autres câbles sont déconnectés avant de déconnecter la
terre
E.1.3 Protection contre la foudre
L'utilisation de dispositifs de protection contre la foudre dépend des exigences
réglementaires et de l'utilisateur final. Toutes les unités extérieures RADWIN sont conçues
avec des circuits de limitation de surtension afin de minimiser les risques de dommages dus à
RADWIN 2000+ Series User Manual Release 4.2.40 E‐1

Précautions de sécurité pendant le montage de ODU
la foudre. RADWIN conseille l'utilisation d'un dispositif de parafoudre supplémentaire afin de
protéger le matériel de coups de foudre proches.
Matériel supplémentaire requis
L'équipement requis pour l'installation du matériel est le suivant:
• Pince à sertir RJ‐45 (si un câble pré‐assemblé ODU/IDU n'est pas utilisé)
• Perceuse (pour le montage sur mur seulement)
• Câbles de terre IDU et ODU
• Clef 13 mm (½)
• Câble ODU ‐ IDU si non commandé (type extérieur, CAT‐5e, 4 paires torsadées, 24 AWG)
• Colliers de serrage
• Ordinateur portable avec Windows 2000 ou Windows XP.
E.1.4 Précautions de sécurité pendant le montage de ODU
Avant de connecter un câble à l'ODU, la borne protectrice de masse (visse) de l'ODU doit être
connectée à un conducteur externe protecteur ou à un pylône relié à la terre. Il ne doit pas y
avoir de fusibles ou d'interrupteurs sur la connection à la terre.
Seulement un personnel qualifié utilisant l'équipement de sécurité approprié doit pouvoir
monter sur le pylône d'antenne. De même, l'installation ou le démontage de ODU ou de
pylônes doit être effectuée seulement par des professionnels ayant suivi une formation.
 Pour monter l'ODU:
1. Vérifier que les supports de fixation de l'ODU sont correctement mis à la terre.
2. Monter l'unité ODU sur le pylône ou sur le mur; se référer à la Installation sur
pylône et mur au dessous.
3. Connecter la câble de terre au point de châssis sur l'ODU.
4. Relier le câble ODU‐IDU au connecteur ODU RJ‐45.
5. Visser les presses‐étoupe de câbles pour assurer le scellement hermétique des
unités ODU.
6. Attacher le câble au pylône ou aux supports en utilisant des colliers classés UV.
7. Répéter la procédure sur le site distant.
Ne pas se placer en face d'une ODU sous tension.
E.1.5 Connecter la terre à IDU‐C
Connecter un câble de terre de 18 AWG à la borne de masse de l'appareil. L'appareil doit être
constamment connecté à la terre.

Installation sur pylône et mur
• Les appareils sont prévus pour être installés par un personnel de
service.
• Les appareils doivent être connectés à une prise de courant avec
une protection de terre.
• Le courant CC du IDU‐C doit être fourni par l'intermédiaire d'un dis‐
joncteur bipolaire et le diamètre du câble doit être de 14 mm avec
un conduit de 16 mm.
E.2 Installation sur pylône et mur
L' ODU ou l'O‐PoE peuvent être montés sur un pylône ou un mur.
E.2.1 Contenu du kit de montage ODU
Le kit de montage ODU comprend les pièces suivantes:
Figure E‐1: Contenu du kit de montage ODU

Montage sur un pylône
E.2.2 Montage sur un pylône
Figure E‐2: Montage sur un pylône (1) Figure E‐3: Montage sur un pylône (2)
E.2.3 Montage sur un mur
Figure E‐4: Montage sur un mur (1) Figure E‐5: Montage sur un mur (2)
E.2.4 Montage d'une antenne externe
L'antenne externe optionnelle peut être montée sur un pylône.
E.2.5 Contenu du kit de montage d'une antenne externe
Le kit de montage d'une antenne externe comprend les pièces suivantes
• Douze rondelles plates
• Huit rondelles élastiques

Contenu du kit de montage d'une antenne externe
• Huit écrous hex
• Quatre boulons
• Un support en U
• Un support à pivotement
• Deux courroies de fixation en métal
 Pour installer une antenne externe sur un pylône:
1. Attacher le support en U à l'arrière de l'antenne en utilisant quatre rondelles plates,
quatre rondelles élastiques et quatre écrous hex.
2. Attacher le support à pivotement au support en U en utilisant huit rondelles plates,
quatre rondelles élastiques, quatre écrous hex et quatre boulons.
3. Passer les deux courroies de fixation par les fentes verticales dans le support à
pivotement.
4. Attacher l'antenne au pylône en utilisant les deux courroies de fixation .
Ajuster l'inclinaison nécessaire en utilisant l'échelle angulaire et serrer tous les boulons et
écrous à la position requise.

Part 8: Regulatory Notices
Release 4.2.40
Regulatory Compliance
General Note
This system has achieved Type Approval in various countries around the world. This means
that the system has been tested against various local technical regulations and found to
comply. The frequency bands in which the system operates may be “unlicensed” and in these
bands, the system can be used provided it does not cause interference.
FCC ‐ Compliance
This equipment has been tested and found to comply with the limits for a Class B digital
device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference in a residential installation. This equipment
generates, uses and can radiate radio frequency energy and, if not installed and used in
accordance with the instructions, may cause harmful interference to radio communications.
However, there is no guarantee that interference will not occur in a particular installation. If
this equipment does cause harmful interference to radio or television reception, which can
be determined by turning the equipment off and on, the user is encouraged to try to correct
the interference by one or more of the following measures:
• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the
receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
Changes or modifications to this equipment not expressly approved by the party responsible
for compliance could void the user's authority to operate the equipment.
It is the responsibility of the installer to ensure that when using the
outdoor antenna kits in the United States (or where FCC rules apply), only
those antennas certified with the product are used. The use of any
antenna other than those certified with the product is expressly forbidden
by FCC rules 47 CFR part 15.204.
It is the responsibility of the installer to ensure that when configuring the
radio in the United States (or where FCC rules apply), the Tx power is set
according to the values for which the product is certified. The use of Tx
power values other than those, for which the product is certified, is
expressly forbidden by FCC rules 47 CFR part 15.204.
Indoor Units comply with part 15 of the FCC rules. Operation is subject to the following two
conditions:
(1) These devices may not cause harmful interference.

Outdoor units and antennas should be installed ONLY by experienced
installation professionals who are familiar with local building and safety
codes and, wherever applicable, are licensed by the appropriate
government regulatory authorities. Failure to do so may void the product
warranty and may expose the end user or the service provider to legal and
financial liabilities. Resellers or distributors of this equipment are not
liable for injury, damage or violation of regulations associated with the
installation of outdoor units or antennas. The installer should configure
the output power level of antennas according to country regulations and
antenna type.
• Where Outdoor units are configurable by software to Tx power val‐
ues other than those for which the product is certified, it is the
responsibility of the Professional Installer to restrict the Tx power to
the certified limits.
• This product was tested with special accessories ‐ indoor unit (IDU or
PoE), FTP CAT‐5e shielded cable with sealing gasket, 10 AWG ground‐
ing cable ‐ which must be used with the unit to insure compliance.
(2) These devices must accept any interference received, including interference that may
cause undesired operation.
Canadian Emission Requirements for Indoor Units
This Class B digital apparatus complies with Canadian ICES‐003.
Cet appareil numẻrique de la classe B est conforme ả la norme NMB‐003 du Canada.
China MII
Operation of the equipment is only allowed under China MII 5.8GHz band regulation
configuration with EIRP limited to 33 dBm (2 Watt).
India WPC
Operation of the equipment is only allowed under India WPC GSR‐38 for 5.8GHz band
regulation configuration.
Unregulated
In countries where the radio is not regulated the equipment can be operated in any
regulation configuration, best results will be obtained using Universal regulation
configuration.
Safety Practices
Applicable requirements of National Electrical Code (NEC), NFPA 70; and the National
Electrical Safety Code, ANSI/IEEE C2, must be considered during installation.

NOTES:
1. A Primary Protector is not required to protect the exposed wiring as long as the exposed
wiring length is limited to less than or equal to 140 feet, and instructions are provided to
avoid exposure of wiring to accidental contact with lightning and power conductors in
accordance with NEC Sections 725‐54 (c) and 800‐30.
In all other cases, an appropriate Listed Primary Protector must be provided. Refer to Articles
800 and 810 of the NEC for details.
2. For protection of ODU against direct lightning strikes, appropriate requirements of NFPA
780 should be considered in addition to NEC.
3. For Canada, appropriate requirements of the CEC 22.1 including Section 60 and additional
requirements of CAN/CSA‐B72 must be considered as applicable.

RADWIN Worldwide Offices
Corporate and EMEA Regional Headquarters
Corporate and EMEA Headquarters North America Regional
27 Habarzel Street Headquarters
Tel Aviv,6971039
Israel 900 Corporate Drive
Tel: +972.3.766.2900 Mahwah, NJ, 07430
Fax: +972.3.766.2902 USA
Tel: +1-877-RADWIN US
Email: sales@radwin.com (+1-877 723-9468)
Tel: +1-201-252-4224
Fax: +1-201-621-8911
Email: salesna@radwin.com
Customer Support - North America:
Hours: 9 am - 6 pm EST (Mon - Fri)
Email: supportusa@radwin.com
RADWIN Regional Offices
RADWIN Brazil RADWIN Mexico
Av. Chucri Zaidan, 920 – 9º Quinto #20 Col El Centinela
São Paulo, 04583-904 Mexico, DF, O4450
Brazil Mexico
Tel: +55.11.3048-4110 Tel: +52 (55) 5689 8970
Email: salesbr@radwin.com Email: salesmx@radwin.com
RADWIN Peru RADWIN India
Av. Antares 213 E-13,B-1 Extn., Mohan Co-operative Industrial Estate
Lima, 33 New Delhi, 110 044
Peru India
Tel: +511.6285105 Tel: +91-11-40539178
Fax: +511-990304095 Email: salesin@radwin.com
Email: salespe@radwin.com
RADWIN Philippines RADWIN South Africa
5 Bur Bank St. P.O. Box 3554, Rivonia
Laguna, Belair, Santa Rosa Johannesburg ,2128
Laguna Philippines South Africa
Tel: +63 928 7668230 Tel: +27 (0)82 551 5600
Email: salesph@radwin.com Email: sales@radwin.com
RADWIN Italy and Spain RADWIN Central America
Piazza Arenella 7/H Calle La CaÃ±ada # 108-E
Napoli ,80128 Jardines de la Hacienda
Italy Ciudad Merliot El Salvador
Tel:+390815564116 Tel: +503 2278-5628
Fax: +39335433620 Email: sales@radwin.com
Email: salesit@radwin.com
RADWIN 2000+ Series User Manual Release 4.2.40 i
RADWIN Worldwide Offices (Continued)
RADWIN South East Asia
All Season Mansion
87/38 Wireless Road Lumpinee
Bangkok ,10330
Thailand
Tel: +66811707503
Email: sales@radwin.com

RADWIN 2000+ Series User Manual Release 4.2.40 ii
RADWIN 2000+ Series
User Manual
Cat.No. DO0185370/0.2
This manual contains information that is proprietary to RADWIN Ltd (RADWIN hereafter). No
part of this publication may be reproduced in any form whatsoever without prior written
approval by RADWIN.
Right, title and interest, all information, copyrights, patents, know‐how, trade secrets and
other intellectual property or other proprietary rights relating to this manual and to the
RADWIN products and any software components contained therein are proprietary products
of RADWIN protected under international copyright law and shall be and remain solely with
RADWIN.
The RADWIN name is a registered trademark of RADWIN. No right, license, or interest to such
trademark is granted hereunder, and you agree that no such right, license, or interest shall be
asserted by you with respect to such trademark.
You shall not copy, reverse compile or reverse assemble all or any portion of the User Manual
or any other RADWIN documentation or products. You are prohibited from, and shall not,
directly or indirectly, develop, market, distribute, license, or sell any product that supports
substantially similar functionality based or derived in any way from RADWIN products.Your
undertaking in this paragraph shall survive the termination of this Agreement.
This Agreement is effective upon your opening of a RADWIN product package and shall
continue until terminated. RADWIN may terminate this Agreement upon the breach by you of
any term thereof. Upon such termination by RADWIN, you agree to return to RADWIN any
RADWIN products and documentation and all copies and portions thereof.
For further information contact RADWIN at one of the addresses under Worldwide Contacts
below or contact your local distributor.
Disclaimer
The parameters quoted in this document must be specifically confirmed in writing before
they become applicable to any particular order or contract. RADWIN reserves the right to
make alterations or amendments to the detail specification at its discretion. The publication
of information in this document does not imply freedom from patent or other rights of
RADWIN, or others.
Trademarks
WinLink 1000, RADWIN 2000, RADWIN 5000, RADWIN 6000 and RADWIN 600 are
trademarks of RADWIN Ltd
Windows 2000, XP Pro, Vista, Windows 7 and Internet Explorer are trademarks of
Microsoft Inc.
Mozilla and Firefox are trademarks of the Mozilla Foundation.
RADWIN 2000+ Series User Manual Release 4.2.40 iii

Other product names are trademarks of their respective manufacturers.

RADWIN 2000+ Series User Manual Release 4.2.40 iv
RADWIN 2000+ Series User Manual Release 4.2.40 v

Radwin 2000+ Series Point To Point Broadband Wireless: User Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Radwin 2000+ Series Point To Point Broadband Wireless: User Manual

Uploaded by

Copyright:

Available Formats

USER

RADWIN 2000+ Series User Manual Release 4.2.40 iii

RADWIN 2000+ Series User Manual Release 4.2.40 vii

RADWIN 2000+ Series User Manual Release 4.2.40 viii

RADWIN 2000+ Series User Manual Release 4.2.40 1‐1

RADWIN 2000+ Series User Manual Release 4.2.40 1‐2

RADWIN 2000+ Series User Manual Release 4.2.40 2‐1

RADWIN 2000+ Series User Manual Release 4.2.40 2‐2

RADWIN 2000+ Series User Manual Release 4.2.40 2‐3

RADWIN 2000+ Series User Manual Release 4.2.40 3‐1

RADWIN 2000+ Series User Manual Release 4.2.40 3‐2

RADWIN 2000+ Series User Manual Release 4.2.40 3‐3

RADWIN 2000+ Series User Manual Release 4.2.40 3‐4

RADWIN 2000+ Series User Manual Release 4.2.40 3‐5

RADWIN 2000+ Series User Manual Release 4.2.40 4‐1

RADWIN 2000+ Series User Manual Release 4.2.40 4‐2

RADWIN 2000+ Series User Manual Release 4.2.40 4‐3

RADWIN 2000+ Series User Manual Release 4.2.40 4‐4

RADWIN 2000+ Series User Manual Release 4.2.40 4‐5

RADWIN 2000+ Series User Manual Release 4.2.40 4‐6

Flat Antenna Dish Antenna Mesh Antenna

RADWIN 2000+ Series User Manual Release 4.2.40 4‐7

RADWIN 2000+ Series User Manual Release 4.2.40 4‐8

RADWIN 2000+ Series User Manual Release 4.2.40 4‐9

RADWIN 2000+ Series User Manual Release 4.2.40 4‐10

RADWIN 2000+ Series User Manual Release 4.2.40 4‐11

RADWIN 2000+ Series User Manual Release 4.2.40 4‐12

RADWIN 2000+ Series User Manual Release 4.2.40 4‐13

RADWIN 2000+ Series User Manual Release 4.2.40 4‐14

RADWIN 2000+ Series User Manual Release 4.2.40 4‐15

RADWIN 2000+ Series User Manual Release 4.2.40 4‐16

RADWIN 2000+ Series User Manual Release 4.2.40 4‐17

RADWIN 2000+ Series User Manual Release 4.2.40 4‐18

RADWIN 2000+ Series User Manual Release 4.2.40 4‐19

RADWIN 2000+ Series User Manual Release 4.2.40 4‐20

RADWIN 2000+ Series User Manual Release 4.2.40 4‐21

RADWIN 2000+ Series User Manual Release 4.2.40 4‐22

RADWIN 2000+ Series User Manual Release 4.2.40 4‐23

RADWIN 2000+ Series User Manual Release 4.2.40 4‐24

RADWIN 2000+ Series User Manual Release 4.2.40 4‐25

RADWIN 2000+ Series User Manual Release 4.2.40 4‐26

RADWIN 2000+ Series User Manual Release 4.2.40 4‐27

RADWIN 2000+ Series User Manual Release 4.2.40 4‐28

RADWIN 2000+ Series User Manual Release 4.2.40 4‐29

RADWIN 2000+ Series User Manual Release 4.2.40 4‐30

RADWIN 2000+ Series User Manual Release 4.2.40 4‐31

RADWIN 2000+ Series User Manual Release 4.2.40 4‐32

RADWIN 2000+ Series User Manual Release 4.2.40 4‐33

RADWIN 2000+ Series User Manual Release 4.2.40 4‐34

RADWIN 2000+ Series User Manual Release 4.2.40 4‐35

RADWIN 2000+ Series User Manual Release 4.2.40 4‐36

RADWIN 2000+ Series User Manual Release 4.2.40 4‐37

RADWIN 2000+ Series User Manual Release 4.2.40 4‐38

RADWIN 2000+ Series User Manual Release 4.2.40 4‐39

RADWIN 2000+ Series User Manual Release 4.2.40 4‐40

Memory 512 Mb 1 Gb 2 Gb

RADWIN 2000+ Series User Manual Release 4.2.40 5‐1

RADWIN 2000+ Series User Manual Release 4.2.40 5‐2

RADWIN 2000+ Series User Manual Release 4.2.40 5‐3

RADWIN 2000+ Series User Manual Release 4.2.40 5‐4

RADWIN 2000+ Series User Manual Release 4.2.40 5‐5

RADWIN 2000+ Series User Manual Release 4.2.40 5‐6

Observer admin Monitoring Read‐Only public Read‐Only public