L-Series Digital Microwave Radio

Proteus AMTL-Series

Digital Microwave Radio4 TO 50 MBIT/S AT 7 TO 38 GHZ;

2 TO 16E1, 4 TO 12DS1, AND ETHERNET

System User’s ManualPart Number: 8831901-00

Revision JIssued: 10/06

© Copyright 2005, Microwave Networks Inc., USA. All rights reserved.

Information in this manual is subject to change without notice. No part of this publication may be reproduced or distributed in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microwave Networks Incorporated.

TRADEMARKS Proteus AMT, Proteus AMT L-Series, and Proteus EM are registered trademarks of Microwave Networks Inc.

Microsoft is a registered trademark of Microsoft Corp.

HP is a registered trademark of Hewlett-Packard Corp.

All other products or services referred to in this manual are the trademarks, service marks, or product names of their respective holders.

DISCLAIMER

Products, specifications, configurations, and other technical information in this manual are subject to change without notice. All the statements, technical information, and recommendations are believed to be accurate and reliable but are presented without warranty of any kind. Users take full responsibility for the application of any products specified herein.

IN NO EVENT SHALL MICROWAVE NETWORKS INCORPORATED OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF MICROWAVE NETWORKS INCORPORATED HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

COMPLIANCE

Microwave Networks Incorporated hereby declares that this wireless communication system is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC.

This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

Proteus LC System User’s Manual Page v

WARRANTY

Commercial Warranty

Products manufactured by Microwave Networks Incorporated ("MNI") are warranted to be free from defect in material and workmanship under normal use and service for a period of two (2) years from the date of shipment. In the event of a defect during the warranty period, Buyer will return the defective item to the MNI depot repair facility for repair or replacement. Repair at MNI's option may include the replacement of parts or equipment and all replaced parts or equipment shall be the property of MNI. Parts or equipment replaced during the warranty period are warranted for the remainder of the original applicable warranty period or ninety (90) days, whichever is greater. This expressed warranty is extended by MNI to the original Buyer for commercial, industrial or governmental use. Such action on the part of MNI shall be the full extent of MNI's liability and Buyer's exclusive remedy for breach of warranty. Expenses of Buyer such as travel expenses are not covered by this warranty.

This warranty extends only to products manufactured by MNI, and it is expressly conditioned upon the equipment having been installed in accordance with the installation practices accepted by the telecommunications industry, the standard installation and configuration practices recommended by MNI, and the equipment having been maintained in accordance with MNI recommended standard maintenance practices. Vendor products and other equipment not manufactured by MNI are excluded, but carry their own separate limited warranties.

This warranty shall automatically terminate if the product is used in other than its normal and customary use, has been subject to misuse, accident, neglect, or damage, is improperly disassembled, improper alterations or repairs, or if nonconforming parts are used in the product, unless done by a service facility authorized by MNI to perform warranty service. The warranty for Network Management Systems (NMS) shall automatically terminate if software is altered, added, or removed from the platform without the prior approval of MNI. NMS provided by MNI do not include virus protection software and this warranty does not cover damages caused by computer viruses.

WARRANTY

Proteus LC System User’s Manual Page vi

Because each radio system is unique, MNI disclaims liability for range, coverage, or operation of a system as a whole under this warranty. This warranty shall not cover any damages caused by Acts of God including, but not limited to, flood, lightning, seismic activity; and events of Force Majeure such as fire, explosion, war, civil disturbance, et al.

THIS MNI WARRANTY IS GIVEN IN LIEU OF ALL OTHER WARRANTIES, EITHER EXPRESSED OR IMPLIED, WHICH ARE SPECIFICALLY EXCLUDED, INCLUDING WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

An authorization to return products under this warranty must be obtained from a MNI Customer Service Representative prior to making shipment to MNI's service location, and all returns shall be shipped freight pre-paid. MNI shall be responsible for return freight charges only on repaired and replaced products found to be defective.

In the event that MNI provides services only, MNI warrants the performance and specifications of such services but does not warrant that services performed will fulfill the total system requirement of the Buyer.

Contacting Us

Company Headquarters:Microwave Networks Incorporated4000 GreenbriarStafford, TX 77477USATel 281.263.6500Fax 281.263.6400Toll free in US 1.888.225.6429

Internet: www.microwavenetworks.com

24-Hour Customer ServiceTel 281.263.6501Toll free in US 1.888.225.4762E-mail: [email protected]

InternationalLondonTel 44.1628.788383Fax 44.1628.788424

http://www.microwavenetworks.com


mailto:[email protected]

Page vii Proteus LC System User’s Manual

Revision HistoryRev. E — Release, 10/2005

Rev. F — 11/2005Chapter 1 - Radio Description 1-4Appendix C–Radio Management Interfaces C-2

Rev. G — 2/06Chapter 1 - Radio Description 1-4, 1-21Chapter 3 - Commissioning 3-7Chapter 4 - Operation allChapter 5 - Maintenance 5-4, 5-5, 5-11 to 5-16

Rev. H — 6/06 [7/141]

1. Added correct 15G ITU standard.

Front Matter Cover, TOC, LOF, LOT, Revision HistoryChapter 1 - Radio Description 1-4, 1-15 to 1-17, 1-19, 1-20[7/14], 1-22Chapter 2 - Installation 2-4, 2-13, 2-14, 2-16, 2-19, 2-20Chapter 3 - Commissioning 3-4, 3-9, 3-10Chapter 4 - Operation 4-10, 4-11Chapter 5 - Maintenance 5-14Appendix A–Frequency Tables allAppendix F–Hot-Standby Protected Radio F-2, F-6, F-7, F-8, F-15 to F-18

Rev. J — 10/06Front Matter Cover, Revision HistoryAppendix A–Frequency Tables A-6, A-11

Page viii Proteus LC System User’s Manual

Proteus LC System User’s Manual Page ix

Using This Manual

Introduction

This section is a guide to the Proteus AMT L-Series radio information in this manual.

Manual Organization

This manual is organized into the following sections.

Using This Manual Provides a quick look of how this manual presents our product information.

Table of Contents Lists all chapters, sections, headings, and subheadings in the manual, as well as where to find them.

Chapter 1–Radio DescriptionGeneral radio description and system specifications.

Chapter 2–InstallationInstructions on how to unpack, configure, and install the radio.

Chapter 3–CommissioningInstructions on how to align, configure, power, and test a radio and microwave hop.

Using This Manual

Proteus LC System User’s Manual Page x

Chapter 4–OperationDescribes signal flow through the radio, switching and loopback. Includes instructions on using radio features.

Chapter 5–Maintenance Routine maintenance, diagnostics, repairs, and field upgrade procedures.

Appendix A–Frequency TablesLists ODU frequencies, sub-bands, their parts, and part numbers.

Appendix B–Alarm Definitions Defines radio alarms displayed by radio management interfaces.

Appendix C–Radio Management InterfacesDiscusses craft terminal (VT100) and Windows-based radio interfaces.

Appendix D–WAN / IPO-Air Channel RoutingExplains the WAN, or IPO-Air, channel routing and routing procedures.

Appendix E–Optional ODU and RFU MountingDiscusses offset pole installation and indoor mounting options of the RFU.

Appendix F–Hot-Standby Protected RadioDescribes hot-standby radio equipment, operation, and installation.

Appendix G–Ethernet PerformanceIncludes a complete latency table for Ethernet data.

Microwave Networks

Proteus AMT L-Series Manual Page xi

Table of Contents

Chapter 1 — Radio DescriptionOverview ....................................................................................................................... 1-1

System Components........................................................................................... 1-2Fault Protection .................................................................................................. 1-2

Indoor Unit .................................................................................................................... 1-3Chassis................................................................................................................ 1-3IDU Circuit Boards ............................................................................................ 1-4Front Panel ......................................................................................................... 1-5Line Interface ..................................................................................................... 1-6 Radio Capacity Configuration........................................................................... 1-7

Outdoor Unit................................................................................................................ 1-10Radio Frequency Unit ...................................................................................... 1-10Antenna ............................................................................................................ 1-12

IDU-to-ODU Interface Cable ...................................................................................... 1-14Radio Management...................................................................................................... 1-15

Element Manager ............................................................................................. 1-16EM Connections ..................................................................................... 1-16

SNMP............................................................................................................... 1-17SNMP Connection .................................................................................. 1-17

Text-Based Menu Interface.............................................................................. 1-18Text-Based Interface Connection ........................................................... 1-18

Telnet................................................................................................................ 1-18Telnet Connection................................................................................... 1-19In-Band NMS Mode ............................................................................... 1-19

System Specifications.................................................................................................. 1-20General Radio Specifications ........................................................................... 1-20System Performance: Power and Threshold .................................................... 1-22Ethernet Performance: Throughput and Latency ............................................. 1-23

Chapter 2 — InstallationInstallation Information ................................................................................................. 2-1

Location.............................................................................................................. 2-1Environment ....................................................................................................... 2-1Grounding........................................................................................................... 2-2Cable and Connector Considerations ................................................................. 2-2

Tools and Material......................................................................................................... 2-3Preparing the Site .......................................................................................................... 2-3

Mounting the Rack ............................................................................................. 2-3Unpacking Equipment........................................................................................ 2-4

Installing the Coaxial Cable .......................................................................................... 2-5Assembling the Cable......................................................................................... 2-5

Table of Contents

Page xii Proteus AMT L-Series Manual

Installing the Cable ............................................................................................ 2-7Installing the Indoor Unit .............................................................................................. 2-8

Mounting the IDU .............................................................................................. 2-8Connecting Power .............................................................................................. 2-8Adding Power Protection ................................................................................. 2-10Connecting E1/T1 Lines .................................................................................. 2-11Connecting Ethernet......................................................................................... 2-13Connecting Network Management .................................................................. 2-13

In-Band NMS Mode ............................................................................... 2-15Installing the ODU ...................................................................................................... 2-15

Fundamentals ................................................................................................... 2-15Torque Specifications ............................................................................. 2-16

Unpacking Hardware........................................................................................ 2-16Attaching the Mounting Assembly .................................................................. 2-17Attaching the Antenna to the Mounting Assembly.......................................... 2-18Attaching the RF Unit to the Antenna.............................................................. 2-19Connecting the Coaxial Cable to the ODU ...................................................... 2-20

Chapter 3 — CommissioningPowering the Radio ....................................................................................................... 3-1Verifying Radio Configuration ..................................................................................... 3-2Aligning the ODU ......................................................................................................... 3-4

Course ODU Alignment..................................................................................... 3-4Fine ODU Alignment ......................................................................................... 3-5

Alignment Procedure ................................................................................ 3-5Making Configuration Changes .................................................................................... 3-7

Configuring the ODU......................................................................................... 3-7Setting Transmit and Receive Frequency................................................. 3-7Setting Transmit Power Output ................................................................ 3-7

Configuring the IDU .......................................................................................... 3-8Setting Capacity........................................................................................ 3-8Setting Tributaries .................................................................................... 3-8Setting NMS Mode................................................................................... 3-9

Verifying Radio Operation .......................................................................................... 3-10

Chapter 4 — OperationIntroduction ................................................................................................................... 4-1Basic Operation ............................................................................................................. 4-1Indoor Unit (IDU).......................................................................................................... 4-2

Line Interface ..................................................................................................... 4-3Signal Multiplexing............................................................................................ 4-3Modulation and Coding...................................................................................... 4-5IF Conversion and Multiplexing ........................................................................ 4-5

Microwave Networks

Proteus AMT L-Series Manual Page xiii

Outdoor Unit (ODU) ..................................................................................................... 4-7User Interfaces............................................................................................................... 4-9

NMS/SNMP (Ethernet) ...................................................................................... 4-9COMPUTER/CTI (Serial)................................................................................ 4-10Management Software...................................................................................... 4-10

Chapter 5 — MaintenanceIntroduction ................................................................................................................... 5-1Customer Service Options............................................................................................. 5-1

Support Contacts ................................................................................................ 5-1Repair and Exchange Services ........................................................................... 5-1Technical Support Services................................................................................ 5-2

Maintenance .................................................................................................................. 5-3Changing Payload Configuration ....................................................................... 5-3Upgrading Payload Capacity and Data Type ..................................................... 5-5Replacing IDU Fuses and the Backup Battery................................................... 5-6

Replace the Power Supply Fuse ............................................................... 5-6Replace the Backup Battery...................................................................... 5-7

Replacing IDU Depot-Level Components ......................................................... 5-8Replace the Power Supply Board ............................................................. 5-8Replace the IF Board ................................................................................ 5-9

Replacing ODU RF Units ................................................................................ 5-10Updating Firmware with TFTP........................................................................ 5-11

Using EM to Update Firmware............................................................... 5-11Using CTI to Update Firmware .............................................................. 5-12

Loading Firmware with Bootloader ................................................................. 5-13Maintenance Checks.................................................................................................... 5-15

Periodic Maintenance....................................................................................... 5-15Monthly Checks...................................................................................... 5-15Semi-Annual Checks .............................................................................. 5-15Annual Checks........................................................................................ 5-15

Appendix A — Frequency TablesOverview ...................................................................................................................... A-1Frequency and Channel Plans ...................................................................................... A-1

7GHz................................................................................................................. A-38GHz................................................................................................................. A-511 GHz .............................................................................................................. A-613GHz............................................................................................................... A-715GHz............................................................................................................... A-718GHz............................................................................................................... A-923GHz............................................................................................................. A-1026 GHz ........................................................................................................... A-11

Table of Contents

Page xiv Proteus AMT L-Series Manual

38 GHz ............................................................................................................. A-11

Appendix B — Alarm Definitions

Appendix C — Radio Management InterfacesOverview ....................................................................................................................... C-1Connections ................................................................................................................... C-2

Computer............................................................................................................ C-2NMS-SNMP....................................................................................................... C-2

SNMP Basics ............................................................................................ C-3Installing the SNMP MIB......................................................................... C-4MIB Tables ............................................................................................... C-4

Element Manager........................................................................................................... C-5Key Features....................................................................................................... C-6System Requirements......................................................................................... C-6Basics ................................................................................................................. C-6

Polling and Port Indicators ....................................................................... C-7Alarms ...................................................................................................... C-7Event and Alarm Logging ........................................................................ C-7Identifying Radios .................................................................................... C-7Security ..................................................................................................... C-7EM Menus ................................................................................................ C-8

Craft Terminal and Command Line Interface ............................................................. C-10Menus ............................................................................................................... C-12

Main Menu ............................................................................................. C-12Alarm Menu............................................................................................ C-12Performance Menu ................................................................................. C-13Test Menu ............................................................................................... C-13Configuration Menu ............................................................................... C-13Utility Menu ........................................................................................... C-13

Security and Radio Identity.............................................................................. C-14Alarms .............................................................................................................. C-15Performance ..................................................................................................... C-17Test ................................................................................................................... C-19Configuration ................................................................................................... C-22Utilities ............................................................................................................. C-26

Appendix D — WAN/IPO-Air Channel RoutingOverview ....................................................................................................................... D-1

LAN Port ............................................................................................................ D-1WAN Port........................................................................................................... D-1

WAN Port Communication ...................................................................... D-1IP Data Routing ............................................................................................................. D-3

Microwave Networks

Proteus AMT L-Series Manual Page xv

The Routing Table............................................................................................. D-3Static Routes...................................................................................................... D-4

Example: Using Static Route to Connect a PC to a Radio ...................... D-5Advantages of Static Routing .................................................................. D-6Disadvantages of Static Routing.............................................................. D-6

Routing Information Protocol (RIP) ................................................................. D-6Advantages of RIP................................................................................... D-7Disadvantages of RIP .............................................................................. D-7Bypassing Network Size Limit of RIP .................................................... D-7

Appendix E — Optional ODU and RFU MountingOverview ....................................................................................................................... E-1

Offset ODU Mounting ....................................................................................... E-1RFU Rack Mounting Kit .................................................................................... E-3

Installing the Mounting Kits.......................................................................................... E-5Installing the Offset Mounting Kit ..................................................................... E-5Installing the Rack Mounting Kit....................................................................... E-5

Selecting Waveguide ..................................................................................................... E-6

Appendix F — Hot-Standby Protected RadioOverview ....................................................................................................................... F-1

Reverse Channel Switch..................................................................................... F-3Redundancy Switch Unit ............................................................................................... F-5

RSU Front Panel Features .................................................................................. F-6RSU Interconnect Cables ................................................................................... F-7

Installing the Redundancy Switch Unit ......................................................................... F-8Mounting the RSU ............................................................................................. F-8Interconnecting the IDU and RSU ..................................................................... F-8Connecting E1/T1 Line Signals to the RSU....................................................... F-9

Installing the HSB ODU.............................................................................................. F-11Torque Specifications ............................................................................. F-11

Unpacking Hardware........................................................................................ F-11Attaching the Standard Mounting Assembly ................................................... F-12Attaching the Antenna to the Mounting Assembly.......................................... F-14Attaching the RF Unit to the Antenna.............................................................. F-15

Non-Protected Units ............................................................................... F-15Hot-Standby Protected Units .................................................................. F-15

Connecting the Coaxial Cable to the ODU ...................................................... F-17

Appendix G — Ethernet PerformanceOverview ...................................................................................................................... G-1

Table of Contents

Page xvi Proteus AMT L-Series Manual

Microwave Networks

Proteus AMT L-Series Manual Page xvii

List of Tables

Chapter 1 — Radio DescriptionTable 1-A Early-Model IDU Part Numbers.......................................................................... 1-3Table 1-B Current-Model IDU Part Numbers...................................................................... 1-3Table 1-C IDU Boards ........................................................................................................ 1-4Table 1-D IDU Front-Panel Features.................................................................................. 1-5Table 1-E Radio Configurations ......................................................................................... 1-7Table 1-F ETSI Radio Capacity and Payload Configurations............................................. 1-8Table 1-G ANSI Radio Capacity and Payload Configurations............................................ 1-9Table 1-H RF Unit Part Numbers...................................................................................... 1-11Table 1-I RF Unit Connections ......................................................................................... 1-11Table 1-J IDU-to-ODU Cable Components ...................................................................... 1-14Table 1-K General Specifications ..................................................................................... 1-20Table 1-L Environmental Specification ............................................................................. 1-21Table 1-M Mechanical Specification ................................................................................. 1-21Table 1-N Power Specification ......................................................................................... 1-21Table 1-O RF Transmit Power.......................................................................................... 1-22Table 1-P System Specifications – ETSI Bandwidths....................................................... 1-22Table 1-Q System Specifications – ANSI Bandwidths...................................................... 1-22Table 1-R Hot-Standby Branching Loss ........................................................................... 1-22Table 1-S Ethernet Data Throughput & Latency, ETSI Bandwidths ................................. 1-23

Chapter 2 — InstallationTable 2-A Installation Kit..................................................................................................... 2-2Table 2-B IDU-to-ODU Cable Components........................................................................ 2-6Table 2-C IDU-to-ODU Cable Assembly ............................................................................ 2-6Table 2-D E1/T1 Line Wiring on DB78 ............................................................................. 2-11Table 2-E Prefabricated DB78P Cable Wire List .............................................................. 2-12Table 2-F 100-BaseT Wiring (RJ45)................................................................................. 2-13Table 2-G Computer Port (Serial; Sub-D 9-Pin Female) .................................................. 2-14Table 2-H NMS Connection (IP Interface) ........................................................................ 2-14Table 2-I Fastener Torque Specifications ........................................................................ 2-16

Chapter 3 — Commissioning

Chapter 4 — Operation

Chapter 5 — MaintenanceTable 5-A Proteus AMT-L Firmware Files......................................................................... 5-14

Table of Contents

Page xviii Proteus AMT L-Series Manual

Chapter A — Frequency TablesTable A-A RF Frequencies and Channel Plans ................................................................. A-2Table A-B 7GHz, 154 MHz T/R Spacing ............................................................................ A-3Table A-C 7GHz, 160 MHz T/R Spacing............................................................................ A-3Table A-D 7GHz 161 MHz T/R Spacing............................................................................. A-4Table A-E 7GHz 196 MHz T/R Spacing ............................................................................. A-5Table A-F 8GHz 119 MHz T/R Spacing ............................................................................. A-5Table A-G 8GHz 208 MHz T/R Spacing............................................................................. A-5Table A-H 8GHz 266 MHz T/R Spacing............................................................................. A-6Table A-I 8GHz 311.32 MHz T/R Spacing.......................................................................... A-6Table A-J 11GHz 490 MHz T/R Spacing............................................................................ A-6Table A-K 11GHz 530 MHz T/R Spacing ........................................................................... A-6Table A-L 13GHz 266 MHz T/R Spacing ........................................................................... A-7Table A-M 15GHz 315 MHz T/R Spacing .......................................................................... A-7Table A-N 15GHz 420 MHz T/R Spacing........................................................................... A-8Table A-O 15GHz 490 MHz T/R Spacing........................................................................... A-8Table A-P 15GHz 475 MHz T/R Spacing ........................................................................... A-8Table A-Q 15GHz 640 MHz T/R Spacing........................................................................... A-8Table A-R 15GHz 644 MHz T/R Spacing........................................................................... A-9Table A-S 15GHz 728 MHz T/R Spacing ........................................................................... A-9Table A-T 18GHz 1010 MHz T/R Spacing ......................................................................... A-9Table A-U 18GHz 1560 MHz T/R Spacing......................................................................... A-9Table A-V 23GHz 1008 MHz T/R Spacing ....................................................................... A-10Table A-W 23GHz 1200 MHz T/R Spacing ...................................................................... A-10Table A-X 23GHz 1232 MHz T/R Spacing ....................................................................... A-10Table A-Y 26 GHz 800 MHz T/R Spacing ........................................................................ A-11Table A-Z 26 GHz 1008 MHz T/R Spacing ...................................................................... A-11Table A-AA 38GHz 700 MHz T/R Spacing....................................................................... A-11Table A-AB 38GHz 1260 MHz T/R Spacing..................................................................... A-11


Appendix C — Radio Management InterfacesTable C-A EM Menus and Descriptions ............................................................................. C-8Table C-B CLI Commands ............................................................................................... C-11

Appendix D — WAN/IPO-Air Channel Routing

Appendix E — Optional ODU and RFU MountingTable E-A ODU - RFU Offset Mounting Kit ........................................................................ E-1Table E-B Offset Mounting Kit Components, P/N 8708271-xx........................................... E-2Table E-C Waveguide Adapters on Offset Mounting Plate ................................................ E-2

Microwave Networks

Proteus AMT L-Series Manual Page xix

Table E-D RFU Rack Mounting Kit ..................................................................................... E-3Table E-E ODU Rack Mounting Kit Components ............................................................... E-3Table E-F Waveguide Adapters on Rack Mounting Plate .................................................. E-4Table E-G Adapter to Waveguide Interface Dimensions .................................................... E-6Table E-H Flexible Waveguide for Offset Mounting Option ............................................... E-6

Appendix F — Hot-Standby Protected RadioTable F-A Hot-Standby Branching Loss ............................................................................. F-1Table F-B Typical Hot-Standby Switching Time.................................................................. F-2Table F-C Common RSU Front-Panel Features................................................................. F-6Table F-D Hot-Standby Radio Interconnect Cables............................................................ F-7Table F-E 100-BaseT Wiring (RJ45) .................................................................................. F-8Table F-F E1/T1 Line Wiring on DB78................................................................................ F-9Table F-G Prefabricated DB78P Cable Wire List ............................................................. F-10Table F-H Fastener Torque Specifications ...................................................................... F-11

Appendix G — Ethernet PerformanceTable G-A Throughput and Latency for Ethernet Data in ETSI Bandwidths...................... G-1

Table of Contents

Page xx Proteus AMT L-Series Manual

Microwave Networks

Proteus AMT L-Series Manual Page xxi

List of Figures

Chapter 1 — Radio DescriptionFigure 1-1. Proteus AMT L-Series Radio ........................................................................... 1-1Figure 1-2. IDU Chassis ..................................................................................................... 1-3Figure 1-3. IDU Front Panel (see Table 1-D for call-out description) ................................. 1-5Figure 1-4. Proteus AMT L-Series ODU........................................................................... 1-10Figure 1-5. RF Unit Features ........................................................................................... 1-11Figure 1-6. Low Profile Antennas..................................................................................... 1-12Figure 1-7. 1.2- and 1.8m Antennas ................................................................................ 1-12Figure 1-8. Signals Multiplexed onto the IDU-to-ODU Cable .......................................... 1-14Figure 1-9. Interfaces to Radio Management Applications .............................................. 1-16

Chapter 2 — InstallationFigure 2-1. IDU Power Connection for -48V Input.............................................................. 2-9Figure 2-2. IDU Power Connection for +24V Input............................................................. 2-9Figure 2-3. Connecting Power Protection Devices........................................................... 2-10Figure 2-4. Prefabricated DB78P Cable........................................................................... 2-12Figure 2-5. Single ODU Mounting Dimensions ................................................................ 2-17

Chapter 3 — CommissioningFigure 3-1. Typical Antenna Side Lobes ........................................................................... 3-6

Chapter 4 — OperationFigure 4-1. Simplified Radio Link Diagram......................................................................... 4-1Figure 4-2. IDU Functional Block Diagram......................................................................... 4-2Figure 4-3. Line Interface Functions .................................................................................. 4-3Figure 4-4. Multiplexing Data Lines and Overhead Channels............................................ 4-4Figure 4-5. Outdoor Unit Block Diagram ............................................................................ 4-7Figure 4-6. ODU Duplex Operation .................................................................................... 4-8Figure 4-7. User Interface Functions.................................................................................. 4-9Figure 4-8. Craft Terminal Interface Radio Management Software Outline...................... 4-11Figure 4-9. Element Manager Radio Management Software Outline............................... 4-12

Chapter 5 — MaintenanceFigure 5-1. IDU Power Supply .......................................................................................... 5-8Figure 5-2. IF Board in the IDU .......................................................................................... 5-9Figure 5-3. IF Board .......................................................................................................... 5-9

Table of Contents

Page xxii Proteus AMT L-Series Manual

Appendix A — Frequency Tables


Appendix C — Radio Management InterfacesFigure C-1. Radio Management Ports ............................................................................... C-1Figure C-2. SNMP MIB Tables........................................................................................... C-4Figure C-3. Element Manager Main Screen ...................................................................... C-5Figure C-4. EM Menu and Status Bar ................................................................................ C-7Figure C-5. Radio Loopbacks .......................................................................................... C-20

Appendix D — WAN/IPO-Air Channel RoutingFigure D-1. Example Network............................................................................................ D-5Figure D-2. Example of a Large RIP-Enabled Radio Network........................................... D-8

Appendix E — Optional ODU and RFU MountingFigure E-1. ODU Offset Mount Kit, P/N 8708271-xx.......................................................... E-2Figure E-2. RFU Rack Mount Kit, P/N 8708272-xx............................................................ E-4

Appendix F — Hot-Standby Protected RadioFigure F-1. Hot-Standby Configuration .............................................................................. F-2Figure F-2. Hot-Standby ODU Mounting with Coupler ....................................................... F-3Figure F-3. Reverse Channel Switch Operation ................................................................ F-4Figure F-4. Hot-Standby Indoor Equipment ....................................................................... F-5Figure F-5. RSU Front Panel ............................................................................................. F-6Figure F-5. RSU Front Panel ............................................................................................. F-6Figure F-6. IDU to RSU Connections................................................................................. F-7Figure F-7. IDU to RSU Connections................................................................................. F-8Figure F-8. Prefabricated DB78P Cable .......................................................................... F-10Figure F-9. Protected ODU Mounting Dimensions .......................................................... F-12

Appendix G — Ethernet Performance

Proteus AMT L-Series Manual Page 1-1

Chapter 1Radio Description

Overview Proteus AMT L-Series is a point-to-point microwave radio that accommo-dates low-to-medium backhaul applications in cellular, enterprise, utility, public safety, and private LANs and WANs. The single, low-profile plat-form offers configuration options for up to 16E1 or 16DS1, Ethernet traffic, or a combination of both up to 50 Mbps. Full-duplex radio frequency com-munication operates from 7 to 38 GHz in bandwidths from 3.5- to 28-MHz.

Proteus AMT L-Series configuration and operation is software con-trolled. Configuration licenses set traffic type, bandwidth, modulation, and throughput (Table 1-E). Management software lets you set frequency, TX power, and tributaries, and configure bandwidth, modulation, radio capac-ity, and traffic type for your configuration.

The universal IDU and ODU handle all modulation options, capacity, and data types. Configuration license keys set radio capacity and traffic type (Table 1-E). Data rate and modulation settings establish the operating band-width. Radio management software maintains the radio license key.

Figure 1-1. Proteus AMT L-Series Radio

OUTDOOR UNIT (ODU)

INDOOR UNIT (IDU)

Radio Description

Page 1-2 Proteus AMT L-Series Manual

System ComponentsIn-door units fit in one rack space (1RU). RF units mount directly to the antenna using press-fit adapters.

The Proteus AMT L-Series radio is a compact split-mount configuration. An indoor unit that mounts in a single rack space (1RU) provides signal pro-cessing at QPSK or 8PSK modulation to convert digital line signals to, and from, intermediate frequency (IF) signals.

An RG-8 coaxial cable connects IF signals, power, and telemetry between the indoor unit (IDU) and an outdoor unit (ODU). The ODU includes a radio frequency (RF) unit, integrated antenna, and mounting hardware. The ODU, which mounts on a grounded tower, pole, or wall mast, converts IF to, and from, RF signals.

IDUs match modulation to data-rate and bandwidth.

ODUs operate in the 7/8, 10, 11, 13, 15, 18, 23, 26, 38-GHz frequency bands using ETSI (International) and ANSI (North American) RF channel plans (Appendix A).

Signal processing at QPSK modulation provides optimum system gain; 8PSK doubles the throughput in a given RF bandwidth. Bandwidths sup-ported include 3.5, 7, 14 and 28 MHz for ETSI-based radios and 5, 10, 20 and 30/40 MHz for ANSI-based radios. Radio data rate and modulation es-tablish the actual bandwidth required

Changing bandwidth on early-model units sometimes requires changing the IF board in the IDU (Chapter 5, "Maintenance"). You never have to change or modify outdoor units to change data rate or occupied bandwidth.

Current-model radios include IDUs that handle all modes of bandwidth, modulation, and capacity. Your radio is licensed to the mode you purchase.

Current model radios use a universal IDU that handles all modes of opera-tion – modulation options, scalable capacity, and voice and data interfaces. Software license keys set radio capacity and traffic type (Table 1-E). Radio management software maintains your radio configuration license (see “Radio Management” on page 1-15).

Automatic transmit power control (ATPC) lets the radio maintain a constant receive signal level (RSL) at the receive site by amplifying or attenuating the transmitter. ATPC is automatic or you set RSL threshold and maximum TX power. Minimum power is -4 dBm. APC keeps RSL within +3 dB of the set point by stepping far-end transmit power ±1 dB.

Fault Protection

The L-Series radio is ideal for low-cost non-protected (NP) radio links – one IDU and one ODU per terminal. But for critical communications links use the Proteus AMT L-Series hot-standby radio.

A redundancy switch operates in conjunction with two radios and one an-tenna at both ends of a link to provide monitored hot-standby (HSB) protec-tion to the on-line radio (see Appendix F "Hot-Standby Protection").

Indoor Unit


Indoor UnitEarly-model indoor units (Table 1-A) match modulation to data-rate and bandwidth with an IF board change (Table 1-C). Current-model IDUs (Table 1-B) match bandwidth, modulation, and capacity with software li-cense keys (Table 1-F, Table 1-G) that you purchase.

ChassisThe IDU mounts in standard 19-inch equipment racks in a one rack unit (1RU; 1.75 inch) space. Signal and power connects to the front panel, which allows installations in tight locations.

The aluminum chassis houses the main board, power supply, IF board, and front-panel board (Figure 1-2). The chassis also dissipates heat from critical components.

Ground IDUs to the facility ground system to protect radios from lightning, EMI, and RFI.

Ground the IDU chassis to the facility ground for safety, to enable operation, and to minimize damage from lightning strike and the impact of electromag-netic- and radio frequency-interference (EMI/RFI). Ground systems that fol-low published guidelines, such as ITU-T Rec. K.27, provide the ground ref-

Table 1-A Early-Model IDU Part Numbers

Bandwidth48V Model 24V Model

Part Number Description Part Number Description3.5 / 7 MHz ETSI 8209307-40 IDU, 48V, 3.5/7MHz, 2/4/8E1 8209307-20 IDU, 24V, 3.5/7 MHz, 2/4/8E114 / 28 MHz ETSI 8209307-41 IDU, 48V, 14/28MHz, 8/16E1 8209307-21 IDU, 24V, 14/28 MHz, 8/16E1

2.5 / 5 MHz FCC 8209307-42 IDU, 48V, 2.5/5MHz, 2/4/8DS1 8209307-22 IDU, 24V, 2.5/5 MHz, 2/4/8DS1

10, 20, 30, 40 MHz FCC 8209307-43 IDU, 48V, 10/28MHz, 8/16DS1 8209307-23 IDU, 24V, 10/28MHz, 8/16DS1

Table 1-B Current-Model IDU Part Numbers

Bandwidth48V Model 24V Model

Part Number Description Part Number DescriptionUniversal ETSI 8209324-40 IDU, 48V, 16E1 8209324-20 IDU, 24V, 16E1Universal FCC 8209324-41 IDU, 48V, 16DS1 8209324-21 IDU, 24V, 16DS1

Figure 1-2. IDU Chassis

Radio Description


erence necessary for reliable radio operation. The IDU front panel includes ground connection points to connect a suitable ground bus.

IDU Circuit Boards

The IDU chassis houses four circuit boards: the main board, IF board, power supply, and front panel board. Table 1-C lists board part numbers and board variations.

Each IDU ships with either –48V or +24V power; an optional AC converter (P/N 7310050-00) is available for sites with AC power requirements. IF bandpass filters reside on the IF board. Bandpass filters set the bandwidth of the transmitted signal and provide adjacent channel rejection in the receive path.

Main and IF boards on current-model IDUs can handle all modes. A software license key enables each mode.

The main and IF board of the IDU handles all operating modes and band-widths. Software sets data capacity and bandwidth – you receive a software license for the configuration you purchase (see “Radio Capacity Configura-tion” on page 1-7).

Table 1-C IDU BoardsComponent Part Numbers

IDUMain Board, 16E1/DS1 8000621-21Universal IF Board 8000614-23/43Power Supply -48V 8000569-01

+24V 8000579-01Optional 100/250Vac to 48Vdc converter kit 8708263-00

Indoor Unit


Front Panel

Signal and power connectors and service indicators mount on the IDU front panel (Table 1-D). A green indicator lights when the unit is powered. Condi-tion indicators light on major (red) and minor (yellow) alarm.

Figure 1-3. IDU Front Panel (see Table 1-D for call-out description)

Table 1-D IDU Front-Panel FeaturesFeature Description1. DC Power 3-pin Phoenix connector to -48 Vdc or optional

+24 Vdc power. Mates with plug P/N 3024080-03. See Power Specification for require-ments.

2. ODU 50-Ω N-type connector for signal and power between IDU and ODU. Cable length between units is limited to 22 dB of loss at 350-MHz (260m with TM-LMR-400, or 300m with LMR-500).

3. LEDs Power (green), Minor alarm (yellow), and Major alarm (red) indications

4. COMPUTER 9-pin sub-D connector. RS-232 serial connection for radio management interface. Supports both craft terminal interface and Element Manager.

5. NMS1/2 RJ45 ports for SNMP or terminal application using internet protocol (IP). Ports provide bridged IP interface to a 64-kbps channel.

6. 10/100A/B 10- or 100BaseT Ethernet interface. 100-Ω bal-anced; IEEE 802.3, 802.3u. Ports are bridged, include cable autosensing and rate auto-negotia-tion. This interface is enabled on units with an Ethernet license (see ”Radio Capacity Configura-tion”). Port auto-configuration allows cabling Ethernet between radios (see Chapter 2 ”Con-necting Ethernet”).

7. HSBY 26-pin sub-D connector for redundancy protected systems (see Appendix F)

8. 4-16 CHANNEL I/O 78-pin sub-D connector. The line interface for up to 16 PDH channels. DS1 lines are 100-Ω bal-anced, and E1 lines are 120-ohm balanced; both meet ITU-G.703. The interface is enabled for units with PDH licenses (see ”Radio Capacity Configuration”).

Ground ( ) Bare metal area on chassis for ground connec-tions. Hardware for ground straps is provided.

Radio Description


Line Interface

The line interface of Proteus AMT L-Series radios (Figure 1-3) supports ple-siochronous digital hierarchy (PDH) communication at ETSI data rates from 2 to 16E1 and at ANSI rates from 4 to 16DS1. Radio capacity depends on the capacity and data type license you purchase (see “Radio Capacity Con-figuration” on page 1-7)

E1 lines on the DB78 connector are a 120-Ω balanced; DS1 lines are 120-Ω balanced. The line interface follows ITU-T Rec. G.703. Radio configuration software lets you set DS1 line code to AMI or B8ZS; E1 line code is HDB3.

Ethernet (10/100) ports for 100BaseT use RJ45, shielded, 100-Ω balanced connectors with data indicators. Indicators show enabled ports and activity. The ethernet data ports support IEEE 802.3 and IEEE 802.3u autosensing and auto-negotiating. Autosensing allows the ethernet port to inter-operate with both 100- and 10baseT devices. Auto-negotiate provides compatibility and inter-operability between ethernet devices that support multiple possible speed, duplex, and wiring combinations.

Auto-negotiate is the ethernet port default setting. You can disable (Power Down) each ethernet port, or configure the port data rate. Set the Ethernet port using the radio management application (see ”Radio Management”) to one of:

• Powered Down• Auto-Negotiate (default)• 10BaseT Half-dplx• 10BaseT Full-dplx• 100BaseT Half-dplx• 100BaseT Full-dplx

Ethernet connects between two radios back-to-back and auto-negotiate and auto-sense configure the ports. If an ethernet port in auto-negotiate connects to a device that does not support auto-negotiation (parallel detect), as speci-fied in IEEE 802.3u clause 28, it configures to half-duplex even when the connected device is a full-duplex device.

The later case can cause excessive collisions and communications errors. Avoid any auto-negotiation problems on mission-critical links by hard-code both devices to the best possible speed and duplex setting.

Indoor Unit


Radio Capacity Configuration

Table 1-E lists radio capacity configurations. Always check the list of valid configurations using the valid command of the radio user interface, which may include newer configurations.

Table 1-F (ETSI) and Table 1-G (ANSI) list available capacity licenses with throughput, modulation, and traffic options. Configurations with QPSK modulation have 2 b/Hz bit efficiency for high gain (HG), and radios 8PSK modulation have 3 b/Hz bit efficiency for high throughput (HP).

Table 1-E Radio Configurations Bandwidth Capacity Modulation Bandwidth Capacity Modulation

ETSI ANSI

3.5 MHz

2E1 QPSK

5 MHz

4DS1QPSK100BT 2DS1 100BT

4E18PSK

100BT2E1 100BT 8DS1

8PSK100BT 4DS1 100BT

7 MHz

4E1QPSK

2DS1 100BT2E1 100BT 100BT

100BT

10 MHz

8DS1

QPSK8E1

8PSK

4DS1 100BT4E1 100BT 2DS1 100BT2E1 100BT 100BT

100BT 16DS1

8PSK

14 MHz

8E1

QPSK

12DS1 100BT4E1 100BT 8DS1 100BT2E1 100BT 4DS1 100BT

100BT 2DS1 100BT16E1 100BT

8PSK

100BT12E1 100BT

20 MHz

16DS1 100BT

QPSK

8E1 100BT 12DS1 100BT4E1 100BT 8DS1 100BT2E1 100BT 4DS1 100BT

28 MHz

16E1

QPSK

2DS1 100BT12E1 100BT 100BT8E1 100BT 16DS1 100BT

8PSK

4E1 100BT 12DS1 100BT2E1 100BT 8DS1 100BT

100BT 4DS1 100BT16E1 100BT

8PSK

2DS1 100BT12E1 100BT 100BT8E1 100BT

28 MHz

16DS1 100BT

QPSK

4E1 100BT 12DS1 100BT2E1 100BT 8DS1 100BT

100BT 4DS1 100BT2DS1 100BT

100BT16DS1 100BT

8PSK

12DS1 100BT8DS1 100BT4DS1 100BT2DS1 100BT

100BT

Radio Description


Configuration designations in Table 1-F and Table 1-G denote licensed ra-dio capacity, modulation and the active traffic (line) type. The first three digits identify approximate throughput and the dash letter identify modula-tion and active traffic type.

• -A indicates QPSK PDH only• -B indicates QPSK Ethernet only• -C indicates QPSK PDH plus Ethernet• -D indicates 8PSK PDH only• -E indicates 8PSK Ethernet only• -F indicates 8PSK with PDH plus Ethernet

Table 1-F ETSI Radio Capacity and Payload ConfigurationsLicensed Throughput Bandwidth System Configuration

DesignationCapacity Modulation*

* QPSK offers high gain while 8PSK offers high throughput. 8PSK units have QPSK capability.

Traffic Type†

† "+xx Mbit/s" show the Ethernet payload throughput.

Gain‡

‡ Typical with 7/8, 15, and 18G RFU; 13G: -1dB, 23G: -2dB, 38G: -5dB.

4 Mbit/s QPSK2E1

4.096 Mbit/s 3.5 MHz 115.0 dB004-A (PDH)

4.1Mbit/s 004-B (ETH)

8 Mbit/s 8PSK4E1

8.192 Mbit/s 3.5 MHz 103.0 dB008-D (PDH)

8.2Mbit/s 008-E (ETH)2E1+4.1Mbit/s 008-F (BOTH)

8 Mbit/s QPSK4E1

8.192 Mbit/s 7 MHz 112.5 dB008-A

8.2Mbit/s 008-B2E1+4.1Mbit/s 008-C (BOTH)

16 Mbit/s 8PSK

8E1

16.384 Mbit/s 7 MHz 101.5 dB

016-D16.5Mbit/s 016-E4E1+ 8.2Mbit/s

016-F2E1+12.4Mbit/s

16 Mbit/s QPSK

8E1

16.384 Mbit/s 14 MHz 109.5 dB

016-A16.5Mbit/s 016-B4E1+8.3Mbit/s

016-C2E1+12.4Mbit/s

32 Mbit/s 8PSK

16E1

32.768 Mbit/s 14 MHz 98.5 dB

032-D33.1Mbit/s 032-E12E1+8.2Mbit/s

032-F8E1+16.5Mbit/s4E1+24.8Mbit/s2E1+28.9Mbit/s

32 Mbit/s QPSK

16E1

32.768 Mbit/s 28 MHz 106.5 dB

032-A33.1Mbit/s 032-B12E1+8.2Mbit/s

032-C8E1+16.5Mbit/s4E1+24.8Mbit/s2E1+28.9Mbit/s

50 Mbit/s 8PSK

16E1

51.768 Mbit/s 28 MHz 98.0 dB

050-D51.7Mbit/s 050-E16E1+ 18.6Mbit/s

050-F12E1+26.9Mbit/s8E1+35.1Mbit/s4E1+43.4Mbit/s2E1+47.5Mbit/s

Indoor Unit


Table 1-G ANSI Radio Capacity and Payload ConfigurationsLicensed Throughput Bandwidth System Configuration

Capacity Modulation* Traffic Type† Gain‡ Designation

6 Mbit/s QPSK4DS1

6.2 Mbit/s 5 MHz 113.5 dB006-A (PDH)

6.2Mbit/s 006-B (ETH)2DS1+3.1Mbit/s 006-C (BOTH)

12 Mbit/s 8PSK

8DS1

12.4 Mbit/s 5 MHz 102 dB

012-D12.4Mbit/s 012-E4DS1+6.2Mbit/s 012-F2DS1+9.3Mbit/s

12 Mbit/s QPSK

8DS1

12.4 Mbit/s 10 MHz 110.5

012-A12.4Mbit/s 012-B4DS1+6.2Mbit/s 012-C2DS1+9.3Mbit/s

24 Mbit/s 8PSK

16DS1


024-D24.7Mbit/s 024-E12DS1+6.2Mbit/s

024-F8DS1+12.4Mbit/s4DS1+18.5Mbit/s2DS1+21.6Mbit/s

30 Mbit/s QPSK

16DS1


031-A31Mbit/s 031-B16DS1+6.2Mbit/s

031-C12DS1+12.4Mbit/s8DS1+18.6Mbit/s4DS1+24.8Mbit/s2DS1+27.9Mbit/s

42 Mbit/s 8PSK

16DS1


043-D43.2Mbit/s 043-E16DS1+18.5Mbit/s

043-F12DS1+24.7Mbit/s8DS1+30.9Mbit/s4DS1+37.0Mbit/s2DS1+40.1Mbit/s

34 Mbit/s QPSK

16DS1

34.0 Mbit/s 30 MHz 106.5 dB

034-A34.0Mbit/s 034-B16DS1+9.3Mbit/s

034-C12DS1+15.4Mbit/s8DS1+21.6Mbit/s4DS1+27.8Mbit/s2DS1+30.9Mbit/s

49 Mbit/s 8PSK

16DS1


049-D49.4Mbit/s 049-E16DS1+24.7Mbit/s

049-F12DS1+30.9Mbit/s8DS1+37.1Mbit/s4DS1+43.3Mbit/s2DS1+46.4Mbit/s

* QPSK offers high gain while 8PSK offers high throughput. 8PSK units have QPSK capability.† "+xx Mbit/s" show the Ethernet payload throughput.‡ Typical with 7/8, 15, and 18G RFU; 13G: -1dB, 23G: -2dB, 38G: -5dB.

Radio Description


Outdoor Unit

Radio Frequency Unit

The outdoor unit (ODU) includes the radio frequency (RF) unit, an inte-grated antenna with press-fit adapters, and the mounting hardware.

Appendix E describes alternate ODU mounting configuration - offset and rack mounting.

The RFU mounts to the antenna with latches, so it can be replaced without tools or affecting antenna alignment.

To mount the ODU separate from the antenna, order the offset mounting hardware separately. To mount the ODU in a rack, order the rack mounting kit separately. Appendix E lists the part numbers for, and describes, these al-ternate mounting configurations.

Table 1-H lists the basic RFU part numbers. Appendix A details the trans-mit/receive spacing, high/low (go/return) channel, and sub-band of each of the RF units. RF units accept a 350-MHz intermediate frequency (IF) from the IDU, and return 140-MHz IF to the IDU (see page 1-14).

Figure 1-4. Proteus AMT L-Series ODU

RF Unit

AntennaMounting latches

N-Type input/output connector

Mounting latches

Outdoor Unit


Table 1-H RF Unit Part Numbers

Unit Frequency Range T/R Spacing (MHz) Part Number*

7G 7.12 – 7.9 GHz 154, 160, 161, 196 63-07yyyy-zzx11-61008G 7.9 – 8.5 GHz 119, 126, 208, 266, 311.32 63-08yyyy-zzx11-610011G 10.7 – 11.7 GHz 490, 530 63-11yyyy-zzx11-610013G 12.75 – 13.25 GHz 266 63-13yyyy-zzx11-610015G 14.4 – 15.35 GHz 315, 420, 475, 490, 640, 644, 728 63-15yyyy-zzx11-610018G 17.7 – 19.7 GHz 1010, 1560 63-18yyyy-zzx11-610023G 21.30 – 23.6 GHz 1008, 1200, 1232 63-23yyyy-zzx11-610026G 24.25 – 26.5 GHz 1008 63-26yyyy-zzx11-610038G 37 – 40 GHz 700, 1260 63-38yyyy-zzx11-6100

* x – subunit or sub-bandy – T/R spacingz– low band (00) / high band (10)

BACK SIDE VIEW FRONT

ANTENNAINTERFACE

MOUNTINGCLAMPS

N-TYPE INPUT/OUPUT(TO/FROM IDU)AGC VOLTAGE

CONNECTION(FACES ANTENNA)

MOUNTINGCLAMPS

LOCKABLELATCH

LOCKABLELATCH

POLARIZATIONMARK

Figure 1-5. RF Unit Features

Table 1-I RF Unit ConnectionsConnection DescriptionIDU In/Out Type N femaleAGC Voltage BNC

RF Input/Output

Direct press-fit coupling to the antenna. All units have a circular waveguide interface. 13G & 15G units normally use a rectangular waveguide interface.

Radio Description


Antenna

The ODU uses 30, 45, 60, 90, 120, and 180 cm antennas. 30 to 90 cm, direct interface, low-profile antennas (Figure 1-6) for 13 to 38-GHz radios. 120 and 180 cm antennas (Figure 1-7) are available for 7 to 23-GHz radios.

Figure 1-6. Low Profile Antennas

Figure 1-7. 1.2- and 1.8m Antennas

Outdoor Unit


Appendix E describes options for separate antenna and RF unit placement - offset and rack mounting.

All antenna include an applicable radio interface flange and mounting hard-ware. Antenna mounting hardware is a single bracket that accommodates left or right hand mounting and to a tower or pole.

RF units fasten to antennas with latches. The antenna has a self-fitting feed assembly for direct 'push-fit' coupling of the RF unit.

The antenna mounting hardware includes course and fine adjustment points for elevation and azimuth: ± 35° elevation, ± 15° azimuth.

NOTE: See Appendix E for mounting RF units apart from antennas.

Radio Description


IDU-to-ODU Interface CableA single RG-8A/U coaxial cable assembly (or RG-8A/U equivalent) that uses Type N connectors at each end couples the IDU and ODU. The coaxial cable assembly carries transmit IF at 350-MHz from the IDU to the ODU, and receiver IF at 140-MHz from the ODU to the IDU (Figure 1-8). The ca-ble also carries two radio telemetry channels at 5.5 and 10 MHz for alarm and control signals between the IDU and ODU, and -48 VDC to power the ODU. Cable length is limited to 22 dB cable loss at 350-MHz; typically 260-meters of recommended cable (Table 1-J).

Two types of cable are available: standard cable for cable runs through con-duit, and plenum cable for cable runs in environmental air spaces (plenum spaces). Plenum cables provide adequate fire-resistance and have low smoke-producing characteristics.

Cables and associated material ship un-assembled. Use the assembly proce-dure in Chapter 2 to assemble your cable.

NOTE: If you use a standard RG8A/U cable from second-source, MNI cannot guarantee radio operation to specification.

DC

DATA LINK5.5 MHz Up

10 MHz Down350 MHZ

IF Up

CABSPE.VSD

140 MHZIF Down

Figure 1-8. Signals Multiplexed onto the IDU-to-ODU Cable

Table 1-J IDU-to-ODU Cable ComponentsDescription Part NumberRG-8 A/U cable - per meter (Times Microwave LMR-400) 9900641-00

N-Type connector - 2 per cable 9900642-00RG-8 A/U plenum cable - per meter (LMR400LLPL) 9900646-00N-type connector for 9900646 - 2 per cable 9900647-00Ground kit for RG-8 cable 9900648-00Crimp tool for 9900942-00 9900645-00Cable-prep tool 9900643-00Cable center-conductor de-burring tool 9900644-00

Radio Management


Radio ManagementAll Proteus AMT L-Series radios include a radio management channel for terminal-to-terminal communication of alarm, control, and status informa-tion. This channel makes all operational data from both ends of a link avail-able at either terminal. A second overhead channel is a 64-kbps Ethernet channel for SNMP radio management is called the out-of-band NMS mode. Radio application code 1.B and later lets you use radio Ethernet payload to transport NMS data–the in-band NMS mode.

NOTE: In-band NMS mode is a software setting in CTI that places NMS data on the same channel as the Ethernet payload. Connecting these ports together externally while in the in-band mode causes port collisions.

Each device controller accesses all alarms and controls in the IDU and ODU. Access radio management data at the controller in several ways as Figure 1-9 shows:

• Element Manager—A Windows® graphical interface provided with each Proteus AMT L-Series radio that connects to the controller from the serial COMPUTER port, or the NMS port on the front panel. Radios ship with the EM installation disk.

• CTI/CLI—Craft-terminal interface and command line interface. Character-mode menu system for VT100-compatible terminals or applications. Access the command line by exiting the menu system. Connection to the serial COMPUTER port or through Telnet to the NMS port on the front panel.

• SNMP—IP-based open-system interface that connects to the NMS port. Radios ship with the Proteus AMT L-Series management information base (MIB) file for use with any SNMP application.

You can connect multiple radio controllers to a central manager. Each con-troller has its own address, so the manager can access coupled radios indi-vidually.

Radio Description


Element Manager

Element Manager (EM) is the radio link maintenance and control system. EM gives radio installers, maintenance personnel, and operators a tool for management and control of individual radio links–on site or from remote lo-cations–using the familiar Windows® environment.

Note: For management of radio networks order and use the Element Management System, P/N 8708270-00, with EM.

EM has full function from either the serial or the IP interface. Software con-trols all radio configuration. You never open the IDU to change jumpers or switches.

EM connects to the radios locally on the serial or Ethernet ports. EM inter-faces remotely through an IP network to provide all the same functions as the local serial interface.

EM Connections

EM operates in a personal computer running the Windows® operating sys-tem attached to the Proteus AMT L-Series radio. As a network element the radio acts as a multi-homed device. That is, the radio has two IP interfaces: an external 10/100-Mbps Ethernet interface, called LAN in EM, and an inte-gral 64-kbps IP-based overhead channel, called WAN. The WAN transports radio-specific data across each microwave link or a radio network.

Figure 1-9. Interfaces to Radio Management Applications

IDU

Element ManagerOn PC via Ethernet

On PC via Serial

3rd Party SNMPManager via Ethernet

3rd Party Telnet Clientvia Ethernet

Craft Terminal /Command Line Interface

VT100 via Serial

Element Manager

Radio Management


EM queries the radio that you connect to, or address, for configuration, events, and alarms, and performance data. The system gathers and posts per-formance-data changes every five seconds. EM also displays radio informa-tion, alarms, status, configuration, logs, and reports. You can open any or all screens from the EM main window.

SNMP

SNMP provides device management using Ethernet. Since SNMP is an open-standard protocol, any SNMP-capable application can manage Proteus AMT L-Series radios.

SMNP is a network management standard for LANs that defines a cli-ent/server relationship. The client program or network manager makes vir-tual connections to a server program, called an SNMP agent, that operates on a remote network device and serves information about device status to the manager. SNMP uses a management information base (MIB) to define these virtual connections. Any SNMP manager, with proper access, can query the status and modify the configuration of each managed device.

A MIB is a standard set of structure and format definitions for exchanging information about network devices. Microwave Networks' MIB is a private MIB for its radio. The MIB contains the common name of each object (which must be unique), the value of the object IDs (which are hierarchical and must be unique), and the textual description of the syntax and semantics of the radio.

SNMP Connection

NMS uses SNMP either on the out-of-band NMS port of the front panel, or on the Ethernet payload in the in-band mode. You can configure the NMS port speed and duplex settings–auto-negotiation mode is the default. Change NMS ports independently from Configuration menus. Settings include: Powered Down, Auto-negotiate, 10BaseT Half-duplex, 10BaseT Full-du-plex, 100BaseT Half-duplex, 100BaseT Full-duplex. Port 1 is the top con-nector and Port 2 the bottom.

When connecting radios back-to-back, set the port speed to a fixed setting on one of the radios. Cable auto-sensing (MDI/MDIX) is always enabled, and works for most hubs and radios. However, MiLan hubs connect with fixed cable pinout: straight to back or crossed to front ports.

Ethernet routing options include static routing–manual entry of up to 32 IP path addresses–or dynamic routing where IP routing is self-learning. Rout-ing Information Protocol (RIP) provides dynamic routing of up to 15 radios in a subnet. Spans of these 15-radio subnets are unlimited.

Use RIP for networks of moderate size within the following limitations:

• Limited to sub-networks whose longest path is 7 hops (15 radios).

Radio Description


• Uses fixed metrics to compare alternative routes; it is unsuited to situations where routes need to be chosen based on real-time parameters such a measured delay, reliability, or load.

After setting the IP address of the first-accessed radio locally, and then con-figuring it as an intermediate gateway, routing tables of radios network ex-change and incorporate route information as the radio network changes.

The management station, or SNMP manager, sends get and set requests to the SNMP agents–the radios. The radio answers get and set requests from the manager as specified by the MIB.

Each radio has two IP addresses: the Ethernet interface at the front panel, and the IP-over-air interface (WAN). The over-air interface transports radio support data, including get and set requests from the SNMP manager, over the microwave link and to other addressed radios as routing tables define (see Appendix D for LAN and WAN channel configuration and routing).

Text-Based Menu Interface

A text-based or craft-terminal interface (CTI) is available on all Proteus AMT L-Series radios as an alternative to EM and SNMP for radio operation, administration, and maintenance. The Proteus AMT L-Series radio text-based menu system gives radio installers and maintenance personnel a simple and efficient way to monitor and control radios from a VT100 com-patible terminal or from a portable PC that uses a terminal emulation appli-cation.

The text-based interface does not have the hardware and software require-ments of the graphical interface, and is small enough to be integral to each radio. All a user needs is a terminal.

Radio information presented by the text-based interface is static and does not provide the extended help information that a novice user may need. Text-based BER and performance statics update once every five seconds.

Text-Based Interface Connection

Proteus AMT L-Series text interface operates on any VT100-compatible ter-minal or application attached to the COMPUTER connection or through a Tel-net session as the next section describes.

Telnet

Use Telnet to connect to the radio via IP without an SNMP manager. Telnet is a terminal emulation program for TCP/IP networks. Telnet typically comes with the Windows® operating system. Connecting to the radio through Telnet enables the text-based interface – CTI/CLI.

Radio Management


The Telnet option enables commercially available TCP/IP network manage-ment facilities a way to monitor Proteus AMT L-Series radios.

To start a Telnet session, connect to the IP address of a radio on your net-work, and then log in to the radio by entering a valid user name and pass-word.

Telnet Connection

Telnet to the radio management application uses the radio IP interface. Con-nect Telnet through the RJ-45 NMS (ethernet) connection of the front panel to employ the radio craft-terminal interface (CTI) or command-line interface (CLI).

You can set NMS port speed and duplex settings – auto-negotiation mode is the default. Change NMS ports independently from Configuration menus. Settings include: Powered Down, Auto-negotiate, 10BaseT Half-duplex, 10BaseT Full-duplex, 100BaseT Half-duplex, 100BaseT Full-duplex. Port 1 is the top connector and Port 2 the bottom.

When connecting radios back-to-back, set the port speed to a fixed setting on one of the radios. Cable auto-sensing (MDI/MDIX) is always enabled, and works for most hubs and radios. However, MiLan hubs connect with fixed cable pinout: straight to back or crossed to front ports.

In-Band NMS Mode

Alternately, connect to the radio management using the in-band NMS mode. This is a software setting in CTI that places NMS data on the same channel as the Ethernet payload. You do not have to cable the NMS ports to the Ethernet payload. Doing so with the radio in the in-band mode would cause data collisions.

Radio Description


System SpecificationsProteus AMT L-Series is a mixed Plesiochronous Digital Hierarchy (PDH) and Ethernet (packet-data) radio. The radios service PDH lines that use in-ternational (ETSI) and North American (ANSI) digital transmission stan-dards.

General Radio Specifications

The first few tables cover general specifications. Subsections that follow list specifications for radios that use ETSI and ANSI bandwidths.

Table 1-K General SpecificationsParameter SpecificationOperating Frequencies 7.125—8.50 GHz* 17.70—19.70GHz

10.70—11.70 GHz* 21.20—23.60 GHz12.75—13.25 GHz* 24.25 - 26.5 GHz14.40—15.35 GHz 37.00—40.00 GHz

Intermediate Frequencies Transmit (up the cable) 350 MHz, Receive 140 MHzTransmit Frequency StabilityOutput Power ControlMin. Output Power

±7 ppmManual or Automatic: 1 dB steps

-4 dBmReceiver Frequency StabilityReceiver Coding

±7 ppmReed Solomon FEC

Residual BER < 10-11

IDU to ODU InterfaceConnector TypeCableMax. Distance

Coaxial, N-Type FemaleTimes Microwave LMR400 or equivalent RG-8A/U22 dB of cable loss at 350 MHz

Radio Management SNMP/Telnet

Element ManagerCraft Terminal

NMS (10/100BaseT), RJ-45, IEEE 802.3, 802.3uIN-BAND OR OUT-OF-BAND MODE

NMS (10/100BaseT), RJ-45, IEEE 802.3, 802.3uCOMPUTER (RS-232), DB9 for VT100 terminal

StandardsSafetyEMI/EMCCircuit BreakersRadio Approval

7/8 GHz10 GHz11 GHz13 GHz15 GHz18 GHz23 GHz26 GHz38 GHz

EN 60950EN 301 489; EN 300 385, FCC Part 15EN 60947-2FCC Part 101, EN 302 217

EN 301 216; ITU-R F.385.7EN 301 216; ITU-R F.747EN 301 216; ITU-R F.387.7EN 301 128; ITU-R F.497.5EN 301 128; ITU-R F.636-3EN 301 128; ITU-R F.595.5EN 300 198; ITU-R F.637-2EN 300 431; ITU-R F.748-2EN 300 197; ITU-R F.749-1

* ETSI ONLY

System Specifications


Table 1-L Environmental SpecificationIDU

Temperature-5 to +50°C Full Performance-10 to +50°C Operational-40 to +70°C Storage

ETSI 300-019-1-3 Class 3.2

Humidity Up to 95%, non-condensingAltitude 5000 metersODU Full Performance Operational*

Temperature -33 to +55°C -55 to +55°C ETSI 300-019-1-4 Class 4.1E(with extended temperature requirement)Humidity up to 100%

Altitude 5000 meters* System gain variance is within 2db

Table 1-M Mechanical SpecificationIDUDimensions (H x W x D) 4.5 x 43 x 28 centimeter Weight 3 kgODUDimensions 25 cm OD x 10 cm deepWeight 4 kg

Table 1-N Power SpecificationParameter SpecificationStandard Voltage -30 Vdc to -60 Vdc EN 300 132-2

(Power Supply Inter-face at the Input to Telecommunica-tions Equipment)

Optional Voltage +19 to +28 Vdc

Power Consumption*

* Inrush current: ≥8A for up to 3 ms.Power supplies must handle the radio in-rush current. MNI recommends its AC converter, P/N 8708263-00.

50 watts non-protected100 watts protected

Power Protection 48V – 5A fuse24V – 7A fuseIf used, circuit breakers must be ≥6A with a trip characteristic of 'C' or slower.

Radio Description


System Performance: Power and Threshold

Table 1-O lists transmit power for all data rates and bandwidths.

Table 1-P lists threshold and throughput measurements for non-protected ra-dios using ETSI bandwidths. Table 1-Q lists threshold and throughput mea-surements for non-protected radios using ANSI bandwidths.

Hot-standby (HSB) radios, discussed in Appendix F, use an unequal-split coupler assembly. Include the following branching losses in HSB radio specifications

Table 1-O RF Transmit PowerRF Unit TX Power*

* Maximum TX power setting. Actual output power will be ±1dB at the antenna flange. Minimum TX power setting must be no less than -4dBm.

QPSK 8PSK7/8 GHz 25 dBm 21dBm11, 13, 15, 18 GHz 24 dBm 20 dBm23 GHz 22 dBm 19 dBm26 GHz 22 dBm 18 dBm38 GHz 20 dBm 16 dBm

Table 1-P System Specifications – ETSI Bandwidths Bandwidth 3.5 MHz 7 MHz 14 MHz 28 MHz 3.5 MHz 7 MHz 14 MHz 28 MHz

Data Rate* 4 Mbit/s 8 Mbit/s 16 Mbit/s 32 Mbit/s 8 Mbit/s 16 Mbit/s 32 Mbit/s 50 Mbit/s

Modulation QPSK Optional 8PSKEmission Designator 3M50G7W 7M00G7W 14M0G7W 27M5G7W 3M50G7W 7M00G7W 14M0G7W 27M5G7W

Receive Threshold (10-6; dBm)7/8, 13, 38 GHz -90.0 -87.5 -84.5 -81.5 -82.0 -80.5 -78.0 -76.5

15, 18, 23, 26 GHz -91.0 -88.5 -85.5 -82.5 -83.0 -81.5 -79.0 -77.5* Minimum throughput. Use any payload configuration licensed up to the maximum available data rate (see Table 1-F).

Table 1-Q System Specifications – ANSI BandwidthsBandwidth 5 MHz 10MHz 20 MHz 28 (30) MHz 10 MHz 20 MHz 28 (30) MHzData Rate* 6 Mbit/s 12 Mbit/s 31 Mbit/s 34 Mbit/s 24 Mbit/s 42 Mbit/s 49 Mbit/s

Modulation QPSK Optional 8PSKEmission Designator 5M00G7W 10M00G7W 20M0G7W 27M5G7W 7M00G7W 20M0G7W 27M5G7WReceive Threshold (10-6; dBm)7/8, 13, 38 GHz -88.5 -85.5 -84.0 -81.5 -78.0 -78.0 -77.015,18, 23, 26 GHz -89.5 -86.5 -85.0 -82.5 -79.0 -79.0 -78.0

* Minimum throughput. Use any payload configuration licensed up to the maximum available data rate (see Table 1-G).

Table 1-R Hot-Standby Branching LossPrimary Secondary

Transmitter 1.9 dB 6.5 dBReceiver 1.9 dB 6.5 dB

System Specifications


Ethernet Performance: Throughput and Latency

Table 1-S shows the typical throughput and latency expected for each ca-pacity using the Ethernet payload configuration. Although the table only covers a 1518-byte frame size Appendix G presents a detailed table that cov-ers frame sizes from 64 bytes.

Table 1-S Ethernet Data Throughput and Latency, ETSI Bandwidths, 1518-byte Frame Size

Bandwidth Modulation Capacity Throughput (Mbit/s)

Latency (ms)

3.5 MHz QPSK - 100BT 4.15 5.7678PSK - 100BT 8.29 4.4918PSK 2E1 100BT 4.15 5.992

7 MHz QPSK - 100BT 8.28 3.0818PSK - 100BT 16.56 2.445QPSK 2E1 100BT 4.16 4.5978PSK 2E1 100BT 12.42 2.6868PSK 4E1 100BT 8.29 3.194

14 MHz QPSK - 100BT 16.56 2.2398PSK - 100BT 33.10 1.911QPSK 2E1 100BT 12.42 2.4838PSK 2E1 100BT 28.97 1.957QPSK 4E1 100BT 8.29 2.9718PSK 4E1 100BT 24.83 2.0358PSK 8E1 100BT 16.59 2.284

28 MHz QPSK - 100BT 33.10 1.3798PSK - 100BT 51.72 1.223QPSK 2E1 100BT 28.97 1.4348PSK 2E1 100BT 47.58 1.246QPSK 4E1 100BT 24.83 1.5068PSK 4E1 100BT 43.45 1.266QPSK 8E1 100BT 16.56 1.7488PSK 8E1 100BT 35.17 1.336QPSK 12E1 100BT 8.28 2.4978PSK 12E1 100BT 26.91 1.4408PSK 16E1 100BT 18.63 1.644

Radio Description



Chapter 2Installation

Installation InformationThis material covers physical installation of a non-protected radio. See Chapter 3 to setup and initialize the radio.

This chapter outlines physical installation of a non-protected Proteus AMT L-Series radio. See Chapter 3, Commissioning, to setup the radio and start traffic; see Appendix F for hot-standby radio installation.

Proper installation planning includes: selecting a site, verifying site ground, and arranging power. Follow procedures in this section for trou-ble-free operation. Procedures typically progress in the following order:

• preparing the site• unpacking equipment• running the coaxial cable• installing the IDU• installing the ODU

Location

When selecting a site look for:

• Climate-controlled environment with adequate air flow for the IDU• Ample power. Rate power protection for in-rush current (page 2-8)• Site grounding that meets ITU-T Re. K.27 and applicable local

standards• Proper floor loading, space, and overhead support• Enough clearance in front of the equipment for maintenance• Enough lighting for installation and maintenance

Environment

Mount the IDU away from heat sources and in a weather–protected area. The IDU chassis relies on convection to cool the boards. Keep heat sinks on the back of the chassis clear of obstruction.

The ODU is exposed to severe weather. Ensure all RF Unit cover screws are tight. Seal and weatherproof any external connector.

Installation


Grounding

The IDU chassis must be grounded to the facility grounding system to minimize the possibility of damage from lightning strikes and the impact of electromagnetic- and radio frequency-interference (EMI/RFI). The ODU must also be grounded to systems for towers and shelters that fol-low published guidelines, such as ITU-T Rec. K.27, that provide the ground reference necessary for reliable radio operation

Ideally, a grounding system provides the shortest possible path and the lowest possible impedance to the ground reference point. The ground reference is established by buried grids for telecommunication site-spe-cific situations (tower and shelter) or the water pipe and/or buried ground rods (usually at the power entry point) for a building.

The recommended resistance of the building primary ground to earth shall be as low as possible and should not exceed five (5) ohms.

Cable and Connector Considerations

Use RG-8A/U coaxial cable with a double shield (Times Microwave LMR400 or equivalent) with male N-connectors at each end of the cable to connect the IDU to the ODU. When cutting the cable add extra length for service loops. Seal and weatherproof any external connection.

A high density sub-D connector connects T1/E1 lines using shielded twisted-pair wires. See 'Connecting E1/T1 Lines,"on page 2-11.

A connector kit ships with each radio, which includes the items you need to cable the AMT L-Series radio. Table 2-A lists items in kit P/N 8708236-02.

RJ45 cables connect 100-Mbps Ethernet data using 8-position modular connectors on CAT5 unshielded twisted pair (UTP) cable. See 'Connect-ing Network Management,"on page 2-13.

Use RJ45 cross-over cables when the two connecting devices have the same interface type: a data terminating equipment (DTE) interface or a data communications equipment (DCE) interface. Use a straight-through cable when connecting a DTE device to a DCE device; like connecting a PC to a hub. The cable between the computer and the hub must be less than 100 meters long.

Table 2-A Installation KitPart Number Description Use3070037-00 Cable Connector, DB9P, Serial user interface3070037-05 Cable Connector, DB78P Line signals3024080-25 Latching Plug Connector, 3 pos. Power8860017-10 AMT L-Series Quick-Start Guide Instructions

Tools and Material


Tools and Material

Gather the following tools to install the radio:

• 1/4" open end wrench• 3/8" open end wrench or hollow nut driver for 3/8-16 nut• Phillips screwdriver (large)• Straight blade screwdriver (medium)• Various wire cutters (for cable preparation)• Crimping tool for Type-N connector • Hand-held voltmeter, including adapter for BNC connector• 5/32 in. (or 4 mm) Allen wrench• Optical aid (binoculars) or compass (optional)• Communications devices such as two-way radios

Also, prepare the following materials:

• 2 standard (sealed) N-type connectors• Tie wraps (or similar) for fastening cable• Lightening protectors (if necessary)• 8.5 mil all-weather electrical tape or vinyl mastic for

weatherproofing• Coax cables: up to 22-dB of cable loss at 350-MHz (about

260 meters of cable)

Preparing the SiteMounting the Rack

A typical floor-mounting procedure includes drilling holes in the floor to match the mounting holes. Rack hardware is available for both floor and overhead supports.

Install any overhead support structure above the rack. The rack attaches to the support with J-hooks. If support is a channel ladder that spans the ceiling, one J-hook on each side of the ladder provides enough support. If the channel ladder is a short piece attached to an overhead structure, use additional J-hooks.

After drilling the mounting holes, place the rack on top of the holes and install appropriate anchor bolts through the mounting holes in the rack. If the area for the rack does not have rear access, connect DC power as de-scribed in the following text prior to securing the rack.

A radio rack typically has a ground bar running the length of the rack. This assembly accepts up to 6-AWG stranded grounding wire. Attach ground bars to the office/building ground.

Installation


Tighten the anchor bolts to secure the rack. On an overhead-supported rack, tighten the support hardware at the top as well as the bolts at the base.

Run two wires for the DC power connection at the front of the radio to primary and secondary DC source (typically batteries).

Unpacking Equipment

Each product is completely assembled, tested, and then shipped in pack-aging that minimizes the effects of shock in shipping. On receipt, check the crate for damage.

Carefully remove equipment from the containers to prevent damage to the units. Ensure that all parts and accessories are removed from the con-tainer and packing material before they are discarded. Check equipment for physical damage.

File claims for shipping damage immediately with the transportation company, and report the issue with MNI Customer Service at U.S. 281.263.6501; or toll free within the U.S. at 1.888.225.6429.

If more than one radio gets delivered to a single site, identify the radio by the packing list. Verify that you received all components listed on the shipping order. Each radio terminal is shipped as either the 'LB' or 'HB' radio – which refers to 'go' and 'return' frequencies of its channel plan.

• An 'LB' terminal transmits in the lower portion, and receives in the upper portion, of the assigned frequency band.

• An 'HB' terminal transmits in the upper (high) portion, and receives in the lower portion, of the assigned frequency band.

While unpacking the units, compare the serial number of the ODU with the factory supplied test data. Labels on each unit list serial numbers and frequencies.

ODU tuning is fixed to the range of its diplexer. Spares come in sets that include the high- and low-band units (go and return frequencies of each channel plan).

The RF unit is set as a transmit low- or high-band unit. RF units use a di-plexer instead of band-pass filters. Sub-band and transmit/receive spac-ing (low/high band) are fixed and must be specified at time of order. If purchasing and storing spares, store LB/HB sets for each frequency. RF unit synthesizers tune through the entire half-band of its frequency plan, but tuning range is fixed to the bandwidth of the diplexer.

NOTE: To tune an RF unit past its tuning range you need a new unit with a different diplexer. Diplexer replacement is a factory-level procedure. Contact Customer Service for more detail.

The IDU is fixed, tested, and labeled at the factory to a matching ODU. MNI recommends that you keep IDU/ODU pairs together, but IDUs will work with ODUs with 350/140-MHz IF; these units have part numbers that start with AMT2.

Installing the Coaxial Cable



Find, as far in advance as possible, the best route to get the IDU-to-ODU coaxial cable from the ODU installation point to the IDU. Use a ple-num-rated cable as local code requires.

Protect the exposed cable as much as possible until installation is com-plete.

Start at the ODU installation point and run the un-terminated cable end along the selected route. Leave enough cable at the site to reach the ODU and create a service loop.

If the cable must cross a commercial built-up roof, put insulation be-tween the cable and roof. Plenum cable is recommended for such an in-stallation. Use the following guidelines for proper cable installation:

• When cutting the cable to length, add extra for drip and service loops. Limit cable length to 22 dB of loss at 350-MHz (260m of TM-LMR-400, or 300m of LMR-500).

• Add strain relief to cable connections.• Seal and weatherproof any external connector. Deterioration of

connectors from moisture is a serious problem. Weatherproof connectors using one of the following methods:– Cover the exposed connector and portion of the cable with 8.5-mil

insulating electrical tape or vinyl mastic.

– Cover the exposed connector and a portion of the cable with heat-shrinkable sleeve. Shrink the sleeve with a heat source, let cool, and cover with a coat of sealing compound.

Follow manufacturer's procedures for applying tape and shrinkable sleeve to obtain the best weatherproofing seal.

• When running the cable between the IDU and ODU, follow standard installation practices. Avoid sharp corners. Time Microwave LMR400 cable has a 2.5 cm (1-inch) minimum bend radius. Check manufacturer’s specification if you use another cable type. Secure the cable to the tower members or cable runways using hangers or tie-wraps at one-meter (three-foot) intervals.

Assembling the Cable

A single coaxial cable connects the IDU to the ODU. Use RG-8A/U 50-ohm coaxial cable (Time Microwave LMR400, 500, or equivalent) with male N-connectors at each end of the cable. The crimp tool and die that Table 2-B lists supports N-type connectors.

Installation


Table 2-B IDU-to-ODU Cable ComponentsDescription Part NumberRG-8 A/U cable - per meter (LMR-400) 9900641-00N-Type connector - 2 per cable 9900642-00RG8 A/U plenum cable - per meter (LMR400LLPL) 9900646-00N-type connector for 9900646 - 2 per cable 9900647-00Ground kit for RG-8 cable 9900648-00Crimp tool for 9900642-00 9900645-00Cable-prep tool 9900643-00Cable center-conductor deburring tool 9900644-00

Table 2-C IDU-to-ODU Cable AssemblyStep Procedure1 Cut the cable, allowing for service loops at the IDU and ODU.2 Slide a crimp ring on the un-stripped cable with its gasket facing

away from the connector body. A dot of silicon can help work the gasket over the cable jacket.

3 Expose 7/32" (5.6mm) of the center conductor. Do not score the conductor.

4 Remove 5/8" (15.9mm) of the cable jacket. Do not cut through the braid.

5 Flare the braid slightly and trim it to 7/16" (11.1mm). Push the pin over the center conductor and crimp it with a 0.108-inch (2.7mm) hexagonal crimp tool.

6 Guide the pin and cable through the insulator into the back of the connector, until the pin is home. Slide a crimp ring over the braid and into the recess at the back of the connector. Crimp the connector with a 0.475" (12.1mm) hexagonal crimp tool.

7 If the crimp ring will not pass over the braid, comb the braid and re-trim it to 7/16" (11.1mm). Repeat Step 6.



Installing the Cable

To install the IDU to ODU coaxial cable:

1. If the IDU is installed, remove DC power from the front of the unit.

2. Connect the coaxial cable to the ODU port of the IDU.

3. Install the cable grounding kit, P/N 9900648-00, per the manufacturer instruction.

4. At the ODU – connect a 6-AWG copper wire (not supplied) from the ODU grounding post to a ground point on the tower. This ground cable places the ODU at the same electrical potential as the IDU. See “Grounding” on page 2-2.

5. At the ODU – connect the coaxial cable to the ODU N-type connector on the bottom of the RF unit.

WARNING Ensure DC power is off at the IDU prior to connecting the cable at the ODU. If you cannot avoid connecting a 'hot' cable, remember that the cable carries DC power. DO NOT short the center contact of the cable connector to the connector body!

6. Weatherproof as previously described on page 2-5.

Installation


Installing the Indoor Unit

Mounting the IDUTo install hot-standby units see Appendix F.

Mount the IDU shelf in the standard 19-inch equipment rack or equip-ment cabinet. The chassis occupies one rack space and does not require forced convection cooling. When mounting:

• Avoid direct heat. If unavoidable, use deflector plates.• Locate equipment near sufficient power outlets to provide power to

test equipment.• Eliminate conditions that could cause water to drip onto equipment.

This non-protected unit takes one rack unit (1RU; 1.75 inch) of space.

Ground the IDU to facility ground to prevent damage to equipment and ensure reliable operation.

Ground the IDU chassis to the facility grounding system to minimize the likelihood of damage from lightning strikes and the impact of electro-magnetic- and radio frequency-interference (EMI/RFI). Grounding sys-tems for towers and shelters that follow published guidelines, such as ITU-T Rec. K.27, provide the ground reference necessary for reliable ra-dio operation. The IDU chassis front panel provides points for ground-ing.

Connecting PowerPower supplies must handle radio in-rush current≥8A up to 3ms.

The IDU power connector is a 3-pin Phoenix connector. The mating plug, 3024080-25, ships in the install kit (Table 2-A) with the radio. To connect power:

1. Connect the facility ground to pin 3 of the power plug.

NOTE: The radio does not work without proper ground connections.

If used, rate circuit breakers to handle the in-rush current: ≥6A with trip characteristic 'C' or slower.

Both the -48V and +24V power supplies require a ground reference to operate. Mounting screws ground a unit that you mount in a grounded EIA rack or enclosed cabinet. Otherwise, you must connect "ground" (pin 3) to the facility ground.

2. Turn your power supply on and check the polarity of the supply leads, and then turn your power supply off.

3. Connect positive supply lead to the positive pin of the mating plug as Figure 2-1 and Figure 2-2 show.

4. Connect negative supply lead to the negative pin of the mating plug as Figure 2-1 and Figure 2-2 show.

5. Plug the mating plug into the power connector.

See page 2-10 when installing a power protection device.

DC input to the 48V power supply will be between -40 to -60 Vdc (nom-inally -48V). The power supply tolerates up to 1Vpp input ripple, DC to 50 MHz, such that the peak voltages stay within the -40 to -60V limit.



NOTE: While the -48V power supply accepts from -40 to -60V, there will be up to 100 mV drop between the IDU input connector and the ODU connector. Under worse case conditions, voltage to the ODU varies from -39.9V to -60V

DC input to the 24V power supply will be between +19 to +30 Vdc (nominally +24V). The power supply tolerates up to 1Vpp input ripple, DC to 50 MHz, such that the peak voltages stay within the +19V to +30V limit.

For a single battery source on a protected radio, jumper positive (+) of the main IDU to positive (+) of the standby IDU, and negative (-) of the main IDU to negative (–) of the standby IDU with 12- or 14-AWG stranded wire.

Figure 2-1. IDU Power Connection for -48V Input

Figure 2-2. IDU Power Connection for +24V Input

Ground '+' of 48V supply to set ground refer-ence.

Ground '-' of 24V supply to set ground ref-erence.

Installation


Adding Power Protection

Proteus AMT L-Series power supplies include unique power protection, in addition to fuses, to provide reliable operation. The internal fast-blow fuses are 5A for -48V and 7A for +24V systems.

• Reverse polarity protection: wiring inputs in reverse will not cause damage.

• Positive/negative input protection: connecting +48V or -24V will not cause damage.

• Over-voltage input protection: connecting 48V instead of 24V (24V units) will not cause damage.

• Lightning protection: power leads can sustain a one-time standard impulse current of 8/20 µS at 5A.

NOTE: A lighting induced surge on the cable to the ODU is likely to turn on, "fire", the spark-gap protection device on the IF board. The device then conducts until power is removed when it resets. This causes the fuse to blow on -48V units.

Power supplies must handle the radio in-rush current.

Plan power devices — power supplies, fuse panels, breakers, un-inter-ruptible power supplies — to handle the radio in-rush current ≥8A up to 3 ms. If used, use circuit breakers ≥6A with category C, or slower, over-current ratings (EN 60947-2 1992). Figure 2-3 shows where you would install power protection devices.

UPS IDU

AC

PW

R

Optionally place afuse or breaker here.

Fuse or breaker notneeded; UPSincludes protection

Converter is internally limited;no fuse or breaker needed.

CH

AR

GER

IDUBatteryPack

AC/DC

48V/24V

Power Supplyfuse: 5A / 7AFAST-BLO

Power Supply fuse:5A FAST-BLO

Optionallyplace fuse orbreaker here.6A SLO-BLO

DC Power Connection

AC Power Connection 8708263-00

48V

for 48V

If using a breaker,use ≥6A trip rating 'C'or slower.

Must handleinrush current;≥8A for 3ms.

Figure 2-3. Connecting Power Protection Devices



Connecting E1/T1 LinesUse the twisted pair sets of your cable for each ring/tip signal of E1/DS1 lines.

Do not untwist any pair more than 12.7 mm (1/2 inch).

Line input and output signals connect with a DB78 female connector provided in the installation kit (Table 2-A). Line signals (Table 2-D) connect via twisted-pair wire to the E1/DS1 channels.

MNI sells a pre-fabricated DB78 cable, Figure 2-4, suitable for wire wrap. The cable is shielded 100-ohm cable, Essex 55-A99-21 (T1/E1 rated), with a metal shell connector – AMP 748368-1. Table 2-E lists the DB-78 cable pinning.

Table 2-D E1/T1 Line Wiring on DB78

Pin Signal Ch. Pin Signal Ch. Pin Signal Ch. Pin Signal Ch.1 TXT 15 21 TXR 15 40 TXT 16 60 TXR 162 RXT 15 22 RXR 15 41 RXT 16 61 RXR 163 GND 23 TXT 13 42 GND 62 TXT 144 TXR 13 24 RXT 13 43 TXR 14 63 RXT 145 RXR 13 25 GND 44 RXR 14 64 GND6 TXT 11 26 TXR 11 45 TXT 12 65 TXR 127 RXT 11 27 RXR 11 46 RXT 12 66 RXR 128 GND 28 TXT 9 47 GND 67 TXT 109 TXR 9 29 RXT 9 48 TXR 10 68 RXT 1010 RXR 9 30 GND 49 RXR 10 69 GND11 TXT 7 31 TXR 7 50 TXT 8 70 TXR 812 RXT 7 32 RXR 7 51 RXT 8 71 RXR 813 GND 33 TXT 5 52 GND 72 TXT 614 TXR 5 34 RXT 5 53 TXR 6 73 RXT 615 RXR 5 35 GND 54 RXR 6 74 GND16 TXT 3 36 TXR 3 55 TXT 4 75 TXR 417 RXT 3 37 RXR 3 56 RXT 4 76 RXR 418 GND 38 TXT 1 57 GND 77 TXT 219 TXR 1 39 RXT 1 58 TXR 2 78 RXT 220 RXR 1 59 RXR 2

Female front panel con-nector shown; mating connector pins are the mirror image (page 2-12).

1

Installation


Table 2-E Prefabricated DB78P Cable Wire List Pin Color Signal Pin Color Signal Pin Color Signal1 BLU/WHT TXT 15 33 BLK/BLU TXT 5 66 VIO/ORG RXR 12

21 WHT/BLU TXR 15 15 ORG/BLK RXR 5 47 NONE GND

3 NONE GND 34 BLK/ORG RXT 5 48 GRN/VIO TXR 10

2 ORG/WHT RXT 15 35 NONE GND 67 VIO/GRN TXT 10

22 WHT/ORG RXR 15 16 GRN/BLK TXT 3 49 BRN/VIO RXR 10

4 GRN/WHT TXR 13 36 BLK/GRN TXR 3 68 VIO/BRN RXT 10

23 WHT/GRN TXT 13 17 BRN/BLK RXT 3 69 NONE GND

5 BRN/WHT RXR 13 37 BLK/BRN RXR 3 50 GRY/VIO TXT 8

24 WHT/BRN RXT 13 18 NONE GND 70 VIO/GRY TXR 8

25 NONE GND 19 GRY/BLK TXR 1 51 BLU/WHT RXT 8

6 GRY/WHT TXT 11 38 BLK/GRY TXT 1 71 WHT/BLU RXR 8

26 WHT/GRY TXR 11 20 BLU/YEL RXR 1 52 NONE GND

7 BLU/RED RXT 11 39 YEL/BLU RXT 1 53 ORG/WHT TXR 6

27 RED/BLU RXR 11 40 ORG/YEL TXT 16 72 WHT/ORG TXT 6

8 NONE GND 60 YEL/ORG TXR 16 54 GRN/WHT RXR 6

9 ORG/RED TXR 9 41 GRN/YEL RXT 16 73 WHT/GRN RXT 6

28 RED/ORG TXT 9 61 YEL/GRN RXR 16 74 NONE GND

10 GRN/RED RXR 9 42 NONE GND 55 BRN/WHT TXT 4

29 RED/GRN RXT 9 43 BRN/YEL TXR 14 75 WHT/BRN TXR 4

30 NONE GND 62 YEL/BRN TXT 14 56 GRY/WHT RXT 4

11 BRN/RED TXT 7 44 GRY/YEL RXR 14 76 WHT/GRY RXR 4

31 RED/BRN TXR 7 63 YEL/GRY RXT 14 57 NONE GND

12 GRY/RED RXT 7 64 NONE GND 58 BLU/RED TXR 2

32 RED/GRY RXR 7 45 BLU/VIO TXT 12 77 RED/BLU TXT 2

13 NONE GND 65 VIO/BLU TXR 12 59 ORG/RED RXR 2

14 BLU/BLK TXR 5 46 ORG/VIO RXT 12 78 RED/ORG RXT 2

Pins in the shaded area are for those wires in an inner wht/org binder

Figure 2-4. Prefabricated DB78P Cable



Connecting Ethernet

10/100BaseT signals connect via RJ45 wiring on UTP CAT5 cable to 100-Ω balanced connectors. Connect Ethernet signals to bridged ports ETH1 and ETH2 as Table 2-F shows.

Ethernet ports are auto-sensing and auto-negotiating, so Ethernet connects between radios.

Ethernet connects between two radios back-to-back and auto-negotiate and auto-sense (MDI/MDIX) configure the ports. If an ethernet port in auto-ne-gotiate connects to a device that does not support auto-negotiation (parallel detect), as specified in IEEE 802.3u clause 28, it configures to half-duplex even when the connected device is a full-duplex device.

The latter case can cause excessive collisions and communications errors. Avoid any auto-negotiation problems on mission-critical links by setting both devices to the best possible speed and duplex setting.

You can configure speed and duplex settings. Auto-negotiate is the ether-net port default setting. You can disable (Power Down) each ethernet port, or configure the port data rate. Set the Ethernet port using the radio manage-ment application to one of:

• Powered Down• Auto-Negotiate (default)• 10BaseT Half-duplex• 10BaseT Full-duplex• 100BaseT Half-duplex• 100BaseT Full-duplex

Use RJ45 cross-over cables when the two connecting devices have the same interface type, i.e., both data terminating equipment (DTE) or data communications equipment (DCE). Use a straight-through cable when connecting a DTE device to a DCE device; for example, a PC to a hub

Once you connect Ethernet data set up IP routing as Appendix D describes.

Connecting Network ManagementRadio service channels provide the path for radio performance data and alarm messages, and for issuing configuration and control statements to individual radios, radio hops, and multiple radios of a radio network. This overhead channel includes the network management channel for ra-dio management communications and the auxiliary channels that the next section covers.

Table 2-F 100-BaseT Wiring (RJ45*)

* See “Cable and Connector Considerations” on page 2-2.

2-port bridgePin Signal I/O Pin Signal I/O1 Rx + I 5 GND2 Rx – I 6 TX – O3 Tx + O 7 GND4 GND 8 GND

18

Installation


A management controller accesses all alarms and controls in the IDU and ODU. The following interfaces provide access to radio management con-troller data in two modes–Ethernet IP and serial:

• COMPUTER: 9-pin sub-D connector. RS-232 serial interface to computer using VT100 emulation. The installation kit (Table 2-A) includes the mating connector for a straight-through cable (Table 2-G).

Wire the COMPUTER port serial cable straight through.

• NMS: two RJ-45 ports connection to the 64-kbps Ethernet channel for SNMP radio management–also called the out-of-band NMS port. Ports are bridged networks. Access the radio using SNMP or an IP application such as Telnet.

NMS port is auto-sensing (MDI/MDIX) and auto-negotiating. You can configure speed and duplex settings; auto-negotiation is the default. When you connect NMS ports between radios back-to-back auto-negoti-ate handles port configuration.

NOTE: Auto-sensing is always enabled, and works for most hubs and radios. MiLan hubs, however, connect with fixed cable pinout: straight to back or crossed to front ports.

Table 2-G Computer Port* (Serial; Sub-D 9-Pin Female)

* Wire cable straight through

Pin Signal I/O1 NC2 TXD O3 RXD I 4 NC5 GND6 NC7 NC8 NC9 NC

Table 2-H NMS Connection* (IP Interface)

* Use a shielded RJ45 crossover cable when connecting a computer to either NMS port, or when cabling from one IDU to another.

Pin Signal I/O1 Tx + O2 TX – O3 RX + I4 NC5 NC6 RX – I7 NC8 NC

8 1

1 8

IP NMS CROSSOVER CABLE

Installing the ODU


In-Band NMS Mode

You can optionally connect NMS in-band, which places NMS data on the same channel as the Ethernet payload. This is a software setting in CTI that places NMS data on the same channel as the Ethernet payload. You do not have to cable the NMS ports to the Ethernet payload. Doing so with the radio in the in-band mode would cause data collisions.

Installing the ODU

FundamentalsFor hot-standby ODU installation see Appendix F.

The non-protected ODU consists of an RF unit, a pole-mounting assem-bly, and a 0.3, 0.6, 0.9, or 1.2-meter antenna. All antennas include hard-ware for mounting to vertical pipe.

NOTE: Antenna mounting instructions included here are generic. Use any manufacturer’s instructions first.

Installing the ODU requires:

• unpacking equipment• attaching the mounting hardware to the pole• attaching the antenna to the mounting hardware• attaching the RF unit to the antenna• connecting the IDU-to-ODU coaxial cable

The ODU leaves the factory configured and designated as a low-band or high-band unit depending on the assigned transmit frequency sub-band. Ensure system components match before continuing this installation.

WARNING Read instructions before assembling or installing the antenna. Installation can be dangerous and requires qualified personnel familiar with antenna installation.

Microwave Networks disclaims responsibility or liability for damage or injury resulting from incorrect or unsafe installation procedures.

Installation


Torque Specifications

The following chart has the recommended torques for tightening nuts and bolts provided with the hardware kit. Prior to installing RF Unit hardware, place a small amount of silicon grease on bolt threads.

Unpacking Hardware

Carefully unpack the antenna assembly and mount from its shipping car-ton. The standard 0.3- and 0.6-meter (1- and 2-ft.) antennas ship partially assembled and include the following components:

• reflector and radome assemblies• feed assembly• offset tower mount• various bolts, nuts, flat washers, lock washers, allen keys• tube of Loctite

Table 2-I Fastener Torque SpecificationsUS Recommended Bolt Torque*

Size Grade 5 Grade 8 18-8 S/SCoarse Fine Coarse Fine Coarse Fine

#4 - - - - 5.2 -#6 - - - - 9.6 -#8 - - - - 19.8 -#10 - - - - 22.8 31.71/4 8 10 12 14 6.3 7.85/16 17 19 24 27 11 11.8

US Recommended Bolt Torque3/8 31 35 44 49 20 227/16 49 55 70 78 31 331/2 75 85 105 120 43 459/16 110 120 155 170 57 63

Metric Recommended Bolt Torque (Nm)Diameter Class 8.8 Class 10.95 7 96 12 168 30 4010 55 7512 100 13514 160 21516 245 33520 480 650* Sizes from 4 to 10 are in inch-pounds.

Sizes from 1/4 up are in foot-pounds.

Installing the ODU


Attaching the Mounting Assembly

Mounting hardware attaches the antenna to a vertical pole with a diame-ter of 48 to 115 mm (1.9 to 4.5 inches). The assembly adjusts to ±25� fine elevation and ±180� (±10� fine) azimuth. Use the approximate mounting dimensions in Figure 2-5 to determine installation require-ments.

A

+

Dim B

Dim C

Dim C

Dim D

Dim F

ODU

AGC ACCESS AREA

ODU CABLE WORKING AREA

NOTES: 1.

2.

3.

ANT POLE MOUNTING DETAILS VARY.

ODU CAN MOUNT ON EITHER SIDE OF POLE.

DIMENSIONS ARE APPROXIMATE.

ODU DIMENSIONS (mm)

1 ft (.3m) 398 289 278 110 220 422 ft (.6m) 651 410 292 110 220 422.5 ft (.8m) 889 622 301 153 338 NA4 ft (1.2m) 1248 904 414 538 1074 NA

DIM A DIM B DIM C DIM D DIM E DIM FAntenna

Figure 2-5. Single ODU Mounting Dimensions

Installation


Use the following steps to attach the mounting assembly to a pole.

Attaching the Antenna to the Mounting AssemblyStep 1: Remove the lower drain plug(s) from the reflector, and then

attach the radome to the reflector using the included pan-head screws, lock-washers, and flat washers. Position the radome drain hole at the bottom.

Step 2: Coat the threads of the socket-head screws on the antenna mounting plate with the included anti-seize compound (Loctite).

Step 1: Attach the mounting bracket around the pipe for left (below) or right offset.

Step 2: Secure the mounting assembly with included flat washers, lock washers, and bolts.

Step 3: Move the hardware around the pipe so the antenna faces the final azimuth direction. Tighten after antenna alignment is complete.

Installing the ODU


Step 3: Align and secure the antenna to the mounting assembly with the socket-head screws. The hardware kit includes an allen key that fits the mounting screws.

Step 4: Apply the silicone grease to the included antenna feed o-ring. Install the o-ring on the antenna feed assembly.

Attaching the RF Unit to the Antenna

The antenna has a feed assembly that couples the non-protected RF unit directly to the antenna. Install the RF unit after properly installing the an-tenna feed o-ring. Set horizontal or vertical polarization by changing RF unit orientation relative to the fixed position of the antenna. 13- and 15-GHz units have a transition assembly that must also turn to change polarization.

Step 1: Observe the V label on the RF unit housing. The V label must point up for vertical polarization.

Step 2: Remove the polyester tape covering the antenna feed assembly and carefully fit the RF unit to the antenna. Gently press into place.

Step 3: Secure the RF unit to the mounting assembly using the four snap fasteners (latches).

Installation


Connecting the Coaxial Cable to the ODU

WARNING DO NOT WORK IN FRONT OF AN ENERGIZED ODU!The power-density level at the open end of any RF-Unit output when transmitting exceeds the level recommended by ANSI/IEEE C95.1-1992.

Step 1: Attach the coaxial cable(s) to the ODU. Step 2: Weatherproof all connections using amalgamating tape for

weatherproofing as described on page 2-5.

Step 3: Connect a 6-AWG copper wire (not supplied) from the ODU grounding post to a ground point on the tower. This grounding cable places the ODU at the same electrical potential as the mounting pipe.

Step 4: Before leaving the site, check that all hardware on the mount, shroud, radome and ODU are secure. Visually inspect the antenna and ODU once a year.


Chapter 3Commissioning

This chapter includes procedures to align and setup the Proteus AMT L-Series radio for operation after physical installation in Chapter 2. Use this material to configure your radio and start traffic as soon as possible.

The radio link normally ships with the ability to pass traffic between ter-minals once installed, powered, and properly aligned. If not tailored to your specific requirements, configure the radio as the sections following ODU alignment (page 3-4) detail.

After installing hardware as Chapter 2 describes, commission the radio by:

• applying power• checking configuration• aligning the link• making configuration changes (if necessary)• verifying operation

Powering the RadioAfter installation and prior to applying power, verify that:

Power circuits must handle in-rush current as the Installation chapter (page 2-10) describes.

• no shorts exist between ground and the pins using an ohm-meter • all connectors are secure• DC connections including ground are wired as Chapter 2 describes

Turn on power to the IDU. If nothing happens, verify the supply voltage at the connector with a voltmeter.

Under normal conditions the power LED lights, the IDU boots, and as the radio attempts to synchronize the alarm indicators turn on and off. If the course antenna alignment completed during ODU installation is good enough, the radio will pass traffic.

After verifying radio settings complete the antenna alignment.

Commissioning


Verifying Radio ConfigurationConnect a computer to the local access port using a serial cable, start the CTI or Element Manager (EM), and open the Configuration menu (shown below).

The radio is set to your specifications as ordered. Document your config-uration settings on the next page.

Once you configure your radio backup the configuration to file using BACKUP CONFIGURATION from the EM File menu.

CAUTION: If you reset the configuration of the far-end radio to factory defaults, or if you connect through the WAN and reset factory defaults, you lose communication (TX Mute) and all parameters show '?'. You can only disable TX Mute from the local radio.

--------------------------------------------------Configuration Menu 1. IDU 2. ODU 3. Payload / Modulation 4. IP 5. Alarms 6. Reset to factory Settings 0. ExitRadio A, No Alarms, Link Up > 2

Verifying Radio Configuration


Element Manager Configuration Craft Terminal ConfigurationIDU IDURadio Name: Radio NameRadio Location: InventoryRadio Contact: License KeyDate/Time: Admin Password mni (case sensitive)License Key: Guest Password none (press Enter)Admin Password: mni (case sensitive) Set ClockGuest Password: none (press Enter) Craft Port RateCraft Baud Rate: NMS Speed

NMS Mode (in/out of band)ODU ODUTransmit Freq Min (MHz) ODU InfoTransmit Freq Max (MHz) TX Frequency (MHz)Transmit Freq (MHz) RX Frequency (MHz)Receive Freq (MHz) TX Power (min:-4,

max:20)Band (GHz)Sub-Band APC ModeTransmit High/Low RSL Setpoint [dBm]Transmit Power (dBm)(ATPC Maximum)

ODU Mute StatePAYLOAD

Transmit Power Min (dBm) E1 ConfigurationTransmit Power Max (dBm) 100 BaseT Configuration

ATPC Enable Channel Bandwidth ATPC RSL Setpoint Current State Transmit Mute State IP CONFIGURATION*Tx Mute Timeout (sec) LAN Interface

AddressPAYLOADInstalled Mask

Bandwidth Routing ConfigLIM A Type WAN Interface

AddressLIM B TypeCurrent Mask

Modulation RoutingBandwidth Routing Table

AddLIM A TypeLIM B Type Delete

Proposed ChangeBandwidth ALARMSLIM A Type Major Alarm SummaryLIM B Type Minor Alarm Summary

LIM A TRIBUTARIES IP-over-air Channel FailInstalled Type Terminal-to-Terminal

Channel FailConfigured TypeEquipped Far End Terminal FailureLIM B TRIBUTARIES Primary Power Supply

FailureInstalled TypeConfigured Type Secondary Power

Supply FailureEquipped IP ADDRESSES* IF Board PLL LockLAN Configuration Equipment MismatchWAN Configuration Configuration FailDefault Gateway Set all to defaultTFTP ServerTrap ModeALARMSAlarm Table

Commissioning


* If IP addresses are not set at the factory, default addresses are: LAN Address: 172.10.111.121LAN Mask: 255.255.0.0LAN Routing Config: NoneWAN Address: 172.111.127.1WAN Mask: 255.255.255.252WAN Routing Config: NoneTFTP Address: 172.10.111.111TFTP File Name: LC_App.mnz

NOTE: Set radio IP addresses properly for the terminal-to-terminal management channel and MNI protection routing to work. See Appendix D for routing.

The factory configures the ODU based on customer specification. If not, set using EM as follows:

• Open Configuration and select ODU• Enter the transmit frequency in MHz for the addressed radio. The

radio automatically sets receive frequency.• Set maximum transmit power and ATPC (automatic transmit power

control)• Click Apply to set changes and continue working or OK to set

changes and exit

Aligning the ODUProper antenna alignment is required for reliable operation of a terrestrial microwave system. Since RF units mount on the antennas, the entire out-door unit (ODU) moves during alignment.

A terrestrial microwave radio needs clear line-of-sight to its correspond-ing far-end terminal to operate. Correct alignment ensures highest possi-ble performance—maximum power and minimum interference—of the microwave signal.

Course ODU Alignment

This procedure should have been done after ODU installation, however this section repeats the steps for convenience.

WARNING DO NOT WORK IN FRONT OF AN ENERGIZED ODU!The power-density level at the open end of any RF-Unit output when transmitting exceeds the level recommended by American National Standards Institute (ANSI) C95.1-1992.

Aligning the ODU


Pre-align ODU azimuth, horizontal reference, by pointing the unit to-ward the far-end unit as closely as possible.

1. Loosen the U-bolts that secure the unit to allow deliberate movement of the ODU around the mast.

2. Rotate the ODU to the estimated bearing using a compass and binoculars.

3. Tighten the U-bolts.

To pre-align elevation, vertical reference, by pointing the unit either up or down to the approximate position.

1. Loosen the clamping bolts and center bolt.2. Move the antenna to the estimated vertical angle.3. Tighten the clamping and center bolts.

The antenna is now coarsely adjusted in both elevation and azimuth. With the radio powered, you may now notice that you can pass traffic across the link. Complete the antenna alignment by doing the following fine alignment.

Fine ODU Alignment

This adjustment is best done by first establishing the path with ODUs coarsely adjusted in both elevation and azimuth. A co-worker should ob-serve RSL on the IDU at the far-end of the link. The near- and far-end sites should be able to communicate to complete the procedure.

Alignment Procedure

1. At the transmit ODU, connect a digital multimeter to the test connection using test leads that have a BNC connector at one end. On a protected system, use the test connector on the standby ODU.

2. Pan the ODU in azimuth using the fine azimuth adjustment to locate the main lobe of the microwave signal. Watching the AGC voltage at the receive site for peak signal. The main lobe will have the highest AGC voltage. RSL at the IDU should be close to the figure determined in your path calculation.As Figure 3-1 shows the signal side lobes are typically 15-20 dB down. If the signal peaks below the expected level, you are most likely reading a side lobe or have cross polarized the antenna. There are sharp drops in power response between the lobes and broad response at the peaks.

3. After locating the main lobe stop panning at the point of maximum signal strength (highest AGC voltage).

4. Tighten azimuth adjustment nuts just enough to prevent the ODU from moving.

Commissioning


5. Pan the ODU in elevation and stop at the point of maximum signal strength (highest AGC voltage).

6. Tighten the fine elevation adjustment just enough to prevent the ODU from moving.

7. As the radio nears the maximum signal strength, use both adjustments to play one against the other. Align both antennas in two planes, elevation and azimuth, to get the optimum signal strength.

8. Once the azimuth and elevation adjustment is optimal, tighten the U-bolts on the pole to secure the entire assembly. Tighten each of the nuts equally in repetitive steps until all are secure to help prevent the antenna from moving its position during tightening. Monitor AGC during the process to ensure that the ODU does not move.

At the completion of this adjustment, the RSL voltage level should be as predicted by your path budget calculation.

If the level is lower than predicted, identify and fix the discrepancy. These include: checking the path for line-of-sight and proper fresnel1 clearances, recalculating the path parameters and checking transmit power. Also, verify antenna polarization and alignment.

1 The area around the visual line-of-sight that radio waves spread out into after they leave the antenna. This area must be clear or signal strength weakens.

Figure 3-1. Typical Antenna Side Lobes

Making Configuration Changes



Configuring the ODU

Normally, MNI configures and tests each ODU at frequencies the cus-tomer order. If a link requires changes to ODU operating frequency use the radio management application from local access port. Configuration changes require administrative-level access.

NOTE: RF unit synthesizers tune to frequencies throughout the half band (low/high) of the channel plan, but unit tuning is limited to the bandwidth of its diplexer. Diplexer replacement is a factory-level procedure, so tuning past the bandwidth of a diplexer requires upgrading or replacing the RF unit. Contact Customer Service for details.

Setting Transmit and Receive Frequency

You can set transmit radio frequency at the local site only as follows:

1. Open Configuration from the main menu2. Select ODU3. Enter the transmit frequency for the NE radio. The IDU automatically

sets receive frequency.

Note: Frequency accuracy is guaranteed when you set transmit frequency in 250-kHz steps, or in 529.464-kHz steps for 8-GHz units with 311.32 T/R, per the ITU F.386 channel plan. Deviating from this can cause transmit-frequency accuracy errors beyond stated accuracy and stability specifications.

4. Click Apply to set changes and continue working on the screen5. Click OK to set changes and exit

Setting Transmit Power Output

Change the ODU output power when necessary as follows:

1. Open Configuration from the main menu2. Select ODU3. Enter the transmit power (ATPC maximum) in dBm 4. Click Apply to set changes and continue working5. Click OK to set changes and exit

Commissioning


Configuring the IDUAny configuration change requires Admin-level access.

Indoor units are set and tested at the capacity stated on your purchase or-der. Use CTI or Element Manager (EM) to configure your IDU.

Setting CapacityThe radio capacity and line type is limited to the configuration you order, but you can purchase a software key to increase capacity.

The IF board matches radio bandwidth to radio capacity: 3.5-, 7-, 14-, and 28-MHz bandwidth for ITU channel plans, and 5, 10, 20, 25 MHz for FCC channel plans. On early-model IDUs you may need to change the IF board to increase radio capacity (see Chapter 5, "Replace the IF Board").

Setting TributariesTo set line types in EM or CTI:

1. Open Configuration from the main menu

2. Select PAYLOAD

3. Configure your proposed line type. Near- and far-end radios configure together. For example, the IDU reads that an 8E1 as the 'installed type', but you may want to temporarily use the radio as a 4E1; your 'proposed type.

4. In EM click APPLY to set changes

LIM refers to the line interface in Element Manager.

5. From the Payload menu of CTI select TRIBUTARY CONFIGURATION, or from EM select LIM A/B1 TRIBUTARIES, to set individual lines to equipped or unequipped. The IDU monitors equipped channels for loss of signal (LOS) while unequipped channels pass traffic without monitor.

NOTE: Set disconnected lines to unequipped to prevent LOS alarms for those lines from filling the alarm log.

6. In EM click APPLY to set changes and continue working, or click OK to set changes and exit

1 LIM B is the Ethernet interface.



Setting NMS ModeTo set NMS mode using CTI to:

• In-Band—in the Ethernet payload• Out-of-Band—in the separate 64-kbps NMS channel

1. Select CONFIGURATION, IDU (and either near-end, or far-end) from the main menu

2. Select NMS PORT MODE

3. Set port to OUT OF BAND or IN BAND

NOTE: When setting NMS to in-band mode remove external connections between NMS and 10/100BaseT Ethernet ports. CTI configuration connects the ports internally, and an external connection will causes network collisions.

4. Exit CTI.

--------------------------------------------------

Near End IDU Configuration Menu

1. Radio Name [Radio A]

2. Inventory

3. License Key [g999-gBQb-MSJF]

4. Admin Password

5. Guest Password

6. Set Clock [2006-6-12,14:51:58]

7. NMS Port Line Speed [Auto-Negotiate/Auto-Negotiate]

8. NMS Port Mode [Out-of-band]

0. Exit

Radio A, No Alarms, Link Up > 8

--------------------------------------------------

Near End NMS Mode Configuration

1. Out-of-band

2. In-band

0. exit

Radio A, No Alarms, Link Up >

Commissioning


Verifying Radio Operation

Verifying operation involves checking alarm conditions and radio per-formance. Alarm conditions show alarms on individual radios and traffic affecting conditions.

To get a quick summary of alarm conditions check the status-bar on EM for alarm indications.

• Green indicators show normal operation• Red indicators show alarm or degraded condition

To monitor individual alarm indications:

1. Open Status from the main menu2. Select NE Alarms to view the local radio alarm indications. Select FE

Alarms to review alarm indications of radio across the link• Green indicators show normal operation• Red indicators show alarm or degraded condition

Measuring performance in a digital communications system can be done by transmitting pseudorandom data sequences through a channel and rec-ognizing bit errors at the receive end. To start the bit error rate test (BERT) and monitor performance use EM as follows:

1. Open Test2. Select BERT3. Select the appropriate tabs for aggregate or individual line interfaces.

Un-selected tributaries operate normally during channel tests. Aggregate is a bit-error rate test on the near-end aggregate channel. Tributary testing is disabled in aggregate mode

4. Click Apply to set changes and continue working

The BERT dialog displays the bit error rate, or check the G.826 statistics of the Performance window.


Chapter 4Operation

Introduction

This chapter focuses on operation in the transmit direction since receive functions are opposite.

Basic Operation

The Proteus AMT L-Series radio connects distant points in a communica-tion network by converting input data to a radio frequency (RF) signal that can be carried at microwave frequencies. Figure 4-1 shows the radio transmits its signal from one radio (near end) to a matched radio at an-other location within line of sight (far end). The connection between two radios is called a microwave link or hop. The far-end radio converts the RF signal back to its original form.

ODUIDUDataLines

ODU IDU DataLines

Figure 4-1. Simplified Radio Link Diagram

Operation


Indoor Unit (IDU)

The IDU processes signals between terrestrial networks and the micro-wave radio link. Signal transport is bi-directional and separated into transmit and receive functions. The IDU also provides overhead chan-nels that manage the radio and permit radio maintenance.

In the transmit direction (Figure 4-2) the IDU accepts customer line data and multiplexes in overhead and management channels. To improve ra-dio threshold the IDU adds forward error correction (FEC) bits. The mul-tiplexed signal goes to the MODEM that modulates a QPSK, or 8PSK, signal. The IF processor filters the signal and generates a modulated 350-MHz IF that goes to the transmitter in the ODU.

In the receive direction (Figure 4-2) a 140-MHz IF from the receiver in ODU goes to an IF processor that filters and down-converts the signal to baseband. The demodulator converts the signal from QPSK, or 8PSK, to a digital signal for the demultiplexer. Demultiplexed signals separate into their original form for output at the customer line inteface.

Figure 4-2. IDU Functional Block Diagram

IDU

NMSConnector

MgmtSerial

PowerSupply

MgmtChannels

Control/MgmtProcessor

Command/Telemetry

TX MUX

Decoder/DEMOD

Encoder/MOD

AGCDetect

IF Board

Cable/MUX& AGC

DB78I/O

Connector

EthernetI/O

Connector

RX DEMUX

PR

OC

ES

SO

R B

US

ODU DC POWER

PROCESSOR BUS

RX

BU

S

TX B

US

RX BUS

RX BUS

TX BUS

PROCESSOR BUS

TX BUS

Indoor Unit (IDU)


The multiplexer is software accepts PDH only (E1 or DS1), Ethernet only or a combination of PDH and Ethernet. Likewise, software config-ures the modem to generate modulated signals in different bandwidths (3.5 MHz to 28 MHz) and different modulations (QPSK, 8PSK).

In addition to the line data, two overhead channels provision radio man-agement and operation. The first is the IP Over-the-Air (IPOA) channel, which is a 64-kbps channel that transports radio SNMP-based network management traffic across the hop. This is a standard IP channel and can alternately transport SNMP packets from outboard hardware over the ra-dio. The second channel is a 9600-baud terminal-to-terminal channel that provides direct communication between the two radio terminals in a link. This channel ensures that the two terminals maintain communication any time there is a valid radio link and allows link management even if the IPOA channel is improperly configured.

The total tributary plus management channel data rates across the radio link are within the available configured capacity. In the case of Ethernet, optional flow control capability is used to minimize packet loss when-ever the IDU detects excessive instantaneous data rate demand. Al-though flow control increases packet-transmission success it does not eliminate packet loss. The radio uses its end-to-end protocol to retrans-mit any dropped packets.

Line Interface

Each line (Figure 4-3) communicates to the mainboard through FIFOs that provide asynchronous operation. The mainboard controls read data from the TX FIFO.

Remote loopback of Ethernet data only works with broadcast packets.

Tributary loopback occurs at the line interface. Because Ethernet is a routing protocol, remote Ethernet loopback only supports broadcast packets.

Signal Multiplexing

The multiplexer, Figure 4-4, addresses the line interface FIFOs through transmit and receive buses using transaction-start pulses. All reads or

Tx FIFO-n

Rx FIFO-n

Tx Bus

Rx Bus

IDU Front PanelLine Connector

TransformersLine

Interface

To Mainboard

Figure 4-3. Line Interface Functions

Operation


writes for the respective bus go through an addressed FIFO until the mainboard asserts a new address.

Transmit and receive buses operate independently. When a transmit FIFO empties before the allocated frame slot fills, the line interface breaks the valid-data signal and the multiplexer inserts stuff-data. For the receive direction, the multiplexer discards stuff-data and parity words from the far-end are not written to the receive FIFO.

The radio carries two management channels over the link: a 64 kbps IP-over-the-air (IPOA), and a terminal-to-terminal channel at 9.6 kbps (Figure 4-4). The terminal-to-terminal channel operates even if the TCP/IP stack or other higher-layer services are unavailable.

Data from the overhead management channels get multiplexed into the radio link in the same fashion by the mainboard via the overhead channel interface as Figure 4-4 shows.

The radio management channels provides the terminal-to-terminal com-munications, such as commands and status, and are always on.

To the MODEM, overhead channels work the same as line tributaries. Data is pulled or pushed by the multiplexer function from individual channel interfaces.

Ethernet Bridge Multiplex

E1/DS1 LIU

Term-Term CH.(9.6 kbps)

IPOA CH.(64 kbps)

ManagementChannels

Overhead

Channel

Interface

Rx Bus

Tx Bus

Buffer/ControlInterface

VHDL

VHDL

Buffer/ControlInterface

LineBuffer

LineBuffer

Figure 4-4. Multiplexing Data Lines and Overhead Channels

Indoor Unit (IDU)


Modulation and Coding

To accommodate data rates efficiently, the MODEM can be configured into 8PSK or QPSK modulation and FEC coding configurations that sat-isfy the capacities and occupied bandwidths. Forward error correction (FEC) provides further flexibility in transport capacity and link margin.

Prior to encoding, the data is in a frame format that can be configured as an integer number of code words. The frame includes a frame count for scrambling and de-scrambling. Data and stuff slots for each transport and overhead channel get transported in the order read from the line and overhead channels.

Stuff slots let the radio link and line interfaces transmit asynchronously –intermittently rather than in a steady stream. A data unit that represents the stuff counts of each line or overhead channel as well as frame stuff counts get inserted into the frame. Stuff counts and redundancy checks are used to detect frame transmission errors.

Aggregate loopback is a digital loop of the modem. Input from the line interface and multiplexer connect to the demultiplexer for output to the line tributaries.

IF Conversion and Multiplexing

The IF board connects to the main board to interface signals between IDU and ODU. IF bandwidth matches customer data rate requirements (see Chapter 1, "IDU Circuit Boards").

The transmit IF function receives a 100-ohm differential signal that is the 40-MHz output from the modem DAC. This signal is up converted to 350 MHz, filtered, amplified and sent to the multiplexer/demultiplexer.

The multiplexer isolates the five bands of signals passing between the ODU and IDU: DC, up- and down-link telemetry, and up and down IF. The circuit also maintains a relatively-low insertion loss and good return loss in all bands of interest.

-48 Vdc powers the ODU. An ASK command telemetry output to the ODU is -15 ±2 dBm centered at 5.5 MHz ±100 kHz. The ASK telemetry path has a combined pass band of 2- to 20 MHz. ODU telemetry (from the ODU) is ≤ 0 dBm and ≥ -20 dBm and centered at 10 MHz ±100 kHz. Total insertion loss for the telemetry path is 10dB at 5.5 MHz and 7.5 dB at 10 MHz.

The IF path gets split between the 350 MHz transmit IF and 140 MHz re-ceive IF. Total insertion loss for the 140 MHz IF is 5 dB, and for the 350 MHz IF path 97 dB.

Operation


The board gets the nominal 140 MHz IF at -10dBm output of the ODU. The receive path has AGC to compensate for the ODU/IDU interconnect cable length. The line loss of this cable at 140 MHz is between 0 and 15 dB. The IF circuit also aids in adjacent channel filtering.

The isolated IF signal from the ODU first gets amplified, filtered at the appropriate bandwidth, slope and speed correction, and is then presented as a differential 100-ohm signal to the modem ADC circuitry.

Outdoor Unit (ODU)


Outdoor Unit (ODU)

The ODU includes an outdoor RF unit, antenna, and mounting hardware. RF unit operation is independent of data rate, bandwidth, and modulation so one ODU accommodates all IDU configurations.

The ODU performs conversions of the intermediate frequencies (IF) from and to the IDU. The transmitter up-converts the 350-MHz IF signal from the IDU to the final radio frequency, and then filters and amplifies the signal that goes to the antenna. The receiver down-converts and fil-ters the radio frequency to a 140-MHz IF signal that goes to the IDU.

This full-duplex operation requires transmit and receive frequency pairs, usually governed by applicable RF standards. Near-end and far-end ODUs operate on opposite TX and RX frequencies. High band RF unit transmits in the upper half-band and receives in the lower half-band. Low band RF unit transmits in the lower half-band and receives in the upper half-band. Tuning range of the RF unit frequencies is the range of the installed diplexer. Independent transmitter and receiver oscillators al-low operations in unique T/R spacings.

Figure 4-5. Outdoor Unit Block Diagram

Operation


Transmitter power output varies with modulation. +25 dBm is typical for QPSK modulation, and +21 dBm is typical for 8PSK modulation. TX output power is variable in 1 dB increments and can be manually set via software control. Minimum power setting is -4dBm output.The ASK telemetry channel communicates commands to the RF unit and alarm and radio identification data to the IDU.

An automatic transmit power control (ATPC) feature keeps the radio’s receive signal level (RSL) constant at the receive site by amplifying or attenuating transmitter power. ATPC function is automatic once RSL threshold and maximum TX power have been set. ATPC maintains the RSL within ±3 dB of the set point by stepping the far-end transmit power in 1 dB steps. Minimum output power is -4 dBm.

The RF unit mounts to the antenna with latches and no tools are required during installation. Replacement of an RF unit does not affect antenna alignment.

Figure 4-6. ODU Duplex Operation

User Interfaces


User Interfaces

Radio management includes both serial and IP-based text and graphic in-terfaces for radio control and supervision by support personnel. Control involves configuration and test while supervision involves monitoring status and performance, radio identification, and inventory.

IP (Internet protocol) and non-IP interfaces are available for the Proteus AMT L-Series radio as Figure 4-7 shows. Radio interfaces connect open-system and proprietary management software to the radio. Soft-ware includes a command line interface (CLI), a text-based menu system called the craft terminal interface (CTI), and the graphical system called Element Manager (EM).

NMS/SNMP (Ethernet)

Two 10/100-BaseT Ethernet ports, labeled NMS1/2, are available on the IDU front panel for out-of-band (64-kbps channel) radio management via simple network management protocol (SNMP). IP messages ad-dressed to the far-end, or other network radios, travel through an IP-over-the-air (IPO-Air), or WAN, channel.

SNMP capability lets commercially-available TCP/IP network manage-ment facilities monitor Proteus AMT L-Series radios in their network. A proprietary Management Information Base (MIB) defines the transmis-sion between a third-party NMS application and the radio.

You can set NMS port speed and duplex settings; auto-negotiate is the default. Change NMS ports independently from Configuration menus. Settings include: Powered Down, Auto-negotiate, 10BaseT Half-duplex,

FRONT PANEL

ENETRepeater ENET ENET

Driver

NMS-1

NMS-2

IP

TCP/UDP

HDLC SERIALDriver

RA

DIO

MA

NA

GEM

ENT

CH

AN

NELS

IPOA Ch(64 kbps)

SERIALDriver

Term-TermProtocol

Term-Term(9.6 kbps)COMPUTER

CLI/CTISERIALDriver CLIUART

RADIO API

Near End Data

Far End Data

TELNET CLI

SNMP

Figure 4-7. User Interface Functions

Operation


10BaseT Full-duplex, 100BaseT Half-duplex, 100BaseT Full-duplex. Port 1 is the top connector and Port 2 the bottom.

When connecting radios back-to-back, auto-sensing (MDI/MDIX) and auto-negotiation handle port configuration.

NOTE: You can configure the Proteus L-Series SNMP-based NMS to IN-BAND MODE so management information travels the same network path as your data. See Setting NMS Mode, page 3-9.

COMPUTER/CTI (Serial)

The craft terminal interface (CTI) is a serial craft interface for local radio management. The local COMPUTER port does not use the SNMP agent or the TCP/IP stack, but also supports a graphical user interface (GUI) for the radio.

Management Software

Both CTI and EM follow a similar software template. Both use similar selections and responses. The difference between the two is how the soft-ware displays radio data. Figure 4-8 outlines the CTI/CLI management software menus and choices and Figure 4-9 outline the EM menus and selections.

NOTE: Since management software works with both Proteus AMT and Proteus AMT L-Series radios, line interface displays indicate LIM for Line Interface Modules as on the AMT.

User Interfaces


Exit

is a

lway

s se

lect

ion

#0

1.

Agg

rega

te

Loca

l Lo

opba

ckR

adio

sel

ect

1. A

gg L

ocal

Loo

pbac

k2.

Agg

Loo

pbac

k Ti

me

2. A

ggre

gate

BER

Tes

tR

adio

sel

ect

Cle

ar A

ll Ag

g BE

R R

esul

ts1.

Agg

BER

Tes

t Mod

e2.

Agg

BER

Tes

t Res

ults

3. C

lear

Agg

BER

Res

ults

3.

Trib

utar

y Lo

opba

ckR

adio

sel

ect

1. T

rib L

ocal

Loo

pbac

k2.

Trib

Rem

ote

Loop

back

4. T

ribut

ary

BER

Tes

tR

adio

sel

ect

1. T

rib B

ER T

est M

ode

2. T

rib B

ER T

est R

esul

ts3.

Cle

ar T

rib R

esul

ts5.

OD

U M

ute

Rad

io s

elec

t1.

Odu

Mut

e St

ate

2. O

du M

ute

Tim

e

Rad

io s

elec

tion

in N

Pis

:

1.

Nea

r End

(Lo

cal)

2

. Fa

r En

d

0.

Exit

1. ID

UR

adio

sel

ect

1. R

adio

Nam

e2.

Inv

ento

ry3.

Lic

ense

Key

4. A

dmin

Pas

swor

d5.

Gue

st P

assw

ord

6. S

et C

lock

7. C

raft

Port

Rat

e8.

NM

S Sp

eed

9. N

MS

Mod

e2.

OD

U Rad

io s

elec

t /w

info

1. O

DU

Info

2. T

X Fr

eque

ncy

3. R

X Fr

eque

ncy

4. T

X Po

wer

5. A

PC M

ode

6. R

SL S

etpo

int

7. O

DU

Mut

e St

ate

3. P

aylo

ad /

Mod

ulat

ion

Rad

io s

elec

t /w

info

1. E

1 C

onfig

urat

ion

2.

100B

aseT

Con

figur

atio

n3.

Cha

nnel

Ban

dwid

th4.

Cur

rent

Sta

teC

onfig

ure

Mod

em4.

IPR

adio

sel

ect

/w in

fo1.

LAN

Intf

(add

ress

)

1. L

AN IP

Add

ress

2.

LAN

IP M

ask

3

. LAN

Rou

ting

Con

fig2.

WAN

Inte

rface

1.

WAN

IP A

ddre

ss

2. W

AN IP

Mas

k

3. W

AN R

outin

g C

onfig

3. R

outin

g Ta

ble

(dis

play

s)

1. A

dd R

oute

2

. Del

ete

Rou

te

3. C

hang

e D

efau

ltR

oute

5.

Ala

rms

(map

ping

)R

adio

sel

ect

1. M

ajr A

larm

Sum

2. M

inor

Ala

rm S

umm

ary

3. IP

-ove

r-ai

r C

hann

el F

ail

4. …

11. M

ore…

12.

Set

all

to d

efau

lt6.

Res

et

to F

acto

ry

Sett

ings

Ala

rms

Perf

orm

ance

Util

ities

Test

Con

figur

atio

n

1.

Cur

rent

A

larm

sR

adio

sel

ect

2.

Latc

hed

Ala

rms

Rad

io s

elec

t3.

Ala

rm L

ogR

adio

sel

ect

1. S

how

Log

2. R

eset

Log

4. C

hang

e Lo

gR

adio

sel

ect

1. S

how

Log

2. R

eset

Log

Cle

ar

all

latc

hed

alar

ms

Rad

io

Sele

ct1.

Las

t Se

cond

2. L

ast

Min

ute

3. L

ast

Hou

r4.

Las

t D

ay6.

La

st W

eek

Elap

sed

Sec.

Avai

labl

e Se

c.Er

rore

d Se

c.Se

vere

ly E

rror

ed S

ec.

Bit E

rror

Rat

e(C

trl-C

to E

xit)

6. A

ll St

atis

tics

Elap

sed

Sec.

Avai

labl

e Se

c.U

nava

ilabl

e Se

c.Er

rore

d Se

c.:

Seve

rely

Err

ored

Sec

.Er

rore

d Se

c. R

atio

Sev

Erro

red

Sec.

Rat

ioTo

tal

Cod

ewor

dsBi

t Err

or R

ate

Back

Bit

Erro

r Rat

eC

urre

nt R

SLFa

de M

argi

nTr

ansm

it Po

wer

(Ctrl

-C to

exit)

7. H

isto

ry1.

Dat

a C

olle

ctio

nEn

able

2. D

ata

Col

lect

ion

Inte

rval

3. C

olle

cted

Var

iabl

es4.

Upl

oad

File

nam

e5.

Upl

oad

Inte

rval

6. S

tora

ge I

nfo

7. S

how

His

tory

8. R

eque

st M

anua

lU

ploa

d9.

Cle

ar H

isto

ry8.

R

eset

Sta

ts

1. D

ownl

oad

File

sR

adio

sel

ect

1

. Be

gin

Dow

nloa

d

2. F

lash

Des

tinat

ion

[NA]

3

. TFT

P Fi

le N

ame

[lc_a

pp.m

nz]

4. T

FTP

Serv

er A

ddre

ss2.

Cop

y Im

age

(Sec

onda

ry

toPr

imar

y)3.

Cop

y Im

age

(Prim

ary

to

Seco

ndar

y)4.

Sy

nchr

oniz

e Se

cond

ary

Imag

es5.

Reb

oot

To P

rimar

y Im

age

Rad

io s

elec

tAl

l Rad

ios

7. R

eboo

t To

Sec

onda

ry I

mag

eR

adio

sel

ect

All R

adio

s

Rad

io s

elec

tion

in H

SB i

s:

1.

Nea

r En

d Pr

imar

y

2.

Far

End

Prim

ary

3.

Nea

r En

d Se

cond

ary

(Loc

al)

4.

Far

End

Seco

ndar

y

0.

Exit

Prot

eus

CTI

/CLI

Rad

io M

anag

emen

t Sof

twar

e

RED

-

traf

fic a

ffec

ting

sele

ctio

n

Firm

war

e up

date

re

quire

sre

boot

, w

hich

doe

s no

t af

fect

traf

fic

on

L-Se

ries

radi

os.

Figure 4-8. Craft Terminal Interface Radio Management Software Outline

Operation


Ala

rms N

E/F

ETe

st S

ettin

gsN

E/F

EEv

ent L

ogA

larm

& E

vent

sw

/ sav

e to

file

feat

ure

IDU

Rad

io n

ame

& lo

catio

nC

onta

ctD

ate/

Tim

eLi

cens

e K

eyA

dmin

Pas

swor

dG

uest

Pas

swor

dC

raft

port

baud

rate

OD

UTX

Fre

quen

cyTX

Pow

erA

TPC

mod

eR

SL

set p

oint

TX m

ute

& ti

meo

utPA

YLO

AD

Inst

alle

d BW

LIM

A/B

Typ

eC

urre

nt Mod

ulat

ion

BW

LIM

A/B

Typ

eP

ropo

sed

BW

LIM

A/B

Typ

eLI

M A

Trib

utar

ies

Equ

ippe

d/U

nequ

ippe

dE

ncod

ing

LIM

B (1

00B

T)Tr

ibut

ary

Equ

ippe

d/U

nequ

ippe

dIP

Add

ress

esLA

NW

AN

Def

ault

gate

way

TFTP

IPTr

ap M

ode

Sta

tic R

oute

sTr

ap D

esitn

atio

nsA

larm

s Tabl

e (d

ispl

ay)

Edi

t/Map

Res

tore

Def

aults

RF

Stat

istic

sN

E/F

E T

x P

ower

min

/max

/avg

.N

E/F

E R

SL

min

/max

/avg

.Fa

de M

argi

n

G.8

26 S

tatis

tics

NE

/FE

Per

form

ance

(bas

ed o

n G

.826

)

His

tory C

onfig

ure,

(dis

play

and

sav

epe

rform

ance

dat

a)H

isto

rical

Dat

a Ta

ble

Con

nect

Dis

conn

ect

Bac

kup

Con

figur

atio

n

Res

tore

Con

figur

atio

n

Exit

Prot

eus

EM G

raph

ical

Rad

io M

anag

emen

t Sof

twar

e

Stat

usPe

rfor

man

ceU

tility

Rad

io In

foTe

stC

onfig

urat

ion

Inve

ntor

yIm

age

Boo

ted

OD

U S

eria

l/Firm

war

e V

er.

IDU

Ser

ial/F

irmw

are

Ver

.IF

Boa

rd T

ype/

Ser

ial

LIM

A/B

Typ

e an

d S

eria

lFu

ll In

fo T

able

/ S

ave

to F

ile

Link

View On

scre

en ra

dio

grap

hic

of p

erfo

rman

ce a

nd in

vent

ory

OD

U M

ute

TX c

ontro

l and

tim

er

Loop

back

Dig

ital a

ggre

gate

Line

(trib

utar

ies)

BER

T BE

R te

st fo

rag

greg

ate

data

pat

hor

trib

utar

ies

Cop

y Im

age

Sou

rce

Des

tinat

ion

Dow

nloa

d Fi

rmw

are

Reb

oot N

E R

adio

prim

ary

imag

ese

cond

ary

imag

eal

l rad

ios

Reb

oot F

E R

adio

prim

ary

imag

ese

cond

ary

imag

eal

l rad

ios

Res

tore

fact

ory

defa

ults

File

Figure 4-9. Element Manager Radio Management Software Outline


Chapter 5Maintenance

Introduction

Proteus AMT L-Series radios require minimal preventive and corrective maintenance. Checking terminal and link performance periodically and analyzing performance logs help uncover problems that may need atten-tion.

Customer Service Options

Support Contacts

For repair service or technical assistance call 1-888-225-4762 (U.S.) or 1-281-263-6501 (international), or fax 1-281-263-6730. You can also e-mail Technical Services at [email protected].

Repair and Exchange Services

Standard repair turn around is typically 14 calendar days from receipt of module to shipment from Microwave Networks. Emergency exchange is typically one day from receipt of request to shipment. Standard repair and emergency exchange time frames do not necessarily apply to discon-tinued products or frequency-specific modules, assemblies, and radios.

For repair services:

1. Call our Customer Care Center – 1-888-225-4762 (U.S.) or 1-281-263-6501 (international)– for a Return Authorization Number (RA#) prior to shipment of any equipment for repair. The customer care representative can explain charges, if any.

2. Return modules in static-safe material. Pack securely for shipment.



Maintenance


3. Provide the following information to facilitate repair or exchange:• Company name, 'Ship To', and 'Bill To' addresses• Contact name, telephone and FAX number, e-mail address• Radio model and serial number• Module part number, serial number, and description• Description of the problem or damage• Configuration and license key• Operating frequency when applicable

Include the RA number on the inside and on the outside of the package. For out of warranty repairs include a purchase order.

Send your package to:Microwave Networks, Inc. 4000 Greenbriar #100A, Stafford, Texas, 77477 ATTN: Repair/Returns

Technical Support Services

Around-the-clock telephone support is available on all Microwave Net-works products. For telephone support contact 1-888-225-4762 (U.S.) or 1-281-263-6501 (international). You can e-mail Technical Services any-time at [email protected].

Normal hours are 8:00 A.M. to 5:00 P.M., Monday through Friday, U.S. Central Time. After-hour telephone support is available through our dis-patch operators.

Technical Support is guaranteed for current products or products on Ad-ditions and Maintenance (AM) status.

Support for Manufacturing Discontinued (MD) products vary by product age, available material, available spares, etc. Telephone technical support on discontinued products may be subject to a charge depending upon du-ration and nature of assistance.



Maintenance


Maintenance

Changing Payload Configuration

L-Series radios use a universal IDU for all payload, modulation, and bandwidth configurations1. Maximum radio capacity is limited to the ca-pacity and data type license you purchase. You can reconfigure payload to any configuration within your license using the radio application soft-ware.

For example, Table 1-F lists an ETSI radio licensed for PDH plus Ether-net at 28-MHz bandwidth, 8PSK modulation has 50 Mbit/s throughput. This license lets you set the payload to any one of six configurations:

– 16 E1 plus 18.6 Mbit/s Ethernet– 12 E1 plus 26.9 Mbit/s Ethernet– 8 E1 plus 35.1 Mbit/s Ethernet– 4 E1 plus 43.4 Mbit/s Ethernet– 2 E1 plus 47.5 Mbit/s Ethernet– 51.7 Mbit/s Ethernet

CAUTION Changing payload configuration stops all traffic.

1. From the CTI configuration menu select 3. PAYLOAD / MODULATION.

2. The radio select screen displays your "current" configuration.

3. Select and edit the near and far-end radio payload – your "proposed" configuration.

1 Early-model radios have fixed radio capacity and bandwidth. Replace the IF boards in these units as “Replace the IF Board” on Page 5-9 describes.

--------------------------------------------------Configuration Menu 1. IDU 2. ODU 3. Payload / Modulation 4. IP 5. Alarms 6. Reset to factory Settings 0. ExitRadio A, No Alarms, Link Up >

--------------------------------------------------Payload / Modulation 1. Near End (Local) [8 E1 + 100 BaseT @ 28 MHz] 2. Far End [8 E1 + 100 BaseT @ 28 MHz] 3. Configure Modem 0. ExitRadio A, No Alarms, Link Up >

Maintenance


4. Select 4 - CURRENT STATE to review the installed, current, and proposed configuration.

NOTE: "INSTALLED CONFIGURATION" is main-board capability.

5. When complete, exit to the Payload/Modulation screen. Select CONFIGURE MODEM.

When re-configuring the modem, current license capabilities are checked to find a configuration that meets the requested configuration and the li-cense requirements. If a satisfactory configuration is not available, mo-dem configuration fails. If the proposed configuration fails, proposed configuration displays INVALID. See ”Upgrading Payload Capacity and Data Type” on the next page to upgrade your radio license.

--------------------------------------------------Near End Channel Configuration 1. E1 Configuration [8 E1] 2. 100 BaseT Configuration [100 BaseT] 3. Channel Bandwidth [28 MHz] 4. Current State [VALID] 0. ExitRadio A, No Alarms, Link Up >

--------------------------------------------------Installed Configuration: E1 Configuration : 16 E1 100 BaseT Configuration: 100 BaseT Channel Bandwidth : 28 MHz

Current Configuration: E1 Configuration : 8 E1 (16 Mbps) 100 BaseT Configuration: 100 BaseT (34 Mbps) Channel Bandwidth : 28 MHz Modulation Type : 8 PSK

Proposed Configuration: VALID E1 Configuration : 4 E1 100 BaseT Configuration: 100 BaseT Channel Bandwidth : 28 MHz

Maintenance


Upgrading Payload Capacity and Data Type

L-Series radios ship licensed in one of three traffic modes: PDH only, PDH plus Ethernet, and Ethernet only. The license also sets maximum radio capacity and modulation.

Upgrade capacity, data type, or modulation on your radio by upgrading your license key2. Chapter 1 Table 1-F and Table 1-G list all licensed modes. Call Customer Care purchase a license upgrade.

License key is unique to one IDU and identifies your IDU by mainboard serial number.

All license keys are unique to one IDU. The IDU verifies license key to its mainboard serial number. Before upgrading a license key ensure that the upgrade matches the mainboard serial number using the radio the in-ventory screen.

1. Open CTI and log in to the radio

2. Select the near-end Configuration menu.

3. Write down the current license key

4. Select License Key

5. Enter the key code

6. Once set, view enabled capabilities from the inventory. See the previous section ”Changing Payload Configuration” to change the payload configuration.

2 Early-model radios have fixed radio capacity and bandwidth. Replace the IF boards in these units as “Replace the IF Board” on Page 5-9 describes.

Near End IDU Configuration Menu 1. Radio Name [Radio A] 2. Inventory 3. License Key [****-****-****] 4. Admin Password 5. Guest Password 6. Set Clock [2005-10-4,10:08:42] 7. Craft Port Rate [9600] 8. NMS Speed [Auto-Negotiate/Auto-Negotiate] 0. ExitRadio A, No Alarms, Link Up > 3

Enter new value for License Key:

Maintenance


Replacing IDU Fuses and the Backup Battery

IDUs have no user-configuration jumpers and few components to change in the field. You may, however, need to replace a power supply fuse or the main-board backup battery.

Replace the Power Supply Fuse

The cartridge fuses listed below are protect the power supply from light-ning strikes and shorting. The fuse opens only in the case of an excessive surge, a component failure, or a short on the cable to the ODU.

• 48V P/N 3110015-01 2AG-125V, FAST-BLO, 5 AMP• 24V P/N 3110015-02 2AG-125V, FAST-BLO, 7 AMP

An in-line fuse in the DC path to the ODU prevents damage to the IF board if the IDU/ODU cable shorts.

The power supply fuse mounts on a fuse clip in the front of the power supply. To replace the fuse:

1. Turn the IDU off by disconnecting the power cable.

2. If you can reach all screws on the IDU top cover, remove the cover. Otherwise, pull the unit from the rack to remove the top cover.

3. Pull the fuse from its clip on the front of the power supply board using a fuse puller like the one show here.

4. Replace the fuse, restore the unit in the rack, and apply power.

-48V

2A fuseRFI/EMI

Ferrite Bead

SurgeProtector

IDU

To Cable IDU/ODU

Maintenance


Replace the Backup Battery

The Proteus AMT L-Series backup battery (Figure 5-2) has a lifetime rat-ing to match the radio. You should not have to replace the backup bat-tery. However, if the radio fails to keep proper date and time, or fails to save event logs, a low battery may be the cause. IDUs store operating pa-rameters and radio configuration in non-volatile memory.

NOTE: Backup radio configurations to file from the EM File menu.

Please call Customer Service at 281.263.6501, or toll free in the U.S. at 1.888.225.4762, if you believe this battery ever needs replacement.

A lithium-ion battery, P/N 3900388-00, located on main-board, allows the IDU to maintain a real-time clock and critical-event logs when the unit losses power. The battery is 3V, 220 mAH battery; Panasonic CR2032.

WARNING The battery can explode if inserted backwards. Only use the same or equivalent battery. Dispose used batteries according to manufacturer's instructions.

To replace the battery:

1. Turn the radio off by disconnecting the power cable.2. If you can reach all screws on the IDU top cover, remove the cover.

Otherwise, pull the unit from the rack to remove the top cover.3. Remove the old battery from the battery well on the main-board.4. Clean the new battery surfaces to remove dust and oils.5. Insert the new battery into the empty well.6. Replace the cover, restore the unit in the rack, and apply power.

Maintenance


Replacing IDU Depot-Level Components

Replace the Power Supply Board

CAUTION Don an antistatic strap prior to handling. Electrostatic discharge (ESD) can damage the equipment.

The power supply (Figure 5-1) mounts on the left side of the chassis. To replace the power supply:

1. Turn the IDU off by disconnecting the power cable.

2. If you can reach all screws on the IDU top cover, remove the cover. Otherwise, pull the unit from the rack to remove the top cover.

3. Disconnect the power cable assembly from the board. Some cables have an in-line fuse. Do not break wires going to the in-line fuse assembly.

4. Remove the 6 to 9 screws holding the power supply board to the chassis.

5. Replace the board, restore the unit in the rack, and apply power.

Figure 5-1. IDU Power Supply

Maintenance


Replace the IF Board

You may need to perform this procedure on early-model Proteus AMT L-Series radios. Current models use a universal IF board (Table 1-C).

CAUTION Don an antistatic strap prior to handling. Electrostatic discharge (ESD) can damage the equipment.

The IF board-to-mainboard connection is delicate. Use care when removing the IF board.

Early-model radios have a fixed occupied bandwidth. Changing occu-pied bandwidth requires replacing the IF board. Figure 5-2 shows the lo-cation of the boards in the IDU chassis.

To replace the IF board:

1. Turn the radio off and disconnect power and signal cables.

2. Move the IDU to a bench.3. Remove the IDU top cover.4. Disconnect two cables from the IF

board.5. Remove the six Phillips-head screws

that secure the board.6. The board connects to a multi-pin

header on the mainboard–framed top right in the illustration. Carefully lift the board straight up to remove.

7. Reverse these steps to replace the board.

8. Power the radio.9. Using the radio management software, check the IF board ID and

bandwidth. If you switched bandwidth, check that you have a valid line configuration.

Figure 5-2. IF Board in the IDU

IF Board

Main Board BACKUPBATTERY

PowerSupply

Figure 5-3. IF Board

Maintenance


Replacing ODU RF Units

RF units mount directly to the back of the antenna. The housing is circu-lar and made of cast aluminum. It attaches to the antenna with a di-rect-mount fitting and four snap fasteners (latches). So, any RF unit can be removed from the antenna without changing antenna alignment.

Other than the antenna fitting, the RF unit has three external connections: an N-type connector for the IDU/ODU cable, a BNC connector to the AGC test voltage for alignment, and a grounding lug.

RF units are also data rate independent, so the same unit works with any IDU data rate or modulation scheme.

Each RF unit has full-duplex transceiver that transmits on one frequency and receives on a second. Its match, at the far-end of a path, operates on opposite transmit and receive frequencies. Consequently, RF units are re-ferred to as 'LB' or 'HB' heads. LB, low band, units transmit in the lower half-band and receive in the upper half-band, and 'HB', high band, units transmit high and receive low.

The RF unit oscillator tunes to any frequency in its half-band, but the di-plexer has RF channel filters with bandwidths that are not as wide the half-band tuning range. Thus, the tuning range of any RF unit is the range of the diplexer. Replacement heads, if not being used to change to different bands, must match the original configuration.

To replace the RF unit:

1. Remove power from the IDU by disconnecting the power cable. Tag the plug and unit to prevent someone from applying power to the unit while you work at the ODU.

2. At the ODU remove the IDU/ODU cable and ground.Rotate the RF assembly to set vertical- or horizontal polarization as indicated on the RFU cover.

3. Hold the RF unit against the antenna with one hand while opening the snap fasteners that secure the unit to the antenna.

4. Slide the unit away from the antenna and place the unit to the side.5. Slide the replacement into place on the antenna. Use the vertical

label on the housing to orient the head for proper polarization.6. Close the four latches that secure the unit to the antenna.7. Connect ground and the IDU/ODU cable.8. Apply power to the IDU by connecting the power cable.

Maintenance


Updating Firmware with TFTP

Using EM to Update Firmware

Updating application code requires that you reboot the IDU.

Reboot does not affect traffic.

General

Updating the radio firmware is like updating BIOS in a PC. Firmware includes application, boot, and FPGA code or images (Table 5-A).

Download application code to the secondary image location in the IDU. After download, boot from the secondary image to check that the code works, and then copy the image from the secondary to the primary, default boot, location. Maintain the secondary image as a backup. Boot and FPGA images load to individual locations.

Get a free trial version of a TFTP server at www.solarwinds.net

Load the compressed image file (*.mnz) through the Ethernet NMS port using any networked PC running TFTP server software. Configure the TFTP server according to the product instructions.

Download Files and Reboot Radio1. Open Utility 2. Select Download Firmware3. Type the TFTP IP address in the appropriate field4. Select the Flash destination (e.g., Secondary App Firmware)5. Enter the file name (Table 5-A)

CAUTION Image files for use with TFTP are compressed .mnz files. If TFTP download fails, use Bootloader and the uncompressed .hex or .mni files. See “Loading Firmware with Bootloader.

6. Click Begin Download to start7. Continue Step 4 and 5 to download multiple files8. Reboot the radio. If you updated application code, reboot from the

secondary image.9. Check the revision numbers under Radio Info, Inventory. If correct,

copy the code from the secondary to the primary (default boot) image location, and then reboot from the primary.

http://www.solarwinds.net



Maintenance


Using CTI to Update Firmware

Updating the firmware requires that you reboot the IDU. Reboot does not affect traffic.

GeneralFirmware includes application, boot, and FPGA code or images (Table 5-A). Download application code to the secondary image location in the IDU. After download, boot from the secondary image to check that the code works, and then copy the image from the secondary to the pri-mary, default boot, location. Maintain the secondary image as a backup. Boot and FPGA images load to individual locations.

Get a free trial version of a TFTP server at www.solarwinds.net.

Load the compressed image file (*.mnz) through the Ethernet NMS port using any networked PC running TFTP server software.

Download Files and Reboot Radio1. Log in to IDU2. From main menu, select 5-Utilities

3. Select 1-Download Files4. Select a radio to update – NE/FE primary or secondary (protected)

5. Enter the file name (Table 5-A)

CAUTION Image files for use with TFTP are compressed .mnz files. If TFTP download fails, use Bootloader and the uncompressed .hex or .mni files. See “Loading Firmware with Bootloader.

6. Enter the flash destination (e.g., Secondary App Firmware)7. Enter the IP address of your TFTP server8. Select 1 to start download

Utility Menu 1. Download Files 2. Copy Image (Secondary to Primary) 3. Copy Image (Primary to Secondary) 4. Synchronize Secondary Images 5. Reboot To Primary Image 6. Reboot To Secondary Image 0. ExitRadio A, No Alarms, Link Up >

Download Files 1. Near End (Local) 2. Far End 0. ExitRadio A, No Alarms, Link Up >

Near End Download Menu 1. Begin Download 2. Flash Destination [N/A] 3. TFTP File Name [lc_app.mnz] 4. TFTP Server Address [172.16.99.2] 0. ExitRadio A, No Alarms, Link Up >




Maintenance


Progress shows on screen. If progress stops at 2%, check your connect to the TFTP server. The radio IP address must be on the same subnet as the TFTP server, and you must have a good connection.

Reboot does not affect traffic.

If you update the application code, reboot the radio from the secondary image to verify operation. Once verified, copy the image into the pri-mary location. Leave the secondary image as a backup.

From Utility, select Copy Image (Secondary to Primary), and select the radio. When copy completes, re-boot the IDU.

Check firmware version from Configuration, IDU, NE/FE, Inventory.

Loading Firmware with BootloaderCompressed code files (.mnz) do not work with Bootloader.

If a radio boot sequence fails, the Bootloader, shown below, displays that failure and stops. You can load firmware to a problem IDU using Boot-loader and a terminal connected to the IDU serial craft port.

1. Press CTRL+C during the boot sequence to load the bootloader menu.

Bootloader loads files to the IDU only from the local serial port.

2. After you stop the boot, Bootloader selections open.

Table 5-A lists the file names of the image files for use with TFTP and Bootloader.

– Primary/Secondary image — application code– Boot Loader — new Bootloader version– FPGA — E1/DS1 MODEM code

Proteus AMT Bootloader Version 1.2

(c) Microwave Networks, Inc., 2002-2003

Primary Application Image CRC...Passed

Secondary Application Image CRC...Passed

Press 'CTRL-C' within 2 seconds to stop boot

Booting Primary Image

Loading Application Code...

Starting Application Code...

1. Force boot of primary image

2. Force boot of secondary image

3. Download new primary image and reboot

4. Download new secondary image and reboot

5. Download new boot loader and reboot

6. Download new FPGA image 1 and reboot



9. Change CRAFT port baud rate and reboot

0. Exit

Maintenance


FPGA images based on radio bandwidth options are separate image files as Table 5-A shows.

Serial load of the uncompressed image files is slow.

3. Set the craft port baud rate to the highest rate of the connected serial terminal.

4. Select the destination (e.g., 4. Download new secondary image and reboot)

NOTE: FPGA (modem) image location to recover in Bootloader allows you to recover from failure. One image location is enough to restore the NMS port. Use TFTP with EM or CTI to fully restore.

5. Use your terminal application to start the file transfer. Select transfer - text file on terminal emulation applications.

Boodloader shows file transfer progress. Be patient, this will take some time!

Table 5-A Proteus AMT-L Firmware Files*

*. For current-version IDU on the product CD or from microwavenetworks.com.

File Type P/N TFTP File Bootloader FileBootloader 4600067-01 not applicable LC_Boot.hex

Application Code 4600068-01 LC_App.mnz 4600068-01_1.hex†

4600068-01_2.hex

†. Use either _1 or _2.

7MHz E1 FPGA‡

‡. File name includes revision level shown here as an underscore.

4600071-01 4600071-01_.MNZ 4600071-01_.hex14MHz E1 FPGA 4600072-01 4600072-01_.MNZ 4600072-01_.hex28MHz E1 FPGA 4600073-01 4600073-01_.MNZ 4600073-01_.hex5MHz DS1 FPGA 4600074-01 4600074-01_.MNZ 4600074-01_.hex10MHz DS1 FPGA 4600075-01 4600075-01_.MNZ 4600075-01_.hex25MHz DS1 FPGA 4600076-01 4600076-01_.MNZ 4600076-01_.hex2.5MHz DS1 FPGA 4600079-01 4600079-01_.MNZ 4600079-01_.hex3.5MHz E1 FPGA 4600080-01 4600080-01_.MNZ 4600080-01_.hex

1. Force boot of primary image

2. Force boot of secondary image

3. Download new primary image and reboot

4. Download new secondary image and reboot

5. Download new boot loader and reboot




9. Change CRAFT port baud rate and reboot

0. Exit

Your Selection: 4

Please send the file over the serial port

(you may have to press 'CTRL-Z' when the file download completes)


Maintenance Checks


Maintenance Checks

Periodic Maintenance

The Proteus AMT L-Series radio requires only periodic inspections to isolate potential problems and ensure trouble-free operation.

Monthly Checks

Use one of the user interfaces to check performance and event logs. Con-tinued analysis of the logs over time give a good general indication of ra-dio performance.

The RSL display only reads up to -90 dBm, and does not accurately measure RSL for radios operating beyond-90 dBm.

Verify RSL (receive signal strength). Low RSL, or AGC voltage, that stays low can mean antenna misalignment, RF path obstruction, decrease in transmitter power, or a reduction in receiver sensitivity. Ignore minor random variations caused by weather and temperature changes since they can cause day-to-day variation.

Semi-Annual Checks

Visually inspect the ODU. Pay particular attention to the IDU/ODU ca-ble. Look for signs of rubbing, chafing, or cracks. Check weatherproof-ing for deterioration. Remove any old weatherproofing and check con-nectors for damage. Clean and re-seal ODU connectors.

Annual Checks

Check transmitter parameters at least annually (or more often if required by your regulatory agency). Follow regulatory agency guidelines to check the transmitter. Typical parameters to be measured are carrier fre-quency, output power, and modulation characteristics.

Maintenance


Proteus AMT L-Series Manual Page A-1

Appendix AFrequency Tables

Overview

This appendix lists the frequency range and channel plan for each RF unit. RF units are full-duplex that is–they transmit on one frequency and receive on a second. Complement units at opposite-ends of links operate at counterpart transmit and receive frequencies. Consequently, RF units are referred to as 'LB' or 'HB' units. LB low band units transmit in the lower half-band and receive in the upper half-band, and 'HB' high band units transmit high and receive low.

RF unit synthesizers cover the entire half-band of the frequency plan. However, the tuning range of any RF unit is the range of its diplexer. Tuning past the diplexer range requires replacing the diplexer. Diplexer replacement is a factory-level procedure for which you must contact Mi-crowave Networks’ Customer Service.

Frequency and Channel Plans

This section includes the frequencies and channel plans for RF units that operate at 140-MHz IF input and 350-MHz IF output. Table A-A on page A-2 lists each frequency table.

Frequency Tables

Page A-2 Proteus AMT L-Series Manual

Table A-A RF Frequencies and Channel PlansFrequency Range (GHz) T/R Spacing (MHz) Table Page7 GHz 7.12 - 7.9 154

160 161196

A-BA-CA-DA-E

A-3A-3A-4A-5

8 GHz 7.9 - 8.5 119 208 266

311.32

A-FA-GA-HA-I

A-5A-5A-6A-6

11-GHz 10.7 - 11.7 490530

A-JA-K

A-6A-6

13 GHz 12.75 - 13.25 226 A-L A-715 GHz 14.4 - 15.35 315

420475490640644728

A-MA-NA-PA-OA-QA-RA-S

A-7A-8A-8A-8A-8A-9A-9

18 GHz 17.7 - 19.7 10101560

A-TA-U

A-9A-9

23 GHz 21.3 - 23.6 100812001232

A-VA-WA-X

A-10A-10A-10

26 GHz 24.25 - 26.5 8001008

A-YA-Z

A-11A-11

38 GHz 37 - 40 GHz 7001260

A-AAA-AB

A-11A-11



7GHz

*LB-LOW BAND; HB-HIGH BAND


Table A-B 7GHz, 154 MHz T/R Spacing

Sub-Band* ODU P/N TX Lower Limit, MHz

TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-070154-00111-6100 7428 7484 7582 7638HB1 63-070154-10111-6100 7582 7638 7428 7484LB2 63-070154-00211-6100 7470 7526 7624 7680HB2 63-070154-10211-6100 7624 7680 7470 7526LB3 63-070154-00311-6100 7512 7568 7666 7722HB3 63-070154-10311-6100 7666 7722 7820 7876

Table A-C 7GHz, 160 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-070160-00111-6100 7433.5 7496.5 7593.5 7656.5HB1 63-070160-10111-6100 7593.5 7656.5 7433.5 7496.5LB2 63-070160-00211-6100 7478.5 7541.5 7638.5 7701.5HB2 63-070160-10211-6100 7638.5 7701.5 7478.5 7541.5LB3 63-070160-00311-6100 7526 7589 7686 7749HB3 63-070160-10311-6100 7686 7749 7526 7589

Frequency Tables



Table A-D 7GHz 161 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-070161-00111-6100 7114 7177 7275 7338HB1 63-070161-10111-6100 7275 7338 7114 7177LB2 63-070161-00211-6100 7149 7212 7310 7373HB2 63-070161-10211-6100 7310 7373 7149 7212LB3 63-070161-00311-6100 7184 7247 7345 7408HB3 63-070161-10311-6100 7345 7408 7184 7247LB4 63-070161-00411-6100 7219 7282 7380 7443HB4 63-070161-10411-6100 7380 7443 7219 7282LB5 63-070161-00511-6100 7239 7302 7400 7463HB5 63-070161-10511-6100 7400 7463 7239 7302LB6 63-070161-00611-6100 7274 7337 7435 7498HB6 63-070161-10611-6100 7435 7498 7274 7337LB7 63-070161-00711-6100 7309 7372 7470 7533HB7 63-070161-10711-6100 7470 7533 7309 7372LB8 63-070161-00811-6100 7344 7407 7505 7568HB8 63-070161-10811-6100 7505 7568 7344 7407LB9 63-070161-00911-6100 7414 7477 7575 7638HB9 63-070161-10911-6100 7575 7638 7414 7477LB10 63-070161-01011-6100 7449 7512 7610 7673HB10 63-070161-11011-6100 7610 7673 7449 7512LB21 63-070161-02111-6100 7484 7547 7645 7708HB21 63-070161-12111-6100 7645 7708 7484 7547LB22 63-070161-02211-6100 7519 7582 7680 7743HB22 63-070161-12211-6100 7680 7743 7519 7582LB23 63-070161-02311-6100 7539 7602 7700 7763HB23 63-070161-12311-6100 7700 7763 7539 7602LB24 63-070161-02411-6100 7574 7637 7735 7798HB24 63-070161-12411-6100 7735 7798 7574 7637LB25 63-070161-02511-6100 7609 7672 7770 7833HB25 63-070161-12511-6100 7770 7833 7609 7672LB26 63-070161-02611-6100 7644 7707 7805 7868HB26 63-070161-12611-6100 7805 7868 7644 7707




8GHzFor reference; contact MNI about availability.


Table A-E 7GHz 196 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-070196-00111-6100 7093 7149 7289 7345HB1 63-070196-10111-6100 7289 7345 7093 7149LB2 63-070196-00211-6100 7121 7177 7317 7373HB2 63-070196-10211-6100 7317 7373 7121 7177LB3 63-070196-00311-6100 7149 7205 7345 7401HB3 63-070196-10311-6100 7345 7401 7149 7205LB4 63-070196-00411-6100 7177 7233 7373 7429HB4 63-070196-10411-6100 7373 7429 7177 7233LB5 63-070196-00511-6100 7205 7261 7401 7457HB5 63-070196-10511-6100 7401 7457 7205 7261

Table A-F 8GHz 119 MHz T/R Spacing

Sub-Band* ODU P/N† TX Lower Limit, MHz

TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-080119-00111-6100 8279 8307 8398 8426HB1 63-080119-10111-6100 8398 8426 8279 8307LB2 63-080119-00211-6100 8293 8321 8412 8440HB2 63-080119-10211-6100 8412 8440 8293 8321LB3 63-080119-00311-6100 8307 8335 8426 8454HB3 63-080119-10311-6100 8426 8454 8307 8335LB4 63-080119-00411-6100 8321 8349 8440 8468HB4 63-080119-10411-6100 8440 8468 8321 8349LB5 63-080119-00511-6100 8335 8363 8454 8482HB5 63-080119-10511-6100 8454 8482 8335 8363LB6 63-080119-00611-6100 8349 8377 8468 8496HB6 63-080119-10611-6100 8468 8496 8349 8377

* LB-LOW BAND; HB-HIGH BAND

† The same ODUs are used for 119 and 126 MHz T/R spacing

Table A-G 8GHz 208 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-080208-00111-6100 8043 8113 8251 8321HB1 63-080208-10111-6100 8251 8321 8043 8113LB2 63-080208-00211-6100 8099 8169 8307 8377HB2 63-080208-10211-6100 8307 8377 8099 8169LB3 63-080208-00311-6100 8155 8225 8363 8433HB3 63-080208-10311-6100 8363 8433 8155 8225LB4 63-080208-00411-6100 8211 8281 8419 8489HB4 63-080208-10411-6100 8419 8489 8211 8281

Frequency Tables




11 GHz

11 GHz ODU is not available for use with L-Series in the U.S.A. Check with MNI for availability.



Table A-H 8GHz 266 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-080266-00111-6100 7905 8024 8171 8290HB1 63-080266-10111-6100 8171 8290 7905 8024LB2 63-080266-00211-6100 8017 8136 8283 8402HB2 63-080266-10211-6100 8283 8402 8017 8136

Table A-I 8GHz 311.32 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-080311-00111-6100 7731 7867 8042 8178HB1 63-080311-10111-6100 8042 8178 7731 7867LB2 63-080311-00211-6100 7835 7971 8146 8282HB2 63-080311-10211-6100 8146 8282 7835 7971

Table A-J 11GHz 490 MHz T/R Spacing

Sub-Band ODU P/N TX Lower Limit, MHz

TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz


Table A-K 11GHz 530 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz


http://www.microwavenetworks.com/proteus.asp

http://www.microwavenetworks.com/proteus.asp



13GHz

13-GHz ODUs have either rectangular (standard) or circular (optional) antenna interface. The antennas you purchase must matched this inter-face.


15GHz

15-GHz ODUs have a standard rectangular antenna interface or an op-tional circular antenna interface. Antennas that you purchase must match this interface.


Table A-L 13GHz 266 MHz T/R SpacingSub-Band

ODU P/N Rect. Interface

ODU P/N Circ. Interface

TX Lower Limit, MHz

TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-130266-00111-6000 63-130266-00111-6100 12751 12814 13017 13080HB1 63-130266-10111-6000 63-130266-10111-6100 13017 13080 12751 12814LB2 63-130266-00211-6000 63-130266-00211-6100 12807 12870 13073 13136HB2 63-130266-10211-6000 63-130266-10211-6100 13073 13136 12807 12870LB3 63-130266-00311-6000 63-130266-00311-6100 12863 12926 13129 13192HB3 63-130266-10311-6000 63-130266-10311-6100 13129 1392 12863 12926LB4 63-130266-00411-6000 63-130266-00411-6100 12919 12982 13185 13248HB4 63-130266-10411-6000 63-130266-10411-6100 13185 13248 12919 12982

Table A-M 15GHz 315 MHz T/R SpacingSub-Band*

ODU P/NRect. Interface

ODU P/NCirc. Interface

TX Lower Limit, MHz

TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-150315-00111-6000 63-150315-00111-6100 14627 14732 14942 15047HB1 63-150315-10111-6000 63-150315-10111-6100 14942 15047 14627 14732LB2 63-150315-00211-6000 63-150315-00211-6100 14725 14844 15040 15159HB2 63-150315-10211-6000 63-150315-10211-6100 15040 15159 14725 14844LB3 63-150315-00311-6000 63-150315-00311-6100 14823 14928 15138 15243HB3 63-150315-10311-6000 63-150315-10311-6100 15138 15243 14823 14928

Special Purchase

LB4 63-150315-00411-6000 NA 14767 14872 15082 15187HB4 63-150315-10411-6000 NA 15082 15187 14767 14872

Frequency Tables






Table A-N 15GHz 420 MHz T/R SpacingSub-Band*

ODU P/N Rect. Interface

ODU P/N Circ. Interface

TX Lower Limit, MHz

TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz


Table A-O 15GHz 490 MHz T/R SpacingSub-Band*



TX Lower Limit, MHz

TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz


Table A-P 15GHz 475 MHz T/R SpacingSub-Band*



TX Lower Limit, MHz

TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-150475-00111-6000 63-150475-00111-6100 14500 14668 14975 15143HB1 63-150475-10111-6000 63-150475-10111-6100 14975 15143 14500 14668LB2 63-150475-00211-6000 63-150475-00211-6100 14660 14828 15135 15303HB2 63-150475-10211-6000 63-150475-10211-6100 15135 15303 14660 14828LB3 63-150475-00311-6000 63-150475-00311-6100 14715 14883 15190 15358HB3 63-150475-10311-6000 63-150475-10311-6100 15190 15358 14715 14883

Table A-Q 15GHz 640 MHz T/R SpacingSub-Band*



TX Lower Limit, MHz

TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-150640-00111-6000 63-150640-00111-6100 14500 14610 15140 15250HB1 63-150640-10111-6000 63-150640-10111-6100 15140 15250 14500 14610LB2 63-150640-00211-6000 63-150640-00211-6100 14605 14715 15245 15355HB2 63-150640-10211-6000 63-150640-10211-6100 15245 15355 14605 14715





18GHz



Table A-R 15GHz 644 MHz T/R SpacingSub-Band*



TX Lower Limit, MHz

TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-150644-00111-6000 63-150644-00111-6100 14400 14512 15044 15156HB1 63-150644-10111-6000 63-150644-10111-6100 15044 15156 14400 14512LB2 63-150644-00211-6000 63-150644-00211-6100 14498 14610 15142 15254HB2 63-150644-10211-6000 63-150644-10211-6100 15142 15254 14498 14610LB3 63-150644-00311-6000 63-150644-00311-6100 14596 14708 15240 15352HB3 63-150644-10311-6000 63-150644-10311-6100 15240 15352 14596 14708

Table A-S 15GHz 728 MHz T/R SpacingSub-Band



TX Lower Limit, MHz

TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB2 63-150728-00211-6000 63-150728-00211-6100 14500 14615 15228 15343HB2 63-150728-10211-6000 63-150728-10211-6100 15228 15343 14500 14615

Table A-T 18GHz 1010 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz


Table A-U 18GHz 1560 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-181560-00111-6100 17700 18000 19260 19560HB1 63-181560-10111-6100 19260 19560 17700 18000LB2 63-181560-00211-6100 17840 18140 19400 19700HB2 63-181560-10211-6100 19400 19700 17840 18140

Frequency Tables


23GHz




Table A-V 23GHz 1008 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-231008-00111-6100 22000 22314 23008 23322HB1 63-231008-10111-6100 23008 23322 22000 22314LB2 63-231008-00211-6100 22286 22600 23294 23608HB2 63-231008-10211-6100 23294 23608 22286 22600

Table A-W 23GHz 1200 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz


Table A-X 23GHz 1232 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz




26 GHz 140/350 MHz IFThe 26 GHz ODU mounts to the back of its antenna using a circular waveguide interface.

38 GHz



Table A-Y 26 GHz 800 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

L01 63-260800-00111-6100 24250 24450 25050 25250H01 63-260800-10111-6100 25050 25250 24250 24450

Table A-Z 26 GHz 1008 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

L01 63-261008-00111-6100 24549 24871 25557 25879H01 63-261008-10111-6100 25557 25879 24549 24871L02 63-261008-00211-6100 24843 25151 25851 26159H02 63-261008-10211-6100 25851 26159 24843 25151L03 63-261008-00311-6100 25123 25445 26131 26453H03 63-261008-10311-6100 26131 26453 25123 25445

Table A-AA 38GHz 700 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz


Table A-AB 38GHz 1260 MHz T/R Spacing


TX Upper Limit, MHz

RX Lower Limit, MHz

RX Upper Limit, MHz

LB1 63-381260-00111-6100 37044 37632 38304 38892HB1 63-381260-10111-6100 38304 38892 37044 37632LB2 63-381260-00211-6100 37604 38192 38864 39452HB2 63-381260-10211-6100 38864 39452 37604 38192

Frequency Tables


Proteus AMT L-Series Manual Page B-1

Appendix BAlarm Definitions

100BT Tributary n Local Loopback Stated tributary is in local loopback (minor).

100BT Tributary n Remote Loopback Stated tributary is in remote loopback (minor).

100BT Tributary n RX AIS All 1s (alarm indication signal) received on Ethernet tributary

100BT Tributary n RX LOS Loss of signal on Ethernet tributary (minor).

100BT Tributary n TX PN Pattern Stated tributary is transmitting a BER psuedo-random number pat-tern (minor).

Aggregate Local Loopback Aggregate local loopback is active (minor). A digital loopback be-tween MODEM and LIM.

Aggregate Transmit PN Pattern Modem is transmitting BER psuedo-random number pattern instead of payload data.

AIS Inserted on Tributaries AIS (blue signal) generator active. All 1s (alarm indication signal) inserted on tributary.

Alarm Log Reset Indicates that the alarm log was reset. Setting the reset as an alarm adds a time-stamped entry to the alarm log for tracking.

APC at Max Power Automated Power Control is on and the far end is requesting more power, but the power is at the maximum setting allowed by the user (minor).

Configuration Fail Modem did not configure properly due to line failure, equipment mismatch, or modem failure (major). Proposed LIM (line) type does not fit licensed configuration.

Configuration Not Supported Proposed LIM (line) type does not fit available hardware.

Custom BER Level Current BER is greater than the threshold specified by the alarm. The default value for the threshold is 10-9, but can be changed via alarm mapping (minor).

E1/DS1 Tributary n Local Loopback Indicated tributary is in local loopback (minor).

E1/DS1 Tributary n Remote Loopback Indicated tributary is in remote loopback (minor).

E1/DS1 Tributary n RX LOS Loss of signal on tributary n (1–16; minor).

Alarm Definitions

Page B-2 Proteus AMT L-Series Manual

E1/DS1 Tributary n TX PN Pattern Indicated tributary is transmitting a BER psuedo-random number pattern (minor).

E1\DS1 Tributary n RX AIS AIS (blue signal) received on n (1–16) tributary.

Equipment Mismatch Equipment does not match radio configuration (major).

Far End Terminal Failure Far end IDU has a current major alarm (minor at Near-End terminal).

Flash Fail Power-up tests indicated that the FLASH failed (minor).

Hot-Standby Hi Priority Alarm Signals that one of the alarms that is mapped as an HPA (high prior-ity alarm) is active. If one radio on a hot-standby system has a high priority alarm and the other does not, then the RSU switches to the radio path with no HPA and sets the radio with an HPA off-line.

Hot-Standby Low Priority Alarm Signals that one of the alarms mapped as an LPA (low priority alarm) is active. The Redundancy Switch Unit (RSU) takes no action on LPA.

Hot-Standby Other Radio Alarm An alarm used on the hot-standby radio configuration. The alternate radio has a high priority alarm (minor).

I2C Failure I2C bus (to IF board, PS board, EEPROM, and temperature sensor) failed.

IF Board PLL Lock Synthesizer on the IF board will not lock. Data will likely not pass over IF (major).

IP-Over-Air Channel Fail Loss of the 64-kbps IP overhead channel (minor).

Major Alarm Summary Any alarm thought to be potentially traffic-affecting

Minor Alarm Summary Any alarm condition that degrades radio performance or a radio in diagnostic mode.

Modem Receive Fail Modem is not currently acquired (includes error and unconfigured states; major).

Modem Rx AGC Fail Adaptive gain control circuitry is out of range (major).

Modem Rx Carrier The receive radio is not detecting a carrier at the IDU.

Modem Rx Frame Loss The modem is trying, but cannot, acquire (major).

Modem Transmit Fail Modem transmitter is malfunctioning (major).

ODU Mute Alarm ODU output muted.

ODU RX/TX Alarm ODU indication of a TX or RX failure (major).

ODU Telemetry Alarm Cannot communicate with the ODU (minor).

Primary Power Supply Fail Power supply of main unit is in alarm. Problem will likely kill the processor before the alarm turns on (major).

Alarm Definitions

Proteus AMT L-Series Manual Page B-3

RAM Fail Power-up DRAM test failed (minor).

Real Time Clock Fail Power-up test indicated that the Real Time Clock failed (minor).

Reverse Channel Switch Request Other side of a protected link requested a reverse channel switch (major).

RSL Threshold Fade margin is below the threshold specified by the alarm. Default value for the threshold is 2 dB, but can be changed via alarm map-ping (minor).

Rx AIS Signal AIS (all ones) inserted on the receive interface. LOS on the receive line interface.

Rx BER >10^-3 Current bit error rate is greater than the threshold (major).

Rx BER >10^-6 Current bit error rate is greater than the threshold (minor).

Secondary Power Supply Failure Power supply of Redundancy Switch Unit is in alarm (major).

SRAM Fail Power-up test indicated that the SRAM failed (minor).

System Bootup System booted (used to mark alarm log; minor).

Term-to-Term Channel Fail IDU cannot talk to far-end IDU (terminal), and cannot get or set far-end parameters (minor).

Watchdog Timeout Last boot cycle was caused by the watchdog timer going off (unex-pected reset; major).

Alarm Definitions

Page B-4 Proteus AMT L-Series Manual

Proteus AMT L-Series Manual Page C-1

Appendix CRadio Management Interfaces

OverviewA controller in the IDU handles radio operation by accessing all alarms and controls in the IDU and ODU. Users have three management inter-faces to the controller through the front-panel management ports that Figure C-1 shows: Element Manager – the Windows-based graphical user interface, CTI – the text-based menu interface, and SNMP – an in-dustry standard IP interface. The front-panel management ports include: COMPUTER – an RS232 serial connection, and NMS – an RJ45 Ether-net interface for Telnet/SNMP

Multiple radio controllers can be cascade coupled to a central manager (Chapter 2, ”Connecting Network Management”). Each controller has its own address, so the manager can access coupled radios individually.

The controller also transmits and receives radio management data to, and from, the radio at the opposite, or far end, of its radio link. Accessing any unit includes the near and far-end data for easy analysis.

Information such as the remote Major/Minor alarms travel on this chan-nel. Services include:• Radio service messages• Radio management communications

Figure C-1. Radio Management Ports

Radio Management Interfaces

Page C-2 Proteus AMT L-Series Manual

Connections

Radio service channels provide the link for broadcasting radio perfor-mance data and alarm messages, and issuing configuration and control statements to individual radios, radio hops, and multiple radios in a con-nected network. This overhead channel includes the network manage-ment channel for radio management communications and the auxiliary channels.

A management controller accesses all alarms and controls in the IDU and ODU. The following interfaces provide access to radio management con-troller data in two modes: IP and serial. The follows sub-sections detail the connections.

• COMPUTER: 9-pin sub-D connector. 9.6 to 57.6 kbps RS-232 serial interface to computer using VT100 emulation. Also works with EM serial mode.

• NMS: two RJ-45 ports for 10/100BaseT IP management data. This connection works using SNMP, Telnet, or EM.

Computer

The computer port on the IDU front panel provides direct RS-232 serial access to radio maintenance applications. Connect a VT100 terminal or use any terminal emulation program, such as the HyperTerminal pro-gram that ships with Windows, to access the text-based maintenance ap-plication.

Use Element Manager (EM) from a computer serial connection to the front-panel computer port. EM asks for connection type on opening.

Serial connections to terminals or computers use a straight-through serial cable terminated with DB-9 connectors (not provided). See the Chapter 2, Installation, for the serial connection details.

Set terminal emulation programs for VT100 with a port setting of 9600 bps, 8 data bits, no parity, 1 stop bit, and xon/xoff flow control.

NMS-SNMP

Proteus AMT radios have two RJ45 ports for 10BaseT Ethernet to an SNMP agent. Connect SNMP through the RJ-45 NMS port on the front panel.

NMS port speed and duplex have manual settings, but auto-negotiation mode is the default. Change NMS ports independently from Configura-tion menus. Settings include: Powered Down, Auto-negotiate, 10BaseT Half-duplex, 10BaseT Full-duplex, 100BaseT Half-duplex, 100BaseT Full-duplex. Port 1 is the top connector and Port 2 the bottom.

Connections


Because auto-negotiation is the default speed, and auto-sensing (MDI/MDIX) is always enabled, you can connect Ethernet ports between radios without configuration or special cabling.

Access any radio from an Ethernet LAN or WAN using the radio IP ad-dress. Once connected, use EM, Telnet, or any SNMP management soft-ware to access radio configuration, diagnostic, or performance data.

SNMP Basics

SNMP provides open-standard radio management via Ethernet. Since SNMP is an open-standard protocol, any SNMP-capable management application may be used to manage SNMP-based radios.

SMNP is a network management standard for LANs that defines a cli-ent/server relationship. The client program (called the network manager) makes virtual connections to a server program (called the SNMP agent) that operates on a remote network device and serves information about device status to the manager. SNMP uses a management information base (MIB) to define these virtual connections. Any SNMP manager, with proper access, can query the status and modify the configuration of each managed device.

A MIB is a standard set of structure and format definitions for exchang-ing information about network devices. Microwave Networks’ MIB is a private MIB for its radio. The MIB contains the common name of each object (which must be unique), the value of the object IDs (OID, which are hierarchical and must be unique), and the textual description of the syntax and semantics of the radio.

Ethernet routing in the Proteus AMT is self-learning, which makes set-ting up a radio network uncomplicated. Routing Information Protocol version 2 (RIP-2) provides dynamic routing of up to 15 radios in a sub-net. Spans of these 15-radio subnets are unlimited.

RIP is primarily for networks of moderate size and has these limitations:

• Limited to sub-networks whose longest path is 7 hops (15 radios).• Uses fixed metrics to compare alternative routes; so it is unsuited to

situations where routes need to be chosen based on real-time parameters such a measured delay, reliability, or load.

After setting the IP address of the first-accessed radio locally, and then configuring it as an intermediate gateway, routing tables of radios net-work exchange and incorporate route information as the radio network changes.

The management station, or SNMP manager, sends get and set requests to the SNMP agents–the radios. The radio answers get and set requests from the manager as specified by the MIB.

Each radio has two IP addresses: one addresses the Ethernet interface (LAN), and the other the over-the-air interface (WAN). The over-the-air interface transports radio support data, including get and set requests



from the SNMP manager, over the microwave link and to other ad-dressed radios as routing tables define.

Installing the SNMP MIB SNMP-compliant devices, called agents, store data about themselves in Management Information Bases (MIBs) and return this data on SNMP requests. A MIB is a database of objects that a network management sys-tem can monitor. SNMP uses a standardized MIB format that allows any SNMP tool to monitor any device defined by a MIB.

Radio data that the Proteus AMT L-Series MIB stores include status, alarms, performance statistics, radio configuration, and commands to the radio controller.

The product CD included with your shipment has the radio MIB file. Open the MIB file in a text editor to view details about the managed ob-jects.

To install the MIB

1. Insert the CD into the drive on the management station computer.2. When the CD menu opens select MIB. 3. Copy the file .mib file to the MIB support directory of your SNMP

management application.4. Add and compile the new MIB according to the steps outlined by your

SNMP application for adding a MIB file.

MIB TablesFigure C-2 shows the major Proteus AMT SNMP objects.

Status–view link or radio status.

Alarms–configure and monitor current and latched radio alarms.

Notify–control and monitor traps.

Performance–monitor radio performance statistics.

Control–perform system tests and monitor results.

Configuration–view and change radio settings.

Utility–use the utilities to install, and distribute radio operating code.

Figure C-2. SNMP MIB Tables

Element Manager


Element Manager

Element Manager® (EM) is the Proteus AMT L-Series and Proteus AMT radio and link graphical supervisory system that simplifies configuring, monitoring, and testing your radio or link. It provides radio management from a PC using the Windows™ operating system.

You never have to open the radio to set jumpers or switches. Proteus AMT management interfaces, whether graphic or text based, control all radio configuration.

EM runs on a personal computer and interfaces radios locally, through the standard serial interface, for simple on-site radio and link manage-ment. EM also functions remotely through an IP-based network or through dial-up modem. Figure C-3 shows the EM display of a protected radio configuration with LinkView enabled. LinkView summarizes per-formance graphically for both primary/secondary and near-end (top) and far-end (bottom) radios.

Figure C-3. Element Manager Main Screen



Key Features

Element Manager (EM) gives radio installers, maintenance personnel, and operators an efficient tool for complete management and control of their Proteus AMT L-Series and AMT radios—on site or from remote lo-cations. EM is fully functional with real-time detailed data from any con-nection.

EM connects on-site to the radio computer connector, or from remote lo-cations through the SNMP connection.

A radio manager can use EM to configure a radio, test a radio or link, and monitor performance and alarms.

System Requirements

This version of EM is designed for Windows 9x, NT, XP, and 2000.

System requirements:

• 700-MHz processor (recommended)• 128 MB of RAM • 126 MB free disk space (full installation)• 200 MB free disk space for optimal performance

Connect the PC to the serial COMPUTER connector on the IDU using a standard, straight-through, RS-232 cable (not provided). Chapter 2, In-stallation, describes the cable assembly and its wiring.

Basics

EM operates in a personal computer attached to the radio serial port or remotely through an IP network or by PTSN with a modem to let opera-tors control and monitor any radio in a network.

In an IP network the radio acts as multi-homed device. That is, the radio has two IP interfaces—one 10/100-Mbps Ethernet interface and one 64-kbps IP-based overhead channel. The radio uses the overhead channel to get radio-specific data across the link.

When connecting to radios through a LAN you must know the IP address of the target radio.

EM queries the radio that interface for configuration, events, and alarms. EM’s graphical interface provides a clear display of radio information, alarms, status, configuration, and logs as Figure C-4 shows. Windowed views let you configure the display to show only the data you need.

Element Manager


Polling and Port Indicators

EM polls the connected radio or the network for status. The status bar at the bottom of the main screen, Figure C-4, shows that the manager is connected and the current status of the local radio and the network link.

Alarms

Colors indicators on the status bar match IDU indicators and display ra-dio health.• Green indicates normal operation.• Yellow is a minor alarm. The radio link may be running but not

optimal.• Red signals a major alarm. The radio link is down or severely

degraded.• Blinking Yellow indicates a test control, such as loopback, is active.• Blue shows latched alarms – past alarm conditions that EM logs.

Event and Alarm Logging

The radio logs up to 200 items: 100 radio alarms and 100 events. Events include configuration changes and condition changes. The radio stores the 16 most recent alarm events in protected memory. Should a power failure occur or the radio logic get reset, the last 16 alarms are available for fault isolation. Event (change) logs are not saved through power fail-ures or logic reset. EM displays events in the event (change) log and alarms in the alarm log.

Identifying Radios

Once initialized, screens identify radios as NE or FE, by radio name, and as primary or secondary on protected systems. You can view the radio in-formation to identify radio name and location.

Security

EM has administrator and guest security levels. Guests can read, but not change, radio parameters. Administrators can change radio configura-tion. Your password logs you to local and remote radios at the same secu-rity level.

Figure C-4. EM Menu and Status Bar



Initially, guest access requires no password, and the administrator pass-word is mni. The system does not let users set a password for one user (admin/guest) that is already in use by another.

EM Menus

Drop down menus display selections for radio information displays, con-trol dialog, and application help. Use EM Help (F1) for topics about op-erating EM. Table C-A shows and details each of the EM menus.

Table C-A EM Menus and DescriptionsMenu Description

Connect opens when EM opens or when selected. Set the connection as serial or Ethernet.Default passwords are:Guest – no passwordAdmin – mniDisconnect lets you close the connec-tion.Backup Configuration lets you save your radio setup to a configuration file (.cfg) that you can load to another, or replacement, radio.Restore Configuration lets you load a specific radio configuration file.You can also load configuration files to EM in Demo mode for validation and troubleshooting.Alarms and Test Settings displays are identical for near- and far-end radios, and primary/secondary radios. Green LED icons indicate normal conditions; red LED icons show an active alarm or that a test is active. Select Alarms to open the Alarm Log. Select Event Log from the menu.RF Statistics displays RSL*, fade mar-gin, and AGC voltages of the near-end/ far-end, and primary/secondary receiv-ers.G.826 Statistics shows link error perfor-mance statistics.Use History to configure and display historical performance data.You can save performance data to a comma-separated values (.csv) file manually or automatically, and import these files into database or spreadsheet applications for analysis.

The RESTORE CONFIGURATION command opens a restore options box. The RESTORE PASSWORDS option is typically not used. The option restores passwords that you manually edit in your backup file. If not manually entered, EM sets passwords as three asterisks (***).

Element Manager


Menu DescriptionRadio Info provide radio performance data. Inventory lists serial numbers, firmware version, and interface type. Link View shows radio performance of near- and far-end primary/secondary radios. Use Test to configure radio tests. ODU Mute attenuates the online trans-mitter, Loopback sets aggregate (digi-tal; modem) and tributary loopbacks (digital; line interface), and BERT sets aggregate and tributary bit error rate tests.IDU: change date and time, radio name, location, contacts, and license key. Also set passwords, and set the craft port baud rate.ODU: set transmit frequency and output power. Also set ATPC and the RSL set points. The ODU display includes an ODU Mute switch and timer.Payload: configure payload for the licensed throughput (affects traffic).LIMA/B: configure lines as equipped or unequipped for LOS monitoring. Also set line encoding: B8ZS, AMI, HDB3.

Set disconnected lines to UNEQUIPPED to prevent LOS alarms in the alarm logs.

IP Addresses: set IP addresses and network masks of LAN (radio), WAN (IPO-Air), and TFTP server for updating radio operating code.Set and add Trap Destination. Set and add Static Routes. Also, set trap mode to silent–off, verbose–all data, or terse–summary.Default gateway lets you define where the radio sends IP packets destined for other IP subnets (typically a router in the same network or subnet).

Alarms: map alarm events as high- or low-priority alarm (HPA/LPA), No Alarm, minor alarm, or none.

Table C-A EM Menus and Descriptions (continued)



Craft Terminal and Command Line Interface

The craft terminal interface (CTI) provides a text-based system for ac-cessing radio data and controls with a VT100-compatible terminal or em-ulation program.

CTI includes a character-based menu system and a limited command set, called the command line interface (CLI), to configure a radio, check alarms, set controls, and monitor radio performance. Like EM, CTI ac-cesses the radio alarm log. Instead of using a mouse, you enter command or select menu options using your terminal or computer keyboard.

The craft-terminal interface (CTI) menu opens after you log in. Select Exit to go to the command-line prompt. CLI has a few commands for di-rect access, scripting, and factory troubleshooting as Table C-B lists.

Utility lets administrators update and validate radio operating code – firm-ware†.Use Download Firmware to download application code using TFTP.The IDU has two image locations to pro-tect radio firmware. New application code always loads to the secondary image. Reboot new code from the sec-ondary to verify the new code.Copy code to primary image loca-tions–default boot location–after verifica-tion.Factory Defaults discards your radio configuration for the factory settings (affects traffic). You can save your con-figuration to a file (File menu) before reset. The Windows menu lists all open win-dows. Select a window to make it active.

User Manual displays system help top-ics. About lists software release infor-mation.

*. The RSL display only reads up to -90 dBm, and does not accurately measure RSL for radios operating beyond -90 dBm.

†. Firmware files include '.hex' files for the application image, and '.mni' for IDU and LIM programable logic.

Table C-A EM Menus and Descriptions (continued)



Type HELP and press ENTER for a list of available command. Enter HELP MORE for an on-screen description of available commands.

Table C-B CLI Commands

Command Description and UsageEthWrite Write to Ethernet interfaceEthRead Read from Ethernet interfaceEthStats Get detailed statistics from Ethernet interface IPOAstats, IPOAstats {reset}

Show IPOAir Channel Statistics

cpu Monitor CPU performance statisticsexit Ends the CLI sessiong826reset Reset G.826 statisticsg826print Lists G.826 statisticshelp Opens the list of commandsmenu Starts menu-driven interfaceodu Shows odu uplink and downlink information

ping Send an ICMP echo request. Usage: ping host [-n count(max 1000)]

probe Factory use onlyroutes In-depth look at the routing tablesystemlog Display system log messages. Crl-C to abort.shell Enhanced debug shellttstats Show Terminal-to-Terminal channel statistics

termterm Run-time debugging features for terminal-to-terminal channel testing

tasks Displays task information or deletes a taskvalid Displays all valid configurationswhoami Lists user and radio name

Radio A> helpEthWrite EthRead EthStats IPOAstats cpuexit g826reset g826print help menuodu ping probe routes systemlogshell ttstats termterm tasks validRadio A>



Menus

The following sections discuss the craft terminal interface (CTI) menus. The CTI has many of the advantages of a pull-down menu system, but al-lows the menus to be used from a key pad, is integral to the IDU, and does not need a mouse to navigate.

The boot code is the first software loaded during power-up or IDU ini-tialization. You can see the progress of the boot test progress when con-nected to the IDU in serial mode. Press CTRL+C within 2 seconds to stop the boot and use a manual boot menu.

Main Menu

Menu layout includes the menu title, menu selections, and a status line. Status line includes the radio name, alarm condition, and link condition Normal condition shows no alarms and link operating status.

Access top-level tasks from the main menu. Type the number of the menu selection you want and press Enter.

Alarm Menu

--------------------------------------------------

Main Menu

1. Alarms

2. Performance

3. Test

4. Configuration

5. Utilities

0. Exit

Radio A, No Alarm, Link Up >

RADIO NAME RADIO CONDITION LINK CONDITION

MENU SELECTION

MENU TITLE

--------------------------------------------------Alarm Menu 1. Current Alarms 2. Latched Alarms 3. Alarm Log 4. Change Log 5. Clear All Latched Alarms 0. ExitRadio A, No Alarm, Link Up >



Performance Menu

Test Menu

Configuration Menu

Utility Menu

--------------------------------------------------Near End Performance Menu 1. Last Second Statistics 2. Last Minute Statistics 3. Last Hour Statistics 4. Last Day Statistics 5. Last Week Statistics 6. All Statistics 7. History [ON] 8. Reset Stats 0. ExitRadio A, No Alarms, Link Up >

--------------------------------------------------Test Menu 1. Aggregate Local Loopback 2. Aggregate BER Test 3. Tributary Loopback 4. Tributary BER Test 5. ODU Mute 0. ExitRadio A, No Alarm, Link Up >

--------------------------------------------------Configuration Menu 1. IDU 2. ODU 3. Payload / Modulation 4. IP 5. Alarms 6. Reset to factory Settings 0. ExitRadio A, No Alarms, Link Up >

--------------------------------------------------Utility Menu 1. Download Files 2. Copy Image (Secondary to Primary) 3. Copy Image (Primary to Secondary) 4. Synchronize Secondary Images 5. Reboot To Primary Image 6. Reboot To Secondary Image 0. ExitRadio A, No Alarms, Link Up >



Security and Radio Identity

Once you establish communication between the terminal and radio, the login command displays. Log in with your user name and password. The defaults for administrator is admin, and for guest is guest. Initially, guest access requires no password, and administrator access password is mni. Use the configuration menu to enter new passwords.

The software opens by identifying the radio and its operating specifics.

Trying 172.2.16.2 (PORT:23)...Connected to 172.2.16.2...Login: adminPassword: ***

*************************************************************

** Welcome to the Proteus AMT L-Series Radio** (c) 2002-2005, Microwave Networks, Inc.** Software Version: 0.Da (2005-09-27)-1** Capacity: 8 E1 + 100 BaseT** Bandwidth: 28 MHz** TX Frequency: 22718.000 MHz** RX Frequency: 21486.000 MHz** LAN IP Address: 172.2.1.2 MASK 255.255.0.0** WAN IP Address: 3.3.3.1 MASK 255.255.255.0**************************************************************



Alarms

Alarms include near- and far-end current and latched alarms, the alarm and change logs, and a command to clear latched alarms.

Current alarms are those that are active. Alarms are normally self clear-ing, that is, as soon as the condition clears the alarm stops. Latched alarms are past alarm conditions, which each radio logs.

After selection of the radio you want to monitor, the alarms display as a few lines of text under the radio selection menu as shown below.

Up to 100 user change events get time- and date-stamped to the change log, and 100 alarm events to the alarm log as shown below. The 16 most recent alarms are saved to non-volatile memory in the event of power failure or unintended reset. Alarm menus let you select a log to view. Alarm and change log menus also let you reset logs.

Change logs also list user level and IP address of any user that creates a change event.

--------------------------------------------------Alarm Menu 1. Current Alarms 2. Latched Alarms 3. Alarm Log 4. Change Log 5. Clear All Latched Alarms 0. ExitRadio A, No Alarm, Link Up > 1

--------------------------------------------------Current Alarms 1. Near End [Normal] 2. Far End [Normal] 0. ExitRadio A, No Alarm, Link Up > 3

MAJOR: ON IF Board PLL Lock Modem Receive Fail Modem Rx Frame Loss Rx BER > 10^-3MINOR: ON Terminal-to-Terminal Channel Fail Primary Power Supply Failure Secondary Power Supply Failure Rx BER > 10^-6 ODU Telemetry Alarm AIS Inserted on Tributaries



--------------------------------------------------Near End Alarm Log Menu 1. Show Alarm Log 2. Reset Alarm Log 0. ExitRadio A, No Alarm, Link Up > 1

2005/02/24 11:29:55, Radio A, (set), ODU Telemetry Alarm, I: 33, O: 02005/02/24 11:29:55, Radio A, (set), IF Board PLL Lock, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), Tributary 8 RX LOS, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), Tributary 6 RX LOS, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), Tributary 3 RX LOS, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), Tributary 1 RX LOS, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), AIS Inserted on Tributaries2005/02/24 11:29:54, Radio A, (set), Custom BER Level, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), Rx BER > 10^-6, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), Rx BER > 10^-3, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), Modem Receive Fail, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), Major Alarm - Latched, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), Major Alarm Summary, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), Modem Rx Frame Loss, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), Minor Alarm - Latched, I: 33, O: 02005/02/24 11:29:54, Radio A, (set), Minor Alarm Summary, I: 33, O: 0End

--------------------------------------------------Near End Change Log Menu 1. Show Change Log 2. Reset Change Log 0. ExitRadio A, No Alarm, Link Up > 1

2005/02/24 14:46:47, 29, Admin, 172.16.99.22, Command Processor Command2005/02/24 14:44:52, 3, Admin, 172.16.99.22, Command Processor Command2005/02/24 14:44:24, 3, Admin, 172.16.99.22, Command Processor CommandEnd



Performance

G.826 performance statistics for payload and the link use error detection codes inherent to the radio. Near- and far-end statistics for last second to last week consider the following events:

Errored Second (ES) A one second period with one or more errored blocks or at least one defect

Severely Errored Second (SES) A one-second period, which contains ≥ than 30% errored blocks or at least one defect. SES is a subset of ES.

Bit Error Rate (BER) The percentage of bits that have errors relative to the total number of bits received in a transmission, usually expressed as ten to a negative power.

Performance statistics refresh every five seconds. You can also enable performance history data collection and select an interval is between 1 second and 500 days as the following text describes.

-------------------------------------------------Performance 1. Near End 2. Far End 3. Reset All Stats 0. ExitRadio A, No Alarms, Link Up > 1

--------------------------------------------------Near End Primary Performance Menu 1. Last Second Statistics 2. Last Minute Statistics 3. Last Hour Statistics 4. Last Day Statistics 5. Last Week Statistics 6. All Statistics 7. History [N/A] 8. Reset Stats 0. ExitRadio A, No Alarms, Link Up >

Near End Performance (Last Second) Near End Far End Elapsed Seconds: 1 1 Available Seconds: 1 1 Errored Seconds: 0 0 Severely Errored Seconds: 0 0 Bit Error Rate: 0.00e+00 0.00e+00

(CTRL-C to exit)



On the performance statistics menus the All Statistics selection lists all G.826 statistics and the significant RF performance measurements.

The History selection lets you configure and collect performance data for the selected radio at an interval between 1 second and 500 days. When you enable performance history you can display or upload a file of up to 27 performance variables.

Get a free trial version of a TFTP server at www.solarwinds.net

Uploaded performance history files go your TFTP server (not provided) at the interval you set, or you can request a manual upload anytime.

Enter the IP address of the TFTP server in the Utilities menu, Download selection. The file saves to the directory you configure in your TFTP server application.

Near End Performance (Custom) Near End Elapsed Seconds: 172194Available Seconds: 0Unavailable Seconds: 172194Errored Seconds: 0Severely Errored Seconds: 0Errored Seconds Ratio: 0.00e+00Sev Errored Seconds Ratio: 0.00e+00Total Codewords: 0Bit Error Rate: 0.00e+00Back Bit Error Rate: 0.00e+00Current RSL: 0Fade Margin: 70Transmit Power: 0

(CTRL-C to exit)

--------------------------------------------------Near End Performance History Menu 1. Data Collection Enable [OFF] 2. Data Collection Interval [1 Minute] 3. Collected Variables [27 selected] 4. Upload Filename [phist.csv] 5. Upload Interval [15 Seconds] 6. Storage Info 7. Show History 8. Request Manual Upload 9. Clear History 0. ExitRadio A, No Alarms, Link Up >






Test

Use TEST to install, commission, and maintain the radio. You can mute the online transmitter, set local aggregate or tributary loopback, or run a bit-error rate test on local (near end) or remote (far end) radios.

Aggregate local loopback is a digital loopback between the modem out-put and the line interface (Figure C-5).

Tributary loopback occurs at the line interface (Figure C-5) for Ethernet and PDH applications. Because IP is a routing protocol, remote Ethernet loopback only supports broadcast packets.

-------------------------------------------------Test Menu 1. Aggregate Local Loopback 2. Aggregate BER Test 3. Tributary Loopback 4. Tributary BER Test 5. ODU Mute 0. ExitRadio A, No Alarm, Link Up >

-------------------------------------------------Aggregate Local Loopback 1. Near End [N/A] 2. Far End [N/A] 0. ExitRadio A, No Alarm, Link Up > 1

--------------------------------------------------Near End Aggregate Loopback Menu 1. Aggregate Local Loopback [N/A] 2. Aggregate Loopback Time [N/A] 0. ExitRadio A, No Alarm, Link Up > 2

Enter new value for Agg Loop Time (0 for infinity):

-------------------------------------------------Tributary Loopback 1. Near End 2. Far End 0. ExitRadio A, No Alarm, Link Up > 1

--------------------------------------------------Near End Tributary Loopback Menu 1. Tributary Local Loopback 2. Tributary Remote Loopback 0. ExitRadio A, No Alarm, Link Up >



BER test mode lets you configure the test and view test results. BER is expressed as 10 to the negative power. For example, the BER result 3E-6 would indicate that three bits were in error out of 1,000,000 transmitted. Expressions for bits received and bits errored are hexidecimal format.--------------------------------------------------Tributary BER Test 1. Near End 2. Far End 0. ExitRadio A, No Alarm, Link Up > 1

--------------------------------------------------Near End Tributary BER Test 1. Tributary BER Test Mode 2. Tributary BER Test Results 3. Clear Tributary Results 0. ExitRadio A, No Alarm, Link Up > 1

--------------------------------------------------Near End Primary Tributary BER Test Mode 1. Trib 1 [OFF] 2. Trib 2 [OFF] 3. Trib 3 [OFF] 4. Trib 4 [OFF] 5. Trib 5 [OFF] 6. Trib 6 [OFF] 7. Trib 7 [OFF] 8. Trib 8 [OFF] 9. Trib 9 [OFF] 10. Trib 10 [OFF] 11. Trib 11 [OFF] 12. Trib 12 [OFF] 13. Trib 13 [OFF] 14. Trib 14 [OFF] 15. Trib 15 [OFF] 16. Trib 16 [OFF] 0. ExitRadio A, No Alarm, Link Up >

IDU

Multiplexand

Frame

Codingand

Modem

IFP

rocessing

LIU

ODU

RFProcessing

NE/FE LocalTributaryLoopback

Local AggregateLoopback

NE/FE RemoteTributaryLoopback

Figure C-5. Radio Loopbacks



The displays with the BER test results update every five seconds.

--------------------------------------------------Aggregate BER Test 1. Near End [OFF] 2. Far End [OFF] 3. Clear All Agg BER Results 0. ExitRadio A, No Alarm, Link Up > 1

--------------------------------------------------Near End Primary BER Test Mode Menu 1. Aggregate BER Test Mode [OFF] 2. Aggregate BER Test Results 3. Clear Aggregate BER Results 0. ExitRadio A, No Alarm, Link Up > 1

Near End Aggregate BER Results Near End Far EndBits Received: 0 0Bits Errored: 0 0Agg BER: 0.00e+00 0.00e+00Elapsed Time: 000 d 00:00:00 000 d 00:00:00

(CTRL-C to exit)



Configuration

You must have administrative access to change any setting in Configura-tion.

IDU configuration lets you set the radio name, view inventory, and set user passwords, system clocks, and the data rate of the front-panel com-puter port.

NOTE: You must have administrative access to change configuration settings, and know the current passwords to change administrative or guest passwords.

Radio Name provides a line for you to enter a new value. Inventory is read-only data including serial numbers, firmware versions, interface type, and any firmware checksum.

--------------------------------------------------Configuration Menu 1. IDU 2. ODU 3. Payload / Modulation 4. IP 5. Alarms 6. Reset to factory Settings 0. ExitRadio A, No Alarm, Link Up >

--------------------------------------------------Near End IDU 1. Near End (Local) [Radio A] 2. Far End [Radio B] 0. ExitRadio A, No Alarm, Link Up > 1

--------------------------------------------------Near End IDU Configuration Menu 1. Radio Name [Radio A] 2. Inventory 3. License Key [r2go-FZgZ-QkYJ] 4. Admin Password 5. Guest Password 6. Set Clock [2005-10-11,18:02:12] 7. Craft Port Rate [9600] 8. NMS Speed [Auto-Negotiate/Auto-Negotiate] 0. ExitRadio A, No Alarms, Link Up >

Near End

Image Booted: Primary *** Hardware Components ***Odu Serial #: 52043252Odu Version: B Odu Firmware Version: 10000.32Motherboard Part Number: 8000621-20Motherboard Serial #: 061405049Motherboard Version: A03Motherboard Firmware Part Number: 4600068-00Motherboard Firmware Version: 0.Da (2005-09-27)-1IF Board Part Number: 8000614-13IF Board Serial #: 060705113Idu Power Supply Part Number: 8000569-00



Craft Port Rate (COMPUTER port) provides a line for you to enter a new value. Set the port to 9600, 19200, 38400, or 57600 bps.

ODU configuration lets you view the RF unit information and current settings. Admin access lets you adjust the transmit frequency and output power, and set APC and RSL trip points.

Idu Power Supply Serial #: 060605127PDH Part Number: 8000621-20100BaseT Part Number: 8000621-20*** Firmware Components ***Bootloader Firmware Part Number: 4600067-00Bootloader Firmware Version: 0.B (2005-08-14)Bootloader Firmware Checksum: 65535Primary App Firmware Part Number: 4600068-00Primary App Firmware Version: 0.Da Primary App Firmware Checksum: 37720Secondary App Firmware Part Number: 4600068-00Secondary App Firmware Version: 0.B Secondary App Firmware Checksum: 6553528Mhz E1 Modem Firmware Part Number: 4600073-0028Mhz E1 Modem Firmware Version: Vert0028Mhz E1 Modem Firmware Checksum: 190217Mhz E1 Modem Firmware Part Number: 4600071-007Mhz E1 Modem Firmware Version: Rev_B7Mhz E1 Modem Firmware Checksum: 6553514Mhz E1 Modem Firmware Part Number: 4600072-0014Mhz E1 Modem Firmware Version: Rev_B14Mhz E1 Modem Firmware Checksum: 65535*** Software Components ***Feature License Key Serial #: FTRKEY Component Service State Serial #: COMPSVCDynamic Image Transfer Serial #: DYNIMGQPSK Modulation Serial #: QPSK8PSK Modulation Part Number: 4600089-228PSK Modulation Serial #: 8PSKConfigurable Bandwidth Serial #: BWCFG2.5 Mhz Bandwidth Serial #: BW2.53.5 Mhz Bandwidth Serial #: BW3.55 Mhz Bandwidth Serial #: BW57 Mhz Bandwidth Serial #: BW714 Mhz Bandwidth Serial #: BW1420 Mhz Bandwidth Serial #: BW2025 Mhz Bandwidth Serial #: BW2528 Mhz Bandwidth Serial #: BW28E1 Rate Channels Serial #: E1100BaseT Payload Part Number: 4600089-61100BaseT Payload Serial #: ETHNMS Speed Select Serial #: NMSSPDRIPv1 Dynamic Routing Serial #: RIP1RIPv2 Dynamic Routing Serial #: RIP2Press any key to continue...

--------------------------------------------------ODU 1. Near End [13120.000 MHz] 2. Far End [12854.000 MHz] 0. ExitRadio A, No Alarm, Link Up > 1

--------------------------------------------------Near End ODU Configuration Menu 1. ODU Info 2. TX Frequency [13120.000 MHz] 3. RX Frequency [12854.000 MHz] 4. TX Power [15 dBm (min:-11, max:19)] 5. APC Mode [OFF] 6. RSL Setpoint [-60 dBm] 7. ODU Mute State [Online] 0. ExitRadio A, No Alarm, Link Up >



ODU information includes the fixed sub-band and transmit/receive spac-ing (low/high band).

Set TX Power (max power in APC): 19

Enable APC to let the radio adjust far-end transmit power in ±1 dB steps to keep RSL within +3 dB of the RSL set point. APC works with your RSL set point and TX Power settings.

Select Payload / Modulation and configure the E1/DS1 channels. For PDH lines 'enable' activates tributaries. Disable channels (lines) for ser-vice. Set the radio to monitor signals on channels "In Use" for loss of sig-nal. You can also assign E1 and DS1tributaries line encoding. E-rate lines–AMI or HDB3, and DS-rate lines are B8ZS.

IP Configuration lets you set the radio IP address, IP mask, and routing. You can enter static routing information of up to 32 routes or use RIP (routing information protocol). RIP automates the population of routing tables on your network.

Serial Number: 3Firmware Version: 53Frequency Band: 13 GHzSub-band: BTx Hi/Lo: HiMin TX Frequency: 13087 MhzMax TX Frequency: 13122 MhzMin RX Frequency: 12821 MhzMax RX Frequency: 12856 MhzT/R Spacing: 266 Mhz

Enter new value for APC: 1. On 2. Off Select:

Enter new value for RSL Setpoint (in -dBm):

Payload / Modulation 1. Near End (Local) [8 E1 + 100 BaseT @ 28 MHz] 2. Far End Primary [8 E1 + 100 BaseT @ 28 MHz] 3. Configure Modem 0. ExitRadio A, No Alarm, Link Up > 1--------------------------------------------------Near End Channel Configuratio 1. E1 Configuration [8 E1] 2. 100 BaseT Configuration [100 BaseT] 3. Channel Bandwidth [28 MHz] 4. Current State [VALID] 0. ExitRadio A, No Alarm, Link Up > 1

--------------------------------------------------IP 1. Near End (Local) [172.2.1.2] 2. Far End [172.3.1.1] 0. ExitRadio 5, No Alarms, Link Up >



RIP is classified as a distance vector protocol, which means it uses dis-tance, as measured in routing hops, to determine a packet's optimal path. Routers send out advertisements to one another every 30 seconds. Each router that receives a given advertisement increases the hop count by one. If advertisements are received from multiple routers, the path to the router with the lowest hop count is the path chosen. Should the preferred route be unavailable, the route with the higher hop count is used as a backup.

Custom router advertisement allows you to enter the IP address and IP mask of a device or gateway on your network that may be problematic for RIP discovery. After custom advertisement, population of routing ta-bles with the device or gateway address continues automatically.

--------------------------------------------------Near End IP Configuration Menu 1. LAN Interface [172.2.1.2] 2. WAN Interface [3.3.3.1] 3. Routing Table 0. ExitRadio A, No Alarms, Link Up > 1

--------------------------------------------------Near End LAN Interface Configuration 1. LAN IP Address [172.2.1.2] 2. LAN IP Mask [255.255.0.0] 3. LAN Routing Config [RIP] 0. ExitRadio A, No Alarms, Link Up > 1

Please enter new value for LAN Address (in dotted decimal):

--------------------------------------------------Near End LAN Port Routing Settings 1. Routing Protocol [RIP] 2. Transmit Mode [RIP 1 Compatibility] 3. Receive Mode [RIP 1 and RIP 2] 4. Enable Custom Advertisement [OFF] 5. Custom Advertisment Address [0.0.0.0] 6. Custom Advertisement Mask [0.0.0.0] 0. ExitRadio A, No Alarms, Link Up > 1

Enter new value for LAN Routing Protocol: 1. Disabled 2. RIP 3. MNI Protection Routing Select:



Utilities

Since Proteus AMT L-Series is completely software configured, you can update the radio operating code using the Utility menu.

Download code (firmware) for bootloader (startup), application, IDU TX, IDU RX, E1/DS1 LINE, and Ethernet LINE code. Download to the secondary image location or synchronize secondary im-ages to copy a secondary image from another radio. Boot from the sec-ondary image to check that the code works, before copying the code to the primary, boot, location.

Get a trial version of an TFTP server at http://www.solarwinds.net

IDU and line code downloads to programmable logic in the IDU. The source port is the Ethernet port from a TFTP server. Use any networked PC running TFTP server software to download firmware to the radio.

Copy image files (code) to the primary (default boot) location after con-firming operation. Maintain the secondary image as a backup.

--------------------------------------------------Utility Menu 1. Download Files 2. Copy Image (Secondary to Primary) 3. Copy Image (Primary to Secondary) 4. Synchronize Secondary Images 5. Reboot To Primary Image 6. Reboot To Secondary Image 0. ExitRadio A, No Alarms, Link Up >

-----------------------------------------------Synchronize Secondary Images 1. Source Radio [N/A] 0. ExitRadio A,, No Alarms, Link Up > 1

--------------------------------------------------Synchronize Secondary Images Source Radio 1. Near End (Local) 2. Far End 0. ExitRadio A, No Alarms, Link Up > 2

--------------------------------------------------Far End Synchronize Secondary Images 1. Source Radio [Far End] 2. Synchronize Images 0. ExitRadio A, No Alarms, Link Up >

Near End Download Menu 1. Begin Download 2. Flash Destination [N/A] 3. TFTP File Name [lc_app.mnz] 4. TFTP Server Address [172.16.99.2] 0. ExitRadio 5, No Alarms, Link Up >



Reboot affects traffic. The radio loads the operating code and must again synchronize with the facing site.

--------------------------------------------------Utility Menu 1. Download Files 2. Copy Image (Secondary to Primary) 3. Copy Image (Primary to Secondary) 4. Synchronize Secondary Images 5. Reboot To Primary Image 6. Reboot To Secondary Image 0. ExitRadio A, No Alarms, Link Up > 5

--------------------------------------------------Utility Menu 1. Download Files 2. Copy Image (Secondary to Primary) 3. Copy Image (Primary to Secondary) 4. Synchronize Secondary Images 5. Reboot To Primary Image 6. Reboot To Secondary Image 0. ExitSWLab-100, No Alarms, Link Up > 5

--------------------------------------------------Reboot To Primary Image 1. Near End (Local) 2. Far End 3. All Radios 0. ExitRadio A, No Alarms, Link Up > 3

Are you sure you wish to reboot all radios (y/n)? yRebooting Online Far End Radio ...Rebooting myself, good bye ...



Proteus AMT L-Series Manual Page D-1

Appendix DWAN/IPO-Air Channel Routing

OverviewUse this section to set up and implement your radio network.

The wide area network (WAN) interface, or IPO-Air (Internet Protocol over the air), channel is a dedicated channel in the microwave communi-cation path that transmits data at 64 kbps minimum. The channel passes Internet Protocol (IP) packets from one radio to another. Each radio has the ability to receive packets on its Ethernet LAN interface and forward them to the IPOAir, or WAN, interface. Any radio can also receive pack-ets from the IPOAir interface and forward them to the Ethernet interface.

The network architecture of Proteus AMT L-Series radios allows IP ac-cess to any radio on the network. This section provides the information you need to administer your radio network.

LAN Port

The local area network (LAN) port is the 10/100BaseT Ethernet interface at the RJ-45 connector on the radio front panel. It is called LAN because it immediately communicates with any Ethernet device on the same sub-net, which typically consists of devices in the same room or building.

WAN Port

The wide area network (WAN) port is tied directly to the IPOAir chan-nel. The WAN port has no physical interface as it is integral to the IDU. The channel allows a radio to communicate with its counterpart radio at the far side of a microwave link (far-end radio). It is called WAN because it communicates with a device several miles away, and therefore covers a much wider area than the LAN port.

WAN Port CommunicationTo communicate via IP, radios in a link must have IP addresses on the same subnet.

Both radios in a link must have IP addresses on the same subnet to com-municate. The address and subnet mask determine the subnet. Subnet mask is a description of values within an IP address unique to the subnet. For example, a device has the IP address 172.25.10.2 and subnet mask 255.255.0.0. The subnet mask indicates that the first two numbers of the IP address defines the subnet – 172.25.0.0. Devices with the IP address

WAN/IPO-Air Channel Routing

Page D-2 Proteus AMT L-Series Manual

that start with 172.25 are part of the 172.25 subnet, and routing should not be required to communicate between these devices.

The IP address and subnet mask may be represented by a single 32-bit number instead of four decimal numbers ranging from 0 to 255. In a sub-net mask, the first, or most significant, bit of the mask must be set to bi-nary 1 while any bit after the first 0 must also be 0. Therefore, 255.255.255.252, binary 11111111 11111111 11111111 11111100, is a valid mask; but 255.255.255.172, binary 11111111 11111111 10101100, is not.

Because of this restriction on subnet masks, they are sometimes referred to by the number of leading 1’s in the mask. For example, a subnet mask of 255.255.0.0 would be called a 16-bit subnet mask, because the first 16 bits are 1’s. A common notation to describe the network in the preceding paragraph is 172.25.0.0/16, which reports the number of bits in the sub-net mask.

Since there are only two radios in a link (four in protected), WAN sub-nets can be small. The following CTI Configuration screens show a WAN interface with an address of 172.17.1.1 and a mask of 255.255.255.252. This means that the WAN port is on subnet 172.17.1.0/30 and may only communicate with other ports on the same subnet.

If the radio does not connect to the WAN interface on the other side of the link, the IP-OVER-AIR CHANNEL FAIL alarm activates. This could hap-pen if the link fails or if WAN interface addresses are not on the same subnet.

--------------------------------------------------Configuration Menu 1. IDU 2. ODU 3. Payload / Modulation 4. IP 5. Alarms 6. Reset to factory Settings 0. ExitRadio A, No Alarm, Link Up > 4--------------------------------------------------IP 1. Near End (Local) [172.2.1.2] 2. Far End [172.3.1.1] 0. ExitRadio A, No Alarms, Link Up > 1--------------------------------------------------Near End IP Configuration Menu 1. LAN Interface [172.2.1.2] 2. WAN Interface [172.17.1.1] 3. Routing Table 0. ExitRadio A, No Alarms, Link Up > 2--------------------------------------------------Near End WAN Interface Configuration 1. WAN IP Address [172.17.1.1] 2. WAN IP Mask [255.255.255.255] 3. WAN Routing Config [RIP] 0. ExitRadio A, No Alarms, Link Up >

IP Data Routing


IP Data RoutingThe routing engine that makes the decisions on whether or not to forward a packet from one interface to another is on an IDU processor between the two ports. The processor receives all packets, examines them, and de-cides if the packet is intended for that radio or needs to be forwarded. Configure the routing table, below, properly for routing to work.

The IPOAir channel can carry any type of IP data, including, but not lim-ited to, Internet Control Messaging Protocol (ICMP, used for PING pro-gram), Telnet, Trivial File Transfer Protocol (TFTP), or Simple Network Management Protocol (SNMP). The IPOAir channel does not support non-IP data such as AppleTalk and NetBios.

The Routing Table

The routing table tells the routing engine what to forward, and where to forward it. The following screen shows a typical routing table for a Pro-teus AMT L-Series radio.

The table is broken into eight columns: ID, DESTINATION, MASK, NEXT HOP, TYPE, INT (interface), MET, ADDED. The ID identifies a route, mak-ing it easier to delete a route using the menu system. The destination is the address where a packet ultimately ends. The mask, along with the destination, defines the subnet ID of where the packet is going. For ex-ample, in ID7 above, the destination address is 172.18.0.0 and the subnet mask is 255.255.0.0, so this route refers to subnet 172.18.0.0/16. The next hop address tells the radio where to send the packet next to get it on its way. In ID7, that address is 172.17.1.2. So any time this radio receives a packet bound for any address that starts with 172.18, it knows to for-ward it on to the device at address 172.17.1.2. The type, direct (DIR) or

IP Configuration Menu 1. LAN Interface [172.16.20.201] 2. WAN Interface [172.40.200.201] 4. Routing Table 0. ExitRadio A, No Alarms, Link Up >

ID Destination Mask Next Hop Type Int Met Added 1 0.0.0.0 0.0.0.0 172.16.40.1 IND 2 2 Dynamic 2 127.0.0.0 255.0.0.0 127.0.0.1 DIR 1 1 System 3 172.16.0.0 255.255.0.0 172.16.99.100 DIR 2 1 System 4 172.16.200.100 255.255.255.255 127.0.0.1 IND 1 1 System 5 172.17.1.0 255.255.255.252 172.17.1.1 DIR 3 2 Dynamic 6 172.17.1.1 255.255.255.255 127.0.0.1 IND 1 1 System 7 172.18.0.0 255.255.0.0 172.17.1.2 IND 3 3 Dynamic

--------------------------------------------------Route Table 1. Add Route 2. Delete Route 3. Change Default Route [172.16.40.1] 0. ExitRadio A, No Alarms, Link Up >



indirect (IND) tells us whether the radio will forward the packet directly to the final destination (DIR) or to another router (IND). The interface field tells us which interface the radio will route the packet on. INT1 is the loopback interface, INT2 is the LAN interface, and INT3 is the WAN interface. ID7 is routing packets across the WAN interface.MET specifies the metric used to select between multiple routes with the same prefix. The lowest metric is the best matching route. ADDED spec-ifies the type of route. Routes you add are Static, routes using RIP are Dynamic, and routes configured by the IP protocol are System.

Looking at the rest of the routing table, ID6 has a subnet mask with no 0’s in it; therefore it refers to the specific address 172.17.1.1. The next hop is the loopback port of 127.0.0.1, so this route shows that packets destined for 172.17.1.1 go to this radio. Note that 172.17.1.1 is the radio WAN interface. There is a similar route for each active interface in the radio, except for the loopback interface. ID4 refers to the LAN interface at 172.16.200.100.

ID5 refers to a network at 172.17.1.0/30, and tells the radio to forward these packets directly out the WAN port. This network is the same net-work that the WAN port is on. This route is added automatically when the WAN port is active, and there is a similar route for all active inter-faces. ID3 refers to the LAN subnet, and ID2 refers to the loopback sub-net.

ID1 is a special route called a default route. Note that it is really referring to a network with an all 0’s mask, which would cover all conceivable ad-dresses. This route tells the radio that when it has no idea of what to do with a packet based upon the other routes, send the packet to address 172.16.40.1. The default route address is presumably a sophisticated router with a much larger routing table.

Static Routes Add static routes to PCs to monitor radios on a different subnet. See the following page.

Static routes are routes that you add to a routing table. Static routes stay in the routing table across power-ups until the you delete them. The ex-ception is when an interface goes down and all the routes to that interface temporarily become inactive. This can occur when the WAN interface fails down as a result of microwave link or radio failure. When the inter-face comes up, the routes become active.

For example, consider the example network in Figure D-1. If the net-work does not use dynamic routing such as RIP (page D-6), then you add static routes to each device to get them to communicate.

IP Data Routing


The following paragraphs discuss connecting a PC to a radio on a different subnet.

Example: Using Static Route to Connect a PC to a Radio BotRadio, which knows how to get to the devices that it is directly at-tached to, has routes to the 172.18.0.0/16 and 172.17.1.0/30 networks. However, it does not know how to get to the 172.16.0.0/16 network, so it cannot communicate with the PC on that network. So, add a static route to the 172.16.0.0/16 network; a route with an IP address 172.16.0.0, a subnet mask 255.255.0.0, and a next-hop destination 172.17.1.1 (the WAN port on the other radio). Note that the next-hop destination has to be an address that the radio already knows how to reach.

Now BotRadio knows how to communicate with the PC, but the PC does not know how to communicate with BotRadio. The PC knows nothing about the IPOAir network or the 172.18.0.0/16 Ethernet network, so it needs two routes. The first is a route to 172.17.1.0 address with a 255.255.255.252 mask and a next-hop address of 172.16.200.100 (To-pRadio). This gets the PC access to the IPOAir network. The second route is to 172.18.0.0 with a mask of 255.255.0.0 and a next-hop address of 172.16.200.100. This gets the PC access to the 172.18.0.0/16 Ethernet network.

At the PC, use the PING command to attempt to send packets to BotRa-dio. PING is a simple program that sends Internet Control Messaging Pro-tocol (ICMP) packets from one device to another, and expects the packet to "echo" back. When you ping 172.17.1.2 (the WAN interface on BotRadio), you receive replies, but do not receive replies when you ping 172.18.200.101 (the BotRadio LAN interface) because the PC is sending all the packets to TopRadio for forwarding, and TopRadio knows how to get to 172.17.1.2 (on a network to which it is directly attached), but does not know how to get to 172.18.200.101.

To fix the problem, add a route to TopRadio to address 172.18.0.0, mask 255.255.0.0, and a next-hop address of 172.17.1.2. This lets TopRadio

Figure D-1. Example Network



forward packets to the LAN interface of BotRadio. Once done, you can ping address 172.18.200.101 from the PC.

Advantages of Static RoutingOnce you understand how static routes work, they are relatively simple to use. You enter them once, after which the network should continue to work indefinitely. The routes are secure and cannot be modified by exter-nal devices.

Disadvantages of Static RoutingFor a large network, there can be a lot of static routes that would have to be added on each device in the network. Also, if you have a protected configuration such as a loop network, static routes can only define one path through the network. If the defined path goes down, you will lose communication, even if an alternate microwave path is still operational. Finally, when adding new radios to an existing network, the static routing table on each radio would have to be updated to describe the new subnets added.

Routing Information Protocol (RIP)Use RIP when building large networks, or when connecting networks that included protected radios.

The Proteus AMT L-Series radio supports Routing Information Protocol (RIP) 1 and 2. RIP is a standard protocol that performs dynamic routing. Each RIP-enabled device on the network declares information about the networks it knows. When device receives this information that describes a network that it does not already know, it adds the routing information of that network to its routing table.

For example, in the network in Figure D-1, if both radios have RIP en-abled on both the LAN and WAN ports on boot up, the BotRadio will learn about the 172.16.0.0/16 network from TopRadio and TopRadio will learn about the 172.18.0.0/16 network from BotRadio. Both will add the routes to their routing table, and the PC will be able to ping BotRadio without manually adding any static routes to either radio.

NOTE: L-Series radios fix RIP transmit mode on the WAN to 'RIP 1'. Both LAN and WAN set to transmit mode RIP 2 would cause conflicts in the routing table.

--------------------------------------------------Near End WAN Port Routing Settings 1. Routing Protocol [RIP] 2. Transmit Mode [RIP 1 Compatibility] 3. Receive Mode [RIP 1 and RIP 2] 4. Enable Custom Advertisement [OFF] 5. Custom Advertisment Address [0.0.0.0] 6. Custom Advertisement Mask [0.0.0.0] 0. ExitRadio A, No Alarms, Link Up >

IP Data Routing


Advantages of RIP

RIP helps configure network communications much faster on large net-works because you don't have to setup static routing tables in any of the radios. And, as you add radios you do not have to re-visit previously in-stalled radios to update routing tables.

When you have a multi-path network, RIP finds the shortest path in terms of routing hops. If that path breaks for any reason, RIP finds the al-ternate path and resume communications.

NOTE: When you install routers with MNI protected radios, such and AMT radios, you MUST use RIP.

RIP is an industry standard protocol that is supported by other third-party devices such as routers. In a complex mixed network, radios running RIP are able to communicate with these other devices to enable communica-tions across the network.

Disadvantages of RIP

Network Size: The RIP standard is limited to 15 routes in a single line. Since each radio performs routing, there are two routing hops for each radio link. So a network that contains more than seven microwave links in a single line will not be able to establish communications across the network using RIP alone.

Convergence: RIP is typically slow to converge. When a device stops receiving a certain route, it can take the device up to five minutes for the route to time out and delete from the routing table. In a large protected network, when one path goes down and the routes in all the radios need to be updated to re-establish communications, network down-time can be significant.

Security and Faults: It is possible for a hack to send RIP packets that lets all network data route to his or her device. Also, if one of the devices on the network does not strictly follow the RIP standard or fails in such a way that it starts to send incorrect RIP advertisement, the entire network can fail.

Bypassing Network Size Limit of RIP

To help alleviate this problem, the Proteus implementation of RIP has CUSTOM ROUTING ADVERTISEMENT. This allows the radio to send out a single, larger network advertisement that appears to RIP as if it is con-nected directly to the radio without using multiple routers; Figure D-2.



In Figure D-2, each route RIP learns has a metric equal to the number of routers that must be traversed to get to the network. From the perspective of the radio with address 172.16.1.1, networks 172.16.1.0/24 and 172.16.2.0/24 (the directly connected networks) have metrics of 1. Net-work 172.16.3.0/24, which it has learned from 172.16.3.1, has a metric of 2. Network 172.16.4.0/24 has a metric of 3, and the metric increases by one for each network down the line. Network 172.17.1.0/24 has a metric of 15, which is the maximum metric allowed by RIP. So 172.16.1.1 will not learn network 172.17.2.0/24, which should have a metric of 16.

All subnet masks are 255.255.255.0

LAN 172.16.1.1172.16.2.1WAN

WAN172.16.3.1172.16.2.2

LAN

microw

ave linkEthernet connection

172.16.3.2172.16.4.1

LANWAN

172.16.5.1172.16.4.2WAN

LAN

172.16.5.2172.16.6.1

LANWAN

172.16.7.1172.16.6.2WAN

LAN

172.16.7.2172.16.8.1

LANWAN

172.16.9.1172.16.8.2WAN

LAN 172.16.9.2172.16.10.1

LANWAN

172.16.11.2172.16.12.1 WAN

LAN

172.16.11.1172.16.10.2 WAN

LAN

172.16.13.1172.16.12.2

LANWAN

172.16.13.2172.16.14.1 WAN

LAN

172.16.15.1172.16.14.2

LANWAN

172.17.2.1172.17.1.2 WAN

LAN

172.16.15.2172.17.1.1 WAN

LAN

Figure D-2. Example of a Large RIP-Enabled Radio Network

IP Data Routing


Use CUSTOM ADVERTISEMENT to extend a RIP enabled networks.

To fix this problem, send a CUSTOM ADVERTISEMENT (using the radio management software) out of port 172.16.15.2. This advertisement will be the network 172.17.0.0/16, with a metric of 1 (at 172.16.15.2). By the time the route traverses to 172.16.1.1, the metric will have grown to 15, and will be added to the routing table. Now 172.16.1.1 will know how to get to both the 172.17.1.0/24 and 172.17.2.0/24 networks. As long as any links added below the 172.17.2.1 radio are within the 172.17.0.0/16 "su-pernet" they will be able to communicate with 172.16.1.1.

In the same example, the radio at 172.17.2.1 cannot learn the 172.16.1.0/24 network because of the same RIP limitation. To solve this, send a CUSTOM ADVERTISEMENT out of port 172.17.1.1 for "supernet" 172.16.0.0/24.

Since the radio with LAN address 172.16.15.2 is sending these custom supernet advertisements out of both ports, it is forming a border between two RIP domains. Such routers are sometimes referred to as border gate-ways.



Proteus AMT L-Series Manual Page E-1

Appendix EOptional ODU and RFU Mounting

OverviewRF units typically mount and latch directly to push-fit antennas to form the ODU. RF units can mount separate from antennas using the offset pole mount kit or the rack mount kit. Antennas for these configurations use a standard rectangular waveguide feed.

Offset ODU MountingUse antennas from a variety of vendors that use a standard rectangular waveguide interface.

Use the ODU offset mounting kit, Table E-A and Figure E-1, to mount a non-protected RF unit on a pole separate from an antenna that uses a standard waveguide feed. Employ the offset ODU option where a Pro-teus AMT L-Series push-fit antenna is not available, a site has antennas for reuse, or to meet customer mounting requirements.

NOTE: Do not use a push-fit antenna. The kit does not convert the push-fit antenna feed to a standard waveguide interface.

When using the offset pole mounting kit, a length of flexible or elliptical waveguide connects the RF unit to an antenna that uses a standard waveguide feed. The kit has an adapter that connects the RF unit RF I/O port to a standard rectangular waveguide interface. This interface is a cover flange with threaded screw holes in a square pattern.

The flexible waveguide you choose may have either a choke or cover flange, but must have a groove for an O-ring to provide an environmental seal. The waveguide flange must also have un-tapped screw holes or pre-placed screws to secure the flange to the adapter on the mounting plate, and to the antenna at the opposite end. Table E-A ODU - RFU Offset Mounting KitDescription P/N7/8-GHz ODU Offset Mounting Kit, Circular I/O 8708271-0711-GHz ODU Offset Mounting Kit, Circular I/O 8708271-1113-GHz ODU Offset Mounting Kit, Rect. I/O 8708271-0015-GHz ODU Offset Mounting Kit, Rect. I/O 8708271-0118-GHz ODU Offset Mounting Kit, Circular I/O 8708271-1823/26-GHz ODU Offset Mounting Kit, Circular I/O 8708271-2338-GHz ODU Offset Mounting Kit, Circular I/O 8708271-38

Optional ODU and RFU Mounting

Page E-2 Proteus AMT L-Series Manual

Table E-B lists components of the ODU offset kit. Table E-C lists the suggested waveguide size and flange type for each RF frequency.

Figure E-1. ODU Offset Mount Kit, P/N 8708271-xx

Table E-B Offset Mounting Kit Components, P/N 8708271-xxDescription P/N QtyKit, Bolt (3/8")/Bracket, Pole Mount 8708225-00 1Plate, Offset Mounting, NP/HSBY 8509698-02 1Screw, 6-32 x 0.438, Phillips-head Flat, SS 1304105-14 10Nut, 6-32, English, w/ext tooth lock washer 0285556F03 8Striker, Offset Mounting, NP/HSBY 8509697-01 4Adapter, ODU (Table E-C) 38000xx-xx 1O-Ring, 1.612" ID, 0.103" diameter, BUNA-N 3900009-09 1O-ring Lubricant, 10cc 52500-118 1Paste, Anti-Seize, 7.5g Tube 6900048-01 1

Table E-C Waveguide Adapters on Offset Mounting PlateODU P/N Flex Waveguide Waveguide Flange7/8 GHz 3800061-01 WR112 circular PBR8411 GHz 3800076-01 WR90 circular PBR10013 GHz 3800060-01 WR75 rectangle PBR12015 GHz 3800059-01 WR62 rectangle PBR14018 GHz 3800064-00 WR42 circular PBR22023/26 GHz 3800065-00 WR42 circular PBR22038 GHz 3800066-00 WR28 circular PBR320

Overview


RFU Rack Mounting Kit Use antennas from a variety of vendors that use a standard rectangular waveguide interface.

The ODU rack mounting kit,Table E-D, provides hardware for mounting an RF unit indoors in a standard 19-inch equipment rack separated from the outdoor antenna.

When using the offset pole mounting kit, a length of flexible or elliptical waveguide connects the RF unit to an antenna that has a standard waveguide feed. The kit has an adapter,Table E-E, that converts the RF unit RF I/O to a standard rectangular waveguide interface. This interface is a cover flange with threaded screw holes in a square pattern. The waveguide you choose to interface with the adapter may be either a choke or cover flange, but must have a groove for an O-ring that pro-vides the environmental seal, and un-threaded screw holes for screws that secure the waveguide to the adapter at the RF unit and the interface at the antenna.

NOTE: Do not use the offset pole mount kit with a Proteus AMT L-Series push-fit antenna. The kit does not have an adapter to convert the push-fit antenna feed to a standard waveguide interface.

The ODU rack mount kit will normally be used with standard antennas from a variety of vendors using a traditional rectangular waveguide feed. Table E-E lists components of the ODU rack mounting kit. Table E-F lists suggested waveguide size and flange type for each RF frequency.

Table E-D RFU Rack Mounting KitDescription P/N7/8GHz, Rack Mounting Kit, Circular I/O 8708272-0711-GHz, Rack Mounting Kit, Circular I/O 8708272-1113GHz, Rack Mounting Kit, Rectangular I/O 8708272-0015GHz, Rack Mounting Kit, Rectangular I/O 8708272-0118GHz, Rack Mounting Kit, Circular I/O 8708272-1823/26GHz, Rack Mounting Kit, Circular I/O 8708272-2338GHz, Rack Mounting Kit, Circular I/O 8708272-38

Table E-E ODU Rack Mounting Kit ComponentsComponent P/N QtyRFU Mount 8509738-01 1Screw, 6-32 x 0.438, Phillips-head Flat, SS 1304105-14 10Waveguide adapter, see Table E-F 38000XX-XX 1Nut, 6-32, English, w/ext tooth lock washer 0285556F03 8Striker, Offset Mounting, NP/HSBY 8509697-01 4Screw,12-24, self-tap, slot hex-head, SS 38531400 8O-ring,1.612" ID, 0.103" diameter, BUNA-N 3900009-09 1O-ring Lubricant, 10cc 52500-118 1



Table E-F Waveguide Adapters on Rack Mounting PlateODU P/N Flex Waveguide Waveguide Flange7/8 GHz 3800061-01 WR112 circular PBR8411 GHz 3800076-01 WR90 circular PBR10013 GHz 3800060-01 WR75 rectangle PBR12015 GHz 3800059-01 WR62 rectangle PBR14018 GHz 3800064-00 WR42 circular PBR22023/26 GHz 3800065-00 WR42 circular PBR22038 GHz 3800066-00 WR28 circular PBR320

Figure E-2. RFU Rack Mount Kit, P/N 8708272-xx

Installing the Mounting Kits


Installing the Mounting Kits

Installing the Offset Mounting Kit

Install the coax cable, IDU, and antenna as Chapter 2 describes.

Prior to installing nuts on bolts, place a small amount of anti-seize paste on the bolt threads.

To install the offset mounting kit:

Step 1: If not attached, secure the waveguide adapter and strikers to the mounting plate with the include screws and nuts. Figure E-1 shows hardware placement.

Step 2: Use the 3/8-16" U-bolts in the kit to secure the offset mounting plate (Figure E-1) to a vertical pole that is 1.9 to 4.5 inches (48 to 115 mm) in diameter.

Step 3: Torque bolts to 31 ft.-lbs. (42.036 Nm).

Step 4: Place a small amount of lubricant in the groove on the adapter and coat the O-ring, and then slide the O-ring in place.

Step 5: Push the RF unit onto the adapter, keeping proper polarization, and latch the unit to the mounting plate.

Step 6: Screw one end of the flexible waveguide to the adapter on the back of the mounting plate, and screw the opposite end to the antenna feed.

Installing the Rack Mounting Kit

Use the rack mounting kit at sites where you need to keep the RF unit in-doors. The IDU-to-ODU cable may only have to be a few feet long, but the length of ellipical waveguide between the RF unit and antenna will depend on the site.

To install the rack mounting kit:

Step 1: If not attached, secure the waveguide adapter and strikers to the mounting bracket with the included screws and nuts. Figure E-2 shows hardware placement.

Step 2: Use #4-40 screws to secure the mounting bracket (Figure E-2) to the equipment rack.

Step 3: Place a small amount of lubricant in the groove on the adapter and coat the O-ring, and then slide the O-ring in place

Step 4: Push the RF unit onto the adapter, keeping proper polarization, and latch the unit to the bracket.

Step 5: Screw one end of the elliptical waveguide to the adapter on the back of the bracket, and screw the opposite end to the antenna feed.



Selecting WaveguideAdapters on the offset mounting kit and rack mounting kit have rectan-gular and circular interfaces depending on ODU frequency. Table E-G list waveguide mechanical dimension and type for the adapter and for the flex- or ellipical waveguide interface.

NOTE: Flex- and elliptical waveguide flanges must have O-ring seals.

Table E-H lists some of the flexible waveguide available for use with the ODU offset mounting option. Contact MNI sales for different lengths.

Table E-G Adapter to Waveguide Interface Dimensions1

ODUDimension (inch)

Flex Waveguide Type Waveguide FlangeA B C D E

screw7/8 GHz 1.474 1.352 1.178 0.900 8-32 Circular - WR112 PBR8411 GHz 1.280 1.220 0.770 0.400 8-32 Circular - WR90 PBR10013 GHz 1.122 1.040 0.750 0.375 6-32 Rectangular - WR75 PBR12015 GHz 0.956 0.994 0.622 0.311 6-32 Rectangular - WR62 PBR14018 GHz 0.670 0.640 0.420 0.170 4-40 Circular - WR42 PBR22023/26 GHz 0.670 0.640 0.384 0.250 4-40 Circular - WR42 PBR22038 GHz 0.530 0.500 0.280 0.177 4-40 Circular - WR28 PBR320

1. 18-GHz waveguide interface illustrated for example and dimensioning.

Table E-H Flexible Waveguide for Offset Mounting OptionFrequency (GHz) Part Number Waveguide Assembly1 Equivalent (Microtech)

12.7 - 13.3 9901280-00 Flex, WR75 - 24" MTPS075 UWN24B14.4 - 15.3 9901281-00 Flex, WR62 - 24" MTPS062 UWN24B10.7 - 11.7 9901272-00 Flex, WR90 - 36" MTPS090 FWN36B17.7 - 19.7

9901282-00 Flex, WR42 - 24" MTPS042 UWN24B21.2 - 23.624.2 - 26.537.0 - 40.0 905534-30A Flex, SR28 - 24" MTPS028 UWN24B

1. For other lengths contact an MNI representative (U.S. 281-263-6500)

Proteus AMT L-Series Manual Page F-1

Appendix FHot-Standby Protected Radio

OverviewA hot-standby (1:1) radio has two identical co-located terminals (IDU and ODU) connected to a Redundancy Switch Unit (RSU). The RSU provides protection switching for the transmit and receive signal paths.

The hot-standby protected radio configuration uses redundant terminals to protected against equipment or path failure. The antenna and RSU on hot-standby configurations are not redundant.

Protection switching is non-reverting—system will not switch to original radio once alarms clear.

The Redundancy Switch Unit (RSU) handles the switch between main and standby units. Both transmit and receive signal paths switch to-gether. Figure F-1 shows the protected radio configuration.

Both radios operate at the same frequency using an unequal-split coupler assembly connected to a single antenna. The main radio transmit path connects via the through-arm of the coupler while the standby radio con-nects via the coupled arm. Table F-A shows the branching losses in through the coupler.

When a transmit failure occurs, the RSU switches the off-line transmitter on line after a small amount of time from alarm discovery. Once the sec-ondary transmitter is on-line, the far end receivers acquire the new signal and must synchronize before sending data to the output ports. Table F-B list the typical system switch times.

Table F-A Hot-Standby Branching LossPrimary Secondary

Transmitter 1.9 dB 6.5 dB

Receiver 1.9 dB 6.5 dB

Hot-Standby Protected Radio

Page F-2 Proteus AMT L-Series Manual

The receive path uses the same coupler. Threshold on the standby re-ceiver is about 6.5-dB worse and 1.9-dB on the main path. On a properly planned path it is adequate for all but the worst conditions. Normally the system operates only on the primary receivers and switches to standby on hardware failure.

Hot-standby ODUs include an unequal-split coupler (Figure F-2) for RF unit mounting and coupling. The coupler combines RF ports of two RF units to a single antenna. Branching loss through the coupler is 1.9-dB on the main RF unit (transmit and receive) and 6.5-dB on the standby RF unit.

Table F-B Typical Hot-Standby Switching Time

IF BW ManualSwitch

Software(Online Request)

Loss of Signal(Data Input) High BER IDU Power

FailODU Power Fail

28 MHz 281.3 ms 289.1 ms 318.1 ms 432.2 ms 309.1 ms 221.3 ms14 MHz 175.4 ms 161.2 ms 175.4 ms 281.9 ms 190.8 ms 159.2 ms7 MHz 164.2 ms 170.3 ms 196.0 ms 190.6 ms 190.6 ms 181.7 ms3.5 MHz 313.8 ms 374.4 ms 361.4 ms 162.2 ms 162.0 ms 186.7 ms

CONTROL& STATUS

USERDATA

HSB_OP.VSD

COUPLERHOT

STANDBYSWITCH

DATA

IDU(MAIN)

CONTROL& STATUSDATA

ODU(MAIN)

IDU(STANDBY)

ODU(STANDBY)

Figure F-1. Hot-Standby Configuration

Overview


Reverse Channel Switch

A hot-standby radio has redundant standby equipment. Reverse channel switching lets a far-end terminal put the redundant transmitting terminal in operation when a transmitter fails, Figure F-3 [1].

The far-end receive terminal detects a transmit failure [2] that activates a remote transmit alarm [3] that triggers a transmit switch request [4] to the transmit site. The switch request causes the transmitting terminal to put the redundant equipment in operation [5].

RF units fasten to antennas with latches. The antenna has a self-fitting feed assembly for direct 'push-fit' coupling of the RF unit.

Figure F-2. Hot-Standby ODU Mounting with Coupler



The current HSB coupler design comes vertically polarized. An adapter kit is available for horizontal polarization

Original couplers came with an antenna interface vertically polarized, and you rotated the complete RF assembly for horizontal polarization.

Hot-standby couplers come with an push-fit antenna interface fixed for vertical polarization. Set horizontal polarization on the current coupler design by changing out the polarization adapter for a horizontally polar-ized adapter. Ask for kit 8209282-xx; where 'xx' is frequency range of the HSB coupler.

On early-model couplers you had to change the orientation of the RF unit assembly (RFUs and coupler) relative to the fixed mounting position of the antenna, and, on ODUs at 15-GHz and below, also turn the transition on the antenna.

All antenna mounting hardware includes course and fine adjustment points for azimuth and elevation.

ODU(STANDBY)

ODU(MAIN)

IDU(STANDBY)

RSU

IDU(MAIN)

ODU(STANDBY)

ODU(MAIN)

IDU(STANDBY)

RSU

IDU(MAIN)

1

3

2

1

3

5

4

5

Figure F-3. Reverse Channel Switch Operation

Redundancy Switch Unit



The hot-standby (HSB) protected radio has two identical co-located ter-minals (IDU and ODU) connected to a Redundancy Switch Unit (RSU). The switch mounts between the two IDUs (Figure F-4) to provide pro-tection switching for customer input and output signals. Customer input and output as well as IDU control signals connect to the switch, which monitors alarms on both radio paths.

An RSU switches customer data.

Jumper cables link NMS and ports of co-located radios; see Table 2-L.

Switches match IDU line types for ANSI or ETSI systems.

• P/N 8209265-18, 16E1 Redundancy Switch Unit• P/N 8209265-19, 16DS1 Redundancy Switch Unit

The RSU has automatic and manual switch modes. Normally, the switch remains in AUTO mode. With no alarms the switch sends line signals through the main path. If RSU logic detects a traffic-affecting alarm on the local (near-end) radio, it routes user traffic to the alternate path. Near-end radio transmit and receive paths change simultaneously, but the far-end radio path stays in its current state.

A hot-standby switch is non-reverting and is not hitless.

Auto-switching logic begins at the main terminal, but once switched does not revert signals to the main path–even after alarms clear. On mul-tiple alarms, major alarms have priority over minor alarms. If both paths have major alarms, switch logic locks the system in its current state until one terminal operates normally.

Manual switching is a user-controlled switch for maintenance and test-ing. Manual switch has priority over switch logic.

Switching is not hitless and errors occur each time the path switches. Preventing RSU logic from reverting signals to the main path after alarms clear allows a technician or operator to return the system to the primary path at the least disruptive time.

Both ODUs operate on the same frequency and connect to the same an-tenna through a directional coupler. The active path transmits directly to

IDU A

RSU

IDU B

Figure F-4. Hot-Standby Indoor Equipment



the antenna. The transmitter of the path in standby gets attenuated by at least 50 dB with a mute attenuator at the output of the transmit oscillator.

RSU Front Panel Features

Figure F-5 shows the Redundancy Switch Unit (RSU) front-panel fea-tures that Table F-C describes the common features. The right side of the front panel includes a ground lug for attaching ESD protection devices.

All versions of the RSU have connections for 100BaseT Ethernet data from the IDU: ETH1/2, ETH1/2 A, and ETH1/2 B. The RSU only switches one of the 100BaseT IDU ports.

1 2 3 4 5 6 7 8 9Figure F-5. RSU Front Panel

Table F-C Common RSU Front-Panel Features1 16

CHANNEL I/O

DB78 high-density connector; 120-Ω balanced for E1; 100-Ω for DS1. Mating connector, PN 3070037-05, included.

2 IDU A/B & AUTO

Online LEDs; light when switch activates associated mode. Manual mode is either IDU A or B. AUTO allows logic to determine appropriate switch.

3 AUTO/MAN SWITCH

Toggle switch. For manual override to main or standby radio path. AUTO position allows switch logic to select the appropriate path.

4 NMS RJ45 NMS port for customer connection to the 64-kbps out-of-band channel. When connecting radios back-to-back, auto-sensing and auto-negotia-tion handle port configuration. Cable auto-sensing (MDI/MDIX) is always enabled, and works for most hubs and radios.

5 ETH1/2 RJ45 ETH1/2 ports connect customer 100BaseT Ethernet.

6 NMS A/B RJ45 NMS port to connect NMS data from and to the IDUs. Use with the 64-kbps out-of-band channel.

7 ETH1/2 A/B RJ45 ETH1/2 ports connect 10/100BaseT Ethernet to the A or B IDU.

8 HSBY A/B DB26 high density sub-D connection for connecting power, controls, and alarms from and to the IDUs.

9 IDU A/B DB78 high-density connector for line signals to the IDU; 120-Ω balanced for E1; 100-Ω for DS1. con-nects to the IDU with the 8108724-00 cable assembly included with the hot-standby cable kit.

NMS port speed and duplex settings are configurable.Settings include:

Powered Down,Auto-negotiate (default),10BaseT Half-duplex,10BaseT Full-duplex,100BaseT Half-duplex100BaseT Full-duplex.



RSU Interconnect Cables

Hot-standby cables connect customer data and radio control signals from the Redundancy Switch Unit (RSU) to both main and standby IDUs. See Chapter 2, Installation, for connector details.

All versions of the RSU have connections for 100BaseT systems. The RSU has three RJ45 connectors: customer input, main radio, and second-ary radio. Although the 100BaseT LIM has four ports, the current RSU provides one switch-protected path.

Figure F-6. IDU to RSU Connections

Table F-DItem 1. & 4

Table F-DItem 2.

Table F-DItem 3a.

Table F-D Hot-Standby Radio Interconnect CablesItem Part Number Description Qty1 8108726-01 Ethernet Cables, RJ45, 8", 100BT, crossover 62 8108658-00 HSBY Cables, 2 x DB26P, shielded 23a 8108724-00 Line I/O Cables, 2 x DB78P, 6", narrow backshell 23b 3070037-05 Line I/O Conn., DB78P, hi-den., solder cup 14 8108726-00 Ethernet Cables, RJ45, 13", 100BT, crossover 3



Installing the Redundancy Switch Unit

Mounting the RSUMount the RSU shelf in the standard 19-inch equipment rack or equip-ment cabinet between the main and standby IDU. The RSU takes one rack unit (RU) of space. An installed hot-standby IDU mounts in three (3) RUs.

Interconnecting the IDU and RSUHot-standby cables connect user data and radio management data from the Redundancy Switch Unit (RSU) to both main and standby IDUs. Call outs in Figure F-7 refer to the cables in Table F-D.

The current RSU provides one switch-protected Ethernet path. RJ45 ca-bles connects 100-Mbps Ethernet data using 8-position modular connec-tors on CAT5 unshielded twisted pair (UTP) cable.

Use RJ45 cross-over cables (8108726-01) when two connecting the IDU to the RSU. Table F-E lists crossover pinning.

Once you connect Ethernet data you must set up IP data routing and as Appendix D describes

3a2143bFigure F-7. IDU to RSU Connections

Table F-E 100-BaseT Wiring (RJ45) 2-port bridge

Pin Signal I/O Pin Signal I/O1 Rx + I 5 GND2 Rx – I 6 TX – O3 Tx + O 7 GND4 GND 8 GND

18

Installing the Redundancy Switch Unit


Connecting E1/T1 Line Signals to the RSULine input and output connect to the RSU in the same way they connect to the IDU line connectors. To wire each I/O, follow cable pin-outs in Table 2-D on Page 2-11 or in Table 2-F on Page 2-13.

Line ports are auto-sensing so the RSU does not need configuration.

Use the twisted pair sets of your cable for each ring/tip signal of E1/DS1 lines.

Do not untwist any pair more than 12.7 mm (1/2 inch).

Line input and output signals connect with a DB78 female connector provided in the installation kit (Table 2-A). Line signals (Table F-F) con-nect via twisted-pair wire to the E1/DS1 channels.

MNI sells a pre-fabricated DB78 cable, Figure F-8, suitable for wire wrap. The cable is shielded 100-ohm cable, Essex 55-A99-21 (T1/E1 rated), with a metal shell connector – AMP 748368-1. Table F-G lists the DB-78 cable pinning.

Table F-F E1/T1 Line Wiring on DB78

Pin Signal Ch. Pin Signal Ch. Pin Signal Ch. Pin Signal Ch.1 TXT 15 21 TXR 15 40 TXT 16 60 TXR 162 RXT 15 22 RXR 15 41 RXT 16 61 RXR 163 GND 23 TXT 13 42 GND 62 TXT 144 TXR 13 24 RXT 13 43 TXR 14 63 RXT 145 RXR 13 25 GND 44 RXR 14 64 GND6 TXT 11 26 TXR 11 45 TXT 12 65 TXR 127 RXT 11 27 RXR 11 46 RXT 12 66 RXR 128 GND 28 TXT 9 47 GND 67 TXT 109 TXR 9 29 RXT 9 48 TXR 10 68 RXT 1010 RXR 9 30 GND 49 RXR 10 69 GND11 TXT 7 31 TXR 7 50 TXT 8 70 TXR 812 RXT 7 32 RXR 7 51 RXT 8 71 RXR 813 GND 33 TXT 5 52 GND 72 TXT 614 TXR 5 34 RXT 5 53 TXR 6 73 RXT 615 RXR 5 35 GND 54 RXR 6 74 GND16 TXT 3 36 TXR 3 55 TXT 4 75 TXR 417 RXT 3 37 RXR 3 56 RXT 4 76 RXR 418 GND 38 TXT 1 57 GND 77 TXT 219 TXR 1 39 RXT 1 58 TXR 2 78 RXT 220 RXR 1 59 RXR 2

Female front panel con-nector shown; mating connector pins are the mirror image (Page F-10).

1



Table F-G Prefabricated DB78P Cable Wire List Pin Color Signal Pin Color Signal Pin Color Signal1 BLU/WHT TXT 15 33 BLK/BLU TXT 5 66 VIO/ORG RXR 1221 WHT/BLU TXR 15 15 ORG/BLK RXR 5 47 NONE GND3 NONE GND 34 BLK/ORG RXT 5 48 GRN/VIO TXR 102 ORG/WHT RXT 15 35 NONE GND 67 VIO/GRN TXT 1022 WHT/ORG RXR 15 16 GRN/BLK TXT 3 49 BRN/VIO RXR 104 GRN/WHT TXR 13 36 BLK/GRN TXR 3 68 VIO/BRN RXT 1023 WHT/GRN TXT 13 17 BRN/BLK RXT 3 69 NONE GND5 BRN/WHT RXR 13 37 BLK/BRN RXR 3 50 GRY/VIO TXT 824 WHT/BRN RXT 13 18 NONE GND 70 VIO/GRY TXR 825 NONE GND 19 GRY/BLK TXR 1 51 BLU/WHT RXT 86 GRY/WHT TXT 11 38 BLK/GRY TXT 1 71 WHT/BLU RXR 826 WHT/GRY TXR 11 20 BLU/YEL RXR 1 52 NONE GND7 BLU/RED RXT 11 39 YEL/BLU RXT 1 53 ORG/WHT TXR 627 RED/BLU RXR 11 40 ORG/YEL TXT 16 72 WHT/ORG TXT 68 NONE GND 60 YEL/ORG TXR 16 54 GRN/WHT RXR 69 ORG/RED TXR 9 41 GRN/YEL RXT 16 73 WHT/GRN RXT 628 RED/ORG TXT 9 61 YEL/GRN RXR 16 74 NONE GND10 GRN/RED RXR 9 42 NONE GND 55 BRN/WHT TXT 429 RED/GRN RXT 9 43 BRN/YEL TXR 14 75 WHT/BRN TXR 430 NONE GND 62 YEL/BRN TXT 14 56 GRY/WHT RXT 411 BRN/RED TXT 7 44 GRY/YEL RXR 14 76 WHT/GRY RXR 431 RED/BRN TXR 7 63 YEL/GRY RXT 14 57 NONE GND12 GRY/RED RXT 7 64 NONE GND 58 BLU/RED TXR 232 RED/GRY RXR 7 45 BLU/VIO TXT 12 77 RED/BLU TXT 213 NONE GND 65 VIO/BLU TXR 12 59 ORG/RED RXR 214 BLU/BLK TXR 5 46 ORG/VIO RXT 12 78 RED/ORG RXT 2

Pins in the shaded area are for those wires in an inner wht/org binder

Figure F-8. Prefabricated DB78P Cable

Installing the HSB ODU



Torque Specifications

Table F-H lists recommended torques for tightening nuts and bolts pro-vided with the hardware kits. Prior to installing RF Unit hardware, place a small amount of anti-seize lubricant on bolt threads.

Unpacking Hardware

Carefully unpack the antenna assembly and mount from its shipping car-ton. The standard 0.3- and 0.6-meter (1- and 2-ft.) antennas ship partially assembled and include the following components:

• reflector and radome assemblies• feed assembly• offset tower mount• various bolts, nuts, flat washers, lock washers, allen keys• tube of Loctite

Table F-H Fastener Torque SpecificationsUS Recommended Bolt Torque*

Size Grade 5 Grade 8 18-8 S/SCoarse Fine Coarse Fine Coarse Fine

#4 - - - - 5.2 -#6 - - - - 9.6 -#8 - - - - 19.8 -#10 - - - - 22.8 31.71/4 8 10 12 14 6.3 7.85/16 17 19 24 27 11 11.83/8 31 35 44 49 20 227/16 49 55 70 78 31 331/2 75 85 105 120 43 459/16 110 120 155 170 57 63

Metric Recommended Bolt Torque (Nm)Diameter Class 8.8 Class 10.95 7 96 12 168 30 4010 55 7512 100 13514 160 21516 245 33520 480 650* Sizes from 4 to 10 are in inch-pounds.

Sizes from 1/4 up are in foot-pounds.



Attaching the Standard Mounting AssemblyThe following covers standard direct-fit mounting. Appendix E describes offset and rack mounting options.

Mounting hardware attaches the antenna to a vertical pole with a diame-ter of 48 to 115 mm (1.9 to 4.5 inches). The assembly adjusts to ±25� fine elevation and ±180� (±10� fine) azimuth. Approximate mounting di-mensions for a protected unit in Figure F-9 can help you determine in-stallation requirements

A

+

Dim B

Dim C

NOTES: 1.

2.

3.

ANT POLE MOUNTING DETAILS VARY.

ODU CAN MOUNT ON EITHER SIDE OF POLE.

DIMENSIONS ARE APPROXIMATE.

Dim G

ODU

ODU

ODU

HSB ODU DIMENSIONS (mm)

DIM A DIM B DIM C DIM D DIM E DIM F DIM G1 FT / .3M ANT 398 289 278 110 220 42 3002 FT / .6M ANT 651 410 292 110 220 42 2242.5 FT / .8M ANT 889 622 301 153 338 NA 1354 FT / 1.2 ANT 1248 904 414 538 1074 NA 70

Figure F-9. Protected ODU Mounting Dimensions



Use the following steps to attach the mounting assembly to the pipe (or pole).

Step 1: Attach the mounting bracket around the pipe for left or right offset (left offset shown below).

Step 2: Secure the mounting assembly with included flat washers, lock washers, and bolts.

Step 3: Move the hardware around the pipe so the antenna faces the final azimuth direction. Tighten after antenna alignment is complete.



Attaching the Antenna to the Mounting AssemblyStep 1: Remove the lower drain plug(s) from the reflector, and then

attach the radome to the reflector using the included pan-head screws, lockwashers, and flat washers. Position the radome drain hole at the bottom.

Step 2: Coat the threads of the socket-head screws on the antenna mounting plate with the included anti-seize compound (Loctite).

Step 3: Align and secure the antenna to the mounting assembly with the socket-head screws. The hardware kit includes an allen key that fits the mounting screws.

Step 4: Apply the silicone grease to the included antenna feed o-ring. Install the o-ring on the antenna feed assembly.



Attaching the RF Unit to the Antenna

Non-Protected Units

The antenna has a feed assembly that couples the non-protected RF unit directly to the antenna. Install the RF unit after properly installing the an-tenna feed o-ring.

You change the orientation of the RF unit assembly relative to the fixed mounting position of the antenna for horizontal polarization.

Hot-Standby Protected Units

A hot-standby ODU has two RF units mounted on a coupler / mounting assembly. The coupler connects to the antenna like the non-protected RF unit. Snap fasteners hold the assembly in place and four socket-head screws secure it to the back of the antenna

Hot-standby couplers come with vertically polarized antenna interfaces. When you need horizontal polarization use the horizontal polarization kit – 8209282-xx; where 'xx' is frequency range of the HSB coupler.

On early-model couplers you changed to horizontal polarization by changing the orientation of the complete RF unit assembly (RFUs and coupler) relative to the fixed mounting position of the antenna, and, on ODUs at 15-GHz and below, also turn the transition on the antenna.

Step 1: Observe the V label on the RF unit housing. The V label must point up for vertical polarization.

Step 2: For non-protected units: remove the polyester tape covering the antenna feed assembly and carefully fit the RF unit to the antenna. Gently press into place.

Step 3: Secure the RF unit to the mounting assembly using the four snap fasteners.



.

NOTE: The current coupler design has a removable vertical polarization interface, which you can replace with a horizontal polarization adapter. Original hot-standby coupler/combiners come with an antenna interface fixed to vertical polarization. Rotate the complete assembly for horizontal polarization.

Step 1: For hot-standby protected units: Coat the threads of the socket-head screws on the coupler with the included anti-seize compound (Loctite).

Step 2: Carefully place the feed hub of the coupler over the antenna feed assembly. Gently press coupler in place. Lock the assembly to the antenna using the four snap fasteners. Screw the socket-head screws to the antenna and tighten using the allen key from the hardware kit.

Step 3: Remove the plastic covers from the coupler feed assemblies and apply silicone grease from the hardware kit to the o-rings

Step 4: Remove the polyester tape covering the the feed and carefully fit the RF unit on the coupler.

Step 5: Secure the RF unit to the coupler assembly using the four snap fasteners.



Connecting the Coaxial Cable to the ODU

WARNING DO NOT WORK IN FRONT OF AN ENERGIZED ODU!The power-density level at the open end of any RF-Unit output when transmitting exceeds the level recommended by American National Standards Institute (ANSI) C95.1-1992.

Step 1: Attach the coaxial cable(s) to the ODU(s). Step 2: Weatherproof all connections using amalgamating tape for

weatherproofing as described in Chapter 2.

Step 3: Connect a 6-AWG copper wire (not supplied) from the ODU grounding post to a ground point on the tower. This grounding cable places the ODU at the same electrical potential as the mounting pipe.

Step 4: Before leaving the site, check that all hardware on the mount, shroud, radome and ODU are secure. Visually inspect the antenna and ODU once a year.



Proteus AMT L-Series Manual Page G-1

Appendix GEthernet Performance

OverviewTable G-A shows the typical throughput and latency expected for each capacity using the Ethernet payload in ETSI configurations. The table covers from 64- to 1518-byte frame size.

Table G-A Throughput and Latency for Ethernet Data in ETSI Bandwidths

Modulation Capacity Frame Size(bytes)

Throughput(Mbps)

Latency(ms)

3.5 MHz

QPSK - 100BT

64 4.92 2.625128 4.53 2.729256 4.32 3.055512 4.22 3.6301024 4.17 4.7671280 4.15 5.2741518 4.15 5.767

8PSK - 100BT

64 9.84 2.760128 9.06 2.805256 8.64 2.982512 8.44 3.2701024 8.33 3.8771280 8.30 4.2081518 8.29 4.491

8PSK 2E1 100BT

64 4.92 2.800128 4.53 2.944256 4.32 3.209512 4.22 3.7651024 4.17 4.9011280 4.15 5.4921518 4.15 5.992

7 MHz

QPSK - 100BT

64 9.84 1.327128 9.05 1.396256 8.64 1.548512 8.43 1.8691024 8.32 2.4951280 8.29 2.8111518 8.28 3.081

Ethernet Performance

Page G-2 Proteus AMT L-Series Manual

7 MHz

8PSK - 100BT

64 19.67 1.379128 18.11 1.426256 17.27 1.523512 16.85 1.7051024 16.63 2.0851280 16.58 2.2701518 16.56 2.445

QPSK 2E1 100BT

64 4.92 1.419128 4.53 1.527256 4.33 1.847512 4.23 2.3761024 4.18 3.5031280 4.16 4.0601518 4.16 4.597

8PSK 2E1 100BT

64 14.75 1.395128 13.58 1.448256 12.96 1.560512 12.64 1.7981024 12.47 2.2541280 12.44 2.4811518 12.42 2.686

8PSK 4E1 100BT

64 9.84 1.411128 9.06 1.497256 8.64 1.648512 8.44 1.9601024 8.33 2.5831280 8.30 2.8951518 8.29 3.194

14 MHz

QPSK - 100BT

64 19.67 1.176128 18.11 1.219256 17.28 1.312512 16.85 1.5031024 16.63 1.8761280 16.59 2.0651518 16.56 2.239

8PSK - 100BT

64 39.34 1.201128 36.21 1.232256 34.54 1.296512 33.69 1.4221024 33.24 1.6711280 33.16 1.7971518 33.10 1.911

QPSK 2E1 100BT

64 14.75 1.186128 13.58 1.246256 12.95 1.363512 12.64 1.5891024 12.47 2.0391280 12.44 2.2721518 12.42 2.483



Throughput(Mbps)

Latency(ms)

Overview


14 MHz

8PSK 2E1 100BT

64 34.42 1.205128 31.68 1.237256 30.22 1.306512 29.47 1.4371024 29.08 1.7061280 29.01 1.8431518 28.97 1.957

QPSK 4E1 100BT

64 9.84 1.210128 9.06 1.289256 8.64 1.437512 8.44 1.7421024 8.33 2.3741280 8.30 2.6981518 8.29 2.971

8PSK 4E1 100BT

64 29.50 1.211128 27.16 1.245256 25.91 1.315512 25.26 1.4681024 24.93 1.7501280 24.87 1.9021518 24.83 2.035

8PSK 8E1 100BT

64 19.68 1.224128 18.12 1.266256 17.29 1.373512 16.88 1.5581024 16.65 1.9161280 16.61 2.1071518 16.59 2.284

28 MHz

QPSK - 100BT

64 39.34 0.677128 36.21 0.708256 34.54 0.766512 33.69 0.8951024 33.24 1.1421280 33.16 1.2701518 33.10 1.379

8PSK - 100BT

64 61.46 0.649128 56.57 0.667256 53.97 0.723512 52.63 0.8251024 51.94 1.0211280 51.80 1.1261518 51.72 1.223

QPSK 2E1 100BT

64 34.42 0.673128 31.68 0.707256 30.22 0.780512 29.47 0.9161024 29.09 1.1741280 29.01 1.3111518 28.97 1.434



Throughput(Mbps)

Latency(ms)



28 MHz

8PSK 2E1 100BT

64 56.54 0.645128 52.05 0.673256 49.65 0.727512 48.42 0.8311024 47.79 1.0401280 47.65 1.1481518 47.58 1.246

QPSK 4E1 100BT

64 29.50 0.678128 27.16 0.718256 25.90 0.790512 25.26 0.9331024 24.93 1.2261280 24.87 1.3691518 24.83 1.506

8PSK 4E1 100BT

64 51.63 0.646128 47.52 0.678256 45.33 0.731512 44.21 0.8381024 43.63 1.0601280 43.52 1.1661518 43.45 1.266

QPSK 8E1 100BT

64 19.67 0.698128 18.11 0.743256 17.27 0.833512 16.85 1.0221024 16.63 1.3941280 16.58 1.5801518 16.56 1.748

8PSK 8E1 100BT

64 41.79 0.654128 38.47 0.680256 36.70 0.744512 35.79 0.8591024 35.32 1.1031280 35.23 1.2221518 35.17 1.336

QPSK 12E1 100BT

64 9.84 0.734128 9.06 0.813256 8.64 0.968512 8.43 1.2751024 8.32 1.9041280 8.30 2.2181518 8.28 2.497

8PSK 12E1 100BT

64 31.96 0.654128 29.42 0.694256 28.07 0.761512 27.38 0.8991024 27.02 1.1781280 26.95 1.3161518 26.91 1.440



Throughput(Mbps)

Latency(ms)

Overview


28 MHz

8PSK 16E1 100BT

64 22.13 0.667128 20.37 0.710256 19.43 0.801512 18.96 0.9661024 18.71 1.3141280 18.66 1.4841518 18.63 1.644



Throughput(Mbps)

Latency(ms)



Documents

L-Series Digital Microwave Radio